In a November 11, 2026 description of Lichen, the author outlines a system in which a user enters a 2-of-2 contract with a central entity and holds Bitcoin-backed tokens on an L2. The design aims to let users withdraw without having to trust that entity to cooperate.
How would a withdrawal work? In the normal case, the user and the entity cooperate to complete it within the channel. If they dispute the withdrawal, the design moves enforcement to Bitcoin. The described mechanism uses pre-signed transactions, RISC Zero/Groth16 proofs and BitVMX dispute resolution.
What are the practical constraints? The author compares the system’s liquidity requirement to Lightning Network inbound capacity. The central entity must also remain online to handle disputes. In the author’s regtest performance figures, a worst-case dispute takes approximately 22–25 transactions. Those figures describe the reported test scenario, not a measured outcome for a live deployment.

