LibraryStorage and networks2024Design paperCorpus record
io.net: a network of GPU suppliers
io.net. io.net.
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 2
01 Claim ledger
What the paper is allowed to say
Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.
Claim 01 · Paper model
The defect
Aggregated GPUs are a supply listing until a verification rule exists. Read the docs for the rule before calling it a depin proof.
Claim 02 · Paper model
The proposal
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
Claim 03 · Paper model
The mechanism
A supplier registers capacity. A customer schedules a workload. Payment follows the metering the docs describe.
Claim 04 · Paper model
The bound
No capacity figure is stated here.
02 Three cuts
Observation, model, falsifier
A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.
01 The defect
Observation
What the study says
Aggregated GPUs are a supply listing until a verification rule exists. Read the docs for the rule before calling it a depin proof.
Model
What has to hold
You are reading io.net's docs. A hardware photo is not a proof.
Falsifier
What would retire it
What must a supplier show to be paid?
02 The proposal
Observation
What the study says
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
Model
What has to hold
The document is the one at the source URL. A marketing page with the same brand is not this text.
Falsifier
What would retire it
Who schedules the job?
03 The mechanism
Observation
What the study says
A supplier registers capacity. A customer schedules a workload. Payment follows the metering the docs describe.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What must a supplier show to be paid?
04 The bound
Observation
What the study says
No capacity figure is stated here.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What must a supplier show to be paid?
03 Sequence
One action, as an operating tape
- 01A supplier registers capacity. A customer schedules a workload. Payment follows the metering the docs describe.
- 02Verification, if it is a heartbeat or a challenge, is the security. If the docs only meter hours, the product is metered rental.
- 03A coordinator that schedules jobs is a liveness and censorship point.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
What actually moves
The cut
Verification, if it is a heartbeat or a challenge, is the security. If the docs only meter hours, the product is metered rental.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
This note does not say the verification is cryptographic unless the page you opened says so.
What a later deployment may change
The cut
A coordinator that schedules jobs is a liveness and censorship point.
Why it carries weight
If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.
Where it is dropped
A later client, parameter or reward formula is a different object from this paragraph.
05 Register
What has to be true
Cryptography · Not re-measured
You are reading io.net's docs. A hardware photo is not a proof.
Model · Not re-measured
The document is the one at the source URL. A marketing page with the same brand is not this text.
Model · Not re-measured
No price, supply, yield, or adoption figure is added by this desk.
06 Divergence
What happened after the paper
This is not Akash's lease document and not a zkML proof.
A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.
07 Pre-mortem
What to check before you use the idea
- 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.
08 Anatomy
The paper, in the order a builder needs
The problem it names
Aggregated GPUs are a supply listing until a verification rule exists. Read the docs for the rule before calling it a depin proof.
What the design proposes
- A supplier registers capacity. A customer schedules a workload. Payment follows the metering the docs describe.
- Verification, if it is a heartbeat or a challenge, is the security. If the docs only meter hours, the product is metered rental.
- A coordinator that schedules jobs is a liveness and censorship point.
How the mechanism is specified
- A supplier registers capacity. A customer schedules a workload. Payment follows the metering the docs describe.
- Verification, if it is a heartbeat or a challenge, is the security. If the docs only meter hours, the product is metered rental.
- A coordinator that schedules jobs is a liveness and censorship point.
What this page does not treat as proven
- No capacity figure is stated here.
- This note does not say the verification is cryptographic unless the page you opened says so.
- This is not Akash's lease document and not a zkML proof.
Why the desk still reads it
io.net publishes a network that aggregates GPU suppliers for compute jobs. The design question is who checks that a GPU did the work.
09 Lexicon
Terms, opened into the record
- Metered rental
- Payment for time or usage without a proof of correct execution.
- Challenge
- A check that the supplier did the declared work, if the docs include one.
10 Repository
Every linked record on this page
Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.
Concepts
Papers
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.