Fission server tasks breakdown

[bdehaynin]

All lists in this issue are non-exhaustive, feel free to add new entries and order them by priority.

Preliminary Questions

• What are our objectives for the next 6 months?
  • Build a new Fission server stack that's written in Rust
    so we can reuse and benefit from other Rust libraries,
    such as rs-ucan, rs-wnfs, rs-awake, etc.
  • Upgrade to the new UCANs across the ecosystem.
  • Passkey support, server needs to understand ECDSA signed UCANs.
• What dependencies does the Fission Server have?
  • Rust language
  • rs-ucan
  • CAR Mirror, optional, but better sooner than later.
    Fast short-term solution here is to upload CAR files via HTTP,
    where the calculation of what to upload is done in ODD.js
• What is a Fission account?
  A Fission account is an account registered on our Account Service
  which has an email address. If a DID is registered but without an email
  it is considered an app-owned-login.
• How will we publish apps?
  1. The app developer registers a Fission account.
  2. They add their app to their file system and publishes it.
  3. The app is now already accessible through the IPFS gateway.
  4. If they used the DNS naming service, it'll be available at a domain name.

Research

What topics still need to be investigated?

• What exactly are the interactions with ODD.js?
• What is a Fission account?
• Research how to provide paid accounts #114
• Research federation with other services #112
• Research Storage service solutions #111
• Investigate DNS solutions #110

Tasks to breakdown and prioritize

Set higher priority for tasks that are needed to complete Collector

Boxes for quick reorder:

• Organisation mono repo
  • Configuration management: https://crates.io/crates/config
  • Rust structure for Workspaces (separate crates)
• UCANs
  • Integrate rs-ucan
  • Ability to decode a DID, extract the public key and validate a UCAN
  • Support for various key types: ED25519, RSA, ECDSA (for passkeys)
• Account service
  • Database layer: deisel
  • Account DB table (DID, email)
  • Endpoint: user registration (provides a UCAN)
  • Endpoint(s) for creating / registering app accounts #103
  • Volume datamodel #104
• Channel service
  • Set up a websocket relay channel per DID (reference implementation) #105
• Storage service
  • Connect to an IPFS node #106
  • Endpoint: Download a block (requires UCAN)
  • Endpoint: Export a DAG by downloading a CAR file (requires UCAN)
  • Endpoint: Import a DAG by uploading a CAR file (requires UCAN)
  • CAR Mirror integration #107

Goals for MVP:

• Signups
• Ability to register DNS
• DIDs + UCANs

Milestones

1. MVP
   • July 31st
2. CAR Mirror integration

Past this - discover process with the ODD sdk, work on the dependencies, etc

Visual Roadmap

Figma

Documentation to write

• Research how to provide paid accounts #114
• Research federation with other services #112
• Research Storage service solutions #111
• Investigate DNS solutions #110

Resources:

• Components of the new Fission Server
• https://talk.fission.codes/t/context-for-a-very-odd-server/4484
• https://talk.fission.codes/t/fission-server-meeting-notes-ipfs-thing/4568
• UCAN and UX flows in Figma
• https://crates.io/crates/diesel-async

[expede]

[jeffgca]

Zeeshan: "use async diesel"