lightninglabs / lightninglabs/taproot-assets
file: use append only merkle-tree or SMT in the file format to allow for probabilistic verification?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
The file format will grow linearly as the number of transfers do. One idea to reduce validation costs somewhat (though it can be parallelized) is to commit to a tree of all the individual transitions in the file. Given this tree, a verifier can use a hash function as a random oracle (a la the fiat shamir transform) to implement probabilistic verification, in a cut-and-choose style. A verifier would then repeat this verification in order to achieve a negligible probability of a fake asset/file.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the file-format validation and transition-commitment paths, then evaluate the append-only Merkle-tree or SMT proposal against the probabilistic-verification goal; done means an agreed design with the required implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100