lightninglabs / lightninglabs/taproot-assets
Add tombstone handling to `asset.New`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
https://github.com/lightninglabs/taro-private/pull/30#discussion_r1186565730
-Update `asset.New` to reject 0-value assets that do not use the NUMS key
-Error on assets with the NUMS key and non-zero amounts
This may have to change once we sort out the standard for burning.
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
Start at the asset.New entry point and read the linked pull-request discussion for the intended tombstone rules. Verify the zero-value and NUMS-key cases described in the issue, and confirm the behavior against existing asset tests if present; the result should reject non-NUMS zero-value assets and NUMS-key assets with non-zero amounts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100