Developed by PureStake, AlgoSigner is an open-source browser extension that provides a secure way for holders of the Algo token to interact with dApps without granting them control of their keys.
This is a leap forward for developers who want to build DeFi applications on Algorand. This enables devs to initiate transactions and accept Algos seamlessly, without jeopardizing the security of their usersâ secrets.
Hey, I want to ask something. I want to use AlgoSigner to sign a transaction that will modify accounts of an already created asset, but I donât know what type should I chose and what params are mandatory.
I try with this params:
AlgoSigner.sign({
âassetIndexâ: values.assetId,
âfromâ: values.reserveAccount,
âassetManagerâ: values.managerAccount,
âassetReserveâ: values.reserveAccount,
âassetFreezeâ: values.freezeAccount,
âassetClawbackâ: values.clawbackAccount,
ânoteâ: ââ,
âtypeâ: âacfgâ,
âfeeâ: txParams[âmin-feeâ],
âfirstRoundâ: txParams[âlast-roundâ],
âlastRoundâ: txParams[âlast-roundâ] + 1000,
âgenesisIDâ: txParams[âgenesis-idâ],
âgenesisHashâ: txParams[âgenesis-hashâ]
})
And it fails with this message: Validation failed for transaction because of invalid properties.
I double checked and AlgoSigner does support the config in general, it does not support the destroy (which is incredibly easy to do). There may be a subtle issue with one of the fields above causing a problem.
The clawback is for sure not supported yet in AlgoSigner, the good news is a release is coming soon that adds that in. The destroy will also have new warnings on the extension side, as it is all too easy.
Full dApp asset support is included in AlgoSigner as of 1.1.0. We just released 1.2.0 which provides additional support for atomic transactions and more application transaction support.