From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: 0x0ff <0x0ff@onsats•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] CTV Signet Parameters
Date: Mon, 21 Feb 2022 19:19:23 -0800 [thread overview]
Message-ID: <CAD5xwhj7m=rspdPT-wvFp68XMP9rwp+7Rva5njKAOS+Hc0SGnA@mail.gmail.com> (raw)
In-Reply-To: <JZVz-IgaaNyb9jjetlc0S5heZg9RhMsGl2ixRTIk5-Y1yITvf_Q3QFaLJmtRUR0ugxA9gfuu6NosUPfuQm5BfbPoDyyQhAOYzmfvaHYwbmk=@onsats.org>
[-- Attachment #1: Type: text/plain, Size: 2457 bytes --]
There's also now a faucet:
https://faucet.ctvsignet.com
thanks 0x0ff!
--
@JeremyRubin <https://twitter.com/JeremyRubin>
On Fri, Feb 18, 2022 at 3:13 AM 0x0ff <0x0ff@onsats•org> wrote:
> Good day,
>
> I've setup the explorer for CTV Signet which is now up and running at
> https://explorer.ctvsignet.com
>
> Best,
> @0x0ff <https://twitter.com/0x0ff_>
>
> ------- Original Message -------
> On Thursday, February 17th, 2022 at 9:58 PM, Jeremy Rubin via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Hi devs,
>
> I have been running a CTV signet for around a year and it's seen little
> use. Early on I had some issues syncing new nodes, but I have verified
> syncability to this signet using
> https://github.com/JeremyRubin/bitcoin/tree/checktemplateverify-signet-23.0-alpha.
> Please use this signet!
>
> ```
> [signet]
>
> signetchallenge=512102946e8ba8eca597194e7ed90377d9bbebc5d17a9609ab3e35e706612ee882759351ae
> addnode=50.18.75.225
> ```
>
> This should be operational. Let me know if there are any issues you
> experience (likely with signet itself, but CTV too).
>
> Feel free to also email me an address and I can send you some signet coins
> -- if anyone is interested in running an automatic faucet I would love help
> with that and will send you a lot of coins.
>
> AJ Wrote (in another thread):
>
> > I'd much rather see some real
> > third-party experimentation *somewhere* public first, and Jeremy's CTV
> > signet being completely empty seems like a bad sign to me. Maybe that
> > means we should tentatively merge the feature and deploy it on the
> > default global signet though? Not really sure how best to get more
> > real world testing; but "deploy first, test later" doesn't sit right.
>
> I agree that real experimentation would be great, and think that merging
> the code (w/o activation) for signet would likely help users v.s. custom
> builds/parameters.
>
> I am unsure that "learning in public" is required -- personally I do
> experiments on regtest regularly and on mainnet (using emulators) more
> occasionally. I think some of the difficulty is that for setting up signet
> stuff you need to wait e.g. 10 minutes for blocks and stuff, source faucet
> coins, etc. V.s. regtest you can make tests that run automatically. Maybe
> seeing more regtest RPC test samples for regtests would be a sufficient
> in-between?
>
>
> Best,
>
> Jeremy
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>
>
>
>
[-- Attachment #2: Type: text/html, Size: 8531 bytes --]
next prev parent reply other threads:[~2022-02-22 3:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:58 Jeremy Rubin
2022-02-18 11:13 ` 0x0ff
2022-02-22 3:19 ` Jeremy Rubin [this message]
2022-04-20 2:31 ` Anthony Towns
2022-04-20 17:05 ` Nadav Ivgi
2022-04-21 2:36 ` Anthony Towns
2022-04-28 12:23 ` Jeremy Rubin
2022-04-20 17:13 Buck O Perley
2022-04-21 5:03 ` Anthony Towns
2022-04-21 6:16 ` Jeremy Rubin
2022-04-21 6:25 ` Jeremy Rubin
2022-04-21 13:22 ` Russell O'Connor
2022-04-21 15:05 ` Jeremy Rubin
2022-04-22 0:58 ` Anthony Towns
2022-04-22 1:10 ` Nadav Ivgi
2022-04-22 5:30 ` Jeremy Rubin
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='CAD5xwhj7m=rspdPT-wvFp68XMP9rwp+7Rva5njKAOS+Hc0SGnA@mail.gmail.com' \
--to=jeremy.l.rubin@gmail$(echo .)com \
--cc=0x0ff@onsats$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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