NATIVE BCTS · TWO-WAY DOGEOS CHIKYŪ MVP

SwissDLT,
meet DogeOS.

Lock native BCTS and mint sdBCTS on DogeOS. Burn sdBCTS to release your original BCTS. Minimal infrastructure, on-chain evidence, no database.

SwissDLT Chain 94↔DogeOS Chain 6281971

Two-way experimental MVP Separate single relayers in each direction · capped deposits · heuristic confirmations · no threshold validation or external audit. Use small experimental amounts only.

Deposit native BCTS

Your deposit emits a unique, replay-protected ID.

Connect a wallet and verify both network addresses before depositing.

Mint on DogeOS

After source confirmations, anyone can request delivery.

Deposit ID

The relayer checks the source event and DogeOS replay registry before minting.

Return to SwissDLT

Burn sdBCTS on DogeOS, then release the same amount of native BCTS.

Return ID

After DogeOS confirmations, the source relayer verifies the burn and releases collateral.

BRIDGE STATUSChecking configuration…

SOURCE VAULTNot deployed

DOGEOS TOKENNot deployed

01 · Lock

Native collateral

BCTS stays in an immutable SwissDLT vault and can leave only through the configured release operator.

02 · Verify

Confirmed evidence

Each direction waits for configurable confirmations. This is a heuristic, not finality or consensus verification.

03 · Mint & release

Replay protection

Deposit IDs and return IDs are recorded on their destination chains before value is issued or released.