[SDK] Use w3up in SDK

[ryscheng]

Describe the feature you'd like to request

web3.storage is moving towards w3up, instead of their existing clients
https://github.com/web3-storage/w3up/tree/main/packages/w3up-client

From what Travis told me today, this isn't quite ready yet for production use, but wanted to file an issue for it to track it and start testing it

Describe the solution you'd like

Replace the nft.storage and web3.storage clients in the SDK and replace with w3up

Describe alternatives you've considered

N/A

[ryscheng]

CC @bitbeckers @Jipperism

I just got this email. Looks like they're deprecating the older client by end of year!
I think we might need to move on this sooner than expected:

Dear user,

Hello from web3.storage! We have some exciting news that affects you as a current web3.storage user.

We are launching our new upload API and client, which is replacing our existing upload API. We accomplished a ton with our old API from initially launching as a free Filecoin data onboarding platform for developers. As we evolve into a standalone business, that means pivoting to a product that takes what is so great about the old web3.storage (easy-to-use, reliable and fast IPFS hosting, with data stored on the decentralized Filecoin network) and combines it with key features and a differentiated developer experience. This includes, among other things:
Seamless uploads of any size
Lower prices competitive with traditional cloud storage providers
The ability to give other users the ability to upload directly to web3.storage on your behalf
web3-native application models using cryptographic, UCAN-based authorization
You’re probably wondering what this means for you, a current web3.storage user. Here’s the tl;dr:
The new upload API and client is live. Its account system is completely separate from that of the legacy web3.storage.
The legacy web3.storage upload API, pinning service API, and w3name will sunset on January 9, 2024. Until then, you will still be able to upload to your legacy account up to your free account limit. The old dashboard can be found here.
All uploads to the legacy web3.storage prior to January 9, 2024 will continue to be stored until further notice, though over time latency and availability may degrade.
To continue maintaining the current level of availability of your stored data, you will be able to migrate your uploads to a new web3.storage account. Reply to this email if you are interested!
Effective immediately, no new accounts can be created for the old web3.storage API.
We will continue to enforce the legacy web3.storage Terms of Service for legacy web3.storage accounts. Those who violate the Terms of Service risk an account ban and removal of uploads.
As you look to potentially migrate over to our new upload API, we wanted to share some more details about the product and pricing.
Users can sign up for one of three plans. You can do so by following the Quickstart instructions in our docs.
Starter: Free to use for the first 5GB of storage
Lite: $10/mo for 100GB storage ($0.05/GB-mo for extra storage), 100GB egress/mo. (extra egress for $0.05/GB)
Business: $100/mo for 2TB storage (extra storage for $0.03/GB-mo), 2TB egress/mo. (extra egress for $0.03/GB)
All users must enter payment information, even when signing up for the Starter tier. We recognize that this might add inconvenience for you, but this is a necessary measure to prevent users from uploading malicious content.
The new product opens a ton of doors for developers to explore using decentralized protocols like IPFS and UCAN to create interesting and improved experiences for their end users. To learn more about this, check out this blog post, our docs, and our CLI.
Even if you’re not a developer, our web console makes it easy to host even large files and directories over IPFS.
Please join us in celebrating this exciting news by building something awesome! You can find us in our Discord channel (#web3-storage in IPFS Discord) or by reaching out to [email protected] if you have any questions.

Best,
web3.storage team

[ryscheng]

Looks like they're building a yet to be released migration tool, need to contact support to get early access?

[bitbeckers]

@ryscheng thanks for keeping us up to date here! While I'd appreciate early access, if it's flaky I don't think we currently have the bandwidth for 'getting things running'. So would be nice, not a must have imho.

Since they'll be sunsetting soon, and like you suggested, we better migrate to the new upload flow soon. I'm looping in @Jipperism here because looking at the docs they suggest setting up a BE service with a worker cue or at a minimum a backend that provides authentication to our users to upload client side.

We should assess what's applicable for our usecase (one-shot-uploads).

Docs on uploading: https://web3.storage/docs/how-to/upload/
Docs on architecture: https://web3.storage/docs/concepts/architecture-options/

[bitbeckers]

API is live with metadata and allowlist upload endpoint: hypercerts-api.vercel.app

Metadata: /api/v1/metadata
AllowList: api/v1/allowlist

Repo: https://github.com/hypercerts-org/hypercerts-api

[bitbeckers]

hypercerts-api-production.up.railway.app