The next big thing from the team at Rivet
It’s called Cardinal — and “upgrade” is an understatement. Learn what it is and how we’re rolling it out below.
At Rivet, we envision a future where anyone can effortlessly bring their ideas to life without limits — whether imposed by technical know-how, or gatekeepers of the status quo.
That’s why we’ve made it our mission to build the best possible node infrastructure APIs for the developers and teams who are building that future.
Our team has not only spared no effort to make Rivet a scale-on-demand, high-availability (99.95% uptime SLA) service — we’ve done it without compromising the values that inspire and animate the web3 movement.
Since we launched Rivet, we’ve continually added unique capabilities and features to empower developers even further — such as the ability to signup/login with web3, pay with DAI or ETH, and access indexed transaction/log data.
Today, we’re beyond excited to announce our next big thing — Cardinal. So what is it?
Without getting into too much detail (if you’re curious about digging deeper, you can read about it in-depth here) — Cardinal is the open source technology we created to take Rivet to the next level.
With Cardinal, we will be able to provide availability, performance, and quality beyond even what you’ve already come to expect from Rivet — with no increase in cost — on an essentially unlimited number of blockchains. While we will soon be adding support for the most popular protocols, the first step is rolling out Cardinal for the networks we currently support.
We’ve been working on perfecting Cardinal for more than a year, so we expect the transition to be seamless. So to ensure we give you plenty of time to get comfortable with the Cardinal upgrade before we cut over, we’re rolling it out in 5 phases over the course of 8 weeks.
TLDR: Phase Overview Timeline
Phase 1: Universal Opt-in (~14 days) ——— You are Here!
Phase 2: Testnet Cutover w/ Opt-out (~14 days)
Phase 3: Mainnet Cutover w/ Opt-out (~7 days)
Phase 4: Testnet Opt-out Disabled (~21 days)
Phase 5: Mainnet Opt-out Disabled
Phase 1: Cardinal Opt-in Opens • ~14 Days
Starting on February 14 (today!), you may opt in to Cardinal to begin testing. To opt in, you don’t need to make any changes in your codebase — all you have to do is toggle it on in the Update Plan view of the Rivet dashboard.
Testnets, ETH Mainnet, and ETC Mainnet will all have separate toggles, so you can conduct tests on your testnet of choice before you decide to opt in on Mainnet.
During this phase, you can opt out in the Update Plan view at any time. If you do encounter issues that necessitate opting out, please contact us via email at support@rivet.cloud or hit us up on Discord and we’ll work with you to get it sorted out.
Phase 2: Testnets to Cardinal with Opt-out • ~14 Days
At the outset of this phase, all testnets will be cut over to Cardinal by default. As in Phase 1, if you need to opt out for any reason, you can do so from the Update Plan view of the Rivet dashboard. If you need to opt out of Cardinal due to any issues with your testnet-deployed applications, you will have to do so manually!
Again, if you encounter issues, please contact us via our support email address so we can help get it resolved.
Phase 3: Mainnets to Cardinal with Opt-out • ~7 Days
In this phase, we’ll do the same thing we did in Phase 2 — this time for the ETH and ETC mainnets. If you need to opt out of Cardinal due to any issues with your mainnet-deployed applications, you will have to do so manually!
Phase 4: Testnets Cutover to Cardinal • ~21 Days
At the outset of Phase 4, we will permanently cut over all testnets to Cardinal and disable the corresponding opt-out.
Note: we will not begin this phase if there are any outstanding issues identified by your reports to us or by our ongoing testing throughout the preceding phases.
Phase 5: Mainnets Cutover to Cardinal
At the outset of Phase 5, we will permanently cut over all mainnets to Cardinal and disable the corresponding opt-outs. As with Phase 4, if there are any outstanding issues, we will resolve them before beginning this phase.
Epilogue: What’s Next for Rivet 2.x
We’ve got big plans for 2022, and the Cardinal rollout is just the beginning. So what’s next on the roadmap?
• Support for EVM-based chains like Polygon, Arbitrum, BSC, and more. (Any special requests? Email support@rivet.cloud or hit us up on Discord to start a conversation!)
• A brand new Rivet Dashboard experience, optimized to make working with multiple keys across multiple chains, managing your account/plan preferences, and visualizing your usage data a breeze.
• Tokenized request capacity. A pure utility token that will enable you to mint tokens with your unused request capacity, burn them to add that capacity to a new or exiting Rivet account. Send them to a friend/hackathon winner/bug bounty/Gitcoin grant/portfolio company/MOOC student/DAO treasury/smart contract/etc. (Cool, right?!)
• And more!
This is just a high-level snapshot of where we’re headed — stay tuned for more details as 2022 progresses. And as always, we can’t wait to see what you’ll BUIDL. Cheers!!!
— ❤️ The Rivet Team
