w3up-client and the available hosted APIs are currently beta preview features. JavaScript library that provides a convenient interface to the w3up platform, a simple "on-ramp" to the content-addressed decentralized IPFS network. w3up services use ucanto, a Remote Procedure Call (RPC) framework built around UCAN, or User Controlled Authorization Networks. UCANs are a powerful capability-based authorization system that allows fine-grained sharing of permissions through a process called delegation. See our intro to UCAN blog post for an overview of UCAN. w3up-client and ucanto take care of the details of UCANs for you, but a few of the underlying terms and concepts may "bubble up" to the surface of the API, so we'll cover the basics here. We'll also go over some terms that are specific to w3up that you might not have encountered elsewhere.
Features
- w3up services use UCAN (User Controlled Authorization Networks), which is a powerful capability-based authorization system
- UCAN-based APIs center around capabilities, which consist of an ability and a resource
- To invoke capabilities, a client must have a private signing key managed by an Agent
- Spaces help keep track of which uploads belong to which users
- Both Agents and Spaces are identified using DIDs, which are a W3C specification for verifiable identities in decentralized systems.
- Before data can be uploaded via w3up-client, the client needs permissions to upload to the target service by having permissions to a registered Space