An open-source, security audited, Algorand wallet browser extension that lets users approve and sign transactions that are generated by Algorand dApp applications — available for Chrome.
The extension is available on the Chrome Extension Store
This is the preferred solution for end-users, updates will be automatically installed after review by the extension store
Developers working with dApps may also install directly from the release package, or by downloading the project and building it.
As part of the process of supporting the Algorand Foundations ARCs, in 1.10.0 a number of non-breaking additions have been made to support how dApps will work with AlgoSigner. In time, the existing legacy features will be deprecated.
- A new top level object,
window.algorandis made available and can be accessed by the dapp to make calls to AlgoSigner. The existingwindow.AlgoSignerobject remains but will be deprecated over the next year. - An updated connection flow and address discovery process for dApps is in place, using
algorand.enable(). The existing connection flow persists but will be deprecated over the next 3-6 months. - Dapps may also now request for AlgoSigner to directly post signed transactions to the network and not return the signed blob to the dApp for handling.
- Additional documentation regarding the use of
authAddrfor signing transactions with rekeyed accounts.
An interactive transition guide is available here to aid in the migration of existing functionalities.
- Watch Getting Started with AlgoSigner
- Using a Ledger device
- Adding Custom Networks (such as BetaNet or a private network)
- Troubleshooting Connection issues
For teams looking to integrate AlgoSigner into a project:
NOTE: AlgoSigner.sign() and AlgoSigner.signMultisig() have been officially deprecated. An interactive transition guide is available here if you still need to migrate existing functionalities.
For developers interested in working with AlgoSigner, an Extension Development Guide is available. Pull requests we accept need to be narrow in scope and all contributors need to sign (once) our CLA after submitting one in order for it to be considered.
This project is under the MIT License
