Troubleshooting
- Wrong signer: Ensure your
providerSignerKeymatchesAccessRegistry.providerSignerOf(apiId). - Inactive API: Your listing isn’t active yet — finish activation in the dashboard.
- Clock skew: Nodes reject snapshots if
providerTsdrifts too far from chain time; sync NTP. - Duplicate snapshots: If you use
hash-change, unchanged payloads reuse the sameseqNoby design. - Huge payloads: Trim non‑essential fields; consider splitting into paginated sub‑routes.
Last updated on