You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ProofService is a zero-trust identity binding protocol.
All binding record is signed by user’s asymmetric keypair (called Avatar, currently secp256k1).
So there is a possibility to put ProofRecord’s existed binding record onto secp256k1-related blockchain, so that “smart contract”-ish on-chain program can use these data.
Expected outcomes
Build a smart contract on EVM-based chain which holds all the binding records. It should at least:
Accept new record uploading (and verifying the signature before saving)
Has a public function to let other contract query these saved binding records.
Modify proof_server to upload every new record onto this contract.
Description
ProofService is a zero-trust identity binding protocol.
All binding record is signed by user’s asymmetric keypair (called Avatar, currently
secp256k1
).So there is a possibility to put ProofRecord’s existed binding record onto
secp256k1
-related blockchain, so that “smart contract”-ish on-chain program can use these data.Expected outcomes
proof_server
to upload every new record onto this contract.Skills required
solidity
)Mentor
Nyk Ma @nykma
Expected size of project
175h
Level
Medium
The text was updated successfully, but these errors were encountered: