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.

An interactive transition guide is available here to aid in the migration of existing functionalities.

• Multiple improvements to Custom Networks including:
  • Automatic fetching of genesis ID and hashes for the user.
  • Achieved full compatibility with enable() calls.
  • Other UI/UX changes.
• Updated a lot of error messages and data structures to better communicate the causes of errors.

• Connecting to a dApp using an enable() call while logged out no longer closes the connection window after inputting your password.
• Improved validations for keyreg transactions regarding nonParticipation.
• Improved validations for acfg transactions regarding the distinctions between 'Create', 'Config' and 'Destroy'.
• Fixed account permission bug on enable() calls.
• SDK support updated to v2.0.0.

• 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:

• dApp Development guide
• AlgoSigner dApp Integration Guide

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