lightninglabs / lightninglabs/taproot-assets
[feature]: Improve supply verifier syncer: retries and missing supply commit insertion
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
The supply verifier syncer should be improved in the following ways:
-
Retry with backoff: When connecting to a universe server or attempting to fetch/insert a supply commitment, the syncer should apply backoff and retry logic on failure.
-
Handle missing prior supply commits: If the universe server rejects a supply commit because it is missing one or more prior supply commits (e.g., the one being inserted has a spent supply commit outpoint that the server doesn't recognize), the syncer should attempt to insert the missing earlier supply commits first, then retry the original insertion.
Notes
- Syncer code:
universe/supplyverifier/syncer.go
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 in universe/supplyverifier/syncer.go and trace the connection, supply commitment fetch, and insertion paths. Check how failures and missing prior supply commits are surfaced; done means those operations retry with backoff, missing earlier commits are inserted first, and the original insertion is retried.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100