You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: