Bug: DeniedAt is not taken into account

graphprotocol / allocation-optimizer

Agents and algorithms for optimizing Indexer decision problems.

MIT License

13 stars 14 forks source link

Bug: DeniedAt is not taken into account #37

Closed fordN closed 1 year ago

fordN commented 1 year ago

Subgraph deployments with non-0 deniedAt values will not capture any indexing rewards. These subgraphs should have an expected profit from indexing rewards of 0.

anirudh2 commented 1 year ago

This should be fixed in the latest release - v2.3.0! If you run into further issues, feel free to re-open!