Validator key generation: what swap users need to know

Validator key generation creates the credentials Chainflip operators need to run validators; it is not a step ordinary users take before swapping. Validators use keys to help run the network and authorize its actions. A swapper uses their own wallet to approve a transaction. Mixing up these roles can lead to sharing sensitive information with the wrong person.

What does validator key generation do?

It gives a validator the keys it needs to participate in Chainflip. Operators create credentials for their node and accounts. The protocol also runs shared key-generation ceremonies, where validators work together to create keys for the network’s vaults. A vault is where assets are held as the network processes swaps.

Those shared keys use threshold signatures: a way for a group to authorize a transaction without one validator holding the whole signing key. This lets validators collectively approve transfers from vaults. It is separate from the key in your wallet, which you use to approve spending from your own address.

Do you need validator keys before a swap?

No. A regular swapper does not generate validator keys or join a key-generation ceremony. You choose a supported asset pair, provide a destination address, and approve the transaction from the wallet that holds the asset you are sending. The network’s validators handle their part behind the scenes.

The type of swap can affect how you start and what information you provide. For a closer look at which Chainflip swap type fits your task, see the separate guide. Before confirming, check the source asset, destination asset, network, and destination address. A validator’s keys should never be needed for this.

What should validator operators protect?

Operators have a different job. They must generate and store their own node credentials securely, keep recovery material private, and back it up as the official setup instructions require. If a secret key or recovery phrase is exposed, someone else may be able to control the associated account. A validator’s Ethereum key is intended for the node, not for a personal wallet.

Keep these roles straight:

• Wallet key: authorizes your own swap transaction.
• Validator keys: let an operator run and manage a validator.
• Shared vault key: lets validators jointly authorize network transfers.

For most users, the practical check is simple: approve the swap in your wallet and never disclose its recovery phrase. Watch the transaction status and confirm the output arrives at the address you gave. Operators should watch for key rotations and follow current setup guidance, since their key duties continue after a swap begins.