Piotr Dyraga
Piotr Dyraga
Some tests failed but it looks like some test environment issue rather than a problem with the code here.
@janpio Done, sorry for the delay. All tests are passing now. :tada:
Another thing to consider: [renaming `group` package](https://github.com/keep-network/keep-core/pull/3093#discussion_r929976372) to clearly indicating the components are used in DKG.
Thank you for submitting the issue @gregbostrom 🙌 This is indeed a problem, same as https://github.com/keep-network/keep-core/issues/1333, that should be solved during the work on https://github.com/keep-network/keep-core/issues/491.
Is it still relevant or are we good to close it?
During work on this card, we need to ensure our subscriptions are handled properly. We have some technical debt to pay in Ethereum integration layer - a lot of code...
- [ ] PoC - 3 days - [ ] code generation - 2 days - [ ] concurrent test - 3 days - [ ] ethereum API update -...
After 12+ hours of executing relay requests locally, I observed a fatal failure of the client: ``` 18:54:58.095 INFO keep-relay: [member:1,channel:579d0,state:*entry.entrySubmissionState] transitioning to a new state at block: [1308] machine.go:132...
@eth-r What should we do with this PR? We can close without merging if we want - this will all stay in the history.
The remaining work has been extracted to separate issues: - https://github.com/keep-network/keep-core/issues/3344 - https://github.com/keep-network/keep-core/issues/3279 - https://github.com/keep-network/keep-core/issues/3145