group-tokenization VS bitcoin-cash-node

I think BCH has potential to bring me way more than x2 x3 BTC can, which is why my BCH bags are bigger and I'm working hard on actually doing something to help move the needle. I expect the gains from BCH to be worth all my time and energy spent on this. BCH is also an instance of Bitcoin, the invention, one that may live up to the P2P potential, but as we have seen in 2017, that's not been enough to claim THE "Bitcoin" title, not as the invention, but a particular implementation of the invention that got the most market cap. Nothing is forever, and success of one doesn't preclude success of the other. If we grow big, the name won't matter. I like cash, and when I say cash I mean Bitcoin Cash :) Anyway, both blockchains are viable, they exist, they are used in one way or another, and compete with all the other blockchains to take the market cap.

I took over Andrew Stone's work and have been working on Group Tokens for about a year now, and then Jason joined in and now we're gonna push this together!

Thanks to everyone who's interacted with me since then I learned A LOT, and had my mind changed many times, in a good way, about what Group needs to be, not whether it's a good idea or not. I like to believe I did my part in opening people's eyes that it IS a great idea, one that will bring a lot of value to BCH, and through this process we've gotten really close to the idea's final shape! That's how the Group CHIP got to v6.0 and is now titled "Unforgeable Groups", because it's all about enabling something more abstract, generic blockchain "primitives" that can let builders create amazing things, at no additional cost to our network, and allow users easy access to those products through easy "P2PKH" tokens, those that can interact with contracts and be moved around as easy and cheap as BCH!

Hey man, thanks! I think we'll end up merging the 2 proposals, here's a first step in that direction: https://gitlab.com/0353F40E/group-tokenization/-/commit/bf37f2db09d0c2e0e0287d70d8741b1d495d2428

Unforgeable Groups CHIP scope

The latest "Group" proposal (v4.2) is more than just "tokenization". It got simpler and more powerful at the same time. It now enables generic BCH output groups that can be used to create persistent Script covenant contracts that can prove their genuineness. This is something that current contracts cannot do, even with the new Introspection opcodes. Group would make it possible because the groupID is a commitment to the whole genesis transaction, but this is not a post about that.

Will you soon shut up about BCH being shit against "superior chains" when I point you to the CHIPs such as Native Introspection Opcodes, Bigger Script Integers which allows better smart contract functionality coming in 2022, and PMv3 and Group Tokens which allow better token and transaction formats that are coming in 2023?

MAJOR UPDATE - 4.0 Unforgeable Groups for Bitcoin Cash

Here's the latest version of the CHIP: https://gitlab.com/0353F40E/group-tokenization/-/blob/6cc8488e145007f2c34b1a5e39368986430dcfdc/CHIP-2021-02_Group_Tokenization_for_Bitcoin_Cash.md

Thinking maybe this: https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node/-/tree/master

Yep, just a suggestion/comment in the config file here which showed me 'this was useful for me, let me share it' kind of vibes. I also checked their history there. Seem to be helping review things too (i have no idea about the back story here, just going on what I'm seeing before me)

They're already implemented and running on testnet4, using node software built from this MR: https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node/-/merge_requests/1600

Either build the test branch yourself (https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node/-/merge_requests/1600) or use Calin's build here (https://www.c3-soft.com/downloads/BitcoinCash/testing/mr-1600)

At first I was disappointed by the results following official build instructions for BCHN (here) & Bitcoin Core (here), but eventually I realized they were missing the strip * command. BCHN gave a strange warning when running it, but that issue is apparently resolved with the -DCLIENT_VERSION_IS_RELEASE flag. Without stripping, the bitcoin-qt.exe can be 415 MiB instead of under 31 MiB.

#!/bin/bash sudo apt-get update sudo apt-get upgrade -y sudo apt-get install -y build-essential cmake git git-lfs libboost-chrono-dev libboost-filesystem-dev libboost-test-dev libboost-thread-dev libevent-dev libminiupnpc-dev libssl-dev libzmq3-dev ninja-build python3 help2man unzip sudo apt-get install -y build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev sudo apt-get install -y libdb-dev libdb++-dev liblmdb++-dev sudo apt-get install -y htop git config --global user.email "[email protected]" git config --global user.name "Your Name" #git clone https://github.com/mtrycz/txunami.git #cd txunami #git submodule update --init --recursive #cd BitcoinUnlimited #git checkout dev #./autogen.sh #./configure --with-gui=no --enable-shared --enable-wallet --with-incompatible-bdb #make -j9 #./src/bitcoind -scalenet -blockmaxsize=256000000 -maxmempool=2048 -daemon -rpcworkqueue=32 #cd .. #make git clone https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node.git cd bitcoin-cash-node/ git checkout 24.1.0 #git clone https://gitlab.com/matricz/bitcoin-cash-node.git #cd bitcoin-cash-node/ #git checkout phmap mkdir build cd build cmake -GNinja .. -DBUILD_BITCOIN_QT=OFF -DCMAKE_BUILD_TYPE:STRING=Release ninja #cd #wget https://mtrycz-test.s3.eu-central-1.amazonaws.com/prunedscalenet.zip #unzip prunedscalenet.zip mkdir /dev/shm/.bitcoin cd # ./bitcoin-cash-node/build/src/bitcoind -daemon -debug=bench -debug=coindb -checkpoints=0 -assumevalid=0 -datadir=/dev/shm/.bitcoin -scalenet # tail -f /dev/shm/.bitcoin/scalenet/debug.log | grep -E --color "Flush:|"

BCH runs by a diverse set of node implementations that have slightly different implementations (and docs), although following the same consensus rules. I would recommend starting with BCHN's list of consensus changes since the hard fork in 2017: https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node/-/blob/master/doc/bch-upgrades.md

A draft implementation is coming to testnets for BCH via Bitcoin Cash Node hopefully soon.