{"type":"rich","version":"1.0","author_name":"npub1vjzmc45k8dgujppapp2ue20h3l9apnsntgv4c0ukncvv549q64gsz4x8dd","author_url":"https://nostr.ae/npub1vjzmc45k8dgujppapp2ue20h3l9apnsntgv4c0ukncvv549q64gsz4x8dd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2022-11-24\n📝 Original message:\nHi Clara,\n\nI think the simplest recommended policy you can devise is credential shown\nto the routing hop should cover for full routing fees, therefore the\nrouting hop benefits from a zero-jamming risk situation. Then you can\nappreciate the \"liquidity value\" credentials requested in function of your\nlocal channel congestion rate, or even network data. Increasing your\nreturns in exchange of higher risk exposure. And even more, you can lay on\ntop a reputation layer, where the reputation scores are fully fungible\nagainst monetary credentials, in the acceptance of a HTLC forward request.\n\nSo I think I agree with you a recommended policy is needed, let's just\nstart with a simple one! And refine it with time once we sense we have\nsolid foundations.\n\nBest,\nAntoine\n\n\nLe mer. 23 nov. 2022 à 11:00, Clara Shikhelman \u003cclara.shikhelman at gmail.com\u003e\na écrit :\n\n\u003e Hi Antoine,\n\u003e\n\u003e To discuss your proposed solution in detail, I think that some kind of\n\u003e recommended policy is needed. If presenting one is a low priority, and\n\u003e waiting for other things, my main concern is that it will just never happen\n\u003e (\"any decade now\" kind of situation).\n\u003e\n\u003e Best,\n\u003e Clara\n\u003e\n\u003e On Tue, Nov 22, 2022 at 8:13 PM Antoine Riard \u003cantoine.riard at gmail.com\u003e\n\u003e wrote:\n\u003e\n\u003e\u003e Hi Clara,\n\u003e\u003e\n\u003e\u003e Shared the mail on #lightning-dev Libera chat to get more feedback on\n\u003e\u003e schedule.\n\u003e\u003e\n\u003e\u003e \u003e Do you have a timeline in mind for presenting such a policy?\n\u003e\u003e\n\u003e\u003e See the comments on the BOLT #1043  PR, for now I'm thinking more to\n\u003e\u003e refine the proposed credentials architectural framework.\n\u003e\u003e I think dynamic routing policy in function of channel congestion rate,\n\u003e\u003e and you combine that with reputation to do active risk-management are far\n\u003e\u003e more advanced questions.\n\u003e\u003e\n\u003e\u003e Best,\n\u003e\u003e Antoine\n\u003e\u003e\n\u003e\u003e Le mar. 22 nov. 2022 à 15:54, Clara Shikhelman \u003c\n\u003e\u003e clara.shikhelman at gmail.com\u003e a écrit :\n\u003e\u003e\n\u003e\u003e\u003e Dear All,\n\u003e\u003e\u003e\n\u003e\u003e\u003e If the call time (Monday the 28th at 7 pm UTC) doesn't work out for you,\n\u003e\u003e\u003e please reach out!\n\u003e\u003e\u003e\n\u003e\u003e\u003e Thanks for your quick and detailed response, Antoine.\n\u003e\u003e\u003e\n\u003e\u003e\u003e If by recommend policy, you mean the set of algorithms that should guide\n\u003e\u003e\u003e\u003e the token quantity, rate issuance, token acquisition cost, and the\n\u003e\u003e\u003e\u003e adaptations in function of the local channel congestion, or even the\n\u003e\u003e\u003e\u003e gossips of the other routing nodes, not at all.\n\u003e\u003e\u003e\u003e\n\u003e\u003e\u003e\n\u003e\u003e\u003e Do you have a timeline in mind for presenting such a policy?\n\u003e\u003e\u003e\n\u003e\u003e\u003e Looking forward to discussing this further over the phone call, will\n\u003e\u003e\u003e make some inquiries to make sure the time works for most people.\n\u003e\u003e\u003e\n\u003e\u003e\u003e Best,\n\u003e\u003e\u003e Clara\n\u003e\u003e\u003e\n\u003e\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20221123/4dfcbdf3/attachment.html\u003e"}