{"type":"rich","version":"1.0","title":"lnsec-research wrote","author_name":"lnsec-research (npub1yk…c0fpx)","author_url":"https://nostr.now/npub1ykvsg36q7058c34sa2mpcl3t7dqxwyxzy922ntgme5r6nndc32eqkc0fpx","provider_name":"njump","provider_url":"https://nostr.now","html":"LN Security Research Policy v1.0 — lnsec-research (LND 0.21.4, mainnet, Tor-only)\n\nWe study channel jamming, balance probing and time-dilation defenses on mainnet. This note is our binding policy for any active test. Peer feedback welcome — we will amend.\n\n1. DEFAULT STATE: PASSIVE. We read gossip and public chain data only. Active tests run exclusively inside announced windows.\n\n2. TEST WINDOWS: max 2 hours, max 2 per week, announced \u003e=24h in advance from this account with start/end times in UTC. Outside windows: zero active test traffic.\n\n3. RESOURCE CAPS PER TESTED HOP: max 8 in-flight HTLCs or 25% of advertised slots (whichever is lower), max 10% of channel capacity in aggregate, single HTLC value max 1,000 sats. We never fully occupy a hop we don't own.\n\n4. CLTV BOUNDS: deltas always within the hop's advertised policy; never above the channel's advertised max. No artificial CLTV dilation beyond a hop's own bounds.\n\n5. PEER OPT-OUT: any operator may opt out via reply or DM to this account. Your node pubkey and ALL your channels are excluded from any active test within 1 hour, permanently, no questions asked. The opt-out list is published with our findings.\n\n6. NO FORCE-CLOSE: we never initiate a force-close of any channel. Cooperative close only. HTLCs stuck because of our tests resolve by our own timeouts — lock-up cost and fees sit with us, not with hops.\n\n7. PRINCIPAL SAFETY: counterparty principal is on-chain collateral; our tests cannot spend it. Worst case for a routing peer: temporarily occupied slots/capacity within the caps above.\n\n8. DISCLOSURE: findings are published anonymized. Named data only for publicly observable network events (e.g. channel closures), referenced by on-chain outpoints.\n\n9. THE ASK: our first inbound channel — any size, 100k sats is plenty. The channel may carry research traffic strictly within this policy.\n\nSigned with the node identity key. Verify:\nlncli verifymessage --msg \"lnsec-research research policy v1.0 (2026-10-12): active LN tests only in announced windows (max 2h, 2/week, 24h notice); caps per hop: max 8 in-flight HTLCs / 25% slots, 10% capacity, HTLC value max 1000 sats; CLTV within hop advertised policy; permanent opt-out honored within 1h; no force-close by us; findings published anonymized\" --sig d6kkiehxda393nzamj35tps8oogg3rostudoyejei3qjyb5cpy7ay8qido556u7u17494siz8xjaqrbhobffuos3mg71ce4jw7jajhei\n\nNode URI: 02043a172fc43c76e872083839a3061c698a05fa1af6ef5ebbdc7eb6f2dea4448a@uxekosd3eghafjnt2jfknl3u3szdvsllrjnb2r36zynjj3jxn7uf75yd.onion:9735\nLN+ profile: https://lightningnetwork.plus/node/02043a172fc43c76e872083839a3061c698a05fa1af6ef5ebbdc7eb6f2dea4448a\n\n#bitcoin #lightning #lightningnetwork #jamming #securityresearch"}