Security model
This bridge is reserve-backed: it releases existing GLC from pre-funded reserves rather than creating new tokens. Understanding that distinction is the fastest way to understand what can and cannot go wrong.
Reserve-backed, not synthetic
The bridge never creates a synthetic derivative of GLC, and it never changes GLC's total supply on either network. A transfer works by verifying a deposit on the source network, then releasing existing GLC from the destination network's reserve. If a reserve does not have enough capacity, the transfer is refused rather than accepted.
What the frontend never does
- Request or store a private key.
- Perform a custody operation, or authorize a reserve release itself.
- Calculate an authoritative fee, quote, or settlement amount — the backend does.
- Bypass a reserve or pause check reported by the backend.
- Represent an unknown or failed transfer as successful.
What can go wrong
A direction can be paused, or a destination reserve can run out of available capacity — both are shown plainly on the bridge form and the status page. A transfer can also land in manual review, or fail outright; every state is visible on that transfer's detail page, with what it means for your funds and what to do next.