Write main DF script

[trentmc]

Scope:

• Do "calculate rewards"
• Do "dispense funds"
• Not for this issue: data consume volume, other features. Other github issues handle that.
• In py, so Trent can drive more readily. And, more amenable to data science analysis.

Links:

• df-py repo. Related: df-js repo (alpha).

TODOs:

• [x] Go through tutorials on GraphQL & TheGraph with python.
  • GraphQL: GraphQL queries, GraphQL spec
  • TheGraph: docs, all subgraphs
  • Ocean * TheGraph: ocean-subgraph, graph-node (fork)
  • py * TheGraph:
  • Google search
  • "Use The Graph to query Ethereum data in Python"
  • TheGraph-Intro ipynb
  • Bubbletea
• [x] In df-py: tests: create a local test setup of oceanv4 contracts
  • [x] Initiate df-py from VestingWallet-CLI repo 923e97
  • [x] In df-py repo, copy in oceanprotocol/contracts v4 branch
  • [x] In tokenspice, clean up all oceanv4 stuff. GH issue
  • [x] In df-py repo: Write basic test to set up fake assets + pools. Leverage tokenspice. d41447
  • [x] In df-py repo: have fake consume c10483
• [x] In df-py: create CLI stubs for "compute rewards", "dispense funds", more
• [x] Get local subgraph going. Resources: (a) docs from TheGraph (b) Ocean Barge
• [x] In df-py: implement "compute rewards"
  • [x] Implement in tests
  • [x] Implement in CLI
• [x] In df-py: implement "dispense funds".
  • [x] Implement in tests
  • [x] Implement in CLI 52e0c4

[trentmc]

Alex C:

checkout this query: https://subgraph.mainnet.oceanprotocol.com/subgraphs/name/oceanprotocol/ocean-subgraph/graphql[…]tokenReserve%7D%0A%20%20%20%20%7D%0A%20%20%7D%0A%7D

we have all join/exit transactions for every pool so we can rebuild user history and see exactly how much each user has in each pool

[trentmc]

Done! :) https://github.com/oceanprotocol/df-py/commit/49a034b43d510896f323d7f9decf94daa2c5d1dc