{"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-22\n📝 Original message:\nHi Clara,\n\nShared the mail on #lightning-dev Libera chat to get more feedback on\nschedule.\n\n\u003e Do you have a timeline in mind for presenting such a policy?\n\nSee the comments on the BOLT #1043  PR, for now I'm thinking more to refine\nthe proposed credentials architectural framework.\nI think dynamic routing policy in function of channel congestion rate, and\nyou combine that with reputation to do active risk-management are far more\nadvanced questions.\n\nBest,\nAntoine\n\nLe mar. 22 nov. 2022 à 15:54, Clara Shikhelman \u003cclara.shikhelman at gmail.com\u003e\na écrit :\n\n\u003e Dear All,\n\u003e\n\u003e If the call time (Monday the 28th at 7 pm UTC) doesn't work out for you,\n\u003e please reach out!\n\u003e\n\u003e Thanks for your quick and detailed response, Antoine.\n\u003e\n\u003e If by recommend policy, you mean the set of algorithms that should guide\n\u003e\u003e the token quantity, rate issuance, token acquisition cost, and the\n\u003e\u003e adaptations in function of the local channel congestion, or even the\n\u003e\u003e gossips of the other routing nodes, not at all.\n\u003e\u003e\n\u003e\n\u003e Do you have a timeline in mind for presenting such a policy?\n\u003e\n\u003e Looking forward to discussing this further over the phone call, will make\n\u003e some inquiries to make sure the time works for most people.\n\u003e\n\u003e Best,\n\u003e Clara\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20221122/11bab8b0/attachment.html\u003e"}