You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: IndexingPaymentsTodo.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,6 @@
1
1
# Still pending
2
2
3
3
* Arbitration Charter: Update to support disputing IndexingFee.
4
-
* Double check cancelation policy. Who can cancel when? Right now is either party at any time. If gateway cancels allow collection till that point.
5
4
* Expose a function that indexers can use to calculate the tokens to be collected and other collection params?
6
5
* test_SubgraphService_CollectIndexingFee_Integration fails with PaymentsEscrowInconsistentCollection
7
6
* Switch timestamps to uint64.
@@ -15,6 +14,7 @@
15
14
16
15
# Done
17
16
17
+
* DONE: ~~Double check cancelation policy. Who can cancel when? Right now is either party at any time. Answer: If gateway cancels allow collection till that point.~~
18
18
* DONE: ~~If an indexer closes an allocation, what should happen to the accepeted agreement? Answer: Look into canceling agreement as part of stop service.~~
19
19
* DONE: ~~Switch `duration` for `endsAt`? Answer: Do it.~~
20
20
* DONE: ~~Support a way for gateway to shop an agreement around? Deadline + dedup key? So only one agreement with the dedupe key can be accepted? Answer: No. Agreements will be "signaled" as approved or rejected on the API call that sends the agreement. We'll trust (and verify) that that's the case.~~
0 commit comments