Issue reported in AionR aion_pool2 connection issue
is caused by RPC output format inconsistance between Aion(Java) and AionR for eth_getBlockByNumber/eth_getBlockByHash. When the block contains transactions, result.transactions[0].blockNumber is a number in Aion and a Hex string in AionR. Changing AionR code will cause more inconsistance. AionR cannot make a fix until the AION RPC standard has been made. I wonder if aion_pool2 can be updated to accept both data types.
Issue reported in AionR aion_pool2 connection issue is caused by RPC output format inconsistance between Aion(Java) and AionR for eth_getBlockByNumber/eth_getBlockByHash. When the block contains transactions, result.transactions[0].blockNumber is a number in Aion and a Hex string in AionR. Changing AionR code will cause more inconsistance. AionR cannot make a fix until the AION RPC standard has been made. I wonder if aion_pool2 can be updated to accept both data types.