Skip to main content

Welcome to Salt

Salt is programmable signing infrastructure for co-managed digital assets.

It lets organisations create accounts controlled by multiple signers, governed by policies, and supported by automated co-signers called Robo Guardians. Users keep control of their signing material. Salt coordinates the workflows around account creation, policy enforcement, and transaction signing, but Salt is not a signer and does not custody user key material.

Salt can be used directly through the Salt app, programmatically through the Salt SDK, or embedded into fintech applications that need self-custodial wallet infrastructure for their own users.

What Salt is for​

Salt is designed for teams and applications that need to move digital assets without relying on a single private key, a smart contract wallet on every chain, or a custody provider that sits inside the signing quorum.

With Salt, you can:

  • create policy-controlled accounts for organisations, teams, bots, and agents
  • manage the same account address across EVM chains
  • delegate limited execution rights without giving up custody
  • use Robo Guardians to automatically co-sign transactions that satisfy policy
  • build embedded wallet flows through the Salt SDK
  • let fintech users view and manage their Salt-backed holdings on the Salt app

One account, many EVM chains​

A Salt account behaves like an EOA. The same account address can be used across EVM chains, without deploying a separate smart contract wallet on each network.

This makes Salt useful for organisations that operate across chains, and for fintechs that want to give users a consistent account layer without rebuilding wallet infrastructure chain by chain.

See supported networks

Policies before signatures​

Salt separates transaction coordination from cryptographic signing.

Before a transaction is signed, Salt checks whether the proposed action complies with the account’s active policies. Policies can restrict things like destination addresses, transaction size, functions, assets, timing, and signer permissions.

If the transaction passes policy, Robo Guardians can participate in the signing flow. If it does not, they do not co-sign.

This allows organisations to delegate execution to humans, bots, agents, or third-party managers without giving them unrestricted control over assets.

Robo Guardians​

Robo Guardians are self-hosted automated co-signers for Salt accounts.

They hold one part of an organisation’s signing quorum and co-sign only when a proposed transaction satisfies the organisation’s policies. They are designed to stay online when human signers are not, so approved workflows can continue without waiting for manual approval every time.

Each Robo Guardian runs on infrastructure chosen by the organisation. The organisation can run it on its own hardware or cloud environment, or delegate hosting to a third party it trusts.

Salt coordinates with Robo Guardians, but does not host them, control them, or hold their key material.

Learn more about Robo Guardians

Ways to use Salt​

Use the Salt SDK​

Use the Salt SDK to create organisations, accounts, policies, and transaction flows programmatically.

This is the right path for developers, automated services, bots, agents, and teams building their own interface on top of Salt.

Embed Salt in a fintech application​

Fintechs can use Salt as wallet infrastructure inside their own product. Their users can onboard through the fintech’s interface while still having Salt-backed accounts that can be viewed at app.salt.space where appropriate.

This lets fintechs build managed account, treasury, yield, payments, or asset management experiences without taking custody of user assets.

Where to start​