web3.personal.unlockAccount doesn't accept integer as unlock period parameter
See original GitHub issue- Version: 3.9.0
- Python: 2.7
- OS: not platform specific
What was wrong?
Method web3.personal.unlockAccount doesn’t accept integer as unlock period parameter.
Example:
web3.personal.unlockAccount(eth_address, 'strongPassword', 10000)
returns ValueError
:
ValueError: {u'message': u'invalid type: integer
10000, expected a 0x-prefixed, hex-encoded number of type U128', u'code': -32602, u'data': None}
when using value in HEX :
web3.personal.unlockAccount(eth_address, 'strongPassword', 10000)
it works fine (returns True
)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:9 (2 by maintainers)
Top Results From Across the Web
parity: web3.eth.personal.unlockAccount: integer to hex ...
I am having problems to unlock my account with a parity node. It seems like that the integer I am passing in web3.eth.personal....
Read more >Unlocking accounts and making transactions in web3.js
The unlock period parameter is optional. How is it possible to check if accounts are locked (prior to making transactions)?. Are there any...
Read more >Nethereum/Nethereum - Gitter
var unlockAccountResult = await web3.Personal.UnlockAccount.SendRequestAsync(senderAddress, password, 120); Full code as maybe you all read ...
Read more >web3.js Documentation - Read the Docs
9.11 unlockAccount . ... Most web3.js objects allow a callback as the last parameter, ... Note: An uncle doesn't contain individual transactions.
Read more >Calling web3.eth.personal.unlockAccount throws error
The rpc* configuration parameters are for JSON-RPC (over HTTP), not IPC/WS. Share.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Apologies, was OoO. @djrtwo I’m connected to the parity node. I was testing in v3.9.0. It’s not a issue for me to provide the number in hex, but it variable type wasn’t consistent with web3js, that’s why Piper recommended to file a bug.
Oh, so it’s node specific. Looks like a false alarm, feel free to close the bug.
Yes! Apologies, copy paste fail.