Vendor-funded research
Top 10 Best Eth Treasury Services of 2026

GITNUXSOFTWARE ADVICE

Business Finance

Top 10 Best Eth Treasury Services of 2026

Top 10 ranked eth treasury services for Ethereum teams. Includes Stakefish, Blockdaemon, and Kiln with criteria and tradeoffs.

28 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

An editor sets the topic, the inclusion criteria, and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

ETH treasury teams need governed custody, validator operations, and reporting that match internal controls such as RBAC, audit logs, and settlement workflows. This ranked comparison of the top ETH treasury services helps evidence-minded buyers evaluate tradeoffs between institutional-grade custody depth, staking administration automation, and integration paths such as APIs and data schemas.

Stakefish is the best fit for treasuries that need liquid ETH staking exposure with strong on-chain reconciliation, whereas Blockdaemon works better when you want automated, API-driven signing tied to operational runs and reporting, and if governance is your priority, Kiln and Figment are the clearer alternatives.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Stakefish

Liquid staking receipts convert staking exposure into ERC-20 balance tracking without manual validator operations.

Best for: Fits when treasuries need liquid ETH staking exposure with strong on-chain reconciliation.

2

Blockdaemon

Editor pick

Provisioning and orchestration of wallet and signing workflows through an API-oriented operational model.

Best for: Fits when ETH treasuries need automated, API-driven signing workflows tied to operational runs and reporting.

3

Kiln

Editor pick

Governed transaction approval workflows that enforce treasury intent boundaries before execution.

Best for: Fits when governance-led teams need controlled ETH reserve execution with audit-friendly workflows.

Comparison Table

1
StakefishBest overall
specialist
9.2/10
Overall
2
enterprise_vendor
8.8/10
Overall
3
specialist
8.6/10
Overall
4
enterprise_vendor
8.3/10
Overall
5
enterprise_vendor
8.0/10
Overall
6
specialist
7.7/10
Overall
7
enterprise_vendor
7.4/10
Overall
8
enterprise_vendor
7.1/10
Overall
9
enterprise_vendor
6.8/10
Overall
10
enterprise_vendor
6.4/10
Overall
#1

Stakefish

specialist

Stakefish provides professional Ethereum validator and staking services.

9.2/10
Overall
Features9.1/10
Ease of Use9.4/10
Value9.0/10
Standout feature

Liquid staking receipts convert staking exposure into ERC-20 balance tracking without manual validator operations.

Stakefish handles the operational side of staking by maintaining validator participation and reward accrual, while the treasury can interact at the level of staking deposits and received staking tokens. That separation helps teams treat staking exposure as an auditable on-chain position rather than an internal validator runbook. The integration surface is practical for treasuries that already track on-chain receipts and want automated settlement into token balances.

A tradeoff is that governance and key controls stay outside treasury RBAC, so internal approval workflows must be implemented around contract calls rather than validator signing. Stakefish fits situations where a treasury needs liquid ETH staking exposure for ongoing budgeting and collateral use, and where validator-level tuning is not a requirement.

Pros
  • +Liquid staking token model supports ongoing treasury liquidity planning
  • +On-chain receipts make staking exposure easy to reconcile with balances
  • +Validator operations are abstracted behind a deposit and receipt flow
  • +Good fit for treasuries that route staking into downstream DeFi usage
Cons
  • –Validator and key-level governance remain external to treasury controls
  • –Custom withdrawal and liquidity timing depends on the provider staking mechanics
  • –Policy enforcement must be implemented at the contract interaction layer
  • –Treasury reporting needs careful mapping from receipts to underlying ETH
Use scenarios
  • Treasury operations teams

    Maintain liquid ETH staking exposure

    Faster monthly balance closing

  • DeFi treasury managers

    Use staked ETH as collateral

    Higher capital efficiency

Show 2 more scenarios
  • Risk and compliance leads

    Audit staking position via on-chain data

    Clearer audit trails

    The on-chain staking position supports evidence-based reporting tied to token holdings and transfers.

  • Protocol funds teams

    Ongoing staking allocation management

    Lower operational overhead

    Recurring allocations stay operationally simple by using the staking contract flow for new deposits.

Best for: Fits when treasuries need liquid ETH staking exposure with strong on-chain reconciliation.

#2

Blockdaemon

enterprise_vendor

Blockdaemon provides institutional staking, validator operations, and digital asset infrastructure services.

8.8/10
Overall
Features8.7/10
Ease of Use9.0/10
Value8.9/10
Standout feature

Provisioning and orchestration of wallet and signing workflows through an API-oriented operational model.

Blockdaemon is commonly chosen when ETH treasury teams need repeatable operational runs, not one-off key handling. Its control surface centers on wallet and signing workflow orchestration, plus programmatic transaction execution paths designed for treasury policy decisions. The most relevant fit signal is how quickly signing and transaction automation can be connected to downstream processes like reporting and reconciliation. Teams can also stage changes in controlled environments to reduce operational risk during policy updates.

A practical tradeoff is governance alignment. Teams that require highly custom approval logic across multiple spending streams may need more engineering to map treasury policy to Blockdaemon’s workflow primitives. A good usage situation is a treasury that automates routine ETH transfers and validator-related actions while enforcing a consistent approval workflow across environments.

Pros
  • +API-first workflow orchestration for treasury transactions and signing
  • +Environment support that helps stage workflow changes safely
  • +Operational automation that reduces manual key handling steps
  • +Clear integration path for reconciliation and on-chain reporting loops
Cons
  • –Custom approval logic may require extra engineering work
  • –Workflow mapping effort increases for multi-stream treasury policies
  • –Operational maturity matters to avoid workflow drift during changes
Use scenarios
  • Treasury operations teams

    Automate ETH transfers with policy approvals

    Fewer manual steps, faster releases

  • Security engineering teams

    Enforce controlled signing across environments

    Lower change-related operational risk

Show 2 more scenarios
  • Protocol treasury ops

    Coordinate ETH allocations with validator actions

    More consistent treasury execution

    Run validator-adjacent operational flows under a consistent transaction approval process.

  • Compliance and finance teams

    Reconcile on-chain activity to policy

    More audit-ready operational records

    Automate integration paths that support reconciliation loops after policy-driven transactions.

Best for: Fits when ETH treasuries need automated, API-driven signing workflows tied to operational runs and reporting.

#3

Kiln

specialist

Kiln provides enterprise Ethereum staking and validator management services.

8.6/10
Overall
Features8.5/10
Ease of Use8.7/10
Value8.5/10
Standout feature

Governed transaction approval workflows that enforce treasury intent boundaries before execution.

Kiln is positioned for organizations that treat ETH reserves as an operational program with defined rules for how actions get proposed, approved, and executed. It fits treasury teams that need governance gates before transfers, along with operational reporting that helps reconcile wallet activity against internal intents. Automation and API surface are used to reduce manual steps during routine treasury operations, especially around recurring movements and operational monitoring.

A tradeoff appears in workflow fit. Kiln is best aligned when the treasury team wants a governed execution model with clear approval steps, and it can feel heavier when the priority is fully self-directed self-custody with minimal process overhead. The most effective usage situation is an operations-led treasury that runs frequent reserve adjustments but must keep execution auditable and policy-bound.

Pros
  • +Policy-bound approval workflows for governed ETH reserve execution
  • +Automation that reduces manual operations during recurring treasury actions
  • +Operational reporting and reconciliation oriented around wallet activity
  • +Integration options that support reliable signing and execution steps
Cons
  • –Workflow-driven model can add overhead for ad-hoc treasury moves
  • –Operational tuning requires governance discipline and clear rule ownership
  • –Complex edge cases may need specialist support to implement safely
Use scenarios
  • Treasury operations teams

    Monthly reserve rebalancing under approvals

    Fewer manual steps, consistent approvals

  • Security and governance teams

    Restricted signing for treasury transfers

    Reduced policy bypass risk

Show 1 more scenario
  • Finance ops and reporting

    Wallet reconciliation to internal intents

    Faster discrepancy detection

    Provides operational visibility that helps match executed on-chain activity to treasury objectives.

Best for: Fits when governance-led teams need controlled ETH reserve execution with audit-friendly workflows.

#4

Anchorage Digital

enterprise_vendor

Anchorage Digital provides institutional crypto custody, staking, and trading services for ETH reserves.

8.3/10
Overall
Features8.6/10
Ease of Use8.1/10
Value8.0/10
Standout feature

Policy-based signing and approval orchestration that keeps operational audit evidence tied to custody-controlled keys.

Anchorage Digital focuses on custody and on-chain treasury operations for institutional ETH holdings, with an emphasis on policy-driven controls around access and approvals. Its core capabilities center on managed custody workflows, transaction signing orchestration, and operational reporting that supports wallet reconciliation.

Pros
  • +Governed custody workflows support controlled signing and approval paths.
  • +Operational reporting supports wallet reconciliation across ETH holdings and activity.
  • +Enterprise-grade integration supports onboarding of treasury operations into existing systems.
  • +API and automation surface supports recurring treasury execution and monitoring.
Cons
  • –Multi-party approval configurations require careful coordination across stakeholders.
  • –Advanced custody workflows can add operational overhead for smaller treasury teams.
  • –Validator operations and staking workflow depth may lag specialist staking providers.
  • –Operational tooling may require more internal process design than pure custody vendors.

Best for: Fits when regulated treasury teams need managed ETH custody plus governed execution workflows.

#5

Deloitte

enterprise_vendor

Deloitte provides digital asset strategy, risk, accounting, tax, and treasury advisory services.

8.0/10
Overall
Features7.6/10
Ease of Use8.2/10
Value8.2/10
Standout feature

Control design that maps treasury policy approvals into enforced signing and operational workflows across stakeholders.

Deloitte provides eth treasury services that translate governance and control requirements into custody, signing, and operational workflows. Delivery typically centers on policy design, multi-stakeholder operating procedures, and documentation that supports audit-oriented operations around ETH assets.

Pros
  • +Governance-first operating procedures for ETH custody and signing workflows
  • +Clear control mapping from treasury policy into approval steps and roles
  • +Structured documentation for key ceremonies, rotations, and operational runbooks
  • +Program delivery experience across multi-party stakeholders and reporting needs
Cons
  • –Consulting-led delivery can slow iteration on high-frequency on-chain treasury changes
  • –Automation depth depends on how systems integrate with the engagement scope
  • –Produces more artifacts than turnkey on-chain execution tooling
  • –Requires strong internal owners to keep workflows current and enforceable

Best for: Fits when governance-heavy ETH reserve strategy work needs implementation discipline and control documentation.

#6

Figment

specialist

Figment provides institutional Ethereum staking, validator operations, and staking administration.

7.7/10
Overall
Features7.8/10
Ease of Use7.6/10
Value7.5/10
Standout feature

Managed validator operations tied to staking allocation governance workflows and ongoing operational reporting for treasury oversight.

Figment is an ETH treasury service provider that focuses on validator operations and operational support around ETH positions, rather than acting as a full custody suite. It is distinct for teams that need hands-on execution for staking lifecycle steps, including validator management, monitoring, and change coordination.

Pros
  • +Strong validator operations support for staking allocation and lifecycle changes
  • +Operational monitoring and reporting that fit ongoing treasury oversight
  • +Clear coordination model for approvals and change management
  • +Execution experience across real staking conditions and operational edge cases
Cons
  • –Less suited for teams needing end-to-end custody and signing tooling
  • –Onboarding depends heavily on aligning treasury policy with execution workflows
  • –API surface may not match specialized treasury integrations used by banks
  • –Limited fit for large multi-wallet signing orchestration without external tooling

Best for: Fits when governance teams want delegated validator execution and operational reporting for ETH reserves.

#7

Komainu

enterprise_vendor

Komainu provides regulated digital asset custody, collateral management, and staking services.

7.4/10
Overall
Features7.6/10
Ease of Use7.1/10
Value7.3/10
Standout feature

Custody-first governance for transaction authorization workflows that ties operational handling to treasury approval steps.

Komainu focuses on institutional crypto custody and treasury workflows for ETH reserve strategy, with operational controls designed around qualified custody and segregated account handling. Its core capabilities center on secure custody operations plus governance for transaction authorization flows, which matters when custody and treasury execution must be auditable end to end.

Pros
  • +Institutional custody posture with operational controls aligned to custody governance needs
  • +Clear separation of custody operations and treasury execution workflows
  • +Transaction approval coordination fits treasury processes that require explicit authorization steps
  • +Operational reporting support supports wallet reconciliation workflows
Cons
  • –Treasury policy automation is less developer-native than API-first treasury systems
  • –On-chain validator operations and staking orchestration are not a universal fit
  • –Wallet-level customization depends on operational configuration and custody process scope
  • –Higher process overhead for teams that need frequent, low-latency signing

Best for: Fits when institutional teams need managed ETH custody controls plus audited execution coordination for treasury workflows.

#8

Hex Trust

enterprise_vendor

Hex Trust provides institutional digital asset custody, staking, and administration services.

7.1/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.3/10
Standout feature

Transaction approval workflow built around governed key setups that separate operational custody from signing authority.

Hex Trust is a crypto treasury and custody provider focused on operational control for institutional ETH reserve management. It supports custody workflows that route signing through governed key setups, including multisignature or contract wallet patterns for transaction approvals.

Pros
  • +Governed custody workflows for controlled ETH transaction approvals
  • +Operational reporting geared for treasury reconciliation and governance checks
  • +Automation-friendly integration surface for treasury orchestration
  • +Key setup options aligned with multi-approver signing requirements
Cons
  • –Operational success depends on disciplined policy and signer governance
  • –Validator operations require additional design effort for allocations
  • –On-chain reporting depth can be limited by chosen integration paths
  • –Wallet and policy configuration complexity can slow early rollout

Best for: Fits when treasury teams need governed custody controls and integration for recurring ETH reserve operations.

#9

Ceffu

enterprise_vendor

Ceffu provides institutional digital asset custody, settlement, and staking services.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.7/10
Standout feature

Configured transaction approval and signing workflow around multisignature custody operations rather than custody only.

Ceffu operates as an ETH treasury custody and operations service focused on institutional key management workflows. It supports configuration of custody controls around multisignature wallet operations and managed transaction signing processes.

Pros
  • +Managed multisignature signing workflow reduces operator error risk
  • +Custody configuration centered on transaction approval controls and quorum
  • +Reconciliation-oriented operational reporting supports treasury operations
  • +Works well for recurring ETH movements with consistent governance
Cons
  • –Less suited for custom on-chain tooling that needs deep API coverage
  • –Approval workflow changes require governance discipline and clear ownership
  • –Limited visibility into low-level signing internals compared with bespoke setups
  • –Validator and staking operations are not its primary execution focus

Best for: Fits when treasury teams need governed ETH custody operations with repeatable signing workflows.

#10

Fidelity Digital Assets

enterprise_vendor

Fidelity Digital Assets provides institutional digital asset custody and trading services.

6.4/10
Overall
Features6.4/10
Ease of Use6.4/10
Value6.5/10
Standout feature

Governance-aligned, custody-managed transaction execution workflows that coordinate approvals with signer responsibilities.

Fidelity Digital Assets is a managed custody and institutional crypto services provider aimed at enterprises that need operational control over ETH holdings for treasury use cases. Its core capabilities center on custody-grade asset holding, transaction execution workflows, and institutional reporting oriented to reconciliation and audit readiness.

Pros
  • +Institutional custody orientation supports controlled ETH asset handling for treasuries
  • +Operational workflows fit governance patterns that require approval before execution
  • +Reconciliation and reporting outputs support monthly treasury close processes
  • +Supports managed execution instead of requiring in-house wallet operator staffing
Cons
  • –API and automation surface is not designed for highly customized treasury workflows
  • –ETH reserve strategy automation such as rules-based rebalancing is limited
  • –Integration can require process alignment with Fidelity custody and execution roles
  • –Sandbox-style developer testing workflows are not a central part of adoption

Best for: Fits when an enterprise needs governance-aligned ETH custody and managed execution with reconciliation support.

Conclusion

After evaluating 10 eth treasury, Stakefish stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Stakefish

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

How to Choose the Right Eth Treasury

Ethereum treasury execution hinges on who can authorize transfers, how signing workflows run, and how on-chain positions reconcile to operational records. This guide frames those control and automation mechanics around Stakefish, Blockdaemon, and Kiln, then contrasts additional providers that support different governance and custody patterns.

The evaluation tracks the operational shape of each ETH treasury service, including workflow provisioning, approval boundaries, and reconciliation through staking exposure or custody-managed activity. Providers included are Stakefish, Blockdaemon, Kiln, Anchorage Digital, Deloitte, Figment, Komainu, Hex Trust, Ceffu, and Fidelity Digital Assets.

ETH Treasury services: custody, signing workflows, and reconciliation for reserve execution

An ETH treasury service coordinates custody-controlled keys, transaction approval workflows, and the operational controls that govern when signed actions can execute. It also covers how ETH reserve exposure shows up in reporting through mechanisms like liquid staking receipts or wallet reconciliation across ETH holdings and activity.

Stakefish focuses on liquid staking receipts that convert staking exposure into ERC-20 balance tracking without manual validator operations, which supports ongoing treasury liquidity planning and reconciliation. Blockdaemon emphasizes API-oriented orchestration that provisions wallet and signing workflows for automated runs tied to operational execution and reporting. Kiln enforces governed transaction approval workflows that apply intent boundaries before execution to keep reserve actions audit-friendly.

ETH Treasury execution control points and automation surfaces

ETH treasury execution succeeds when the signing workflow, approval boundaries, and operational reconciliation line up with how the organization governs transfers. This guide evaluates providers on how they operationalize those control points through provisioning, API orchestration, and the observable outputs that treasury teams reconcile against.

  • Liquid staking position reconciliation model

    Stakefish converts staking exposure into liquid tracking via ERC-20 balance representation using staking receipts, which reduces manual validator alignment work for treasury reporting. This approach is a fit when treasury needs ongoing liquidity planning with reconciled staking exposure.

  • API-first provisioning for wallet and signing workflows

    Blockdaemon emphasizes API-oriented orchestration for wallet and signing workflows that can be tied to operational runs and reporting. This fits teams that want automated execution paths with environment support for staging workflow changes.

  • Governed transaction approval workflows with intent boundaries

    Kiln provides governed transaction approval workflows that enforce intent boundaries before execution, which supports audit-friendly reserve execution. This is a fit when governance-led teams want rule-bound execution instead of ad-hoc signing.

  • Custody-linked governed signing workflows and reconciliation reporting

    Anchorage Digital pairs governed custody workflows with operational reporting that supports wallet reconciliation across ETH holdings and activity. This is a fit for regulated treasury teams that require controlled signing and approval paths tied to custody operations.

  • Control design that maps treasury policy into approval steps

    Deloitte focuses on governance-first operating procedures that map treasury policy approvals into enforced signing and operational workflow steps across stakeholders. This fits governance-heavy reserve strategy work that needs control documentation discipline.

  • Validator operations tied to staking allocation governance

    Figment supports managed validator operations connected to staking allocation governance workflows and ongoing operational monitoring. This is a fit when treasury wants delegated validator execution and reporting aligned to allocation lifecycle changes.

  • Custody-first authorization workflows aligned to execution coordination

    Komainu emphasizes custody-first governance for transaction authorization workflows, which ties operational handling to treasury approval steps. This fits institutional teams that want audited coordination between custody operations and treasury execution workflows.

Choose execution architecture by mapping approvals, automation, and reconciliation

Treasury teams should start by matching the provider’s workflow shape to the authorization model that governs when ETH reserve transactions can execute. The second step should map how staked or custodied positions appear in reconciliation, so operational records can be tied to on-chain outcomes without manual glue work.

  • Pick the execution control philosophy: intent-governed versus automation-orchestrated versus liquid-reconciled

    If governance must enforce intent boundaries before any execution action, Kiln’s governed approval workflows are designed around policy-bound decision steps. If operational runs must trigger signing through an API workflow engine, Blockdaemon’s API-first orchestration is the dominant model.

  • Match reconciliation to how staking exposure must show up in treasury ledgers

    If treasury reconciliation needs staked exposure represented as liquid balances, Stakefish uses liquid staking receipts that convert staking exposure into ERC-20 balance tracking without manual validator operations. If reconciliation depends more on managed validator monitoring and allocation lifecycle reporting, Figment ties validator operations to staking allocation governance and ongoing operational reporting.

  • Decide whether the primary integration point is workflow provisioning or custody-controlled approvals

    Blockdaemon and Anchorage Digital both support governed signing paths, but Blockdaemon centers on API-driven workflow orchestration while Anchorage Digital ties governed custody workflows to operational reporting for wallet reconciliation. Teams that prioritize end-to-end governance-controlled custody workflows should compare anchorage-style reconciliation to Komainu’s custody-first authorization alignment.

  • Size the operational overhead for recurring versus ad-hoc reserve actions

    Kiln’s workflow-driven model reduces manual effort for recurring treasury actions, but it can add overhead when ad-hoc moves require new rule interpretations. Hex Trust and Ceffu both rely on governed approval discipline, so reserve teams should evaluate how often rules change compared with how often operations need to move quickly.

  • Align stakeholder workflows with how approvals are mapped across roles

    Deloitte’s governance-first approach maps treasury policy approvals into enforced signing and operational workflow steps across stakeholders, which suits organizations that want control mapping clarity. For organizations that require deeper developer-native API coverage for highly customized treasury workflows, Ceffu and Fidelity Digital Assets both show limits in automation surface for rules-based rebalancing.

Which ETH Treasury teams benefit from these execution models

Different treasury organizations optimize for different failure modes such as unauthorized transfer risk, reconciliation drift, or operational throughput during recurring reserve actions. The best fit depends on which component of the execution pipeline is the bottleneck, either approval boundaries, signing workflow automation, or position reconciliation visibility.

  • Treasury teams that need ERC-20 style reconciliation of staking exposure

    Stakefish is a strong fit when staking exposure must appear as liquid tracking via receipts to reduce manual validator alignment and support ongoing liquidity planning.

  • Engineering-driven treasuries that automate signing through APIs

    Blockdaemon fits when workflow provisioning and signing orchestration must be programmable through an API-first operational model tied to operational runs and reporting.

  • Governance-led organizations that require intent boundaries before execution

    Kiln suits teams that want governed transaction approval workflows that enforce treasury intent boundaries and keep execution audit-friendly.

  • Regulated treasury organizations that need custody-controlled signing with reconciliation evidence

    Anchorage Digital supports governed custody workflows and operational reporting that supports wallet reconciliation across ETH holdings and activity, which matches regulated approval requirements.

  • Institutional operators that want custody governance aligned to authorization coordination

    Komainu is designed around custody-first governance for transaction authorization workflows with clear separation between custody operations and treasury execution workflows.

Common failure points when implementing ETH Treasury execution

Most implementation failures come from mismatches between approval workflows and the actual operational cadence of reserve actions. Other failures come from reconciliation gaps where on-chain outcomes do not map cleanly to the records treasury teams use for liquidity and governance reporting.

  • Assuming API orchestration covers governance logic without additional workflow engineering

    Blockdaemon supports API-first workflow orchestration, but custom approval logic can require extra engineering work and workflow mapping effort increases for multi-stream treasury policies.

  • Over-optimizing for governed workflows and then treating ad-hoc moves as the same as recurring actions

    Kiln’s workflow-driven model reduces manual operations for recurring treasury actions, but ad-hoc reserve moves can require additional overhead when intent rules must be tuned and ownership must be clear.

  • Building reconciliation around wallet-only balances while staking exposure uses a different operational representation

    Stakefish provides liquid staking receipts that convert staking exposure into ERC-20 balance tracking, while other models rely more on managed validator operations or custody activity reporting, so reconciliation logic must match the provider’s representation.

  • Configuring multi-party approvals without planning for stakeholder coordination effort

    Anchorage Digital supports governed custody workflows, but multi-party approval configurations require careful coordination across stakeholders to avoid execution friction.

  • Choosing custody-only controls when the treasury needs end-to-end signing automation for custom tooling

    Ceffu centers on governed multisignature signing workflow configurations, but it is less suited for custom on-chain tooling that needs deep API coverage for highly customized treasury execution logic.

How We Selected and Ranked These Providers

We evaluated Stakefish, Blockdaemon, Kiln, and the other included providers on feature fit for ETH treasury execution workflows, operational ease of provisioning and governance workflows, and the value delivered for implementing reserve controls. Features accounted for 40% of the score, ease accounted for 30%, and value accounted for the remaining 30%. Stakefish earned the highest overall rating because liquid staking receipts convert staking exposure into ERC-20 balance tracking without requiring manual validator operations, which directly reduces reconciliation friction for ETH reserve visibility.

Frequently Asked Questions About Eth Treasury

How do ETH treasuries integrate staking actions with accounting when using Stakefish?
Stakefish separates validator operations from treasury interaction by letting treasuries act at the level of staking deposits and received staking tokens. That design turns staking exposure into ERC-20 token balances, so Blockdaemon and Kiln teams can still reconcile ETH reserve movements against token settlement without running validator lifecycle steps in-house.
Which providers support API-driven transaction execution tied to an approval workflow?
Blockdaemon exposes an API-oriented orchestration model that connects signing and transaction automation to operational runs and reporting paths. Kiln also supports automation through governed execution steps, but it focuses on enforcing treasury intent boundaries through workflow gates rather than validator-style settlement.
When does operational reporting matter more than custody-only controls for an ETH treasury?
Anchorage Digital couples custody workflows with operational interfaces that treasuries can run as recurring processes, which is useful when wallet reconciliation is required across time-based policies. Figment and Stakefish can deliver strong operational visibility for staking and token settlement, but Anchorage emphasizes reconciliation evidence tied to custody-controlled keys.
What security and access controls differ between Hex Trust and Ceffu for signing workflows?
Hex Trust routes signing through governed key setups using multisignature or contract wallet patterns and emphasizes transaction approval workflows tied to those setups. Ceffu focuses on configured custody controls around multisignature wallet operations and repeatable signing flows, so the team can standardize approval and execution packaging for recurring reserve actions.
Where does RBAC-style admin control fit, and what breaks if governance stays outside the workflow layer?
Stakefish keeps governance and key controls outside the treasury RBAC layer, so internal approval workflows must be implemented around contract calls rather than validator signing. Blockdaemon and Kiln both align closer to workflow enforcement, but teams still need to map approval logic to the provider’s workflow primitives to avoid bypass paths for routine transfers.
How should ETH treasuries plan data migration from existing wallet and reporting systems?
Deloitte typically centers onboarding on policy design and documentation that maps internal operating procedures into custody, signing, and reporting workflows. Anchorage Digital and Komainu both provide operational reporting artifacts that support wallet reconciliation, which reduces the gap between legacy tracking and new execution records.
Which provider is a better fit for validator execution delegation with governance oversight?
Figment fits teams that need delegated validator execution and ongoing operational reporting tied to staking lifecycle steps. Stakefish supports treasury-level reconciliation via staking deposits and received tokens, but it is oriented around staking exposure settlement rather than hands-on validator management.
What breaks if an ETH treasury expects validator-like lifecycle controls from a custody-first provider?
Komainu and Ceffu focus on custody and audited execution coordination, so they are not designed to replace validator operational runbooks with validator-level tuning. Stakefish can cover tokenized staking exposure and settlement, but teams needing validator lifecycle change coordination should evaluate Figment for validator operations instead.
How do onboarding and operating model complexity differ between Kiln and Fidelity Digital Assets?
Kiln uses governed transaction approval workflows that enforce intent boundaries before execution, which adds workflow configuration aligned to approval steps. Fidelity Digital Assets is oriented toward managed custody and institutional execution that fits established governance processes for approvals and signer responsibilities, which reduces DIY wallet engineering but shifts operational surfaces into managed workflows.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Vendor-funded research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.