Quote from: franky1 on July 15, 2018, 10:40:45 AM

Quote from: Wind_FURY on July 13, 2018, 06:36:45 AM

Quote from: franky1 on July 09, 2018, 06:22:03 PM

i actually bothered to read the bitcoin cash codebase.. and actually. if you read the code. the 32mb is known as a consensus limit.. but they also have a "regulated" limit of 2mb called the policy limit
https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/src/policy/policy.h#L19

this is the same as what bitcoin core had before 2013.. 1mb consensus limit but 0.5mb "regulated limit" (in policy.h)which then went up to 0.75mb
and then in around 2015 went up to 1mb.. all without needing to fork or have big discussions because the policy was a flexcap limit

check it out consensus.h vs policy..h

I want to get back to this, and I am embrassed to say that I am not sure how that works. Who decides when to increase the "flex cap" limit? Is it the miners only, or does it have to be in consensus with the non-mining full nodes?

at current coding. core and cash accepts anything below consensus.h limit.. and then core freely allows the mining pool to make the blocks bigger than policy which will still be acceptable to core as long as the new blocksize stays under consensus (meaning to non-mining nodes) policy is meaningless to core users as its something pools decide solely by themselves

Maybe I misunderstood but how would it be "meaningless" if it is enforced to stay under a limit even if pools can decide but only if up to that limit?

Quote

however take bitcoin unlimiteds proposal a few years back (core rejected it) where by the policy.h becomes somthing non-mining nodes vote on by having s a value in their node identity and then mining pools only move forward making bigger blocks if a high percentage of nodes wave a flag to say its ok to do so.. they said it was a bad voting mechanism

kind of funny that devs that said no to it.. becasue it was them same devs that actually then went on to beg users to put "nosegwitx2" or "yesUASF" in their identifier to see how many people wanted the core roadmap. they even promoted people put it into thier twitter usernames and other non-code social stuff such as 'buy a UASF hat and take a picture on social media and get people to share it'.. (facepalm)

Yes it is very bad because it would be open to Sybil attacks. It would be easy for some group of people to set up and run nodes in Alibaba cloud service.

Quote

devs love their social drama campaigns but try to avoid code voting (avoided consensus upgrade and done the 3shell trick of a MANDATORY bilateral split) which they thought was OK because all the social media and social identifiers said it was ok (facepalm)

The Core developers should not be pressured by fraudsters like Roger Ver, Craig Wright, or the mining cartels. Do you agree or disagree?