Kiln scores 18 points above Twinstake, led by slashing cover, rate transparency, and lock-up disclosure. Kiln ranks #1 and Twinstake #6 of 7 published staking. Every term of the gap is on the ledger below; the inputs are on the audit receipt.
Kiln79
vs
Twinstake61
Scores are out of 100; published scores fall within 41–99 · ranks #1 and #6 of 7
Kiln scores 18 points above Twinstake, led by slashing cover, rate transparency, and lock-up disclosure.
Kiln #1 of 779
Twinstake #6 of 761
Scores are out of 100; published scores fall within 41–99; a bar is empty at 41 and full at 99.
Why, term by termKiln leads on 4 of 4 published criteria; Twinstake on 0. The terms sum to the gap.
TermKilnTwinstakeWeightPoints
Slashing cover6/102/108.2+8.5for Kiln+4.4 of 32
Rate transparency6/102/105.8+6.0for Kiln+3.1 of 32
Lock-up disclosure8/106/105.3+2.7for Kiln+1.4 of 32
Voting from custody7/106/104.8+1.2for Kiln+0.6 of 32
Net of the terms+18.5
Reproduced gap+18.5
Published gapAfter score rounding and bounds — see the note below7961+18.0
Weight is in points of the 86-point weighted total. Points are score points of the gap between the two.
KilnScore 79The white-label validator operator running under other firms' staking buttons, with 15 named custody-platform integration guides and a per-network lock-up figure published across 26 protocol docs pages (2026-09-28 count) — but a slashing base layer whose size it has never quantified, a commission printed for only two of those 26 networks, and a governance posture stated for two niche products while the Cosmos-family chains where delegated stake actually votes are left silent.Strength: Unbonding disclosure — 8/10Watch-out: Read all three parts of the September 2025 breach disclosure before you sign, and then ask for the base slashing coverage limit in writing. Kiln itself names the victim. (1) https://www.kiln.fi/post/sol-incident-swissborg---announcement, September 8, 2025: "SwissBorg and Kiln are investigating an incident that may have involved unauthorized access to a wallet used for staking operations... The incident resulted in Solana funds being improperly removed from the wallet used for staking operations." (2) https://www.kiln.fi/kiln-responds-tot-infrastructure-issue-with-validator-exit-funds-remain-protected, "PARIS, FRANCE — September 9, 2025": "Kiln today began the orderly exit of all of its Ethereum (ETH) validators", and "The exit process is expected to take between 10 and 30 days depending on the validator" — an operator-side security event that put every ETH client's principal into a multi-week forced exit, which no unbonding table warns you about. (3) The post-mortem at https://www.kiln.fi/post/re-enablement-of-kiln-services-and-security-incident-information, October 7, 2025: a threat actor compromised "a GitHub access token belonging to a Kiln infrastructure engineer", harvested cloud credentials via CI workflows, and "modified the Kiln Connect API backend controller to return a malicious transaction, which one Kiln enterprise customer signed in their custody solution, causing a loss of funds." The malicious transaction "changed the withdrawal authority of the Solana stakes, only if the existing withdrawal authority of the stake account provided in the POST call held stake balances above 150k SOL" — targeted at the largest clients, and the customer's own quorum approved it inside their custody instance. NOTE THE DIVERGENT ATTRIBUTION, which is the single most useful thing here: Kiln places the mitigation duty on the client — "Kiln has consistently recommended that customers decode transactions to verify their integrity before signing", and "Signing and broadcasting a transaction without decoding may result in a loss of authority over stake accounts, as occurred in this case" — while SwissBorg's own primary statement (https://swissborg.com/blog/swissborg-security-update-kiln-breach) puts it on Kiln: "the tampering of the transaction happened within Kiln's infrastructure", and states "no breach occurred within SwissBorg's infrastructure", quantifying the loss at "over 192,000 SOL". The lesson for this category is precise: non-custody protected the keys but not the client, because the attack came through the transaction the operator constructed, and it was not a slashing event — so the Chainproof base layer, whose size Kiln has never published, would not obviously have answered it. Ask for the base coverage limit, what perils it covers beyond slashing, and whether the operator or the client bears an API-origin malicious-transaction loss. Get it in the contract; Kiln's own institutional docs tell you to, saying "For more details and Kiln's coverage please read our T&Cs or the Order Form you have signed with Kiln."TwinstakeScore 61Cayman-registered, Nethermind- and Webn-backed non-custodial validator operator built exclusively for professional investors (its own briefing notes state "Twinstake does not provide staking services to retail customers"), with a genuinely useful ungated per-protocol lock-up corpus and a shipped Ethereum exit-queue product — but with no fee published anywhere, no assets-under-stake figure, a lock-up corpus that lives only in PDFs whose own landing pages are empty stubs, and a loss-allocation claim that consists of the two words "slashing insurance" repeated across twelve pages without an insurer, a limit or a policy.Strength: Unbonding disclosure — 6/10Watch-out: Two of the three numbers an allocator underwrites are not public, so the term sheet has to carry them. Before committing, get in writing (a) the slashing instrument itself — carrier, aggregate and per-event limit, trigger (correlated vs single-validator, principal vs rewards), named beneficiary, and whether it survives a Twinstake insolvency — because the site's only statement is "external slashing insurance", repeated verbatim on twelve pages with no insurer and no limit, the one page that elaborates does so with an unquantified absolute ("assets are protected from validator penalties"), and the page that comes closest to a risk page, /about-us/compliance, is entirely KYC/AML/OFAC and never mentions insurance at all; and (b) the commission — rate, base, per-network variation and change clause — because there is no published figure of any kind, the 92-endpoint API you will integrate against contains zero occurrences of "fee" or "commission", and the only pricing-adjacent language on the domain is "Flexible commercial terms" in a client case study. Add a third line item: MEV. /insights/twinstake-approach-to-maximal-extractable-value-mev-on-ethereum describes relay strategy in detail and even notes that Twinstake "offers the ability to connect to paid-for relayer services", but never states who keeps execution-layer and MEV revenue or at what split — an unpriced MEV split plus a paid relay option is a second and third undisclosed cost vector. Finally, currency-check the good news: the per-protocol unbonding figures you can verify pre-signature sit in PDF briefing notes bulk-dated November 27, 2025 whose landing pages are empty stubs, the PDFs print no date on their face, and the Ethereum note still carries a pre-Pectra "entry churn rate is fixed at 8 validators per epoch" beside a post-Pectra 2048 ETH maximum — so model exit timing from live queue data (Twinstake's own note points to validatorqueue.com) rather than from the constants on the page. Do not plan on the Activation & Exit Calculator during diligence: it is available only inside the Twinstake Portal and through the authenticated API, to institutions already staking with Twinstake.
Quick facts
At a glance
2 of 3 rows read the same for both.
FactKilnTwinstake
PricingSnapshotKiln validator docs page "Solana (SOL)" (https://docs.kiln.fi/v1/kiln-products/validators/protocols/solana-sol, fetched 28 September 2026), Mainnet table with columns Name | Commission | MEV commission | Address: Kiln1 — "5%" commission, "100% (offchain rebates & compounding)" MEV commission, vote account DdCNGDpP7qMgoAy6paFzhhak2EeyCZcgjH7ak5u5v28m; Kiln2 — "7%" commission, "7%" MEV commission, vote account HCvnhbT3Sn5RsueDisWzzn5FkW8tAqoQK1dr7cvAVzin. The same page adds: "Each validator commission rate is public and the same for all funds on a given validator. The validator takes its commission automatically when rewards are generated. Your staking rewards are distributed net of the validator commission." These are Solana validator rates only. Of the 26 validator protocol pages Kiln documents, only this page and the NEAR page print a commission figure, https://www.kiln.fi/pricing returns 404, and no institutional contract rate is published.Twinstake's contact page (https://www.twinstake.com/contact, fetched 28 September 2026) lists under "Sales": "Contact our sales team to discuss pricing or request a demo". No fee, rate card, commission or percentage price appears on any of the 153 pages in https://www.twinstake.com/sitemap.xml (all fetched 28 September 2026, all HTTP 200), so there is no list price to compare; the rate is set in a sales conversation.
Asset coverageEditorial——
Region fitSnapshotglobalglobal
From the published criteria
Which should you pick?
Kiln
79#1 of 7
Leads
Pick it when
Pick Kiln if slashing cover matters most — it scores 6/10 to Twinstake's 2/10 there (weight 34).
Strength
Unbonding disclosure — 8/10
Tradeoff
Read all three parts of the September 2025 breach disclosure before you sign, and then ask for the base slashing coverage limit in writing. Kiln itself names the victim. (1) https://www.kiln.fi/post/sol-incident-swissborg---announcement, September 8, 2025: "SwissBorg and Kiln are investigating an incident that may have involved unauthorized access to a wallet used for staking operations... The incident resulted in Solana funds being improperly removed from the wallet used for staking operations." (2) https://www.kiln.fi/kiln-responds-tot-infrastructure-issue-with-validator-exit-funds-remain-protected, "PARIS, FRANCE — September 9, 2025": "Kiln today began the orderly exit of all of its Ethereum (ETH) validators", and "The exit process is expected to take between 10 and 30 days depending on the validator" — an operator-side security event that put every ETH client's principal into a multi-week forced exit, which no unbonding table warns you about. (3) The post-mortem at https://www.kiln.fi/post/re-enablement-of-kiln-services-and-security-incident-information, October 7, 2025: a threat actor compromised "a GitHub access token belonging to a Kiln infrastructure engineer", harvested cloud credentials via CI workflows, and "modified the Kiln Connect API backend controller to return a malicious transaction, which one Kiln enterprise customer signed in their custody solution, causing a loss of funds." The malicious transaction "changed the withdrawal authority of the Solana stakes, only if the existing withdrawal authority of the stake account provided in the POST call held stake balances above 150k SOL" — targeted at the largest clients, and the customer's own quorum approved it inside their custody instance. NOTE THE DIVERGENT ATTRIBUTION, which is the single most useful thing here: Kiln places the mitigation duty on the client — "Kiln has consistently recommended that customers decode transactions to verify their integrity before signing", and "Signing and broadcasting a transaction without decoding may result in a loss of authority over stake accounts, as occurred in this case" — while SwissBorg's own primary statement (https://swissborg.com/blog/swissborg-security-update-kiln-breach) puts it on Kiln: "the tampering of the transaction happened within Kiln's infrastructure", and states "no breach occurred within SwissBorg's infrastructure", quantifying the loss at "over 192,000 SOL". The lesson for this category is precise: non-custody protected the keys but not the client, because the attack came through the transaction the operator constructed, and it was not a slashing event — so the Chainproof base layer, whose size Kiln has never published, would not obviously have answered it. Ask for the base coverage limit, what perils it covers beyond slashing, and whether the operator or the client bears an API-origin malicious-transaction loss. Get it in the contract; Kiln's own institutional docs tell you to, saying "For more details and Kiln's coverage please read our T&Cs or the Order Form you have signed with Kiln."
Twinstake
61#6 of 7
Pick it when
Twinstake leads Kiln 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 — 6/10
Tradeoff
Two of the three numbers an allocator underwrites are not public, so the term sheet has to carry them. Before committing, get in writing (a) the slashing instrument itself — carrier, aggregate and per-event limit, trigger (correlated vs single-validator, principal vs rewards), named beneficiary, and whether it survives a Twinstake insolvency — because the site's only statement is "external slashing insurance", repeated verbatim on twelve pages with no insurer and no limit, the one page that elaborates does so with an unquantified absolute ("assets are protected from validator penalties"), and the page that comes closest to a risk page, /about-us/compliance, is entirely KYC/AML/OFAC and never mentions insurance at all; and (b) the commission — rate, base, per-network variation and change clause — because there is no published figure of any kind, the 92-endpoint API you will integrate against contains zero occurrences of "fee" or "commission", and the only pricing-adjacent language on the domain is "Flexible commercial terms" in a client case study. Add a third line item: MEV. /insights/twinstake-approach-to-maximal-extractable-value-mev-on-ethereum describes relay strategy in detail and even notes that Twinstake "offers the ability to connect to paid-for relayer services", but never states who keeps execution-layer and MEV revenue or at what split — an unpriced MEV split plus a paid relay option is a second and third undisclosed cost vector. Finally, currency-check the good news: the per-protocol unbonding figures you can verify pre-signature sit in PDF briefing notes bulk-dated November 27, 2025 whose landing pages are empty stubs, the PDFs print no date on their face, and the Ethereum note still carries a pre-Pectra "entry churn rate is fixed at 8 validators per epoch" beside a post-Pectra 2048 ETH maximum — so model exit timing from live queue data (Twinstake's own note points to validatorqueue.com) rather than from the constants on the page. Do not plan on the Activation & Exit Calculator during diligence: it is available only inside the Twinstake Portal and through the authenticated API, to institutions already staking with Twinstake.
Self-identify in 10 seconds
Which one is actually for you?
KilnLeads
Choose Kiln if slashing cover matters most
Slashing cover: 6/10 against 2/10 for Twinstake (weight 34)
Rate transparency: 6/10 against 2/10 for Twinstake (weight 24)
Lock-up disclosure: 8/10 against 6/10 for Twinstake (weight 22)
KilnScore 79The white-label validator operator running under other firms' staking buttons, with 15 named custody-platform integration guides and a per-network lock-up figure published across 26 protocol docs pages (2026-09-28 count) — but a slashing base layer whose size it has never quantified, a commission printed for only two of those 26 networks, and a governance posture stated for two niche products while the Cosmos-family chains where delegated stake actually votes are left silent.Strength: Unbonding disclosure — 8/10Watch-out: Read all three parts of the September 2025 breach disclosure before you sign, and then ask for the base slashing coverage limit in writing. Kiln itself names the victim. (1) https://www.kiln.fi/post/sol-incident-swissborg---announcement, September 8, 2025: "SwissBorg and Kiln are investigating an incident that may have involved unauthorized access to a wallet used for staking operations... The incident resulted in Solana funds being improperly removed from the wallet used for staking operations." (2) https://www.kiln.fi/kiln-responds-tot-infrastructure-issue-with-validator-exit-funds-remain-protected, "PARIS, FRANCE — September 9, 2025": "Kiln today began the orderly exit of all of its Ethereum (ETH) validators", and "The exit process is expected to take between 10 and 30 days depending on the validator" — an operator-side security event that put every ETH client's principal into a multi-week forced exit, which no unbonding table warns you about. (3) The post-mortem at https://www.kiln.fi/post/re-enablement-of-kiln-services-and-security-incident-information, October 7, 2025: a threat actor compromised "a GitHub access token belonging to a Kiln infrastructure engineer", harvested cloud credentials via CI workflows, and "modified the Kiln Connect API backend controller to return a malicious transaction, which one Kiln enterprise customer signed in their custody solution, causing a loss of funds." The malicious transaction "changed the withdrawal authority of the Solana stakes, only if the existing withdrawal authority of the stake account provided in the POST call held stake balances above 150k SOL" — targeted at the largest clients, and the customer's own quorum approved it inside their custody instance. NOTE THE DIVERGENT ATTRIBUTION, which is the single most useful thing here: Kiln places the mitigation duty on the client — "Kiln has consistently recommended that customers decode transactions to verify their integrity before signing", and "Signing and broadcasting a transaction without decoding may result in a loss of authority over stake accounts, as occurred in this case" — while SwissBorg's own primary statement (https://swissborg.com/blog/swissborg-security-update-kiln-breach) puts it on Kiln: "the tampering of the transaction happened within Kiln's infrastructure", and states "no breach occurred within SwissBorg's infrastructure", quantifying the loss at "over 192,000 SOL". The lesson for this category is precise: non-custody protected the keys but not the client, because the attack came through the transaction the operator constructed, and it was not a slashing event — so the Chainproof base layer, whose size Kiln has never published, would not obviously have answered it. Ask for the base coverage limit, what perils it covers beyond slashing, and whether the operator or the client bears an API-origin malicious-transaction loss. Get it in the contract; Kiln's own institutional docs tell you to, saying "For more details and Kiln's coverage please read our T&Cs or the Order Form you have signed with Kiln."
Twinstake
Twinstake leads Kiln on no published criterion
Choose it only if something outside the published criteria decides for you — your country, a funding rail, or custody.
TwinstakeScore 61Cayman-registered, Nethermind- and Webn-backed non-custodial validator operator built exclusively for professional investors (its own briefing notes state "Twinstake does not provide staking services to retail customers"), with a genuinely useful ungated per-protocol lock-up corpus and a shipped Ethereum exit-queue product — but with no fee published anywhere, no assets-under-stake figure, a lock-up corpus that lives only in PDFs whose own landing pages are empty stubs, and a loss-allocation claim that consists of the two words "slashing insurance" repeated across twelve pages without an insurer, a limit or a policy.Strength: Unbonding disclosure — 6/10Watch-out: Two of the three numbers an allocator underwrites are not public, so the term sheet has to carry them. Before committing, get in writing (a) the slashing instrument itself — carrier, aggregate and per-event limit, trigger (correlated vs single-validator, principal vs rewards), named beneficiary, and whether it survives a Twinstake insolvency — because the site's only statement is "external slashing insurance", repeated verbatim on twelve pages with no insurer and no limit, the one page that elaborates does so with an unquantified absolute ("assets are protected from validator penalties"), and the page that comes closest to a risk page, /about-us/compliance, is entirely KYC/AML/OFAC and never mentions insurance at all; and (b) the commission — rate, base, per-network variation and change clause — because there is no published figure of any kind, the 92-endpoint API you will integrate against contains zero occurrences of "fee" or "commission", and the only pricing-adjacent language on the domain is "Flexible commercial terms" in a client case study. Add a third line item: MEV. /insights/twinstake-approach-to-maximal-extractable-value-mev-on-ethereum describes relay strategy in detail and even notes that Twinstake "offers the ability to connect to paid-for relayer services", but never states who keeps execution-layer and MEV revenue or at what split — an unpriced MEV split plus a paid relay option is a second and third undisclosed cost vector. Finally, currency-check the good news: the per-protocol unbonding figures you can verify pre-signature sit in PDF briefing notes bulk-dated November 27, 2025 whose landing pages are empty stubs, the PDFs print no date on their face, and the Ethereum note still carries a pre-Pectra "entry churn rate is fixed at 8 validators per epoch" beside a post-Pectra 2048 ETH maximum — so model exit timing from live queue data (Twinstake's own note points to validatorqueue.com) rather than from the constants on the page. Do not plan on the Activation & Exit Calculator during diligence: it is available only inside the Twinstake Portal and through the authenticated API, to institutions already staking with Twinstake.
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 4 of 10weight 8.2 of 86Kiln leads
Kiln6/10 out of 10
Twinstake2/10 out of 10
Lock-up disclosure
by 2 of 10weight 5.3 of 86Kiln leads
Kiln8/10 out of 10
Twinstake6/10 out of 10
Rate transparency
by 4 of 10weight 5.8 of 86Kiln leads
Kiln6/10 out of 10
Twinstake2/10 out of 10
Voting from custody
by 1 of 10weight 4.8 of 86Kiln leads
Kiln7/10 out of 10
Twinstake6/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
Kiln14/20Twinstake14/20
Tie
Published criteriaweight 30 of 86
Kiln15.9/30Twinstake8.8/30
Kiln leads
Frictionweight 10 of 86 · constant here
Kiln2.7/10Twinstake2.7/10
Tie
Trust recordweight 8 of 86 · constant here
Kiln3.2/8Twinstake3.2/8
Tie
Measured dataweight 18 of 86 · constant here
Kiln8.3/18Twinstake8.3/18
Tie
Decision rulePublished order
Choose Kiln unless the term Twinstake leads on is the one you are buying.
Twinstake leads Kiln 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% (Kiln 7/10, Twinstake 6/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% (Kiln 6/10, Twinstake 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% (Kiln 8/10, Twinstake 6/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
Kiln scores 18 points above Twinstake, led by slashing cover, rate transparency, and lock-up disclosure. Published scores, out of 100: Kiln 79 (rank 1 of 7 staking), Twinstake 61 (rank 6 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
Kiln #1 of 779
Twinstake #6 of 761