---
tags: PM, archived
---

[toc]

# [ARCHIVED] Notes May 2020

# Research Projects
* Ethereum + IPFS projects
* 3Box
* TheGraph
*

## w/c 21-May-2020
*

## w/c 18-May-2020
* **Main focus: Research**
* What are the components we want to build? Demo roadmap: why are we building what we're building? See [Ben's slide deck](https://docs.google.com/presentation/d/1HgMGbzljtGHaHIWuzQrMAU84bXrzGG_Y0UJx0_k9fZs/edit#slide=id.g85745e0c87_0_0)
* What's being built now?
* What could we build that's useful? Check statusx
* Fully decentralised computation _requires_
* Co-ordination/Orchestration of resources
* Co-ordinating pointers to IPFS (contracts, multiple nodes executing the same thing, consensus on result(s))
* [Databus definition](https://en.wikipedia.org/wiki/Databus)
* **Lesser focus:** Refined version of presentation deck (that incorporates feedback from Jason/Renee from last week)
* See stand-up notes from 14/15-May
* "Competitive Landscape" deep dive
* What other projects have existed? What is/was their story?
* Planing for outreach conversations with TheGraph, Infura, Ocean, Audius?
* Plus informal conversations (Ben)
* Tweet "Calling all devs! ..."
* Make progress on building
* Components

## To be scheduled

* Channels: discord, github, Twitter, etc.
* Website plus tagline

---

# Stand-up Notes

## 19-May-2020
present: kevin, simona, ben

### Applications
Big data analysis, complex simulations, CGI rendering, machine learning and neural network training, AR/VR world building, and biosystems modeling are some potential areas where this type of computing gets useful.
https://www.skalex.io/decentralized-computing/

## 18-May-2020
present: kevin, simona, ben

## 15-May-2020
present: kevin, simona, ben

- start dev-interviews: (Ben+Simona)
- "How do you use Ethereum+IPFS in your project?"
- "What hurdles did you need to overcome?"
- Twitter copy: Calling all devs! Are you building on Ethereum + IPFS? I would love to know what the main hurdles you’re facing are. Is it speed? Is it complex dev work (Ben - fill in realistic stuff here)? I am really curious to understand the pain points. Here’s one of mine: @benjaminbollen
- talk to TheGraph, Infura, Ocean
- requires: mini-outline external directional doc
- ~~read-write + “internal” processing as Mosaic “extension”~~
- Competive Landscape
- Understand existing architectures better
- what's our unique insight
- dev updates:
- ring-write-logs extending single-writer-logs
- mosaic node doc https://hackmd.io/iHTAtIvmTuuP6KvWIS4MyQ?both

Dev-interviews

talk to TheGraph, Infura, Ocean
read-write + “internal” processing as Mosaic “extension”

## 14-May-2020
present: pro, kevin, simona, jason, renee, ben

* ~~Simplify title~~
* Improve Problem Statement plus incorporate the ‘Landscape’ $ slide
* Competitive Landscape
* ~~Split in two: Marketplaces vs Runtime/OS~~
* Ethereum, IPFS
* Add Infura, TheGraph, Textile
* Illustrate other and our architecture -- chocolate & peanut butter!
* Applications → change to Use Cases.
* Have 3-4 max, What, ~~Why~~, How
* Focus on today’s needs vs future needs
* Which developers need this today and how does it help them? (Infura + the graph: no execution layer, just interfaces to get data
* Reach out to Audius

## 13-May-2020 - Potential Applications
* Contact Tracing
* Smart Contract Wallet (L1, BTC…)
* Account Recovery (Social Recovery + 6-digit PIN)
* Contacts Chat App
* Music / Audius
* *GoogleDrive
* Maps (traffic, route-finding)
* Github on rings
* InterPlanetary Docker Registry (aka Docker Hub) on rings
* Pepo / Decrypt / Tolkin.me / other Ost projects