Purchase a server-enforced ForgeMiner identity for 500 test-network SFD, then register for proof work; the receipt is not live-chain settlement.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
Purchasing a ForgeMiner identity deducts 500 test-network SFD and creates a Tier-3 application record for the authorizing wallet. The SFD debit, identity row, and deterministic chunk assignments are recorded atomically in PostgreSQL. The returned identifier is an application receipt, not a chain transaction.
A Tier-3 ForgeMiner application identity unlocks validator registration, scheduled proof challenges, and application-ledger rewards. Higher tiers use server-enforced ascension and may change configured obligations and reward multipliers. None of these records establish live-contract ownership, independent custody, or physical mining hardware.
Each ForgeMiner record is assigned 1,024 deterministic application chunks committed by a Poseidon Merkle root. Scheduled challenges require a matching witness and client-generated proof within the runtime deadline. This exercises proof verification but does not attest physical capacity, a proof pod, or chain settlement.