You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Milestones: (A quarter is every six weeks with ~20hr work week)
- Q1:
- Be hands-on with Weaver asset exchange
- Complete literature survey on HTLC, fair exchange and distributed fault-tolerance
- Design proposal for fault-tolerant asset exchange between two Fabric networks in Weaver.
- Q2:
- Build the protocol for fault-tolerant asset exchange between two Fabric networks
- Design proposal for fault-tolerant asset exchange between different combinations Corda and Besu networks in Weaver.
- Q3:
- Build the protocol for Corda and Besu
- Q4:
- Design and build the protocol for automated asset exchange (or)
- 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) | - Some papers to start reading:
- MAD-HTLC
- Cross-chain Deals and Adversarial Commerce: https://arxiv.org/pdf/1905.09743.pdf
- Atomic Cross-Chain Swaps: https://arxiv.org/pdf/1801.09515.pdf
- Failure is (literally) an Option: Atomic Commitment vs Optionality in Decentralized Finance: https://arxiv.org/pdf/2109.12167.pdf
- A literature survey on attacks on HTLC
- Literature survey on analysis of cross-chain swaps and proposals for fault-tolerant cross-chain swaps
- Put paper summaries in GDoc, send to slack
- Send papers to slack channel to get approval as to whether or not they are relevant
- Propose fault models that are feasible to protect against in a cross-chain atomic swap (builds upon set 1)
- Fault model archetypes/schemas will be acquired as you read papers
- Make a master list of all fault models and then shortlist what is realistic
- Get feedback from slack based on what constitutes a fault model
- NOTE: Cryptography definitions may vary regarding fault models and/or their properties
- [LAG] Run 2x Fabric Networks + 1x Corda Network (Corda is MEMORY HEAVY) on the VM + 1x Besu test network + test Weaver implementation
- 1 pair of networks (ideally fabric/fabric) is sufficient to test #3
- [LAG] Project Plan on HLF Project Page (just timeline; 24 weeks total/6 weeks per quarter, 4 quarters total)
- [!!!] Set up remote access to your tower
- Fix Zenhub ticket reporting issue
|
Week 3 (Mobile/Research Heavy) | - TBD
|