Retroactive Morpho reward Distribution automation

[Xeonus]

Morpho wants to distribute MORPHO rewards to boosted pool depositors. At the moment, they only distribute rewards every 2 weeks based on the 2 previous weeks deposits into their vaults. Given this, the cleanest solution is to also count boosted pool deposits retroactively and distribute rewards accordingly

Requirements

• Morpho tracks rewards to v3 vault
• Maxis provide code-base to track deposits into boosted pools retroactively (v3 subgraph has pool snapshots)
• Rewards get distributed to depositors either by Morpho or Maxis

Not clear yet:

• If Morpho will send rewards to a new safe or do its own distro based on our airdrop csv
• Angle can't do retroactive campaigns, so we need to do our own airdrop

Implementation details

Example: deployed test pool on Gnosis chain

Endpoint: https://api.studio.thegraph.com/query/75376/balancer-v3-gnosis/version/latest

Query operation:

query Users($where: User_filter, $block: Block_height) {
  users(where: $where, block: $block) {
    shares {
      balance
      id
      user {
        id

      }
    }
  }
}

Variables:

{
  "where": {
    "shares_": {
      "pool_in": [
        "0xd1d7fa8871d84d0e77020fc28b7cd5718c446522"
      ],
      "balance_gt": 0.0001
    }
  },
  "block": {
    "number_gte": 37435326
  }
}

Response:

{
  "data": {
    "users": [
      {
        "shares": [
          {
            "balance": "0.210018189788151984",
            "id": "0xd1d7fa8871d84d0e77020fc28b7cd5718c446522-0x75d06bae37a9c349142fe7cee77804900b1c0ec3",
            "user": {
              "id": "0x75d06bae37a9c349142fe7cee77804900b1c0ec3"
            }
          }
        ]
      }
    ]
  }
}
```

[gosuto-inzasheru]

ref: https://docs.merkl.xyz/merkl-mechanisms/types-of-campaign/airdrop

[Xeonus]

As discussed with Fabio and Franz and @gosuto-inzasheru , the subgraph has data for each block. We therefore shall query by a set of blocks every x hours to get shares. As there are no gauges yet, this approach is ok. Need to add additional logic once staking gauges go live! We can reuse some logic from this repo Trit made: https://github.com/BalancerMaxis/ecosystem_balances_example

More efficient query logic shared here

Query:

query PoolShares($where: PoolShare_filter, $block: Block_height) {
  poolShares(where: $where, block: $block) {
    user {
      id
      shares {
        balance
      }
    }
  }
}

Variables (example for gnosis boosted v3 pool):

{
  "where": {
    "balance_gt": 0.001,
    "pool_in": ["0xd1d7fa8871d84d0e77020fc28b7cd5718c446522"]
  },
  "block": {
    "number": 37435326
  }
}

[gosuto-inzasheru]

https://github.com/balancer/bal-mining-scripts/pull/125/files