2023-03-09 TSC Meeting Notes

Owned by Nathan Southern
Last updated: Mar 09, 2023

Date

ZOOM Meeting Information:

Thursday, Mar. 9, 2023, at  9am PT/12pm ET


Join Zoom Meeting

https://zoom.us/j/7904999331

Meeting ID: 790 499 9331

Attendees:

TSC Voting Members Attendance:

Meeting Agenda:

  1. Call to Order 
  2. Anti-Trust, Review of TSC Meeting format and Participation by TSC Chair
  3. Introductions
  4. TSC Activity Desk
    1. Architecture Working Group (SeanB)
      1. Call for AWG Co-Chairs 
    2. RRDMWG Update (PeterA)
    3. AAIS Stat Reporting using openIDL internal Project (PeterA)
    4. ND Uninsured Motorist POC (KenS)
    5. MS Hurricane Zeta POC (KenS) 
    6. openIDL Testnet update (JeffB)
      1. Auto Stat plan POC (a.k.a., "AWG Architecture POC" )
    7. Infrastructure WG (SeanB)
  5. Introducing an Infrastructure Partner Prospect - Kaleido (LanayaN)
  6. AOB

FOLLOW UP:

  •  

Recording/Meeting Minutes

I. Introductory Comments

A. LF AntiTrust - Sean Bohan

B. Introductions by all participants

II. Agenda -

A. TSC Activity Desk

  1. AWG Recap - excellent meeting on Monday
    1. Reduction of time from 2 hrs. every Monday to an hour every Monday
    2. Great chat on GT2 and Aurora and how it might apply to openIDL - Peter Antley
    3. Next week Joseph may be presenting on the discovery work he's been doing
    4. Still live call AWG for co-chairs - former chair Satish Kesala (The Hartford) rejoined the last as participant
  2. RRDMWG Update - Peter Antley
    1. Working on productionizing ETL/decoding job req'd for personal auto. Standing by and ready to provide assistance to Hartford & Trvl when they produce their test data
    2. Getting test data loaded into nodes
    3. AAIS is on a 2-week sprint - end of sprint right now. Story for sprint next week. PA will quantitatively plot out roadmap for next year. 
    4. Foresees producing reg reports by the end of the year but wants to get more systematic about this planning.
    5. Concrete estimates on ETAs and a timeline forthcoming
    6. Timeline to be presented at next TSC
  3. ND POC - Ken Sayers
    1. Broad overview of ND POC objectives & results so far - grew out of the knowledge that 15% of people on road in ND are uninsured, etc.
    2. Second report sent - DOT currently analyzing report to grasp gap between show of registered VINs and actual registered VINs
    3. ND POC great proven tool for exposing data quality issues 
    4. Currently collecting data for second month. Third report in April
    5. Then it will be closed off and team will determine next steps
  4. Mississippi Hurricane Zeta POC Update - Ken Sayers
    1. Broad overview of Zeta POC objectives so far - large carrier working with MS DOI to reproduce a report through openIDL concerning Hurricane Zeta
    2. Will also contract with Crisis Track to correlate damage reports with insured information about the locations in MS to get better insights and provide feedback to insured about damage reports
    3. Triangulation of different parties to build this POC
    4. Currently in the planning stage. Hasn't begun execution yet.
  5. Testnet Update - Jeff Braswell
    1. Outreach to carriers for contributing data - for next stage of integrating data into currently upgraded Test Net architecture based on HL Fabric Operator
    2. About to connect the teams to begin taking the steps toward running said test data through architecture Peter has developed with Senofi
  6. IWG Update
    1. Co-chairs Yanko and Aashish
    2. Group meets every other week same time slot (Thursdays at noon) as the TSC.
    3. Last week: group discussed experiences of Senofi team - creation of testnet  - reasons behind HL Fabric Operator as opposed to alternative
    4. Currently working on topic for next call on 3/16 12pm EST - topic will be developed with chairs today for that meeting

III. Kaleido Presentation

A. Background from S. Bohan -

  1. Member of HL foundation 
  2. Contributors of Firefly
  3. Doing great work evangelizing Firefly and how it is used 
  4. As such they are running a growing OSS project, and doing the leg work necessary to get people to use the code but also contribute and become part of the community that is building Firefly
  5. Lanaya has been in discussion with Kaleido team for a couple of months
  6. They are a prospective infrastructure partner

B. Presentations by Sofia and Andrew

  1. Sofia
    1. Started with Kaleido team on the IBM side - working with Chainyard when they were IT people working alongside teams for component delivery
    2. Had ownership of IBM blockchain platform
    3. Decided to do the delivery in the open - moving it away from closed source.
    4. Took open blockchain code to LF which became HL Fabric
    5. Helped start the HL community and brought in Brian Behlendorf.
    6. Launched industry's first blockchain-managed service - running a node as a service
    7. Spent two years on the Gen 1 approach to building networks. Believed companies needed governance/much easier way to adopt Web3 technologies. Node only 5% of the total solution. People needed a plug-and-play stack - product-led - Gen-1 deployments - very heavy consulting, custom code, 20-50 mil average price tags - can do what Gen 1 did at a fraction of the cost with the product led approach
    8. Kaleido has pioneered 500+ APIs, 40+ plug and play services. 
    9. Very strong proponents of OSS 
    10. A layer that didn't exist in OSS community - hundreds of layer ones and some assorted tooling but needed the on-and-off chain stack of technologies to get transactions on and off blockchain, exchange private data, etc. This is the firefly stack
    11. Early on - Kaleido partnered with AAIS & Microsoft. 
    12. Onboarded a number OSS technologies that enterprises want to run
    13. All about making Web3 digital access radically simple for enterprise 
    14. Only ones with consortium of service. Spans a myriad of industries, geographies. Also a strong interest in insurance.
    15. Right out of the box - very rich features that any enterprise project will need - clickable and deployable - Kaleido provides SLAs, run manage and support this for clients.
    16. Various chain options from private and consortium to app chains and public. Meeting tools
    17. Offerings as well higher up on value stack.
    18. Everything in the Kaleido UI has an API behind it - very useful for getting stakeholders aligned with the initial phases of a project





    1. Longstanding company - specializing in infrastructure. Recently Microsoft brought ethereum chains to them
    2. Heavily invested in compliance
    3. Connected to SMEs across numerous industries
    4. Scale & performance testing across thousands of chains daily. Upgrades running constantly
    5. Represent enterprise networks and clients at respective standards bodies.
    6. Working internationally - a constellation of different use cases, new tech stack required.
    7. Seeks to be a one stop platform for enterprises moving into Web3
  2. Case studies - a few examples to demonstrate Kaleido's capability and versatility. 
  3. Demo - Andrew - to illustrate the types of work done by Kaleido in the Web3 Consortium space
  4. :



Discussion Items:



TimeItemWhoNotes




Goals:


Action Items: