public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Hector Chu <hectorchu@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Block size hard fork
Date: Sat, 1 Aug 2015 01:05:43 +0100	[thread overview]
Message-ID: <CAAO2FKFQjjftgEgZoDAUrMxa86KTbNzAqg+xgExTRPpGxedwRw@mail.gmail.com> (raw)

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

I haven't seen much discussion on this list of what will happen when the
blockchain forks due to larger blocks. I think the debate surrounding this
issue is a storm in a teacup, because transactions on the smaller chain can
and will appear on the bigger chain also. There is nothing tying
transactions to the blocks they appear in.

Miners will migrate to the bigger chain in search of higher profits due to
higher volume of fees. They can also collect the higher fees of the smaller
chain by including into the bigger chain as many as possible of the
transactions from the smaller chain.

To stop this from happening the smaller chain would somehow need to change
the serialized format of their transactions so the signatures would no
longer be valid across chains.

Incidentally I read somewhere that the losing chain would have their coins
sold down. Trying to sell the smaller chain's coins in the short term at
least is not advisable, as those transactions will appear on the bigger
chain too.

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

             reply	other threads:[~2015-08-01  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01  0:05 Hector Chu [this message]
2015-08-01  0:17 ` Gregory Maxwell
2015-08-01  8:43   ` Hector Chu

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=CAAO2FKFQjjftgEgZoDAUrMxa86KTbNzAqg+xgExTRPpGxedwRw@mail.gmail.com \
    --to=hectorchu@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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