M-of-N on DogeOS
Attesters & co-signers
How multiple signers on the DogeOS bridge contract verify L1 deposits — including ecosystem co-attester slots.
Wrapped DRC-20 on DogeOS is minted only when enough registered attesters have signed the same L1 deposit proof. This is M-of-N multisig on the DogeOS bridge contract — not a single operator approve button.
Plain English
- User locks DRC-20 on Dogecoin L1.
- Each attester independently checks: “This txid:vout is real, confirmed, correct tick/amount, paid to custodian.”
- Each attester signs the mint message with their own key.
- The DogeOS contract counts signatures. If count ≥ threshold → mint. Otherwise → reject.
Nobody can mint alone.
Where signing happens
| Layer | Role |
|---|---|
| Dogecoin L1 | Real coins locked; no smart contract — only UTXOs and OP_RETURN |
| Off-chain verification | Core RPC + DogeSoft indexer build the mint digest (evidence hashes) |
| DogeOS EVM | Bridge contract stores attester addresses, threshold, and enforces mintFromL1Tx |
Attester set & DogeOS co-signers
Attesters are registered Ethereum addresses on the bridge contract (isAttester).
The threshold (attesterThreshold) is public on-chain.
Current model:
- DogeSoft operator attester — runs Core + indexer verification, signs with operator-controlled key.
- Ecosystem co-attesters (partners) — separate organizations with their own attester keys and their own Core + Standard v1 verification before signing.
Partnership integration includes a co-attester slot on the DogeOS bridge contract. Plain requirements:
- Attester keys are separate — each partner holds and uses their own signing key.
- Verification is Core + Inscription Standard v1 — not “trust DogeSoft’s API response.”
- A co-attester must be able to re-check the L1 outpoint themselves (own Dogecoin Core + own Standard v1 parse) and refuse to sign if tick, amount, owner, custodian output, or confirmations do not match.
- Re-reading only the DogeSoft indexer API is not independent verification — that is a second signature on one truth source.
We do not pretend a second full wallet / explorer / AMM / oracle stack already exists. The co-attester requirement is: Core + Standard v1 parser + own key + right to refuse on divergence.
Honest disclosure: Multiple signatures over a shared verification pipeline is weaker than each attester running fully isolated infrastructure. The partnership program exists to add independent operators and keys — not to pretend competing indexers already exist for Doginals/DRC-20 production.
What each attester checks before signing
- L1 transaction exists on Core and meets
l1ConfirmationsRequired. - Custodian received the expected vout (
scriptPubKeyhash in digest). - OP_RETURN hash matches DRC-20 transfer envelope (
opReturnHashin digest). - Tick and amount match the bridge session and indexed DRC-20 state.
- Outpoint not already minted (
processedL1Deposit). - Reserve attestation hash valid for the ticker on-chain.
Partner / embed program
Integrators who embed DogeSoft Bridge or route volume through DogeOS can apply for:
- Registered co-attester address on the bridge contract.
- Reference attester implementation (verify Core + Standard v1, sign digest — not indexer-API-only).
- Published ABIs and verify playbook (Transparency).
Contact: dogesoft.io — partnerships / builders channel.