Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support trampoline routing
See original GitHub issueUnder development, see https://github.com/spesmilo/electrum/commits/trampoline
Note that the spec is not ready yet, only Phoenix currently uses it (with an Eclair node).
One issue with the incomplete spec is that trampoline fees have to be guessed; indeed, Eclair does not return a node_update payload in its error messages, because the Acinq devs have not decided of the format for new gossip messages. Having to guess fees makes it difficult to perform multi-trampoline routing.
I think we should still deploy this now, the user experience is much better than with local routing. In addition, the gossip part of the spec might not make any progress for years if there is no demand for it.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
merged, closing
see #6966