-
Notifications
You must be signed in to change notification settings - Fork 40
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
bug: events not emitted for proxy calls #1964
Comments
|
|
|
My inference on the issue:
Conclusion: Proxy call events are suppressed |
hi @laciferin2024 ! I've tried to reproduce the issue you described by writing two very simple smart contracts, where contract A sends txn to contract B and contract B emits an event. you can find the contract in the attached files. I found no issues in this setup. could you please add more details on how do you think this bug is reproducible? thank you! |
Ok i will write the reproducer then |
Describe the bug
The dePin I built is working on ethereum but fails to work e2e on skale. After debugging around for 11 hours, I discovered that all evm operations are successfully. Deals are agreed but events are not emitted from the Storage Contract
This issue is the storage contract: https://aware-fake-trim-testnet.explorer.testnet.skalenodes.com/address/0x298e6C04a8cB0569cF02427CBF4511E8398a422B?tab=txs
Its a secondary contract managed by Controller contract.
WE have services listening to the DealStateChange events.
But none of the services are getting those events.
Additionally deals are getting stored and updated successfully via these txs: https://aware-fake-trim-testnet.explorer.testnet.skalenodes.com/address/0x7dF66926b83Bda6E9D95267D51a38EAb9579e93B
Screenshots
The gud news is that evm is working just fine, its updating deals. I manually updated deals without contract modifications and its all working but for e2e working we will need the nodes to emit the events of storage and payment contracts!
The text was updated successfully, but these errors were encountered: