And they can't just do
NetworkParams.TESTNET = NetworkParams.REGTEST
at the start of a program that is connecting to regtest?
It's not like changing the address code is a huge problem or anything, but
it would disrupt a bunch of people and seems kind of annoying. Surely
there's a simpler way t
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
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. wrote:
> Hi folks,
>
> I propose changing all of the address versions in -regt
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 n
4 matches
Mail list logo
