Bridge
The planned 1:1 path from the supported source token to native GOD, with explicit activation gates.
No real-asset bridge is open.
The public testnet uses synthetic balances with no monetary value. Its faucet is not a bridge, and its balances do not have a guaranteed mainnet conversion. No approval request, deposit address or signing form is provided here.
One backing supply. A 1:1 representation.
The design fixes GOD's economic supply at 1,000,000,000. The supported source token is intended to be locked in reviewed custody before the corresponding amount becomes usable on GOD Chain. This is a 1:1 representation of backing, not another independently spendable billion coins.
- Source to GOD: a reviewed source deposit is observed, its canonical state and finality are independently verified, and an authorized non-replayed credit releases the matched native amount.
- Use on GOD Chain: native GOD pays Gas and supports eligible staking. An address-format conversion does not move funds.
- Return to the source: native withdrawal accounting reserves the amount, and the reviewed source release is separately confirmed before completion. Pending, failed or delayed outcomes require reconciliation; never assume that both sides completed.
Source-network fees and GOD Chain Gas are separate. Costs, approved limits, custody identity and signing controls must be displayed by a future activated interface before a user signs.
What activation must establish.
- Authenticated original source, an exact compiled runtime match and review of mint, admin, proxy, upgrade, pause and transfer restrictions.
- A supported source network, reliable historical state and independently verified finality; a provider's finalized label alone is not sufficient.
- Reviewed custody and code bindings, signer/upgrade control, replay protection, limits and backing conservation.
- Recoverable deposit and withdrawal processing, delayed outcomes, emergency pause and restart/recovery evidence.
- Backed initial native funding, approved economics and a pinned release/configuration with explicit activation authorization.
Local source-recompilation tools and simulated bridge tests are available development evidence. They do not by themselves approve the real token, deploy custody, authenticate a provider or enable real assets.
Follow verified bridge status.
Until these gates are satisfied, use the synthetic testnet only. A future release must publish its supported source identity, complete terms, reviewed custody and current readiness; it must not silently reuse an old or unconfigured address.