Exchange sidechain coins for Bitcoin, Bitcoin Cash, Litecoin, and more — peer-to-peer, with no intermediaries. Powered by BIP-300 drivechain technology from Layer Two Labs.
A trustless swap protocol that leverages sidechain consensus to enable safe cross-chain exchanges.
When a swap is created, L2 coins are locked on-chain. Only a valid claim transaction can unlock them, preventing double-spends and MEV attacks.
Coinshift monitors the parent chain via Bitcoin Core RPC, tracking confirmations and verifying that L1 payments have actually been made.
Every swap has an expiration block height. If the L1 payment isn't confirmed in time, locked coins are automatically returned to the maker.
Swap sidechain coins for BTC, BCH, LTC, and more. Each parent chain has configurable confirmation requirements and RPC settings.
BLAKE3 hashing generates unique, deterministic swap identifiers that prevent duplicate and replay attacks across the network.
Use the cross-platform desktop app, the command-line interface, or integrate directly via the JSON-RPC API. Choose what fits your workflow.
Coinshift sits at the intersection of the Bitcoin mainchain and BIP-300 sidechains. A Layer Two Labs project.
The BIP-300/301 patched Bitcoin Core node provides the base layer — securing sidechain deposits via hashrate escrows and committing sidechain block hashes via Blind Merged Mining.
Validates sidechain deposits, withdrawals, and BMM commitments. Acts as the bridge between L1 and L2, ensuring consensus rules are enforced on both sides.
The sidechain runtime hosts the swap protocol, wallet, mempool, and miner. Blocks are merge-mined with Bitcoin via BMM, inheriting its proof-of-work security.
The core swap protocol: create offers, lock outputs, monitor L1 payments, and claim coins — all trustlessly enforced by the sidechain's consensus layer.
Coinshift monitors these parent chains via Bitcoin Core-compatible RPC to verify that L1 payments have been made and confirmed.
A typical L2-to-L1 swap in four steps.
Alice locks her L2 coins on the sidechain, specifying how much L1 she wants, which parent chain, and her L1 receiving address.
Bob sees the offer, agrees to the rate, and broadcasts an L1 transaction to Alice's specified address.
The system monitors the parent chain via RPC. Once the required number of confirmations is reached, the swap becomes claimable.
Bob submits a claim transaction on the sidechain. The locked outputs are released to him. The swap is complete.
Download the full drivechain stack and start swapping on testnet or mainnet.