Twinstake

• Name: Twinstake
• URL: https://www.twinstake.com/
• Category: institutional staking operator / validator operations company / compliance-shaped staking workflow middleware
• Summary: Twinstake belongs as an entity note. The interesting surface is not just that it runs validators. It is that the company bundles institutional staking operations, transaction-crafting support, reporting, communication-channel-based concierge workflow, and explicit Ethereum relay-filtering policy into one operator-controlled shell.
• What it does:
  • Operates non-custodial staking infrastructure for institutions such as asset managers, hedge funds, venture firms, foundations, exchanges, and other professional allocators
  • Provides API-based staking and reporting workflows, including endpoints for staking data plus transaction-crafting support for staking and unstaking across supported assets
  • Offers a concierge-style operating layer where staking activity can be initiated through client-chosen channels such as Slack, email, or Telegram while assets remain with the client’s custodian or wallet provider
  • Runs a portal for tracking staking positions, transaction history, rewards breakdowns, and downloadable daily or enhanced reports
  • Markets compliance-focused Ethereum validator configurations, including OFAC-compliant relay filtering by default and an optional stricter filtering layer for institutions with higher screening requirements
  • Maintains public validator- and staking-adjacent repositories spanning permissioned delegation, validator registries, deposit tooling, monitoring, and validator metadata
• Key claims:
  • The official site positions Twinstake as the institutional staking standard and describes it as an institutional-grade, non-custodial staking provider built for institutions rather than retail users
  • The products page says clients can stake from their custodian or wallet provider of choice, that Twinstake offers a high-performance API for reporting plus staking and unstaking transaction workflows, and that the service includes SOC 2-backed security posture plus external slashing insurance
  • The same products page makes the company boundary unusually explicit by describing white-glove service, client-chosen communication channels, detailed daily and enhanced reports, and a portal for operational visibility rather than only validator uptime
  • The compliance page says Twinstake adopts a Level 1 compliance-first Ethereum configuration by default, connecting only to OFAC-compliant relayers, and also offers a stricter Level 2 filtering layer for clients that want broader illicit-activity screening
  • The public GitHub organization reinforces that Twinstake is not only a sales layer but also maintains validator-operation and staking-adjacent technical artifacts such as permissioned NEAR delegation contracts, Ethereum deposit tooling, validator registries, validator-info repositories, and monitoring-related software
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials for this pass were Twinstake’s official site, products page, compliance page, and public GitHub organization.
• Sources:
  • https://www.twinstake.com/
  • https://www.twinstake.com/products
  • https://www.twinstake.com/about-us/compliance
  • https://github.com/twinstake

Internal linkages

• Project-layer alias: twinstake.
• Keep this note on the clearest adjacent reads: kiln, figment, and chorus-one.
• Useful execution-policy contrast: mev-boost.
• The analytical point is operator workflow, validator-policy configuration, and institution-facing staking operations — not a directory of every validator shop.

Protocol / company boundary

• There is not a very useful standalone Twinstake protocol boundary doing most of the analytical work.
• The useful questions are who operates the validators, who sets the easiest institutional staking workflow, who authors the reporting and transaction-crafting path, and who decides the default relay-filtering posture for Ethereum block production.
• That is why this note belongs in companies/: the practical authority lives in the company-run operating shell rather than in a neutral protocol primitive.

Control surface

• The leverage sits in validator operations, staking API defaults, concierge workflow, reporting visibility, supported-network coverage, and the client path through custodians or wallet providers.

• On Ethereum the leverage sharpens around relay policy: once an institution inherits Twinstake’s default OFAC-compliant relayer set or buys the stricter filtering tier, the company is shaping block-production policy rather than merely offering passive infrastructure.

• Read Twinstake as a validator-operations and compliance-shaped staking-workflow company, not as a protocol in its own right.

• Last reviewed: 2026-08-06 UTC