web3.storage legacy API version retirement
Stopped workingSubscribe to Web3Share
Calls to web3.storage legacy API stopped working on January 9, 2024.
What to use instead of these calls
Move uploads to another storage service: the w3up client is deprecated, the upload host of its successor (Storacha, up.storacha.network) no longer resolves, and web3.storage now redirects to fil.one.
No successor stands: web3.storage became Storacha, which now redirects to fil.one, another product; choosing a storage service is the team’s call.
In Web3's words
The legacy web3.storage upload API and pinning service API will sunset on January 9, 2024.
Facts
- API
- Web3
api.web3.storage - Kind
- Version retirement
- Announced
- November 14, 2023
- Takes effect
- January 9, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Web3's own pages
Questions
When does this change take effect?
Calls to web3.storage legacy API stopped working on January 9, 2024.
What happens to calls after January 9, 2024?
They have failed since January 9, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.