Francis Mendoza, fmendoza@ripple.com, Ripple Labs (RippleX team) - United States
Venkatraman Ramakrishna, vramakr2@in.ibm.com, IBM Research - India
Krishnasuri Narayanam, knaraya3@in.ibm.com, IBM Research - India
Dhinakaran Vinayagamurthy, dvinaya1@in.ibm.com, IBM Research - India
Sandeep Nishad, sandeep.nishad1@ibm.com, IBM Research - India
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
- Atomic Cross-Chain Swaps
- Atomic Commitment vs Optionality
- 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
- 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
- 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) | - (In-meeting) Review papers and establish consensus on critical semantics
- Determine abstractions for fault-models
- Review paper #3
|
Week 4 | - (In-meeting) Review papers and establish consensus on critical semantics
- Determine abstractions for fault-models
- Review paper #3
|
Week 5 | - Discussion of importance of two-phase commit; fundamental basis of other interoperability options (cross-chain swaps, cross-chain deals, etc.)
- Discussion on further refining fault model
|
Week 6 | - Discussion on further defining fault-model
- Discussion on Cross-Chain payments with success guarantees, formalized model of verifiably correct cross-chain swaps
|
Week 7 | - Finish discussion on formalized model of verifiably correct cross-chain swaps
|
Week 8 | - Acquire critique on current protocol for fault-tolerant cross-chain swaps
|
Week 9 | - Iterate on current protocol to refine security guarantees
|
Week 10 | - Finalize v1.0 of Byzantine Swaps: our current Byzantine Fault Tolerant HTLC Protocol
- Determine features to utilize to solve key problems, involving but not limited to:
- Weak Denial-Of-Service (DoS) problem
- Strong Formal Guarantees (Atomicity, Safety, Liveness)
|
Week 11 | - Architectural call on how to implement specific facets of protocol atop Hyperledger Weaver’s features
- Where to look regarding files to modify for Fault-Tolerant Hyperledger Fabric + R3 Corda Asset Swap
|