Web3.js: parity: web3.eth.personal.unlockAccount: integer to hex conversion not working?

Created on 14 Jan 2019 · 5Comments · Source: ChainSafe/web3.js

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.unlockAccount('...', '...', 10000) is not converted to a hex and send to the parity endpoint. I am having no problems with geth but thisParity issue send me over here.

Could somebody confirm that this is not a problem with web3?

The error message I received is:

UnhandledPromiseRejectionWarning: Error: Returned error: Invalid params: invalid type: integer 10000, expected a 0x-prefixed, hex-encoded number of length 32.

2.x Stale bug on hold

Source

Knowledge91

Most helpful comment

That's true there is a missing mapping for the duration property of the unlockAccount method. Thanks for submitting this issue. I will add this fix as soon as possible.

nivida on 18 Jan 2019

👍2

All 5 comments

That's true there is a missing mapping for the duration property of the unlockAccount method. Thanks for submitting this issue. I will add this fix as soon as possible.

nivida on 18 Jan 2019

👍2

I have the same problem

indigoram89 on 30 Jan 2019

I've checked it and web3.js can't handle this in a clean way because parity will have the number as hex string and geth as number.
The only solution would be to create a web3.eth.personal.parityUnlockAccount() method until parity or geth has changed it. I will open an issue in the geth and parity repository for syncing this.

nivida on 27 Feb 2019

👍1

So how do we unlock accounts now with parity?

EDIT: If anyone stumbles over the same problem, just use null as the duration parameter.

gnorbsl on 12 Jun 2019

❤1

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions