
Samuel Teboul
865 posts















🚀 I’ll be in Singapore from September 16th to 20th for TOKEN2049. Looking forward to meeting market makers, asset managers, banks, and institutions to discuss wallet security, open-source systems, and access controls. I’ll also share case studies on: 🛠️ Building a wallet stack from modular components 🔒 Unifying access controls across multiple custody systems 💡 Reducing dependency and increasing leverage on single wallet vendors See you there!

📖 One of the best parts of our open-source access management system for web3? It’s easy to integrate with other best-of-breed parts and build your ideal wallet stack. Open and modular by design. ⚔ An example? You can now manage your Narval Armory stack through the Rabby interface you already know and love. Best-in-class dApp interaction meets best-in-class key access management. And yes, you can still operate your wallets programmatically. Use Armory for any backend wallet needs in your systems or for any team and dev keys. 🎬 Check out the short video to see it in action. It only took us a few days to complete. What other integrations would you like to see or build? We’ve got more on the way! 🔗 youtube.com/watch?v=sRGSIK…

📢 Breaking news. ⌛ In the last couple of months, we've been heads down building. And we got tired of waiting. During our closed beta, we’ve authorized hundreds of thousands of transactions to understand the needs of a web3 access management system. 📖 Today, we’ve released it fully open-source. Including a key vault for signing EVM transactions. We believe you should be able to build an institutional wallet stack from entirely open-source components. 🎛 The Armory Stack is an access management system tailored for use cases that need strong authentication and fine-grained authorization. It is designed to secure the usage of private keys, wallets, and web3 applications. 👉 Learn more in our blog post: mirror.xyz/0xaee67BE46Ff5…

Most wallet needs are actually access management needs. So we built the most secure, advanced, and flexible web3 access management layer, interoperable with any key management system. Very simple. Don't put keys in code. Stop not knowing who has seen a plaintext key or when. Focus on your product. Simplify your operations and polish your security story. Secure the usage of any private key, or local, staging, and production wallets, with the same interface. Easily onboard and off-board people. Rotate credentials and audit logs. Simple SDKs. Contact me today to get access.

While OAuth, the open authorization standard in web2, offers a framework for access delegation (ie letting a system access and use a protected resource/data), it's not fit for web3. Web3 has specific Auth needs: ✴ Wallets require trust models & signing schemes removing trust from even trusted operators ✴ Transactions need web3-aware policy rules around transfer details & contract calls ✴ Integrations with the blockchain ecosystem requires interfacing with decentralized systems and less-traditional signing curves To tackle these challenges, most wallet technologies have bundled their own auth solutions with the rest of their stack - but many problems and use-cases remain unresolved. 👀 Time for OAuth 3.0, tailored for web3? 👀





