Some context:
We are happy to announce a new release a RGB Core v0.7, which provides a freeze for all consensus-related formats. It ships with full taproot-based OP_RETURN commitments; new LNPBP-4 multi-protocol commitments based on merkle trees (support for using RGB alongside other client-side-validation protocols); state transition bundling for multi-participant transactions (required for LN, pay/coinjoin); data containers (binary data for NFTs etc) and support for arbitrary rich data in contract state with a new schema for representing hierarchies of such data strucutres.
Alongside it we have released RGB Node v0.7 Beta 1, which is a developer preview to test all those new RGB features. The RGB Node API is subject to change with the new v0.8 version (which will include many wallet/PSBT-related, data storage and networking) changes, so it is advised not to invest a lot of effort into integrating this version and rather wait for v0.8 in two weeks.
reply
This sounds interesting, but still hard to comprehend the implications. I have yet to find a good documentation/summary of RGB. Is there e.g. any mobile wallet example taking advantage of RGB is some form?
Folks from RGB claimed that Taro is a clone, so I read documentation of Taro and that was explained quite well. If it's indeed a clone then I have some understanding. Or is there some notable difference that RGB has?
reply