Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryData and agents2022Design paperCorpus record

RedStone: modular price delivery

RedStone. RedStone.

RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
1

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.

  1. Claim 01 · Paper model

    The defect

    Modular delivery does not remove the signer. It changes when the bytes arrive.

  2. Claim 02 · Paper model

    The proposal

    RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.

  3. Claim 03 · Paper model

    The mechanism

    The payload is signed off chain and verified on chain. Verification of the signature is the contract's job. A missing check is not this design.

  4. Claim 04 · Paper model

    The bound

    No feed count and no deviation threshold is copied 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.

  1. 01 The defect

    Observation

    What the study says

    Modular delivery does not remove the signer. It changes when the bytes arrive.

    Model

    What has to hold

    You are reading RedStone's docs, not a consumer's integration tutorial.

    Falsifier

    What would retire it

    Who can add a signer?

  2. 02 The proposal

    Observation

    What the study says

    RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.

    Model

    What has to hold

    You are reading RedStone's docs, not a consumer's integration tutorial.

    Falsifier

    What would retire it

    Does the consumer check the timestamp?

  3. 03 The mechanism

    Observation

    What the study says

    The payload is signed off chain and verified on chain. Verification of the signature is the contract's job. A missing check is not this design.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    Which addresses must sign the payload?

  4. 04 The bound

    Observation

    What the study says

    No feed count and no deviation threshold is copied here.

    Model

    What has to hold

    You are reading RedStone's docs, not a consumer's integration tutorial.

    Falsifier

    What would retire it

    Which addresses must sign the payload?

03 Sequence

One action, as an operating tape

  1. 01The payload is signed off chain and verified on chain. Verification of the signature is the contract's job. A missing check is not this design.
  2. 02The data provider set is the trust assumption. Rotation of that set is a governance event.
  3. 03A push model and a pull model fail differently. The docs you cite have to say which one the consumer uses.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.

    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

    An unsigned HTTPS price is not RedStone.

  2. What actually moves

    The cut

    The data provider set is the trust assumption. Rotation of that set is a governance event.

    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.

  3. What a later deployment may change

    The cut

    A push model and a pull model fail differently. The docs you cite have to say which one the consumer uses.

    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 is not an audit of any consumer protocol.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading RedStone's docs, not a consumer's integration tutorial.

  • 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 note is not an audit of any consumer protocol.

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

  4. 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

Modular delivery does not remove the signer. It changes when the bytes arrive.

What the design proposes

  • The payload is signed off chain and verified on chain. Verification of the signature is the contract's job. A missing check is not this design.
  • The data provider set is the trust assumption. Rotation of that set is a governance event.
  • A push model and a pull model fail differently. The docs you cite have to say which one the consumer uses.

How the mechanism is specified

  • The payload is signed off chain and verified on chain. Verification of the signature is the contract's job. A missing check is not this design.
  • The data provider set is the trust assumption. Rotation of that set is a governance event.
  • A push model and a pull model fail differently. The docs you cite have to say which one the consumer uses.

What this page does not treat as proven

  • No feed count and no deviation threshold is copied here.
  • An unsigned HTTPS price is not RedStone.
  • This note is not an audit of any consumer protocol.

Why the desk still reads it

RedStone publishes a modular oracle: signed data can be pushed on demand or stored for a contract to pull, rather than one contract updated on a fixed heartbeat only.

09 Lexicon

Terms, opened into the record

Signed payload
Price bytes with signatures a contract can verify.
Pull delivery
The user brings the signed bytes in the transaction that needs them.

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

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.