Platform Overview (Protocol Design)

Goldie City is a protocol for launching and operating precious-metal token ecosystems with institutional-grade controls.

Instead of deploying an ERC-20 token in isolation, the protocol deploys a consistent ecosystem per token and enforces critical rules on-chain:

• Governance & role boundaries (who can do what)
• Compliance enforcement (issuance/transfer gating where configured)
• Pricing integrity (oracle inputs with staleness protections)
• Proof publishing (auditable records with validity semantics)
• Redemption auditability (on-chain lifecycle and escrow patterns)

This documentation describes the protocol design and how the pieces fit together.

What is enforced on-chain vs off-chain

Goldie City uses a strict separation between enforcement and operations:

• On-chain enforcement: balances, transfers, privileged actions (roles), compliance gating, pricing calculations (where implemented), proof records, redemption state.
• Off-chain operations: KYC/KYB decisioning and document handling, custody and audits, fulfillment/logistics, monitoring and incident response.

The protocol is designed so that the most important integrity properties are non-bypassable: if a rule is configured to be enforced (e.g., compliance gating), it is enforced by contract logic.

Actors

• Platform operator: governs shared protocol controls and upgrades.
• Issuer: launches and operates a specific token ecosystem.
• Participants: hold, transfer, and redeem tokens subject to configured policy.

In many deployments, participants are provisioned a non-custodial wallet during onboarding so they can sign transactions with minimal friction while still retaining control of the account.

Why factory-based ecosystems

Institutions care about predictability: audits, diligence, integrations, and monitoring are easier when every token ecosystem follows the same blueprint. The protocol’s factory pattern creates repeatable deployments and a consistent “where is X?” map across tokens.

Key properties (what external parties can verify)

• Role grants/revokes and privileged actions are recorded on-chain.
• Transfer/issuance enforcement is executed on-chain.
• Oracle usage and staleness checks are observable via state and behavior.
• Proof publication cadence and latest-proof state is observable.
• Redemption lifecycle is recorded as state transitions and events.

For more on wallet types (MPC, smart wallets, gas sponsorship, and multisig), see /docs/wallet-and-signing-ux.