Christopher Joel

Determine the use-case for a JS-packaged rs-ucan

4

We need to determine the scope and use-case for wielding WASM-targeted rs-ucan from JavaScript. **Please share your use-case for a JS-packaged rs-ucan in this issue.** In #17 , we have...

Add `witnessed_by_cid`-equivalent helper to `UcanBuilder` API

1

As of #28 , we only recognize CIDs in the `prf` field of UCANs. However, the `UcanBuilder` API only accepts a `Ucan` as the value for the `witnessed_by` method that...

Now that all proofs are referenced by their CID, and with consideration of the [UCAN as Bearer Token](https://github.com/ucan-wg/ucan-as-bearer-token#2-request-headers) spec's affordance for transmitting UCANs wholesale via the `ucan` header, it would...

As of #28 , we will have introduced support for UCAN-IPLD. However, notably absent is support for non-standard signature schemes in the `UcanIpld` representation. Even though `ucan-key-support` only currently includes...

Part of #11 https://github.com/ucan-wg/spec#94-session-content-id

Part of #11 https://github.com/ucan-wg/spec#41-ucan

Abstract over DIDs with an async verify interface

1

DIDs may not always resolve directly to public key bytes. This being the case, the current strategy to resolve DIDs to key material via `DidParser` is probably not adaptable enough...

Referencing discussion in https://github.com/ucan-wg/spec/discussions/81#discussioncomment-3033382 This library should offer an out-of-the-box facility for checking if the token being presented at the point of invocation has been seen already or not.