You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the discussion in CheckerNetwork/core#259, we want each Station Module to own the implementation of querying rewards scheduled for the Station operator.
A possible solution: add a new API similar to Zinnia.jobCompleted() and a new event type that can be printed to stdout, similar to the existing type jobs-completed.
The text was updated successfully, but these errors were encountered:
Question: Not every module might use scheduled rewards, it's entirely possible for a module to pay directly and not have an understanding of scheduled rewards. How can we unify this?
I assume we need to know more about the 2nd module before it makes sense to continue with this issue.
Question: Not every module might use scheduled rewards, it's entirely possible for a module to pay directly and not have an understanding of scheduled rewards.
Agreed 💯
How can we unify this?
I assume we need to know more about the 2nd module before it makes sense to continue with this issue.
+1, it's hard to design a generic solution when we have only one module.
OTOH, with the current Station Desktop UI, it's very clear what options modules have:
They can pay operators directly, in which case the Station UI will see the paid rewards in the wallet balance (& transaction list) and no additional support is required from the module.
The module implements some variant of scheduled rewards, in which case the module needs to tell the Station what amount of rewards is allocated to the user but not paid yet.
If a module needs something else, then we will need to change the Station Desktop UI & design to support that. Potentially also the Station Core vs Station Desktop integration, since it's currently the responsibility of Station Core to discover scheduled rewards. See
My goal for this task was to move the logic querying the smart contract from Station Core to the Zinnia module. Supporting modules that don't use scheduled rewards or use a different mechanism is IMO out of the scope of this task.
Per the discussion in CheckerNetwork/core#259, we want each Station Module to own the implementation of querying rewards scheduled for the Station operator.
A possible solution: add a new API similar to
Zinnia.jobCompleted()
and a new event type that can be printed to stdout, similar to the existing typejobs-completed
.The text was updated successfully, but these errors were encountered: