---
# System prepended metadata

title: Product <-> OSE Convergence Presentation Brain Dump

---

# Product <-> OSE Convergence Presentation Brain Dump

# Topic 

![topic](https://i.imgur.com/HMLOarj.png)


# Intro - Slide 0
Alright, so we heard about our plans for a full featured wallet from Mike. We also got a thorough rundown from Emily and Becca of what's next for Product. So, how do we take that and chart a path towards what we envisioned in the tbDEX white paper?

Let's:
1. do a quick recap of where product eng. is currently at.
2. run through a quick overview of the current state of Open Source
3. Remind ourselves what the result of product <-> ose convergence looks like: AKA tbDEX
4. Discuss **where** convergance starts to surface up to end-users 
5. Discuss **how** we get there



# Slide 1 - Product Eng.

Product Eng. Decision Matrix

```mermaid
stateDiagram-v2
  s0: v0 Janky
  note left of s0
    We are Here
  end note
  s1: What are we building?
  s2: Developer API
  s3: Who is our target audience?
  s4: Cash App Remittances 
  s14: BTC 100
  s5: Any / All Developers
  s6: What kind of Developer API?
  s7: Traditional Stripe/SQ style
  s8: tbDEX PFI Style
  s9: KYC/KYB?
  s10: Traditional
  s11: SSIDV
  s12: With DWNs
  s13: Without DWNs
  
  s0 --> s1
  s0 --> s3
  s1 --> s2
  s3 --> s4
  s3 --> s14
  s3 --> s5
  s2 --> s6
  s6 --> s7
  s6 --> s8
  s7 --> s9
  s9 --> s10
  s9 --> s11
  s8 --> s12
  s8 --> s13
```

* Product. Eng. is setting out to build a Developer API that can be leveraged to facilitate remittances with an initial focus on US <-> Mexico. 
* Three target audiences all with different requirements and appetites for decentralization
  * Cash App Remittances
    * "traditional" target audience looking to facilitate strictly USD -> MXN
    * Likely won't want to surface USDC let alone DIDs VCs
  * BTC 100
    * :warning: _Include description of BTC 100_
  * Any/All developers (tbDEX PFI Style)
    * DIDs (Routing)
    * VCs (Trust)
    * DWNs (Messaging Layer)
* Setting out to tackle the more traditional target audiences first. Why?
  * No one is using DIDs 
  * No one is issuing or accepting the type of VCs needed
  * Messaging layer has yet to be proven out
* At this current moment in time, requiring developers to use DIDs, VCs, and DWNs to use the Remittances API is far too large of a deterrant. Can't see Ryan Budd's remittances efforts buying into all of that so that current Cash App users can send money to Mexico without the slightest hint of USDC 


# Slide 2 - Open Source

:warning: _TODO: High level description of 3 Phases of [Are We Web5 yet?](https://www.notion.so/tbd54566975/WIP-Are-We-Web5-Yet-24af7f5cab93430da77add221c928cd4)_

Phase 1 is titled "Foundations". Goal is to release everything needed for developers to build simple "offline" (aka no cloud DWN present) DWeb Apps. This includes:
- Initiate passwordless registration / login flows using DIDs (DIDs + Janky Wallet)
- Issue Verifiable Credentials to users (SSI Service + Janky Wallet)
- Request verifiable Credentials from users (SSI Service + Janky Wallet)
- Request access, read, write, and subscribe to independently verifiable user data (DWN + Janky Wallet)


By the end of phase 3 (Est. Bitcoin Conf 2023) OSE aims to:
- Introduce highly available DWNs into the picture to enable p2p web5 apps including decentralized service & data discovery (e.g. finding all PFIs, Issuers etc.)
- Charted out a path for web5 on mobile


# Slide 3 - Product + OSE = tbDEX

_Refresh our memory on what the end goal is_

:warning: _TODO: Include Visual Diagram for tbDEX_

# Slide 4 - Where does this all come together?
A Wallet! People need:
* DIDs
* A way to apply for, store, & present Verifiable Credentials
* A way to discover and communicate with PFIs in a decentralized manner

Wallet provides all of this


# Slide 5 - How do we get there?

:bulb: = convergence point

* Remittance API accepts VCs for KYC / CDD / ECCD
  * Continue spearheading foundational/standardization efforts around KYC VCs 
  * Running SSI Service in production :bulb:
  * Risk Systems accept VCs as inputs :bulb: 

* Remittance API is discoverable through a decentralized network
  * Running production ION Nodes :bulb:
    * to reliably anchor and resolve DIDs

* Remittance API becomes back office rails for **our own PFI**
  * formalize & standardize tbDEX messages :bulb: 
  * Send/Receive tbDEX messages through decentralized messaging layer
    * Running production DWN Relay for our own PFI :bulb: 
    * Productionized DWN Provider for all wallet users :bulb: 


# Slide 6 - Big Questions
* Where do wallet efforts live?
* Who carries the responsibility of running services that OSE has built in a production setting?
  * ION nodes
  * SSI Service
  * DWNs
  * 