[Bitcoin-segwit2x] Orderly Process for Coin-Splitting after the fork

Hugh Madden hugh at anxintl.com
Wed Oct 25 19:41:35 UTC 2017

If I understand correctly, using s2x's opt in replay protection is the only
option that will work safe without needing ongoing splitting for every utxo.

With ETH/ETH account based blockchain you could just do something to
invalidate the nonce and job done.

With 1X / 2X I think you need to split every single uxto.

Easier I think to just use the opt-in replay protection.

The helps with the sends side of the equation.

The bigger issue is deposits and extended period chain reorgs due to flip
flopping of hash rate over the two chains.

I don't have any solution for this except an extended outage. Any thoughts
on how many blocks are required to be safe from extended period chain
reorgs ?

On 25 Oct. 2017 11:08 am, "Christophe Biocca via Bitcoin-segwit2x" <
bitcoin-segwit2x at lists.linuxfoundation.org> wrote:

> I'll also mention for completeness that the big-block bounty transaction (
> http://www.blockbounties.info/) has many anyone-can spend outputs which
> are meant to be used to enable anyone else to add funds to the bounty, but
> also effectively can be used for splitting funds.
> This is similar to the coinbase-tx approach, but can happen essentially
> immediately post fork (no need to wait 100 blocks).
> The downside is that the originator of the transaction could invalidate it
> before the fork happens, so it's not 100% guaranteed to work.
> On 25 October 2017 at 04:24, Tomas via Bitcoin-segwit2x <
> bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
>> On Tue, Oct 24, 2017, at 22:41, Moe Adham via Bitcoin-segwit2x wrote:
>> Coinbase: Have miners agree to send a small amount of newly generated
>> coins to wallet operators as quickly as possible after the fork, to allow
>> wallet operators to split wallets
>> I don't think miners actually need to send these coins to wallet
>> operators.
>> A miner or someone else who has acquired some newly minted coins can
>> create transactions with one input and one output that pay to self with
>> SIGHASH_SINGLE | SIGHASH_ANYONECANPAY and provide these replay protected
>> transaction "templates" in large numbers over an API for everyone to use.
>> Tomas
>> bitcrust
>> _______________________________________________
>> Bitcoin-segwit2x mailing list
>> Bitcoin-segwit2x at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
> _______________________________________________
> Bitcoin-segwit2x mailing list
> Bitcoin-segwit2x at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/attachments/20171026/88f735d9/attachment.html>

More information about the Bitcoin-segwit2x mailing list