BNB ChainNo cross-network pricing
A single H100-hour varies severalfold between Nosana, io.net, Akash and Render at the very same moment. Nowhere to compare.
BNB Chain · Four.meme · GPU DePIN routing
Best-path routing
for GPU compute
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.
0DePIN networks indexed
0finality (Fermi)
0gas on BNB Chain
Route Engine
LIVE · real feed
ProviderPrice / NCU·hRep
Best path
—
—
Why it matters
Why best-path routing exists
The same GPU-hour costs 2–4× more on the wrong network — at the very same moment. Foursight makes that gap disappear.
Pick a GPU by hand and you either overpay — or land on a provider that stalls your job.
GPU compute is scattered across a dozen DePIN networks, each with its own pricing unit, availability and reliability. There's nowhere to compare like with like at the moment you actually need to rent.
Foursight indexes every network in real time, normalizes prices to one unit (NCU), and routes each job to the cheapest provider that can actually run it — held in escrow and settled trustlessly on BNB Chain.
- Live prices from Akash & Nosana public APIs, refreshed ~60s
- Real execution today on Nosana, io.net & Akash
- Non-custodial escrow · on-chain settlement · buyback & burn
Try it live
Run the route engine on real GPU supply
Opens the live Supply Index & route console below.
01 — Problem
A fragmented market, incomparable units
GPU power is scattered across dozens of networks. There's nowhere to compare price and reliability at the same moment.
Capacity ≠ delivery
Jobs fail, hang, come back late. There's no portable provider reputation to route around the bad ones.
Units aren't comparable
Every network prices its own way — per second, per job, per credit — across different GPU classes. Comparison is manual and error-prone.
Integration tax
Several networks means several accounts, SDKs and billing systems. An agent can't choose a provider at runtime.
02 — How it works
From job spec to burn — one flow
Indexing and execution stay off-chain. Only what must be trustless lives on-chain.
-
1
Request
A user or agent submits a spec: GPU class, VRAM, duration, region, latency tolerance, container, reliability threshold.
-
2
Index
Foursight reads the Supply Index: normalized price and availability across all networks plus on-chain provider reputation.
-
3
Route
The engine computes the cheapest path under all constraints, optionally splitting the batch across providers.
-
4
Escrow & launch
Funds enter an escrow contract on BNB Chain. A bonded keeper dispatches the job to the provider and monitors it.
-
5
Settle & burn
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.
03 — Architecture
Off-chain speed, on-chain trust
Escrow, settlement, reputation and slashing live in contracts. Indexing and routing are off-chain and deterministic.
Off-chain + snapshot
Supply Index
Network adapters normalize price and availability into a common unit; signed snapshots are posted on-chain for audit.
Off-chain · deterministic
Route Engine
Minimizes landed price over a weighted provider graph under hard constraints: class, region, latency, reliability.
Solidity
Escrow & settlement
Holds funds, pays on proof, takes the route fee, triggers $4SIGHT buyback-and-burn. Non-custodial.
Contract + reports
Reputation oracle
Writes per-provider outcomes; reputation feeds routing; failures and false proofs slash the bond.
Off-chain · $4SIGHT bond
Keeper network
Watch supply, submit routes, dispatch and monitor jobs, post completion proofs. Slashed for dishonesty.
04 — Supply Index · NCU
Live supply index
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 executes live (price estimated from the median). Render is coming soon. Reputation is a proxy here; in production it comes from the on-chain oracle.
Live compute jobs
on-chain escrow → Akash → settle
Indexed networks
Nosana
io.net
Akash
Render
Nosana
io.net
Akash
Render
05 — $4SIGHT token
The token gates route quality — it doesn't sit on top as a tax
Fair-launch BEP-20 on Four.meme: no presale, no team allocation, no vesting. Enters via a bonding curve and graduates into PancakeSwap liquidity.
Route priority stake
Staked $4SIGHT grants priority to scarce clusters in moments of contention. Holders benefit from network usage, not just token trading.
Network security bond
Keepers and providers bond $4SIGHT. False proofs, failures and downtime slash the bond and fund honest reputation.
Deflation buyback & burn
A share of every route fee buys back $4SIGHT on PancakeSwap and burns it. Supply falls from real volume, not treasury subsidy.
Governance DAO
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.
06 — Why BNB Chain
Micro-settlement only makes sense where the transaction is cheaper than the compute
Cheap gas ~0.05 Gwei
Per-job and per-second settlement only makes sense where the transaction is cheaper than the compute it closes.
~1.1s finality (Fermi)
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.
Four.meme
Fair-launch with no insider allocation and liquidity seeding on PancakeSwap at graduation — where buyback-and-burn also runs.
07 — Honest about risks
Not a single swept-under corner
Upstream dependency
Multi-provider redundancy and reputation routing: no single network is critical, split routing lowers concentration.
Token before utility
A read-only price aggregator, verifiable on-chain, works first. Utility switches on as contracts deploy; phases are labeled honestly.
Cross-chain settlement
The keeper takes on paying the provider and bridging. The user only touches BNB or USDT on BNB Chain.
Thin take-rate
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.
Token-as-tax
Staking gates route quality and bonds keepers — it's not rent. Remove the token and the reliability and security guarantees disappear.
09 — AI Assistant
Ask Foursight
The assistant knows the whole protocol: NCU, escrow, tokenomics, routing. Runs on a live model — ask anything.
Hey — I'm the Foursight Protocol assistant. Ask about NCU, the escrow flow, $4SIGHT, routing, or why BNB Chain, and I'll answer to the point.