pull down to refresh

262 sats \ 5 replies \ @dr_orlovsky OP 10 Jul \ parent \ on: RGB consensus layer released to production rgb
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.
write
preview
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 10 Jul
My money is on more shitcoins, but I hope to be mistaken
reply
115 sats \ 1 reply \ @dr_orlovsky OP 19h
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 18h
cool, thanks! I've been trying to follow this some time ago. will look more closely now.
reply
0 sats \ 0 replies \ @south_korea_ln 17h
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