RGBMap now supports NFT collections on RGB 🎨 We've opened an NFT collection standard: projects can open a collection and register each NFT (called a UDA on RGB) under it, with an item number, traits and artwork. Only NFTs signed by the same address as the collection count as members. Anyone else claiming your collection is flagged as a conflict and never counted. No approval step, just your own wallet signature. How to register: ① Open a collection (before minting) Enter a name and how many items, then add a cover (≤256 KiB), website, X and Telegram. Click "Sign with wallet", then "Open". The item count is not a supply cap; leave it at 0 to declare nothing. ② Register a UDA (after minting) Export the contract consignment from the wallet that issued your NFT and upload it. Contract id, name, ticker and precision are read from the file and locked. Then add a logo (PNG/SVG/WEBP, ≤100 KiB) and artwork (≤512 KiB). Keep the artwork small, since it travels with the asset. ③ Join your collection & add issuer proof Pick your collection, set the item number and add traits. Only a collection opened by the address you sign with will count the NFT. For issuer proof, add a DNS TXT record (rgbmap-issuer=) or post the manifest sha256 from your social account. Once indexed, each NFT lights up its cell on the collection page 🟩 Registration is a signed declaration, not an approval or a listing, and published records can't be withdrawn. Try it on Signet 👇 rgbmap.org/signet/join @FedericoTenga @RGB_Bitcoin

A while back @FedericoTenga asked in our group for a sample signet consignment, something people could actually try. Fair ask. Reading about RGB gets you only so far, the design clicks when the files are in your hands. So we built the Sandbox: rgbmap.org/sandbox It runs a full RGB round trip in your browser, on signet, Bitcoin's test network: • two wallets, funded by a faucet • color UTXOs and issue an asset • a chain of three transfers • export the two consignments at the end Nothing to install, no real coins. Every transaction is real, on signet, with a public explorer link, so you can check each step yourself. It all runs in your own browser tab, and nothing gets sent to our servers. We showed it at this week's RGB community call. Thank you, Federico. Your question turned into the walkthrough we now give everyone. RGBMap is what our small team works on full time. We're staying in this ecosystem for the long run, building tools that help more people actually use RGB. If you try the Sandbox and something feels off or unclear, tell us. That feedback is what shapes the next release. Thank you to @RGB_Bitcoin and @MarJJhodl for having us on the call. A small team doesn't forget a chance like that. rgbmap.org/sandbox

Something is being built at #RGBMap. 👀 We spotted a real pain point in the #RGB ecosystem. Instead of writing about it, we started building the fix. It's real. It's useful. It's not ready to be shown yet. #RGB

Same job, different custody. Taproot Assets has the Universe: proofs, served by servers. RGB can't copy that, it's client-side validated, so there is no pool of proofs to serve. #RGBMap publishes what can be public (name, logo, contract ID, signed declarations) and reads what can't (consignments parse in your browser). We hold no proofs. Where an index and a recomputation disagree, the recomputation wins. Auditable is not trustless. rgbmap.org

#RGBMap is on rgb.info, listed among the RGB wallets, DEXs and infrastructure tools. Thank you @RGB_Bitcoin . And we'll keep working to grow this ecosystem.🥳 rgb.info/ecosystem/rgb-walle…

It's live. 🫡 Wednesday @FedericoTenga asked for consignment data read in the frontend — never sent to a server — next to the BTC tx each transfer was committed to. Days, not quarters: it's on signet now. The engine: rgb-lib compiled to WebAssembly, in your tab. Drop a .rgb file and the panel says it out loud — sent anywhere: 0 bytes. What comes back: the issuance, every transfer since, each one's witness tx (opret / tapret), seals, amounts, and what each sender kept. Blinded receipts stay blinded. Our test drop: 4 assets, 6 allocations, 7 transfers — 7 of 7 witness txs carried in the files, 7 of 7 anchored on bitcoin. Blocks 323,460 → 323,467. No wallet. No seed. No account. Credit where it's due: the idea is @FedericoTenga's — one public tweet, and it became a spec anyone could build. RGBMap is an independent team on the open standard: no permission asked, no vendor in the middle. One thing worth saying plainly: no wallet exports consignments yet — that button is the ecosystem's last mile. Until it ships, consignment-export reads yours out of an rgb-lib wallet backup on your own machine, offline: github.com/rgbmap/consignmen… Looking forward to the day a wallet ships it — and to the other teams building on RGB. Then this page is one drag and one drop. Sample, one click, no file: rgbmap.org/signet/consignmen… Read your own: rgbmap.org/signet/consignmen… If a file breaks the reader, we want to hear about it. Want a batch of signet packages to run through it? Say the word. #RGB #RGBMap

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

"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

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.

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.

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.

One "Verified" badge tells you nothing. Valid. Signed. Anchored. Media intact. Ownership unspent. Five different facts — collapsed into one meaningless checkmark. So we split it into five. A wallet can show them separately. We publish evidence, not verdicts.