📝 Add Note on Initial Transaction

Signed-off-by: Pascal Marco Caversaccio <[email protected]>

Author: pcaversaccio

README.md

@@ -9,7 +9,7 @@
 This Bash [script](./safe_hashes.sh) calculates the Safe transaction hashes by retrieving transaction details from the [Safe transaction service API](https://docs.safe.global/core-api/transaction-service-overview) and computing both the domain and message hashes using the [EIP-712](https://eips.ethereum.org/EIPS/eip-712) standard.
 
 > [!NOTE]
-> This Bash [script](./safe_hashes.sh) relies on the [Safe transaction service API](https://docs.safe.global/core-api/transaction-service-overview), which requires transactions to be proposed and _logged_ in the service before they can be retrieved. Consequently, the initial transaction proposer cannot access the transaction at the proposal stage, making this approach incompatible with 1-of-1 multisigs.[^1]
+> This Bash [script](./safe_hashes.sh) relies on the [Safe transaction service API](https://docs.safe.global/core-api/transaction-service-overview), which requires transactions to be proposed and _logged_ in the service before they can be retrieved. Consequently, the initial transaction proposer cannot access the transaction at the proposal stage, making this approach incompatible with 1-of-1 multisigs.[^1] A simple and effective solution is to use the [`--interactive` mode](#interactive-mode), which gracefully defaults to zero values when no transaction is logged, allowing you to fully customise all transaction parameters.
 
 > [!IMPORTANT]
 > All Safe multisig versions starting from `0.1.0` and newer are supported.