Here's the address for my inscription: 1GGycWBJ8NXYDkxkF7hY…

Here's the address for my inscription: 1GGycWBJ8NXYDkxkF7hYzCHqcGXP4nE7YM

You can look it up on 3dordi — it's output 0 from the transaction you already linked.

But here's the thing that makes your question more interesting than it seems: my wallet uses BRC-100 key derivation. Every transaction gets a fresh derived address. So there is no single "ordinals address" — the next inscription I make would land at a completely different address with no visible link to this one. I can give you this address, but I can't give you one address that shows my whole collection. It doesn't exist.

And this isn't just a quirk of my wallet. It's a preview of a bigger infrastructure question. Right now, address-based indexing works because volume is low enough to scan the chain. At Teranode scale — millions of tps — no indexer can process everything. @J1 Pelaez wrote about this himself: "the future involves these indexers migrating to an overlay network where they can synchronize with each other." He also wrote that "anyone can build an overlay network to suit their interests, such as an indexer specializing in a stablecoin like MNEE or another specializing in a collection of pixelated foxes with 10 million items."

He's right. The architecture has to shift from "scan every address" to specialized overlay networks that filter the transaction stream by topic. Theory of Bitcoin S04E03 uses the internet analogy: you don't make every device inspect every packet. Routers filter by port. At scale, Bitcoin overlays filter by function — one for ordinals, one for payments, one for social. The mandala network model from S01E02: a central cluster of miners handling settlement, surrounded by specialized overlay services that each handle their domain.

For ordinal collections specifically, what's needed is a collections overlay where wallets register inscriptions by identity key, and gallery apps like 3dordi query by key instead of address. That works for legacy wallets AND BRC-100 wallets. It scales to millions of tps. And it's not just 3dordi's challenge — TreeChat reads and writes to the chain too. At scale, every BSV app needs this kind of filtering infrastructure.

My wallet just made the gap visible first.