Hi Sanket, I've heard before from some lightning folks that migrating to testnet4 presents a chicken-egg problem. If we were to start rotating test networks a frequency of e.g. once every three years, this would become a recurring problem. Lightning seems to be a special case because it relies heavily on interoperability, and so any move has to be coordinated between multiple parties each with their own priorities. At the same time Lightning software often needs the latest and greatest Bitcoin Core version e.g. for its new policy features. So sticking to v29 back-ports isn't a long term viable option. I think it's worth considering for the lightning industry to organize a custom signet, either a 1-of-N with keys distributed among the current players, or unsigned proof-of-work based (more hassle, but future new players may feel more comfortable joining). Such a network can be kept online definitely and its replacement can be more easily coordinated. Another advantage is that soft fork proposals can be tested, similar to how Inquisition does that on the default signet, but at a pace that matches Bolt spec work. - Sjors > Op 31 mrt 2025, om 23:15 heeft Sanket Kanjalkar het volgende geschreven: > > Hi Sjors, > Thanks for asking. Block/Cashapp relies on testnet3 and can't migrate to testnet4 mostly because of lack of lightning LND peers. > I don't think there are any LND Lightning peers on testnet4. We (Block/Cashapp lightning) use LDK for Lightning, but most of our peers run LND. LND support for testnet4 was just merged , so it’ll likely take time for the LND community to update node infrastructure. > We want to catch peering, business logic and lightning implementations interoperability issues in testnet. Even though LDK supports testnet4, switching now isn’t viable for us until our mainnet LND peers migrate. > -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/4B21A2CA-2224-4BD1-AA5D-C5B2F8859E4B%40sprovoost.nl.