-
Notifications
You must be signed in to change notification settings - Fork 6
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
EVM events can be obtained via RPC-EVM! (integration test?) #118
Closed
Labels
High Priority
Proposed to focus on this when other tasks are present
Sprint Candidate
Proposed by PO for the very next sprint
Comments
tonimateos
added
Sprint Candidate
Proposed by PO for the very next sprint
High Priority
Proposed to focus on this when other tasks are present
labels
Oct 26, 2023
tonimateos
changed the title
Integration test to catch EVM events
EVM events can be obtained via RPC-EVM! (integration test?)
Oct 26, 2023
Note: Integration tests are put in main, but if there is a bug discovered, since this may end up in a hotfix, then branch from last release tag, to avoid merging code that is still developed during the sprint. |
ghost
self-assigned this
Oct 26, 2023
|
ghost
linked a pull request
Oct 26, 2023
that will
close
this issue
the linked PR contains a work that can be continued to properly investigate the evm log issue and adding integration testing suite |
Logs bugs are fixed. v0.3.2 was released and deployed in seldon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
High Priority
Proposed to focus on this when other tasks are present
Sprint Candidate
Proposed by PO for the very next sprint
As a DApp developer on the Evochain I want to get the events of createCollection and MintAsset by using standard web3 tools connected to the RPC endpoint, so that my DApps, which track events, can work
Note: have a look at this code that shows potential issues with current implementation: https://github.com/freeverseio/experiments/tree/master/laos_hardhat
ACCEPTANCE:
The text was updated successfully, but these errors were encountered: