Alan Shaw

@alanshaw

Joined on Apr 9, 2018

  • Welcome to the self directed learning programme for Saturn devs! Developers are encouraged to explore and learn using this framework as a guide. Collect questions and areas where you need clarification and bring to the AMA sessions. :::warning ⚠️ In week 1 you should aim to cover chapter 1 and 2. ⚠️ In week 2 you should aim to cover chapter 3 and 4. ::: Each chapter has a challenge, consume the materials and then attempt to complete the challenge.
     Like  Bookmark
  • Phase 3 finishes on Mar 10. Try for Mar 17. Absolute deadline Mar 24. Lets close out phase 3! This is the list of things we need in place to get to the finish line 🏁 [x] Push UCAN invocations from access-api into kinesis @vasco[x] Store UCAN invocations in S3 [x] HTTP API receives UCANs [x] Finish off UCAN kinesis consumers for metrics @vasco
     Like  Bookmark
  • This document describes a simple UCAN service allowing an implementor to receive an aggregate of CAR files for inclusion in a Filecoin deal. Capabilities The service exposes the following invokeable capabilities: aggregate/add { "iss": "did:web:web3.storage", "aud": "did:web:spade.storage", "att": [{
     Like  Bookmark
  • πŸ”΄ P0 Unify UCAN API endpoints (@bengo/@gozala) w3protocol#325 Add upload-api integration tests! #9 (@hugomrdias/@vasco) Implement UCAN revocations Implement receipts (@gozala/@bengo)WHY: Accurate accounting e.g. generate a reciept for upload received Align with spec Allow receipt for uploaded CAR #95 Websocket(?) API to subscribe to "status receipts" (tracking an upload through the system) Implement spec for accounts (@hugomrdias/@bengo/@alanshaw)
     Like  Bookmark
  • (Work in Progress) Being able to verify that a UCAN invocation happened within a time window gives us some assurances. We need a way to publically verify that a UCAN was created on or after a specific time. By including a drand randomness round in a signed UCAN, we can prove that it was created on or after that randomness round was generated. There's a number of uses for this e.g. it allows us to transparently account for store/add invocations, publically proving that we were asked to store data within a given time frame. It's also reasonable to assume that the UCAN was probably not generated after the included randomness round. There is no incentive to do so if it is likely to be rejected on reciept. It could happen if a private key is compromised, but then the owner has bigger problems 😱. We want a simple way to prevent replay attacks, within a reasonable time window, but we do not necessarily want the UCAN to expire in the same window.
     Like  Bookmark
  • 🚒 Boaty McBoatface https://en.wikipedia.org/wiki/Boaty_McBoatface πŸ†• Published new w3up modules to npm w3up-client TODO πŸ•Έ did:web shipped like a boss We shipped support for did:web keys like a boss….a forgetful boss who forgot we still needed to be able to sign UCANs with a string that in no way resembles our public key and for which we (currently) have no way to resolve to it’s actual value 🀣. Anyway, long story short, we now have support for embedded key resolution (a way of hard coding the resolution step).
     Like  Bookmark
  • Verifying the CLI is as we want it. Currently: $ w3up --help w3up Commands: w3up id Generate a UCAN Identity w3up register <email> Register your UCAN Identity with w3up w3up whoami Show your current UCAN Identity w3up list List your uploads
     Like  Bookmark
  • Key: πŸ”΄ P0 MVP Launch - Live in production for all users. 🟠 P1 Next - OMG do these ASAP after launch. 🟒 P2 Future - Things that will happen in the future. JS UnixFS [ ] πŸ”΄ Add sharding (@gozala + @alanshaw)
     Like  Bookmark
  • Places we store the DAGs in production, past to present. Note that these are upload targets not places where the complete dataset is stored. For example, we switched at one point from using the S3 bucket dotstorage-prod-0 to dotstorage-prod-1, but we did not copy the data across. dotStorage original April 2021 Uploads: IPFS Cluster
     Like  Bookmark
  • Create a new account and register it w3up id w3up register <email> Create second agent w3up id --profile second create the second account and save the agent did Delegate capabilities to another agent
     Like  Bookmark
  • Header Home └─┬ Components β”‚ β”œβ”€ Wallet [Simple authentication and delegation] β”‚ β”œβ”€ Uploader [Utilities to enable fast uploads] β”‚ └─ Uploads List [Paginated listings of uploaded items] β”œ Examples β”‚ β”œβ”€ [React](https://github.com/web3-storage/w3ui/tree/main/examples/react) β”‚ β”œβ”€ [React Native](https://github.com/web3-storage/w3ui/tree/main/examples/react-native) β”‚ β”œβ”€ Vue
     Like  Bookmark