Transparency & verify

Bridge security depends on public verification, not hidden knobs. This page lists what is published, what is on-chain readable, and what we commit to for partners and users.

Operator

Published on-chain

These are not secrets. Read them from the deployed bridge contract on DogeOS (RPC or block explorer). The bridge UI status page mirrors live values. DogeSoftBridge 2.6.0-ds-standard is 0x762d952DDc9bbF11b8442347D2D1B66934703036 on DogeOS Chikyū testnet (chain id 6281971). wDU$T is 0xC1b2889D74Bb9D615E4ce852777FE7583e79b8dA (18 decimals). L1 custody is D9K5fqJ6vhs3FfUgiEn69SYZJQQvtsB2Su. Admin and attester changes are timelocked.

• Bridge contract address
• Wrapped DRC-20 token addresses per ticker (getWrappedAddress)
• attesterThreshold and registered attester addresses (getAttesters)
• l1ConfirmationsRequired and l2ConfirmationsRequired
• l1CustodianAddress (Dogecoin custody destination)
• timelockDelay, minBridgeAmount, maxBridgeAmount
• Per-token rate limits and pause flags
• Mint / release events with l1TxHash, ticker, amount

Contract version: DogeDogeSoftBridge 2.6.0-ds-standard (MIT license).

Verify a mint yourself

1. On DogeOS: Find the mint event — note l1TxHash, l1Vout, ticker, amount.
2. On Dogecoin: Open the same txid in Explorer or your own Core node — confirm the DRC-20 transfer inscription to custody, its BRIDGE_L1_DEPOSIT ref, and 6 confirmations.
3. On that DogeSoftBridge contract: Confirm the ref is marked used and attester threshold was met for that mint transaction.

Wrapped supply is backed by custodian lock + this verification path. It is not a claim that every third-party indexer in the world would parse identical DRC-20 edge cases — it is the DogeSoft reference index that wallet, explorer, and bridge already ship on.

Open source & audit roadmap

What stays private (operational security only)

• Private keys — attester, operator, governance, custodian WIF
• Internal RPC credentials and service API keys
• Unreleased operator-only APIs not yet opened for builders

Contract addresses, thresholds, and confirmation policy are never in this bucket — they are public by design.

Operator continuity & sunset

Wrapped assets only work while the operator can still verify locks and pay releases. If that process stops, wrapped DRC-20 on DogeOS is a claim on L1 custody, not a native L1 coin.

DogeSoft commits to:

• Published L1 release path — burnForRelease → BRIDGE_L1_RELEASE inscription → settleRelease on chain.
• On-chain pause + timelock governance — no silent parameter swaps.
• Wind-down playbook — pause new mints, honor a burn→release window, publish redemption tooling.
• Reserve cap (1,000,000 DU$T, stale after 7 days).

Users should treat wrapped DRC-20 on DogeOS as bridge-issued claims on L1 custody, not as native L1 coins — same as any lock-mint bridge.

FAQ — common review questions