Customers escrow payment for compute jobs. Providers run them in sealed containers and get paid on approval. The platform fee buys tokenised stock, and every holder staking SFG takes a share of it.
Live · read from chainEvery figure here is a contract read or an exchange quote, fetched when the page loaded.
Three stages run between a customer's wallet and a staker's. Each one writes something you can go and read afterwards.
They attach files and a container image. The ETH locks in JobMarket the moment the job is posted, and the provider cannot touch it until the customer approves the result or the confirm window lapses.
Providers lock SFG as collateral first. Their agent claims the job and runs it in a Docker container with no network, /input mounted read-only and /output collected, then anchors a hash of everything it produced.
On approval the provider is paid and the platform fee lands in the Treasury. The treasury buys tokenised equities with it and credits every staker pro rata. There is no issuance anywhere in the path.
Each reward asset is a tokenised stock listed on Robinhood Chain. The quote is that token's own, read from the chain's explorer. The weight is the share of treasury value it represents right now.
| Symbol | Reward asset | Reference | Price | In treasury | Weight |
|---|---|---|---|---|---|
| loading assets | |||||
No price history is shown because none is stored. A 24 h column would be invented.
Six claims. Next to each one, the thing you can do yourself to find out whether it holds.
Escrow, settlement and distribution are on-chain transactions. Execution is the single off-chain hop, and it is bracketed by a hash on the way in and a hash on the way out.
One command checks Docker, registers your node, posts collateral and starts taking jobs.
PROVIDER_PRIVATE_KEY=0x… npm run joinProvide compute