Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Week 1

Hands-on with Weaver asset exchange:

Week 2 (Compute Heavy)

  1. Some papers to start reading: 
    1. MAD-HTLC
    1. Cross-chain Deals and Adversarial Commerce:  https://arxiv.org/pdf/1905.09743.pdf
    2. Atomic Cross-Chain Swaps: https://arxiv.org/pdf/1801.09515.pdf
    3. Failure is (literally) an Option: Atomic Commitment vs Optionality in Decentralized Finance: https://arxiv.org/pdf/2109.12167.pdf
    1. A literature survey on attacks on HTLC 
    2. Literature survey on analysis of cross-chain swaps and proposals for fault-tolerant cross-chain swaps 
    3. Put paper summaries in GDoc, send to slack
    4. Send papers to slack channel to get approval as to whether or not they are relevant
  2. Propose fault models that are feasible to protect against in a cross-chain atomic swap (builds upon set 1)
    1. Fault model archetypes/schemas will be acquired as you read papers
    2. Make a master list of all fault models and then shortlist what is realistic
    3. Get feedback from slack based on what constitutes a fault model
    4. NOTE: Cryptography definitions may vary regarding fault models and/or their properties
  3. [LAG] Run 2x Fabric Networks + 1x Corda Network (Corda is MEMORY HEAVY) on the VM + 1x Besu test network + test Weaver implementation
    1. 1 pair of networks (ideally fabric/fabric) is sufficient to test #3
  4. [LAG] Project Plan on HLF Project Page (just timeline; 24 weeks total/6 weeks per quarter, 4 quarters total)
  5. [!!!] Set up remote access to your tower
  6. Fix Zenhub ticket reporting issue


Week 3 (Mobile/Research Heavy)

  1. (In-meeting) Review papers and establish consensus on critical semantics
  2. Determine abstractions for fault-models
  3. Review paper #3


Week 4 

  1. (In-meeting) Review papers and establish consensus on critical semantics
  2. Determine abstractions for fault-models
  3. Review paper #3


Week 5 

  1. Discussion of importance of two-phase commit; fundamental basis of other interoperability options (cross-chain swaps, cross-chain deals, etc.)
  2. Discussion on further refining fault model


Week 6 

  1. Discussion on further defining fault-model
  2. Discussion on Cross-Chain payments with success guarantees, formalized model of verifiably correct cross-chain swaps


Week 7 

  1. Finish discussion on formalized model of verifiably correct cross-chain swaps


Week 8 

  1. Acquire critique on current protocol for fault-tolerant cross-chain swaps


Week 9 

  1. Iterate on current protocol to refine security guarantees


Week 10 

  1. Finalize v1.0 of Byzantine Swaps: our current Byzantine Fault Tolerant HTLC Protocol
  2. Determine features to utilize to solve key problems, involving but not limited to:
    1. Weak Denial-Of-Service (DoS)
    1. problem
    2. Strong Formal Guarantees (Atomicity, Safety, Liveness)


Week 11 

  1. Architectural call on how to implement specific facets of protocol atop Hyperledger Weaver’s features
  2. Where to look regarding files to modify for Fault-Tolerant Hyperledger Fabric + R3 Corda Asset Swap
TBD