2020.02.25-08:00pm UTC-0 | datdot sync

[serapath]

location + time zone converter

• https://talky.io/datdot
• https://gitter.im/playproject-io/community

place:	Honolulu	Vancouver	Ottawa	Berlin	Taipei
local time:	10:00am	12:00pm	15:00pm	9:00pm	4:00am

AGENDA

1. What was done since last meeting?

• @joshua-mir
  • datdot-research#6 user accounts + (API & UI)
  • datdot-research#7 substrate validator set & costs for submitting extrinsics
• @ninabreznik
  • datdot-service#2 make lab environment to reliably test scenarios
  • datdot-service#14 package datdot in docker app
• @serapath
  • datdot#22 spec: make presentable spec after public w3f wave4 announcement
• @fionataeyang
  • datdot#2 datdot project landing page
• @RangerMauve
  • datdot#24 encoding compatible hypercores

2. How do roadmapping priorities currently look like?
3. Create new meeting and plan what issues we will do until then
   • => 2020.03.03-08:00pm UTC-0 | datdot sync#35

minutes

no recordings

[ninabreznik]

Notes:

@RangerMauve

• check current encoding-hosting scenario code
• integrating existing new code to it
• refactor to use SDK
• adding missing parts to it (what are they?)
• add manual handling of different data structures
  => datdot-service#8 implement encoding-hosting-challenge flow and add a test scenario

@joshua-mir

• finish attestation
• adding logic for register as encoder, attester etc.
• add new substrate events etc. to hackMD with rust API
• proof format
  => datdot-substrate#20 make attestations & encoding-hosting-challenge flows work

@ninabreznik

• finish first version of the Dockerfile and make it work
• optimize it (@joshua-mir can help?)
  => datdot#14 package datdot in docker app
• update service for attestation logic + later for encoding etc. (plugging together code that will come from @RangerMauve )
  => datdot-service#8 implement encoding-hosting-challenge flow and add a test scenario
  => datdot-service#6 implement attestation flow and add a test scenario

@serapath

• finish the documentation
• update Github
• concept for DatDot landing page with @fionataeyang
• figure out which teams are building data structures based on hypercores => get in touch with them => propose simple standard idea & ask for feedback (individually) & on Consortium call => sum up all the feedback, update proposal of the standard => back to the teams for the update => bounce back & forth until consensus is reached
  • Cabal/Kappa folx (kappa/core irc => Nettle, Substack, Frando)
  • Mapeo (Substack)
  • Sonar (Frando) https://github.com/arso-project/sonar
  • Diego (libscie) https://libscie.org/ https://p2pcommons.com/
  • Ink & Switch (Peter van ...) https://github.com/inkandswitch/pushpin
  • Wireline (Geut)
    => datdot-service#7 standard for discovering related hypercores
    => datdot#22 spec: make presentable spec after public w3f wave4 announcement
    => datdot#2 datdot project landing page

@fionataeyang

• start working on DatDot landing page (download + documentation)
  => datdot#2 datdot project landing page