Preview Feature: UCAN-delegated uploads

[dchoi27]

We have integrated UCAN into our upload authorization flow, and this is now available as a Preview Feature to users. Docs can be found here: https://github.com/nftstorage/ucan.storage#using-ucans-with-nftstorage

From the docs:

For marketplaces and other platforms, adopting UCAN auth can allow you to integrate free, decentralized NFT storage into your own applications without requiring your end users to sign up for an NFT.Storage account. The NFT.Storage API includes endpoints for registering your DID with your NFT.Storage account and obtaining "root tokens" that can be used to delegate storage permissions to other users, whether they have an NFT.Storage account or not.

Please leave any feedback on this Discussion! cc @hugomrdias

[NoelJacob]

Could you add an easy method to this lib to generate and register with this lib.

[dchoi27]

Could you elaborate on what you're looking for?

[NoelJacob]

Like an already initialized NFTStorage class will have a method for generating a UCAN DID. We can pass in the valid from, valid to and permissions as params to it.

It would not require keypair generation, registring public key, getting service DID, etc to be done manually.

[hugomrdias]

Yes we have plans to integrate UCANs in the nft.storage client, for most things, but understand the keypair used to register a DID with the service needs to be saved by the user somewhere like a secret.

[NoelJacob]

How do I get multihash of a car for using with upload/IMPORT attribute?

[hugomrdias]

The mh property is optional and API support is not there yet. We will release more documentation about it when implementation is more stable. For now just ignore it.

If you have a use case for the mh property, meaning restricting one upload to a specific CID or multihash, please get in touch with us we would like to know more about it.

[0x00000010]

This looks like an extremely useful feature. I'm trying to implement it and have run into some problems.

I posted 2 issues, the first is #2154 where I'm getting a TypeError 500 when uploading with a UCAN token to POST /upload, and the other is #2155 when interacting with the documentation for the POST/ucan-upload endpoint.

I'm also having trouble refreshing tokens, which I've detailed at #2156

[dchoi27]

Thanks! We actually wrote a whole new upload service and client that is natively UCAN based. Its alpha will be ~next week if you want to be added to that! It's going to be much better in a lot of ways, and UCANs will just be baked in. Let me know - feel free to reach out to me on Discord (dchoi27 #7898)

[0x00000010]

thanks! am going through your replies now and will reach out directly if i have any more questions

[0x00000010]

@dchoi27 I've sent a friend request on discord

[Zir0h]

Hello! Is this still a thing for nftstorage? Because the https://github.com/nftstorage/ucan.storage/ repo has a big deprecation notice on there and no more activity. Thanks!