Figment vs Blockdaemon Figment leads by 12 points.
Figment scores 12 points above Blockdaemon, led by slashing cover, rate transparency, and lock-up disclosure. Figment ranks #4 and Blockdaemon #7 of 7 published staking. Every term of the gap is on the ledger below; the inputs are on the audit receipt.
FIFigment72
vs
BLBlockdaemon60
Scores are out of 100; published scores fall within 41–99 · ranks #4 and #7 of 7
Figment scores 12 points above Blockdaemon, led by slashing cover, rate transparency, and lock-up disclosure.
FIFigment #4 of 772
BLBlockdaemon #7 of 760
Scores are out of 100; published scores fall within 41–99; a bar is empty at 41 and full at 99.
Why, term by termFigment leads on 3 of 4 published criteria; Blockdaemon on 0. The terms sum to the gap.
TermFigmentBlockdaemonWeightPoints
Slashing cover5/102/108.2+6.4for Figment+3.3 of 32
Rate transparency6/103/105.8+4.5for Figment+2.3 of 32
Lock-up disclosure6/105/105.3+1.4for Figment+0.7 of 32
Net of the terms+12.2
Reproduced gap+12.2
Published gapAfter score rounding and bounds — see the note below7260+12.0
Weight is in points of the 86-point weighted total. Points are score points of the gap between the two.
FigmentScore 72Institutional non-custodial validator operator publishing a 25-network catalog table (2026-09-28 count) with per-network unbonding and 28 named custody integrations, whose only public price is an Ethereum self-serve app fee stated as "10% of total rewards" in an answer that first scopes it to execution-layer rewards, while the institutional contract rate, and the size of its slashing coverage, are both set behind "Meet With Us".Strength: Unbonding disclosure — 6/10Watch-out: The number you would actually pay is not on this site, and the one number that is on it does not say what it is charged on. Figment's only stated fee is the Ethereum self-serve app's, on https://www.figment.io/products/staking-app/ : you "only pay a service fee when your validator is selected to propose a block and earns execution layer rewards", and then "Currently, the service fee is 10% of total rewards, but is subject to change." — so the page does not say whether the 10% is taken on execution-layer or on total rewards. The second, conflicting rate (30% of execution layer rewards) that https://www.figment.io/staking/protocols/ethereum/ printed in August was gone from that page on 2026-09-28. The 10% describes the ETH self-serve app, not an institutional rate, and the institutional pages print no fee at all. Do not mistake the "Avg. Public Node Fee" column on the protocols catalog for Figment's price — it is undefined on the page, and its Ethereum cell, "Varies" in August, read "10%" on 2026-09-28, matching the app fee without saying it is one, so treat it as an undefined benchmark, not a quote. The coverage that reads like indemnity is unquantified the same way: the only insurer Figment names, Nexus Mutual, is an opt-in purchase limited to Ethereum double-sign; the "multi-tiered coverage, including insurance and Figment's balance sheet" on the solutions pages carries no limit and no basis; and the one thing Figment says it "contractually commit[s]" to is slashing ALERTING, not reimbursement. Before committing, make the contract state (a) your actual commission and its base per network, and (b) the coverage limit in figures and who underwrites it — because on the public record neither exists.BlockdaemonScore 60Bank-facing non-custodial validator operator (70+ protocols per its homepage counter, though /validators says "50+ protocols"; ISO 27001 / SOC 2 Type II claimed; $110B+ assets secured platform-wide but only "$6+ billion" in staking infrastructure) whose staking pitch rests on a "100% slashing insurance guarantee" that names no underwriter, no limit and no policy anywhere on its own domain — while publishing tiered self-serve per-compute-unit pricing for its API product and no staking commission at all.Strength: Unbonding disclosure — 5/10Watch-out: Read the guarantee's scope before you read its size, and note that Blockdaemon's own pages disagree about it. The headline is an absolute — "backed by 100% slashing insurance guarantee" (/staking) — but the three pages that say anything about what the policy responds to do not agree: /validators scopes it to rewards ("Customers are 100% guaranteed under our slashing insurance policy against rewards missed due to downtime and slashing risks"), while the blog's disclaimer points at principal ("Covers affected staked balances. Additional terms and conditions apply. Inquire here for more information.") and /trust-center says only "Our slashing protection, backed by leading risk advisors and insurers, safeguards clients against potential losses." Not one names a carrier. The single insurance party identified on the entire domain is Marsh, which Blockdaemon itself calls "the world's leading insurance broker and risk advisor" — a broker, not the underwriter that pays; a domain-wide search for Chainproof, Munich Re, Lloyd's, Nexus Mutual, 'underwriter', 'carrier', 'aggregate limit', 'policy limit' and 'certificate of insurance' returns nothing. So settle this in writing before committing: who is the risk carrier, what is the per-incident and aggregate limit, and does cover attach to slashed principal or only to foregone rewards. Second-order: do not read the homepage's "$110B+ Assets Secured" as staked AUM — the staking pages size that business at "$6+ billion worth of staking infrastructure", an 18x difference, because the $110B is the whole platform including custody. Third: the protocol count is inconsistent on Blockdaemon's own site — the homepage counter says 70+ Protocols while /validators says "Supports 50+ protocols" and /protocols links 61 pages.
Quick facts
At a glance
2 of 3 rows read the same for both.
FactFigmentBlockdaemon
PricingSnapshotFigment app FAQ "How much does it cost to stake through the Figment app?" on https://www.figment.io/products/staking-app/ (fetched 28 September 2026): "You keep all of the consensus layer rewards earned by your validator when staking through the Figment app and only pay a service fee when your validator is selected to propose a block and earns execution layer rewards. This fee is collected on-chain automatically through a smart contract. Currently, the service fee is 10% of total rewards, but is subject to change." That is the Ethereum self-serve app rate; the sentence scopes the fee to execution-layer rewards and then states it as a share of total rewards, and the page does not say which reading governs. It is not an institutional contract rate: the custodian and asset-manager solution pages print no fee and route to "Meet With Us", and the Staking Terms of Use (Last Updated August 21st, 2026) say only that service fees "are publicly available on the relevant block explorer for each Supported Blockchain and are subject to change at any time for any reason."Blockdaemon prints no staking commission figure. The only pricing statement is the "Commission Fee" entry in the glossary of its Trust Center (https://www.blockdaemon.com/trust-center, fetched 28 September 2026): "The Validator charges the Delegators who choose to stake their tokens to the protocol via the validator infrastructure. This fee is charged as a % of any rewards distributed by the protocol to that validator." The same entry ends: "Validators set the commission fee %, but are only able to change it in accordance with limitations set by the Network. The Commission Fee is public information published on the Network, accessible by any participants including Delegators." That is a general definition of how proof-of-stake commission works, not Blockdaemon's price; the staking, validators and custodian pages show reward rates and route to "Get in touch", so the rate for a contract is reachable only through sales or by reading each validator's on-chain commission.
Asset coverageEditorial——
Region fitSnapshotglobalglobal
From the published criteria
Which should you pick?
FI
Figment
72#4 of 7
Leads
Pick it when
Pick Figment if slashing cover matters most — it scores 5/10 to Blockdaemon's 2/10 there (weight 34).
Strength
Unbonding disclosure — 6/10
Tradeoff
The number you would actually pay is not on this site, and the one number that is on it does not say what it is charged on. Figment's only stated fee is the Ethereum self-serve app's, on https://www.figment.io/products/staking-app/ : you "only pay a service fee when your validator is selected to propose a block and earns execution layer rewards", and then "Currently, the service fee is 10% of total rewards, but is subject to change." — so the page does not say whether the 10% is taken on execution-layer or on total rewards. The second, conflicting rate (30% of execution layer rewards) that https://www.figment.io/staking/protocols/ethereum/ printed in August was gone from that page on 2026-09-28. The 10% describes the ETH self-serve app, not an institutional rate, and the institutional pages print no fee at all. Do not mistake the "Avg. Public Node Fee" column on the protocols catalog for Figment's price — it is undefined on the page, and its Ethereum cell, "Varies" in August, read "10%" on 2026-09-28, matching the app fee without saying it is one, so treat it as an undefined benchmark, not a quote. The coverage that reads like indemnity is unquantified the same way: the only insurer Figment names, Nexus Mutual, is an opt-in purchase limited to Ethereum double-sign; the "multi-tiered coverage, including insurance and Figment's balance sheet" on the solutions pages carries no limit and no basis; and the one thing Figment says it "contractually commit[s]" to is slashing ALERTING, not reimbursement. Before committing, make the contract state (a) your actual commission and its base per network, and (b) the coverage limit in figures and who underwrites it — because on the public record neither exists.
BL
Blockdaemon
60#7 of 7
Pick it when
Blockdaemon leads Figment on no published criterion and no score dimension — pick it only if a fact outside the score (country, funding rail, custody) decides for you.
Strength
Unbonding disclosure — 5/10
Tradeoff
Read the guarantee's scope before you read its size, and note that Blockdaemon's own pages disagree about it. The headline is an absolute — "backed by 100% slashing insurance guarantee" (/staking) — but the three pages that say anything about what the policy responds to do not agree: /validators scopes it to rewards ("Customers are 100% guaranteed under our slashing insurance policy against rewards missed due to downtime and slashing risks"), while the blog's disclaimer points at principal ("Covers affected staked balances. Additional terms and conditions apply. Inquire here for more information.") and /trust-center says only "Our slashing protection, backed by leading risk advisors and insurers, safeguards clients against potential losses." Not one names a carrier. The single insurance party identified on the entire domain is Marsh, which Blockdaemon itself calls "the world's leading insurance broker and risk advisor" — a broker, not the underwriter that pays; a domain-wide search for Chainproof, Munich Re, Lloyd's, Nexus Mutual, 'underwriter', 'carrier', 'aggregate limit', 'policy limit' and 'certificate of insurance' returns nothing. So settle this in writing before committing: who is the risk carrier, what is the per-incident and aggregate limit, and does cover attach to slashed principal or only to foregone rewards. Second-order: do not read the homepage's "$110B+ Assets Secured" as staked AUM — the staking pages size that business at "$6+ billion worth of staking infrastructure", an 18x difference, because the $110B is the whole platform including custody. Third: the protocol count is inconsistent on Blockdaemon's own site — the homepage counter says 70+ Protocols while /validators says "Supports 50+ protocols" and /protocols links 61 pages.
Self-identify in 10 seconds
Which one is actually for you?
FIFigmentLeads
Choose Figment if slashing cover matters most
Slashing cover: 5/10 against 2/10 for Blockdaemon (weight 34)
Rate transparency: 6/10 against 3/10 for Blockdaemon (weight 24)
Lock-up disclosure: 6/10 against 5/10 for Blockdaemon (weight 22)
FigmentScore 72Institutional non-custodial validator operator publishing a 25-network catalog table (2026-09-28 count) with per-network unbonding and 28 named custody integrations, whose only public price is an Ethereum self-serve app fee stated as "10% of total rewards" in an answer that first scopes it to execution-layer rewards, while the institutional contract rate, and the size of its slashing coverage, are both set behind "Meet With Us".Strength: Unbonding disclosure — 6/10Watch-out: The number you would actually pay is not on this site, and the one number that is on it does not say what it is charged on. Figment's only stated fee is the Ethereum self-serve app's, on https://www.figment.io/products/staking-app/ : you "only pay a service fee when your validator is selected to propose a block and earns execution layer rewards", and then "Currently, the service fee is 10% of total rewards, but is subject to change." — so the page does not say whether the 10% is taken on execution-layer or on total rewards. The second, conflicting rate (30% of execution layer rewards) that https://www.figment.io/staking/protocols/ethereum/ printed in August was gone from that page on 2026-09-28. The 10% describes the ETH self-serve app, not an institutional rate, and the institutional pages print no fee at all. Do not mistake the "Avg. Public Node Fee" column on the protocols catalog for Figment's price — it is undefined on the page, and its Ethereum cell, "Varies" in August, read "10%" on 2026-09-28, matching the app fee without saying it is one, so treat it as an undefined benchmark, not a quote. The coverage that reads like indemnity is unquantified the same way: the only insurer Figment names, Nexus Mutual, is an opt-in purchase limited to Ethereum double-sign; the "multi-tiered coverage, including insurance and Figment's balance sheet" on the solutions pages carries no limit and no basis; and the one thing Figment says it "contractually commit[s]" to is slashing ALERTING, not reimbursement. Before committing, make the contract state (a) your actual commission and its base per network, and (b) the coverage limit in figures and who underwrites it — because on the public record neither exists.
BLBlockdaemon
Blockdaemon leads Figment on no published criterion
Choose it only if something outside the published criteria decides for you — your country, a funding rail, or custody.
BlockdaemonScore 60Bank-facing non-custodial validator operator (70+ protocols per its homepage counter, though /validators says "50+ protocols"; ISO 27001 / SOC 2 Type II claimed; $110B+ assets secured platform-wide but only "$6+ billion" in staking infrastructure) whose staking pitch rests on a "100% slashing insurance guarantee" that names no underwriter, no limit and no policy anywhere on its own domain — while publishing tiered self-serve per-compute-unit pricing for its API product and no staking commission at all.Strength: Unbonding disclosure — 5/10Watch-out: Read the guarantee's scope before you read its size, and note that Blockdaemon's own pages disagree about it. The headline is an absolute — "backed by 100% slashing insurance guarantee" (/staking) — but the three pages that say anything about what the policy responds to do not agree: /validators scopes it to rewards ("Customers are 100% guaranteed under our slashing insurance policy against rewards missed due to downtime and slashing risks"), while the blog's disclaimer points at principal ("Covers affected staked balances. Additional terms and conditions apply. Inquire here for more information.") and /trust-center says only "Our slashing protection, backed by leading risk advisors and insurers, safeguards clients against potential losses." Not one names a carrier. The single insurance party identified on the entire domain is Marsh, which Blockdaemon itself calls "the world's leading insurance broker and risk advisor" — a broker, not the underwriter that pays; a domain-wide search for Chainproof, Munich Re, Lloyd's, Nexus Mutual, 'underwriter', 'carrier', 'aggregate limit', 'policy limit' and 'certificate of insurance' returns nothing. So settle this in writing before committing: who is the risk carrier, what is the per-incident and aggregate limit, and does cover attach to slashed principal or only to foregone rewards. Second-order: do not read the homepage's "$110B+ Assets Secured" as staked AUM — the staking pages size that business at "$6+ billion worth of staking infrastructure", an 18x difference, because the $110B is the whole platform including custody. Third: the protocol count is inconsistent on Blockdaemon's own site — the homepage counter says 70+ Protocols while /validators says "Supports 50+ protocols" and /protocols links 61 pages.
Criterion by criterion
Scorecard
Published criteria · weight in points of 868 of 8 cells scored. Strength is read from the evidence file; the weight is the published one. Methodology
Slashing cover
by 3 of 10weight 8.2 of 86Figment leads
Figment5/10 out of 10
Blockdaemon2/10 out of 10
Lock-up disclosure
by 1 of 10weight 5.3 of 86Figment leads
Figment6/10 out of 10
Blockdaemon5/10 out of 10
Rate transparency
by 3 of 10weight 5.8 of 86Figment leads
Figment6/10 out of 10
Blockdaemon3/10 out of 10
Voting from custody
weight 4.8 of 86Tie
Figment5/10 out of 10
Blockdaemon5/10 out of 10
Score dimensions
weights sum to 86
The published score is five dimensions, each weighted for the category. "Published criteria" is the criteria block above; the other four are the engine's own terms — availability, friction, trust record, measured data. Each bar is one side's points out of that dimension's maximum; the weight beside the name is its points of the 86-point weighted total. The published criteria above can fill 24 of the block’s 30. A weight marked “constant here” belongs to a dimension every ranked product in the category holds at the same value: it still counts in the total, and it orders nothing here.
Availabilityweight 20 of 86 · constant here
Figment14/20Blockdaemon14/20
Tie
Published criteriaweight 30 of 86
Figment13.1/30Blockdaemon8.4/30
Figment leads
Frictionweight 10 of 86 · constant here
Figment2.7/10Blockdaemon2.7/10
Tie
Trust recordweight 8 of 86 · constant here
Figment3.2/8Blockdaemon3.2/8
Tie
Measured dataweight 18 of 86 · constant here
Figment8.3/18Blockdaemon8.3/18
Tie
Decision rulePublished order
Choose Figment unless the term Blockdaemon leads on is the one you are buying.
Blockdaemon leads Figment on no published criterion and no score dimension — pick it only if a fact outside the score (country, funding rail, custody) decides for you.
The published order weighs every criterion the same way for everyone. To weigh them your way, run .
From the published order
Next best action
If this isn't your case
Other matchups worth comparing
How you can lose money here, and what the ranking scores
Control failure: a key or vote changes the rules, freezes or mints.
Scored by Do you keep custody and still get to vote — and who presses the button? · 20% (Figment 5/10, Blockdaemon 5/10)
Insolvency failure: the firm or issuer that owes you cannot pay.
Scored by If a validator you delegated to gets slashed, who actually writes the cheque? · 34% (Figment 5/10, Blockdaemon 2/10)
Exit failure: you cannot get out at par, on time, or with what is yours.
Scored by How long are the assets locked per network, and did they tell you before you signed? · 22% (Figment 6/10, Blockdaemon 5/10)
Not assessed by this ranking: Liveness failure, Custody failure, Regulatory failure, Execution failure, Information failure. A high place says nothing about these; the Methodology tab says what each means.
Also scored, as cost, quality or a summary of several families: Can you find the rate you would actually pay without booking a sales call? (24%).
Questions
Frequently asked questions
Figment scores 12 points above Blockdaemon, led by slashing cover, rate transparency, and lock-up disclosure. Published scores, out of 100: Figment 72 (rank 4 of 7 staking), Blockdaemon 60 (rank 7 of 7).
Reviewed means both products compared here was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Answer a few quick questions and get one clear recommendation based on how you actually plan to use crypto — with rationale, tradeoffs, and a path to monitor the decision.
No signup·Free first pass · Private·No spam · No account
Not financial advice · Independent · Always do your own research
Not financial advice · For informational purposes only · Always do your own research