Visible to the public Obsidian: Typestate and Assets for Safer Blockchain ProgrammingConflict Detection Enabled

TitleObsidian: Typestate and Assets for Safer Blockchain Programming
Publication TypeJournal Article
Year of Publication2020
AuthorsCoblenz, Michael, Oei, Reed, Etzel, Tyler, Koronkevich, Paulette, Baker, Miles, Bloem, Yannick, Myers, Brad A., Aldrich, Jonathan, Sunshine, Joshua
JournalACM Journals: ACM Transactions on Programming Languages and Systems
Volume42
Date Published11/2020
Keywords2021: January, alias control, blockchain, CMU, linearity, Obsidian Language for Blockchain, ownership, permissions, smart contracts, type systems, typestate
Abstract

Blockchain platforms are coming into use for processing critical transactions among participants who have not established mutual trust. Many blockchains are programmable, supporting smart contracts, which maintain persistent state and support transactions that transform the state. Unfortunately, bugs in many smart contracts have been exploited by hackers. Obsidian is a novel programming language with a type system that enables static detection of bugs that are common in smart contracts today. Obsidian is based on a core calculus, Silica, for which we proved type soundness. Obsidian uses typestate to detect improper state manipulation and uses linear types to detect abuse of assets. We integrated a permissions system that encodes a notion of ownership to allow for safe, flexible aliasing. We describe two case studies that evaluate Obsidian's applicability to the domains of parametric insurance and supply chain management, finding that Obsidian's type system facilitates reasoning about high-level states and ownership of resources. We compared our Obsidian implementation to a Solidity implementation, observing that the Solidity implementation requires much boilerplate checking and tracking of state, whereas Obsidian does this work statically.

DOIhttps://doi.org/10.1145/3417516
Citation Keynode-74165

Other available formats:

Coblenz_Obsidian_Aldrich.pdf
AttachmentSize
bytes