In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/01 Report--
It is believed that many inexperienced people are at a loss about how to solve the problem that the keys, permissions and delays provided in Error 309003 do not meet the declared authorization. Therefore, this article summarizes the causes and solutions of the problem. I hope you can solve this problem through this article.
When EOS application developers try to submit the first transaction in their newly built development environment, they often encounter a 3090003 error, indicating that the key, permission or delay required for transaction authorization does not meet the requirements:
Error 3090003: provided keys, permissions, and delays do not satisfy declared authorizations Ensure that you have the related private keys inside your wallet and your wallet is unlocked.
This is because each new EOSIO blockchain has a default system account, eosio, which will be used to initialize the settings of the blockchain, such as loading system contracts that manage EOSIO blockchains and consensus computing. Each new EOSIO chain has the same development key that needs to be loaded to sign the transaction in the name of the system account eosio.
If you want to learn EOS application development quickly and efficiently, we recommend Huizhi.com 's EOS intelligent contract and introduction to DApp development.
Execute the following command to load the key corresponding to the account eosio:
~ $cleos wallet import 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Note: do not use the development key in a production environment because the private key is public!
So, how should I modify the default private key of eosio?
In the nodeos configuration file (ubuntu default path: ~ / .local / share/eosio/nodeos/config/config.ini), there is a parameter signature-provider that defines the key pair corresponding to the eosio account. If you haven't modified it, this is what it looks like:
Signature-provider = EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV=KEY:5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
The value of the signature-provider parameter is a key pair in the form:
=
Is a valid EOSIO public key string, for example:
OS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
It consists of two parts: The value can be KEY or KEOSD, which varies depending on this part.
When the value is set to KEY, the content should be the private key string corresponding to the public key; when the value is set to KEOSD, the content should be the URL of the keosd wallet. Note that the corresponding wallet still needs to be unlocked.
Therefore, you can use cleos to generate a pair of keys, and then modify signature-provider to change the default private key of eosio.
After reading the above, do you know how to solve the authorization that the keys, permissions and delays provided in Error 309003 do not meet the declaration? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.