Big Integers are not supported by elasticsearch about e2ebridge HOT 4 CLOSED

You are probably right. I have checked that JavaScript can handle those integers (which it can) and I thought I had tested with Elastic. (Older versions of the tool simply divided by 10^6 to avoid this issue which was not nice either.
I will go and investigate.

from e2ebridge.

I have committed 628b98d7305d8d11aecd6075fbb58f8680bf58fb to circumvent this issue. This is not beautiful but as long as Elasticsearch does not support any larger integer formats...

from e2ebridge.

Hi,

I think that block.difficulty and transaction.gasPrice also need to be transformed.

from e2ebridge.

Hi,

I totally agree when it comes to block.difficulty. Commit e39b176e29c72beabc32291c17600faf7b16c7c7 already reflects that: We now divide both block.difficulty and block.totalDifficulty by 10^6.

We could also divide transaction.gasPrice by some factor. But given the fact that a naked value transaction costs 21'000 gas I do not expect anyone to issue an transaction with a gas price beyond 2^63 Wei: This would put the price of a value transaction north of 180'000 ETH... Or did I miss something here?

from e2ebridge.