aljaz/dlc-intro
1
1
Fork 0
mirror of https://github.com/aljazceru/dlc-intro.git synced 2025-12-17 22:14:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Typos

Browse Source
This commit is contained in:
Gregor Pogačnik
2021-09-15 14:22:30 +02:00
parent b6476861d3
commit eacfad882f
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -1,7 +1,7 @@
# dlc-intro # dlc-intro
A gentle introduction to Discreet Log Contracts (DLCs) on Bitcoin A gentle introduction to Discreet Log Contracts (DLCs) on Bitcoin
They offer a way to implement financial smart contracts on Bitcoin and what is more I believe they could also be used directly via Lightning They offer a way to implement financial smart contracts on Bitcoin and what is more I believe they could also be used directly via Lightning channels.
Outline: Outline:

6
dlc.md
View File

@@ -1,10 +1,11 @@
## Discreet Log Contracts ## Discreet Log Contracts
is a wordplay on the "discrete logarithm problem" and the fact that oracles are discreet - they are not even aware of the actual bet. It was presented in the paper [Discreet Log Contracts](https://adiabat.github.io/dlc.pdf) by Thaddeus Dryja who is also one of the creators of lightning network. is a wordplay on the "discrete logarithm problem" and the fact that contracts are discreet. There is no sign of a smart contract on the blockchain. Also the oracle is not aware of who is using his data. The scheme was presented in the paper [Discreet Log Contracts](https://adiabat.github.io/dlc.pdf) by Thaddeus Dryja who is also one of the creators of lightning network.
### Refresher ### Refresher
s = k - h * d s = k - h * d
R = k*G R = k*G
### Operations ### Operations
@@ -33,7 +34,8 @@ Before that block is transmitted to the blokchain they make sure each peer signs
Alice bets on "heads" and creates an output that can be spent using private key ai Alice bets on "heads" and creates an output that can be spent using private key ai
Public key Ai is defined as A + sHEADS * G Public key Ai is defined as A + sHEADS * G
so it is her public key but skewed e that (sHEADS * G) which is publicly known (depending on R from Olivia). so it is her public key but skewed with (sHEADS * G) which is publicly known (depending on R from Olivia).
Bob verifies that the value is correct and signs the transaction Alice gave him (since he knows Alice can't possibly know the private key and will know it just if she won) Bob verifies that the value is correct and signs the transaction Alice gave him (since he knows Alice can't possibly know the private key and will know it just if she won)
Then also Bob creates a spend from the multisig: he uses bi and in the tx you can see public key Bi which is B + sTAILS * G. Now Alice verifies the same way and eventually signs. Then also Bob creates a spend from the multisig: he uses bi and in the tx you can see public key Bi which is B + sTAILS * G. Now Alice verifies the same way and eventually signs.