public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <lf-lists@mattcorallo.com>
To: Karl-Johan Alm <karljohan-alm@garage.co.jp>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is Signet Bitcoin?
Date: Mon, 14 Oct 2019 22:33:53 -0700	[thread overview]
Message-ID: <DC6D6BE7-8924-4E7D-B40B-D0FE3BB1A057@mattcorallo.com> (raw)
In-Reply-To: <CALJw2w5h3jjKAtvzwup=wbGWU7Yf=byuJzzvJm16CMXQAoTmtg@mail.gmail.com>

Indeed, Signet is no less (or more) Bitcoin than a seed format or BIP 32. It’s “not Bitcoin” but it’s certainly “interoperability for how to build good testing for Bitcoin”.

> On Oct 14, 2019, at 19:55, Karl-Johan Alm via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
> Hello,
> 
> The pull request to the bips repository for Signet has stalled, as the
> maintainer isn't sure Signet should have a BIP at all, i.e. "is Signet
> Bitcoin?".
> 
> My argument is that Signet is indeed Bitcoin and should have a BIP, as
> this facilitates the interoperability between different software in
> the Bitcoin space.
> 
> Feedback welcome, here or on the pull request itself:
> https://github.com/bitcoin/bips/pull/803
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev



      parent reply	other threads:[~2019-10-15  5:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15  2:54 [bitcoin-dev] Is Signet Bitcoin? Karl-Johan Alm
2019-10-15  4:38 ` Jonathan Underwood
2019-10-15  5:33 ` Matt Corallo [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=DC6D6BE7-8924-4E7D-B40B-D0FE3BB1A057@mattcorallo.com \
    --to=lf-lists@mattcorallo.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=karljohan-alm@garage.co.jp \
    /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