SolidPeer
Get started

Changelog

Customer-facing changes to the API contract, wire format, and pricing. Operator-internal infrastructure changes aren't listed here.

2026-05-11

  • Chaingraph query interception is off by default. Customer queries reach Hasura verbatim, scored as written and charged accordingly. Operators who want the prior limit-injection / where-required / per-field-cap / global-complexity-cap rejections back can re-enable each independently via the GATEWAY_CHAINGRAPH_* env knobs.
  • All wire-level 429 responses match QuickNode's error.code = 429 convention. Distinction between rate / balance / token_budget / concurrent is in data.reason.
  • Retry-After header added to rate / concurrent 429 responses (integer seconds, RFC 7231).
  • HSTS now sets includeSubDomains — covers per-customer alias subdomains.
  • Per-token CC budget enforced on WebSocket subscription pushes (previously only on HTTP and registration cost).

2026-05-09

  • Per-tier RPS burst capacity decoupled from sustained RPS. Each tier gets a burst pool 20× its sustained rate (Hobby 25 RPS sustained / 500 burst, etc.), refilling at the sustained rate. Wallet cold-starts no longer trip rate-limit 429s.
  • Per-token spend display on the dashboard's token detail card — shows current CC used vs cap, with a progress bar.
  • server.ping charges 10 CC (was 100). It's a no-op keepalive; charging full rate distorted the cost of long-lived WS connections.

2026-05-08

  • Per-customer subdomain aliases. Create a 5-word slug (server-minted from the EFF wordlist, ~64-bit entropy) and the URL https://<slug>.solidpeer.io/ routes to your token / system / network. Hides the URL path; useful for shareable curl one-liners.
  • GraphQL introspection on Chaingraph can be enabled per-deploy via env (off by default).

2026-05-07

  • Telegram bot notifications. Link your account to a Telegram chat from the dashboard; receive payment / balance / expiry alerts.
  • Web push (RFC 8030) for browser notifications.
  • Per-account notification thresholds. 90% CC, 100% CC, 7-day expiry, 1-day expiry — all on by default for paid tiers.

Earlier

The pre-launch period (April – early May 2026) saw the gateway built from scratch on Bun. Significant changes during this period included tier shape calibration, the move to flat per-system pricing, and the first round of per-system load testing.