[Bitcoin-ml] Proposed address format for bitcoin cash

[Lin Zheming]

Why not pushing those wallet services to provide Bitcoin Cash support on the original address format? If they don't, people will not use them.
I see no more efforts in providing this kind of support than adapting a new address format.

We have two-way replay protection right?

Regards,

Lin Zheming

> 在 2017年11月8日，上午7:43，Antony Zegers via bitcoin-ml <bitcoin-ml at lists.linuxfoundation.org> 写道：
> 
> I propose we change the testnet and regtest prefixes in the Cash
> Address specification from "xbctest" and "xbcreg" to "bchtest" and
> "bchreg" respectively.
> 
> I created a pull request to update the spec with this change at:
> https://github.com/Bitcoin-UAHF/spec/pull/31
> 
> It seems that the majority of the ecosystem is converging to "BCH" as
> the symbol for Bitcoin Cash, so I think it makes the most sense to go
> along with this. "XBC" is not generally associated with Bitcoin Cash,
> and conflicts with "Bitcoin Plus".
> 
> Antony
> (aka Mengerian)
> 
> On Fri, Oct 13, 2017 at 12:39 PM, Amaury Séchet via bitcoin-ml
> <bitcoin-ml at lists.linuxfoundation.org> wrote:
>> Hi all,
>> 
>> Numerous people have been asking for a change of address format for Bitcoin
>> Cash and justifiably so. Errors are made while transferring BTC instead of
>> BCC and vice versa and it is taking support resources for whoever wants to
>> supports BCC.
>> 
>> One of the proposed solution was to change the address prefix, but I don't
>> think this is a good solution. It is expensive to change the address format,
>> and there are several problems with the current one, starting by the fact
>> that it isn't extensible, which will force another address format change
>> down the road. This is bad and we'd like to avoid this.
>> 
>> I'd like to put out there a proposal for the new address format:
>> 
>> https://github.com/Bitcoin-UAHF/spec/pull/21
>> 
>> Implementation work has already started. I think you'll find this format
>> supperior to the current one in several ways including:
>> - Better error detection.
>> - More efficient encoding in QR codes.
>> - Easy to compute.
>> - Extensible so we don't need to change it for future developments.
>> - Different from BTC's so no more confusion there.
>> 
>> If the community find this format satisfactory, we should sync with wallets
>> and services to ensure it is implemented soon.
>> 
>> Thanks,
>> 
>> Amaury Séchet
>> 
>> 
>> _______________________________________________
>> bitcoin-ml mailing list
>> bitcoin-ml at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>> 
> _______________________________________________
> bitcoin-ml mailing list
> bitcoin-ml at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20171108/cba28371/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20171108/cba28371/attachment.sig>