New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

[Interop] Lock Commitment #710

Open

Therecanbeonlyone1969 opened this issue Jul 14, 2023 · 1 comment

Assignees

Labels

Collaborator

Therecanbeonlyone1969 commented Jul 14, 2023

We need to finalize a decision on Lock Commitment for the BPI State Object the Interop Worksteps are working on:

Suggestion:

Use Sparse Merkle Tree (SMT) since this allows proof-of-non-membership of the hash of the BPI State Object.

That then needs a separate Smart Contract to

store the Merkle Proof & verify it
verification function that proof is correct (proof has to be verified onchain only once, and then we just need a mapping that says that the proof for this commitment was verified
Store function only for owning BPI
Verification function open to public

Therecanbeonlyone1969 self-assigned this

Therecanbeonlyone1969 added the Interop Demo label

Collaborator Author

Therecanbeonlyone1969 commented Jul 21, 2023 •

edited

Loading

Interop WG Meeting 7/21 agrees to use SMTs for lock commitments. @Therecanbeonlyone1969 to write the contract and PR it.

# for free to join this conversation on GitHub. Already have an account? # to comment