Francisco de Borja Aranda Castillejo
Francisco de Borja Aranda Castillejo
Hi @gmelodie! I'd like to start contributing to filecoin and estuary, can I grab this one? :)
Bumping this one. In my specific case, I avoid getting `i/o timeout` errors from the websocket by using a customized websocket, and then creating a new ethclient with it. ```...
> It would be nice to add a simple contract and invoke it on the e2e side to demonstrate that this actually works? Yes, that's going to be a second...
Closing this PR as the review has been finalized. I'll open a second PR integrating the contracts into this branch.
@richardhuaaa is this old issue a duplicated of #262 ?
@neekolas what topics do we want to cover with the documentation?
Revisiting and bumping this. Currently we store group messages and identity updates with an expiry of MaxInt64, essentially, forever. When indexing a new event it comes with a BlockTimestamp field...
@mkysel I believe after latest discussions this can be closed?
This still needs some changes in the NodeRegistry.
@mkysel @neekolas should we close this issue and move to taking notes elsewhere?