📅 Original date posted:2020-12-28
📝 Original message:
Good morning list,
Before we close this amazing year, I wanted to give you an update and reboot
excitement around trampoline routing for 2021.
Acinq has been running a trampoline node for more than a year to provide
simple
and reliable payments for tens of thousands of Phoenix [1] users. We've
learned
a lot and I just opened a new trampoline routing spec PR to reflect that
[2].
The TL;DR is:
* it's simpler than the previous proposal and more flexible
* it makes MPP more cost-efficient and reliable
* it works nicely with rendezvous or route blinding
* it's as private as normal payments (likely more private) if used properly
(details in the PR)
I strongly believe the current state of trampoline routing can provide great
benefits in terms of wallet UX and reliability, but we need more reviews for
the spec to converge before it can be broadly deployed without fear of
moving
parts or breaking changes. Please have a look at the proposal without
preconceived ideas; you may be surprised by how simple and natural it feels.
I also want to stress that the code changes are very reasonable as it
re-uses
a lot of components that are already part of every lightning implementation
and
doesn't introduce new assumptions.
As a matter of fact, an independent implementation has been completed by the
Electrum team and has been recently tested E2E on mainnet! Having a spec
agreement on feature bits, invoice hints format and onion error codes would
allow their wallet to fully interoperate with Phoenix and future trampoline
wallets, as well as unblock development of even more improvements.
Happy end of year to all and stay #reckless in 2021!
Bastien
[1] https://phoenix.acinq.co/
[2] https://github.com/lightningnetwork/lightning-rfc/pull/829
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20201228/3e357e16/attachment.html>;
Bastien TEINTURIER [ARCHIVE] /
npub17f…ntr0s
2023-06-09 13:01:48
in reply to nevent1q…93td
Author Public Key
npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0sPublished at
2023-06-09 13:01:48Event JSON
{
"id": "41374d4d1f8999935c3dbf49c45842bfe9c9268c6b29fa1439069f2ab78bfb06",
"pubkey": "f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb",
"created_at": 1686315708,
"kind": 1,
"tags": [
[
"e",
"69a59f1b4851854b52bd39326adcbb4a5f19c1e07075e61719d565d7979bdd61",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2020-12-28\n📝 Original message:\nGood morning list,\n\nBefore we close this amazing year, I wanted to give you an update and reboot\nexcitement around trampoline routing for 2021.\n\nAcinq has been running a trampoline node for more than a year to provide\nsimple\nand reliable payments for tens of thousands of Phoenix [1] users. We've\nlearned\na lot and I just opened a new trampoline routing spec PR to reflect that\n[2].\n\nThe TL;DR is:\n\n* it's simpler than the previous proposal and more flexible\n* it makes MPP more cost-efficient and reliable\n* it works nicely with rendezvous or route blinding\n* it's as private as normal payments (likely more private) if used properly\n(details in the PR)\n\nI strongly believe the current state of trampoline routing can provide great\nbenefits in terms of wallet UX and reliability, but we need more reviews for\nthe spec to converge before it can be broadly deployed without fear of\nmoving\nparts or breaking changes. Please have a look at the proposal without\npreconceived ideas; you may be surprised by how simple and natural it feels.\n\nI also want to stress that the code changes are very reasonable as it\nre-uses\na lot of components that are already part of every lightning implementation\nand\ndoesn't introduce new assumptions.\n\nAs a matter of fact, an independent implementation has been completed by the\nElectrum team and has been recently tested E2E on mainnet! Having a spec\nagreement on feature bits, invoice hints format and onion error codes would\nallow their wallet to fully interoperate with Phoenix and future trampoline\nwallets, as well as unblock development of even more improvements.\n\nHappy end of year to all and stay #reckless in 2021!\n\nBastien\n\n[1] https://phoenix.acinq.co/\n[2] https://github.com/lightningnetwork/lightning-rfc/pull/829\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20201228/3e357e16/attachment.html\u003e",
"sig": "1ab521943d77868451346d69668512f6f316baa857c35031fce89baddac0f0174f32313f554cd132951ddc398696953bd850e093f331d152274a35097abad0a3"
}