[Tracking] w3up phase 2

[heyjay44]

Phase 2

Summary

Phase 2 will run until Friday February 3rd and has been broken down by priority:
🔴 P0
🟡 P1
🟢 P2

What success looks like for this phase:

1. Provider and account system so users can log into the website, recover passwords, etc.

2. Log system to be able to track usage, implement metrics

3. w3ui and w3console so users can in use a web console with w3up

---

🔴 P0

metrics and logs

• examine kinesis logs @jchris @vasco-santos

• get w3access to feed into kinesis

• Unify UCAN API endpoints @gobengo @Gozala

w3infra integration tests

Team:
@vasco-santos (primary)
@hugomrdias (support)

Motivation: guarantee no regressions exist when independent systems are updated storacha-network/w3infra#9

• Decide on setup for integration tests test: integration tests setup w3infra#122

storacha-network/w3infra#9:

• Test store/* and upload/* flows with w3up-client + using access
  • Test DUDEWHERE
• Test flows on CARPARK write event
  • Car replicated
  • Side Index created + replicated

^also tracked by this ticket from Phase 1 #152

implement receipts

Team: @Gozala @gobengo

Motivation: Accurate accounting e.g. generate a receipt for upload received

• Implement receipts 🧾  ucanto#151
• align with spec (draft)
• Should we support non DID principals ? ucan-wg/spec#139
• Addressing individual task results as opposed to invocations ucan-wg/invocation#6
• allow receipt for uploaded CAR
• Websocket(?) API to subscribe to “status receipts” (tracking an upload through the system)

implement spec for providers (⛰ epic)

Team: @hugomrdias @vasco-santos @gobengo

Tasks

• Improve email template in postmark to include location information from CF headers, agent information and validation phrase #347
  • validation phrase should be printed in the agent requesting the email flow
• Research and avoid SafeLinks and other auto open email client stuff #348
• Move validation websocket logic to a durable object #293
• Move Postmark email to web3.storage domain instead of dag.house #341
• implement provider/get and consumer/add with ./update #349
• implement provider/add for the smaller flow #350
• Add a report button to the template #371

implement spec for accounts (⛰ epic)

Team: @hugomrdias @gobengo @alanshaw

Motivation: cross application key sharing & verification once per agent not once per space

Tasks

• Make a worker that can be mounted in several URL paths to server DID web documents #384
• Implement access/authorize cap #385
• Implement access/authorize email flow in access-api #386
• Implement access/delegate in access-api #393
• Implement access/claim in access-api #394
• Implement w3access and w3session in access-client #395

create keyring site (⛰ epic) (DESCOPED)

Team: @olizilla @travis @alanshaw @hugomrdias

Requirements for MVP

• with w3ui

w3console (⛰ epic)

Team: @travis @olizilla @yusefnapora

w3ui

• testing add tests w3ui#150
  • add unit tests for React components w3ui#223
  • add integration tests w3ui#222
• ship HeadlessUI & CustomizableUI for React
  • headless feat: "Headless" UI components w3ui#136
  • customizable feat: Customizable UI components w3ui#208
    • support as property in headless components w3ui#235
• integrate keyring site into keyring-core (⚠️ dependency on accounts spec work) integrate keyring site into Authenticator customizable component w3ui#226

w3console

Motivation: to get beta w3console shipped

Reference docs:
user stories
diagram
product meeting
product requirements

• is it possible to have a super-sugar API? w3ui#120 @travis
• design work for console site
  • user flows for console @jchris
  • update w3console theme to align with that of w3ui w3ui#134 @cmunns
  • when is it possible to have a super-sugar API? w3ui#120 is complete, @cmunns can begin work on the layout/design
• build MVP using w3ui
  • Space explorer
    • space manager customizable component w3ui#227
    • add space picker to w3console w3ui#230
  • DnD uploader (requirement: always visible)
    • add customizable drag-and-drop uploader w3ui#228
    • add drag-and-drop uploader to w3console w3ui#231
  • Paginated uploads list
    • make sure pagination works as expected in the headless and customizable components w3ui#229
    • add paginated uploads list to w3console w3ui#232
  • Bucket UI (?)
    • add bucket UI to w3console w3ui#233
  • Keyring site integration
    • integrate keyring site into Authenticator customizable component w3ui#226
    • integrate keyring site into w3console w3ui#234
• ship to beta.console.web3.storage
• update existing website to guide users to new console (end of Phase 2/start of Phase 3)

Getting off IPFS Cluster

Team: @blucas @olizilla @alanshaw

Motivation: cost saving, scalability, be in charge of our own infra

Proposal: https://hackmd.io/@olizilla/Bk-NMVQ9o

• Rollout Pickup Migrate data from IPFS Cluster web3-storage/backup#1
• Migrate data from IPFS Cluster to S3 buckets Migrate data from IPFS Cluster web3-storage/backup#1

Filecoin pipeline: CAR aggregator for space

Team: @vasco-santos @Gozala @alanshaw

• Align on proposal https://hackmd.io/@vasco-santos/BJ_-zDVqj
• w3filecoin scafold
• w3filecoin Data stack feat: base implementation of data stack w3filecoin-infra#9
• commP support in client Add field to store/add to include commP #353
• w3filecoin Consumer Stack
• w3filecoin integrate with Spade

checkup

• update checkup bucket for nft/web3 @blucas @alanshaw @gobengo
  Motivation: new CIDs are not being checked
  • Add support of multiple buckets

docs

P0

• blog updates reflecting changes to w3up here: blog updates web3-storage/web3.storage#2184 @yusefnapora
• Capabilities package READMEs
• quick start guide @yusefnapora
• new docs website create new docs website web3-storage/web3.storage#2190
• update technical docs so that users can pickup and use our kit
• add account recovery to access-client and w3up-client (note: we should focus on w3up-client, less access since that is where folks should go) @yusefnapora
• spec for store / upload
  Update readme and docs to use new capabilities package #326
  spec for current store and upload protocols specs#40

P1

• figure out how to layer in user owned / app owned spaces
• headless UI docs @yusefnapora
  • add components to markdown docs: chore: add headless react components to markdown docs w3ui#241
  • update react examples to use headless components
  • update react examples on w3ui website
• flowchart draft for docs site. Structure based on user stories (different sections/flows based on needs)
• different user guides with user-friendly language

🟡 P1

w3console

Team: @travis @olizilla @yusefnapora

w3ui

• add HeadlessUI for Vue & Solid (adaptation of React base in fix: upload/add capability root validation #136)
• add CustomizableUI for Vue & Solid (adaptation of React base in fix: upload/add capability root validation #136)
• add overview of HeadlessUI & CustomizableUI to w3ui website

• publicly verifiable timestamps for UCAN invocations @alanshaw @Gozala @hugomrdias
  Motivation: feat: add spec for publically verifiable timestamps for UCANs with drand specs#27

• Add UnixFS directory sharding web3-storage/w3up-client#54 and Add support for HAMT directories ipld/js-unixfs#37 @Gozala @alanshaw @gobengo
  Motivation: support for 10k NFT drops

• CAR retrieval by CAR CID @gobengo @Gozala
  Read CAR by CAR CID #274
  Motivation: verifiable downloads ✅

• UCAN log stream consumer for billing @vasco-santos @hugomrdias @gobengo @Gozala
  (last piece of billing work before Stripe integration can begin)

🟢 P2

• UCAN log stream consumers @vasco-santos @Gozala
  - Metrics wanted UCAN Log stream consumers w3infra#117
  - Queryable DB

• UCAN S3 log issue @vasco-santos @alanshaw
  - Multiple invocations for the same UCAN has write freq limitations

• ability to easily delegate a subset of perms to a UCAN

• Rebasing nft.storage on top of web3.storage #167

  • make NFT . Storage consumer of new services
  • make using w3ui
  • setup consumer
  • backup to NFT. Storage feature

🏁 DONE 🏁

Phase 3 tickets:
#353