Elian Ward

RGB maximalist. Building @RGBMap_

[Elian Ward @Elian_Ward]

for the spark — one public idea, and we built it. Days, not quarters. On signet now. Let’s keep going. 🔥This one shipped because the whole team moved as one. Huge thanks to @FedericoTenga

[RGBMap @RGBMap_]

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

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:
https://t.co/iguHAGQbuu
Read your own:
https://t.co/rwKjZXYmJ4

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

[Elian Ward @Elian_Ward]

Thank you @RGB_Pioneers RGBMap exists because the hard parts showed up in the field, not in the spec and because people kept the work on the open standard. Credit to the wider team, and to @FedericoTenga for the public idea that turned into a reader anyone can open. Grateful to be here.🙏

[RGB Pioneers @RGB_Pioneers]

Recognizing an RGB Pioneer: @Elian_Ward

Elian Ward is building RGBMap, an open registry for RGB assets. He has written in public about the hard parts of a shared registry — canonical encoding, silent hash forks, and field problems that never show up in the spec — and then helped ship a browser consignment reader on signet after one public idea. He credits the wider team and keeps the work on the open standard, with no vendor in the middle. RGB users should know him because he is turning those field problems into tools people can actually open.

Applications for RGB Pioneers are now open!
Our goal is to connect contributors, developers, project teams, and users — giving great projects a chance to reach real users, while creating opportunities for community members to participate in testing, get early access, and earn rewards.

Want to become an RGB Pioneer? The application form is in our pinned post. Share your story and join the early RGB community. More opportunities for Pioneers are coming.

[Elian Ward @Elian_Ward]

This is the loop we want: a public request, an independent implementation, and more teams able to use it. Happy to see Utexo and others building on the same standard.🙏

[Utexo @utexocom]

The RGB community is growing every day.

[Kalshi @Kalshi]

JUST IN: Tether CEO says USDT on Bitcoin is coming

[Elian Ward @Elian_Ward]

If you build on #RGB, six things will bite you.

None of them are in the spec. All of them are in the field.

I have hit five. The sixth is the reason I am building anything at all.

[Ben Arc 🏴󠁧󠁢󠁷󠁬󠁳󠁿✊⚡️ @arcbtc]

Tether is being lined up as THE digital dollar, and needs the #bitcoin rails we're working on to power world reserve level economy. Tether buys US debt (thanks to GENIUS act, so far $140bn), is a huge play I'm amazed isnt being reported more widely. CBDC no/Tether yes, it seems.

[Elian Ward @Elian_Ward]

Two mirrors, two hashes, two versions of the truth, and no error anywhere. That is the failure mode I am designing against.

Which is why this cannot be a website. A website may define its JSON however it likes.

Schema, canonical rules, test vectors. In that order.

[Elian Ward @Elian_Ward]

The hard part of a public registry is not storing the data.

It is making two strangers, in two languages, on two continents, compute the exact same hash from the same asset — forever.

Everything else is CRUD.

Why that one sentence decides the whole architecture:

[Elian Ward @Elian_Ward]

So "content-addressed" is not a feature you switch on.

It is a promise you can only keep if the byte-exact serialization is defined first, in public, and checkable by someone who does not trust you.

Get it wrong and the registry does not break loudly. It forks silently.

[Elian Ward @Elian_Ward]

@RGB_Hub Clean release. Fewer requests for Bitcoin tx validation and a much simpler version pin. That’s the kind of update that actually helps builders.

[RGB Hub @RGB_Hub]

Article Repost:

(1/3)
RGB Protocol on Bitcoin's five core libraries now carry the plain v0.11.1 tag, without the release-candidate suffix.

Check the technical changes:

[Elian Ward @Elian_Ward]

@kaleidoswap @arkade_os @RGB_Hub Just applied

[Elian Ward @Elian_Ward]

@utexocom Appreciate it. That’s exactly the idea — a public index for RGB assets instead of a traditional explorer. Happy to walk you through it if it’s useful on the USDT side.

[Elian Ward @Elian_Ward]

A friend asked what I've been building at night.

I said: a public index for RGB assets. He asked if that's a blockchain explorer. I said no, and then talked for about ten minutes.

He said, "so it's a phone book."

He's right. I've been calling it a protocol.

[Elian Ward @Elian_Ward]

The rule I keep coming back to:

identity = network + rgb protocol version + contract id.

Not the name. Not the ticker. Those are labels anyone can copy.

0.11.1 and 0.12 are separate asset spaces on the same chain, verified separately, never assumed compatible.

[RGBMap @RGBMap_]

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.

[Blox Space @bloxspace_turin]

Hackathon organized by @RGBAssociation 🚀

Build apps where the AI runs on device and the money stays in the user's wallet. €6,000 in prizes, free, 70 places. No RGB experience needed.

Apply by 3 Oct.

Read more : https://t.co/cEe8uNxame

[Elian Ward @Elian_Ward]

@RGBAssociation @bloxspace_turin @bitpolito @tether @WDK_tether @qvac Turin + Tether + RGB

[WDK @WDK_tether]

New WDK blog post: swap and bridge in one interface, five routers.

Discover routes at runtime, get a quote, execute, track settlement. Switch providers by changing one label with the same method names and the same flow.

Five community-built routers. One Swidge interface. Your app doesn't care which one is underneath.

https://t.co/q7CC4FqbSY