Describe the bug
While testing the https://github.com/nspcc-dev/neo-go/pull/3402, I discovered that ApplicationLogs plugin returns improper result of getapplicationlog RPC call. The result contains wrong contract field value of notifications section. For example, getapplicationlog for genesis block of mainnet has exactly the same notification's contract hash for all notificaitons (for both OnPersist and PostPersist triggers), 0xd2a4cff31913016155e38e474a2c06d08be276cf (native GasToken). While I'd expect contract hashes of notifications to have proper values.
Describe the bug While testing the https://github.com/nspcc-dev/neo-go/pull/3402, I discovered that
ApplicationLogs
plugin returns improper result ofgetapplicationlog
RPC call. The result contains wrongcontract
field value ofnotifications
section. For example,getapplicationlog
for genesis block of mainnet has exactly the same notification's contract hash for all notificaitons (for both OnPersist and PostPersist triggers),0xd2a4cff31913016155e38e474a2c06d08be276cf
(native GasToken). While I'd expect contract hashes of notifications to have proper values.This bug was introduced in master after 20th of March, because in that day I successfully built neo-modules master and checked genesis block notifications within the scope of https://github.com/neo-project/neo/issues/2834#issuecomment-2008142934. I'm suspecting that this bug was introduced by https://github.com/neo-project/neo-modules/pull/865, because this PR was merged 21th of March and makes a lot of changes in ApplicationLogs plugin, but we need to check.
To Reproduce Steps to reproduce the behavior:
getapplicationlog
RPC request to RPC server with genesis block hash;The result from the fresh master is:
Expected behavior The expected result is mentioned in https://github.com/neo-project/neo/issues/2834#issuecomment-2008142934, it should have proper contract hashes for all genesis notifications:
Platform:
(Optional) Additional context
This bug is critical for 3.7, should be solved before the release.