This repository is no longer under active development.
Support for AlgoSigner by the Algorand Foundation has ended as of March 31st, 2023 and the extension will be unpublished from the Chrome Store. This should not delete the extension if it is installed through the store but neither the extension or code base will be updated or supported.
Refer to the Algorand website for a list of alternative providers. The Algorand Foundation also providers a list of wallet security best practices.
Existing users should migrate to a different wallet immediately. There is no way to export a mnemonic from AlgoSigner. If you did not write it down when creating an account you should migrate to another account before March 31st or rekey your account to an account you do have the secret for.
A: No, this is a planned phasing out of AlgoSigner. There is no known security issue with the wallet.
A: Yes, you can, several guides are available recently depending on your new wallet.
A: The Chrome Store listing is unpublished. There is a final code only release (1.11.0) in the Github repository with the last developed features.
A: No. There will be a branch containing all the changes towards supporting v3, but it should not be considered tested or production ready.
enable()
calls.enable()
call while logged out no longer closes the connection window after inputting your password.keyreg
transactions regarding nonParticipation.acfg
transactions regarding the distinctions between 'Create', 'Config' and 'Destroy'.enable()
calls.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.
window.algorand
is made available and can be accessed by the dapp to make calls to AlgoSigner. The existing window.AlgoSigner
object remains but will be deprecated over the next year. algorand.enable()
. The existing connection flow persists but will be deprecated over the next 3-6 months.authAddr
for signing transactions with rekeyed accounts.An interactive transition guide is available here to aid in the migration of existing functionalities.
boxes
field on application transactions and the stateProofKey
& nonParticipation
fields for key registration transactions.algorand.enable()
calls.authAddr
provided.This project is under the MIT License