aljaz/dlcspecs
1
1
Fork 0
mirror of https://github.com/aljazceru/dlcspecs.git synced 2026-01-31 11:44:29 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #34 from AdamISZ/minor-edits-1

Browse Source 
typos in Protocol desc
This commit is contained in:
Nadav Kohen
2020-03-24 08:58:08 -06:00
committed by GitHub
parent 0fc2e66d00 50f73546a8
commit 5f6c02d882
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Protocol.md
View File

@@ -110,7 +110,7 @@ The following public keys:
1. Funding Public Key
- B's public key used in the multi-signature [funding output](Transactions.md#FundingOutputs)
2. Sweep Public Key
- A's public key used in the creation of the CETs [output script](Transactions.md#CETOutputs).
- B's public key used in the creation of the CETs [output script](Transactions.md#CETOutputs).
#### B's addresses
@@ -194,13 +194,13 @@ We distinguish between user validation, performed by the user (through a user in
At any point in the protocol up until the sending of the `sign` message, both parties can safely decide to cancel the contract.
An empty `cancel` message can be used to inform the other party of the desire to cancel the contract.
If one of the party doesn't send a message after a given timeout, the other party should assume the contract to be canceled.
If one of the parties doesn't send a message after a given timeout, the other party should assume the contract to be canceled.
Timeouts should be proportional to the number of possible outputs of the contract, as the signing and verification of the CET signatures is expected to be the bottleneck.
After party A sends the `sign` transaction, they cannot unilaterally cancel the contract anymore.
If they want to cancel the contract, for example because of not observing the fund transaction in the Bitcoin network, they can try to do so by broadcasting a transaction spending at least one of the UTXO specified in the fund transaction.
After party A sends the `sign` message, they cannot unilaterally cancel the contract anymore.
If they want to cancel the contract, for example because of not observing the fund transaction in the Bitcoin network, they can try to do so by broadcasting a transaction spending at least one of the UTXOs specified in the fund transaction.
If this transaction gets included in the blockchain prior to the fund transaction, the contract will be canceled as this will have rendered the fund transaction invalid.
In the even that the fund transaction gets included first, both party will be bound to the contract.
In the event that the fund transaction gets included first, both parties will be bound to the contract.
# Authors
Takatoshi Nakagawa

2
Transactions.md
View File

@@ -83,7 +83,7 @@ Where
OP_ENDIF
OP_CHECKSIG
- Note that The addition in the if case is elliptic curve point addition
- Note that the addition in the `IF` case is elliptic curve point addition
- `ToRemoteOutput`'s script corresponds to `Remote CET Final Address`
## Refund Transaction