Security at Salt
Salt never holds a key share. Audit reports, security notices and what we changed, posted here as they happen.
Updates
Security and audit updates
Newest first. Longer write-ups live on the blog.
-
Next
Audit report
Our first audit report is on its way
We run AI security audits across Salt’s code and publish every report here in full, findings and fixes included.
-
Update
The Salt recovery tool is open source
If Salt’s services are ever unavailable, you can still rebuild your accounts’ keys and move your assets elsewhere. It runs locally, never talks to Salt’s servers, and is MIT licensed.
-
Blog post
The key was never the weak point
The biggest crypto hacks don’t break the cryptography. They exploit access to systems that doubles as authority over money. How Salt’s signing flow keeps the two apart.
Read the post
Cryptography
Signing on audited cryptography
Salt’s signing layer runs on DKLs23 from Silence Laboratories. Your signers sign together on specialist threshold cryptography built for high-volume signing, and Salt never holds a share.
-
Audit · Cure53
SIL-04 security assessment
Silence Laboratories’ signing services and SDKs, including the DKLs23 library.
Read the report (PDF) -
Audit · Trail of Bits
Comprehensive report
The DKLs23 library and the cryptography underneath it.
Read the report (PDF)
How Salt is built
Nothing to steal in one place
Split by design
Key shares sit with your people (and bots) and your own Robo Guardians. Salt never holds any key shares.
Backed up onchain
Each share is encrypted to its signer’s wallet and stored in a smart contract on Arbitrum.
Policies first
Every transaction is checked against your policies before anyone signs, and auditors can verify those policies themselves.
Recover without us
Our open-source recovery tool gets your assets back even if Salt isn’t around.