Contract state change not visible if request is done over official JSON-RPC node

[mradmilovic]

Hey, devs. Please help. The problem happens when I try to call the contract view method over the official JSON-RPC node (https://mainnet.aurora.dev) but with a certain block number defined. So, if I send the transaction that changes the contract state, for some reason, that change is visible 2 blocks after the block in which the transaction is mined. When we did the same method call, but over a different RPC (Chainstack) everything works fine.

You can see transaction details here ( https://aurorascan.dev/tx/0x5b7ed5cb15d5ae2418224dd7d099fce2d80e6b584084fde6b8fcdaa558130f0b )

If you create a request to RPC with this JSON object you will see that the token id created in the given transaction does not exist in the 69391529 block. It also does not exist in 69391530 but is visible in 69391531.

{
    "jsonrpc":"2.0",
    "id":5,
    "method":"eth_call",
    "params":[
        {
            "from":"0x0000000000000000000000000000000000000000",
            "data":"0xc87b56dd000000000000000000000000000000000000000000000000000000000000185f",
            "to":"0x8b8af1072e8cf40cf75ad6efdf9fe999a47e285c"
        }, 
        69391529
    ]
}

[joshuajbouw]

This sounds like an issue with our RPC as opposed to the Engine. Possible explanation has to be that sometimes NEAR has "skip" blocks.

Also I apologise for the delay, somehow this question slipped through the cracks but we will be ensuring that we will improve this.