Operating principles

Current authority, not promised governance

The ecosystem operates through configured services and authorized administrators. The FTH$ network has a writer and validating replicas; it is not presented as decentralized consensus or a deployed Layer 3 rollup.

This page does not announce a DAO, token-weighted voting or an on-chain proposal system. Holding FTHG, FTH$ or FTHX does not by itself grant administrative permissions. Ethereum contract roles, native ledger authorities and CMS access are distinct.

Your approval controls your wallet

Public holdings and selected-account views update automatically. That does not authorize spending. Transfers, Thanks, trades, wallet linking and reserve obligations require their respective explicit approvals and signatures.

Embedded wallet views are read-only. Private keys, passwords and built-in signing sessions are never passed to parent sites. Keep an encrypted recovery backup and its password separately; the Foundation cannot recover a lost self-custody key.

Separate currency and settlement responsibilities

• Gold: Ethereum access, FTHG and supported native ETH reads, reserve evidence and Ethereum-related operations.
• Notes: native FTH chain operations, FTH$ and community-note accounting. Dollar API compatibility routes use the same underlying ledger.
• Exchange: actual ledger-based trading and liquidity using existing funds. Trading holdings remain separate from main-wallet spending.
• World: gameplay and separate gameplay funds. Deposits and withdrawals move existing balances; a public balance view is not transfer authority.

New bridge-credit and staking-reward issuance of FTH$ is closed. Initial pool funding requires approval and authorized existing balances. Unfunded markets are not advertised with invented liquidity, volume or executable prices.

The Ethereum reserve exception

FTHG origin and backing wallets are pinned reserve authorities. Actual Ethereum settlement remains manual and explicitly authorized; no background wallet refresh sends Ethereum tokens or spends gas.

Gold reconciliation requires a fresh signature from the authorized origin or backing wallet, bound to the ledger genesis, transaction hash, transfer-log index and timestamp. The service verifies a finalized, canonical FTHG transfer between those wallets and deduplicates receipts.

Pending allocations, signed off-chain obligations, previews and confirmed Ethereum receipts are different states. A screenshot or preview is not proof of settlement. FTH$ is not a US-dollar redemption claim, and FTHG is not a claim on physical gold.

Protected administration and publication

Admin at admin.featheral.com provides protected CMS, site, note and product operations. It is described here for completeness, not exposed as a public administration control. The retired CMS host redirects to Admin.

Content edits use revisions. Deployment is reviewed separately from editing; changing a local page does not prove a public release was deployed. Site owners manage their assigned websites, not the whole ecosystem. Exact shipped defaults can receive content refreshes without overwriting custom CMS edits.

Ethereum token safety changes still require the appropriate deployed contract role, Mainnet checks and wallet approval. CMS authorization does not replace an on-chain role or a reserve wallet signature.

Privacy and transparent reporting

Stats uses aggregate traffic reporting where enabled. Site feature settings, origin checks and browser privacy signals constrain telemetry. Public account summaries expose holdings, not private site requests or credentials.

Unavailable network reads and missing prices are reported explicitly. Portfolio totals are estimates rather than guaranteed quotes, and linked, trading and gameplay holdings do not become a single spendable balance.

No financial promises

The sites do not promise returns, automatic rewards, US-dollar redemption, leverage or guaranteed liquidity. Review the asset, network, recipient, amount and fees before approving any action. Use the ecosystem guide to find the correct site and workflow.