From 88894024905f68939dc3e7a7aec91009770b8408 Mon Sep 17 00:00:00 2001 From: daeMOn Date: Fri, 9 Jul 2021 16:08:50 +0200 Subject: [PATCH] docs: stargate updates (#136) --- docs/docs/building.md | 84 ++++++++++++++------------------ docs/docs/cli-introduction.md | 9 ++++ docs/docs/cli-keys.md | 29 +++++++---- docs/docs/cli-tokens.md | 57 ++++++++++++++-------- docs/docs/delegator-guide-cli.md | 33 ++++++------- docs/docs/docker-images.md | 5 +- docs/docs/faucet.md | 79 ++---------------------------- docs/docs/governance.md | 16 +++--- docs/docs/joining-a-testnet.md | 10 ---- docs/docs/networks.md | 37 +++++++------- docs/docs/single-node-network.md | 12 +---- docs/docs/validators/setup.md | 30 ++++++------ docs/docs/versions.md | 3 +- 13 files changed, 168 insertions(+), 236 deletions(-) diff --git a/docs/docs/building.md b/docs/docs/building.md index 5e576c67..51525cb4 100644 --- a/docs/docs/building.md +++ b/docs/docs/building.md @@ -2,73 +2,63 @@ ## Prerequisites -- Go 1.14+ (installation instructions available [here](https://golang.org/dl/)) +- Go 1.16+ (installation instructions available [here](https://golang.org/dl/)) +- Packages: `make`, `gcc` (on ubunty, install them with `sudo apt-get update && sudo apt-get install -y make gcc`) -### Ubuntu 20.04 / Debian 10 +## Building the code -```bash -# Run the following command if using Ubuntu -sudo apt-get install libgmp-dev swig - -# Download and install the MCL libraries -cd ~ -wget https://github.com/herumi/mcl/archive/v1.05.tar.gz -tar xvf v1.05.tar.gz -cd mcl-1.05 -sudo make install -sudo ldconfig +Download the latest released version from github and build the project using the following commands: + +``` +git clone https://github.com/fetchai/fetchd.git && cd fetchd ``` -### MacOS +Then select the particular tag version you want to build, ie: ```bash -# Run the following command if using OS X -brew install swig gmp - -# Download and install the MCL libraries -cd ~ -wget https://github.com/herumi/mcl/archive/v1.05.tar.gz -tar xvf v1.05.tar.gz -cd mcl-1.05 -sudo make install -sudo ldconfig +git checkout v0.8.1 ``` -## Building the code - -Download the latest released version from github and build the project using the following commands: - - git clone https://github.com/fetchai/fetchd.git && cd fetchd - Then build the code with the command: - make build - -This will generate the following binaries: +```bash +make build +``` -- `./build/fetchcli` - This is the command line client that is useful for interacting with the network -- `./build/fetchd` - This is the block chain node daemon and can be configured to join the network +This will generate the `./build/fetchd` binary. For non-developer users we recommend that the user installs the binaries into their system. This can be done with the following command: - sudo make install - -This will install the binaries in the directory specified by your `$GOBIN` environment variable. - -### Boost Dependencies (Only for beaconworld versions `v0.5x` and `v0.6.x`) - -Currently the code requires that the user compiles the code with at least version 1.67 of Boost Serialisation library. Failure to do so will mean that users will not be able to sync with the blockchain. This limitation will be resolved in the near future (with the Boost dependency being removed completely). +```bash +make install +``` -To verify which libraries you have linked against use the following commands +This will install the binaries in the directory specified by your `$GOBIN` environment variable (default to `~/go/bin`). -**Ubuntu 20.04 / Debian 10** ```bash -ldd ./build/fetchd +which fetchd ``` -**MacOS** +This should return a path such as `~/go/bin/fetchd` (might be different depending on your actual go installation). + +> If you get no output, or an error such as `which: no fetchd in ...`, possible cause can either be that `make install` failed with some errors or that your go binary folder (default: ~/go/bin) is not in your `PATH`. +> +> To add the ~/go/bin folder to your PATH, add this line at the end of your ~/.bashrc: +>``` +>export PATH=$PATH:~/go/bin +>``` +> +>and reload it with: +> +>``` +>source ~/.bashrc +>``` + +You can also verify that you are running the correct version ```bash -otool -L ./build/fetchd +fetchd version ``` + +This should print a version number that must be compatible with the network you're connecting to (see the [network page](../networks/) for the list of supported versions per network). \ No newline at end of file diff --git a/docs/docs/cli-introduction.md b/docs/docs/cli-introduction.md index 4581eadb..17518de2 100644 --- a/docs/docs/cli-introduction.md +++ b/docs/docs/cli-introduction.md @@ -16,6 +16,15 @@ fetchcli config trust-node false fetchcli config node https://rpc-fetchhub.fetch-ai.com:443 ``` +### Connecting to stargateworld network + +On Stargate networks, the `fetchcli` binary **does not exists anymore**. Instead, every commands are now provided by `fetchd`. Beside this, the syntax is generaly the same. To connect to the stargateworld network run the following configuration steps: + +```bash +fetchd config chain-id stargateworld-1 +fetchd config node https://rpc-stargateworld.fetch-ai.com:443 +``` + ### Connecting to Agent Land network To connect to the agent land network run the following configuration steps: diff --git a/docs/docs/cli-keys.md b/docs/docs/cli-keys.md index 415ec852..a4f0dfd6 100644 --- a/docs/docs/cli-keys.md +++ b/docs/docs/cli-keys.md @@ -7,7 +7,7 @@ Managing your keys is an essential part of working with the Ledger, since all in To create a new local key you need run the following command: ```bash -fetchcli keys add +fetchd keys add ```
@@ -15,7 +15,7 @@ fetchcli keys add

These keys are stored locally on your system. By default, these keys will be stored in the OS level keychain, however, in general these keys are considered less secure than using a hardware device

-After running the command `fetchcli` will print out a summary of the new key. An example of this output is shown below: +After running the command `fetchd` will print out a summary of the new key. An example of this output is shown below: ```text - name: test @@ -34,7 +34,7 @@ This will be followed by a 24-word mnemonic that can be used to re-generate the A common operation that you will want to do is to lookup the address for a specified key. This can be done quickly using the following command: ```bash -fetchcli keys show -a +fetchd keys show -a ``` An example of the expected output is shown below: @@ -46,7 +46,7 @@ fetch142tawq2rj397mctc3jtw9dfzf03ns0ze4swat0 A less common operation, but still useful, would be to lookup the public key for a specified key. The can be achieved with the following command: ```bash -fetchcli keys show -p +fetchd keys show -p ``` An example of the expected output is shown below: @@ -60,7 +60,7 @@ fetchpub1addwnpepqvtmze0ekffynnjx9n85g6sexzl49ze2vpgc2f52fteyyghjtvvqw682nkx To lookup more detailed information for all keys on your system use the following command: ```bash -fetchcli keys list +fetchd keys list ``` This will output all of your keys information in a yaml format that is similar to the one generated when you first created the key. @@ -75,6 +75,17 @@ This will output all of your keys information in a yaml format that is similar t pubkeys: [] ``` +## Recovering a key + +You can import a key from a 24-word mnemonic by running: + +```bash +fetchd keys add --recover +> Enter your bip39 mnemonic + +``` +You'll be prompted to enter the mnemonic phrase, and it will then print the matching address and key details as when creating a new key. + ## Hardware Wallets ### Setup @@ -87,14 +98,14 @@ We recommend hardware wallets as a solution for managing private keys. The Fetch ### Adding a new key -In order to use the hardware wallet address with the cli, the user must first add it via `fetchcli`. This process only records the public information about the key. +In order to use the hardware wallet address with the cli, the user must first add it via `fetchd`. This process only records the public information about the key. To import the key first plug in the device and enter the device pin. Once you have unlocked the device navigate to the Cosmos app on the device and open it. To add the key use the following command: ```bash -fetchcli keys add --ledger --index 0 +fetchd keys add --ledger --index 0 ```
@@ -121,13 +132,13 @@ It is also possible to import private keys from the agent framework. For example To import this key into the local keychain simply run the following command: ```bash -fetchcli keys import --agent-raw-key +fetchd keys import --agent-raw-key ``` For example: ```bash -fetchcli keys import --agent-raw-key agent /home/user/fetchai_private_key.txt +fetchd keys import --agent-raw-key agent /home/user/fetchai_private_key.txt ```
diff --git a/docs/docs/cli-tokens.md b/docs/docs/cli-tokens.md index 6e7431df..fabe30c7 100644 --- a/docs/docs/cli-tokens.md +++ b/docs/docs/cli-tokens.md @@ -2,22 +2,21 @@ ## Querying your balance -Once the wasm is configured for the desired [network](../cli-introduction/). The user can query there balance using the following command: +Once `fetchd` is configured for the desired [network](../cli-introduction/). The user can query there balance using the following command: ```bash -fetchcli query account fetch1akvyhle79nts4rwn075t85xrwmp5ysuqynxcn4 +fetchd query bank balances fetch1akvyhle79nts4rwn075t85xrwmp5ysuqynxcn4 ``` If the address exists on the network then the user will expect to see an output in the following form: ```text - address: fetch1akvyhle79nts4rwn075t85xrwmp5ysuqynxcn4 - coins: - - denom: atestfet - amount: "1000000000000000000" - public_key: "" - account_number: 20472 - sequence: 0 +balances: +- amount: "8000000000000000000" + denom: atestfet +pagination: + next_key: null + total: "0" ``` @@ -26,19 +25,19 @@ If the address exists on the network then the user will expect to see an output To send funds from one address to another address then you would use the `tx send` subcommand. As shown below: ```bash -./build/fetchcli tx send +fetchd tx bank send ``` In a more concrete example if the user wanted to send `100atestfet` from `main` key/address to `fetch106vm9q6ezu9va7v7e0cvq0nedc54egjm692fcp` then the following command would be used. ```bash -./build/fetchcli tx send main fetch106vm9q6ezu9va7v7e0cvq0nedc54egjm692fcp 100atestfet +fetchd tx bank send main fetch106vm9q6ezu9va7v7e0cvq0nedc54egjm692fcp 100atestfet ``` When you run the command you will get a similar output and prompt. The user can check the details of the transfer and then press 'y' to confirm the transfer. ```text -{"chain_id":"agent-land","account_number":"20472","sequence":"0","fee":{"amount":[],"gas":"200000"},"msgs":[{"type":"cosmos-sdk/MsgSend","value":{"from_address":"fetch1akvyhle79nts4rwn075t85xrwmp5ysuqynxcn4","to_address":"fetch106vm9q6ezu9va7v7e0cvq0nedc54egjm692fcp","amount":[{"denom":"atestfet","amount":"100"}]}}],"memo":""} +{"body":{"messages":[{"@type":"/cosmos.bank.v1beta1.MsgSend","from_address":"fetch12cjntwl32dry7fxck8qlgxq6na3fk5juwjdyy3","to_address":"fetch1hph8kd54gl6qk0hy5rl08qw9gcr4vltmk3w02v","amount":[{"denom":"atestfet","amount":"100"}]}],"memo":"","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""}},"signatures":[]} confirm transaction before signing and broadcasting [y/N]: y ``` @@ -46,16 +45,34 @@ confirm transaction before signing and broadcasting [y/N]: y Once the transfer has been made a summary is presented to the user. An example is shown below: ```text -height: 0 -txhash: CA7C2C842F8F577E9621C2B23A016D93B979AC1A45015807799C5AD959503FA4 -codespace: "" code: 0 +codespace: "" data: "" -rawlog: '[]' -logs: [] +gas_used: "0" +gas_wanted: "0" +height: "0" info: "" -gaswanted: 0 -gasused: 0 +logs: [] +raw_log: '[]' +timestamp: "" tx: null +txhash: 77C7382A0B1B9FE39257A6C16C7E3169A875CB3A87F2CE9D947D7C1335B53E76 +``` + +On failure, the response will have a non zero code, as well as some logs under the `raw_log` key: + +```text +code: 4 +codespace: sdk +data: "" +gas_used: "0" +gas_wanted: "0" +height: "0" +info: "" +logs: [] +raw_log: 'signature verification failed; please verify account number (5815) and chain-id + (stargateworld-1): unauthorized' timestamp: "" -``` \ No newline at end of file +tx: null +txhash: 23701B052B423D63EB4AC94773B5B8227B03A576692A57999E92F2554F2372D4 +``` diff --git a/docs/docs/delegator-guide-cli.md b/docs/docs/delegator-guide-cli.md index ce729bc7..e2a9743b 100644 --- a/docs/docs/delegator-guide-cli.md +++ b/docs/docs/delegator-guide-cli.md @@ -1,7 +1,6 @@ # CLI - Delegator guide - ## Querying the state ### Querying the current staking holdings of the validators @@ -9,10 +8,10 @@ The following command can be used to retrieve the current staking holdings of all validators: ```bash -fetchcli query staking validators +fetchd query staking validators ``` -On `beacon-world` network, this will produce an output similar to the following, describing the status of all the existing validators: +On `stargateworld` network, this will produce an output similar to the following, describing the status of all the existing validators: ```text - | @@ -67,7 +66,7 @@ On `beacon-world` network, this will produce an output similar to the following, To obtain the same informations for a single validator, use the following command, providing the `operatoraddress` of the validator. ```bash -fetchcli query staking validator fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w +fetchd query staking validator fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w ``` A delegator will be particularly interested in the following keys: @@ -82,10 +81,10 @@ A delegator will be particularly interested in the following keys: From a validator address, we can retrieve the list of delegations it received: ```bash -fetchcli query staking delegations-to fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w +fetchd query staking delegations-to fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w ``` -Here is a sample of delegations `validator5` received on `beacon-world`: +Here is a sample of delegations `validator5` received on `stargateworld`: ```text - delegation: @@ -111,13 +110,13 @@ Delegators can choose to redelegate the tokens they already delegated from one v To obtains the list of redelegations made from a validator, use the following command: ```bash -fetchcli query staking redelegations-from fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w +fetchd query staking redelegations-from fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w ``` Which produce an output similar to the following, where delegator `fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m` issued 2 redelegations from `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w` to `fetchvaloper122veneudkzyalay6gusvrhhpp0560mparpanvu`: ```text -fetchcli query staking redelegations-from fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w +fetchd query staking redelegations-from fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w - redelegation: delegator_address: fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m validator_src_address: fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w @@ -141,7 +140,7 @@ fetchcli query staking redelegations-from fetchvaloper1z72rph6l5j6ex83n4urputyka Similarly, the list of redelegations issued by a delegator can be obtained with the following: ```bash -fetchcli query staking redelegations fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m +fetchd query staking redelegations fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m ``` ### Query the user rewards @@ -151,10 +150,10 @@ After having delegated some tokens to a validator, the user is eligible to a sha To retrieve all the outstanding rewards for an address, issue the following command: ```bash -fetchcli query distribution rewards fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m +fetchd query distribution rewards fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m ``` -This address having delegated tokens to 2 validators on `beacon-world`, it produces the following output: +This address having delegated tokens to 2 validators on `stargateworld`, it produces the following output: ```text rewards: @@ -174,7 +173,7 @@ total: Rewards can also be filtered for a given validator, like `validator5` here: ```bash -fetchcli query distribution rewards fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w +fetchd query distribution rewards fetch15fn3meky8ktfry3qm73xkpjckzw4dazxpfx34m fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w ``` we now get only the reward from this validator: @@ -191,7 +190,7 @@ we now get only the reward from this validator: To delegate `1000000 atestfet` tokens to the `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w` validator from the account `myKey`, the following command can be used: ```bash -fetchcli tx staking delegate fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w 1000000atestfet --from myKey +fetchd tx staking delegate fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w 1000000atestfet --from myKey ``` This will prompt for confirmation before issuing a transaction. After the transaction get processed, it should appear under the delegations of the `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w` validator. @@ -208,7 +207,7 @@ Redelegating tokens allows to transfer already delegated tokens from one validat From the above example where we delegated `1000000 atestfet` to `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w`, we can now redelegate parts or all of those tokens to another validator. For example, we redelegate `400000 atestfet` from `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w` to `fetchvaloper122veneudkzyalay6gusvrhhpp0560mparpanvu` with the following command: ```bash -fetchcli tx staking redelegate fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w fetchvaloper122veneudkzyalay6gusvrhhpp0560mparpanvu 400000atestfet --from myKey +fetchd tx staking redelegate fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w fetchvaloper122veneudkzyalay6gusvrhhpp0560mparpanvu 400000atestfet --from myKey ``` This will prompt for confirmation and issue a new transaction once accepted. @@ -224,7 +223,7 @@ Now thoses `400000 atestfet` we redelegated can't be redelegated anymore for 21 At any time, we can transfer parts or all of our delegated tokens back to our account: ```bash -fetchcli tx staking unbond fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w 300000atestfet --from myKey +fetchd tx staking unbond fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w 300000atestfet --from myKey ``` Once again, this will prompt for confirmation and issue a transaction, initiating the transfer of `300000 atestfet` from our stake on `fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w` validator back to our account. Those tokens will then be available **after a 21 days period** (the exact date can be found by querying the redelegation transaction, under the `completion_time` key). @@ -234,7 +233,7 @@ Once again, this will prompt for confirmation and issue a transaction, initiatin In order to transfer rewards to the wallet, the following command can be used: ```bash -fetchcli tx distribution withdraw-rewards fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w --from myKey +fetchd tx distribution withdraw-rewards fetchvaloper1z72rph6l5j6ex83n4urputykawcqg6t98xul2w --from myKey ``` It requires the validator address from where the reward is withdrawn, and the name of the account private key having delegated tokens to the validator. @@ -242,7 +241,7 @@ It requires the validator address from where the reward is withdrawn, and the na When having delegated tokens to multiple validators, all rewards can be claimed in a single command: ```bash -fetchcli tx distribution withdraw-all-rewards --from myKey +fetchd tx distribution withdraw-all-rewards --from myKey ``` The rewards then appears on the account as soon as the transaction is processed. diff --git a/docs/docs/docker-images.md b/docs/docs/docker-images.md index a94c8dd6..d7a79f71 100644 --- a/docs/docs/docker-images.md +++ b/docs/docs/docker-images.md @@ -8,9 +8,8 @@ For every Fetchd release a corresponding docker images is released. The full lis Current Versions: -* [0.7.2, 0.7](https://github.com/fetchai/fetchd/blob/v0.7.2/Dockerfile) (used for fetchhub mainnetv2 networks) -* [0.6.4, 0.6](https://github.com/fetchai/fetchd/blob/v0.6.4/Dockerfile) (used for beaconworld test networks) -* [0.2.7, 0.2](https://github.com/fetchai/fetchd/blob/v0.2.7/Dockerfile) (used for agentworld test networks) +* [0.8.x, 0.8](https://github.com/fetchai/fetchd/blob/release/v0.8.x/Dockerfile) (used for Stargate networks) +* [0.7.x, 0.7](https://github.com/fetchai/fetchd/blob/release/v0.7.x/Dockerfile) (used for Launchpad networks) # Quick Reference diff --git a/docs/docs/faucet.md b/docs/docs/faucet.md index f4fc950f..0e4b35fd 100644 --- a/docs/docs/faucet.md +++ b/docs/docs/faucet.md @@ -1,82 +1,9 @@ # Token Faucet -For the main agent land network we have a simple token faucet implemented to allow users of the network to get started quickly. +For our test networks, we have a simple token faucet implemented to allow users of the network to get started quickly. You can send it an account address, and it will transfer some test token on it. Token Faucets are network specific, depending on the network type they may or may not be deployed. Please check the [networks](../networks/) page for specific details. -The Token Faucet itself is a HTTP REST API and interaction is shown below: +The Token Faucet itself is available from the network block explorer (`GET FUNDS` button on the homepage). -## Making a token claim request - -A user must first submit a token claim request to the faucet. This request can be either URL encoded or JSON encoded. Both examples are shown below: - -URL: `POST /claim/requests` - -### URL Encoded - -**Headers** - -The request must include the following headers: - -``` -'Content-Type: application/x-www-form-urlencoded -``` - -**cURL example** - -```bash -curl -d 'Address=fetch1xqqftqp8ranv2taxsx8h594xprfw3qxl7j3ra2' -H "Content-Type: application/x-www-form-urlencoded" -X POST http://127.0.0.1:5000/claim/requests -``` - -### JSON Encoded - -**Headers** - -The request must include the following headers: - -``` -'Content-Type: application/json -``` - -**cURL example** - -```bash -curl -d '{"Address":"fetch1xqqftqp8ranv2taxsx8h594xprfw3qxl7j3ra2"}' -H "Content-Type: application/json" -X POST http://127.0.0.1:5000/claim/requests -``` - -### Response - -In either submission case, upon successful register the API will respond with the request UID - -```json -{ - "uid": "123e4567-e89b-12d3-a456-426614174000" -} -``` - -## Querying the status of a token claim request - -To query the status of the your token claim request the following API can be used - -URL: `GET /claim/requests/` - -**cURL example** - -```bash -curl http://127.0.0.1:5000/claim/requests/1a472a27-7225-4409-92be-4efd3beed995 -``` - -This will respond with the status of the request claim. If the claim was successful then JSON response will resemble the following: - -```json -{ - "txDigest": "9CA3A7D3614A37C1BB2EA6B746B402CF68D3E5A4CEBFFE1D7ADF212876DAE70B", - "status": "completed", - "statusCode": 20, - "lastUpdated": "2020-08-11T09:48:04.596522" -} -``` - -## Rate limiting - -To prevent malicious actors, this API is rate limited and will block requests if the limits are passed. In this case the user must wait and then try again. +Enter your `fetch...` address in the popup and click *Add funds* button. Wait a few blocks for the transaction to be processed, and you should see it appear along with some funds on your account. diff --git a/docs/docs/governance.md b/docs/docs/governance.md index 2953b301..0c5bff46 100644 --- a/docs/docs/governance.md +++ b/docs/docs/governance.md @@ -7,13 +7,13 @@ In order to be able to take part in the governance you either need to be running In order to delegate stake to a validator the following command should be used: ```bash -fetchcli tx staking delegate --from +fetchd tx staking delegate --from ``` Where the `` begins with the prefix `fetchvaloper1...` and the `` field contains the currency denomination. For example: ```bash -fetchcli tx staking delegate fetchvaloper1cct4fhhksplu9m9wjljuthjqhjj93z0s97p3g7 1000atestfet --from agent +fetchd tx staking delegate fetchvaloper1cct4fhhksplu9m9wjljuthjqhjj93z0s97p3g7 1000atestfet --from agent ``` ## Proposals Overview @@ -55,17 +55,17 @@ It is always recommended that the description of a text proposal has a link to a Once the user has created the JSON file, to generate the text propsal on chain run the following command: -`fetchcli tx gov submit-proposal --proposal proposal.json --from ` +`fetchd tx gov submit-proposal --proposal proposal.json --from ` ## Increasing the deposit for a proposal If a user wants to increase the deposit of a proposal they would run the following command: -`fetchcli tx gov deposit 100atestfet --from ` +`fetchd tx gov deposit 100atestfet --from ` For example: -`fetchcli tx gov deposit 2 100atestfet --from validator` +`fetchd tx gov deposit 2 100atestfet --from validator` ## Listing current proposals @@ -73,17 +73,17 @@ Current proposals are visible from the block explorer and using the CLI. To get the list of current proposals and their corresponding *proposal-ids* the run the following command: -`fetchcli query gov proposals` +`fetchd query gov proposals` ## Voting on a proposal To vote for a proposal run the following command -`fetchcli tx gov vote