Bridge — BLOCK ⇄ wBLOCK
Move value between the Blockle post-quantum layer-1 (native BLOCK) and Solana, where it is represented by wBLOCK, a wrapped SPL token. This is a custodial, trusted-operator bridge: every wBLOCK in circulation is meant to be backed 1:1 by BLOCK held in the operator reserve. It is not a trustless on-chain vault.
Bridge assets
Reserves & backing
BLOCK vs wBLOCK
BLOCK is the native coin of the Blockle post-quantum L1 (8 decimals, block1… addresses). It exists only on the Blockle chain.
wBLOCK is a standard SPL token on Solana (also 8 decimals) that represents BLOCK. It is minted when BLOCK is deposited to the bridge and burned when wBLOCK is redeemed back to BLOCK.
How a bridge works here
BLOCK→wBLOCK: you send BLOCK to the bridge address; after enough confirmations the operator mints the equivalent wBLOCK to your Solana address.
wBLOCK→BLOCK: you burn wBLOCK to the bridge; the operator then releases BLOCK from the reserve to your Blockle address.
⚠ Risks — read before bridging
- Custodial trust. wBLOCK is only as safe as the operator. If the operator's reserve or keys are lost, compromised, or mismanaged, wBLOCK can lose its backing. There is no on-chain vault or smart-contract guarantee enforcing 1:1 backing.
- Wrapped-token risk. wBLOCK is not BLOCK. Its value depends entirely on the bridge honoring redemptions. A wrapped asset can trade below its backing or become non-redeemable.
- Cross-chain risk. Bridges are a common target for exploits. Transfers cross two independent networks and are irreversible once confirmed. Always double-check the destination address and the direction.
- No finality from a signature. Signing a transaction in your wallet only submits it. A bridge transfer is complete only after the source chain confirms and the mint/release lands on the destination chain. Watch the status stages.
- Operator discretion & limits. Per-transfer and daily limits apply. The operator may pause the bridge. Funds sent outside the supported flow may be unrecoverable.