liftedinit / liftedinit/many-rs
Discover a way to move proof key calculation into background/uniform process
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
The current proof implementation requires a direct treatment of collection of all of the keys used to serve a particular endpoint for submission for construction of a proof. It would be desirable to make this process uniform and automated in some way. However, the naive solution of creating a wrapper type that interacts with the underlying merk store runs into issues.
References:
Wrapper type issues - https://coda.io/d/LedgerStore-Proof-Wrapper-Design_dNuzHODZzxm/LedgerStore-Proof-Wrapper-Design_suJTS
Proof implementation PR - https://github.com/liftedinit/many-rs/pull/245
Proof spec PR - https://github.com/many-protocol/specification/pull/89
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the proof implementation PR and proof spec PR linked in the issue, then review the linked wrapper type design discussion. Determine how proof keys are currently collected for an endpoint and what constraints prevent a wrapper around the merk store. Done means the calculation is uniform and automated without requiring direct key collection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100