feat: migrate `forc-wallet` repository to `forc` monorepo (#1) * initial commit * cli methods for generate and import * custom formatting * update docs * add newline * add cargo toml description and license * add ci for wallet * cargo toml lint * Apply suggestions from code review Co-authored-by: John Adler * feat: integration with the SDK (#3) * Use the SDK API to enable basic features * refactor: refactor current wallet functionalities (#11) * Add lock file (#21) * feat: init & new commands - A way to init a new HD wallet or create a new account (#19) * refactor: list accounts without decrypting the wallet (#23) * refactor: Do not require password for listing accounts * docs: better doc comments * feat: added `account` command to show address of an account given its index (#25) feat: added account command to show address of an account given its index * feat: add the sign feature (#24) * Update readme with installation and basic usage (#30) * Update readme with installation and basic usage * Update README.md Co-authored-by: mitchmindtree Co-authored-by: mitchmindtree * bump to v0.1.0 (#29) * feat: Allow wallet to be regenerated from a mnemonic phrase (#34) feat: init accepts optional phrase * feat: Accept optional phrase as a password field rather than a parameter (#36) * feat: Phrase is imported using a password field * Update reaedme with --import * feat: Move init --import to a seperate command (import) (#38) * Adds a CI check to ensure the lock file is always up to date (#42) Add a CI check to ensure the lock file is always up to date Version 0.1.0 was published with an out-of-date lock file. This updates CI to ensure it's always at least up to date with the `Cargo.toml` requirements. * feat: Add --export to account to export account's private key (#40) * CI: build binaries in CI (#41) closes #32. * bump fuels versions to 0.24.0 (#45) closes #44. * feat: Moved --export to a seperate export command (#47) closes #43 * refactor: Use SDK derivation path (#50) closes #28. * refactor: rework some basic functions (#51) Co-authored-by: Ahmed Sagdati <37515857+segfault-magnet@users.noreply.github.com> * Bump version to v0.1.1 (#48) closes #46. * Fix error in the case of an non-existing vault path and refactor discrete string utility (#54) closes #52. closes #53. Also slightly improves the error message for existing vault path. Since these are affecting our users rn, I wanted to get them out as soon as possible hence they are in the same PR. * bump version to 0.1.2 (#55) * Add tests for existing wallet operations (#57) closes #10. * import is own command and not anymore a argument (#58) In commit 217c466 the import argument was moved to a separate command, the current README does not reflect that. * chore: clippy fixes for rust 1.65 (#64) * ci: Added markdown lint (#63) closes #62. * doc: Add export and import to readme (#61) closes #60. * docs: update README quickstart (#67) closes #66 * chore: clippy warnings for rust 1.66.1 (#71) * feat: sign with private key command for testing with local node (#70) closes #69. Co-authored-by: mitchmindtree * chore: bump version to 0.1.3 (#72) * chore: 1.67.0 cargo clippy fix (#74) Rust 1.67.0 is released and there are some new clippy lints to address. * update README to version 1.3 (#73) * Refactor `--path` arg for commands, use consistent terminology for wallet directory (#79) Closes #76. ## `--path` arg Previously each subcommand had it's own instance of the `--path` argument. Instead, we now expect the `--path` argument on the top-level command, e.g. ```console forc wallet --path ./path/to/wallet list ``` rather than ```console forc wallet list --path ./path/to/wallet ``` By coupling the arg with the `wallet` command we also make the association a bit clearer. ## Wallet vs Vault This PR also refactors a lot of the utility functions to use "wallet" when referring to the wallet directory, rather than "vault". Before, the two were used interchangeably which could cause some confusion for future maintainers. * Expect path to wallet file, not dir. Use a cache for account addresses. (#80) *Note: This PR is based on #79 which should land first.* Closes https://github.com/FuelLabs/forc-wallet/issues/78, taking the approach mentioned here: https://github.com/FuelLabs/forc-wallet/issues/78#issuecomment-1425160146 When a path to a wallet is specified, we now expect a path to a keystore file. The file can be anywhere on the user's machine and no longer requires a `.accounts` file in the same directory to track derived accounts. Instead, we now track derived accounts within `~/.fuel/wallets/accounts`, where each wallet has its own unique cache directory named by hashing the wallet's ciphertext into a fixed-length hex string. Each directory contains a file for each derived account address, where the file name is the wallet's account index and the file itself contains the address as a utf8 string. This PR also removes the `serialtest` dev dependency in favour of generating unique directory names for temporary test directories. * Update all dependencies, removed unused (#81) *PR based on #80.* * Address ambiguitiy in init, new, list. Create a new `account` subcommand (#84) *Closes #83.* This aims to address the ambiguities mentioned in #83 using the solution mentioned there. The main behavioural changes are: 1. We now use an `account ` subcommand (rather than a `--account-index ` flag under each command). 2. To create a wallet, we now use `forc wallet new` rather than `forc wallet init`. 3. To create a new account, we now use `forc wallet account new`, rather than `forc wallet new`. 4. To list all accounts, we now use `forc wallet accounts` rather than `forc wallet list`. Also addresses a whole suite of general refactor stuff: - De-duplicates a bunch more logic throughout the crate. - Some of the account-specific logic previously in `utils` has been moved to the `account` module. - Some of the account module functions have been renamed from `new` -> `derive` to reflect the behaviour more closely. - Functions in the `account` module have had `account` removed from their names in favour of using the `account` module as a namespace (rather than c- style name-spacing with underscores). - Moved the single remaining function from the `export` module content (for exporting an account's key) to the `account` module. - Addressed some nits raised by @sdankel in #80. - Improved consistency of error messages. - Fixed some places where we incorrectly used `request_new_password` (it prompts for password confirmation, which we don't need when deriving new addresses or signing). - Take proper transaction ID type as input in CLI args rather than a string. The help output has also been extended with some examples using clap's `after_help` attribute: ```console EXAMPLES: # Create a new wallet at the default path `~/.fuel/wallets/.wallet`. forc wallet new # Import a new wallet from a mnemonic phrase. forc wallet import # Derive a new account for the default wallet. forc wallet account new # Derive a new account for the wallet at the given path. forc wallet --path /path/to/wallet account new # Derive (or re-derive) the account at index 5. forc wallet account 5 new # Sign a transaction via its ID with account at index 3. forc wallet account 3 sign tx 0x0bf34feb362608c4171c87115d4a6f63d1cdf4c49b963b464762329488f3ed4f # Export the private key of the account at index 0. forc wallet account 0 export-private-key ``` * Add `--unverified` option to commands that display cached addresses (#85) *PR based on #84.* Closes #77 as the main concern with storing addresses in plain text is that it makes them an easy target of corruption. This PR changes the behaviour of the `forc wallet accounts` and `forc wallet account ` commands to always require a password by default. This ensures the printed addresses are valid. This was tricky to guarantee in the old behaviour as the cached plain-text files could have been corrupted or maliciously altered since they were last written. Both commands now accept an `--unverified` flag that emulates the old behaviour and purely reads the addresses from the cache. * feat: Add support for signing arbitrary data via new `string`, `file` or `hex` subcommands (#88) This PR allows the user to sign arbitrary data. Here are some examples taken from the help output: ```console # Sign an arbitrary string. forc wallet account 3 sign string "blah blah blah" # Sign the contents of a file. forc wallet account 3 sign file /path/to/data-to-sign # Sign a hex-encoded byte string. forc wallet account 3 sign hex "0xDEADBEEF" ``` This PR also re-introduces the `forc wallet sign` subcommand. This re-uses the existing logic for signing via the account subcommand, though provides the additional option of signing with a private key. Some examples: ```console # You can also use the `sign` subcommand directly. The following gives the same result. forc wallet sign --account 3 string "blah blah blah" # Sign directly with a private key provided via interactive prompt. forc wallet sign --private-key string "blah blah blah" ``` Notably, this PR also removes the old `forc wallet sign-private` command in favour of using `forc wallet sign --private-key` in order to try and provide a more uniform interface. The `sign tx` subcommand has been renamed to `sign tx-id` in anticipation of supporting signing transaction *files* in the future. See #89. The `sign` command also now allows for specifying the full private key or account password via command line arguments (`--private-key-non-interactive ` and `--password-non-interactive ` respectively), however these should likely only be used for testing in non-interactive environments. As a result, we don't highlight them as options in the help output, and we provide `WARNING`s about their use in their argument help output. Closes #75. * Publish v0.2.0 (#90) I'll include the following in the release notes too. ## Breaking Changes The `forc wallet` CLI has had a significant overhaul! Notably: * To create a new wallet, use `forc wallet new` rather than `forc wallet init`. * To derive a new account, use `forc wallet account new` rather than `forc wallet new`. * To list all previously derived accounts, use `forc wallet accounts` rather than `forc wallet list`. * The old `--account-index` flag has been removed in favour of the `account` subcommand, e.g. * To sign a tx ID with an account, use `forc wallet account sign tx-id` rather than `forc wallet sign --account-index --tx `. * To export an account private key, use `forc wallet account private-key` rather than `forc wallet export --account-index`. * The `forc wallet accounts` command now requires a password to re-derive accounts for verification. An `--unverified` flag must be passed to read public addresses from the account cache non-interactively. * The `sign` command now accepts a subcommand for the kind of data we're signing, e.g. `tx-id `, `string `, `file `, `hex `. * To sign a tx ID, use `forc wallet sign --account tx-id ` rather than `forc wallet sign --account-index --tx `. * To sign with a private key, use `forc wallet sign --private-key tx-id ` rather than `forc wallet sign-private --tx `. Be sure to check the updated README or `forc wallet --help` for updated usage examples. * feat: add support for displaying public key for an account derived with `forc-wallet` (#93) closes #91. This PR is adding `public-key` subcommand to `account` command. Example usage is: `forc-wallet account public-key` * chore: bump version to 0.2.1 (#94) For releasing #93 to unblock @ra0x3. * Add `balance` and `account balance` subcommands for printing all asset balances (#95) Show the balance of the specified account: ```console forc wallet account balance ``` Show the total balance for the whole wallet: ```console forc wallet balance ``` Show the balance of each non-empty account prior to the wallet total: ```console forc wallet balance --accounts ``` Demo: ```console $ forc wallet account 0 balance Please enter your password to verify account 0: Verifying account 0 Connecting to https://node-beta-2.fuel.network/ Fetching the balance of the following account: 0: fuel1htrldg7wpelrnhvad8lwcep57duhpxmj2h6a55nhr4md4839cy2q04p3tu Account 0: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 1000000000 $ forc wallet account 1 balance Please enter your password to verify account 1: Verifying account 1 Connecting to https://node-beta-2.fuel.network/ Fetching the balance of the following account: 1: fuel1vjnvqkvea7hhluhh8alwt7yuq0nj7d0sfa2vxu3q5drna5ujrzmqy0k43h Account 1: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 500000000 $ forc wallet account 2 balance Please enter your password to verify account 2: Verifying account 2 Connecting to https://node-beta-2.fuel.network/ Fetching the balance of the following account: 2: fuel13c78d66334nqnrat322gfszne77a8tklhfklkshk0fmdq2e0dscsdyrs8u Account 2: Account empty. Visit the faucet to acquire some test funds: https://faucet-beta-2.fuel.network $ forc wallet balance Please enter your password to verify accounts: Verifying account 0 Verifying account 1 Verifying account 2 Verifying account 9 Connecting to https://node-beta-2.fuel.network/ Fetching and summing balances of the following accounts: 0: fuel1htrldg7wpelrnhvad8lwcep57duhpxmj2h6a55nhr4md4839cy2q04p3tu 1: fuel1vjnvqkvea7hhluhh8alwt7yuq0nj7d0sfa2vxu3q5drna5ujrzmqy0k43h 2: fuel13c78d66334nqnrat322gfszne77a8tklhfklkshk0fmdq2e0dscsdyrs8u 9: fuel14f6e7arrxqz8vjc0dyp8yhzng9r2u4wjvm89falk9d2y9vv6l6mq5rj3mf Total: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 1500000000 $ forc wallet balance --accounts Please enter your password to verify accounts: Verifying account 0 Verifying account 1 Verifying account 2 Verifying account 9 Connecting to https://node-beta-2.fuel.network/ Fetching and summing balances of the following accounts: 0: fuel1htrldg7wpelrnhvad8lwcep57duhpxmj2h6a55nhr4md4839cy2q04p3tu 1: fuel1vjnvqkvea7hhluhh8alwt7yuq0nj7d0sfa2vxu3q5drna5ujrzmqy0k43h 2: fuel13c78d66334nqnrat322gfszne77a8tklhfklkshk0fmdq2e0dscsdyrs8u 9: fuel14f6e7arrxqz8vjc0dyp8yhzng9r2u4wjvm89falk9d2y9vv6l6mq5rj3mf Account 0: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 1000000000 Account 1: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 500000000 Total: Asset ID Amount 0x0000000000000000000000000000000000000000000000000000000000000000 1500000000 ``` Just like for the `account` and `accounts` subcommands, the `--unverified` flag allows for retrieving the address associated with an account index without verification to avoid the need to re-enter the password (useful for testing). The `--node-url` flag allows for specifying the network URL. This PR defaults the value to the beta-2 network. Thinking further, we may prefer to default to a local network for safety, and require that remote networks are specified manually. I'll update the PR to make this change. This should make it easier to test and implement #65. ## TODO - [x] Add a more general wallet balance summary command that aggregates the balance of each known account. ### Follow-up - Add option for listing all individual UTXOs (not just full balance). #97. Closes #68 --------- Co-authored-by: Kaya Gökalp * Add beta-3 network URL. Switch to beta-3 as the default. (#101) @bingcicle I'm thinking we probably want to release a new `forc-wallet` version and bump fuelup's beta-3 toolchain version too. I'll cut a patch release as a follow-up. * Add derivation for plain address into forc-wallet (#99) closes #98. implemented `--as-hex` flag: By default, we are given the Bech32 format of the public key from the forc-wallet account command, whereas, for Sway, it is required that we use a plain address in the contract. For the convenience of developers, I rigged up the functionality to derive the plain address directly from the CLI with a unit test that sanity checks the type conversion. --------- Co-authored-by: Kaya Gökalp * Publish version 0.2.2. Only print `EXAMPLES` section on long help (i.e. `--help`). (#102) Co-authored-by: Sophie Dankel <47993817+sdankel@users.noreply.github.com> * feat: transfer (#103) Closes #65 I took the liberty to name the command `transfer` instead of `send` to keep consistent with what's available in `fuels_signers`: https://docs.rs/fuels-signers/0.38.1/fuels_signers/wallet/struct.WalletUnlocked.html#method.transfer Also added an additional feature that shows TX on the block explorer for convenience. Preview: ![image](https://user-images.githubusercontent.com/25565268/228483462-569ebec3-a491-456a-9843-db1036c67b2c.png) * chore: bump clap to v4.2.4 for v1.69 clippy lints (#110) * feat: expose cli functionality as a lib (#109) closes #100. In a recent tooling sync we talked about splitting lib functionality of `forc-wallet` into two parts: 1. Exposing cli bindings 2. Exposing all the functionality as pure functions (which does not require any CLI interaction) This completes the first part, any `forc-wallet` command that is useable from CLI should also be useable consuming `forc-wallet` as lib with this PR. * Update password input message (#112) * chore: bump fuels-* to 0.43 and fuel-* to 0.31 (#116) closes #115. * refactor: expose derive_secret_key functionality (#119) This is needed for forc-deploy integration. Basically forc-deploy wants to be able to derive & interact with accounts residing at the vault of forc-wallet. * fix: plain address queries with as-hex flag fails (#118) closes #117. * chore: bump version to 0.2.3 (#114) * refactor: expose balance collecting and printing functionality (#120) This PR exposes some balance related functionality so that `forc-deploy` can use them to print and collect account information for balance queries. * feat: enforce 0x prefix for hex data input (#125) closes #121. * fix: forc-wallet balance command panics after clap v4 update (#126) closes #122. This was a breaking change, in clap. [Here](https://github.com/clap-rs/clap/discussions/4306) is a discussion in clap's repo for the solution. * chore: bump fuels, fuels-core and fuel-* deps (#123) Co-authored-by: Kaya Gökalp * chore: bump version to v0.2.4 (#124) Co-authored-by: Joshua Batty * An upgrade to `fuel-core` v0.20.1 (#128) This pull request is an upgrade to a `fuel-core 0.20.1` release. --------- Co-authored-by: Voxelot * Release v0.2.5 (#131) * feat: point to beta-4 faucet and block explorer by default (#134) closes #133. With this PR `forc-wallet` points to beta-4 network by default. * chore: bump to v0.3.0 (#136) Publishing v0.3.0 forc-wallet which supports beta-4 network. * chore: bump fuels-rs to 0.49 (#140) * Updated command in error (#141) * chore: upgrade to fuels-rs v0.50.1 (#144) This PR upgrades fuels-rs crates used here to v0.50.1 * feat: upgrade `fuels-rs` and `fuels-core` to `tx-policies` (#145) Co-authored-by: green Co-authored-by: IGI-111 * chore!: upgrade to `fuels-rs` `v0.53.0` (#151) * chore: bump version to 0.4.0 (#153) To get: - #140 - #141 - #144 - #145 - #151 * feat: add --force option to forc-wallet new (#148) close #146 --------- Co-authored-by: Sophie Dankel <47993817+sdankel@users.noreply.github.com> * chore: bump sdk version to 0.54.0 (#158) Bumps sdk version to 0.54.0 for unblocking a fix for https://github.com/FuelLabs/sway/issues/5432 * chore: bump version to 0.4.1 (#159) * chore: expose new options for new_cli so that it can be used outside this repo (#160) It turns out we need it for forc-client as new options changed since last release and I failed to realize * chore: bump version to 0.4.2 (#161) Bumps version to v0.4.2 to get: 1. #160 * refactor: use common forc utils for formatting error & warning output (#155) close #150 Refer to [Comment](https://github.com/FuelLabs/forc-wallet/pull/148#discussion_r1410041380) I have reviewed whole forc-wallet project codes, all warning output that using `println!` has changed to `println_warning` ---- ## Screenshots ### For `Password do not match` #### Before ![image](https://github.com/FuelLabs/forc-wallet/assets/150114626/4dc8c5d9-94b3-48e5-a797-b9115eb78157) #### After ![image](https://github.com/FuelLabs/forc-wallet/assets/150114626/bdfeaf04-9768-44eb-b821-1fd6a3f156b1) ### For `Cached address for account` #### Before ![image](https://github.com/FuelLabs/forc-wallet/assets/150114626/3c0a4b65-ce2a-406e-b674-12b70e1082fe) #### After ![image](https://github.com/FuelLabs/forc-wallet/assets/150114626/f1850c17-1456-4aa0-8db8-2f3be42c23ba) * feat: point to beta-5 by default (#162) Beta-5 endpoint is ready forc-wallet should point to that by default without needing our users to use a flag to point out beta-5. * chore: bump to v0.4.3 (#163) Bumps version to 0.4.3 * chore: bump to sdk 0.56.0, vm 0.47 (#169) This will break compatibility with beta-5. * chore: bump to 0.5.0 (#170) * WIP: Working on `forc wallet list` (#167) Fixes #149 `list` command will request the password to unlock the wallet to derive the requested number of addresses. The derived addresses will be stored in cache. If `--unverified` is passed and the cache has enough addresses, the cache will be used, otherwise the user will be requested to unlock their wallet. * chore: bump to latest sdk for fuel-core 0.24.2 (#171) * chore: bump to v0.6.0 (#172) * chore: bump fuel-core to v0.24.3 (#174) Bumps fuel-core to v0.24.3 * chore: bump to v0.6.1 (#175) Co-authored-by: Brandon Kite * chore: use rust-sdk v0.60 to support fuel-core v0.26.0 (#177) * chore: bump to 0.7.0 (#178) * chore: bump fuels-rs to 0.62.0 (#179) bumps rust sdk version used to v0.62.0 * chore: bump to v0.7.1 (#180) Bump repo to v0.7.1 * chore: bump to fuel-core v0.27.0 (#181) Bumps the repo to use fuel-core v0.27.0 and rust-sdk v0.63.0 * feat: point to testnet for default query end point (#182) Updates the default end point for balance queries to testnet instead of beta-5. * chore: bump to v0.8.0 (#183) * feat: derive and cache some accounts with forc-wallet import (#187) closes #185. Derives some (matching behavior with forc-wallet new) default accounts when `import` is used. * chore: bump sdk to 0.64.0 to support fuel-core v0.28.0 (#189) Bumps sdk version used to 0.64.0, to support fuel-core v0.28.0 * chore: Use FuelLabs fork of publish-crates (#190) Also updating the slack webhook URL * chore: bump to v0.8.1 (#191) Made this a minor bump as fuel-core compatibility is not effected from v0.8.0, also no breaking api changes. * chore: update all dependencies (#195) It has been some time that we updated dependencies, and also #194 depends on nightly rust being able to build the repo which is only possible with https://github.com/tkaitchuck/aHash/issues/227. * ci: add code coverage reports (#194) closes #193. Adds code coverage reporting step to CI. Once we have #192 merged, coverage should increase dramatically. * chore: bump to use sdk 0.65 (#196) Starts the process to update our whole stack to fuel-core v0.31.0 * chore: bump to v0.8.2 (#197) waiting on #196 Co-authored-by: Joshua Batty * chore: bump to sdk 0.66 (#199) * chore: bump to v0.9.0 (#200) Co-authored-by: Sophie Dankel <47993817+sdankel@users.noreply.github.com> * feat: print plain addresses by default (#205) closes #198. We are now printing plain addressed from forc-wallet if bech32 is not explicitly requested by the user. * chore: bump fuels-* to v0.66.5 (#206) Updates fuels-* to v0.66.5 to support fuel-core v0.36.5 * chore: bump version to 0.9.1 (#207) * upgrade to fuels v0.66.6 and bump to v0.10.0 (#208) Upgraded fuels version and ran `cargo update` * feat: implement check sum reporting and update default target (#210) This PR implements couple of things: 1. Adds a new target 2. Adds checksum routines at places where we print user account, and accept user account (transfer to address). 3. Bumps sdk version to latest, 0.66.8. ### Checksum support 1. At the places where we output hex address we now output checksum encoded hex address so that copied and pasted into any other wallet, users will not face any warning. 2. At places where we accept a user account address, (currently only `transfer`'s `to` field), we query the provider to see if this account actually belongs to an user (i.e it is not a blob id, contract id etc). I needed to add an unwrap, at a place where I am sure that the result is not going to be failing. After this release I will remove it by rewriting the transfer section of the wallet. We first check if the checksum is valid while parsing the `To ` field. If that is not the case that is an immediate error. If it is indeed with the correct checksum then we proceed to querying the provider to see if it is an actual address. ### Couple of examples Here I try to transfer some funds to a contract, which has invalid ![image](https://github.com/user-attachments/assets/9843f4a6-4020-431a-b217-47ddd5a04817) Here i try to transfer to my account with valid check sum. ![image](https://github.com/user-attachments/assets/155866d0-4e92-43ad-b7fa-0e4200db8047) * chore: bump sdk to v0.66.9 (#213) Bumps sdk version to v0.66.9 * chore: bump to 0.11.0 (#214) * Import struct force var public visibility (#219) # Changelog - `force` var in the `Import` struct made public # Context This is required to address https://github.com/FuelLabs/forc-wallet/issues/139 as we need to support importing wallet - which requires instantiating the `Import` struct * Fix minor wallet issues (#220) # Changelog - added [`tempfile`](https://crates.io/crates/tempfile) to create test dirs for testing - updated test functions and util functions accordingly (removed redundant helper functions and replaced references) - added `rust-toolchain.toml` with stable rust `1.80.0` - minor refactors to CI workflows to match the `rust-toolchain.toml` rust version - git ignoring IDE directory (`.vscode/`) - fixed `new_at_index` function to print checksum wallet address (currently printing bech32 address to stdout) - updated `ensure_no_wallet_exists` function to handle the following cases: - where wallet path is a directory - where wallet path is an empty file - this also addresses: https://github.com/FuelLabs/forc-wallet/issues/186 - added unit tests for `ensure_no_wallet_exists` --------- Co-authored-by: Kaya Gokalp * chore: bump to 0.11.1 (#221) # Changelog - version bump `0.11.0` -> `0.11.1` * chore: remove beta networks (#229) Closes https://github.com/FuelLabs/forc-wallet/issues/228 * chore: bump sdk to 0.70 (#230) Bumps underlying rust sdk to v0.70, to unblock bump of sway repo * chore: bump version `0.11.1` -> `0.12.0` (#231) * refac: Update fuels and other dependencies (#236) The key changes are: - `WalletUnlocked` changes to `Wallet>` - `Provider` is now required to unlock a wallet, so I added `--node-url` as an option at the top level of the CLI so it can be set for any of the operations. Removed it from the subcommands. - Introduced `CliContext` containing the wallet_path and node_url since they have to get passed around in many places - Added a more thorough unit test of `derive_account_unlocked` that uses a mock Provider Closes https://github.com/FuelLabs/forc-wallet/issues/226 * chore: bump fuels to 0.72, fuel-core to 0.43.1 (#238) * chore: bump version to 0.14 (#239) * feat: wallet export (#240) closes #237 Adds `forc-wallet export` and `forc-wallet export --path ` command to be able to export mnemonic phrase so that it can be imported to the browser wallet. * update fuels-rs (#245) Note: Requires merging of https://github.com/FuelLabs/fuels-rs/pull/1670 ^ then a release is required - after which we can then update the `fuels-rs` dependency ^ this PR has been developed by locally pointing `fuels-rs` to PR branch above ## Description This pull request introduces several updates to modernize the codebase, simplify address handling, and improve maintainability. Key changes include upgrading the Rust version and edition, removing support for `Bech32` addresses, and refactoring related logic and tests to use the `Address` type consistently. - primary changes to Bech32 address removal are due to this pr: https://github.com/FuelLabs/fuels-rs/pull/1669 ### Environment and Configuration Updates: * Updated the Rust version to `1.85.0` in `.github/workflows/ci.yml` and `rust-toolchain.toml` to ensure compatibility with the latest features. [[1]](diffhunk://#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fL15-R15) [[2]](diffhunk://#diff-2b1bde2cf3a858b7bf7424cb8bcbf01f35b94dc80b925d9432cbab3319ca9b4eL3-R3) * Changed the Rust edition to `2024` in `Cargo.toml` for access to new language features. ### Address Handling Simplifications: * Removed support for Bech32 addresses and replaced all instances with the `Address` type across the codebase, including CLI commands, caching, and transfer logic. [[1]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L101-R94) [[2]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L215-L221) [[3]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L528-R450) * Eliminated the `To` enum and related parsing logic for Bech32 and hex addresses, simplifying address validation and usage. ### Code Refactoring: * Refactored functions to remove unnecessary conversions between Bech32 and `Address` types, reducing complexity in methods like `print_accounts_cli`, `transfer_cli`, and `verify_address_and_update_cache`. [[1]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L304-R255) [[2]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L528-R450) [[3]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L612-R518) * Updated test cases to align with the new `Address` type, removing Bech32-related assertions and ensuring compatibility with hex-based addresses. [[1]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L679-R589) [[2]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L701-R611) ### Dependency and Import Cleanup: * Reorganized imports in `src/account.rs` and `src/balance.rs` to remove unused dependencies and improve readability. [[1]](diffhunk://#diff-24f1b99fe644657495a289a0eacb2189c4aa3d51dd1f39253c667c424ba4ca96L6-L27) [[2]](diffhunk://#diff-01340666501d0dc6f96a6ea7a2d24d1d17a0ae1e499ca3cf32d2615a454353ceR2-R14) ### Documentation Adjustments: * Updated comments and type aliases to reflect the transition from Bech32 to `Address`, ensuring clarity in the codebase. --------- Co-authored-by: z * upd forc-tracing 0.67.0 -> 0.68.8 (#246) ## Description This pull request includes a version update for the `forc-tracing` dependency in the `Cargo.toml` file. * [`Cargo.toml`](diffhunk://#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542L14-R14): Updated the `forc-tracing` dependency from version `0.67` to `0.68`. --------- Co-authored-by: z * bump rust stable version 1.86.0 -> 1.90.0 (#248) Co-authored-by: z * bump fuels 0.74 -> 0.75 (#249) Co-authored-by: z * forc-wallet version update 0.15.1 -> 0.15.2 (#250) Co-authored-by: z * chore(deps): bump tokio from 1.44.1 to 1.44.2 (#252) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.44.1 to 1.44.2.

Release notes

Sourced from tokio's releases.

Tokio v1.44.2

This release fixes a soundness issue in the broadcast channel. The channel accepts values that are Send but !Sync. Previously, the channel called clone() on these values without synchronizing. This release fixes the channel by synchronizing calls to .clone() (Thanks Austin Bonander for finding and reporting the issue).

Fixed

sync: synchronize clone() call in broadcast channel (#7232)

#7232: tokio-rs/tokio#7232

Commits

ec4b1d7 chore: forward port 1.43.x
e3c3a56 Merge branch 'tokio-1.43.x' into forward-port-1.43.x
a7b658c chore: prepare Tokio v1.43.1 release
c1c8d10 Merge remote-tracking branch 'origin/tokio-1.38.x' into forward-port-1.38.x
aa303bc chore: prepare Tokio v1.38.2 release
7b6ccb5 chore: backport CI fixes
4b174ce sync: fix cloning value when receiving from broadcast channel
See full diff in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio&package-manager=cargo&previous-version=1.44.1&new-version=1.44.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/FuelLabs/forc-wallet/network/alerts).

Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * add .claude to .gitignore * Fix typo throughout codebase (#253) Fix "seperator" typo throughout codebase **Changes:** - `src/format.rs`: Enum variant `Value::Separator`, method `add_separator()`, and all references - `src/balance.rs`: Two call sites updated to match new method name --- > [!NOTE] > Standardizes typo by renaming `Seperator` to `Separator` in `List` and updates call sites in balance printing. > > - **Formatting (`src/format.rs`)**: > - Rename enum variant `Value::Seperator` -> `Value::Separator`. > - Rename method `add_seperator()` -> `add_separator()` and update internal uses. > - Rename local `seperator` -> `separator` in `Display` impl. > - Fix doc comment typo: “alligned” -> “aligned”. > - **Balance (`src/balance.rs`)**: > - Update calls to `List::add_seperator()` -> `List::add_separator()`. > > ^{Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
ef1c9dc3650cce409f96fd87c599c10ae3d5d032. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).} * Fix Typo in Wallet Accounts Directory Path (#247) --- **Description:** This pull request corrects a typo in the inline documentation for the wallet accounts directory path, changing accoutns to accounts for improved clarity and accuracy. --- > [!NOTE] > Corrects doc comment path from `~/.fuel/wallets/accoutns` to `~/.fuel/wallets/accounts` in `src/main.rs`. > > ^{Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
730bb51be53291c339fafe1ad99ec6296e4f06ad. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).} Co-authored-by: Joshua Batty * chore(deps): bump tracing-subscriber from 0.3.19 to 0.3.20 (#251) Bumps [tracing-subscriber](https://github.com/tokio-rs/tracing) from 0.3.19 to 0.3.20.

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.20

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

Manipulate terminal title bars

Clear screens or modify terminal display

Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

Logs user-provided input (form data, HTTP headers, query parameters, etc.)

Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:
[dependencies]
tracing-subscriber = "0.3.20"
Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.

Commits

4c52ca5 fmt: fix ANSI escape sequence injection vulnerability (#3368)
f71cebe subscriber: impl Clone for EnvFilter (#3360)
3a1f571 Fix CI (#3361)
e63ef57 chore: prepare tracing-attributes 0.1.30 (#3316)
6e59a13 attributes: fix tracing::instrument regression around shadowing (#3311)
e4df761 tracing: update core to 0.1.34 and attributes to 0.1.29 (#3305)
643f392 chore: prepare tracing-attributes 0.1.29 (#3304)
d08e7a6 chore: prepare tracing-core 0.1.34 (#3302)
6e70c57 tracing-subscriber: count numbers of enters in Timings (#2944)
c01d4fd fix docs and enable CI on main branch (#3295)
Additional commits viewable in compare view

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tracing-subscriber&package-manager=cargo&previous-version=0.3.19&new-version=0.3.20)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---

Dependabot commands and options

--- > [!NOTE] > ^{[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is
generating a summary for commit
8d33ac146769ff325d437398139e3a94e22b6136. Configure
[here](https://cursor.com/dashboard?tab=bugbot).} Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Joshua Batty * chore: swap deprecated actions/upload-release-assets to shogo82148/actions-upload-release-asset (#224) GitHub's actions/upload-release-assets is no longer maintained and seems to repeatedly break (e.g. SSLV3_ALERT_BAD_RECORD_MAC), so I suggest moving to a highly active and up to date runner. edit: Replace the deprecated actions/upload-release-asset@v1 with softprops/action-gh-release@v2 to fix reliability issues with release asset uploads. Changes: - Use softprops/action-gh-release@v2 instead of actions/upload-release-asset@v1 - Add conditional check for tag releases - Simplify configuration by using files parameter - Remove unnecessary environment variables and asset content type This resolves the issue where the old action was no longer maintained and repeatedly breaking the release process. --- > [!NOTE] > Switch release asset uploads to softprops/action-gh-release@v2 with tag-only gating and simplified inputs. > > - **CI Workflow (`.github/workflows/ci.yml`)**: > - **Release asset upload (build-release job)**: > - Replace `actions/upload-release-asset@v1` with `softprops/action-gh-release@v2`. > - Add condition `if: github.ref_type == 'tag'` to gate uploads on tags. > - Simplify inputs: use `with.files: ${{ env.ZIP_FILE_NAME }}`; remove `upload_url`, `asset_*` fields, extra `env` token, and content type. > > ^{Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
8dceff6ca44184221efb3aabf965996b568077a9. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).} Co-authored-by: JoshuaBatty * make forc-wallet into a workspace member * update forc-wallet version to 0.16.0 * create forc-wallet CHANGELOG.md file * ci: support independent workspace member releases Update CI workflow to support Tokio-style monorepo releases where each workspace member can be released independently using {crate-name}-{version} tags. Changes: - Update verify_tag.sh to parse crate name from tag format - Remove hardcoded Cargo.toml path from CI workflow - Add RELEASING.md with release process documentation * ci: generalize build-release job for any workspace member Make the build-release job fully generic to support multiple workspace members without hardcoded crate names. The CI now extracts the crate name from the tag and uses it throughout the build process. Changes: - Extract crate name from tag in build-release job - Replace all hardcoded 'forc-wallet' references with dynamic variable - Remove v prefix handling (following Tokio convention) - Update artifact naming to use full tag name - Enhance RELEASING.md with detailed CI workflow explanation * clean up * add Cargo.lock * fix: markdownlint errors - Disable changelog-incompatible rules in .markdownlint.yaml - Add trailing newline to README.md - Add blank lines around lists in RELEASING.md --------- Signed-off-by: dependabot[bot] Co-authored-by: Brandon Kite Co-authored-by: John Adler Co-authored-by: Rodrigo Araújo Co-authored-by: iqdecay Co-authored-by: Kaya Gökalp Co-authored-by: Kaya Gökalp Co-authored-by: mitchmindtree Co-authored-by: mitchmindtree Co-authored-by: Ahmed Sagdati <37515857+segfault-magnet@users.noreply.github.com> Co-authored-by: smuueth <99726574+smuueth@users.noreply.github.com> Co-authored-by: bing Co-authored-by: sarahschwartz <58856580+sarahschwartz@users.noreply.github.com> Co-authored-by: crypdough.eth <106392730+crypdoughdoteth@users.noreply.github.com> Co-authored-by: Kaya Gökalp Co-authored-by: Sophie Dankel <47993817+sdankel@users.noreply.github.com> Co-authored-by: Braqzen <103777923+Braqzen@users.noreply.github.com> Co-authored-by: Hannes Karppila Co-authored-by: Green Baneling Co-authored-by: hal3e Co-authored-by: IGI-111 Co-authored-by: levisyin <150114626+levisyin@users.noreply.github.com> Co-authored-by: César D. Rodas Co-authored-by: zees-dev Co-authored-by: zees-dev <63374656+zees-dev@users.noreply.github.com> Co-authored-by: z Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Kristóf Nagy Co-authored-by: leopardracer <136604165+leopardracer@users.noreply.github.com> Co-authored-by: Alfie John

feat: add the verify feature #45

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

feat: add the `verify` feature #45