Finoa

• Name: Finoa
• URL: https://www.finoa.io/
• Category: regulated wallet-infrastructure company / staking-operator entity / service-boundary note
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Finoa belongs as an entity note. The useful control surface is not a novel custody primitive; it is the company boundary between the old licensed-custody posture, the current technical-services posture, and the still-live Finoa Consensus Services staking operator arm. That split answers questions the product note cannot cleanly answer on its own: which entity still sits in the regulated path, who says it does not control client assets anymore, and where validator and white-label staking operations still remain company-run.
• What it does:
  • Markets Finoa Technical Services as wallet and asset-management infrastructure for regulated VASPs and their institutional customers, with segregated wallets, multisignature governance workflows, and onchain verification flows
  • Explicitly says the current Finoa entity is a technology infrastructure provider rather than a MiCAR-authorized CASP, and says regulated services must be performed by the client’s own licensed entities
  • States in its privacy-policy disclosures that Finoa GmbH voluntarily surrendered and then formally lost its German crypto-custody license effective 31 December 2025, with subsequent data processing framed around orderly wind-down of the former regulated business
  • Operates a separate Finoa Consensus Services staking surface offering delegated staking, in-custody staking, and white-label validator deployments
  • Sells the staking arm on Germany-based infrastructure, worldwide cloud failover, automated operations, and 24/7 monitoring, plus genesis-validator credibility with foundations
• Key claims:
  • The homepage now says Finoa Technical Services “provides technology that enables regulated VASPs to protect and manage their customers digital assets with a secure platform” and explicitly says Finoa “is not an authorized Crypto-Asset Service Provider (CASP) under MiCAR,” “does not exercise control over client assets,” “does not provide custody,” and “does not facilitate the execution of orders”
  • The same homepage still markets the stack around 170+ supported assets, 12 L1 networks, and 10+ staking protocols, which means the company remains operationally relevant even after the custody-license change
  • The privacy policy says the license to conduct crypto-custody business was voluntarily surrendered and formally revoked effective 31 December 2025, and that ongoing processing is now tied to orderly wind-down and residual obligations rather than new regulated business
  • Finoa Consensus Services says it has deployed 10,000+ nodes, supports 7 networks, and has more than $2 billion under delegation at all-time high, with three main service paths: in-custody staking, delegated staking, and white-label nodes
  • The staking site also says foundations use FCS as a genesis validator, which makes the operator note useful beyond pure customer-wallet middleware because validator placement and launch-default influence can matter directly
• Whitepaper: No standalone company whitepaper is the point here. The strongest current primary materials are the Finoa homepage, the wind-down disclosures in the privacy policy, and the separate Finoa Consensus Services site; the earlier source capture in ../whitepapers/finoa-primary-sources-2026-04-30.md remains useful background.
• Sources:
  • https://www.finoa.io/
  • https://www.finoa.io/privacy-policy
  • https://finoa-fcs.io/

Internal linkages

• Product / service-layer note: finoa.
• Best adjacent entity reads: figment, fireblocks, and bitgo.
• Keep the split explicit: the project note is the product/service surface; this note is the legal-and-operating-entity boundary.

Protocol / company boundary

• Keep finoa on the product and service surface institutions still touch directly: wallet workflow, multisignature governance tooling, verification flows, and the separate Finoa Consensus Services staking modes.
• Keep this company note on the named-entity boundary: the former licensed-custody shell, the current technical-services posture that explicitly disclaims custody and MiCAR CASP status, and the still-live validator and white-label staking operator arm.
• That split matters because what workflows does Finoa expose? and which entity is actually licensed, disclaiming control, or running validators now? are related but not identical questions.

Control surface

• The practical leverage sits in service-boundary definition, who actually controls keys versus merely provides tooling, which licensed entity is on the hook, how much institutional workflow remains inside Finoa-managed software, and whether FCS keeps validator and white-label staking dependence alive after the custody posture narrowed.

• Read Finoa as a company whose most important current story is the boundary map: former licensed custodian, current technical-services vendor, and still-live staking operator.

• Last reviewed: 2026-08-13 UTC