Published February 3, 2022, this report presents Phase 1 of Project Hamilton, a collaboration between the Federal Reserve Bank of Boston and MIT’s Digital Currency Initiative investigating a high-performance transaction processor for a hypothetical central bank digital currency. It includes an executive summary, foreword, and technical paper describing transaction design, security goals, implementation, and evaluation. Two architectures are compared: an atomizer design reaching approximately 170,000 transactions per second and a two-phase commit design demonstrating 1.7 million transactions per second. The report examines tradeoffs among scalability, fault tolerance, privacy, auditability, and self-custody, and outlines future research. The open-source system is an experimental research platform, not a production-ready CBDC or a proposal for public launch.
Free preview text
The first 5 pages, shown as text so search engines and readers can find this document.
Page 1
February 3, 2022
Project Hamilton Phase 1
A High Performance Payment
Processing System Designed for
Central Bank Digital Currencies
Federal Reserve Bank of Boston and
Massachusetts Institute of Technology Digital Currency Initiative
Payments Innovation
Project Hamilton Phase 1 Executive Summary
Federal Reserve Bank of Boston | bostonfed.org | Payments Innovation 3
Introduction
In light of continued innovation in money and payments, many central banks are
exploring the creation of a central bank digital currency (CBDC), a new form of central
bank money which supplements existing central bank reserve account balances and
physical currency [5]. CBDCs could exist in various forms depending on a central bank’s
objectives, including a general-purpose CBDC that can be made available to the public
for retail, e-commerce, and person to person payments. Central banks, researchers, and
policymakers have proposed various objectives including fostering financial inclusion,
improving efficiency in payments, prompting innovation in financial services, maintaining
financial stability, and promoting privacy [2,3,9,19].
Because the CBDC research process is still in early stages in many jurisdictions, several
technical design questions remain open for investigation. The answers to these questions
will have meaningful implications and consequences for what options are, or are not,
available to policymakers.
The Federal Reserve Bank of Boston (Boston Fed) and the Massachusetts Institute of
Technology’s Digital Currency Initiative (MIT DCI) are collaborating on exploratory
research known as Project Hamilton, a multiyear research project to explore the CBDC
design space and gain a hands-on understanding of a CBDC’s technical challenges and
opportunities. This paper presents the project’s Phase 1 research. Our primary goal was
to design a core transaction processor that meets the robust speed, throughput, and fault
tolerance requirements of a large retail payment system. Our secondary goal was to
create a flexible platform for collaboration, data gathering, comparison with multiple
architectures, and other future research. With this intent, we are releasing all software
from our research publicly under the MIT open source license.1
By focusing Phase 1 on the feasibility and performance of basic, but resilient
transactions, we aim to create a foundation for more complex functionality in Phase 2.
The processor’s baseline requirements include time to finality of less than five seconds,
throughput of greater than 100,000 transactions per second, and wide-scale geographic
fault tolerance. Topics left to Phase 2 include critical questions around high-security
issuance, systemwide auditability, programmability, how to balance privacy with
compliance, technical roles for intermediaries, and resilience to denial of service attacks.
As exploratory research on the implications of different design choices, this work is not
intended for a pilot or public launch. That said, we consider performance under a variety
of extensive, realistic workloads and fault tolerance requirements.
1 https://github.com/mit-dci/opencbdc-tx
Page 4
Project Hamilton Phase 1 Executive Summary
Federal Reserve Bank of Boston | bostonfed.org | Payments Innovation 4
Core Design and Results
In Phase 1, we created a design for a modular, extensible transaction processing system,
implemented it in two distinct architectures, and evaluated their speed, throughput, and
fault tolerance. Furthermore, our design can support a variety of models for
intermediaries and data storage, including users custodying their own funds and not
requiring storing personally identifying user data in the core of the transaction processor.
In our design users interact with a central transaction processor using digital wallets
storing cryptographic keys. Funds are addressed to public keys and wallets create
cryptographic signatures to authorize payments. The transaction processor, run by a
trusted operator (such as the central bank), stores cryptographic hashes representing
unspent central bank funds. Each hash commits to a public key and value. Wallets issue
signed transactions which destroy the funds being spent and create an equivalent
amount of new funds owned by the receiver. The transaction processor validates
transactions and atomically and durably applies changes to the set of unspent funds. In
this version of our work, there are no intermediaries, fees, or identities outside of public
keys. However, our design supports adding these roles and other features in the future.
The flexibility, performance, and resiliency challenges of this design are addressed with
three key ideas. The first idea is to decouple transaction validation from execution, which
enables us to use a data structure that stores very little data in the core transaction
processor. It also makes it easier to scale parts of the system independently. The second
idea is a transaction format and protocol that is secure and provides flexibility for potential
functionality like self-custody and future programmability. The third idea is a system
design and commit protocol that efficiently executes these transactions, which we
implemented with two architectures.
Both architectures met and exceeded our speed and throughput requirements. The first
architecture processes transactions through an ordering server which organizes fully
validated transactions into batches, or blocks, and materializes an ordered transaction
history. This architecture durably completed over 99% of transactions in under two
seconds, and the majority of transactions in under 0.7 seconds. However, the ordering
server resulted in a bottleneck which led to peak throughput of approximately 170,000
transactions per second. Our second architecture processes transactions in parallel on
multiple computers and does not rely on a single ordering server to prevent double
spends. This results in superior scalability but does not materialize an ordered history for
all transactions. This second architecture demonstrated throughput of 1.7 million
transactions per second with 99% of transactions durably completing in under a second,
and the majority of transactions completing in under half a second. It also appears to
scale linearly with the addition of more servers. In order to provide resilience, each
architecture can tolerate the loss of two datacenter locations (for example, due to natural
disasters or loss of network connectivity) while seamlessly continuing to process
transactions and without losing any data.
Page 5
Project Hamilton Phase 1 Executive Summary
Federal Reserve Bank of Boston | bostonfed.org | Payments Innovation 5
Learnings
Phase 1 has surfaced several key learnings on the potential design of a CBDC:
Select ideas from cryptography, distributed systems, and blockchain technology can
provide unique functionality and robust performance. We suspect existing database and
distributed systems technology is sufficient to provide a more traditional payment
architecture for CBDC where one actor stores users’ accounts, users cannot custody
their own funds, and there is no transaction scripting functionality. We created a new
design to offer both these features and new opportunities for different intermediary roles.
A CBDC can provide functionality that is not currently possible with either cash or bank
accounts. For example, a CBDC could support cryptographic proofs of payment, more
complex transfers to or from multiple sources of funds, and flexible forms of authorization
to spend, such as varying transaction limits.
We found that separating a transaction processor into modular components improves
system scalability and flexibility; for example, we can scale and replicate transaction
validation independently from preventing double spending and committing transactions,
and our architecture can support many future designs for programmability and privacy.
Despite using ideas from blockchain technology, we found that a distributed ledger
operating under the jurisdiction of different actors was not needed to achieve our goals.
Specifically, a distributed ledger does not match the trust assumptions in Project
Hamilton’s approach, which assumes that the platform would be administered by a
central actor. We found that even when run under the control of a single actor, a
distributed ledger architecture has downsides. For example, it creates performance
bottlenecks, and requires the central transaction processor to maintain transaction
history, which one of our designs does not, resulting in significantly improved transaction
throughput scalability properties.
CBDC design choices are more granular than commonly assumed. Currently, CBDC
designs are categorized as direct, two-tier, or hybrid models, with “token” or “account”
access models [1, 2, 7, 12, 15]. We found these limited categorizations lacking and
insufficient to surface the complexity of choices in access, intermediation, institutional
roles, and data retention in CBDC design [10]. For example, wallets can support both an
account-balance view and a coin-specific view for the user regardless of how funds are
stored in the database.
By breaking transaction processing into steps like creation, authorization, submission,
execution, and storing history, CBDC designers can consider the potential roles for
intermediaries at each stage, creating opportunities for innovation.
By implementing a robust system, we identify new questions for CBDC designers and
policymakers to address, regarding tradeoffs in performance, auditability, functionality,
and privacy. Our work raised important questions to address in how the technical
architecture might affect the use and function of CBDC in payments. For example, it is an
open question how important from an economic perspective it might be to support atomic
transactions. In database parlance, this implies multiple operations to different pieces of
Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies: summary, contents and background
This guide helps you understand the scope of Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Summary and overview
Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies is a 44-page documentcredited to Ada T. Alder. Published February 3, 2022, this report presents Phase 1 of Project Hamilton, a collaboration between the Federal Reserve Bank of Boston and MIT’s Digital Currency Initiative investigating a high-performance transaction processor for a hypothetical central bank digital currency. It includes an executive summary, foreword, and technical paper describing transaction design, security goals, implementation, and evaluation. Two architectures are compared: an atomizer design reaching approximately 170,000 transactions per second and a two-phase commit design demonstrating 1.7 million transactions per second. The report examines tradeoffs among scalability, fault tolerance, privacy, auditability, and self-custody, and outlines future research. The open-source system is an experimental research platform, not a production-ready CBDC or a proposal for public launch. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Project Hamilton, Central bank digital currency, Payment processing, Distributed systems, Cryptography, Scalability, Fault tolerance, Financial privacy, OpenCBDC, Technical research with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
Key topics and reader takeaways
The catalogue connects this document with Project Hamilton, Central bank digital currency, Payment processing, Distributed systems, Cryptography, Scalability, Fault tolerance, Financial privacy, OpenCBDC, Technical research. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
Table of contents and reading guide
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 44 pages in the player.
Part 1
Project Hamilton
Use this section of the reading guide to identify how Project Hamilton appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 2
Central bank digital currency
Use this section of the reading guide to identify how Central bank digital currency appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 3
Payment processing
Use this section of the reading guide to identify how Payment processing appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 4
Distributed systems
Use this section of the reading guide to identify how Distributed systems appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 5
Cryptography
Use this section of the reading guide to identify how Cryptography appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 6
Scalability
Use this section of the reading guide to identify how Scalability appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 7
Fault tolerance
Use this section of the reading guide to identify how Fault tolerance appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
Part 8
Financial privacy
Use this section of the reading guide to identify how Financial privacy appears in Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
About Ada T. Alder
Doxxly credits Ada T. Alder as the author or creator of Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
About the source organisation
The recorded source for this item is bostonfed.org. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Begin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
Research questions to consider
As you read Project Hamilton Phase 1: A High Performance Payment Processing System Designed for Central Bank Digital Currencies, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.