Launchnodes / External Signer for Canton
Launchnodes / Canton external signing

Sign transactions securely in Canton. With Fireblocks custody.

External Signer lets your organisation securely sign, isolate and audit transactions for multiple party IDs to multiple vaults in one Fireblocks workspace.

Speak to us
Custody Fireblocks MPC
Secure isolated signing One vault per party ID
Interface JSON-RPC 2.0 over HTTPS
Design principle

Multiple Canton party IDs are mapped to multiple individual vaults in a single Fireblocks workspace, providing secure isolated signing for each party ID and every connected vault.

01 / Multiple party IDs connected to multiple vaults

Sign transactions using a single Fireblocks workspace with multiple vaults.

The external signer holds no assets and no private keys. Keys never leave Fireblocks. It stores only operational metadata: wallets, sessions, networks, tenant to vault mappings and transaction records.

External signer lets party IDs connect individual vaults in a single Fireblocks workspace, ensuring client keys and funds are isolated.

Launchnodes external signer Fireblocks
01Your application submits commands›
02Participant Party ID resolved to vault and key›
03Participant node prepares the transaction›
04Vault signs under its approval policy›
05Participant node re-verifies and commits›
02 / Why it matters

Isolation you can prove.

/ 01

Fireblocks keeps the keys

Signing happens inside each tenant’s Fireblocks vault, under that vault’s own approval policy. There is nothing to extract from the signer.

/ 02

Parties are not tied to a node

An externally signed party derives its identity from its own key rather than the hosting participant, so it can be hosted on your participant, on your customers’, or on ours.

/ 03

Command-agnostic by design

You send fully formed commands and any disclosed contracts; the signer forwards them unchanged.

/ 04

Slow signatures are never lost

Where an approval needs a human, the transaction is left pending rather than failed. Calling sign again polls the original request, so there is no duplicate approval.

/ 05

One record, four identifiers

Every transaction correlates your id, the command id, the custody request id and the ledger update id, with timestamps for preparation and signing.

03 / Boundaries

Commands in. Signatures out.

Your application
Supplies

Everything that depends on your business domain stays with you.

  • Daml commands, fully formed
  • Any disclosed contracts those commands reference
  • The acting wallet, and optionally actAs and readAs
  • Business-level validation
The external signer
Does

Everything between an authenticated request and a committed transaction, including the parts that are easy to get wrong.

  • Authenticates the caller over OIDC
  • Resolves wallet to vault to signing key
  • Prepares the transaction on the participant
  • Obtains the signature from custody, resumably
  • Normalises encodings, submits, records the result
04 / Speak to us

Tell us the isolation and mapping you need.

Tell us how you want to map party IDs to individual vaults to ensure signing and keys are isolated and auditable, and we will walk you through the deployment and the integration on your side of the boundary. Or run the solution as a fully managed service.

Corporate email required / Response within 2 working days
Read, Learn, Participate

Blog

Docs (Gitbook)

Canton Webinar

Cookie Policy

Privacy Policy

71-75 Shelton Street, Covent Garden, London, England WC2H 9JQ

Copyright © 2026 Launchnodes Limited – All rights reserved.

Validator Node End to End Set up and Support

Launchnodes’ Concierge Service provides end-to-end set up for an Ethereum validator node. This is ideal if you want to Solo Stake and have at least 32 Ethereum or multiples of 32 Ethereum in a Metamask wallet, or a wallet compatible with depositing ETH through the ETH launchpad.

The validator nodes can connect to a Launchnodes Beacon node or your own Beacon nodes. You can use this service to build your own customised staking architecture as a solo Ethereum stakers. On AWS or your own infrastructure.

  • A fully managed set up for Ethereum Nodes in your own infrastructure
  • Non-technical users can run an Ethereum node as Solo Stakers
  • Scope for engineers and more technical users to review and optimise Validator node set up
Run Nodes
Etherum
Validator

RPC Nodes

When performing mission critical or financially significant activity on the Ethereum blockchain, having your own RPC nodes ensures you can trust the data. Third party APIs are powerful tools making development at scale easy, but Blockchain-building requires data you can trust, where you own the source, and this is what RPC nodes provide.

Run Nodes
Etherum
Validator

Teku Beacon Node with Geth

A pre-synced Beacon node (using the Teku or Prysmatic client), with the Geth Client for Ethereum that allows you to connect to the beacon chain quickly and connect to Validator nodes. Beacon nodes can take 4-5 days to synchronise. Geth nodes can take 1 or 2 days.

  • Launchnodes Pre-synced Ethereum Beacon node with Geth is synchronised within 3-5 hours, saving 5+ days of synchronisation time
  • Solo Stake Ethereum
  • Run RPC nodes faster and more resiliently
  • Build effective backup infrastructure for staking at scale
Run Nodes
Etherum
Validator

Pre-synced Geth Node

Launchnodes provides a pre-synced Geth Node on AWS for staking ETH, native RPC nodes and other Layer 2 solutions. For the purposes of ETH staking Geth is an execution layer client.

A pre-synced Geth node is useful for any business or person staking ETH and can be used by all consensus layer clients. These consensus layer clients can run on public cloud or private data centre infrastructure. Making it easier and cheaper to stake ETH

All ETH Layer 2 solutions also require an Ethereum Geth node. This easy to run Geth node is pre-synced and can be deployed on public cloud or bare metal. By making Geth easy Launchnodes supports building in the Layer 2 eco-system.

  • A pre-synchronised Geth node to make staking ETH easier, faster and cheaper.
  • Suitable for those staking ETH using all consensus layer clients
  • Makes ETH staking easier on cloud or private data centre infrastructure
Run Nodes
Etherum
Geth

Teku Validator Node

Launchnodes provides an Always ON Teku Validator Node for Ethereum staking on mainnet or testnets

  • Use the power of public cloud or bare metal to build your Solo Staking infrastructure
  • Always running the latest version of the Prysmatic or Teku Validator client software for Solo Staking
  • Your Validator node is easy to set up and private. It is entirely managed in your own infrastructure and connected to a Launchnodes Beacon node with a Geth execution layer client as default.
  • Or connect to your own Prysmatic or Teku Beacon node with your own execution layer client on public cloud or bare metal.
Run Nodes
Etherum
Validator

Nodes for other PoS blockchains

We provide customers with white labelled nodes that can run on public cloud, our infrastructure or data centre infrastructure owned by you. Create your own independent staking infrastructure with your own nodes in your own AWS, GCP or Azure account, or running on your own infrastructure.

Launchnodes offers all the staking building blocks to allow any level of customisation for ETH staking and for alternative blockchains.

Run Nodes
Geth
Beacon
Validator

Prysm Validator Node

Run Validator nodes on your own infrastructure public cloud or bare metal and stake 32ETH per node.

Launchnodes allows you to choose between Prysm or Teku software to be a Solo Staker and run Validator nodes and stake ETH. The Ethereum nodes run on infrastructure you own, while mnemonics, passwords, or public or private keys are never shared with Launchnodes.

Run Nodes
Etherum
Validator

Pre-synced Prysm Beacon Node with Geth

Launchnodes provides a pre-configured Geth client (execution layer) running alongside a Teku client (consensus layer). This allows you to run Beacon nodes that can connect to validator nodes to start earning staking rewards or access blockchain data directly.

Participate and stake Ethereum as a Solo Staker. Use Launchnodes container based product to run Beacon nodes that have a connected Geth node to connect to the beacon chain. The Beacon Chain coordinates the network, and manages Proof of Stake for Ethereum.

Run Nodes
Etherum
Beacon

Registration

Blockchains of most interest:(Required)
Contact Us

Contact us to learn more

Do you currently own Ethereum to stake?

Find out

Find out

Contact Us