How TrueStake discovers your withdrawal addresses
To link your validators, TrueStake needs one thing from you.
Your withdrawal address (or addresses). That's it — no validator index list, no provider login, no private key.
What a withdrawal address is
Every 0x01 (execution-address) or 0x02 (compounding) validator has a withdrawal address embedded directly in its on-chain withdrawal credentials. That's the address the protocol pays out to — automatic sweeps, EIP-7002 withdrawals, everything else.
It's public information. Anyone can look it up on a block explorer; it doesn't grant access to move funds.
How discovery works
You give TrueStake an address. TrueStake reads public chain state and finds every validator whose withdrawal credentials point to it — no manual list of validator indexes required.
Adding validators later
You don't need to tell TrueStake every time you activate a new validator. As long as its withdrawal credentials point to an address you've already linked, TrueStake picks it up automatically on the next ingestion run.
Multiple withdrawal addresses
If you use more than one withdrawal address, link each one — TrueStake discovers the validators under every address you give it, and they all roll up into the same account: one dashboard, one Tax Report per year, with every line still attributed to its own validator.
No login, no API key, no custody
TrueStake reads public chain state only. There's no KYC step, no exchange API key, and no custody of your funds at any point.
TrueStake finds your validators; it never controls them. This isn't a beta limitation — it's permanent.
If you stake through a provider
The mechanism is identical whether you run your own node or a provider like Allnodes, Stakefish, Kiln, or Figment operates it for you. Discovery is keyed on the withdrawal address, not on who runs the hardware. See Setting up TrueStake for SaaS-managed validators.
If your validators are still 0x00
Legacy BLS (0x00) credentials don't contain a withdrawal address at all — there's nothing on-chain for TrueStake to key discovery off until the validator is upgraded to 0x01. See What if my validators still have 0x00 (BLS) withdrawal credentials? for what TrueStake can and can't reconcile in the meantime.
Questions?
Email support@truestake.io with your withdrawal address prefix if a validator isn't showing up as expected.