lightninglabs / lightninglabs/taproot-assets
Optionally generate compressed tap addresses
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
Currently, the tap address (produced by the receiver during the asset send process) is sub-optimally compressed. As an upside, parts of the address in its current format can be trivially interpreted for human readability.
We should add the necessary functionality to produce a compressed tap address.
This issue is incomplete. I will add further details before it can be included in a sprint.
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. It says the tap address is produced by the receiver during the asset send process, so start there after the promised details are added. Done should mean optionally producing a compressed tap address while retaining the current format's human-readable portions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100