Skip to content

Research corpusConsensusBLC-PDF-0002

The Ripple Protocol Consensus Algorithm

The library holds the Ripple consensus paper: agreement among servers that choose which other servers they listen to, rather than a race to spend hash power.

  • Rights uncertain
  • Design paper
  • Historic library path, plus a commonly cited publisher URL
Compare

Record

Authors
David Schwartz, Noah Youngs, and Arthur Britto
Date
2014, as commonly cited for this title. Not re-read from the file bytes in this build.
Publisher
Ripple
Version
Historic library file. Not byte-compared with the publisher URL.
Document ID
BLC-PDF-0002
DOI
None recorded
Last reviewed
1 October 2026
Licence
No licence recorded. Rights status under review.

No hash is published. This build does not store those PDF bytes, so a checksum would be invented. Where a legacy path exists, it points at the Internet Archive copy of the old library.

Direct answer

The library holds the Ripple consensus paper: agreement among servers that choose which other servers they listen to, rather than a race to spend hash power.

Authors follow the library note (Schwartz, Youngs, Britto) in the usual full names of that paper. The bytes were not re-opened for this record.

Why it is in the corpus

  • It is a different answer to ordering transactions: a unique node list, not open work.

Where to read

Legacy path remains. Full text is not republished.

Full text

Full text is not published on this page. Public availability is not a licence to republish a document. Blockchain Lab has not recorded a licence that permits an HTML transcription, a training set, or a retrieval corpus of the paper. Text on this page is Blockchain Lab's own wording, or a pointer to a study that is also Blockchain Lab's wording.

Claims and assumptions

Blockchain Lab's reading of what the document is doing. Not a quotation and not the source text.

  • Servers iterate toward a common set of transactions with the servers they are configured to heed.

Assumptions

  • The overlap of those lists is the safety assumption. The paper does not make every server equal.

What changed

The live XRP Ledger software is a later system. This record is the historic paper.

Relationships

Cite this record

These citations point at the source document. They are not a licence to copy it.

Author–date

Schwartz, D., Youngs, N., & Britto, A. (2014). The Ripple Protocol Consensus Algorithm. Ripple. https://ripple.com/files/ripple_consensus_whitepaper.pdf

BibTeX

@techreport{rippleconsensus2014,
  title = {The Ripple Protocol Consensus Algorithm},
  author = {David Schwartz, Noah Youngs, and Arthur Britto},
  year = {2014},
  institution = {Ripple},
  url = {https://ripple.com/files/ripple_consensus_whitepaper.pdf},
  note = {Rights status: Rights uncertain. Blockchain Lab record: https://blockchainlab.com/research/corpus/papers/ripple-consensus}
}

RIS

TY  - RPRT
TI  - The Ripple Protocol Consensus Algorithm
AU  - David Schwartz
AU  - Noah Youngs
AU  - Arthur Britto
PY  - 2014
PB  - Ripple
UR  - https://ripple.com/files/ripple_consensus_whitepaper.pdf
N1  - Rights status: Rights uncertain
ER  -

CSL-JSON

[
  {
    "type": "report",
    "id": "BLC-PDF-0002",
    "title": "The Ripple Protocol Consensus Algorithm",
    "author": [
      {
        "literal": "David Schwartz"
      },
      {
        "literal": "Noah Youngs"
      },
      {
        "literal": "Arthur Britto"
      }
    ],
    "issued": {
      "date-parts": [
        [
          2014
        ]
      ]
    },
    "publisher": "Ripple",
    "URL": "https://ripple.com/files/ripple_consensus_whitepaper.pdf",
    "note": "Rights status: Rights uncertain. Not a licence to republish the paper."
  }
]

JSONBibTeX fileRIS fileCSL-JSON

Rights record

Source status
Historic library path, plus a commonly cited publisher URL
Use status
Legacy path remains. Full text is not republished.
Rights
Rights uncertain
Training and retrieval
Not permitted from this site. There is no rights-cleared full text to retrieve or to train on.

Rights and licensingCorrections

Useful next step