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 (DogeOS)

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.

• 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: DogeSoftBridge v2.5.0-drc20-production (MIT license).

Verify a mint yourself

1. On DogeOS: Find the BridgeCompleted / mint event — note l1TxHash, l1Vout, ticker, amount.
2. On Dogecoin: Open the same txid in Explorer or your own Core node — confirm custodian vout, OP_RETURN DRC-20 transfer, and confirmation depth.
3. On DogeOS contract: Confirm processedL1Deposit(l1TxHash, l1Vout) is true 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 — BRIDGE_L1_RELEASE via inscriber; L2 burns trigger custodian payout.
• On-chain pause + timelock governance — no silent parameter swaps.
• Wind-down playbook — pause new mints, honor a burn→release window, publish redemption tooling.
• TVL caps until audit + multi-operator attestation milestones are met.

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