7/1 UPDATE: Important Notice Regarding Etherscan-Compatible API Deprecation
And announcing a partnership to replace it
7/1/2024 • Update
Beginning today, you will no longer be able to make calls to our deprecated Etherscan-compatible APIs.
If you’re in need of an alternative to it, please check out MyEtherWallet’s ETHVM APIs, which offer an alternative to Etherscan.
MEW’s API documentation can be found here: https://docs-api.ethvm.com/As we’ve partnered with the team at MEW, please let us know if there is anything it doesn’t do that you wish it could do, or anything you wish it would do differently, and we will gladly reach out to them with your feedback.
Send feedback here: support@rivet.cloudAnd as always, watch this space. We’re not done releasing magic with our awesome partners for you all—our community of BUIDLers, dreamers and inventors of the future. Cheers!!!
Haven’t signed up for this newsletter? please subscribe so subsequent updates can be delivered conveniently to your inbox the moment I tap the publish button. 👉👉👉👇
6/17/2024 • Update
Starting today, 10% of calls to our deprecated Etherscan-compatible APIs will fail and return the following text in the body of the error message:
{"status":"0","message":"NOTOK-deprecation warning","result":"Error! This API is deprecated. See https://rivetcloud.substack.com/p/important-notice-regarding-etherscan"}As we get closer to July 1 and the end of support, we will continue making relevant updates to this post—so watch this space.
Greetings Riveteers—
The purpose of this post is to inform you about an important upcoming change to our API services. As part of our continuous efforts to provide the best possible service, we have decided to deprecate our Etherscan-compatible API. This decision was made after careful consideration and in alignment with our long-term strategy to improve and maintain the stability of our open source stack in light of changes introduced in the most recent hard fork alongside those forthcoming in the future.
While this change should effect a very small number of customers based on our observations regarding how frequently it is called, for those of you that do call it, the following is our path forward. (And fear not, we won’t be leaving you hanging with no alternatives.)
Key Dates and Changes
June 17, 2024:
Starting from this date, any customers making calls to our Etherscan-compatible API will begin to see error messages at a rate of about 10%. These errors are designed to remind you that we will soon stop supporting this method, and will encourage you to transition to our alternative solution based on documentation we will be releasing well in advance of the date we deprecate the endpoint entirely.
July 1, 2024:
On this date, we will completely stop supporting the Etherscan-compatible API. Any calls made to this API method starting on and proceeding after this date will return an error.
Partnering with MEW for an Alternative Solution
While this change is necessary to ensure the ongoing stability and hygiene of our open source stack, we are pleased to announce that we have been working on an alternative in collaboration with our good friends at MEW.
We will be sharing more details about this solution over the coming weeks, so rest assured you will continue to have access to robust and reliable block explorer APIs that don’t rely on Etherscan as a single point of failure.
MEW’s API documentation can be found here:
Support and Assistance
We understand that changes to our API services can be disruptive, and we are here to help make this transition as smooth as possible. If you have any questions or need assistance, please do not hesitate to contact our support team at support@rivet.cloud. Our team is ready to provide you with the support you need during this transition period.
Thank you for your understanding and continued loyalty. We are committed to bringing you the best service and look forward to answering any questions you may have about this change. Cheers!
Greg @ Rivet