For multisig transactions Safe is probably the most widely used service today. It also runs on Sapphire Testnet and Mainnet. However, it only supports EVM transactions. ROFL and other Oasis-specific transactions need to be wrapped as subcalls inside ordinary EVM transaction if you want to sign them with Safe which introduces some friction.
Add support for Safe in Oasis CLI so that instead of broadcasting a transaction, it is wrapped and submitted to Safe for signers to sign and submit. This would standardize and simplify ROFL update process in CI for example:
Possible implementation
Apart from File and Ledger introduce Safe account type. Then store the Safe API key as a private key and a public multisig vault address as an address. Then when using --account my_safe_account, the CLI would send it to the Safe API instead of broadcacsting it to the chain.
For multisig transactions Safe is probably the most widely used service today. It also runs on Sapphire Testnet and Mainnet. However, it only supports EVM transactions. ROFL and other Oasis-specific transactions need to be wrapped as subcalls inside ordinary EVM transaction if you want to sign them with Safe which introduces some friction.
Add support for Safe in Oasis CLI so that instead of broadcasting a transaction, it is wrapped and submitted to Safe for signers to sign and submit. This would standardize and simplify ROFL update process in CI for example:
Possible implementation
Apart from
FileandLedgerintroduceSafeaccount type. Then store the Safe API key as a private key and a public multisig vault address as an address. Then when using--account my_safe_account, the CLI would send it to the Safe API instead of broadcacsting it to the chain.