aljaz/dlcspecs
1
0
Fork 0
mirror of https://github.com/aljazceru/dlcspecs.git synced 2025-12-17 06:14:23 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
master
dlcspecs/meeting/meeting_october_6_2020.md
Nadav Kohen 90b9cb7463 Tuesday October 6 2020 Meeting (#101) 
* October meeting doc

* Made sighash comment less percise and hence less wrong

* Some updates

* Post meeting updates
2020-10-07 10:09:04 -05:00

5.2 KiB
Raw Permalink Blame History

October 6th (7 PM CST)/7th (9 AM JST) Meeting 2020

Housekeeping

  • There is a google form asking for feedback about our meeting format

Secp256k1 Branch Progress

  • schnorrsig merged into secp256k1 (#558)!
  • Updated temp-everything branches called new-temp-everything
  • ZKP Branch built on top of updated schnorrsig containing ECDSA adaptor sigs - upcoming
    • ZKP has new tooling allowing for merging upstream PRs, blockstream folks are in the process of updating ZKP to match upstream
    • Once this is done, I will be opening an ECDSA adaptor sig branch which will be permanent (until merged) and replace new-temp-everything branch
  • BIP 340 support for rust-secp256k1

Oracle Specifications

  • URI format proposal
  • Descriptor proposal
    • We have decided to move forward with the descriptor proposal where we will add a kind of event descriptor allowing for Lloyd's URI-based events
  • "Oracle Address" proposal
    • We have decided we want a serialized blob which can be copy/pasted that the oracle signs for each event
      • Nadav proposes we use TLV format to be inter-operable with P2P messaging, Ben will implement a proposal
  • Oracle Key Rotation/Public Key Infrastructure discussion
    • Everyone agrees that oracles should not have too many events for a single signing key
    • Everyone agrees that having multiple keys is part (or all) of the solution
    • Not everyone agrees about the idea of rotating publicly known keys

TLV and LN Message Format

  • Turns out these are two separate things and BOLT 1 is unanimously agreed to be vague and confusing
  • Matt Corallo suggests we use fragmentation if we want to be LN BOLT 8 compatible
    • This will likely require specification at some point, but may be general enough to end up in the BOLTs

P2P Network Considerations

  • LN doesn't solve all of the P2P problems we had assumed it does (like Network Address Translation)
  • Nicholas proposes we use existing TOR client infrastructure
  • Alternative is to have users set up their own port forwarding
  • Any other ideas?
    • BIP 324?
      • Impl not moving forward
        • Maybe Lloyd wants to do something about this?
      • Antoine doesn't like BIP 324

Specification Writing

Miscellaneous TODOs

Lightning DLCs

  • We have begun trying to support more general outputs on commitment transactions in eclair
  • Lloyd progress update on witness-asymmetric channels
  • Antoine progress update on general outputs in rust-lightning
  • Anyone else have anything to report?