We’ve already adjusted the roadmap around this: upload consignment data in the frontend only, visualize the transfer history together with the BTC txs each transfer was committed to. Site goes live in a few days. Happy to have you test it and share feedback.🫡 #RGB

All roads lead to Bitcoin.

Most registries ask you to trust their index. Ours is built so you don't have to. #RGBMap publishes two things: the public identity of an #RGB asset, and the public segment of the ledger kept by the platforms that issue or list it. Anyone can publish under the same format, and anyone can rebuild the index from what has been published. It is a format and a set of rules. Not a chain, not a database. the index is not the source of truth where an index and a recomputation disagree, the recomputation wins Every byte an index names is fetched again and hashed again. A tampered index cannot make a check pass, because nothing it says is believed. What we never do, on purpose: decide whether an asset is safe merge statuses into one "verified" mark approve — registration is a signed declaration, and nobody reviews it delist — a conflict stays visible, with the conflict shown hold funds — custody stays with the platform know who is reading — no account, no session An index is replaceable, and it should be. Auditable is not trustless. #RGB #RGBMap

It would be cool to also have a website where you can upload your consignment data in the frontend (never sent to a server) and visualize the history together with the BTC txs each transfer was committed to

RGB Protocol Association will host the Stablecoin Summit! Discover more about why Bitcoin needs stablecoins, where the demand comes from, and other related topics. - October 25, 2026 - Lugano, Switzerland - LAC (Sala 1) top floor, with a beautiful view of the Lugano lake

"Supports #RGB" is not a spec. It's a question. #RGB has no single asset type. It has five schemas, and they don't behave the same way: NIA fixed supply, defined at genesis IFA inflatable, with an issuance policy CFA collectible fungible UDA unique digital asset PFA permissioned, for securities and RWA Which is why "does your wallet support #RGB?" is the wrong question. A wallet that handles NIA perfectly can still be the wrong place to receive an IFA, and the sender usually finds out after the fact. In #RGB, schema support is not a preference. It decides whether the transfer can happen at all. #RGB

lightning -> x402

Tether CEO Paolo Ardoino says USDT on Bitcoin is coming Tether has been building toward a Bitcoin-native version of USDT, including through RGB and the Lightning Network Ardoino says expanding stablecoin access on Bitcoin remains a priority for Tether He described RGB as a major pathway for USDT and said Bitcoin has always been central to the company’s vision

Shielded Bitcoin: Private Transfers on Bitcoin L1

Spent an evening in Washington talking USDT on Bitcoin with @MorganStanley They invited me to dinner, where I caught up with @MergnerMS, Joe Medioli and a few people from the team I’ve known for quite some time We talked about @utexocom working with Morgan Stanley on USDT adoption on Bitcoin, both in Europe and globally

USDT on Bitcoin. It's coming home

"Total supply" is the first number everyone asks for. In RGB it is also the one number you cannot honestly print as a single value. NIA — fixed supply. Genesis defines the issuance and secondary issuance is impossible, so initial supply is verifiable. Everything after genesis is ownership moving. IFA — inflatable. There is an initial supply, a maximum defined by the schema, an issuance policy, and a history of every inflation and burn. Genesis only gives you the starting point. Read genesis, print "current total supply" — that is simply wrong. Which leaves three numbers that routinely get collapsed into one: max supply defined by the schema initial supply verifiable at genesis current supply only what has been disclosed, not what exists Any listing that prints a single number is guessing.

Same asset. A different answer in every wallet. One shows it. The next doesn't. A third shows it under a different name, with the wrong logo. Nobody is lying. There's just no public record to check against. That's the gap a registry fills.

We're not asking anyone to trust us. Every record is built from what the issuer published, and carries the evidence to check it without us. The whole index exports. Anyone can mirror it, re-verify it, and run it. If RGBMap disappears tomorrow, the data doesn't.

A registry entry isn't a page. It's a record. Identity, claims, issuer, media, anchor — every field is either verifiable, or explicitly marked unverified. No third state. No blank field that quietly means "fine". Balances and holders are never in it.

RGB Bytes: a blinded UTXO hides which Bitcoin UTXO will receive your assets. Only the sender and the receiver know it, until it is spent again. This way, RGB keeps transfers private.

RGB Association was at @Bitcoinconfasia in Hong Kong 🇭🇰 @birk1907 joined the panel "Pragmatic Maximalism: The Market Wants Stables," and @kaleidoswap was a guest at The Night Shift, the side event co-hosted by @TreeNewsMed and @BiHelix_ . Meeting Stablecoins interest in Asia!

new USDT on Bitcoin launch partner dropping soon eyes wide open

Same name. Same ticker. Same logo. Different bytes. RGB v0.11.1 and v0.12 are separate namespaces. Separate validators. One name, two contracts. Key on the name and you hand a user the wrong contract. Identity is network + protocol version + contract id. Never the name.

We don't know if an asset is good. We don't know if an issuer is honest. We don't know what you hold. RGBMap answers one question: is this record real and intact? Everything else is a verdict. A registry that can't say "I don't know" is just a marketing channel.