-
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
feat: process lightnode sale events #414
feat: process lightnode sale events #414
Conversation
Should this go into |
I think we should merge the current (after this PR) We can leave this PR into dev16 so it's easier to read, then merge everything to master, and push a new dev16 branch. The same we did on paloma. What do you think? |
ba55734
to
81ca12f
Compare
Also, increase logging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I think this is a much cleaner solution now.
* chore: rename eth messages (#412) * feat: process lightnode sale events (#414) * chore: update paloma deps to local development * feat: read node sale events from compass * chore: add unified skyway events handler * feat: use unified skyway event handler * chore: remove left pad on paloma address * fix: wrong NodeSaleEvent hash Also, increase logging. * chore: update REAME to point to 1.12.4 --------- Co-authored-by: Christian Lohr <[email protected]>
Related Github tickets
Background
We need pigeon to pick up on node sale events and report them to paloma. These events will come from compass, following the implementation in palomachain/compass-evm#38. This PR adds support to read and relay those events.
Note: This uses
dev16
branch as base since it builds on top of the renamed skyway calls.Testing completed
Breaking changes