--- title: "Developer Unveils Lichen Design for Trust-Minimized Bitcoin Layer-2 Exits" description: "Adam Gibson's protocol combines 2-of-2 multisig outputs and BitVMX dispute settlement to allow unilateral fund withdrawals without an issuer's permission." url: https://basisdesk.news/news/lichen-bitcoin-layer-2-bitvmx-exit-design published: 2026-10-23T11:16:36.005Z modified: 2026-10-23T11:16:36.005Z section: Tech & Protocols author: Basis Desk Newsroom (AI-generated, source-verified) sentiment: neutral tickers: [BTC] tags: [bitcoin, layer-2, bitvmx, scaling, cryptography] license: Quote with attribution to Basis Desk (basisdesk.news). Not financial advice. --- # Developer Unveils Lichen Design for Trust-Minimized Bitcoin Layer-2 Exits Adam Gibson's protocol combines 2-of-2 multisig outputs and BitVMX dispute settlement to allow unilateral fund withdrawals without an issuer's permission. ## At a glance - **What happened:** Developer Adam Gibson proposed Lichen, a single-issuer Bitcoin layer-2 design that allows users to withdraw funds unilaterally using BitVMX dispute resolution. - **Why it matters:** The mechanism eliminates reliance on honest-majority attestation committees for layer-2 exits, replacing them with onchain dispute settlement. - **Who is affected:** Bitcoin protocol engineers, layer-2 infrastructure developers, and wallet builders evaluating off-chain scaling models. - **What's next:** Exploration of validity proofs and multi-party sequencer committees to eliminate sequencer centralization risks highlighted in the paper. - **Status:** proposed - **Primary source:** [Bitcoin Optech Newsletter #428](https://bitcoinops.org/en/newsletters/2026/10/23/) — Bitcoin Optech ## Key points - Adam Gibson published Lichen, a single-issuer Bitcoin layer-2 design featuring unilateral onchain redemptions. - The system uses 2-of-2 outputs alongside Groth16 proofs and BitVMX transactions to resolve settlement disputes onchain. - Lichen relies on sequencer honesty to record state updates, though future work targets validity proofs and sequencer committees. ## Editorial remark - **Context:** Layer-2 scaling proposals on Bitcoin have historically relied either on federated signer sets or bidirectional payment channels requiring continuous online participation. - **Impact:** Bitcoin scaling developers gain an alternative blueprint to LN-GAP that enforces trust-minimized exits without multi-party federation consensus. - **Watch:** Community feedback on the Bitcoin-Dev mailing list and proof-of-concept benchmarks evaluating BitVMX dispute costs onchain. Developer Adam Gibson presented a paper and proof-of-concept implementation for Lichen, a protocol enabling users to withdraw funds from a single-issuer Bitcoin layer 2 without relying on the issuer's cooperation [1]. Gibson posted the design to the Bitcoin-Dev mailing list [1]. At the time of writing, $BTC traded around $81,484. Under the Lichen architecture, a central entity dubbed a "hub" mints tokens pegged one-to-one to bitcoin on a layer-2 ledger maintained by a separate sequencer [1]. Users deposit funds by locking $BTC into an individual 2-of-2 output shared with the hub, receiving corresponding tokens to execute off-chain transfers [1]. To mirror inbound liquidity models found in the Lightning Network, the hub commits its own capital up to a negotiated cap in the output, allowing recipients to withdraw received tokens onchain [1]. In standard operations, the hub cooperatively signs redemption transactions; if the hub refuses or becomes unresponsive, the user submits a Groth16 proof demonstrating that the sequencer logged the token return [1]. Because native Bitcoin Script cannot parse these zero-knowledge proofs directly, Lichen settles disagreements onchain using presigned BitVMX transactions that reduce the dispute to a single evaluable execution step [1]. ## Off-Chain Tradeoffs and Wallet Updates Lichen removes the need for honest-majority attestation committees used in architectures like LN-GAP, shifting dispute resolution entirely to base-layer scripts enforced by collateral bonds [1]. Both parties lock financial reserves that are forfeited upon losing a challenge [1]. However, Gibson noted residual security constraints: users still rely on the sequencer to process ledger updates honestly [1]. An adversarial or malfunctioning sequencer could fail to register token returns or attest to unreached states, resulting in capital loss for users or the hub [1]. Alongside the Lichen proposal, the Bitcoin development ecosystem saw several complementary infrastructure updates. Contributor João Dias submitted a Delving Bitcoin proposal extending BIP379 miniscript syntax to support private hash preimages directly within Bitcoin Core descriptors, removing external tool dependencies for pre-known secrets [1]. Concurrently, developers shipped security patches across versions 0.14.4 and 0.14.5 of the Eclair Lightning client to mitigate trampoline routing exploits and signature verification bugs in taproot channel splicing [1]. ## Sources 1. [Bitcoin Optech Newsletter #428](https://bitcoinops.org/en/newsletters/2026/10/23/) — Bitcoin Optech, 2026-10-23 --- Basis Desk Newsroom · AI-generated, source-verified · https://basisdesk.news/about/how-we-use-ai