We are happy to announce formation of the RGB Consortium: the official non-profit body acting as an industrial consortium, which will take over the maintenance of RGB protocol and will steward its further development.

Let me unpack what this actually means for Bitcoin (not trying to prove anything to anyone, just share results of my personal “do not trust verify” of the @GrassFedBitcoin claims). 1. Any minority with hash power ~10-20% and minority of nodes (by count, economic value) of <1% may activate a soft fork, causing a chain split and putting the majority funds into a double-spend risk for weeks/month, stopping main chain from efficient operations. 2. This is not how SegWit was activated and was not known before. It is not “just a UASF”. 3. Even if you do not see how pt 1 is possible, it is possible (game-theoretically proven, see my tweets over pas week and discussions with @giacomozucco) and IS a strategy officially used by BIP-110 gang which they proud of discovering, claiming this is a “distributed authoritarianism” and it is good for Bitcoin. 4. Unlike them I see this as a bad thing and not an authoritarianism, but rather a form of destructive nihilism. 5. In pt 5 “possible” doesn’t mean “it will certainly happen”. Yet still just a fact of its theoretical possibility is already a problem: the system with such feature/bug is vulnerable to the whole range of new types of attacks, so even with BIP-110 abandoned, the damage is already done and there will be more followers to this strategy. 6. This vulnerability is specific to PoW consensus with public ledger (“blockchain”), where miners and users see and verify transactions of the entire world. “ZK” do not protect from them. The only protection is a PoW consensus _without_ blockchain - like I proposed few years ago (Prime, for which our team is building a proof of concept).

many thanks to @_polto_ @beBOPcommunity @dr_orlovsky @dr_ukolova for their presence and guest presentations at the first nodl day! Hopefully there will be many others to come! presentations will be available online soon and we’ll also be repeating the announcements here

Ultraviolet is the network made with L2 RGB smart contracts by the creators of RGB - @pandoraprime_ch and @dr_orlovsky It comes with zk-STARK provers, post-blockchain scalability layer 1 Prime, AI agents & data availability layer Storm Follow @UVioletAI along the road of building most decentralized and scalable system in the world

🔥 Speaker Announcement 🔥 We’re honored to welcome @dr_ukolova and @dr_orlovsky to the stage at #BH2025! 🔥 🦡 💡 Olga Ukolova CEO and founder of @pandoraprime_ch, Olga leads the charge in developing scalable, decentralized technologies built on Bitcoin, Lightning, and RGB. Her team is behind tools like Ray Wallet and MyCitadel, designed to make advanced Bitcoin tech accessible and practical for everyday use. 🧬 Dr. Maxim Orlovsky Lead developer of RGB since 2019 and co-founder of both the LNP/BP Association and RGB Consortium. With a background in neuroscience and machine learning, Maxim is pioneering LNP/BP tech to build a framework for a truly sovereign — and post-human — future. Together, they are shaping the next chapter of Bitcoin’s evolution — from smart contracts to privacy-preserving applications. 🎟️ Don’t miss their talks, grab your ticket now: baltichoneybadger.com See you in Riga! 🇱🇻

🔥 Speaker Announcement 🔥 We’re honored to welcome @dr_ukolova and @dr_orlovsky to the stage at #BH2025! 🔥 🦡 💡 Olga Ukolova CEO and founder of @pandoraprime_ch, Olga leads the charge in developing scalable, decentralized technologies built on Bitcoin, Lightning, and RGB. Her team is behind tools like Ray Wallet and MyCitadel, designed to make advanced Bitcoin tech accessible and practical for everyday use. 🧬 Dr. Maxim Orlovsky Lead developer of RGB since 2019 and co-founder of both the LNP/BP Association and RGB Consortium. With a background in neuroscience and machine learning, Maxim is pioneering LNP/BP tech to build a framework for a truly sovereign — and post-human — future. Together, they are shaping the next chapter of Bitcoin’s evolution — from smart contracts to privacy-preserving applications. 🎟️ Don’t miss their talks, grab your ticket now: baltichoneybadger.com See you in Riga! 🇱🇻

RGB yellow paper is released: the first formally specified scalable smart contract system for Bitcoin & Lightning, made with client-side validation github.com/RGB-WG/yellowpape… Follow us for more updates!

An official security notice on RGB fork claimed to be 'RGB v0.11.1' It has come to our attention that the recently announced "release" of "RGB protocol version 0.11.1" runs a fork of RGB v0.11 from unreleased last year codebase, with heavily modifications to the consensus, affecting its security. These modifications were proposed to the main RGB repositories but didn't meet our security requirements and were of poor code quality. Specifically, its unit test coverage is nearly absent (compared to the full test coverage of v0.12 released by us recently, see the image in the full announcement below); it lacks a lot of functionality specific to zk support; it has removed smart contracting capabilities; has heavy performance and scalability issues etc. Thus, while as a free (libre) software project we do not oppose experiments and fork, we can't prevent possible malicious fork code from entering these forks, nor can't prevent users from using the forked code. Thus, we do not advise any production use of version 0.11.1; the only version recommended by us for the production is v0.12 from github.com/RGB-WG organization. Companies may check whether the forked and changed consensus is used in their dependency trees by running cargo tree -i rgb-consensus, which will show whether the forked and modified version of official rgb-core consensus crate is being used. If this is the case, we recommend to update the software or do not use in production. We also advise users NOT to use products built with version v0.11.1 and modified consensus for any assets or purposes with any real value. We also recommend to change the name of the forked version from RGB Protocol, to avoid user confusion and misguidance. In any case, if a loss of assets would happen, neither the real RGB protocol, nor LNP/BP Standards Association or RGB Consortium can be blamed for it (with claims alike "it is based on your code"), giving the facts that that code was never released and recommended by us for the production, and dramatic scale of consensus modification and code changes made in the fork. We will also not support the forked version of RGB as we do not have any resources to perform its audit or analysis; and the fork maintainers are not interested in our critics, rejecting a normal route of PR peer reviews. You can also read this announcement here: rgb.tech/blog/on-rgb-fork-by…

Finally.