Skip to content

Commit cc2775b

Browse files
f: more todo
1 parent 396c7c2 commit cc2775b

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

IndexingPaymentsTodo.md

+13-5
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,17 @@
55
* Make `agreementId` unique globally so that we don't need the full tuple (`payer`+`indexer`+`agreementId`) as key?
66
* Rename `Decoder.sol` - Maybe turn it into a library instead?
77
* Support indexing agreement upgadeability, so that there is a mechanism to adjust the rates without having to cancel and start over.
8-
* Support for agreements that end up in `RecurringCollectorCollectionTooLate` or ways to avoid getting to that state.
9-
* Should we deal with zero entities declared as a special case?
10-
* Since an allocation is required for collecting, do we want to expect that the allocation is not stale? Do we want to add code to collect rewards as part of the collection of fees? Make sure allocation is more than one epoch old if we attempt this.
11-
* Reject Zero POIs?
12-
* What happens if the escrow doesn't have enough funds? Since you can't collect that means you lose out forever?
8+
* Economics
9+
* If service wants to collect more than collector allows. Collector limits but doesn't tell the service?
10+
* Support for agreements that end up in `RecurringCollectorCollectionTooLate` or ways to avoid getting to that state.
11+
* Should we deal with zero entities declared as a special case?
12+
* Since an allocation is required for collecting, do we want to expect that the allocation is not stale? Do we want to add code to collect rewards as part of the collection of fees? Make sure allocation is more than one epoch old if we attempt this.
13+
* Reject Zero POIs?
14+
* What happens if the escrow doesn't have enough funds? Since you can't collect that means you lose out forever?
15+
* Don't pay for entities on initial collection?
16+
* Should we set a different param for initial collection time max? Some subgraphs take a lot to catch up.
17+
* How do we solve for the case where an indexer has reached their max expected payout for the initial sync but haven't reached the current epoch (thus their POI is incorrect)?
18+
* Double check cancelation policy. Who can cancel when? Right now is either party at any time.
1319
* Expose a function that indexers can use to calculate the tokens to be collected and other collection params?
20+
* Support a way for gateway to shop an agreement around? Deadline + dedup key? So only one agreement with the dedupe key can be accepted?
21+
* Maybe check that the epoch the indexer is sending is the one the transaction will be run in?

0 commit comments

Comments
 (0)