Core + full UTXO
Indexer & truth layer
What the DogeSoft production indexer proves for bridge deposits — UTXOs, DRC-20, inscriptions, the Doge Soft Inscription Standard.
The DogeSoft bridge does not trust a balance API. It verifies deposits against a full Dogecoin indexer fed directly from Dogecoin Core — the same production ledger that powers Explorer, Wallet, AMM, and Inscriber.
Core-first, not API-second
The indexer follows the chain tip from Dogecoin Core with minimal lag (typically milliseconds behind the node). Bridge L1 verification calls Core for raw transactions, block height, and confirmation depth, then cross-checks indexer hydration for agreement on tx decode and depth.
What the production indexer maintains
| Dataset | Why bridge cares |
|---|---|
| Full UTXO set | Every spendable output — spend tracking, not address balances alone |
| Transaction graph | txid → vouts, scripts, values, confirmation height |
| Inscription envelopes | Commit / reveal / move per Doge Soft Inscription Standard |
| DRC-20 state | Tick, amount, deploy/mint/transfer ops, current carrier ownership |
| Doginals / media | Content types, collection metadata (ecosystem consistency) |
| Reorg-aware confirmations | Promotion only after safe depth — same logic as wallet sends |
| Mempool / tip monitoring | Pending visibility before confirm (where enabled) |
How this proves a bridge deposit
For DRC-20 deposits, verification is outpoint-level:
- Find the DRC-20 transfer inscription to custody
D9K5fqJ6vhs3FfUgiEn69SYZJQQvtsB2Suand follow it from the reveal to the custody move. - Read the
dstag:BRIDGE_L1_DEPOSITplus the Doge Soft-issued ref. - Check the sender really held the DU$T before sending.
- Match tick + amount against indexed DRC-20 state on the carrier UTXO.
- Wait for Core depth ≥ on-chain
l1ConfirmationsRequired. - Require indexer agreement on tx presence and confirmations.
This is stricter than “custodian balance increased.” Each ref works once, enforced before signing and again on chain.
L1 release (withdraw)
After a burnForRelease on DogeOS, the release goes out on Dogecoin L1 as a DRC-20 transfer tagged BRIDGE_L1_RELEASE with ref = the request id, then settleRelease closes it on chain. The indexer reads it
like any other DRC-20 transfer, so Explorer shows it with no second parsing stack.
One truth layer across products
Same indexer interpretation in:
- Explorer — human-readable chain browse
- Explorer API — integrator reads (public REST)
- Wallet + extension — balances, sends, DRC-20
- AMM — pool state and swap settlement inputs
- Bridge — deposit gates and release checks
There is no competing production Doginals indexer with this vertical integration today. Others may run nodes and implement Doge Soft Inscription Standard; DogeSoft ships the reference production index that users and apps already depend on.
Wrapped DRC-20 and “canonical L1”
wDRC-20 on DogeOS represents DRC-20 locked in custodian UTXOs as interpreted by the DogeSoft reference indexer under Doge Soft Inscription Standard — the same interpretation the wallet already shows. We do not claim every third-party indexer would parse identical DRC-20 edge cases — we claim one consistent, Core-backed, production index across the entire DogeSoft stack.
Wallet dual-indexer note
The mobile wallet may merge a live tip indexer with the archival explorer index for display balances. Bridge deposit verification uses the archival explorer index + Core for deterministic proof. Wallet and bridge stay aligned on tick, amount, and ownership semantics via Doge Soft Inscription Standard.