Harmonia Technical Status Call ‐ 2023‐07‐25

Attendees

• Adhara
• R3

Notes

• Adhara update

  • Meeting with a stakeholder went well. Feels like alignment on approach, desire to contribute, but practical reality is that they’re snowed under
  • Another stakeholder on board to contribute a more detailed document on principles – Peter helping draft. Possible delay owing to key person's availability but hoping to get it in soon.
  • Code to generate block headers (to complement the existing verification code) will be contributed shortly
  • Looking at Firefly as a potential component to incorporate into design to provide gateway functionality
  • Simulated Corda network with unencumbered (from IP perspective) contract to be contributed when time/resource allows

• R3 update

  • Working on whitepaper
  • Has updated proposed protocol to eliminate the ‘hold-up’ problem
  • Working on some EVM contracts against which we can test
  • ACTION: Adhara, if possible, to prioritise sharing the ERC-2020-like contracts they already have in order to avoid duplication here?
  • Maintaining a fork of web3j owing to some specific Corda constraints
  • Modifying web3j to work inside the constrained C5 runtime

• Moving Harmonia forward

  • Agreement that our preferred outcome remains converging with / influencing one of the major open projects. But too early to know how quick/easy that will be
  • Agreement that there needs to be a sequencing – get support/validation from a broader set of financial markets networks prior to being confident in advocating for our viewpoint with the major interop implementation projects
  • ACTION: R3 to propose next level of detail for execution of above

• NEXT MEETING: Drill in to the exact status/purpose of the code each team is working on but has not yet contributed… how close are we to being able to schedule a hackathon of sorts to bring it together?