public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jonathan Underwood <junderwood@bitcoinbank.co.jp>
To: Karl-Johan Alm via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is Signet Bitcoin?
Date: Tue, 15 Oct 2019 13:38:29 +0900	[thread overview]
Message-ID: <CAMpN3mJ67BpGk-WGJLMcaOEfcLPQrrjEnygqQHmR8xfS5fQC=A@mail.gmail.com> (raw)
In-Reply-To: <CALJw2w5h3jjKAtvzwup=wbGWU7Yf=byuJzzvJm16CMXQAoTmtg@mail.gmail.com>

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

I would also like to agree that Signet should be a BIP.

Problem: Testnet is unreliable. *Testnet is used often for development of
Bitcoin*.
Proposal: To improve the dev environment for Bitcoin, let's create a new
kind of testnet that is more reliable.

I would also like to hear the logic behind "Testnet is Bitcoin" but "Signet
is not Bitcoin"... both are not 100% compatible with mainnet consensus
processes.

-Jon

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

  reply	other threads:[~2019-10-15  4:38 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 [this message]
2019-10-15  5:33 ` Matt Corallo

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='CAMpN3mJ67BpGk-WGJLMcaOEfcLPQrrjEnygqQHmR8xfS5fQC=A@mail.gmail.com' \
    --to=junderwood@bitcoinbank.co.jp \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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