LibraryStorage and networks2018Design paperCorpus record
Akash: a marketplace for compute leases
Akash. Akash.
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 0
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
A compute marketplace that does not check the provider ran the binary is a rental listing. Do not describe it as a proof of computation unless the docs contain the proof.
Claim 02 · Paper model
The proposal
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
Claim 03 · Paper model
The mechanism
A tenant describes a deployment. Providers bid. A lease is the matched contract.
Claim 04 · Paper model
The bound
No price and no provider count 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
A compute marketplace that does not check the provider ran the binary is a rental listing. Do not describe it as a proof of computation unless the docs contain the proof.
Model
What has to hold
You are reading Akash's docs. A GPU listing is not a proof marketplace.
Falsifier
What would retire it
What does a provider have to prove to get paid?
02 The proposal
Observation
What the study says
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
Model
What has to hold
You are reading Akash's docs. A GPU listing is not a proof marketplace.
Falsifier
What would retire it
Who can terminate a lease?
03 The mechanism
Observation
What the study says
A tenant describes a deployment. Providers bid. A lease is the matched contract.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
Who can terminate a lease?
04 The bound
Observation
What the study says
No price and no provider count 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 does a provider have to prove to get paid?
03 Sequence
One action, as an operating tape
- 01A tenant describes a deployment. Providers bid. A lease is the matched contract.
- 02Payment follows the lease terms. It does not, by itself, prove the provider executed the declared image.
- 03A reverse proxy or gateway in front of the deployment is a liveness component. It can also be a censorship point.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
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 provider can halt a lease. The tenant's recourse is whatever the docs specify, which may be economic rather than cryptographic.
What actually moves
The cut
Payment follows the lease terms. It does not, by itself, prove the provider executed the declared image.
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 provider can halt a lease. The tenant's recourse is whatever the docs specify, which may be economic rather than cryptographic.
What a later deployment may change
The cut
A reverse proxy or gateway in front of the deployment is a liveness component. It can also be a 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 Akash's docs. A GPU listing is not a proof marketplace.
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
A provider can halt a lease. The tenant's recourse is whatever the docs specify, which may be economic rather than cryptographic.
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
A compute marketplace that does not check the provider ran the binary is a rental listing. Do not describe it as a proof of computation unless the docs contain the proof.
What the design proposes
- A tenant describes a deployment. Providers bid. A lease is the matched contract.
- Payment follows the lease terms. It does not, by itself, prove the provider executed the declared image.
- A reverse proxy or gateway in front of the deployment is a liveness component. It can also be a censorship point.
How the mechanism is specified
- A tenant describes a deployment. Providers bid. A lease is the matched contract.
- Payment follows the lease terms. It does not, by itself, prove the provider executed the declared image.
- A reverse proxy or gateway in front of the deployment is a liveness component. It can also be a censorship point.
What this page does not treat as proven
- No price and no provider count is stated here.
- This is not a zkVM. There is no proof of correct execution in the base marketplace.
- A provider can halt a lease. The tenant's recourse is whatever the docs specify, which may be economic rather than cryptographic.
Why the desk still reads it
Akash publishes a marketplace where providers bid on deployment leases and a tenant pays for compute. The lease is the product. Verification of the workload is a separate, harder claim.
09 Lexicon
Terms, opened into the record
- Lease
- A matched bid between a tenant and a provider.
- Deployment
- The tenant's requested workload. It is not evidence the workload ran.
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.
No repository match in this text.
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.