Skip to content

Oblivious Oracle Contracts #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LLFourn opened this issue Jan 27, 2022 · 0 comments
Open

Oblivious Oracle Contracts #28

LLFourn opened this issue Jan 27, 2022 · 0 comments

Comments

@LLFourn
Copy link
Contributor

LLFourn commented Jan 27, 2022

The key advantage of Disceet Log Contracts is that the oracle remains oblivious to the details of the contract.
You lose this property if you use something like OP_CHECKSIGFROMSTACK and OP_CAT just check an oracle signature on a message and then pay out to the two users based on the message the oracle signed.

What if there was a maintaining the privacy of a DLC without the complexity in the number of outcomes.

The research topic here would be to come up with something where the two parties have the same guarantees as the OP_CHECKSIGFROMSTACK & OP_CAT covenant but outside observes can't associate the on-chain data to the oracle or which event they were betting on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant