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: docs/RPC_OPERATIONS.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,12 @@ contract outcome, not a provider outage. The caller receives the RPC error and
24
24
the provider remains available for other calls. Transport failures, malformed
25
25
responses, and missing archive state still trigger capability-specific failover.
26
26
27
+
Routed RPC exceptions retain the redacted JSON-RPC error payload, including
28
+
ABI revert data. The pinned-state decoder uses that evidence to recognize
29
+
`Invalid token ID` only at a verified same-receipt NFT mint/burn boundary.
30
+
Keeping only the provider message loses this proof and retries valid receipts
31
+
indefinitely. Unproven absence and unrelated errors still fail enrichment.
32
+
27
33
## Goldsky measurements and limits
28
34
29
35
A small anonymous-output probe from the production host verified the donated provider privately: chain 4663; exact matching block/header and log digests against the local node; old block headers; USDG `decimals()` at blocks 30,000,000 and 56,400,000; receipts; `debug_traceTransaction` with `callTracer`; and a four-item JSON-RPC batch. The local pruned node could not answer those archive-state calls. Individual successful Goldsky requests in this probe took roughly 76–352 ms; these are samples, not percentile/SLA claims.
0 commit comments