It’s been well over a day since the Bitcoin Cash (BCH) network upgraded its protocol, and the consensus rules now come with a 32MB block size. Although the block size increase is quite a feat, BCH developers have also expanded the network’s default data-carrier-size to 220 Bytes and re-enabled some old Satoshi OP_Codes that were previously removed from earlier codebases.

Now over the past 24-hours, lots of people have been playing around with the new BCH features. Also Read: Bitcoin Cash Upgrade Milestone Complete: 32MB and New Features Lots of BCH community members have been discussing the new OP_Code features and the additional space added to the network’s default data-carrier-size.

The first signs of people messing around with the new features came from the Memo and Blockpress developers as both platform’s increased posting character limit from 79 to 217. This means users of both social media applications can now post more content and everything is saved on-chain.

Then shortly after the fork, another OP_Code feature was shown to the community by Openbazaar developer Chris Pacia. Pacia built the first tree signature on the Bitcoin Cash blockchain by utilizing the OP_CAT functionality — which creates a more efficient multi-signature combination.

The Openbazaar programmer explains for addresses with a large number of keys, a tree signature can use less data. “For addresses with a large number of keys a tree signature can use less data. Read more from…

thumbnail courtesy of