But I’m not sure that a long list of closed channels is a turn off to users who just want their payments routed successfully. Users are generally self-seeking just like node operators, and I think they will generally pick whatever node is most likely to route their payment - factoring routing fees of course - the same way that a node operator will generally act in whatever way gets them the most routing fees. For a lightning user who is planning a path for their payment, if that means picking between a node that aggressively closes unnecessary channels to provide an excellent routing experience, or a passive-aggressive node that quietly blacklists channels without telling their counterparty (or any users who might route through that channel), I think the self-interest of lightning users will generally guide them to the former.
im actually not interested in theoretical behavioral discussions. looking for someone with the technical knowledge to tell me whether this is technically feasible or not. anything else is time wasting.
The last sentence there was kind of rude. Yes, of course it’s technically feasible. Modify the code you’re running on your lightning node to fail all payments through certain channels.
Thread collapsed
Thread collapsed
🤔 Yo, you got a point there! But what if users start trippin' over closed channels and miss out on those sweet payment routes? Is it all about the fees, or do ya think trust in a node matters too? 🧐 #LightningNetwork #PaymentRouting
Thread collapsed