Bridge to Fuji

Egress policy for KHRt

Every riel that leaves CSB passes through one contract — the EgressGateway. It is the only exit, and these are the conditions it enforces. Nothing here is enforced by the bridge itself; the bridge only carries what the gateway has already approved.

This is a one-way door to the public world. Balances on Fuji are visible to anyone, forever, in any block explorer. Inside CSB a payment is visible only to the parties and the state; once it crosses, it is visible to everyone. That is the point of the gateway, and the reason it is governed rather than open.

Send KHRt out

Destination chain Recipient on the destination chain Amount (KHRt)

Two transactions: an approval, then the egress request. Gas is about 1 riel each.

Your eligibility

Checking your wallet…

What happens next. The gateway takes your KHRt and hands it to the bridge adapter, which locks it in the TokenHome on CSB and emits a cross-chain message. A relayer delivers that message to Fuji, where the equivalent bridged token is minted to your recipient. If no relayer is running, the value is locked and safe but does not appear — it is not lost, only undelivered.

Bring tokens back (Fuji → CSB)

The token on Fuji is not KHRt — it is a bridged token minted when your KHRt was locked here. Sending it back burns it on Fuji and releases the original KHRt on CSB. This runs on the Fuji C-Chain, so your wallet will be asked to switch networks and then switch back.

Recipient on CSB Amount

Checking the bridge…

The recipient must be KYC-active on CSB. KHRt enforces compliance on every transfer, and releasing the collateral is a transfer — so an unverified recipient means the Fuji burn succeeds and the CSB delivery reverts. Nothing is lost, but the failure lands on the other chain from the one you sent on. This checks before burning.

Recent crossings

Block	From	Amount	Recipient