From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin

summary

The gist

The paper investigates whether new oracle designs have emerged for Bitcoin Layer 1 since the 2015 transition to the Ethereum smart contracts era and whether subsequent Bitcoin improvement proposals…

In short

The paper examines Bitcoin oracle designs since 2015, tracing a shift from multisig-style co-signers to attestation-based Discreet Log Contracts (DLCs). This evolution shows a move toward designs that better fit Bitcoin's community standards and practical uses in areas like betting and prediction markets.

Key concepts

Multisig-style Oracles
Early oracle concepts envisioned oracles as co-signers within a multisignature scheme (like m-of-n). This approach aimed to increase fault tolerance by requiring multiple independent entities to agree on an outcome before a transaction could proceed. It was an initial architectural attempt to secure external data inputs.
Discreet Log Contracts (DLCs)
DLC is a modern attestation-based design that shows strong Bitcoin community compliance. Instead of relying on direct oracle messages, it uses cryptographic proofs to execute conditional transactions based on future public values. This method provides stronger security and practical implementation evidence in real-world scenarios.
Attestation-based Designs
This architectural shift moves away from traditional oracle messages toward using cryptographic attestations. These are proofs generated off-chain that confirm a specific outcome, allowing the contract to execute based on this verifiable external proof rather than direct on-chain data feeds.

Terminology used across episodes

This episode discusses

The paper

From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin · Read on arXiv

Giulio Caldarelli

University of Turin

Unlike Ethereum, which was conceived as a general-purpose smart-contract platform, Bitcoin was designed primarily as a transaction ledger for its native currency, which limits programmability for conditional applications. This constraint is particularly evident when considering oracles, mechanisms that enable Bitcoin contracts to depend on exogenous events. This paper investigates whether new oracle designs have emerged for Bitcoin Layer 1 since the 2015 transition to the Ethereum smart contracts era and whether subsequent Bitcoin improvement proposals have expanded oracles' implementability. Using Scopus and Web of Science searches, complemented by Google Scholar to capture protocol proposals, we observe that the indexed academic coverage remains limited, and many contributions circulate outside journal venues. Within the retrieved corpus, the main post-2015 shift is from multisig-style, which envisioned oracles as co-signers, toward attestation-based designs, mainly represented by Discreet Log Contracts (DLCs), which show stronger Bitcoin community compliance, tool support, and evidence of practical implementations in real-world scenarios such as betting and prediction-market mechanisms.

DOI: 10.3389/fbloc.2026.1903194

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin".

Elias: Here's the gist of the paper. The paper investigates whether new oracle designs have emerged for Bitcoin Layer 1 since the 2015 transition to the Ethereum smart contracts era and whether subsequent Bitcoin improvement proposals have expanded oracles' implementability Using Scopus and Web of Science searches, we observe that the indexed academic coverage remains limited, and many contributions circulate outside journal venues Within the retrieved corpus, the main post-2015 shift is from multisig-style, which envisioned oracles as co-signers, toward attestation-based designs, mainly represented by Discreet Log Contracts (DLCs), which show stronger Bitcoin community compliance, tool support, and evidence of practical implementations in realworld scenarios such as betting and prediction-market mechanisms The Evolution of Oracle Mechanisms The paper traces the development of Bitcoin oracle concepts from early proposals to modern designs, highlighting a significant shift in architectural approach 1.

Nadia: Early efforts involved multisig-style oracles envisioned as co-signers, such as the m-of-n schemes proposed by Orisi, which aimed to improve fault tolerance 2.

Elias: A major post-Ethereum shift is toward attestation-based designs, primarily Discreet Log Contracts (DLCs), which demonstrate stronger Bitcoin community compliance and practical implementations 3.

Nadia: Other conceptual approaches include Truthcoin's proposal to shift oracle computations to auxiliary chains while relying on Bitcoin for settlement 4.

Title and authors: Nadia: So we’re looking at this paper right now, "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin." It’s really digging into what's happened with Bitcoin oracles since that big move to Ethereum in two thousand fifteen and whether there are any new ways people are building these things <ref:2602.09822#pg1>.

Elias: Yeah, it’s looking at the landscape of oracle designs. The authors did a search through Scopus and Web of Science to see what academic work has come out, but they found that most of the papers circulating aren't in traditional journals, which is kind of telling about where the real development is happening.

Priya: So it seems like the academic coverage isn't super deep on this topic yet. What’s the main shift they are tracking? Is it just a change in how people think about these external data feeds?

Nadia: Exactly, Priya. The big thing they found is that the design approach has moved away from multisig schemes where oracles were treated like co-signers. It's moving toward something called attestation-based designs, primarily using Discreet Log Contracts or DLCs.

Elias: Discreet Log Contracts seem to be the key focus here because the paper says they show stronger compliance with Bitcoin community standards and there's actual evidence of them being used in real scenarios like betting and prediction markets.

Priya: So, what does this shift from multisig to DLC actually mean for the security and trust model on Bitcoin? Is it just a different way to manage the risk?

Nadia: It means a change in how you verify data. Instead of relying on multiple people signing off on an oracle's input, you're moving toward a structure where the outcome is verified once an event happens, and that verification is baked into the contract itself through these DLCs > This is what they mean by "the transaction once a specified event outcome has been verified" <ref:2602.09822#pg1>.

Elias: And I think that move toward attestation makes it feel more like a built-in property of the protocol rather than just an add-on mechanism for external data > It moves the trust assumption from "trust these multiple signers" to something more cryptographic.

Priya: So, what are some of these new designs they mentioned, beyond just DLCs? Are there other conceptual ideas floating around?

Nadia: The paper also touched on other things. They mentioned Truthcoin’s proposal which aimed to shift the actual computation of the oracle data off-chain onto auxiliary chains, while keeping Bitcoin for the final settlement > It's like they want to keep the heavy lifting separate from the main chain.

Title and authors: Elias: And then there's also this idea where an AI system can execute conditional transactions based on external events using these DLCs, which is pretty interesting because it avoids needing those explicit on-chain oracle messages that we usually worry about > It lets the contract depend on a value that is publicly known in the future.

Priya: That sounds like it could simplify things for some applications by removing the need for a direct oracle interaction during the transaction itself. But what about managing more complex scenarios with multiple data sources?

Nadia: The paper points out that there's also a design using Verifiable Witness Encryption based on Threshold Signatures, or VweTS, to help an AI system manage those multi-oracle situations > This lets an agent prepare candidate settlement transactions and lock the payment authorization so it only becomes usable if enough independent oracles attest to the same outcome.

Elias: That’s a sophisticated way to handle dependencies between different oracle results without requiring every single one of them to be directly involved in every single transaction > It’s about creating a verifiable proof that a threshold was met.

Priya: Moving into the practical side, they discussed integrating these DLCs with Automated Market Makers or AMMs for prediction markets. How does that change the way liquidity and inventory are accounted for on-chain?

Nadia: They showed a design where buying some shares in an AMM requires a trader to lock some collateral, like K sats as DLC collateral, while the market maker commits the rest of the collateral R > This lets pricing and inventory accounting happen off-chain.

Elias: That’s smart because it separates the high-frequency trading logic from the heavy state management of Bitcoin itself > It’s using the on-chain mechanism for a specific security guarantee rather than running every calculation there.

Priya: And there's another idea they presented, which is offering oracle-less alternatives for certain Bitcoin derivatives by just looking at chain variables like block height or timestamps, citing PowSwap's Blockrate Binaries > That design aims to remove the trust assumptions entirely for a narrow class of events.

Nadia: It’s an interesting trade-off because it removes the need for an external party altogether, but they made it clear that this is only suited for a very specific, narrow set of events > You can't use this for everything.

Elias: So, to wrap up on the main points of "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin," the paper shows a clear trend away from simple co-signer multisig models toward more cryptographically robust attestation methods like DLCs > It maps out how these new mechanisms are being pursued and what real applications they might support.

Title and authors: Priya: So, for someone just listening to this, it suggests that the future of Bitcoin oracles isn't about adding another layer of simple signing; it’s about integrating cryptographic proof directly into the contract logic using things like Discreet Log Contracts > It points toward a future where conditional transactions are verified in a more native way.

Nadia: Right. We saw this paper really highlight how these new designs, from DLCs to VweTS, are making things more flexible for complex applications like prediction markets and AI execution > It shows the evolution of what's possible on Bitcoin Layer one regarding external data dependencies <ref:2602.09822#pg1>.

Elias: It’s less about replacing the whole concept of an oracle and more about making the verification process itself much stronger and more integrated into the underlying script language > The focus is on verifiable outcomes rather than just fetching a piece of data.

Priya: But what does this mean for us in terms of privacy? If we're moving toward off-chain attestation oracles, does that actually improve on-chain privacy for conditional settlements?

Nadia: It’s about shifting the trigger mechanism. Instead of the oracle being an explicit piece of on-chain data that dictates a branch, you have attestations produced off-chain > This means on-chain settlements look more like regular spending transactions, which is a big win for privacy concerns.

Elias: That’s because it decouples the sensitive data gathering from the final settlement process on the main ledger > It moves the point of exposure away from being directly readable by everyone on every transaction.

Priya: So, to wrap up this discussion on "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin," we see a clear progression in how developers are tackling external data needs > The shift toward attestation and contract-like techniques is reshaping the trust model for conditional transactions on Bitcoin.

Nadia: It’s definitely a direction worth watching as these mechanisms move from research papers into actual implementation > We'll keep an eye on how these DLCs scale and how practical they become in the real world.

Elias: Agreed. The work by Caldarelli and the others gives us a better picture of where the technical community is focusing its energy right now > It’s definitely an interesting area to follow as we move past the initial theoretical proposals.

Priya: That's all for this look at modern oracle designs on Bitcoin > We'll see what the next set of papers brings to this space soon.

The paper's summary: Nadia: So, we're looking at this paper, "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin." It’s really tracking how people are building oracle systems for Bitcoin after that big shift to Ethereum back in twenty fifteen and whether there are any new ways to make those oracles work.

Elias: Yeah, it’s looking at the landscape of oracle designs. The authors did a search through Scopus and Web of Science to see what academic work has come out, but they found that most of the papers circulating aren't in traditional journals, which is kind of telling about where the real development is happening.

Priya: So, it seems like the academic coverage isn't super deep on this topic yet. What’s the main shift they are tracking? Is it just a change in how people think about these external data feeds?

Nadia: Exactly, Priya. The big thing they found is that the design approach has moved away from multisig schemes where oracles were treated like co-signers. It's moving toward something called attestation-based designs, primarily using Discreet Log Contracts or DLCs.

Elias: Discreet Log Contracts seem to be the key focus here because the paper says they show stronger compliance with Bitcoin community standards and there's actual evidence of them being used in real scenarios like betting and prediction markets.

Priya: So, what does this shift from multisig to DLC actually mean for the security and trust model on Bitcoin? Is it just a different way to manage the risk?

Nadia: It means a change in how you verify data. Instead of relying on multiple people signing off on an oracle's input, you're moving toward a structure where the outcome is verified once an event happens, and that verification is baked into the contract itself through these DLCs.

Elias: And I think that move toward attestation makes it feel more like a built-in property of the protocol rather than just an add-on mechanism for external data.

Priya: So, what are some of these new designs they mentioned, beyond just DLCs? Are there other conceptual ideas floating around?

Nadia: The paper also touched on other things. They mentioned Truthcoin’s proposal which aimed to shift the actual computation of the oracle data off-chain onto auxiliary chains, while keeping Bitcoin for the final settlement.

The paper's summary: Elias: And then there's also this idea where an AI system can execute conditional transactions based on external events using these DLCs, which is pretty interesting because it avoids needing those explicit on-chain oracle messages that we usually worry about.

Priya: That sounds like it could simplify things for some applications by removing the need for a direct oracle interaction during the transaction itself. But what about managing more complex scenarios with multiple data sources?

Nadia: The paper points out that there's also a design using Verifiable Witness Encryption based on Threshold Signatures, or VweTS, to help an AI system manage those multi-oracle situations. It lets an agent prepare candidate settlement transactions and lock the payment authorization so it only becomes usable if enough independent oracles attest to the same outcome.

Elias: That’s a sophisticated way to handle dependencies between different oracle results without requiring every single one of them to be directly involved in every single transaction. It’s about creating a verifiable proof that a threshold was met.

Priya: Moving into the practical side, they discussed integrating these DLCs with Automated Market Makers or AMMs for prediction markets. How does that change the way liquidity and inventory are accounted for on-chain?

Nadia: They showed a design where buying some shares in an AMM requires a trader to lock some collateral, like K sats as DLC collateral, while the market maker commits the rest of the collateral R. This lets pricing and inventory accounting happen off-chain.

Elias: That’s smart because it separates the high-frequency trading logic from the heavy state management of Bitcoin itself. It’s using the on-chain mechanism for a specific security guarantee rather than running every calculation there.

Priya: And there's another idea they presented, which is offering oracle-less alternatives for certain Bitcoin derivatives by just looking at chain variables like block height or timestamps, citing PowSwap's Blockrate Binaries. That design aims to remove the trust assumptions entirely for a narrow class of events.

Nadia: It’s an interesting trade-off because it removes the need for an external party altogether, but they made it clear that this is only suited for a very specific, narrow set of events. You can't use this for everything.

The paper's summary: Elias: So, to wrap up on the main points of "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin," the paper shows a clear trend away from simple co-signer multisig models toward more cryptographically robust attestation methods like DLCs. It maps out how these new mechanisms are being pursued and what real applications they might support.

Priya: So, for someone just listening to this, it suggests that the future of Bitcoin oracles isn't about adding another layer of simple signing; it’s about integrating cryptographic proof directly into the contract logic using things like Discreet Log Contracts. It points toward a future where conditional transactions are verified in a more native way.

Nadia: Right. We saw this paper really highlight how these new designs, from DLCs to VweTS, are making things more flexible for complex applications like prediction markets and AI execution. It shows the evolution of what's possible on Bitcoin Layer one regarding external data dependencies.

Elias: It’s less about replacing the whole concept of an oracle and more about making the verification process itself much stronger and more integrated into the underlying script language. The focus is on verifiable outcomes rather than just fetching a piece of data.

Priya: But what does this mean for us in terms of privacy? If we're moving toward off-chain attestation oracles, does that actually improve on-chain privacy for conditional settlements?

Nadia: It’s about shifting the trigger mechanism. Instead of the oracle being an explicit piece of on-chain data that dictates a branch, you have attestations produced off-chain. This means on-chain settlements look more like regular spending transactions, which is a big win for privacy concerns.

Elias: That’s because it decouples the sensitive data gathering from the final settlement process on the main ledger. It moves the point of exposure away from being directly readable by everyone on every transaction.

Priya: So, to wrap up this discussion on "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin," we see a clear progression in how developers are tackling external data needs. The shift toward attestation and contract-like techniques is reshaping the trust model for conditional transactions on Bitcoin.

Nadia: It’s definitely a direction worth watching as these mechanisms move from research papers into actual implementation. We'll keep an eye on how these DLCs scale and how practical they become in the real world.

The paper's improvements: Tom: So, we're looking at the improvements suggested in this paper about moving from multisig to DLCs for Bitcoin oracles. It’s talking about how AI can use these new designs to execute transactions and manage complex data sources in much smarter ways.

Nadia: Basically, they show how you can build an AI system that executes conditional transactions based on external events using these Discreet Log Contracts. This means parties don't have to send explicit messages on the chain anymore.

Elias: That’s interesting because it lets the contract depend on a value that is publicly known in the future, which simplifies things for building automated systems. It shifts the trust away from needing an immediate on-chain oracle call.

Priya: Does this mean we can actually use AI to manage multiple data sources without needing a human to constantly sign off on every piece of input?

Nadia: Yeah, they introduce something called Verifiable Witness Encryption based on Threshold Signatures, or VweTS. This lets an agent prepare candidate settlement transactions and lock the payment authorization so it only becomes usable if a certain number of independent oracles attest to the same outcome.

Elias: That’s a way to handle multi-oracle scenarios without requiring every single oracle to be involved in every transaction. It creates a verifiable proof that you hit your required threshold.

Priya: So, for someone just listening, it sounds like this makes AI agents more robust because they can handle uncertainty from multiple sources more effectively. But what about the practical side of using these for things like prediction markets?

Nadia: They also talk about integrating these DLCs with Automated Market Makers or AMMs to support non-custodial prediction markets with dynamic liquidity. This allows a design where buying some shares requires the trader to lock some collateral as DLC collateral while the market maker commits the rest.

Elias: That separates the high-frequency trading logic from Bitcoin’s state management. It lets pricing and inventory accounting happen off-chain, which is a big plus for scalability.

Priya: And they also mentioned these oracle-less alternatives for certain Bitcoin derivatives using chain variables like block height or timestamps, citing PowSwap's Blockrate Binaries. That design aims to remove the trust assumptions entirely for a narrow class of events.

Nadia: It’s an interesting trade-off because it removes the need for an external party altogether, but they made it clear that this is only suited for a very specific, narrow set of events. You can't use this for everything.

Elias: So, to wrap up on the improvements suggested in "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin," we see these new tools making things more flexible for complex applications like prediction markets and AI execution. It shows the evolution of what's possible on Bitcoin Layer one regarding external data dependencies.

Priya: So, for someone just listening, it suggests that the future of Bitcoin oracles isn't about adding another layer of simple signing; it’s about integrating cryptographic proof directly into the contract logic using things like Discreet Log Contracts. It points toward a future where conditional transactions are verified in a more native way.

Nadia: Right. We saw this paper really highlight how these new designs, from DLCs to VweTS, are making things more flexible for complex applications like prediction markets and AI execution. It shows the evolution of what's possible on Bitcoin Layer one regarding external data dependencies.

Conclusion: Tom: So, we're wrapping up our look at "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin." The main idea is that we’re seeing a clear trend away from old multisig models toward these new attestation methods like Discreet Log Contracts.

Nadia: Exactly. It boils down to moving from needing multiple people to sign off on every data point, to having the contract itself verify the outcome once an event happens through these DLCs.

Elias: I think that move toward attestation makes it feel more like a built-in property of the protocol instead of just an add-on mechanism for external data. It’s about verifiable outcomes rather than just fetching a piece of data.

Priya: So, for someone just listening, it suggests that the future of Bitcoin oracles isn't about adding another layer of simple signing; it’s about integrating cryptographic proof directly into the contract logic using things like Discreet Log Contracts. It points toward a future where conditional transactions are verified in a more native way.

Nadia: Right. We saw this paper really highlight how these new designs, from DLCs to VweTS, are making things more flexible for complex applications like prediction markets and AI execution. It shows the evolution of what's possible on Bitcoin Layer one regarding external data dependencies.

Elias: It’s less about replacing the whole concept of an oracle and more about making the verification process itself much stronger and more integrated into the underlying script language. The focus is on verifiable outcomes rather than just fetching a piece of data.

Priya: I think what this means for us in terms of privacy is that shifting to off-chain attestation oracles means on-chain settlements look more like regular spending transactions, which is a big win for privacy concerns. It decouples the sensitive data gathering from the final settlement process on the main ledger.

Nadia: That’s because it moves the point of exposure away from being directly readable by everyone on every transaction. It’s definitely a direction worth watching as these mechanisms move from research papers into actual implementation.

Elias: Agreed. The work by Caldarelli and the others gives us a better picture of where the technical community is focusing its energy right now, but we need to see how these DLCs scale in practice.

Priya: I'm still curious about those limitations they mentioned, though, since this is a big shift. Where does this method stop working?

Nadia: They did flag that the off-chain attestation still requires a trust model for the off-chain part of things. It’s not completely oracle-less everywhere yet.

Elias: So, it's not a magic switch yet, but it’s definitely pushing the boundary on how we handle external data in decentralized systems.

Priya: Alright then, this paper "From Multi-sig to DLCs: Modern Oracle Designs on Bitcoin" shows a clear progression in how developers are tackling external data needs. The shift toward attestation and contract-like techniques is reshaping the trust model for conditional transactions on Bitcoin.

More episodes

← Home