When Rocca showed up on our roadmap last year, we introduced it as a key piece of our long-term wallet strategy. Since then, development has been underway behind the scenes. Today, we're sharing an update on that progress, and we are excited to show you how Rocca is now being used within two real products, ready for you to use today.
A quick primer
Rocca is a white-label wallet framework, meaning it's not an app you'll ever download directly, but infrastructure other teams build their own branded wallet products on top of. It handles the hard, foundational problems every wallet needs solved like secure key storage, decentralized identity, and passkey support.
Rocca in the wild: Pera Wallet and AC2 Wallet
Pera Wallet and AC2 Wallet are the first two products built on Rocca.
Pera Wallet 7.0 is a full rebuild of Pera on the Rocca infrastructure, including its key storage and identity stack. It's the clearest example of what Rocca was built for: a polished, consumer-facing wallet built directly on its foundation.
AC2 Wallet is the reference app for the AC2 Protocol (Agentic Communication & Control Protocol) and uses LiquidAuth together with Rocca’s FIDO2 and WebRTC layer. AC2 applies Rocca to a new problem by giving AI agents a way to request approval from a human that's cryptographically provable, not just a chat message someone could spoof. At its core, AC2 is an open protocol that any agent framework or wallet can adopt directly.
Pera Wallet 7.0 and AC2 Wallet demonstrate how the same underlying infrastructure – Rocca – can be utilized to build two very different products for two very different needs.
More is coming
Pera Wallet and AC2 Wallet are the first two releases built on Rocca, not the last. The Digital Chess ID is set to launch later this year on the same foundation, and a new product coming soon by GoPlausible will also be built on Rocca wallet.
Rocca is ready for you to build on. Access the docs and repo here, and reach out in Discord if you have questions.
Disclaimer: The content provided in this blog is for informational purposes only. The information is provided by the Algorand Foundation and while we strive to keep the information up-to-date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability with respect to the blog or the information, products, services, or related graphics contained in the blog for any purpose. The content of this blog is not intended to be legal, financial, or investment advice nor is it an endorsement, guarantee, or investment recommendation. You should not take any action before conducting your own research or consulting with a qualified professional. Any reliance you place on such information is therefore strictly at your own risk. All companies are independent entities solely responsible for their operations, marketing, and compliance with applicable laws and regulations. In no event will Algorand Foundation nor any affiliates be liable for any loss or damage including without limitation, indirect, or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this blog. Through this blog, you may be able to link to other websites which are not under the control of the Algorand Foundation. We have no control over the nature, content, and availability of those sites. The inclusion of any links does not imply a recommendation nor endorse the views expressed therein. Any statements about future plans, integrations, or protocol upgrades are forward-looking and subject to change. The use of agentic commerce involves risks, including potential fraud and identity verification issues. Users and merchants should ensure they are using verified agents and follow best practices for security and compliance.