-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit "Deploy" notification for native contracts #2834
Comments
Looks like this was fixed in #2942. |
@roman-khimov close? |
It'd be perfect if anyone with the current master node and ApplicationLogs (@superboyiii?) could check that the event is indeed present where we expect it (genesis block persist). The code is very convincing to me, but still a quick check before closing won't hurt. |
I've checked the current master (
Just for the record, here's Base64-encoded hashes of native contracts retrieved from Go script:
And also if needed, then here's the current application logs (for
|
So this issue can be closed as completed. |
Contract 0xfffdc93764dbaddd97c48f252a53ea4643faa3fd says it has deployed contract 0xfffdc93764dbaddd97c48f252a53ea4643faa3fd, nice. |
Summary or problem description
Native contracts are deployed by ContractManagement's
OnPersist
method, but what this method does is just pushing contract state to the DB. For regular contracts we have events generated as well since #2150, while there are no such events for native contracts. Of course they're not critical as of now, we know these contracts well and they're only changed at the genesis block, however this makes native contracts somewhat inconsistent with the regular ones and also can be a problem if we're to ever useNativeUpdateHistory
feature with updates made to native contracts at some non-zero blocks.Do you have any solution you want to propose?
Emit "Deploy"/"Update" events for native contracts.
Neo Version
Where in the software does this update applies to?
The text was updated successfully, but these errors were encountered: