sorry im noob in bitcoin system, blocksize, mining ,network etc.
just want to ask :
bitcoin unlimited is new nodes ? like bitcoin classic,core etc. ?
if 70% of miner using this nodes/config, any effect at bitcoin transaction ?
BU has a flex cap (like what core agreed to have in 2015 before they later backtracted)
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.htmlFurther out, there are several proposals related to flex caps or
incentive-aligned dynamic block size controls based on allowing miners
to produce larger blocks at some cost. These proposals help preserve
the alignment of incentives between miners and general node operators,
and prevent defection between the miners from undermining the fee
market behavior that will eventually fund security. I think that right
now capacity is high enough and the needed capacity is low enough that
we don't immediately need these proposals, but they will be critically
important long term. I'm planning to help out and drive towards a more
concrete direction out of these proposals in the following months.
BU has been running for months now and can happily still run if the consensus moved to more then 'under 1mb' because the rule is simple.
anything under Xmb is acceptable.
no one is saying the rules of the network should ever be 'blocks should be more than X'
but instead move the buffer limit to say
anything under X is acceptable.
core say anything under 1mb is acceptable
classic say anything under 2mb is acceptable
BU say anything below 16mb is acceptable, and locally(user adjustable) stick to a under 1mb flexcap right now
and then let miners choose whats safe to create and relay out without large orphan risk.
miners right now produce blocks between 200bytes-995kb which has only a 1% acceptable loss orphan risk
scenario one:(only core is holding back, with only informal half-promises of flexcaps, with no eta)if core devs release a below 2mb update, core users have to review what they are downloading and try it
classic do nothing more
BU do nothing more. BU user changes setting locally
and then the 95% consensus of below 2mb can be seen.
when all is happy and when mining pools see safe majority(95-100%) of nodes are happy with 'below 2mb', the mining pools then flag their own desire. and when there is 95%+ of mining pool acceptance, the pools make a block 1.0000000250mb (1mb plus alittle) to see the orphan risk.
if there is an unforseen issue. then mining pools go back to making 995kb blocks until solution is found.
if the orphans are low, they continue with this small amount extra until they are happy nodes are not crashing out and block are not orphaning to any extent. and slowly build up over time as the network gains confidence.
much like what happened in 2013 after nodes could fully utilise the 1mb rule after the 500k limit bug was found. they didnt suddenly jump straight to 1mb blocks. it build up slowly over 3 years
scenario two:if there is no 95% consensus of an possible block growth proposed compromise amount. then everything carries on as is until there is a consensus that allows mining pools to try out the new consensus
