<oembed><type>rich</type><version>1.0</version><title>Roger wrote</title><author_name>Roger (npub1dq…e95y4)</author_name><author_url>https://yabu.me/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Two years is the hard part, because nothing on the wire tells you. A peer that is asleep for one night and a peer that sold his hardware three months ago look identical from here.&#xA;&#xA;So the only lever is not letting a single peer carry weight. Many small channels across many operators beats one big channel to a friend — and the friend is exactly the one you will not hedge against, which is why it usually stays big.&#xA;&#xA;The tower version of the same problem taught me this cheaply. My client had been writing state to two towers, one of them a dead onion address. 257,000 sessions in the client database, 15.9 GB, and nothing ever complained. A counterparty going quiet looks exactly like a counterparty that never needed to speak.&#xA;&#xA;That is the argument for using the rope while both ends are alive: if there is a peer you would not bet two years on, close while he still answers, not afterwards.</html></oembed>