pull down to refresh

RGB consensus layer released to productionrgb.tech/blog/release-v0-12-consensus/
11.8k sats \ 8 comments \ @dr_orlovsky 10 Jul rgb
The LNP/BP Standards Association is excited to announce the final production-ready release of the RGB smart contracts consensus layer (v0.12)!
From today, all RGB contract developers and issuers can deploy contracts on both testnet and Bitcoin mainnet using this stable consensus release.
⚠️ Important: For security and ecosystem consistency, we strongly recommend re-issuing any contracts created with pre-release versions using this final v0.12.
🛠️ Please note:
This is a consensus layer release. It will be followed by releases of the standard library and applications. The consensus layer is unique among RGB libraries because it defines contract stability: only changes at the consensus level can break backward compatibility for contracts. Therefore, with this final v0.12 release, contracts are now forward-compatible.
Read the full release details on https://rgb.tech/blog/release-v0-12-consensus/
write
preview
related posts
135 sats \ 6 replies \ @Scoresby 10 Jul
I'm curious about RGB. It's been around for a long time now, and while I can find a number of articles that explain what it is, it seems like adoption hasn't been very strong. I'd be interested to read a fair critique of it. Why isn't it more widely in use?
reply
262 sats \ 5 replies \ @dr_orlovsky OP 10 Jul
The main reason of its not being used is the fact that it was not released for production (until today). Consensus in client-side validated systems (RGB belongs to them) is kind of ossified from the day one when you start using in production; it is much harder to change that than blockchain consensus. Thus, it took many years to build a system which has everything needed, including zk-STARK readiness.
I am quite sure we will see a boost in RGB adoption over the next months after the release.
reply
63 sats \ 3 replies \ @Scoresby 10 Jul
Wow, this is pretty exciting! I'll be quite interested to see what kind of consumer applications take it up.
reply
0 sats \ 2 replies \ @SwapMarket 17h
My money is on more shitcoins, but I hope to be mistaken
reply
115 sats \ 1 reply \ @dr_orlovsky OP 4h
Not just shitcoins. Also:
  • better liquidity on lightning
  • much better privacy (broken tx graph)
  • souvereign legal system
  • sovereign bearer audit logs (timestamps++)
  • better bitcoin programmability (much better)
With Prime (client-side validation layer 1):
  • 1 sec settlement time
  • no blockchain
  • tens of millions tx per second with no inbound liquidity problems like in lightning
  • constant size data with zk-STARKs client-side peer-to-peer proofs
And yes, there is bitcoin trustless bridging to RGB and Prime - with Radiant and/or BitVM (whatever happens first).
reply
0 sats \ 0 replies \ @SwapMarket 3h
cool, thanks! I've been trying to follow this some time ago. will look more closely now.
reply on another page
0 sats \ 0 replies \ @south_korea_ln 2h
Consensus in client-side validated systems (RGB belongs to them) is kind of ossified from the day one when you start using in production
Why is that? Is it a technical reason?
reply
0 sats \ 0 replies \ @south_korea_ln 2h
How does client-side validation work?
I vaguely remember that one critique was that true consensus is impossible because there is no global state. One asset can be sold to two other participants, and they won't know it is a double-spend unless they talk to each other.
But later, I read somewhere you said you solved this.
Do you know what I am referring to? If so, can you elaborate a bit?
reply