You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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:
Provider and account system so users can log into the website, recover passwords, etc.
Log system to be able to track usage, implement metrics
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
storacha-network/w3infra#9:
store/*
andupload/*
flows with w3up-client + using access^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 spec for providers (⛰ epic)
Team: @hugomrdias @vasco-santos @gobengo
Tasks
./update
#349implement spec for accounts (⛰ epic)
Team: @hugomrdias @gobengo @alanshaw
Motivation: cross application key sharing & verification once per agent not once per space
Tasks
access/delegate
inaccess-api
#393access/claim
inaccess-api
#394access-client
#395create keyring site (⛰ epic) (DESCOPED)
Team: @olizilla @travis @alanshaw @hugomrdias
Requirements for MVP
w3console (⛰ epic)
Team: @travis @olizilla @yusefnapora
w3ui
HeadlessUI
& CustomizableUI for Reactas
property in headless components w3ui#235keyring-core
(w3console
Motivation: to get beta w3console shipped
Reference docs:
user stories
diagram
product meeting
product requirements
beta.console.web3.storage
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
Filecoin pipeline: CAR aggregator for space
Team: @vasco-santos @Gozala @alanshaw
w3filecoin
scafoldw3filecoin
Data stack feat: base implementation of data stack w3filecoin-infra#9commP
support in client Add field to store/add to include commP #353w3filecoin
Consumer Stackw3filecoin
integrate with Spadecheckup
Motivation: new CIDs are not being checked
docs
P0
Update readme and docs to use new capabilities package #326
spec for current store and upload protocols specs#40
P1
🟡 P1
w3console
Team: @travis @olizilla @yusefnapora
w3ui
HeadlessUI
for Vue & Solid (adaptation of React base in fix: upload/add capability root validation #136)CustomizableUI
for Vue & Solid (adaptation of React base in fix: upload/add capability root validation #136)HeadlessUI
&CustomizableUI
to w3ui websitepublicly 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
🏁 DONE 🏁
Phase 3 tickets:
#353
The text was updated successfully, but these errors were encountered: