diff --git a/docs/cli-reference/dfx-ping.mdx b/docs/cli-reference/dfx-ping.mdx index 73e5433556..b1a05c85e4 100644 --- a/docs/cli-reference/dfx-ping.mdx +++ b/docs/cli-reference/dfx-ping.mdx @@ -4,7 +4,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; -Use the `dfx ping` command to check connectivity to the IC or a testnet. This command enables you to verify that you can connect to the environment where you want to deploy to. +Use the `dfx ping` command to check connectivity to a network. This command enables you to verify that you can connect to the environment where you want to deploy to. To ping your local server, please note that you can only run this command from within the project directory structure. For example, if your project name is `hello_world`, your current working directory must be the `hello_world` top-level project directory or one of its subdirectories. @@ -22,11 +22,11 @@ You can specify the following argument for the `dfx ping` command. | Argument | Description | |----------|---------------------------------------------------------------| -| provider | Specifies the IC or testnet URL that you want to use. | +| provider | Specifies the network URL that you want to use. | ## Examples -You can use the `dfx ping` command to check whether the IC is currently available at a specific network address by running a command similar to the following: +You can use the `dfx ping` command to check whether the mainnet is currently available at a specific network address by running a command similar to the following: ``` bash dfx ping https://icp-api.io @@ -36,6 +36,7 @@ If the IC is running on the specified network provider address, the command retu ```json { - "ic_api_version": "0.8" + "replica_health_status": "healthy", + "root_key": [48, 129, 130, 48, 29, 6, 13, 43, 6, 1, 4, 1, 130, 220, 124, 5, 3, 1, 2, 1, 6, 12, 43, 6, 1, 4, 1, 130, 220, 124, 5, 3, 2, 1, 3, 97, 0, 129, 76, 14, 110, 199, 31, 171, 88, 59, 8, 189, 129, 55, 60, 37, 92, 60, 55, 27, 46, 132, 134, 60, 152, 164, 241, 224, 139, 116, 35, 93, 20, 251, 93, 156, 12, 213, 70, 217, 104, 95, 145, 58, 12, 11, 44, 197, 52, 21, 131, 191, 75, 67, 146, 228, 103, 219, 150, 214, 91, 155, 180, 203, 113, 113, 18, 248, 71, 46, 13, 90, 77, 20, 80, 95, 253, 116, 132, 176, 18, 145, 9, 28, 95, 135, 185, 136, 131, 70, 63, 152, 9, 26, 11, 170, 174] } ``` \ No newline at end of file diff --git a/docs/cli-reference/dfx-quickstart.mdx b/docs/cli-reference/dfx-quickstart.mdx index 9528af5efa..62801c131f 100644 --- a/docs/cli-reference/dfx-quickstart.mdx +++ b/docs/cli-reference/dfx-quickstart.mdx @@ -4,10 +4,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; -Use the `dfx quickstart` command to perform initial one time setup for your identity and/or wallet. This command -can be run anytime to repeat the setup process or to be used as an informational command, printing -information about -your ICP balance, current ICP to XDR conversion rate, and more. +Use the `dfx quickstart` command to perform initial one time setup for your identity and/or wallet. This command can be run anytime to repeat the setup process or to be used as an informational command, printing information about your ICP balance, current ICP to XDR conversion rate, and more. ## Basic usage @@ -21,7 +18,7 @@ You can use the following optional flags with the `dfx quickstart` command. | Flag | Description | |-------------------|----------------------------------------------------------------------------------------------------------------------------------------| -| `--identity` | The user identity to run this command as. It contains your principal as well as some things DFX associates with it such as the wallet. | +| `--identity` | The user identity to run this command as. It contains your principal as well as some things `dfx` associates with it such as the wallet. | ## Options @@ -39,12 +36,12 @@ To run a guided setup, run `dfx quickstart` ``` bash dfx quickstart ``` + ```shell -Your DFX user principal: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx -Your ledger account address: xxxxx -Your ICP balance: 1234.567 ICP -Conversion rate: 1 ICP <> 3.7950 XDR -Import an existing wallet? no -Spend 2.63504611 ICP to create a new wallet with 10 TC? no -Run this command again at any time to continue from here. +Your DFX user principal: hoqq7-3eo6j-dee4s-aiabk-6rqxw-kwgyo-rhru7-bdgmk-k5ipv-chkhx-cqe +Your ledger account address: 594369ede58d796ee76912d66201409930c9528d804f49a8e3f432bff957eae9 +Your ICP balance: 3.99910000 ICP +Conversion rate: 1 ICP <> 3.3357 XDR +Mainnet wallet canister: mwylj-4aaaa-aaaak-aflyq-cai +Mainnet wallet balance: 66.28 TC ``` diff --git a/docs/cli-reference/dfx-replica.mdx b/docs/cli-reference/dfx-replica.mdx index 7320d40ac5..3f904a1b33 100644 --- a/docs/cli-reference/dfx-replica.mdx +++ b/docs/cli-reference/dfx-replica.mdx @@ -4,4 +4,4 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; -**NOTE**: The replica command has been removed. Please use the [dfx start](./dfx-start.mdx) command instead. +The replica command has been removed. Please use the [dfx start](./dfx-start.mdx) command instead. diff --git a/docs/cli-reference/dfx-schema.mdx b/docs/cli-reference/dfx-schema.mdx index ee881dccb9..33fdcb9c2d 100644 --- a/docs/cli-reference/dfx-schema.mdx +++ b/docs/cli-reference/dfx-schema.mdx @@ -18,7 +18,7 @@ You can use the following option with the `dfx schema` command. | Option | Description | |------------------------|----------------------------------------------------------------------------| -| `--for ` | Display schema for which JSON file. (default: dfx) | +| `--for ` | Display schema for which JSON file. (default: `dfx`) | | `--outfile ` | Specifies a file to output the schema to instead of printing it to stdout. | The parameter passed to `--for` can be one of the following: @@ -28,8 +28,8 @@ The parameter passed to `--for` can be one of the following: | dfx | dfx.json | | networks | networks.json | | dfx-metadata | dfx-related metadata stored in canister and accessible with `dfx canister metadata dfx` | -| extension-manifest | extension.json [example][example-extension-json] | -| extension-dependencies | dependencies.json [example][example-dependencies-json] | +| extension-manifest | extension.json [View an example][example-extension-json] | +| extension-dependencies | dependencies.json [View an example][example-dependencies-json] | ## Examples @@ -51,7 +51,7 @@ You can print the schema for the "dfx" metadata JSON (which contains fields such dfx schema --for dfx-metadata ``` -If you want to write the schema for dfx.json to `path/to/file/schema.json`, you can do so by running the following command: +If you want to write the schema for `dfx.json` to `path/to/file/schema.json`, you can do so by running the following command: ``` bash dfx schema --outfile path/to/file/schema.json diff --git a/docs/cli-reference/dfx-sns.mdx b/docs/cli-reference/dfx-sns.mdx index b5e0ae59d5..cb1f40ebd1 100644 --- a/docs/cli-reference/dfx-sns.mdx +++ b/docs/cli-reference/dfx-sns.mdx @@ -5,10 +5,12 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; :::caution -The `dfx sns` command is no longer part of dfx, and has now been turned into the dfx extension. In order to obtain it, please run `dfx extension install sns`. +The `dfx sns` command is no longer part of dfx, and has now been turned into a `dfx` extension. In order to obtain it, please run `dfx extension install sns`. ::: -Use the `dfx sns` subcommands to simulate decentralizing a dapp. +Use the `dfx sns` subcommands to simulate handing a dapp off to the community for decentralized governance. + +## Basic usage The basic syntax for running `dfx sns` commands is: @@ -31,10 +33,9 @@ To view usage information for a specific subcommand, specify the subcommand and dfx sns validate --help ``` - ## dfx sns create -Use the `dfx sns create` command to create an SNS configuration file. The configuration file specifies important, legally and financially relevant details about dapp decentralization. The file leaves blank parameters such as token name; you will need to fill these in. +Use the `dfx sns create` command to create an SNS configuration file. The configuration file specifies important, legal and financial details about the dapp's decentralization. The file leaves blank parameters such as token name; you will need to fill these in. ### Basic usage @@ -63,11 +64,12 @@ dfx sns validate ### Examples -You can use the `dfx sns validate` command to verify that a configuration template is valid. It is not; it needs details such as token name: +You can use the `dfx sns validate` command to verify that a configuration template is valid. It is not, it needs details such as token name: ``` bash dfx sns config create ``` + Fill in the blank fields, then: ``` bash dfx sns config validate @@ -77,26 +79,31 @@ dfx sns config validate Use the `dfx sns deploy` command to create SNS canisters according to the local configuration file. -Note: Deploying SNS canisters does not require a proposal, however there is a hefty fee. Please don't create canisters on mainnet until you have tested your configuration locally and are sure that you are happy with it. +Note: Deploying SNS canisters on the mainnet does not require a proposal; however there is a hefty fee. Please don't create canisters on mainnet until you have tested your configuration locally and are sure that you are happy with it. ### Basic usage ``` bash -dfx sns deploy +dfx sns deploy --network=ic ``` ### Examples Create an SNS on the local testnet: + ``` bash dfx sns config create ``` + Fill in the blank fields, then: + ``` bash dfx sns config validate dfx sns deploy ``` -You can now verify that the sns canisters have been created. E.g.: + +You can now verify that the sns canisters have been created. + ``` dfx canister info sns_root dfx canister info sns_ledger diff --git a/docs/cli-reference/dfx-start.mdx b/docs/cli-reference/dfx-start.mdx index 5c9e3f6dfa..6001d44472 100644 --- a/docs/cli-reference/dfx-start.mdx +++ b/docs/cli-reference/dfx-start.mdx @@ -6,7 +6,7 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; Use the `dfx start` command to start a local development environment and web server processes. This command must be run before you can deploy canisters to the local development environment and test your dapps during development. -By default, all local dfx projects will use PocketIC to create this local development environment. You can run `dfx start` and `dfx stop` from any directory. See [local server configuration](#local-server-configuration) and [project-specific local networks](#project-specific-local-networks) below for exceptions. +By default, all local `dfx` projects will use PocketIC to create this local development environment. You can run `dfx start` and `dfx stop` from any directory. See [local server configuration](#local-server-configuration) and [project-specific local networks](#project-specific-local-networks) below for exceptions. ## Basic usage @@ -22,8 +22,8 @@ You can use the following optional flags with the `dfx start` command. |--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `--background` | Starts the local development environment and web server processes in the background and waits for a reply before returning to the shell. | | `--clean` | Starts the local development environment and web server processes in a clean state by removing checkpoints from your project cache. You can use this flag to set your project cache to a new state when troubleshooting or debugging. | -| `--enable-bitcoin` | Enables bitcoin integration. | -| `--enable-canister-http` | Enables canister HTTP requests. (deprecated: now enabled by default) | +| `--enable-bitcoin` | Enables Bitcoin integration. | +| `--enable-canister-http` | Deprecated and now enabled by default. | | `--pocketic` | Runs [PocketIC](https://github.com/dfinity/pocketic) instead of the replica. PocketIC is the default if no flag is used. | ## Options @@ -33,9 +33,9 @@ You can use the following option with the `dfx start` command. | Option | Description | |-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `--host host` | Specifies the host interface IP address and port number to bind the frontend to. The default for the local shared network is `127.0.0.1:4943`, while the default for a project-specific network is '127.0.0.1:8000'. | -| `--bitcoin-node host:port` | Specifies the address of a bitcoind node. Implies `--enable-bitcoin`. | +| `--bitcoin-node host:port` | Specifies the address of a `bitcoind` node. Implies `--enable-bitcoin`. | | `--artificial-delay milliseconds` | Specifies the delay that an update call should incur. Default: 600ms | -| `--domain domain` | A domain that can be served. Can be specified more than once. These are used for canister resolution [default: localhost] | +| `--domain domain` | A domain that can be served. Can be specified more than once. These are used for canister resolution [default: localhost] | ## Examples @@ -69,7 +69,7 @@ more .dfx/pid `dfx start` manages a PocketIC server that provides a local development environment. Running `dfx deploy` and other commands will manage canisters on this local network in the same way that `dfx deploy --network ic` deploys projects to the mainnet. -If run from outside a dfx project directory, or if `dfx.json` does not define the `local` network, then `dfx start` looks for the `local` network definition in `$HOME/.config/dfx/networks.json`. If this file does not exist or does not contain a definition for the `local` network, then dfx uses the following default definition: +If run from outside a `dfx` project directory, or if `dfx.json` does not define the `local` network, then `dfx start` looks for the `local` network definition in `$HOME/.config/dfx/networks.json`. If this file does not exist or does not contain a definition for the `local` network, then `dfx` uses the following default definition: ``` { @@ -80,7 +80,7 @@ If run from outside a dfx project directory, or if `dfx.json` does not define th } ``` -dfx stores data for the shared local network in one of the following locations, depending on your operating system: +`dfx` stores data for the shared local network in one of the following locations, depending on your operating system: - `$HOME/.local/share/dfx/network/local` (Linux) - `$HOME/Library/Application Support/org.dfinity.dfx/network/local` (macOS) diff --git a/docs/cli-reference/dfx-stop.mdx b/docs/cli-reference/dfx-stop.mdx index fc647a9f94..d801b3c0f9 100644 --- a/docs/cli-reference/dfx-stop.mdx +++ b/docs/cli-reference/dfx-stop.mdx @@ -4,9 +4,9 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; -Use the `dfx stop` command to stop the local development environment processes that you currently have running on your computer. In most cases, you run the canister execution environment locally so that you can deploy canisters and test your dapps during development. To simulate the connection to the IC, these processes run continuously either in a terminal shell where you started them or the in the background until you stop or kill them. +Use the `dfx stop` command to stop the local development environment processes that you currently have running on your computer. In most cases, you run the canister execution environment locally so that you can deploy canisters and test your dapps during development. To simulate the connection to the mainnet, these processes run continuously either in a terminal shell where you started them or the in the background until you stop or kill them. -You can run this command from any directory unless you are working with a dfx.json project that defines a project-specific local network. See [Local Server Configuration](dfx-start.mdx#local-server-configuration) for details. +You can run this command from any directory unless you are working with a `dfx.json` project that defines a project-specific local network. See [local server configuration](dfx-start.mdx#local-server-configuration) for details. ## Basic usage @@ -27,16 +27,19 @@ If the local development environment is running in a current shell rather than i The current process identifier (`pid`) for the canister execution environment process started by `dfx` is recorded in a file named `pid`. You can view the process identifier before running the `dfx stop` command by running one of the following commands: For a project-specific local network: + ``` bash cat .dfx/network/local/pid ``` -For the shared local network, on Linux: +For the shared local network on Linux: + ``` bash cat $HOME/.local/share/dfx/network/local/pid ``` -For the shared local network, on MacOS: +For the shared local network on MacOS: + ``` bash cat '$HOME/Library/Application Support/org.dfinity.dfx/network/local/pid' ``` @@ -47,7 +50,7 @@ This command displays a process identifier similar to the following: 1896 ``` -If you are still having trouble with a persistent service running after attempting to stop, you can terminate all running jobs with: +If you are still having trouble with a persistent service running after attempting to stop, you can terminate all running processes with: ``` bash dfx killall diff --git a/docs/cli-reference/dfx-upgrade.mdx b/docs/cli-reference/dfx-upgrade.mdx index 329eb4a331..b450d91414 100644 --- a/docs/cli-reference/dfx-upgrade.mdx +++ b/docs/cli-reference/dfx-upgrade.mdx @@ -4,6 +4,6 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; -> **NOTE**: The upgrade command has been removed. Please use the [dfx version manager][dfxvm] instead. +The upgrade command has been removed. Please use the [dfx version manager][dfxvm] instead. [dfxvm]: https://github.com/dfinity/dfxvm diff --git a/docs/cli-reference/dfx-wallet.mdx b/docs/cli-reference/dfx-wallet.mdx index 19cd69bff2..dc96b23793 100644 --- a/docs/cli-reference/dfx-wallet.mdx +++ b/docs/cli-reference/dfx-wallet.mdx @@ -6,8 +6,9 @@ import { MarkdownChipRow } from "/src/components/Chip/MarkdownChipRow"; Use the `dfx wallet` command with subcommands and flags to manage the cycles wallets of your identities and to send cycles to the wallets of other account cycles wallet canisters. -The basic syntax for running the `dfx wallet` commands is: +## Basic usage +The basic syntax for running the `dfx wallet` commands is: ```bash dfx wallet [option] [flag] @@ -28,17 +29,17 @@ For reference information and examples that illustrate using `dfx wallet` comman ---------|----------------------------------- |[`add-controller`](#dfx-wallet-add-controller) | Add a controller using the selected identity's principal. | |[`addresses`](#dfx-wallet-addresses)|Displays the address book of the cycles wallet.| -|[`authorize`](#dfx-wallet-authorize)|Authorize a custodian by principal for the selected identity's cycles wallet| +|[`authorize`](#dfx-wallet-authorize)|Authorize a custodian by principal for the selected identity's cycles wallet.| |[`balance`](#dfx-wallet-balance)|Displays the cycles wallet balance of the selected identity. |[`controllers`](#dfx-wallet-controllers) |Displays a list of the selected identity's cycles wallet controllers. |[`custodians`](#dfx-wallet-custodians) |Displays a list of the selected identity's cycles wallet custodians. |[`deauthorize`](#dfx-wallet-deauthorize) | Deauthorize a cycles wallet custodian using the custodian's principal. -|`help`|Displays a usage message and the help of the given subcommand(s). +|`help`|Displays a usage message and the help info for the given subcommand(s). |[`name`](#dfx-wallet-name) |Returns the name of the cycles wallet if you've used the `dfx wallet set-name` command. |[`remove-controller`](#dfx-wallet-remove-controller) |Removes a specified controller from the selected identity's cycles wallet. |[`send`](#dfx-wallet-send) |Sends a specified amount of cycles from the selected identity's cycles wallet to another canister. |[`set-name`](#dfx-wallet-set-name) |Specify a name for your cycles wallet. -|[`upgrade`](#dfx-wallet-upgrade) |Upgrade the cycles wallet's Wasm module to the current Wasm bundled with DFX. +|[`upgrade`](#dfx-wallet-upgrade) |Upgrade the cycles wallet's Wasm module to the current Wasm bundled with `dfx`. ## Using your wallet @@ -47,7 +48,7 @@ After you have used the `dfx identity deploy-wallet` command to create a cycles ## dfx wallet add-controller -Use the `dfx wallet add-controller` to add a controller to the wallet. An identity assigned the role of Controller has the most privileges and can perform the following actions on the selected identity's cycles wallet: +Use the `dfx wallet add-controller` to add a controller to the wallet. An identity assigned the role of controller has the most privileges and can perform the following actions on the selected identity's cycles wallet: * Rename the cycles wallet. @@ -70,7 +71,6 @@ A controller is also a custodian and can perform the following actions associate ### Basic usage - ``` dfx wallet add-controller [option] [flag] ``` @@ -82,7 +82,7 @@ You can use the following options with the `dfx canister call` command. |Option |Description| --------|------------| -|`--network ` |Specifies the environment (e.g., Internet Computer or testnet) of the controller you want to add. +|`--network` |Override the environment to connect to. By default, the local development environment is used. A valid URL (starting with `http:` or `https:`) can be specified here, e.g. "http://localhost:12345/" is a valid network name. ### Arguments @@ -110,7 +110,7 @@ Added b5quc-npdph-l6qp4-kur4u-oxljq-7uddl-vfdo6-x2uo5-6y4a6-4pt6v-7qe as a contr ## dfx wallet addresses -Use the `dfx wallet addresses` command to display the wallet's address book.The address entries contain the principal and `role` (`Contact`, `Custodian`, or `Controller`), and might contain a `name`, and `kind` (`Unknown`, `User`, or `Canister`) associated with the address. +Use the `dfx wallet addresses` command to display the wallet's address book. The address entries contain the principal and `role` (`Contact`, `Custodian`, or `Controller`), and might contain a `name`, and `kind` (`Unknown`, `User`, or `Canister`) associated with the address. ### Basic usage @@ -148,7 +148,6 @@ Use the `dfx wallet authorize` command to authorize a custodian for the wallet. ### Basic usage - ``` dfx wallet authorize [flag] ``` @@ -163,7 +162,7 @@ Use the following necessary argument with the `dfx wallet authorize` command. ### Example -For example, to add alice_auth as a custodian, specify her principal in the following command: +For example, to add `alice_auth` as a custodian, specify the identity's principal in the following command: ``` dfx wallet authorize dheus-mqf6t-xafkj-d3tuo-gh4ng-7t2kn-7ikxy-vvwad-dfpgu-em25m-2ae @@ -181,7 +180,6 @@ Use the `dfx wallet balance` command to display the balance of the cycles wallet ### Basic usage - ``` dfx wallet balance ``` @@ -267,11 +265,10 @@ hpnmi-qgxsv-tgecj-hmjyn-gmfft-vbego-lpcax-ou4ld-oh7kr-l3nu2-yae Use the `dfx wallet deauthorize` command to remove a custodian from the cycles wallet. -NOTE: that this will also remove the role of controller if the custodian is also a controller. +NOTE: This will also remove the role of controller if the custodian is also a controller. ### Basic usage - ``` dfx wallet deauthorize [flag] ``` @@ -287,7 +284,7 @@ Use the following necessary argument with the `dfx wallet deauthorize` command. ### Example -For example, to remove "alice_auth" as a custodian, specify her principal in the following command: +For example, to remove `alice_auth` as a custodian, specify her principal in the following command: ``` @@ -313,10 +310,10 @@ dfx wallet name [flag] ### Example -If you have named your cycles wallet "Terrances_wallet", then the command would return the following: +If you have named your cycles wallet "my_wallet", then the command would return the following: ``` -Terrances_wallet +my_wallet ``` ## dfx wallet remove-controller @@ -334,20 +331,22 @@ dfx wallet remove-controller [flag] Use the following necessary argument with the `dfx wallet remove-controller` command. -|Argument |Description - -|`` | Specify the principal of the controller you want to remove. +|Argument |Description | +|---------|-----------| +|`` | Specify the principal of the controller you want to remove. | ### Example -For example, to remove alice_auth as a controller, specify her principal in the following command: +For example, to remove `alice_auth` as a controller, specify the identity's principal in the following command: ``` dfx wallet remove-controller dheus-mqf6t-xafkj-d3tuo-gh4ng-7t2kn-7ikxy-vvwad-dfpgu-em25m-2ae ``` + The command outputs something similar to the following: + ``` Removed dheus-mqf6t-xafkj-d3tuo-gh4ng-7t2kn-7ikxy-vvwad-dfpgu-em25m-2ae as a controller. ``` @@ -369,7 +368,7 @@ You can use the following option with the `dfx wallet send` command. |Option |Description -----------|---------- -|`--network` |Override the environment to connect to. By default, the local development environment is used. A valid URL (starting with `http:` or `https:`) can be specified here. E.g. "http://localhost:12345/" is a valid network name. +|`--network` |Override the environment to connect to. By default, the local development environment is used. A valid URL (starting with `http:` or `https:`) can be specified here, e.g. "http://localhost:12345/" is a valid network name. ### Arguments @@ -377,21 +376,21 @@ You must specify the following arguments for the `dfx wallet send` command. |Argument |Description -----------|---------- -|`` |Specify the destination canister using its Canister ID. +|`` |Specify the destination canister using its canister ID. |`` |Specify the number of cycles to send. ### Examples Send cycles from the selected identity's cycles wallet to another cycles wallet. -For example, to send 2,000,000,000 cycles from the cycles wallet of the selected identity, ``, to the cycles wallet of the destination identity, `` with a wallet address `r7inp-6aaaa-aaaaa-aaabq-cai`, run the following command: +For example, to send 2_000_000_000 cycles from the cycles wallet of the selected identity, ``, to the cycles wallet of the destination identity, `` with a wallet address `r7inp-6aaaa-aaaaa-aaabq-cai`, run the following command: ``` dfx wallet send r7inp-6aaaa-aaaaa-aaabq-cai 2000000000 ``` -If the transfer is successful, the command does not displays any output. +If the transfer is successful, the command does not display any output. ## dfx wallet set-name @@ -400,7 +399,7 @@ Use the `dfx wallet set-name` command to assign a name to the selected identity' ### Basic usage ``` - dfx wallet set-name [flag] +dfx wallet set-name [flag] ``` ### Arguments @@ -414,25 +413,25 @@ You must specify the following arguments for the `dfx wallet set-name` command. ### Example -If you want to set the name of the current identity's cycles wallet to "Terrances_wallet" you can run the following command: +If you want to set the name of the current identity's cycles wallet to "my_wallet" you can run the following command: ``` -dfx wallet set-name Terrances_wallet +dfx wallet set-name my_wallet ``` ## dfx wallet upgrade -Use the `dfx wallet upgrade` command to upgrade the cycle wallet's Wasm module to the current Wasm bundled with DFX. +Use the `dfx wallet upgrade` command to upgrade the cycle wallet's Wasm module to the current Wasm bundled with `dfx`. ### Basic usage - ``` - dfx wallet upgrade [flag] +dfx wallet upgrade [flag] ``` ### Example + To upgrade the Wasm module to the latest version, run the following command: ```