turinglabs
turinglabs
@irenegia this is the miro board: https://miro.com/app/board/uXjVPAMsLPg=/?share_link_id=57183390559
@0xjona please follow @gdelsi if needed for those improvements
Starting a discussion about what data must be collected from the referee network. At the moment i've inserted those statuses: - `PING`: signal that says node is available, i'm sending...
We need one more signal: - `ERROR`: signal that shows the error if happens
@0xjona @irenegia we need to discuss with @claudiofabbro on how to show data. All things i proposed in comments above are implemented and collected, now we need to understand how...
@irenegia the API part is done, we collect data as i described [here](https://github.com/protocol/retriev/issues/15#issuecomment-1227051874) but there's no graphic implementation. I think we should continue working on that with Elisea.
@irenegia here we are: @gdelsi
Split the `SLASH_` in two different signals to have more granularity: `SLASH_AS_LEADER_`: When a referee slashes the provider as leader `SLASH_WITH_CONSENSUS_`: When a referee collects the slashes and post them...
@nicola can we close this issue since is now implemented in notion? cc @irenegia