Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 9C388C0011 for ; Tue, 22 Feb 2022 03:19:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 78DBF404F4 for ; Tue, 22 Feb 2022 03:19:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRVZwJx6bkAK for ; Tue, 22 Feb 2022 03:19:37 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by smtp2.osuosl.org (Postfix) with ESMTPS id F36664049E for ; Tue, 22 Feb 2022 03:19:36 +0000 (UTC) Received: by mail-lf1-x130.google.com with SMTP id e5so22117035lfr.9 for ; Mon, 21 Feb 2022 19:19:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tDE8DtZ/w4vXxlSb668W/IxLRfZ58LuwYXgI5sPocng=; b=KP/GDsuP2dmnHuyQODYWrGyosNXC5hM5uDS3mKZdiXtGrMqAWn2H0K9f9nnFZc2moz lNNJYGu+vGuR+RYU6BXvwy1ZuWUiPXpRMDxX/wlnNlMKBXT4dzzySfwoUSwaahJoOoWM bIrHfqQx6HBJtw+SGyVLVzLbMTv8TLAeNnQXNsD8rBS56f2tASzh+m+x32noRyJd167P QprPLzoxdoOwuZS6o+I5P/cmbkGAfTH/AUiEBpUDAQphLsMIpfwNpz6nc0Zvviqvp46g 2dYTI48f65UCvpifaPC4m32f1tZ0crW5CpqDa4IX9eAzQHtDOXvY2xJ/p6mRIK4qMDMn J1Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tDE8DtZ/w4vXxlSb668W/IxLRfZ58LuwYXgI5sPocng=; b=hVq669QA1QBotdSZeLh8Ki6c68DWnL7FetSIK/TE66slNt5GmBXeGXoiEiF0zu4e4e +LIXs4FKTp+6F+g3lflUWcpaRAsGrTxylPvFJMhNwZcO8XRlJR9MbyNhk6xx+odlzjB3 7upeN7GC2jVKj9uawNnyid6xv0FVpgcL8Y8flAUyClTce9gOGnIdrAORCFrKRmUo+hJh lHp+QDpWMvh4de8QhyRiN/NGvtNnNYGNTrdJnk15XRmXGrAhFoMyoTD/eVmI5YJL9vSs sEkFFXvfWpilaLrbi3ZIs/ZQZFoid67+ehGTpvlRP4YSHlJKFzNGSNi8x/3Lczehk8lC a88g== X-Gm-Message-State: AOAM5324BVQ/KpjCrDWBv7/Bh0lxE/TLZm4Gms4E+FsI8yChdYyRdoir a10lO6E3a8+sEG5pkonDOwO+4V0zdKDCEqYBYX/3n5LkrWmCvA== X-Google-Smtp-Source: ABdhPJximsInsV3B3j5LBnidKzqmH4vQbuYHSqnLtcG5p0R4xAmvP9GxU01+jz3bbBsnP04zc5W22wvKvH9iCFToQgQ= X-Received: by 2002:a05:6512:1288:b0:443:f15d:6a2e with SMTP id u8-20020a056512128800b00443f15d6a2emr4289991lfs.363.1645499974648; Mon, 21 Feb 2022 19:19:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jeremy Rubin Date: Mon, 21 Feb 2022 19:19:23 -0800 Message-ID: To: 0x0ff <0x0ff@onsats.org> Content-Type: multipart/alternative; boundary="00000000000077886f05d892d1dd" Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] CTV Signet Parameters X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2022 03:19:38 -0000 --00000000000077886f05d892d1dd Content-Type: text/plain; charset="UTF-8" There's also now a faucet: https://faucet.ctvsignet.com thanks 0x0ff! -- @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 > > ------- 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 > > > --00000000000077886f05d892d1dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There's also now a fa= ucet:

https://faucet.ctvsign= et.com

thanks 0x0ff!
--
@JeremyRubin


On Fri, Feb 18, 2022 at 3:13 AM 0x0ff <0x0ff@onsats.org> wrote:
Good day,
<= /div>

I've setup the explorer f= or CTV Signet which is now up and running at=C2=A0https://explorer.ctvsignet.com

Best,

------- Original Message -------
On Thursday, February 17th, 2022 at 9:58 PM, Jeremy Rubin via bitco= in-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 v= erified syncability to this signet using https://github.com/JeremyRubin/bitc= oin/tree/checktemplateverify-signet-23.0-alpha. Please use this signet!=

```
[signet]
signetchal= lenge=3D512102946e8ba8eca597194e7ed90377d9bbebc5d17a9609ab3e35e706612ee8827= 59351ae
addnode=3D50.18.75.225
```

This should be operational.= Let me know if there are any issues you experience (likely with signet its= elf, but CTV too).

<= div style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:r= gb(0,0,0)" class=3D"gmail_default">Feel free to also email me an address an= d 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 co= ins.

AJ Wrote (in another thread):

> I'd = much rather see some real
= > third-party experimentation *somewhere* public first, and Jer= emy'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
&= gt; default global signet though? Not really sure how best to get= more
> real world test= ing; but "deploy first, test later" doesn't sit right.
I agree that real experime= ntation would be great, and think that merging the code (w/o activation) fo= r 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

<= div>

--00000000000077886f05d892d1dd--