graphprotocol / indexer-rs / 29513639787

72%

push

github

perf: stop querying the network subgraph on every TAP receipt (#1069)

* perf(service): move allocation-redeemed check to a background watcher

The TAP receipt path queried the network subgraph once per receipt to ask whether the
allocation's escrow was already redeemed, blocking every paid query on an external round trip.
A watcher now keeps a snapshot for the active allocations and the check reads it in memory.

* perf(service): read RAV redemption from postgres, not the subgraph

The redeemed check no longer polls the network subgraph at all. indexer-agent already records
when a collection's closing RAV is redeemed on-chain; the check now loads those rows and stays
current through a trigger with pg_notify, the same pattern the deny-list check uses.

* fix(service): reject from redeemed_at so the check can fire in time

The final flag is only set a finality window after redemption, past the default buffer in
which receipts still pass eligibility, so the check never fired. Keying on last and redeemed_at
fires at redemption time; rows are scoped per service provider and reconnects trigger reloads.

* docs(service): state when the redeemed check can actually fire

In the routine lifecycle redemption follows the same recently-closed buffer that gates the
eligibility check, so by the time a closing RAV is redeemed, eligibility already rejects the
receipt; the check's real role is insurance against out-of-band redemptions, not a routine gate.

* fix(service): re-listen before resyncing redeemed RAVs after reconnect

When the notification connection dropped, the watcher reloaded the redeemed set while still
disconnected; sqlx only reconnects on the next receive call, so a redemption landing between
the reload and the reconnect went unseen. Re-issue LISTEN first, then reload, as at startup.

* fix(service): resync redeemed RAVs when a notification fails to parse

The watcher used to log and skip a notification it could not parse. The payload comes from
this... (continued)

216 of 238 new or added lines in 2 files covered. (90.76%)

10830 of 15117 relevant lines covered (71.64%)

112.75 hits per line