Phase 1 โ€” Requester side on testnet

Buy Compute.
Pay for Work That Verifies.

The station is where a job gets created: pick a hardware tier, choose how hard the result is checked, see every part of the price, and escrow it on chain. If the job fails, the requester is made whole out of the provider's stake โ€” not out of somebody else's escrow.

BNB Smart Chain Testnet ยท Chain 97 tOMC has no monetary value
Testnet only. Jobs settle in tOMC on BNB Smart Chain Testnet. tOMC and tBNB are worthless and are sold nowhere. The GPU actually runs off chain; the contract holds the escrow, the assignment record and the verdict. Never send real funds to these addresses.
Not connected โ€”
Quotes and the tier ladder work without a wallet. Escrowing a job needs one.
tOMC balance
0
Wallet, spendable on jobs
Providers registered
โ€”
Staked nodes the scheduler can pick
Total staked behind them
โ€”
The bond a failed job is paid from
Settled volume
โ€”
โ€” jobs settled

1 ยท Configure the job

The tier is the hardware class you need. Every tier minimum is read live from the staking contract, so this page and the staking page can never disagree.

A tier is a class of machine, not a promise about a specific GPU. The scheduler picks an eligible node inside the class.
Describe the container, the resources and the region. Only a hash of this text goes on chain โ€” the description stays in your browser.
This is the single biggest lever on price. Redundancy costs two to three times as much because the job really does run two to three times.
There is no published price list yet. You type the ceiling rate you are willing to pay; the contract can never settle above it. The benchmark against hyperscalers and other networks is published after mainnet.
Missing the deadline is a 2% penalty on the provider's stake. You still get the escrow back, plus your share of the penalty.
Claim test tOMC right here: once a day, five per address, 20 tOMC each.
Approval is written for exactly the ceiling of the job you just configured โ€” never an unlimited allowance.
Fill in a rate and hours to see the price breakdown.

Who stands behind the job

Read straight from the two contracts. No wallet needed.

1
Stake is the right to be assigned

The scheduler may only pick a provider whose node is registered, in good standing, and staked at or above the job's tier minimum. The ladder is read from the staking contract at assignment time โ€” it cannot be argued with.

2
Stake is what pays you when the job fails

Timeout 2%, offline 5%, bad output 30%, proven fraud 100% of that provider's stake. Half of whatever is slashed goes to the requester whose job failed, 30% to the treasury, 20% is burned.

3
Stake is not an investment product

Staking OMC is a security deposit, not a yield. There is no advertised rate here and there will not be one: what a node earns depends on work it actually delivers.

Staking a GPU instead? That side lives on the staking page. โ†’

Tier ladder

The same five tiers priced on the staking page, read live from the contract.

TierHardwareMinimum stake

Market

Counters for the requester side, live.

Jobs createdโ€”
Jobs settledโ€”
Fees burnedโ€”
Reward pool leftโ€”
Slashed so farโ€”
Every settled job pays a 3% protocol fee: 30% of the fee is bought back and burned, 70% goes to the reputation reward pool. The burn is 0.9% of settled volume.
tOMC (test token) 0xBEB21E40FB50A0F4ba9287C2058DC7851e450671
OMCStaking 0x3226dffED51e28CEf526F8c078B2EC9a092E36e6
OMCComputeMarket 0x3B81E6edfbA775B4E53694F531C3b0236D77FEF1
Lifecycle

What happens after you click escrow

The same eight steps the whitepaper describes from the requester's side, with the part each contract plays marked.

1Submit

Container image, resources, region, ceiling price, verification policy and protection level.

2Escrow

The ceiling is locked in OMCComputeMarket. It can never be charged more than this.

3Filter

Nodes that miss the VRAM, driver, region, TEE, stake or reputation bar are dropped.

4Score

Survivors are ranked on TFLOPS, VRAM, bandwidth, latency and reputation, weighted per job class.

5Assign

A provider is drawn from the top-k and recorded on chain โ€” the eligibility check runs in that transaction.

6Execute

The node pulls the image, gets the keys after assignment, runs the job and returns an attestation.

7Verify

Spot-check, redundancy or TEE attestation decides whether the output is accepted.

8Settle

Pass: the provider is paid, the fee splits, reputation updates. Fail: bond slashed, requester refunded.

The part that is honest. The GPU runs off chain and the scheduler is a trusted role during the testnet, exactly as the verifier is on the staking contract. What is enforced on chain is the escrow, the eligibility filter, the settlement and the penalty. Disputes open for 48 hours after delivery; the protocol first re-executes the job on an independent node before anything escalates.
Pricing

How the price is built โ€” and what we will not claim

๐Ÿงฎ

Structure, not a rate card

GPU-hours ร— reference rate ร— verification multiplier, plus a 3% protocol fee, minus 10% of that fee when you pay in OMC. You set the ceiling; the contract refuses to settle above it.

๐Ÿ”

Verification is the price lever

Spot-check adds the audit rate on top. Full redundancy costs 2โ€“3ร— because the work is done 2โ€“3 times. TEE carries a premium and needs TEE-capable nodes to be online.

๐Ÿ“‰

The target, stated plainly

OMC targets below the median of the centralized GPU marketplaces. Hyperscalers ran $6.88โ€“$12.29 per H100 SXM GPU-hour, marketplaces $2.49โ€“$6.16, other decentralized networks $1.25โ€“$3.00. The measured OMC benchmark is published after mainnet.

No number on this page is a quote. The station shows the arithmetic and the target; it does not publish a price. Any figure you enter is your own ceiling. Treat every output of the box above as indicative โ€” it is a way to see where the money goes, not an offer.