Discreet Log Contracts (DLCs)

Definition: A Discreet Log Contract (DLC) is a Bitcoin contract that lets two parties commit funds to pre-agreed payouts based on an outcome reported by an oracle. Before the event, the parties prepare a funding transaction, possible Contract Execution Transactions (CETs), and a time-locked refund path. An oracle’s signature on the event result can unlock the matching CET. Bitcoin validates the eventual settlement transactions; the contract’s event terms and alternative payouts are arranged largely off-chain. The design aims to make a DLC difficult for outside observers—and, in some constructions, the oracle itself—to identify, but privacy depends on how it is built and used.125

TypeBitcoin protocol for conditional, pre-arranged settlement
ParticipantsTwo contracting parties and one or more event oracles2
Settlement pathsFunding transaction, outcome-specific CETs, and a time-locked refund transaction34
Main dependencyAccurate, timely oracle data and each party’s ability to broadcast the appropriate transaction
DirectoryBitcoin Directory

How a DLC is prepared

A DLC begins with an event description and the oracle information needed to attest to it. An oracle can announce its signing key and a public nonce before an event, then later publish a signed outcome. The parties negotiate the contract’s terms, collateral, possible outcomes, and refund timing. They use that information to calculate payouts for each outcome and construct the transactions that could settle the contract.2

For each supported result, the parties create a Contract Execution Transaction. They exchange signatures and adaptor signatures in advance, tying each prepared payout to the oracle’s future signature for that result. When the oracle announces the result, a party can complete the matching signature and broadcast that CET. The other outcome transactions remain unusable under the agreed signing scheme. This is a simplified description: event formats, signature construction, and transaction handling vary between implementations.13

Funding, settlement, and refunds

The parties lock their agreed collateral in a funding transaction. After the event, the CET for the attested outcome spends that funding output and pays each party according to the terms they signed. The oracle does not directly take custody of the collateral; it supplies a signed message that lets the pre-arranged transaction path be completed. Bitcoin nodes check the funding and settlement transactions using Bitcoin’s normal script and consensus rules rather than executing a general-purpose smart contract program.14

A refund transaction provides a timeout path if the expected oracle message never arrives. It is timelocked so it can be broadcast after the agreed deadline and return collateral according to the contract setup. This reduces the risk of funds remaining locked indefinitely, but participants still need to monitor the contract, manage transaction fees, and use compatible software. Exact recovery behavior depends on the implementation and the transactions signed during setup.34

Privacy and the oracle trust model

“Discreet” refers to the effort to keep the contract’s existence and terms from being obvious in public transaction data. In the original construction, a funding output can resemble an ordinary multisignature output, and the oracle can publish a result without being contacted by a particular contract’s participants. That can reduce what the oracle and outside observers learn, but it does not make a DLC anonymous by definition. Funding and settlement still appear on Bitcoin, and the transaction pattern, wallet behavior, communication channels, or a particular implementation may reveal information.125

A DLC also relies on an oracle to report an agreed real-world event. The protocol can constrain how an oracle’s signature unlocks a payout, but it cannot establish that the oracle’s report is true. The current DLC specifications note that their design does not by itself prevent a contracting party from colluding with an oracle. Using multiple oracles can change the trust model, but does not remove the need to evaluate their data sources, incentives, availability, and failure procedures.26

Uses and limitations

DLCs can express payouts tied to a published price, a sports score, a weather observation, or another event that an oracle can describe in a signed message. The original proposal discusses financial contracts such as derivatives, where the final payout depends on a publicly verifiable future value. A DLC is not a token or a separate blockchain, and it does not run arbitrary application code on Bitcoin. It is a way to prepare Bitcoin transactions whose valid settlement depends on an oracle attestation and the signatures arranged by the counterparties.15

Before using one, participants need to understand the contract’s outcome definitions, oracle rules, collateral, refund deadline, transaction fees, and software support. An ambiguous event description or unavailable oracle can complicate settlement. A single oracle can report a false result or fail to publish; multiple-oracle arrangements may reduce dependence on one source but add coordination and design choices. DLCs therefore reduce some on-chain disclosure and counterparty interaction while leaving meaningful oracle, software, liquidity, and operational risks.23

History

  • June 2017: Thaddeus Dryja published the original paper proposing Discreet Log Contracts for private, oracle-based contracts on Bitcoin.1
  • June 2018: MIT’s Digital Currency Initiative published an explainer and demonstration of DLCs, including an example involving Bitcoin-settled dollar futures.5
  • As of November 10, 2026: The public DLC specifications repository describes its documents as a work in progress; its repository is an evolving technical specification, not a finalized Bitcoin protocol standard.6

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Dryja, Thaddeus. “Discreet Log Contracts.” MIT Digital Currency Initiative, June 2017. https://adiabat.github.io/dlc.pdf.
  2. Discreet Log Contracts. “Introduction.” Discreet Log Contracts Specifications. GitHub. Accessed November 10, 2026. https://github.com/discreetlogcontracts/dlcspecs/blob/master/Introduction.md.
  3. Discreet Log Contracts. “Non-Interactive Protocol.” Discreet Log Contracts Specifications. GitHub. Accessed November 10, 2026. https://github.com/discreetlogcontracts/dlcspecs/blob/master/Non-Interactive-Protocol.md.
  4. Discreet Log Contracts. “Transactions.” Discreet Log Contracts Specifications. GitHub. Accessed November 10, 2026. https://github.com/discreetlogcontracts/dlcspecs/blob/master/Transactions.md.
  5. MIT Digital Currency Initiative. “Discreet Log Contracts.” Accessed November 10, 2026. https://www.dci.mit.edu/projects/discreet-log-contracts.
  6. Discreet Log Contracts. “dlcspecs: Specification for Discreet Log Contracts.” GitHub. Accessed November 10, 2026. https://github.com/discreetlogcontracts/dlcspecs.