Change log
Review the latest changes to the Salt SDK. Install the latest version from npm with npm install salt-sdk.
SDK Version 0.0.45β
- Added Denied Message Proposers policy that can limit proposers from signing messages with Salt accounts. Salt payment authorisations are the only exception. It is applied automatically to all proposers on newly created accounts
- Added a way to query for signed messages. Use
salt.getMessages()andsalt.getMessageById()to get the messages you've signed - Deprecated:
agentcollaborator role is nowdelegate. For this release, the nameagentstill works but is deprecated, so please switch todelegate - The unused
notesfield has been removed fromsalt.submitTx()params - Improved error handling and new error types for clearer and more consistent error messages
SDK Version 0.0.44β
- Changing a policy now requires signing an authentication message
- Added an invitation listener
- Added payer parameter to
createAccount()andsubmitTx(): The payer can be different from the signer, and paying from Salt accounts is supported - Added
getAccountFeePaymentsandgetOrganisationFeePayments()as a way to fetch information about fees paid - Terminology change in SDK: the term
human signerhas been changed toproposer
SDK Version 0.0.43β
π¨ Breaking Changesβ
RoboHost.provisionedhas been removed as it was a duplicate ofRoboHost.signers.length
Improvementsβ
- Robo Guardian Setup process observability improvement: Organisation owners can subscribe to Robo Guardian setup updates via WebSockets as well as a readiness signal (see salt.createRoboHost() docs for an example)
- AWS: A single AWS account can now host multiple Robo Guardian stacks
- Audit: Salt now records the SDK version used by all authenticated users
SDK Version 0.0.42β
π¨ This release includes a breaking change, and anything using Salt SDK 0.0.41 will need to be upgraded to version 0.0.42.
- You can now customise the SIWE message, using the parameter siweStatement in the
SALT({...,siweStatement})constructor - Better error handling: Added a
HostCeremonyError(a mirror of the existingJoinCeremonyError) - Additional checks and logic to mitigate against payload tampering in transaction ceremonies
- Additional checks and logic for ceremony joiners
- Improvements to updating collaboratorsβ statuses
SDK Version 0.0.41β
Updates the bundled MPC signing library.
SDK Version 0.0.40β
The first production release.
- Each network is now backed by a freshly deployed shard registry that the SDK targets automatically, and signing has been hardened against a failure that could occur when a signer key was reused across a very large number of key generations.
- Chain handling is simplified: the SDK no longer validates the wallet's connected chain, so the
WrongChainerror is no longer thrown (the class is retained as a deprecated no-op for backwards compatibility β pass the intended chain in your call parameters instead). - A
PreconfiguredEnvironmenttype ('MAINNET' | 'TESTNET' | 'STAGING') is now exported.
SDK Version 0.0.39β
- Adds detailed ceremony-timeout reporting.
- A new
CeremonyTimeoutErrortells you which phase timed out (waiting at the party barrier or during a protocol round), how long it waited, how many parties or messages it expected versus received, and which peers were still missing.
SDK Version 0.0.38β
Invitations now include information about who sent them and which organisation they belong to (invitedBy and organisation).
SDK Version 0.0.37β
Renames "members" to "collaborators" across the organisation APIs to match Salt's terminology, and adds a CeremonyJoinError that reports why the relay refused a ceremony join, for example the session was not found, a party was already connected, or the session was already in progress.
π¨ Breaking Changesβ
inviteMemberhas been renamed toinviteCollaboratorMember,MemberAccessLevelandMemberStatusare nowCollaborator,CollaboratorAccessLevelandCollaboratorStatus
SDK Version 0.0.36β
This version introduces some missed types which was causing misleading errors on the event emitters. It also adds a new function and a new supported chain.
SDK Version 0.0.35β
This version changes the way that Robo Guardian containers are registered. Now instead of an API key, you will be given a One time Password to verify after the robos start up. Also due to updates in the underlying libraries, the signing ceremonies should all be more resilient and less sensitive to latency.
SDK Version 0.0.34β
v0.0.34 is a significant change from v0.0.18. A lot of the SDK has been rewritten, but should still feel familiar. Any code that touches the SDK is likely to require changes to migrate to this version.
π¨ Breaking Changesβ
- Accounts created with v0.0.18 or older no longer work
- The underlying MPC process has been heavily changed - previous code written for v0.0.18 is likely not to work with v0.0.30
submitTxarguments have changed- ethers is no longer supported - this version uses viem
- Authentication now uses shorter tokens with refresh tokens
New Featuresβ
- Expanded organisation management - invite/update/remove members, decline invitations
- Expanded account management
- Expanded policy management - list/delete policies for accounts
- Robo Guardian container setup functions can now be done using the SDK