question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
userpastacommented, Aug 31, 2017

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.

1reaction
userpastacommented, Aug 1, 2017

Yes! Apologies, copy paste fail.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found