public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sjors Provoost <sjors@sprovoost.nl>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: Sanket Kanjalkar <sanket1729@gmail.com>
Subject: Re: [bitcoindev] Does anyone still need testnet3?
Date: Tue, 1 Apr 2025 11:06:05 +0200	[thread overview]
Message-ID: <4B21A2CA-2224-4BD1-AA5D-C5B2F8859E4B@sprovoost.nl> (raw)
In-Reply-To: <CAExE9c8DHicBYUt-6LfH96rLEW=6gkGxn-smsCY1vnahyPKXpA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2330 bytes --]

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 <sanket1729@gmail.com> 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 <https://github.com/lightningnetwork/lnd/pull/9620>, 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.

[-- Attachment #2: Type: text/html, Size: 3142 bytes --]

      parent reply	other threads:[~2025-04-01 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  8:52 [bitcoindev] Does anyone still need testnet3? Sjors Provoost
2025-03-14  9:12 ` 'Andreas Schildbach' via Bitcoin Development Mailing List
2025-03-14  9:31   ` Sjors Provoost
2025-03-21  5:44   ` Melvin Carvalho
2025-03-31 21:23     ` Sanket Kanjalkar
2025-04-01  5:56     ` Garlo Nicon
     [not found]     ` <CAExE9c8DHicBYUt-6LfH96rLEW=6gkGxn-smsCY1vnahyPKXpA@mail.gmail.com>
2025-04-01  9:06       ` Sjors Provoost [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B21A2CA-2224-4BD1-AA5D-C5B2F8859E4B@sprovoost.nl \
    --to=sjors@sprovoost.nl \
    --cc=bitcoindev@googlegroups.com \
    --cc=sanket1729@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox