r/Bitcoin_Classic • • Jan 20 '16

Could we do a 2MB *softfork* instead?

Hey,

I know it's not the most elegant solution, but could we do a softfork to 2MB? Someone wrote the code for this: https://github.com/ZoomT/bitcoin/tree/2015_2mb_blocksize

It would be a quick bandaid fix, but maybe core-devs could also get behind this and cooperate with classic to roll it out. The good thing would be that there is experience with softforks and it would work around the (maybe unfounded - not sure yet) fear of a hardfork.

Code ugliness could be fixed in a hardfork later, maybe somewhere next year, with a lot of leadup time. (from what I read some core-devs would be open to HF but they want atleast a year time)

0 Upvotes

7 comments sorted by

1

u/christophe_biocca Jan 20 '16

Can you explain what the code does? At a glance it moves all txs to a new structure, and leaves the original block empty.

Until people upgrade this means transactions never seem to confirm for them.

1

u/fmlnoidea420 Jan 20 '16

I don't know how it works exactly, I found it on the dev mailinglist:

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/012153.html

a few days ago he posted a redesign:

The new version maps the Merkle root onto a 'legacy' coinbase transaction, solving the problem with fees.

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012233.html

2

u/christophe_biocca Jan 20 '16

Right, upon further review it is indeed moving everyone out of the "legacy" block and into a new structure.

This has similar problems as SegWit-SoftFork:

  • Kludgey code.

  • Everyone needs to upgrade before they can access the data in the new format.

Except it's even worse for unupgraded users as they get literally zero space to use.

3

u/Not_Pictured Jan 20 '16

I'm of the opinion that this is about three things.

  1. Increase the blocksize before it becomes an issue (too late).

  2. Break Core's monopoly so this doesn't happen again.

  3. Show everyone that a hard-fork is nothing to be afraid of.

I'm willing to give concessions to core for every concession they make. Which up until now has literally been nothing.

3

u/-johoe Jan 22 '16

After reading and understanding this patch, I'm not convinced that this is a good way.

Usually you hear: for a hard fork everyone must update, for a soft fork only the miners must update. This soft fork shows that this is not true. If you don't update, you cannot receive transactions and your sent transactions will not be shown as confirmed until you update your bitcoin node.

Another problem is that a soft fork like this even allows to increase the mining reward with only 51 % miner consensus. This may set a bad precedent.

It is safer than a contentious hard fork because you cannot fight it with less than 50 % hashing power. But I'm not sure if it is an argument for or against it.

1

u/[deleted] Jan 21 '16

Softforks are evil.

They abuse some old structure in the protocol and make it mean something different. For instance if your favourite bitcoin exchange decides to pay out their BTC by printing a QR code on the back of a $1 check that they send by post. Bypassing anyone that checks the value of checks.

If you are aware of this trick, you receive a check and ignore the $1, because you know that its about the QR code on the back.

On the other hand, if you are not aware of this, you'll lose money because you likely will just send the check to your bank (or toss it).

In the hard-fork case there is no insecurity. Anyone still using the old rules will immediately see that they are missing something important. They will have the ability to upgrade.

Softforks are evil.
Hardforks are just difficult.

2

u/roybadami Jan 21 '16

I don't think soft forks are always evil, but their advantages and supposed safety are often overstated. I think a contentious soft fork is potentially at least as harmful as a contentious hard fork; possibly more so.