Safe-CLI

Command line utility for Gnosis Safe contracts. Use it to manage your Gnosis Safe easily from the command line

Installing

Python >= 3.7 is required. Python 3.9 is recommended.

git clone https://github.com/gnosis/safe-cli.git
cd safe-cli
stat venv 2>/dev/null || python -m venv venv
source venv/bin/activate && pip install -r requirements.txt

Using

cd safe-cli
source venv/bin/activate
python safe_cli.py <checksummed_safe_address> <ethereum_node_url>

Then you should be on the prompt and see information about the Safe, like the owners, version, etc. Next step would be loading some owners for the Safe. At least threshold owners need to be loaded to do operations on the Safe and at least one of them should have funds for sending transactions.

There're 3 operation modes:

blockchain: The default mode, transactions are sent to blockchain.
tx-service: Use tx-service command to enable it. Transactions are sent to the Gnosis Transaction Service (if available on the network), so you will be able to see it on the Gnosis Safe web interface/mobile apps. At least one signer is needed to send transactions to the service. Txs are not executed.
relay-service: Use relay-service [optional-gas-token] to enable it. Sends transactions trough the Gnosis Relay Service (if available on the network). If a optional gas token is set, it will be used to send transactions. For mainnet you can check available gas tokens here.

Loading owners is not needed if you just want to do read-only operations.

To load owners:

> load_cli_owners <account_private_key>
Loaded account 0xab...cd with balance=123 ether
Set account 0xab..cd as default sender of txs

You can also load owners from an environment variable. Before running the safe-cli:

export MY_PRIVATE_KEY=YOUR_EOA_PRIVATE_KEY

Then:

> load_cli_owners MY_PRIVATE_KEY
Loaded account 0xab...cd with balance=123 ether
Set account 0xab..cd as default sender of txs

To check the loaded owners:

> show_cli_owners

To unload an owner:

> unload_cli_owners <ethereum_checksummed_address>

Operations currently supported:

send_custom <address> <value-wei> <data-hex-str> [--delegate] [--safe-nonce <int>] [--tx-service] [--relay-service]: Sends a custom transaction from the Gnosis Safe to a contract. If --delegate is set a delegatecall will be triggered.
send_ether <address> <value-wei> [--safe-nonce <int>] [--tx-service] [--relay-service]: Sends ether from the Gnosis Safe to another account
send_erc20 <address> <token_address> <value> [--safe-nonce <int>] [--tx-service] [--relay-service]: Send ERC20 token from the Gnosis Safe to another account
approve_hash <keccak-hexstr-hash> <sender-address>: Approves a safe-tx-hash for the provided sender address. Sender private key must be loaded first.
add_owner <address>: Adds a new owner address to the Safe.
remove_owner <address>: Removes an owner address from the Safe.
change_threshold <integer>: Changes the threshold of the Safe.
enable_module <address>: Enable module address
disable_module <address>: Disable module address
change_fallback_handler <address>: Updates the fallback handler to be address. Supported by Safes with version >= v1.1.0. WARNING: DON'T USE THIS IF YOU DON'T KNOW WHAT YOU ARE DOING. ALL YOUR FUNDS COULD BE LOST
change_guard <address>: Updates the guard to be address. Supported by Safes with version >= v1.3.0. WARNING: DON'T USE THIS IF YOU DON'T KNOW WHAT YOU ARE DOING. ALL YOUR FUNDS COULD BE LOST
change_master_copy <address>: Updates the master copy to be address. It's used to update the Safe. WARNING: DON'T USE THIS IF YOU DON'T KNOW WHAT YOU ARE DOING. ALL YOUR FUNDS COULD BE LOST
update: Updates the Safe to the latest version (if you are on a known network like Rinkeby or Mainnet). WARNING: DON'T USE THIS IF YOU DON'T KNOW WHAT YOU ARE DOING. ALL YOUR FUNDS COULD BE LOST

Operations currently supported with transaction service (Mainnet, Rinkeby, Goerli, xDai...):

balances: Returns a list of balances for ERC20 tokens and ether.
history: History of multisig transactions (including pending).
get_delegates: Returns a list of delegates for the Safe.
add_delegate <address> <label> <signer-address>: Adds a new delegate address to the Safe.
remove_delegate <address> <signer-address>: Removes a delegate address from the Safe.

If the information in the information bar is outdated or there's any problem you can force the safe-cli to update the information about the Safe using:

> refresh

Creating a new Safe

Use safe_creator.py <node_url> <private_key> --owners <checksummed_address_1> <checksummed_address_2> --threshold <uint> --salt-nonce <uint256>.

Example:

python safe_creator.py https://rinkeby.infura.io/v3/token $PRIVATE_KEY --owners 0x848EF06Bb9d1bc79Bb3B04b7Ea0e251C6E788d7c --threshold 1

Demo

For this demo, PRIVATE_KEY environment variable was set to a EOA private key (owner of a a previously created and outdated Safe) and ETHEREUM_NODE_URL to a http rinkeby node. At first, Safe is updated to the last version and then 123 Wei are sent to the owner of the Safe (it could be any other address).

Don't use update command in mainnet, as it can leave your Gnosis Safe funds stuck. Safe CLI is still a beta

Use custom contracts

Safe-cli comes with the official Gnosis Safe contract addresses deployed on Mainnet, Rinkeby, Kovan and Goerli configured by default. If you want to use your own you can edit the file safe_cli/safe_addresses.py

Be careful when modifying these addresses, the funds in a Safe can get stuck if an invalid address it's used when updating to an invalid Safe Master Copy.

gsgalloway/safe-cli