LibraryData and agents2021Design paperCorpus record
Pyth: first-party signed prices aggregated on a chain
Pyth Network. Pyth Data Association.
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
- 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
A price with many publishers is still not the world's price. It is the price those publishers signed.
Claim 02 · Paper model
The proposal
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
Claim 03 · Paper model
The mechanism
Publishers sign a price and a confidence interval. The aggregate is a function of those signatures, as the docs define the function.
Claim 04 · Paper model
The bound
No publisher count and no accuracy 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
A price with many publishers is still not the world's price. It is the price those publishers signed.
Model
What has to hold
You are reading Pyth's docs. A dashboard price is not the signed payload.
Falsifier
What would retire it
How old may an update be and still be accepted?
02 The proposal
Observation
What the study says
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
Model
What has to hold
You are reading Pyth's docs. A dashboard price is not the signed payload.
Falsifier
What would retire it
What does a contract verify: a signature threshold, or a single updater?
03 The mechanism
Observation
What the study says
Publishers sign a price and a confidence interval. The aggregate is a function of those signatures, as the docs define the function.
Model
What has to hold
You are reading Pyth's docs. A dashboard price is not the signed payload.
Falsifier
What would retire it
How old may an update be and still be accepted?
04 The bound
Observation
What the study says
No publisher count and no accuracy 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
Who is allowed to publish on the feed you cite?
03 Sequence
One action, as an operating tape
- 01Publishers sign a price and a confidence interval. The aggregate is a function of those signatures, as the docs define the function.
- 02A consumer contract that reads Pyth has chosen that aggregate as an input. The contract's liquidation rule is a separate design.
- 03Pull delivery, where the user posts the update, means freshness is whoever paid to push the bytes.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
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
A consumer contract that reads Pyth has chosen that aggregate as an input. The contract's liquidation rule is a separate design.
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 a later deployment may change
The cut
Pull delivery, where the user posts the update, means freshness is whoever paid to push the bytes.
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
Model · Not re-measured
You are reading Pyth's docs. A dashboard price is not the signed payload.
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 Chainlink's 2017 white paper.
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 price with many publishers is still not the world's price. It is the price those publishers signed.
What the design proposes
- Publishers sign a price and a confidence interval. The aggregate is a function of those signatures, as the docs define the function.
- A consumer contract that reads Pyth has chosen that aggregate as an input. The contract's liquidation rule is a separate design.
- Pull delivery, where the user posts the update, means freshness is whoever paid to push the bytes.
How the mechanism is specified
- Publishers sign a price and a confidence interval. The aggregate is a function of those signatures, as the docs define the function.
- A consumer contract that reads Pyth has chosen that aggregate as an input. The contract's liquidation rule is a separate design.
- Pull delivery, where the user posts the update, means freshness is whoever paid to push the bytes.
What this page does not treat as proven
- No publisher count and no accuracy figure is stated here.
- A confidence interval is not a promise of future execution quality.
- This is not Chainlink's 2017 white paper.
Why the desk still reads it
Pyth publishes prices signed by first-party publishers and aggregated into a feed a contract can read. The signature set is the oracle assumption.
09 Lexicon
Terms, opened into the record
- Publisher
- A named party who signs a price. The feed is only their signatures.
- Confidence interval
- A width the publishers attach. It is not a liquidation rule until a consumer uses it as 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.
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.