2020.02.04-08:00pm UTC-0 | next 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#9 2020.01.?? | consult with mafintosh
  • datdot-substrate#1 roadmapping
  • datdot-research#6 user accounts + (API & UI)
  • datdot-research#7 substrate validator set & costs for submitting extrinsics
• @ninabreznik
  • datdot-research#9 2020.01.?? | consult with mafintosh
  • datdot-service#2 make lab environment to reliably test scenarios
  • datdot-service#1 roadmapping
  • datdot-research#3 research proof-of-service
• @serapath
  • datdot-research#9 2020.01.?? | consult with mafintosh
  • datdot#22 spec: make presentable spec after public w3f wave4 announcement
  • datdot-research#1 roadmapping
  • datdot#1 roadmapping
• @fionataeyang
  • brand#2 Ideas of interaction design collection
  • datdot#2 datdot project landing page
• @RangerMauve
  • datdot-research#9 2020.01.?? | consult with mafintosh
  • datdot#24 encoding compatible hypercores
• @substack
  • ???

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

minutes

no recordings

[jam10o-new]

didn't catch y'all online if the call did happen - either way I guess I'll put a status update here and we can discuss it async, I guess:

haven't committed anything this week and my next two days are pretty much blocked, but I did have some solidification re: attestations, shouldn't need much update to api, other than maybe adding additional parameters to register attestations (for specifying registration of friends, if we want them to participate onchain at all) [correction/edit: friends should only need to register if they need to be reported, I think that this would need an additional vec in the storage value I describe below]

Weekend plans are figuring out if what Nina has been seeing is a bug - it's another off-by-one at worst - but in my ad-hoc testing in the apps UI I haven't been able to replicate it yet. After that is done, finishing off the hash types (blind until we have some reliable challenge response attempts, which is why I'm prioritizing the potential bug in challengeMap first), and then finally finishing off the first implementation of attestations.

Specifically: I have attestations as a tuple of two vecs which represent "required attestations" and "seen attestations". Anyone can make an attestation and be added to the seen set, but only once every required attestation has been added to the seen set are the votes of the required attestors counted and the challenge resolved based on the majority of them. I think I'll emit the state of all attestations as an event before clearing it from state so it can be reported to the UI - feedback welcome on format and info that would include.

things that might need clarification/context: the bug: seemingly we're seeing a challenge in the challengeMap with selectedUserIndex, challengeIndex set to 0 - this challenge is for the pubkey 0x0....0 (which is obviously invalid), chunk 0, with a deadline of 0 blocks. This should not be a possible/valid challenge.

[jam10o-new]

would probably be worthwhile to concretely determine what the blockers are for calling something a good "v1" next meeting.

[ninabreznik]

Quick short notes:

Updates

• @joshua-mir sharing snippet about the challenges process https://gist.github.com/joshua-mir/4ac7207360103bdd79a27cbd9a0d07a1
• @serapath sharing DatDot spec https://hackmd.io/lnHbg-sgTlaXfkVCcMM_MA?both
  • add Offer attesting
  • add Nominate as friend (Add friend?)
• @RangerMauve finished Intercept-hypercore-storage https://github.com/RangerMauve/intercept-hypercore-storage
• @ninabreznik shared first draft of UX concept https://www.draw.io/#LDaDot

Other

• try to use linter
• contact Dieter (Web3 foundation grants)
• make DatDot dictionary (hosters = dotters?, backers? etc.) => let's then together discuss
• Encoding/decoding math
• Docker
• Dashboard (get in touch with @substack)