Abstract

The Station/Meridian team is aiming for major product releases at LabWeek 2023 (Nov 13-17). We likely won’t be able to get everything done as requested by stakeholders, so we need to negotiate a configuration of deliverables that works.

• [ ] @Julian Gruber: adjust dependencies and options now that we have 4 deliverables, and other Spark/Meridian requirements

Deliverables

The key deliverables are:

• STA Station public release with rewards
• MER Meridian Impact Evaluator framework
  • Potential variables:
    • Smart contract tasking (instead of centralized tasking service)
    • Smart task sampling (instead of basic random sampling)
    • Smart contract membership management (instead of implicit membership)
• SPA Spark running on Meridian
• RAT Retrieval attestation
  • ⚠️ There probably isn’t going to be a Boost release with this builtin until labweek. Maybe we won’t even be able to ship a special tagged version towards participating SPs

Dependencies

• STA hard depends on RAT, as without fraud detection neither the rewards paid nor the data produced will be right
• STA soft depends on MER, as while it can’t pay rewards without it, it can pay rewards with a partially implemented Meridian - for example one with a centralized instead of a smart contract orchestrator
• MER soft depends on STA and transitively RAT, as Station/Spark will be the living implementation to ship together with the spec
• RAT soft depends on STA and transitively MER, as while attestation can still be implemented, the network of data producers will be small without rewards

Options

<aside> 💡 Options starting with Prioritise … are mutually exclusive, but can be combined with others, eg. Prioritise Meridian and IE smart contract without tasking.

</aside>

Prioritise Station

➕ STA