Meridian Roadmap

💡
This document is currently in flux, as we’re figuring out the set of . It is based on a previous understanding of priorities, as described in and .

Starmaps Roadmap

https://starmap.site/roadmap/github.com/filecoin-station/roadmap/issues/1

Milestones

flowchart LR
  PN[Non-technical preparation]
  subgraph PT[Technical preparation]
    B[Boost]
  end
  M[Measure]
  E[Evaluate]
  R[Reward]
  M --> E
  E --> R
  B --> M
  PN --> R

Unless resourcing or dependencies on external teams inform us otherwise, the milestones Measure, Evaluate and Reward should be implemented sequentially.

The preparation milestones can happen in tandem, as visualized above. Eventually during Measure, Technical preparation: Boost will need to have been completed. Eventually during Reward, Non-technical preparation will need to have been completed.

M1-M3 have the same deadline as there’s a lot of uncertainty on the Boost part:

  • Which implementation is going to be approved?
  • How long will it take to roll out?

There’s an alternative way to structure this: Target the existing frisbii server as an SP in all of the milestones, then add a milestone for proper Boost support.

M0: Non-technical preparation @Patrick Woodhead

  1. Talk to legal
    1. What are the implications of this architecture from a legal perspective
    1. What should we look out for
    1. Can we comfortably issue rewards like this
    1. Are we able to help peers with push rewards initially?
  1. Secure funds
    1. We need one or more pots of FIL for initial rewards, for as long as there are no SPARK customers yet
    1. Talk to Reputation working group
    1. Talk to Network funding
  1. Reach out to contractors for the smart contracts
  1. Reach out to Security audit firms

M1: Boost retrieval attestation

  1. Make SPs participate in attestation protocol @Miroslav Bajtoš
    1. Write spec for signature chain header (all protocols, start with http) ✅
      1. Ensure chains can’t be reused (include hash of unique request identifier)
      1. See
    1. Create GH issue on Boost repo (https://github.com/filecoin-project/boost) + follow up where requested / as necessary
  1. Dev provider setup @Julian Gruber 3d ✅
    1. Create dev server using https://github.com/ipld/frisbii which implements the attestation logic ✅
    1. Deploy dev server for measure to target ✅

This milestone will follow

M2: Measure

TODO @Julian Gruber: This section needs to be updated. With the IE smart contract, there won’t be a separate measure smart contract

  1. Smart Contract
    1. Function to emit commitment event
  1. Service
    1. Phase: Store ✅
      1. Receive logs ✅
      1. Store logs in database ✅
      1. Store attestation token @Julian Gruber
    1. Phase: Commit @Julian Gruber 1w
      1. Periodically fetch logs ✅
      1. Create Merkle tree ✅
      1. Store Merkle tree ✅
      1. Provision wallet
      1. Call smart contract with Merkle root hash
  1. Database ✅
    1. Deploy ✅
  1. Peer: Spark module @Miroslav Bajtoš
    1. Submit logs to service ✅
    1. Start request attestation
      1. Forward headers in Lassie
    1. Attach attestation token

This milestone will follow

M3: Evaluate

TODO @Julian Gruber: This section needs to be updated. With the IE smart contract, there won’t be a separate evaluate smart contract, plus evaluation is a 1-phase process again.

  1. Service: Stage I / Data preprocessing 1w @Julian Gruber
    1. Periodically fetch logs from measure database
    1. Detect fraud: Validate attestation
    1. Aggregate
      1. Buckets: Honest logs, fraudulent logs
      1. Sum measurements
    1. Store aggregates in database
    1. Call smart contract with aggregated measurements
  1. Database
    1. Deploy
  1. Smart Contract
    1. Function to emit commitment events
  1. Service: Stage II 2w @Julian Gruber
    1. Simple CRUD UI for managing evaluations
      1. Create evaluation
      1. Get evaluation status
      1. Get evaluation result
      1. Approve evaluation
      1. Submit evaluation
    1. Backend
      1. Fetch honest aggregates from database
      1. Evaluate
      1. Create batches of evaluations
      1. Call rewards factory smart contract with batches

This milestone will follow

M4: Reward

  1. Smart Contract: Payment Splitter
    1. Contract template
    1. Claim function
  1. Smart Contract: Rewards Factory
    1. Function that accepts evaluation batch
    1. Deploy payment splitter smart contract with rewards inlined
  1. Peer (Station): Claim FIL @Julian Gruber
    1. UI
      1. Write UI spec ✅
      1. Visualize unclaimed rewards
      1. Ability to claim FIL, with confirmation
    1. Backend
      1. Discovery of rewards available to claim

This milestone will follow

M5: Soft launch as Rewards Technical Preview

M6 could take significant time, depending on the strategy we use. We would like to be able to release to a technical audience first, which is fine with transferring FIL to the Station wallet in order to claim their rewards.

  1. Update Station Website
  1. Messaging and internal outreach
  1. Airdrops and /or other schemes
  1. Spotlight / internal announcements

M6: Claim rewards with empty wallet

  1. Contracts
    1. Solve initial claim without FIL in wallet
  1. Peer (Station)
    1. Potentially UI work

This milestone will follow

M7: Product & GTM (Station)

  1. Update Station Website
  1. Messaging and outreach
  1. Airdrops and /or other schemes
  1. Decide on talks for Labweek and other events for Meridian / Station
  1. Swag
  1. Other incentives beyond financial ones