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
Describe the bug
Due to the block mining time in Skaled and for optimizing performance costs, Skaled has reduced the usage of the 'pending' tag in the 'eth_getBlockByNumber' JSON-RPC call, resulting in some behavior differences from Ethereum.
This issue is also relevant for other JSON-RPC calls, such as eth_getBlockByNumber, eth_getBlockTransactionCountByNumber, eth_getTransactionByBlockNumberAndIndex, etc where the "pending" tag used.
Versions
Skaled: 3.18.0
Environment:
Active Schain medium type 16 nodes
Endpoint to Schain
Adress with Sfuel on balance
To Reproduce
Send transaction sfuel transfer to schain
Send eth.getBlock('pending') call to the chain until the transaction mined and save the block number NNN
Check block with call eth.getBlock(NNN)
Expected behavior
The pending block should contain pending transactions from the next block.
Actual state:
The pending block always contains 0 transactions
oleksandrSydorenkoJ
changed the title
"eth_getBlockByNumber ('Pending')" request returns 0 instead of transactions that will be included in the next block
"eth.getBlock('Pending')" request returns 0 instead of transactions that will be included in the next block
Mar 11, 2024
Describe the bug
Due to the block mining time in Skaled and for optimizing performance costs, Skaled has reduced the usage of the 'pending' tag in the 'eth_getBlockByNumber' JSON-RPC call, resulting in some behavior differences from Ethereum.
This issue is also relevant for other JSON-RPC calls, such as eth_getBlockByNumber, eth_getBlockTransactionCountByNumber, eth_getTransactionByBlockNumberAndIndex, etc where the "pending" tag used.
Versions
Skaled: 3.18.0
Environment:
Active Schain medium type 16 nodes
Endpoint to Schain
Adress with Sfuel on balance
To Reproduce
eth.getBlock('pending')
call to the chain until the transaction mined and save the block number NNNeth.getBlock(NNN)
Expected behavior
The pending block should contain pending transactions from the next block.
Actual state:
The pending block always contains 0 transactions
Logs
The text was updated successfully, but these errors were encountered: