gasPrice RPC gives back number instead of HEX

[frozeman]

The docs state it should return a HEX, though it returns a number as string:
https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_gasprice

[tgerring]

Currently is reporting the value from string const at

go-ethereum/rpc/packages.go

Line 29 in 483d96a

defaultGasPrice = "10000000000000"

[frozeman]

Currently:

{
"id":73,
"jsonrpc":"2.0",
"result":"1000000000"
}

expect:

{
"id":73,
"jsonrpc":"2.0",
"result":"0x09184e72a000"
}

[maran]

What's the benefit of giving the result in hex? Wouldn't it make more sense to change the specification to show it in base 10?

[tgerring]

I think some of the "hex result" might have to do with lack of large number support in JavaScript. Maybe @debris could provide some insight?

[maran]

I thought we were using bignumber.js to work around that.

[frozeman]

its the big number i guess. in ethereum js the hex is change into a big number.

[debris]

bignumber.js can handle decimal numbers in strings as well. The real issue is that we have differences in cpp && go ethereum json-rpc api. Go is already returning hex for balance rpc method. Let's unify this && return hex for all value related properties.