The current way transactions are done is ‘in one go’ with creating the transaction and signing and broadcasting all done in one step using the safe-api command
safe wallet transfer.
This won’t allow hardware wallets to be used (or any offline / air-gapped signing). A typical hardware wallet process requires a three step process: create unsigned transaction, sign the transaction with the hardware wallet, broadcast the signed transaction.
This topic is to explore the possibility of allowing this workflow.
Perhaps we could introduce some flags to
safe wallet transfer
safe wallet transfer --create <from> <to> <balance> etc
safe wallet transfer --sign <unsigned-tx-data>
safe wallet transfer --broadcast <signed-tx-data>
I wonder if the
--dry-run flag is potentially useful here?
Just spitballing, I realise this is a nice to have and can be done later, but thought if there were some simple wins here we might be able to look into it.