mirror of https://github.com/aljazceru/dlcspecs.git synced 2025-12-17 06:14:23 +01:00

Files

Nadav Kohen 7905d5e89a Tuesday September 1 2020 Meeting (#66 )

* Tuesday September 1 2020 Meeting

* Added some details

* Add C# impl

2020-09-08 15:46:15 -05:00

September 1st (7 PM CST)/2nd (9 AM JST) Meeting 2020

Secp256k1 Branch Progress

schnorrsig to be merged into secp256k1 soon (#558) after most recent BIP 340 change
ZKP Branch built on top of updated schnorrsig containing ECDSA adaptor sigs - upcoming
- ZKP to move to using secp256k1 as a git subtree instead of rebasing all the time
Temporary non-zkp branch with everything DLC's need on it (with stable APIs that will appear on the final zkp branch ... I think)
- Same branch but with JNI integration as well
- Rust Wrapper Branch

Size issue
- We are going to have messages much larger than allowed in LN
  - BOLT 8: "The maximum size of any Lightning message MUST NOT exceed 65535 bytes."
Related, Dual-Funding LN protocol has a lot of interaction that we likely don't want
- separate messages for each input and output added (sometimes with acks in between), as well as messages for removing inputs and outputs.
How do we want to structure Contract Info TLVs?
- How do we want to structure CET signature TLVs?
  - Copy order from Contract Info to save space?
- Can we make offers more compact by making part of one of Oracle Info or Contract Info implicit where it is derived from the analogous explicit version in the other one?
How do we want to structure Oracle Info TLVs?
- Enumerated Outcomes
- Ranged Outcomes
- Number Outcomes (R value per digit)
- Compound Outcomes?
  - A generalization of Number Outcomes to enumerations
- Rolling DLCs
How do we want to structure Funding Input TLVs?
- How do we want to structure Funding Signature TLVs?
Using Signatures vs. using Script Signatures?

We should merge #57 soon and begin iterating on it
- Open issues for unresolved things
We should merge #59 soon and begin iterating on it
- Open issues for unresolved things
Lloyd will write a doc like BIP 340 describing our variant of ECDSA Adaptor Signatures
Oracle specification in progress
- Are the two drafts going to be merged?
Someone should probably begin on a proposal for a spec doc like BOLT 5 which should, among other things
Specify when to double spend funding inputs (presumably some timeout after dlc_sign message sent)
- Pinning Issue
Specify fee-bumping mechanism (CPFP)
@ariard has volunteered to do this!
Discuss adding and suggesting Rationales
Anything else?

Lexicographical OP_CHECKMULTISIG ordering of funding public keys
anchor change outputs
Connection Handling and Multiplexing
Contract ID
TLV Streams
How should we encode fee rates? We moved from Sats/VByte to Sats/KW so we probably need more precision (bitcoind does 3 decimal points?)