ONE ASSET. TWO NETWORKS.
A bridge for your WIN.
Move native WIN to Winc (WINC) on BNB Smart Chain.
Always six decimals. Designed for one-to-one backing.
1 · Your WIN wallet
Open Win-client to unlock a saved wallet or choose “Import WIN wallet JSON”. Your WIN wallet will approve the escrow lock before any WINC can be minted.
Not connected · WIN wallet connection is not available yet.
Keep your recovery phrase and private key inside Win-client. This bridge never asks you to import them.
2 · Your BSC wallet
WINC · 6 DECIMALSContract deployment and bridge activation are required before transfers.
Connect MetaMask to select your BSC Testnet address. BNB remains the gas coin. Connecting never approves a transfer.
Not connected.
- Wallet address
- —
- Network
- —
- Gas balance
- — BNB
- Token balance
- — WINC
- WINC contract
- Not deployed
Use the MetaMask extension or open this page in the MetaMask mobile browser. Wallet balance and token metadata checks do not verify bridge backing.
Bridge assets
1 WIN = 1 WINCEVERY STEP ACCOUNTED FOR
Bridge activity
Your transfers will appear here.
Track both chains, transaction references and recovery status.
UNDERSTAND THE TRUST
A transparent prototype.
The bridge design requires two of three independent bridge operators to authorize minting and native releases. The EVM does not directly verify Shardus transaction signatures.
Threshold trust. A compromised signing threshold can authorize false messages and steal backing. One compromised key cannot authorize a transfer alone; operator outages can delay completion.
Finality before action. Configured finality, independent observations and replay protection are required in each direction.
Test assets today. Public BSC Testnet access, independent security review and operational hardening are required before real funds. Local operators are controlled by one developer process, so they are not independent.