mirror of
https://github.com/selfxyz/self.git
synced 2026-01-10 07:08:10 -05:00
readme
This commit is contained in:
26
README.md
26
README.md
@@ -1,20 +1,14 @@
|
||||
# Passport SBT - ETHGlobal Paris
|
||||
# Embassy
|
||||
|
||||
This is our submission for the ETHGlobal Paris Hackathon.
|
||||
A monorepo for embassy, a proof of passport protocol.
|
||||
|
||||
The goal is too let users scan the NFC chip in their government-issued passport to prove that
|
||||
it is valid. If valid, the user can generate a proof that can be verified onchain. We are using
|
||||
that proof to mint them a Soulbound Token (SBT) they can use to show that they indeed hold
|
||||
Embassy lets users scan the NFC chip in their government-issued passport.
|
||||
If the signature is valid, the user can generate a proof that can be verified onchain.
|
||||
We are using that proof to mint them a Soulbound Token (SBT) they can use to show that they indeed hold
|
||||
an official passport.
|
||||
|
||||
We forked two repositories and added functionality to make everything work.
|
||||
|
||||
- [passport-reader](https://github.com/tananaev/passport-reader/tree/master): Android app to scan passports
|
||||
- [zkrsa](https://github.com/dmpierre/zkrsa/tree/main): ZK Circuit to prove RSA signature onchain and frontend to generate the proofs
|
||||
|
||||
### Roadmap
|
||||
|
||||
- ✅ Make sure we can extract the signature from a passport
|
||||
- ✅ Make sure we can actually verify that a passport signature is signed by the issuing country
|
||||
- ✅ Modify the Next.js frontend of `zkrsa` in order to accept an endpoint that stores signature data from someone scanning their passports
|
||||
- ✅ Get zkrsa working with the signature format we are able to retrieve from the Android app
|
||||
@@ -26,12 +20,4 @@ We forked two repositories and added functionality to make everything work.
|
||||
- 🚧 Decompose the hashed eContent of the passport into the private user data and reconstitute them in the circuit
|
||||
- ✅ Modify the Android app to let people send their signature data to the Next.js backend (and store it temporarily)
|
||||
- 🚧 Safe Module to claim a Safe if holding the right SBT
|
||||
- 🚧 Using Sismo Data Groups or EAS Attestations to let people prove they own such an SBT without revealing which one
|
||||
|
||||
Deployments :
|
||||
|
||||
- gnosis: 0x9c891A2C692D672059a171b4499eC3c61093eC34
|
||||
- goerli: 0x64390f86E8986FEb2f0E2E38e9392d5eBa0d0C48
|
||||
- polygon: 0x9c891A2C692D672059a171b4499eC3c61093eC34
|
||||
- neon evm devnet: 0xBf79f2F49e9c4F1284149ddEFfB5CA4325bf4226
|
||||
- celo alfajores: 0x9c891A2C692D672059a171b4499eC3c61093eC34
|
||||
-
|
||||
Reference in New Issue
Block a user