Setting up TrueStake for SaaS-managed validators
If Allnodes, Stakefish, Kiln, Figment, or another provider operates the node behind your validators, you're SaaS-managed. You own the withdrawal credentials. The provider runs the hardware, keeps the client synced, and handles slashing protection.
That split is exactly what TrueStake is built around: an account is defined by who controls the withdrawal credentials, not who operates the node.
What TrueStake needs from you
Just your withdrawal address, or addresses if you have more than one validator. It's public information — already visible on-chain inside your validators' withdrawal credentials.
Handing it over doesn't grant access to move funds. TrueStake never asks for a provider login, a provider API key, or a private key of any kind. There's no account to connect on your provider's side.
See How TrueStake discovers your withdrawal addresses for the mechanics.
How ingestion works once you're linked
Ingestion for a SaaS-managed account works the same as for any other account. The first run covers your validators' full on-chain history; nightly runs after that keep your dashboard current.
There's nothing provider-specific to configure, and nothing changes if your provider updates their own tooling behind the scenes.
Why TrueStake's record doesn't depend on your provider
TrueStake doesn't read your provider's dashboard, statement, or invoice. Every receipt is reconciled against your validators' actual on-chain settlement events — sweep withdrawals, user-triggered (EIP-7002) withdrawals, fee-recipient payments — cross-checked against TrueStake's own Reth and Lighthouse node data, to within a 100-wei tolerance.
If a provider's number and the chain ever disagree, the chain wins. You'll see that as a reconciliation finding, never a silent correction.
That independence is also why this record is worth having in the first place. If you switch providers, renegotiate a fee, or just want to double-check a statement, your TrueStake record doesn't move with them — it's keyed to your withdrawal address, not to any one provider's books. See why an independent record matters when a provider changes.
Fee recipients and provider rotation
Providers sometimes route your validators' fee recipient — the address that receives priority fees and MEV-Boost payments when your validator proposes a block — through their own infrastructure, and that address can rotate over time.
TrueStake tracks fee-recipient history per validator and attributes each block-proposal payment to the period it actually happened in. The on-chain record is the final authority, not a snapshot of "who your fee recipient is today."
What grade you get
SaaS-managed validators get the same Chain Derived Audit Grade as Solo stakers who run their own node. Owning the withdrawal credentials — not operating the hardware — is what determines the grade.
Questions?
Email support@truestake.io. Include your provider name and your withdrawal address prefix if you're asking about a specific validator.