Skip to main content

FAQ

Access & Authentication​

How do I authenticate?​

Depends which product you mean — there's no single answer here. Tokens for ShredStream and Relayer/TPU. Source-IP allowlists for Direct Shreds. SWQOS HTTP skips auth entirely and uses an on-chain tip instead; SWQOS QUIC checks a signing keypair. Full matrix: Authentication.

Can I share credentials across multiple servers or apps?​

For the token-based products, yes. The token is scoped to your subscription, not to a single machine, so it works across as many backends, workers, or clients as you want. Allowlist-based products (Direct Shreds, SWQOS QUIC, Relayer/TPU) don't work that way — every source IP or signing pubkey needs to be listed explicitly.

How do I rotate credentials without downtime?​

Generate the new credential first — a new token, or a new IP/pubkey — in the dashboard, deploy it, and only then revoke the old one. Both stay valid mid-swap, so there's no gap.

Plans & Billing​

What payment methods are accepted?​

Card or crypto, both configured from the dashboard. Crypto invoices settle in USDC, on either Solana or Ethereum.

How do I upgrade or change plans?​

Dashboard → service page → Plan. The change takes effect immediately; billing gets prorated on the next cycle, not on the spot.

Products​

Which chains are supported?​

Solana, exclusively. That's not a roadmap gap — it's where Everstake's validator stake actually converts into a latency and inclusion advantage, so it's the only chain these products are built for.

Status & Privacy​

Is there an SLA?​

Not on self-serve tiers. Those run best-effort on Everstake's production validator infrastructure, no contract behind it. Enterprise customers can negotiate a custom SLA separately. Either way, the real-time picture is here: status page.

Do you log my requests?​

Operational metadata, and nothing more — request counts, response times, error rates, used for billing and reliability. Request bodies, response bodies, transaction contents: none of that gets logged. Same rule applies validator-side, on Searcher Connection — metadata-only on the validator's traffic too.