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
Geth version: 1.10.23
OS & Version: Linux
Commit hash : -
Querying block->transactions->logs return event logs for whole block but should return for each transaction. It could be critical for someone who fetching transactions using graphQL and could lead to double-spends. On 1.10.21 node version it is working as expected.
Expected behaviour
When querying for the transactions in block using graphQL we should receive event logs only for the corresponding transactions.
Actual behaviour
We are receiving event logs for ALL transactions in block for EACH transaction.
Steps to reproduce the behaviour
Make a graphQL query to the node: { block(number:15484104) { transactions { hash logs { account { address } topics data } } } }
Backtrace
-
The text was updated successfully, but these errors were encountered:
System information
Geth version: 1.10.23
OS & Version: Linux
Commit hash : -
Querying block->transactions->logs return event logs for whole block but should return for each transaction. It could be critical for someone who fetching transactions using graphQL and could lead to double-spends. On 1.10.21 node version it is working as expected.
Expected behaviour
When querying for the transactions in block using graphQL we should receive event logs only for the corresponding transactions.
Actual behaviour
We are receiving event logs for ALL transactions in block for EACH transaction.
Steps to reproduce the behaviour
Make a graphQL query to the node:
{ block(number:15484104) { transactions { hash logs { account { address } topics data } } } }
Backtrace
The text was updated successfully, but these errors were encountered: