No cross-network pricing
A single H100-hour varies severalfold between Nosana, io.net, Akash, Render and Aethir at the very same moment. Nowhere to compare.
Foursight indexes live supply, price and reliability across GPU DePIN networks and routes every job to the cheapest provider that can actually run it. Settlement in BNB or USDT, the $4SIGHT token fair-launched on Four.meme.
GPU power is scattered across dozens of networks. There's nowhere to compare price and reliability at the same moment.
A single H100-hour varies severalfold between Nosana, io.net, Akash, Render and Aethir at the very same moment. Nowhere to compare.
Jobs fail, hang, come back late. There's no portable provider reputation to route around the bad ones.
Every network prices its own way — per second, per job, per credit — across different GPU classes. Comparison is manual and error-prone.
Several networks means several accounts, SDKs and billing systems. An agent can't choose a provider at runtime.
Indexing and execution stay off-chain. Only what must be trustless lives on-chain.
A user or agent submits a spec: GPU class, VRAM, duration, region, latency tolerance, container, reliability threshold.
Foursight reads the Supply Index: normalized price and availability across all networks plus on-chain provider reputation.
The engine computes the cheapest path under all constraints, optionally splitting the batch across providers.
Funds enter an escrow contract on BNB Chain. A bonded keeper dispatches the job to the provider and monitors it.
On a signed completion proof, escrow pays the provider and the keeper, takes a route fee, and part of the fee buys back and burns $4SIGHT.
Escrow, settlement, reputation and slashing live in contracts. Indexing and routing are off-chain and deterministic.
Network adapters normalize price and availability into a common unit; signed snapshots are posted on-chain for audit.
Minimizes landed price over a weighted provider graph under hard constraints: class, region, latency, reliability.
Holds funds, pays on proof, takes the route fee, triggers $4SIGHT buyback-and-burn. Non-custodial.
Writes per-provider outcomes; reputation feeds routing; failures and false proofs slash the bond.
Watch supply, submit routes, dispatch and monitor jobs, post completion proofs. Slashed for dishonesty.
Each provider's native price maps to a price-per-NCU (Normalized Compute Unit) — a GPU-second normalized by class via FP16 throughput and VRAM tier. The engine compares like with like.
| Network | Native | Price / NCU·h | Available | Rep | Status |
|---|
Live data: Akash & Nosana public APIs, normalized to a common NCU price (refreshed ~60s). io.net, Render and Aethir have no public price feed — shown as est from the live median. Reputation is a proxy here; in production it comes from the on-chain oracle.
Nosana
io.net
Render
Aethir
Fair-launch BEP-20 on Four.meme: no presale, no team allocation, no vesting. Enters via a bonding curve and graduates into PancakeSwap liquidity.
Staked $4SIGHT grants priority to scarce clusters in moments of contention. Holders benefit from network usage, not just token trading.
Keepers and providers bond $4SIGHT. False proofs, failures and downtime slash the bond and fund honest reputation.
A share of every route fee buys back $4SIGHT on PancakeSwap and burns it. Supply falls from real volume, not treasury subsidy.
Vote on network integrations, fee parameters, NCU weights, slashing thresholds. On-chain DAO as contracts ship.
NCU is an internal unit of account and routing, not a peg. $4SIGHT is never pegged to a fixed amount of compute. This removes the death-spiral risk of a hard peg on volatile, heterogeneous hardware.
Per-job and per-second settlement only makes sense where the transaction is cheaper than the compute it closes.
0.45s blocks after Lorentz, Maxwell and Fermi. Escrow release and incremental billing close to real time — the user stops paying the moment a job stalls.
Fair-launch with no insider allocation and liquidity seeding on PancakeSwap at graduation — where buyback-and-burn also runs.
Multi-provider redundancy and reputation routing: no single network is critical, split routing lowers concentration.
A read-only price aggregator, verifiable on-chain, works first. Utility switches on as contracts deploy; phases are labeled honestly.
The keeper takes on paying the provider and bridging. The user only touches BNB or USDT on BNB Chain.
Competition on the reliability layer, not just price. The goal: become the default route endpoint inside agent frameworks, where the switching cost is the SDK, not the fee.
Staking gates route quality and bonds keepers — it's not rent. Remove the token and the reliability and security guarantees disappear.
The token is a fair-launch, so it lives from day one. Every claim is honest at its stage.
Price index across 3–4 networks. Proves supply data is real and comparable before asking anything of the user.
Fair-launch on Four.meme · governance signalingSingle route, signed completion proofs, non-custodial escrow on BNB Chain.
Buyback-and-burn from route feesPriority staking, keeper bonds, reputation oracle, slashing.
Priority staking · keeper & provider bondingSplit routing, verifiable-compute tier (TEE/ZK attestations), agent SDK, on-chain DAO.
Full on-chain DAOThe assistant knows the whole protocol: NCU, escrow, tokenomics, roadmap. Runs on a live model — ask anything.