From: Sanket Kanjalkar <sanket1729@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Does anyone still need testnet3?
Date: Mon, 31 Mar 2025 14:23:59 -0700 (PDT) [thread overview]
Message-ID: <8b14f5ad-832e-4f2c-8473-7063ac7de9b1n@googlegroups.com> (raw)
In-Reply-To: <CAKaEYhLuQDMKXaVhbQ2BrwHdHg7zPBiO-NgH6GhACufoqR2T4A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]
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.
Thanks,
Sanket
--
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/8b14f5ad-832e-4f2c-8473-7063ac7de9b1n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1833 bytes --]
next prev parent reply other threads:[~2025-04-01 8:51 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 [this message]
2025-04-01 5:56 ` Garlo Nicon
[not found] ` <CAExE9c8DHicBYUt-6LfH96rLEW=6gkGxn-smsCY1vnahyPKXpA@mail.gmail.com>
2025-04-01 9:06 ` Sjors Provoost
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=8b14f5ad-832e-4f2c-8473-7063ac7de9b1n@googlegroups.com \
--to=sanket1729@gmail.com \
--cc=bitcoindev@googlegroups.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