-
-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Nonce Defaulting to 0
in --interactive
Mode
#22
Comments
I proposed a fix in PR: |
0
in --interactive
mode0
in --interactive
Mode
Oh I also made a PR: #24. Can you test that one please? |
Yep - that worked fine for me. In theory you can also default the to / address field from the |
I guess it would be nice to make all parameters optional if you're using |
I don't want to break user space again here tbh for |
If you agree I will merge my PR and close yours to keep everything KISS. |
Thx for raising it! |
Sounds good - thanks for the prompt fix (and the utility overall!). |
Give me another hour or so before I merge it - I wanna run some sanity tests locally. |
### 🕓 Changelog Fixes #22. This PR removes the unnecessary `nonce` override since it is already provided via the CLI. Additionally, fallback values are added for the `version` and `response` parameters in case `curl` fails silently. These changes ensure the script runs smoothly under all conditions. --------- Signed-off-by: Pascal Marco Caversaccio <[email protected]>
In order to verify hashes before submitting an initial signature, I am using:
./safe_hashes.sh --network ethereum --address XXX --nonce YYY --interactive
then entering the transaction data.
Despite specifying the
nonce
, the script seems to use a nonce of 0 - it is worth noting that at the point I'm running the script, the transaction has not yet been added to the SAFE API.If I don't specify a
nonce
on the CLI, then it gives an error message:The text was updated successfully, but these errors were encountered: