'Why does deploying my smart contract fail with : Failure: Tx Failed: Keyset failure (keys-any):
Despite using a unique module name (e.g. THIS was not the issue at hand), deploying my smart contract on kadena's testnet failed with the following error message:
: Failure: Tx Failed: Keyset failure (keys-any): '[my keyset name]
The only way to achieve a success was to assign a separate account that I control as the gas payer. To elaborate for new developers:
When you hit "Deploy" in Chainweaver and fill out the form on the first page of the pop-up, you move to the SIGN tab and choose an account separate from the SENDER to pay for the gas fee.
In the following image we have two keys, red and green. Green is the sender, red is the gas payer. This is a configuration that has worked for me.
It is not clear to me, however, why this is the case or if there is a better solution.
Thank you in advance.
Solution 1:[1]
I don't think the answer above is correct. The desktop edition does indeed disable the use of unrestricted signing for a key as soon as you select it for a managed capability.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | georgep |