402 / 736POON

Joseph Poon

Coauthor of Lightning and Plasma proposals

Joseph Poon helped explore a simple question: must the whole blockchain record every small payment? With Thaddeus Dryja he proposed Lightning Network, and later with Vitalik Buterin, Plasma. Both move some work away from the base chain while seeking to preserve enforceable rules.

Joseph Poon co-authored the Lightning Network and Plasma proposals. The former connects Bitcoin payment channels; the latter explores a hierarchy of subsidiary blockchains. To understand his work, follow how money moves in each design and what users can do when others stop cooperating.

Buying coffee need not involve telling the entire world about the purchase. At Bitcoin’s base layer, however, a network of computers verifies the payment and records it in a shared history. Joseph Poon and Thaddeus Dryja explored easing that workload through payment channels. The linked proposal is dated 14 January 2016 and marked DRAFT 0.5.9.2. This was an important beginning for Lightning; co-authorship does not mean he alone built all its current components. [1]

Imagine Anna and Pavel depositing bitcoin into a channel. They then sign updated allocations of that amount: after a payment, less belongs to Anna and more to Pavel. Each change need not enter the public history. A Bitcoin transaction can enforce the final allocation. In a dispute, responding to an old state and meeting deadlines also matter. Security therefore includes monitoring events, not simply keeping the latest balance. [1]

The recipient need not share a direct channel with the sender. A payment can pass through other participants using an HTLC, a condition linking payment to a secret value and a deadline. BOLT 2 calls the revealed value payment_preimage and its previously known cryptographic fingerprint payment_hash. Software checks that they match. Finding a route does not guarantee payment success: the conditions must be met, while an error or timeout requires failure handling. [3]

Wallets and nodes written by different developers need more detailed shared rules than a broad proposal. BOLTs, the Lightning specifications, serve that purpose. They describe messages between participants, payment routing and transaction structures, and continue to evolve. Co-authoring the whitepaper does not make Poon the author of every later change. Understanding current software also requires its own documentation and the relevant specification. [2]

Poon also co-authored the Plasma working draft of 11 August 2017 with Vitalik Buterin. Plasma is not a Bitcoin payment channel. It proposes subsidiary chains that process transactions and rely on a parent chain, such as Ethereum, to enforce rules. Instead of a network of agreements between pairs of participants, it describes a hierarchy of blockchains. Sharing the goal of moving work off the base layer does not give the designs identical mechanisms or risks. [4]

Plasma normally publishes only compact cryptographic commitments on the root chain, rather like checkable fingerprints of records. The details stay elsewhere. A fingerprint can help verify supplied data, but cannot reveal missing data. Establishing fraud requires the relevant records. Publishing a hash therefore does not solve data withholding: it cannot ensure that users receive everything needed to defend their funds. [4]

With Plasma, users need a way to withdraw if a subsidiary chain fails. The proposal includes delayed withdrawals and an opportunity to challenge an incorrect claim. It assumes an available, correctly functioning root chain where the necessary procedure can be carried out. This is not a promise of instant withdrawal during any failure. Exit rules, available data and deadlines are part of security rather than peripheral details. [4]

The later Plasma Contracts document explicitly describes community research. Alongside Joseph Poon, it names contributors including Dan Robinson and Kelvin Fichter. It also states that it does not endorse any particular project. A service using the Plasma name therefore has not, by that alone, earned the author’s recommendation. Poon’s contribution is clearest in the documents and questions they opened: what can move off-chain, and how can users still enforce correct settlement? [5]

For the clearest picture, read this entry together with Tadge Dryja, Olaoluwa Osuntokun, Lightning Network. The reverse links also lead from Tadge Dryja, Olaoluwa Osuntokun.

DOC · 001Poon and Dryja — Lightning draft (2016)Documentation DOC · 002BOLTs — specification repositoryDocumentation DOC · 003BOLT 2 — HTLC fulfillment and expiryDocumentation DOC · 004Poon and Buterin — Plasma working draft (2017)Documentation DOC · 005Plasma Contracts — community researchDocumentation
Revised: Source-first · No investment advice