lightninglabs / lightninglabs/taproot-assets
[feature]: Multihop routing for taproot assets and Bitcoin taproot channels
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 525
- Forks
- 150
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 31
Description
When the taproot assets (TA) are sent over Lightning, a double conversion TA->BTC->TA leads to high transaction fees since edge nodes will likely set a high price spread to hedge against price risks. AFAIK such behavior is a result of TA channels being private. Additionally, the underlying Bitcoin Taproot channel does not participate in routing since it is private too.
Is it possible to make the TA channel public? In that case, routings like TA-> TA-> TA would be much cheaper than transactions with double conversion.
Alternatively, can the underlying Bitcoin Taproot channel be set as public so that it can participate in the routing?
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 tracing how taproot asset channels and underlying Bitcoin Taproot channels are represented for privacy and routing, then compare the proposed public-channel alternatives; done requires a defined approach for multihop TA routing and corresponding validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100