Ray Wallet

Your easy-to-use #RGB and Ultraviolet wallet. Non-custodial

[BTC Times @BTCTimescom]

The @rgbconsortium & @dr_orlovsky have released RGB I.0 — a scalable smart contract system for #Bitcoin & Lightning using client-side validation, zk-STARKs, and single-use seals. 🟥🟩🟦

https://t.co/BAr66rewKC

[Ray Wallet @raywallet_app]

Hear the major announcements about our wallet on the #BH2025

[Hodl Hodl @hodlhodl]

🔥 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: https://t.co/uRySiJ0mUL

See you in Riga! 🇱🇻

[Ray Wallet @raywallet_app]

Ray wallet will support RGB wallet descriptors from the day one

[RGB Consortium @rgbconsortium]

Wallet descriptors for RGB allow wallet interoperability by representing wallet definition in a human-readable string. They originate from bitcoin output script descriptors, which has gained huge adoption among bitcoin wallets.

We have published the specification how RGB wallet descriptors operate. Please check https://t.co/YGFXLFqzt6 (general descriptor operations) and https://t.co/foWe5zGzSe (tapret-supporting descriptors).

[RGB Consortium @rgbconsortium]

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 https://t.co/aEmwbPWFdy 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://t.co/ZuCisTNeYA

[RGB Consortium @rgbconsortium]

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.

[Marius Off🔗Chain @mariusoffchain]

@yolo2064 @GA_Crypto_ @carlitacrypto_ @LeCryptoDaily @CryptoastMedia @TheCrypt0Matrix @CryptoPicsou @crypto_futur @cryptosaurien @_Cryptique @JoestarCrypto @lendasat Sooner than you think

La 0.12 est sortie, ça veut qu'il manque plus qu'elle soit implémenté par des app, cad que c'est live depuis qq semaines déjà

https://t.co/M2fnjRdxC5
https://t.co/LOboUspvK5

[LNP/BP Labs @lnp_bp]

What is RGB-21 NFT standard? 📕📗📘

1/ RGB-21 standard offers non-fungible assets (or tokens) which may be separately owned and can be transferred between the owners in a permissionless manner, without acknowledgment of an issuer.

[Ray Wallet @raywallet_app]

Fungible assets on #Bitcoin are coming soon 🥳

[LNP/BP Labs @lnp_bp]

What is RGB-20 Standard?🧐🧵

1/ RGB-20 standard offers fungible assets (or tokens), which supply is split between individual owners and can be transferred between them in a permissionless manner, without acknowledgment of an issuer.

[Nandini Arora @nandiniarora584]

Wallets like @BitcoinTribe_ are built upon RGB protocol.
Others include, @BitMask_App @Bitlight_wallet @raywallet_app

Read the RGB blackpaper for better understanding.
https://t.co/ogLuRwo5ZR

[Pandora Prime Inc @pandoraprime_ch]

🔥RGB v0.12 RC1 is here!🔥🔴🟢🔵

Today is not just another #BitcoinPizzaDay🍕
This day marks an important milestone for #Bitcoin.

After 7 months of tireless work, RGB v0.12 RC1 has been released, bringing RGB smart contracts to the new level.

What does this mean for developers, users and #Bitcoin in general? Short 🧵👇

[LNP/BP Labs @lnp_bp]

LNP/BP Standards Association announces RGB version 0.12 with the release candidate 1. As of today, it is the most tested and robust version.

Over the last half of the year, we have brought zk-STARK readiness to the RGB (making it "zk-STARKy"), a huge performance boost, and a lot of simplification and security improvements.

The release candidate is for all developers working with RGB, so they can integrate it into their software.