Our joint with @lnp_bp proposal on improving wallet descriptors:

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-September/021946.html

How to build trustless 2-way-peg with zero soft forks - and bring BTC to RGB for enhanced Bitcoin programmability and privacy: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-September/021948.html

We are happy to welcome @yanganto - the new LNP/BP Standards Association developer and RGB maintainer, who is joined us with the support and help coming from BitLight Labs!

LNP/BP Standards Association is happy to announce the fifth beta release of RGB protocol version 0.11.

This is another milestone on the stabilization of the new v0.11 RGB version. It is the first complete beta release of both consensus-level libraries, standard libraries and tools happening in 2024, opening a way for independent developers integrating with RGB to test all the new functionality.

Release details: https://rgb.tech/blog/release-v0-11-beta-5/

Bitcoin universal computing with L2 client-side validation using AluVM and RGB assembly - and no onchain footprint, fees, softfork or other issues like in all these L1 controversial proposals.

The power of client-side validation which comes with RGB v0.11

Welcome #SSI: self-sovereign identities made with #Bitcoin single-use seals!

ssi:LZS1ux-gjD9nXPF-OcetUUkW-6r3uSCS6-aQhs9W5f-8JE7w

This SSI will be used by us for signing all standard #RGB interfaces and libraries - and assets issuers will be able to do the same for their contracts, such that wallets and users can be safu from impersonators.

Stay tuned to learn more - we will be releasing SSI docs & code alongside RGB v0.11 release.

🚀️️ Congrats to everyone and thank you all for your contributions: we have v0.11 beta 6 out

Beta 6 marks new stage in RGB readiness - please read all the details in the public announcement: https://rgb.tech/blog/release-v0-11-beta-6/

🚀 RGB v0.11 beta 7 is released, coming with many bugfixes and an important improvements:
- introspection of global contract state from scripts
- improved handling of blockchain re-orgs and RBFs
- improved Lightning operations
- hot taproot RGB wallets
- efficient managing of RGB contract state in enterprise and embedded environments
- support for Mempool API and Testnet4

Read the official announcement and learn about all new features and improvements in our blog post: https://rgb.tech/blog/release-v0-11-beta-7/

🚀 RGB v0.11 beta 8 is released, marking the start of the pre-release code freeze. The new beta comes with a several bugfixes and completion of previous epics related to the data persistence and better eltoo support.

Beta 8 release continues a phase of preparation for a public preview of the RGB v0.11. All parties are strongly recommended switching to this latest beta 8, which contains a number of bugfixes and a consensus-breaking change, and provide us with their feedback.

Beta 8 starts a period of codebase freeze: only critical vulnerability changes will be accepted to the codebase. Once there were no critical vulnerabilities discovered, a Preview 1 version of RGB will be released.

Read the official announcement and learn about what's next in our blog post: https://rgb.tech/blog/release-v0-11-beta-8/

Dr. Maxim Orlovsky’s talk from Baltic Honeybadger is live! 🤓🍿
Check it out to learn more about RGB, its ecosystem and future.

RGB is a native member of Bitcoin and the Lightning Network ecosystem. Check out this video if you want to learn more about it! 🔥

https://www.youtube.com/watch?v=m5E6-npQ97w

⚡️🥳Announcement alert ⚡️🥳
We are proud to announce that this year the LNP/BP Standards Association that has been overseeing the RGB development since 2019, has joined the sponsoring team of one of the oldest and most pure signal conferences in the sphere - Baltic Honeybadger that takes place 9th-10th August in Riga🇱🇻

We will be presenting many updates, news and throw workshops, so get your tickets and see you all soon!

Full announcement here https://x.com/lnp_bp/status/1940758927375057291

🥳 Video from BTCPrague RGB event is up! 🥳

During the BTCPrague conference we organised a side event where the latest news on the state of RGB: protocol, tooling and ecosystem were presented.

What is covered in the video?
- Latest news on the state of the protocol and tooling around it.
- Last steps towards the official RGB release.
- Q&A session, including the answer on ‘How do I start with RGB?’
And much more 😎

Huge shoutout to Dr. Maxim Orlovsky for a great and comprehensive presentation! 👏

Grab your coffee, make yourself comfortable and enjoy!
https://youtu.be/Q34QcP2GMMU

🎉 Release Announcement

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/

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][v0.12], see the image 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 https://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: https://rgb.tech/blog/on-rgb-fork-by-bitfinex/

Today, with @rgbconsortium and @pandoraprime we are glad to present the formal specification for RGB smart contracts