Versions Compared

Old Version 1

changes.mady.by.user Francis Mendoza

Saved on

compared with

New Version 2

changes.mady.by.user Francis Mendoza

Saved on

Key

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

Milestones: (A quarter is every six weeks with ~20hr work week)

  1. Q1: 
    1. Be hands-on with Weaver asset exchange
    2. Complete literature survey on HTLC, fair exchange and distributed fault-tolerance
    3. Design proposal for fault-tolerant asset exchange between two Fabric networks in Weaver.
  2. Q2:
    1. Build the protocol for fault-tolerant asset exchange between two Fabric networks
    2. Design proposal for fault-tolerant asset exchange between different combinations Corda and Besu networks in Weaver.
  3. Q3:
    1. Build the protocol for Corda and Besu
  4. Q4:
    1. Design and build the protocol for automated asset exchange (or)
    2. Start writing a research paper with a formal analysis of our protocol on fault-tolerant asset exchange if we find enough novelty wrt state of art.

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. TBD