Formally Verifying the Safety of Pipelined Moonshot Consensus Protocol
M. Praveen, Raghavendra Ramesh, Isaac Doidge

TL;DR
This paper formally verifies the safety of Supra's Pipelined Moonshot consensus protocol, ensuring it prevents forks and double spending in blockchain systems with Byzantine validators.
Contribution
It provides the first formal safety proof for Pipelined Moonshot using IVy, extending verification to all network sizes under Byzantine fault assumptions.
Findings
Pipelined Moonshot is fork-free with less than one-third Byzantine validators.
The formal proof guarantees double spending cannot occur due to forks.
The IVy model and proof are publicly available on Github.
Abstract
Decentralized Finance (DeFi) has emerged as a contemporary competitive as well as complementary to traditional centralized finance systems. As of 23rd January 2024, per Defillama approximately USD 55 billion is the total value locked on the DeFi applications on all blockchains put together. A Byzantine Fault Tolerant (BFT) State Machine Replication (SMR) protocol, popularly known as the consensus protocol, is the central component of a blockchain. If forks are possible in a consensus protocol, they can be misused to carry out double spending attacks and can be catastrophic given high volumes of finance that are transacted on blockchains. Formal verification of the safety of consensus protocols is the golden standard for guaranteeing that forks are not possible. However, it is considered complex and challenging to do. This is reflected by the fact that not many complex consensus…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsDistributed systems and fault tolerance · Software Testing and Debugging Techniques · Mobile Agent-Based Network Management
