Robo Guardians are an Organisation’s automated risk department, and are entirely within the control of your Organisation.
These digital risk managers with wallets hold a portion of the key material for every Account created on Salt, and enforce the Policies set on an Organisation.
The Robo Guardians ‘host’ is a combination of hardware and code that works with Salt and the material that makes up a private key.
To preserve self-sovereignty, the Robo Guardians, and their key material, reside on your organisation’s own infrastructure. Outside of testnet, Salt will never operate Robo Guardians.
Your team will need to set up the Robo Guardian infrastructure when setting up your Organisation on Salt.
Robo Guardian containers are fully owned and controlled by your organisation.
Robo Guardian containers need to be hosted on a server whose sovereignty lives with your organisation. Salt does not have access to your Robo Guardian containers.
A Robo Guardian container controls access to 10 externally owned accounts (EOAs) - otherwise known as Robo Guardians. Every Robo Guardian can act as a co-signer on Accounts in your Organisation.
A Robo Guardian container, and each Guardian within it, is run and secured by your organisation. Salt will provide instructions on how to use an ‘infrastructure as code’ setup to build a secure environment using AWS tools. Otherwise, an organisation may choose to run their Robo Guardian container on any Linux-compatible hardware they chose.