From: "Warren Togami Jr." <wtogami@gmail.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Regtest Address Version Change Proposal
Date: Tue, 13 May 2014 01:02:46 -1000 [thread overview]
Message-ID: <CAEz79PoNZ=B+BsmHkHykeh4TY3q_EVmksAJagzKTFuTAHL-1pA@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP1--8C0Tf=RF1Hi9sXq5wbUC1feBswkGMcwGxwgZ1UYKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
bitcore guesses the network from the address version in several places in
its code. They don't want to change that. Perhaps it wasn't the wisest
approach for them to use. I thought it might be simple to change the
address version since its still relatively new and it isn't a real network.
Would it be too much work to change?
On Tue, May 13, 2014 at 12:30 AM, Mike Hearn <mike@plan99.net> wrote:
> Yes, bitcoinj supports and uses regtest mode. It would also have to be
> changed.
>
> You didn't provide a rationale for this. What's the cost of having them be
> the same?
>
>
> On Tue, May 13, 2014 at 11:45 AM, Warren Togami Jr. <wtogami@gmail.com>wrote:
>
>> Hi folks,
>>
>> I propose changing all of the address versions in -regtest mode to be
>> unique so they are no longer identical to testnet.
>>
>> https://en.bitcoin.it/wiki/List_of_address_prefixes
>> For example, regtest pubkey hash addresses could begin with r or R.
>>
>> We need to know if any existing tools would need to be modified to
>> support this change to regtest. Do existing tools outside of pull tester
>> expect regtest to have testnet addresses? If the quantity of tools that
>> currently handle regtest is small then we can modify them to the new
>> address versions.
>>
>> Warren Togami
>>
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing platform
>> available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 3095 bytes --]
next prev parent reply other threads:[~2014-05-13 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 9:45 [Bitcoin-development] Regtest Address Version Change Proposal Warren Togami Jr.
2014-05-13 10:30 ` Mike Hearn
2014-05-13 11:02 ` Warren Togami Jr. [this message]
2014-05-13 11:28 ` Mike Hearn
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='CAEz79PoNZ=B+BsmHkHykeh4TY3q_EVmksAJagzKTFuTAHL-1pA@mail.gmail.com' \
--to=wtogami@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=mike@plan99.net \
/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