From 431ee2c0a695eb4b1131296cf13cd87c624560c4 Mon Sep 17 00:00:00 2001 From: Kimura Yu <33382781+KimuraYu45z@users.noreply.github.com> Date: Mon, 8 Mar 2021 18:16:29 +0900 Subject: [PATCH] change dir '.gaiad' to '.gaia' (#690) --- Dockerfile | 4 ++-- contrib/Dockerfile.test | 4 ++-- docs/gaia-tutorials/deploy-testnet.md | 8 +++---- docs/gaia-tutorials/join-mainnet.md | 12 +++++----- docs/gaia-tutorials/join-testnet.md | 2 +- docs/gaia-tutorials/upgrade-node.md | 4 ++-- docs/migration/cosmoshub-2.md | 10 ++++----- docs/migration/cosmoshub-3.md | 22 +++++++++---------- docs/migration/cosmoshub-3[ES_es].md | 16 +++++++------- docs/migration/cosmoshub-3[KR_kr].md | 16 +++++++------- docs/resources/genesis.md | 4 ++-- docs/translations/cn/deploy-testnet.md | 8 +++---- docs/translations/cn/genesis.md | 4 ++-- docs/translations/cn/join-mainnet.md | 12 +++++----- docs/translations/cn/join-testnet.md | 2 +- .../cn/validators/validator-setup.md | 2 +- docs/translations/es/join-mainnet.md | 12 +++++----- docs/translations/kr/deploy-testnet.md | 8 +++---- docs/translations/kr/genesis.md | 4 ++-- docs/translations/kr/join-mainnet.md | 12 +++++----- docs/translations/kr/join-testnet.md | 12 +++++----- docs/translations/kr/upgrade-node.md | 4 ++-- .../kr/validators/validator-setup.md | 10 ++++----- docs/validators/kms/kms_ledger.md | 4 ++-- .../ansible/roles/clear-config/tasks/main.yml | 7 ++---- .../roles/extract-config/tasks/main.yml | 4 ++-- .../roles/setup-fullnodes/tasks/main.yml | 6 ++--- .../roles/setup-validators/tasks/main.yml | 10 ++++----- .../roles/upgrade-gaiad/tasks/main.yml | 4 ++-- sims.mk | 8 +++---- 30 files changed, 116 insertions(+), 119 deletions(-) diff --git a/Dockerfile b/Dockerfile index 5f9cf8b9951..c667ef9ac82 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,7 +1,7 @@ # Simple usage with a mounted data directory: # > docker build -t gaia . -# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaiad:/gaia/.gaiad -v ~/.gaiacli:/gaia/.gaiacli gaia gaiad init -# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaiad:/gaia/.gaiad -v ~/.gaiacli:/gaia/.gaiacli gaia gaiad start +# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaia:/gaia/.gaia gaia gaiad init +# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaia:/gaia/.gaia gaia gaiad start FROM golang:1.15-alpine AS build-env # Set up dependencies diff --git a/contrib/Dockerfile.test b/contrib/Dockerfile.test index a2b3125d9ed..c9643a8cea0 100644 --- a/contrib/Dockerfile.test +++ b/contrib/Dockerfile.test @@ -1,7 +1,7 @@ # Simple usage with a mounted data directory: # > docker build -t gaia . -# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaiad:/root/.gaiad -v ~/.gaiacli:/root/.gaiacli gaia gaiad init -# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaiad:/root/.gaiad -v ~/.gaiacli:/root/.gaiacli gaia gaiad start +# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaia:/root/.gaia gaia gaiad init +# > docker run -it -p 46657:46657 -p 46656:46656 -v ~/.gaia:/root/.gaia gaia gaiad start FROM golang:1.15-alpine AS build-env # Set up dependencies diff --git a/docs/gaia-tutorials/deploy-testnet.md b/docs/gaia-tutorials/deploy-testnet.md index 40a03274256..bfbd9ea5619 100644 --- a/docs/gaia-tutorials/deploy-testnet.md +++ b/docs/gaia-tutorials/deploy-testnet.md @@ -18,10 +18,10 @@ Supporting code can be found in the [networks directory](https://github.com/cosm In case you need to use or deploy gaia as a container you could skip the `build` steps and use the official images, \$TAG stands for the version you are interested in: -- `docker run -it -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad init` -- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad start` +- `docker run -it -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad init` +- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad start` - ... -- `docker run -it -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad version` +- `docker run -it -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad version` The same images can be used to build your own docker-compose stack. @@ -61,7 +61,7 @@ gaiad collect-gentxs gaiad start ``` -This setup puts all the data for `gaiad` in `~/.gaiad`. You can examine the genesis file you created at `~/.gaiad/config/genesis.json`. With this configuration `gaiad` is also ready to use and has an account with tokens (both staking and custom). +This setup puts all the data for `gaiad` in `~/.gaia`. You can examine the genesis file you created at `~/.gaia/config/genesis.json`. With this configuration `gaiad` is also ready to use and has an account with tokens (both staking and custom). ## Multi-node, Local, Automated Testnet diff --git a/docs/gaia-tutorials/join-mainnet.md b/docs/gaia-tutorials/join-mainnet.md index b3995d1bf81..34378e43452 100644 --- a/docs/gaia-tutorials/join-mainnet.md +++ b/docs/gaia-tutorials/join-mainnet.md @@ -41,14 +41,14 @@ gaiad init **Note** Monikers can contain only ASCII characters. Using Unicode characters will render your node unreachable. -You can edit this `moniker` later, in the `~/.gaiad/config/config.toml` file: +You can edit this `moniker` later, in the `~/.gaia/config/config.toml` file: ```toml # A custom human readable name for this node moniker = "" ``` -You can edit the `~/.gaiad/config/app.toml` file in order to enable the anti spam mechanism and reject incoming transactions with less than the minimum gas prices: +You can edit the `~/.gaia/config/app.toml` file in order to enable the anti spam mechanism and reject incoming transactions with less than the minimum gas prices: ``` # This is a TOML config file. @@ -72,10 +72,10 @@ Your full node has been initialized! Fetch the mainnet's `genesis.json` file into `gaiad`'s config directory. ```bash -mkdir -p $HOME/.gaiad/config +mkdir -p $HOME/.gaia/config wget https://github.com/cosmos/mainnet/raw/master/genesis.cosmoshub-4.json.gz gzip -d genesis.cosmoshub-4.json.gz -mv genesis.cosmoshub-4.json $HOME/.gaiad/config +mv genesis.cosmoshub-4.json $HOME/.gaia/config ``` If you want to connect to the public testnet instead, click [here](./join-testnet.md) @@ -88,7 +88,7 @@ gaiad start ### Add Seed Nodes -Your node needs to know how to find peers. You'll need to add healthy seed nodes to `$HOME/.gaiad/config/config.toml`. The [`launch`](https://github.com/cosmos/launch) repo contains links to some seed nodes. +Your node needs to know how to find peers. You'll need to add healthy seed nodes to `$HOME/.gaia/config/config.toml`. The [`launch`](https://github.com/cosmos/launch) repo contains links to some seed nodes. If those seeds aren't working, you can find more seeds and persistent peers on a Cosmos Hub explorer (a list can be found on the [launch page](https://cosmos.network/launch)). @@ -114,7 +114,7 @@ For mainnet, the recommended `gas-prices` is `0.025uatom`. ## Set `minimum-gas-prices` -Your full-node keeps unconfirmed transactions in its mempool. In order to protect it from spam, it is better to set a `minimum-gas-prices` that the transaction must meet in order to be accepted in your node's mempool. This parameter can be set in the following file `~/.gaiad/config/app.toml`. +Your full-node keeps unconfirmed transactions in its mempool. In order to protect it from spam, it is better to set a `minimum-gas-prices` that the transaction must meet in order to be accepted in your node's mempool. This parameter can be set in the following file `~/.gaia/config/app.toml`. The initial recommended `min-gas-prices` is `0.025uatom`, but you might want to change it later. diff --git a/docs/gaia-tutorials/join-testnet.md b/docs/gaia-tutorials/join-testnet.md index be1ed17b50d..f631acfc935 100644 --- a/docs/gaia-tutorials/join-testnet.md +++ b/docs/gaia-tutorials/join-testnet.md @@ -34,7 +34,7 @@ These instructions are for full nodes that have ran on previous versions of and First, remove the outdated files and reset the data. ```bash -rm $HOME/.gaiad/config/addrbook.json $HOME/.gaiad/config/genesis.json +rm $HOME/.gaia/config/addrbook.json $HOME/.gaia/config/genesis.json gaiad unsafe-reset-all ``` diff --git a/docs/gaia-tutorials/upgrade-node.md b/docs/gaia-tutorials/upgrade-node.md index 5226aa3f942..ebfd69002fb 100644 --- a/docs/gaia-tutorials/upgrade-node.md +++ b/docs/gaia-tutorials/upgrade-node.md @@ -39,7 +39,7 @@ If you are joining the mainnet, fetch the genesis from the [mainnet repo](https: Save the new genesis as `new_genesis.json`. Then replace the old `genesis.json` with `new_genesis.json` ```bash -cd $HOME/.gaiad/config +cd $HOME/.gaia/config cp -f genesis.json new_genesis.json mv new_genesis.json genesis.json ``` @@ -51,7 +51,7 @@ Then, go to the [reset data](#reset-data) section. If you were running a node in the previous version of the network and want to build your new genesis locally from a state of this previous network, use the following command: ```bash -cd $HOME/.gaiad/config +cd $HOME/.gaia/config gaiad export --for-zero-height --height= > new_genesis.json ``` diff --git a/docs/migration/cosmoshub-2.md b/docs/migration/cosmoshub-2.md index 7fa346f809e..47c21720754 100644 --- a/docs/migration/cosmoshub-2.md +++ b/docs/migration/cosmoshub-2.md @@ -75,9 +75,9 @@ before resetting your validator. Prior to exporting `cosmoshub-2` state, validators are encouraged to take a full data snapshot at the export height before proceeding. Snapshotting depends heavily on infrastructure, but generally this -can be done by backing up the `.gaiacli` and `.gaiad` directories. +can be done by backing up the `.gaia` directories. -It is critically important to back-up the `.gaiad/data/priv_validator_state.json` file after stopping your gaiad process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted. +It is critically important to back-up the `.gaia/data/priv_validator_state.json` file after stopping your gaiad process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted. In the event that the upgrade does not succeed, validators and operators must downgrade back to v0.34.6+ of the _Cosmos SDK_ and restore to their latest snapshot before restarting their nodes. @@ -187,8 +187,8 @@ single parameter, `max_validators`, that we're upgrading based on [proposal 10]( $ gaiad unsafe-reset-all ``` -10. Move the new `genesis.json` to your `.gaiad/config/` directory -11. Replace the `db_backend` on `.gaiad/config/config.toml` to: +10. Move the new `genesis.json` to your `.gaia/config/` directory +11. Replace the `db_backend` on `.gaia/config/config.toml` to: ```toml db_backend = "goleveldb" @@ -197,7 +197,7 @@ single parameter, `max_validators`, that we're upgrading based on [proposal 10]( 12. Note, if you have any application configuration in `gaiad.toml`, that file has now been renamed to `app.toml`: ```bash - $ mv .gaiad/config/gaiad.toml .gaiad/config/app.toml + $ mv .gaia/config/gaiad.toml .gaia/config/app.toml ``` ## Notes for Service Providers diff --git a/docs/migration/cosmoshub-3.md b/docs/migration/cosmoshub-3.md index 1f77b89853a..8f690f1c9ae 100644 --- a/docs/migration/cosmoshub-3.md +++ b/docs/migration/cosmoshub-3.md @@ -97,7 +97,7 @@ applications gain in speed, readability, convinience and interoperability with m led to a `gaiad` and `gaiacli` binary which were seperated and could be used for different interactions with the blockchain. Both of these have been merged into one `gaiad` which now supports the commands the `gaiacli` previously supported. -- **Node Configuration**: Previously blockchain data and node configuration was stored in `~/.gaiad/`, these will +- **Node Configuration**: Previously blockchain data and node configuration was stored in `~/.gaia/`, these will now reside in `~/.gaia/`, if you use scripts that make use of the configuration or blockchain data, make sure to update the path. ## Risks @@ -116,9 +116,9 @@ before resetting your validator. Prior to exporting `cosmoshub-3` state, validators are encouraged to take a full data snapshot at the export height before proceeding. Snapshotting depends heavily on infrastructure, but generally this -can be done by backing up the `.gaiad` directory. +can be done by backing up the `.gaia` directory. -It is critically important to back-up the `.gaiad/data/priv_validator_state.json` file after stopping your gaiad process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted. +It is critically important to back-up the `.gaia/data/priv_validator_state.json` file after stopping your gaiad process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted. In the event that the upgrade does not succeed, validators and operators must downgrade back to gaia v2.0.15 with v0.37.15 of the _Cosmos SDK_ and restore to their latest snapshot before restarting their nodes. @@ -146,13 +146,13 @@ The version/commit hash of Gaia v2.0.15: `89cf7e6fc166eaabf47ad2755c443d455feda0 February 18, 2021 at 06:00 UTC is in UNIX seconds: `1613628000` ```bash - perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaiad/config/app.toml + perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaia/config/app.toml ``` - 1. After the chain has halted, make a backup of your `.gaiad` directory + 1. After the chain has halted, make a backup of your `.gaia` directory ```bash - mv ~/.gaiad ./gaiad_backup + mv ~/.gaia ./gaiad_backup ``` **NOTE**: It is recommended for validators and operators to take a full data snapshot at the export @@ -164,11 +164,11 @@ The version/commit hash of Gaia v2.0.15: `89cf7e6fc166eaabf47ad2755c443d455feda0 Before exporting state via the following command, the `gaiad` binary must be stopped! As a validator, you can see the last block height created in the - `~/.gaiad/data/priv_validator_state.json` - or now residing in `gaiad_backup` when you made + `~/.gaia/data/priv_validator_state.json` - or now residing in `gaiad_backup` when you made a backup as in the last step - and obtain it with ```bash - cat ~/.gaiad/data/priv_validator_state.json | jq '.height' + cat ~/.gaia/data/priv_validator_state.json | jq '.height' ``` ```bash @@ -267,15 +267,15 @@ Cross check your genesis hash with other peers (other validators) in the chat ro 1. Stop your Gaia v2.0.15 instance. -1. After the chain has halted, make a backup of your `.gaiad` directory +1. After the chain has halted, make a backup of your `.gaia` directory ```bash - mv ~/.gaiad ./gaiad_backup + mv ~/.gaia ./gaiad_backup ``` **NOTE**: It is recommended for validators and operators to take a full data snapshot at the export height before proceeding in case the upgrade does not go as planned or if not enough voting power - comes online in a sufficient and agreed upon amount of time. That means the backup of `.gaiad` should + comes online in a sufficient and agreed upon amount of time. That means the backup of `.gaia` should only take place once the chain has halted at UNIX time `1613628000`. In such a case, the chain will fallback to continue operating `cosmoshub-3`. See [Recovery](#recovery) for details on how to proceed. diff --git a/docs/migration/cosmoshub-3[ES_es].md b/docs/migration/cosmoshub-3[ES_es].md index aebc1e508ad..ee7bbb74f25 100644 --- a/docs/migration/cosmoshub-3[ES_es].md +++ b/docs/migration/cosmoshub-3[ES_es].md @@ -46,7 +46,7 @@ Algunos de los principales cambios que hay que tener en cuenta a la hora de actu - **Protocol Buffers**: Inicialmente el SDK de Cosmos utilizaba _codecs_ de Amino para casi toda la codificación y decodificación. En esta versión se ha integrado una importante actualización de los Protocol Buffers. Se espera que con los Protocol Buffers las aplicaciones ganen en velocidad, legibilidad, conveniencia e interoperabilidad con muchos lenguajes de programación. Para más información consulta [aquí](https://github.com/cosmos/cosmos-sdk/blob/master/docs/migrations/app_and_modules.md#protocol-buffers). - **CLI**: El CLI y el commando de full node para la cadena de bloques estaban separados en las versiones anteriores del SDK de Cosmos. Esto dio lugar a dos binarios, `gaiad` y `gaiacli`, que estaban separados y podían utilizarse para diferentes interacciones con la cadena de bloques. Ambos se han fusionado en un solo comando `gaiad` que ahora soporta los comandos que antes soportaba el `gaiacli`. -- **Configuración del nodo**: Anteriormente los datos de la cadena de bloques y la configuración de los nodos se almacenaban en `~/.gaiad/`, ahora residirán en `~/.gaia/`, si utilizas scripts que hacen uso de la configuración o de los datos de la cadena de bloques, asegúrate de actualizar la ruta. +- **Configuración del nodo**: Anteriormente los datos de la cadena de bloques y la configuración de los nodos se almacenaban en `~/.gaia/`, ahora residirán en `~/.gaia/`, si utilizas scripts que hacen uso de la configuración o de los datos de la cadena de bloques, asegúrate de actualizar la ruta. ## Riesgos @@ -56,9 +56,9 @@ Lo más arriesgado que puede hacer un validador es descubrir que ha cometido un ## Recuperación -Antes de exportar el estado de `cosmoshub-3`, se recomienda a los validadores que tomen una instantánea completa de los datos a la altura de la exportación antes de proceder. La toma de snapshots depende en gran medida de la infraestructura, pero en general se puede hacer una copia de seguridad del directorio `.gaiad`. +Antes de exportar el estado de `cosmoshub-3`, se recomienda a los validadores que tomen una instantánea completa de los datos a la altura de la exportación antes de proceder. La toma de snapshots depende en gran medida de la infraestructura, pero en general se puede hacer una copia de seguridad del directorio `.gaia`. -Es muy importante hacer una copia de seguridad del archivo `.gaiad/data/priv_validator_state.json` después de detener el proceso de gaiad. Este archivo se actualiza en cada bloque cuando tu validador participa en las rondas de consenso. Es un archivo crítico necesario para evitar la doble firma, en caso de que la actualización falle y sea necesario reiniciar la cadena anterior. +Es muy importante hacer una copia de seguridad del archivo `.gaia/data/priv_validator_state.json` después de detener el proceso de gaiad. Este archivo se actualiza en cada bloque cuando tu validador participa en las rondas de consenso. Es un archivo crítico necesario para evitar la doble firma, en caso de que la actualización falle y sea necesario reiniciar la cadena anterior. En el caso de que la actualización no tenga éxito, los validadores y operadores deben volver a actualizar a gaia v2.0.15 con v0.37.15 del _Cosmos SDK_ y restaurar a su último snapshot antes de reiniciar sus nodos. @@ -86,21 +86,21 @@ El hash de la versión/commit de Gaia v2.0.15: `89cf7e6fc166eaabf47ad2755c443d45 18 de febrero de 2021 a las 06:00 UTC es en segundos UNIX: `1613628000` ```bash - perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaiad/config/app.toml + perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaia/config/app.toml ``` -1. Después de que la cadena se haya detenido, haz una copia de seguridad de tu directorio `.gaiad`. +1. Después de que la cadena se haya detenido, haz una copia de seguridad de tu directorio `.gaia`. ```bash - mv ~/.gaiad ./gaiad_backup + mv ~/.gaia ./gaiad_backup ``` **NOTA**: Se recomienda a los validadores y operadores que tomen una instantánea completa de los datos a la altura de la exportación antes de proceder en caso de que la actualización no vaya según lo previsto o si no se pone en línea suficiente poder de voto en un tiempo determinado y acordado. En tal caso, la cadena volverá a funcionar con `cosmoshub-3`. Consulte [Recuperación](#recuperación) para saber cómo proceder. 1. Exportar el estado existente de `cosmoshub-3`: - Antes de exportar el estado a través del siguiente comando, el binario `gaiad` debe estar detenido. Como validador, puedes ver la última altura del bloque creado en el `~/.gaiad/config/data/priv_validator_state.json` -o que ahora reside en `gaiad_backup` cuando hiciste una copia de seguridad como en el último paso- y obtenerla con + Antes de exportar el estado a través del siguiente comando, el binario `gaiad` debe estar detenido. Como validador, puedes ver la última altura del bloque creado en el `~/.gaia/config/data/priv_validator_state.json` -o que ahora reside en `gaiad_backup` cuando hiciste una copia de seguridad como en el último paso- y obtenerla con ```bash - cat ~/.gaiad/config/data/priv_validator_state.json | jq '.height' + cat ~/.gaia/config/data/priv_validator_state.json | jq '.height' ``` ```bash diff --git a/docs/migration/cosmoshub-3[KR_kr].md b/docs/migration/cosmoshub-3[KR_kr].md index 3b8dedd01cb..c166fdbd4bb 100644 --- a/docs/migration/cosmoshub-3[KR_kr].md +++ b/docs/migration/cosmoshub-3[KR_kr].md @@ -50,7 +50,7 @@ __이번 업그레이드에서 풀 노드 운영자 업그레이드를 진행하 - **프로토콜 버퍼(Protocol BufferS)**: 이전 버전의 코스모스 SDK에서는 인코딩 및 디코딩 과정에서 아미노 코덱을 사용했습니다. 이번 코스모스 SDK 버전에서는 프로토콜 버퍼가 내장되어있습니다. 프로토콜 버퍼를 통해 애플리케이션은 속도, 가독성, 편의성, 프로그래밍 언어 간 상호호환성 등의 부분에서 상당한 개선이 있을 것으로 기대됩니다. [더 읽기](https://github.com/cosmos/cosmos-sdk/blob/master/docs/migrations/app_and_modules.md#protocol-buffers) - **CLI**: 이전 버전의 코스모스 SDK에서는 블록체인의 CLI와 데몬은 별도의 바이너리로 구성되었으며, 실행하는 블록체인 인터랙션에 따라 `gaiad`와 `gaiacli` 바이너리가 구분되었습니다. 이번 버전의 코스모스 SDK에서는 두 바이너리가 하나의 `gaiad` 바이너리로 통합되었으며 해당 바이너리 내에서 기존에 `gaiacli`에서 사용했던 명령어를 지원합니다. -- **노드 구성**: 이전 버전의 코스모스 SDK에서는 블록체인 데이터와 노드 설정이 `~/.gaiad/`에 저장되었지만, 이번 버전에서는 해당 정보다 `~/.gaia/` 디렉토리에 보관됩니다. 만약 블록체인 데이터 또는 노드 설정을 관리하는 스크립트를 사용하시는 경우 해당 스크립트에서 패스를 변경해야합니다. +- **노드 구성**: 이전 버전의 코스모스 SDK에서는 블록체인 데이터와 노드 설정이 `~/.gaia/`에 저장되었지만, 이번 버전에서는 해당 정보다 `~/.gaia/` 디렉토리에 보관됩니다. 만약 블록체인 데이터 또는 노드 설정을 관리하는 스크립트를 사용하시는 경우 해당 스크립트에서 패스를 변경해야합니다. ## 위험 고지 @@ -63,9 +63,9 @@ __이번 업그레이드에서 풀 노드 운영자 업그레이드를 진행하 ## 복구 -각 검증인은 `cosmoshub-3` 상태를 내보내기(export) 전에 내보내는 블록 하이트의 풀 데이터 스냅샷을 진행할 것을 권장합니다. 스냅샷 과정은 각 검증인의 인프라에 따라 다를 수 있지만, 통상 `.gaiad` 디렉토리를 백업하는 것으로 진행합니다. +각 검증인은 `cosmoshub-3` 상태를 내보내기(export) 전에 내보내는 블록 하이트의 풀 데이터 스냅샷을 진행할 것을 권장합니다. 스냅샷 과정은 각 검증인의 인프라에 따라 다를 수 있지만, 통상 `.gaia` 디렉토리를 백업하는 것으로 진행합니다. -`gaiad` 프로세스를 멈춘 후 `.gaiad/data/priv_validator_state.json` 파일을 백업하는 것은 매우 중요합니다. 이 파일은 검증인이 컨센서스 라운드에 참여할 때마다 업데이트됩니다. 만약 업그레이드 과정이 실패하여 이전 체인을 다시 시작해야되는 경우 검증인의 이중서명을 방지하기 위해서 이 파일은 필수입니다. +`gaiad` 프로세스를 멈춘 후 `.gaia/data/priv_validator_state.json` 파일을 백업하는 것은 매우 중요합니다. 이 파일은 검증인이 컨센서스 라운드에 참여할 때마다 업데이트됩니다. 만약 업그레이드 과정이 실패하여 이전 체인을 다시 시작해야되는 경우 검증인의 이중서명을 방지하기 위해서 이 파일은 필수입니다. 만약 업그레이드 과정이 실패하는 경우, 검증인과 노드 운영자는 gaia v2.0.15(코스모스 SDK v0.37.15 기반)으로 다운그레이드를 진행하고 가장 최근 진행했던 스냅샷을 복구한 이후에 노드를 시작해야합니다. @@ -94,14 +94,14 @@ Gaia v2.0.15의 버전/커밋 해시값: `89cf7e6fc166eaabf47ad2755c443d455feda0 2021년 2월 18일 06:00 UTC의 UNIX seconds 시간 값: `1613628000` ```bash - perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaiad/config/app.toml + perl -i -pe 's/^halt-time =.*/halt-time = 1613628000/' ~/.gaia/config/app.toml ``` - 1. 체인이 멈춘 후 `.gaiad` 디렉토리를 백업하세요 + 1. 체인이 멈춘 후 `.gaia` 디렉토리를 백업하세요 ```bash - mv ~/.gaiad ./gaiad_backup + mv ~/.gaia ./gaiad_backup ``` **참고**: 업그레이드 과정이 예상 외로 실패하거나 합의된 시간 내에 새로운 체인에 충분한 보팅 파워가 참여하지 않는 경우를 대비해 검증인과 노드 운영자는 export height의 풀 데이터 스냅샷을 진행하는 것을 권장합니다. 이 경우에는 체인 업그레이드 과정은 보류되고 `cosmoshub-3`의 운영이 재개됩니다. 해당 과정에 대해서는 [복구](#복구) 항목을 참고하세요. @@ -109,10 +109,10 @@ Gaia v2.0.15의 버전/커밋 해시값: `89cf7e6fc166eaabf47ad2755c443d455feda0 1. 기존 `cosmoshub-3`의 상태를 내보내기: 다음 명령어를 사용하여 상태를 내보내기 전 `gaiad` 바이너리가 꼭 멈춰있어야 합니다! - 검증인으로서 가장 최근 생성된 블록은 `~/.gaiad/config/data/priv_validator_state.json`에서 확인하실 수 있습니다 (또는 이전 과정에서 백업을 진행한 경우 `gaiad_backup`). 블록 높이는 다음과 같이 확인하세요 + 검증인으로서 가장 최근 생성된 블록은 `~/.gaia/config/data/priv_validator_state.json`에서 확인하실 수 있습니다 (또는 이전 과정에서 백업을 진행한 경우 `gaiad_backup`). 블록 높이는 다음과 같이 확인하세요 ```bash - cat ~/.gaiad/config/data/priv_validator_state.json | jq '.height' + cat ~/.gaia/config/data/priv_validator_state.json | jq '.height' ``` ```bash diff --git a/docs/resources/genesis.md b/docs/resources/genesis.md index ca7b55fc4d4..85fed5fadf4 100644 --- a/docs/resources/genesis.md +++ b/docs/resources/genesis.md @@ -12,7 +12,7 @@ Note that you can generate a default genesis file for your own testnet by runnin gaiad init --chain-id ``` -The genesis file is stored in `~/.gaiad/config/genesis.toml`. +The genesis file is stored in `~/.gaia/config/genesis.toml`. ## What is a Genesis File @@ -333,4 +333,4 @@ A `gentx` can be added manually to the genesis file, or via the following comman gaiad collect-gentxs ``` -This command will add all the `gentxs` stored in `~/.gaiad/config/gentx` to the genesis file. In order to create a genesis transaction, click [here](../validators/validator-setup.md#participate-in-genesis-as-a-validator). +This command will add all the `gentxs` stored in `~/.gaia/config/gentx` to the genesis file. In order to create a genesis transaction, click [here](../validators/validator-setup.md#participate-in-genesis-as-a-validator). diff --git a/docs/translations/cn/deploy-testnet.md b/docs/translations/cn/deploy-testnet.md index bf6c20923a0..d8266d26db7 100644 --- a/docs/translations/cn/deploy-testnet.md +++ b/docs/translations/cn/deploy-testnet.md @@ -14,10 +14,10 @@ 如果你需要使用或部署 gaia 作为容器,你可以跳过`build`步骤并使用官方镜像,\$TAG 标识你感兴趣的版本: -- `docker run -it -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad init` -- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad start` +- `docker run -it -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad init` +- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad start` - ... -- `docker run -it -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad version` +- `docker run -it -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad version` 相同的镜像也可以用于构建你自己的 docker-compose 栈 @@ -57,7 +57,7 @@ gaiad collect-gentxs gaiad start ``` -启动将会把`gaiad`相关的所有数据放在`~/.gaiad`目录。你可以检查所创建的 genesis 文件——`~/.gaiad/config/genesis.json`。同时`gaiad`也已经配置完成并且有了一个拥有 token 的账户(stake 和自定义的代币)。 +启动将会把`gaiad`相关的所有数据放在`~/.gaia`目录。你可以检查所创建的 genesis 文件——`~/.gaia/config/genesis.json`。同时`gaiad`也已经配置完成并且有了一个拥有 token 的账户(stake 和自定义的代币)。 ## 多节点,本地的,自动的测试网 diff --git a/docs/translations/cn/genesis.md b/docs/translations/cn/genesis.md index 1169390167e..6ffa0d88b21 100644 --- a/docs/translations/cn/genesis.md +++ b/docs/translations/cn/genesis.md @@ -8,7 +8,7 @@ gaiad init --chain-id ``` -genesis 文件存储在 `~/.gaiad/config/genesis.toml`. +genesis 文件存储在 `~/.gaia/config/genesis.toml`. ## 什么是创世文件 @@ -331,4 +331,4 @@ The `slashing` module handles the logic to slash delegators if their validator m gaiad collect-gentxs ``` -此命令将存储在`~/.gaiad/config/gentx`中的所有`gentxs`添加到genesis文件中。 要创建创世纪交易,请单击[此处](./validators/validator-setup.md#participation-in-genesis-as-a-validator)。 \ No newline at end of file +此命令将存储在`~/.gaia/config/gentx`中的所有`gentxs`添加到genesis文件中。 要创建创世纪交易,请单击[此处](./validators/validator-setup.md#participation-in-genesis-as-a-validator)。 \ No newline at end of file diff --git a/docs/translations/cn/join-mainnet.md b/docs/translations/cn/join-mainnet.md index 4f646a60a2e..d0184480212 100644 --- a/docs/translations/cn/join-mainnet.md +++ b/docs/translations/cn/join-mainnet.md @@ -22,14 +22,14 @@ gaiad init moniker只能包含ASCII字符。使用Unicode字符会使得你的节点不可访问 ::: -你可以稍后在`~/.gaiad/config/config.toml`文件中编辑`moniker`: +你可以稍后在`~/.gaia/config/config.toml`文件中编辑`moniker`: ```toml # A custom human readable name for this node moniker = "" ``` -你可以编辑`~/.gaiad/config/config.toml`文件来开启垃圾交易过滤机制以拒绝收到的手续费过低的交易: +你可以编辑`~/.gaia/config/config.toml`文件来开启垃圾交易过滤机制以拒绝收到的手续费过低的交易: ``` # This is a TOML config file. @@ -53,8 +53,8 @@ minimum-gas-prices = "" 将主网的`genesis.json`文件放置在`gaiad`的配置文件夹中 ```bash -mkdir -p $HOME/.gaiad/config -curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaiad/config/genesis.json +mkdir -p $HOME/.gaia/config +curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaia/config/genesis.json ``` 注意我们使用了[launch repo](https://github.com/cosmos/launch)中的`latest`文件夹,该文件夹包含了最新版本主网的详细信息。 @@ -71,7 +71,7 @@ gaiad start ### 添加种子节点 -你的节点需要知道如何寻找伙伴节点。你需要添加有用的种子节点到`$HOME/.gaiad/config/config.toml`文件中。[`launch`](https://github.com/cosmos/launch) repo包含了一些种子节点的链接。 +你的节点需要知道如何寻找伙伴节点。你需要添加有用的种子节点到`$HOME/.gaia/config/config.toml`文件中。[`launch`](https://github.com/cosmos/launch) repo包含了一些种子节点的链接。 如果这些种子节点不再运行,你可以在Cosmos Hub浏览器(可以在[launch page](https://cosmos.network/launch)中找到)发现种子节点和持久节点。 @@ -102,7 +102,7 @@ fees = gas * gasPrices ## 设置`minimum-gas-prices` -你的全节点可以在交易池中放入未确认的交易。为了保护其免受Spam攻击,最好设置一个`minimum-gas-prices`来过滤交易以决定是否要放入交易池。这个参数可以在`~/.gaiad/config/gaiad.toml`文件中配置。 +你的全节点可以在交易池中放入未确认的交易。为了保护其免受Spam攻击,最好设置一个`minimum-gas-prices`来过滤交易以决定是否要放入交易池。这个参数可以在`~/.gaia/config/gaiad.toml`文件中配置。 推荐的初始`minimum-gas-prices`是`0.025uatom`,如果你愿意可以稍后再修改它。 diff --git a/docs/translations/cn/join-testnet.md b/docs/translations/cn/join-testnet.md index 872bd67401f..d69267f81a5 100644 --- a/docs/translations/cn/join-testnet.md +++ b/docs/translations/cn/join-testnet.md @@ -29,7 +29,7 @@ 首先,移除过期的文件并重置数据: ```bash -rm $HOME/.gaiad/config/addrbook.json $HOME/.gaiad/config/genesis.json +rm $HOME/.gaia/config/addrbook.json $HOME/.gaia/config/genesis.json gaiad unsafe-reset-all ``` diff --git a/docs/translations/cn/validators/validator-setup.md b/docs/translations/cn/validators/validator-setup.md index 71fe332f7a0..232b3ef3727 100644 --- a/docs/translations/cn/validators/validator-setup.md +++ b/docs/translations/cn/validators/validator-setup.md @@ -157,7 +157,7 @@ gaiad tx slashing unjail \ gaiad query tendermint-validator-set | grep "$(gaiad tendermint show-validator)" ``` -你必须要在[区块浏览器](https://explorecosmos.network/validators)中看见你的验证人节点信息。你可以在`~/.gaiad/config/priv_validator.json`文件中找到`bech32`编码格式的`address`。 +你必须要在[区块浏览器](https://explorecosmos.network/validators)中看见你的验证人节点信息。你可以在`~/.gaia/config/priv_validator.json`文件中找到`bech32`编码格式的`address`。 ::: warning 注意 为了能进入验证人集合,你的权重必须超过第100名的验证人。 diff --git a/docs/translations/es/join-mainnet.md b/docs/translations/es/join-mainnet.md index f64757fed87..d2fe6ebdfba 100644 --- a/docs/translations/es/join-mainnet.md +++ b/docs/translations/es/join-mainnet.md @@ -26,13 +26,13 @@ gaiad init El moniker solo debe contener carácteres ASCII. El uso de caracteres Unicode hará que tu nodo sea irreconocible. ::: -Puede editar el apodo (`moniker`) después, en el archivo `~/.gaiad/config/config.toml`: +Puede editar el apodo (`moniker`) después, en el archivo `~/.gaia/config/config.toml`: ```toml # A custom human readable name for this node moniker = "" ``` -Puede editar el archivo `~/.gaiad/config/app.toml` para activar el mecanismo antispam y rechazar las transacciones entrantes con valores inferiores a los precios mínimos para el _gas_: +Puede editar el archivo `~/.gaia/config/app.toml` para activar el mecanismo antispam y rechazar las transacciones entrantes con valores inferiores a los precios mínimos para el _gas_: ``` # This is a TOML config file. @@ -56,8 +56,8 @@ minimum-gas-prices = "" Busque el archivo `genesis.json` de la red principal en el directorio de configuración de `gaiad`. ```bash -mkdir -p $HOME/.gaiad/config -curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaiad/config/genesis.json +mkdir -p $HOME/.gaia/config +curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaia/config/genesis.json ``` Observe que usamos el directorio `latest` en el [repositorio de lanzamiento](https://github.com/cosmos/launch) que contiene detalles para la red principal como la última versión y el archivo de génesis. @@ -74,7 +74,7 @@ gaiad start ### Añada los nodos semilla -Su nodo necesita saber cómo encontrar pares (_peers_). Necesita añadir nodos semilla en buen estado en `$HOME/.gaiad/config/config.toml`. El repositorio para el [`lanzamiento`](https://github.com/cosmos/launch) contiene enlaces a algunos nodos semilla. +Su nodo necesita saber cómo encontrar pares (_peers_). Necesita añadir nodos semilla en buen estado en `$HOME/.gaia/config/config.toml`. El repositorio para el [`lanzamiento`](https://github.com/cosmos/launch) contiene enlaces a algunos nodos semilla. Si estas semillas no funcionan, puedes encontrar más _seeds_ y _peers_ persistentes en un explorador de Cosmos Hub (puede encontrar una lista en la [página del lanzamiento](https://cosmos.network/launch)) @@ -106,7 +106,7 @@ Para la red principal, el `gas-prices` recomendado es `0.025uatom`. ## Establezca `minimum-gas-prices` -Su nodo completo mantiene las transacciones no confirmadas en la _mempool_. Para protegerlo de ataques de spam, es mejor establecer un `minimum-gas-prices` que la transacción debe cumplir para ser aceptada en la _mempool_ de su nodo. Este parámetro puede ser establecido en el siguiente archivo `~/.gaiad/config/app.toml`. +Su nodo completo mantiene las transacciones no confirmadas en la _mempool_. Para protegerlo de ataques de spam, es mejor establecer un `minimum-gas-prices` que la transacción debe cumplir para ser aceptada en la _mempool_ de su nodo. Este parámetro puede ser establecido en el siguiente archivo `~/.gaia/config/app.toml`. El valor inicial recomendado para `min-gas-prices` es `0.025uatom`, pero puede querer cambiarlo más tarde. diff --git a/docs/translations/kr/deploy-testnet.md b/docs/translations/kr/deploy-testnet.md index 5e7c4e9426c..88de6957384 100755 --- a/docs/translations/kr/deploy-testnet.md +++ b/docs/translations/kr/deploy-testnet.md @@ -14,9 +14,9 @@ 컨테이너 형태로 Gaia 디플로이를 원하시는 경우, `build` 단계를 건너뛰시고 공식 이미지 파일을 설치하실 수 있습니다. \$TAG은 설치하시려는 버전을 의미합니다. -- `docker run -it -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad init` -- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad start` -- `docker run -it -v ~/.gaiad:/root/.gaiad -v ~/.gaiad:/root/.gaiad tendermint:$TAG gaiad version` +- `docker run -it -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad init` +- `docker run -it -p 26657:26657 -p 26656:26656 -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad start` +- `docker run -it -v ~/.gaia:/root/.gaia -v ~/.gaia:/root/.gaia tendermint:$TAG gaiad version` 각 이미지는 자체적인 docker-compose 스택을 빌드하는데 사용하실 수 있습니다. @@ -55,7 +55,7 @@ gaiad collect-gentxs gaiad start ``` -이 셋업은 모든 `gaiad` 정보를 `~/.gaiad`에 저장힙니다. 생성하신 제네시스 파일을 확인하고 싶으시다면 `~/.gaiad/config/genesis.json`에서 확인이 가능합니다. 위의 세팅으로 `gaiad`가 이용이 가능하며, 토큰(스테이킹/커스텀)이 있는 계정 또한 함께 생성됩니다. +이 셋업은 모든 `gaiad` 정보를 `~/.gaia`에 저장힙니다. 생성하신 제네시스 파일을 확인하고 싶으시다면 `~/.gaia/config/genesis.json`에서 확인이 가능합니다. 위의 세팅으로 `gaiad`가 이용이 가능하며, 토큰(스테이킹/커스텀)이 있는 계정 또한 함께 생성됩니다. ## 멀티 노드, 로컬, 자동 테스트넷 diff --git a/docs/translations/kr/genesis.md b/docs/translations/kr/genesis.md index d80618ed693..2314d5b4561 100644 --- a/docs/translations/kr/genesis.md +++ b/docs/translations/kr/genesis.md @@ -8,7 +8,7 @@ gaiad init <명칭(moniker)> --chain-id <체인_아이디(chain-id)> ``` -제네시스 파일은 `~/.gaiad/config/genesis.toml`에 저장됩니다. +제네시스 파일은 `~/.gaia/config/genesis.toml`에 저장됩니다. ## 제네시스 파일은 무엇인가? @@ -330,4 +330,4 @@ gaiad add-genesis-account <계정_주소(account_address)> <수량(amount)> <단 gaiad collect-gentxs ``` -위 명령어는 `~/.gaiad/config/gentx`에 있는 모든 `gentxs`를 제네시스 파일에 추가합니다. 제네시스 트랜잭션을 생성하기 위해서는 [여기](./validators/validator-setup.md#participate-in-genesis-as-a-validator)를 확인하세요. \ No newline at end of file +위 명령어는 `~/.gaia/config/gentx`에 있는 모든 `gentxs`를 제네시스 파일에 추가합니다. 제네시스 트랜잭션을 생성하기 위해서는 [여기](./validators/validator-setup.md#participate-in-genesis-as-a-validator)를 확인하세요. \ No newline at end of file diff --git a/docs/translations/kr/join-mainnet.md b/docs/translations/kr/join-mainnet.md index 88e92e2a10a..7e994889247 100644 --- a/docs/translations/kr/join-mainnet.md +++ b/docs/translations/kr/join-mainnet.md @@ -24,14 +24,14 @@ gaiad init `--moniker`는 ASCII 캐릭터만을 지원합니다. Unicode 캐릭터를 이용하는 경우 노드 접근이 불가능할 수 있으니 참고하세요. ::: -`moniker`는 `~/.gaiad/config/config.toml` 파일을 통해 추후에 변경이 가능합니다: +`moniker`는 `~/.gaia/config/config.toml` 파일을 통해 추후에 변경이 가능합니다: ```toml # A custom human readable name for this node moniker = "" ``` -최소 가스 가격보다 낮은 트랜잭션을 거절하는 스팸 방지 메커니즘을 활성화 하시려면 `~/.gaiad/config/gaiad.toml` 파일을 변경하시면 됩니다: +최소 가스 가격보다 낮은 트랜잭션을 거절하는 스팸 방지 메커니즘을 활성화 하시려면 `~/.gaia/config/gaiad.toml` 파일을 변경하시면 됩니다: ``` # This is a TOML config file. @@ -55,8 +55,8 @@ minimum-gas-prices = "" 테스트넷의 `genesis.json`파일을 `gaiad`의 config 디렉토리로 가져옵니다. ```bash -mkdir -p $HOME/.gaiad/config -curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaiad/config/genesis.json +mkdir -p $HOME/.gaia/config +curl https://raw.githubusercontent.com/cosmos/launch/master/genesis.json > $HOME/.gaia/config/genesis.json ``` 위 예시에서는 최신 테스트넷에 대한 정보가 포함되어있는 [launch repo](https://github.com/cosmos/launch)의 `latest` 디렉토리를 이용하는 것을 참고하세요. @@ -72,7 +72,7 @@ gaiad start ``` ### 시드 노드 추가하기 -이제 노드가 다른 피어들을 찾는 방법을 알아야합니다. `$HOME/.gaiad/config/config.toml`에 안정적인 시드 노드들을 추가할 차례입니다. [`launch`](https://github.com/cosmos/launch) repo에 몇 개 시드 노드 링크가 포함되어있습니다. +이제 노드가 다른 피어들을 찾는 방법을 알아야합니다. `$HOME/.gaia/config/config.toml`에 안정적인 시드 노드들을 추가할 차례입니다. [`launch`](https://github.com/cosmos/launch) repo에 몇 개 시드 노드 링크가 포함되어있습니다. 만약 해당 시드가 작동하지 않는다면, 추가적인 시드와 피어들을 코스모스 허브 익스플로러에서 확인하세요(목록은 [launch](https://cosmos.network/launch) 페이지에 있습니다.) @@ -105,7 +105,7 @@ gaiad start ## 최소 가스 가격(`minimum-gas-prices`) 설정하기 -풀노드는 컨펌되지 않은 트랜잭션을 멤풀에 보관합니다. 스팸 트랜잭션으로부터 풀노드를 보호하기 위해서 노드 멤풀에 보관되기 위한 트랜잭션의 최소 가스 가격(`minimum-gas-prices`)을 설정할 것을 권장합니다. 해당 파라미터는 `~/.gaiad/config/gaiad.toml`에서 설정하실 수 있씁니다. +풀노드는 컨펌되지 않은 트랜잭션을 멤풀에 보관합니다. 스팸 트랜잭션으로부터 풀노드를 보호하기 위해서 노드 멤풀에 보관되기 위한 트랜잭션의 최소 가스 가격(`minimum-gas-prices`)을 설정할 것을 권장합니다. 해당 파라미터는 `~/.gaia/config/gaiad.toml`에서 설정하실 수 있씁니다. 기본 권장 `minimum-gas-prices`는 `0.025uatom`이지만, 추후 바꾸실 수 있습니다. diff --git a/docs/translations/kr/join-testnet.md b/docs/translations/kr/join-testnet.md index a87d2bb9c04..15a006b0316 100755 --- a/docs/translations/kr/join-testnet.md +++ b/docs/translations/kr/join-testnet.md @@ -24,14 +24,14 @@ gaiad init --moniker `--moniker`는 ASCII 캐릭터만을 지원합니다. Unicode 캐릭터를 이용하는 경우 노드 접근이 불가능할 수 있으니 참고하세요. ::: -`moniker`는 `~/.gaiad/config/config.toml` 파일을 통해 추후에 변경이 가능합니다: +`moniker`는 `~/.gaia/config/config.toml` 파일을 통해 추후에 변경이 가능합니다: ```toml # A custom human readable name for this node moniker = "" ``` -최소 수수료보다 낮은 트랜잭션을 거절하는 스팸 방지 메커니즘을 활성화 하시려면 `~/.gaiad/config/gaiad.toml` 파일을 변경하시면 됩니다: +최소 수수료보다 낮은 트랜잭션을 거절하는 스팸 방지 메커니즘을 활성화 하시려면 `~/.gaia/config/gaiad.toml` 파일을 변경하시면 됩니다: ``` # This is a TOML config file. @@ -54,7 +54,7 @@ minimum_fees = "" 우선, 과거 파일을 삭제하고 데이터를 리셋합니다. ```bash -rm $HOME/.gaiad/config/addrbook.json $HOME/.gaiad/config/genesis.json +rm $HOME/.gaia/config/addrbook.json $HOME/.gaia/config/genesis.json gaiad unsafe-reset-all ``` @@ -90,8 +90,8 @@ _참고_: 이 단계에서 문제가 있으시다면 최신 스테이블 GO 버 테스트넷의 `genesis.json`파일을 `gaiad`의 config 디렉토리로 가져옵니다. ```bash -mkdir -p $HOME/.gaiad/config -curl https://raw.githubusercontent.com/cosmos/testnets/master/latest/genesis.json > $HOME/.gaiad/config/genesis.json +mkdir -p $HOME/.gaia/config +curl https://raw.githubusercontent.com/cosmos/testnets/master/latest/genesis.json > $HOME/.gaia/config/genesis.json ``` 위 예시에서는 최신 테스트넷에 대한 정보가 포함되어있는 [테스트넷 repo]의 `latest`를 이용하는 것을 참고하세요. 만약 다른 테스트넷에 연결하신다면 해당 테스트넷의 파일을 가져오는 것인지 확인하세요. @@ -104,7 +104,7 @@ gaiad start ### 시드 노드 추가하기 -이제 노드가 다른 피어들을 찾는 방법을 알아야합니다. `$HOME/.gaiad/config/config.toml`에 안정적인 시드 노드들을 추가할 차례입니다. `testnets` repo에 각 테스트넷에 대한 시드 노드 링크가 포함되어있습니다. 만약 현재 운영되고 있는 테스트넷을 참가하고 싶으시다면 [여기](https://github.com/cosmos/testnets)에서 어떤 노드를 이용할지 확인하세요. +이제 노드가 다른 피어들을 찾는 방법을 알아야합니다. `$HOME/.gaia/config/config.toml`에 안정적인 시드 노드들을 추가할 차례입니다. `testnets` repo에 각 테스트넷에 대한 시드 노드 링크가 포함되어있습니다. 만약 현재 운영되고 있는 테스트넷을 참가하고 싶으시다면 [여기](https://github.com/cosmos/testnets)에서 어떤 노드를 이용할지 확인하세요. 만약 해당 시드가 작동하지 않는다면, 추가적인 시드와 피어들을 [코스모스 익스플로러](https://explorer.cosmos.network/nodes)를 통해 확인하실 수 있습니다. `Full Nodes` 탭을 들어가셔서 프라이빗(`10.x.x.x`) 또는 로컬 IP 주소(https://en.wikipedia.org/wiki/Private_network)가 _아닌_ 노드를 열어보세요. `Persistent Peer` 값에 연결 스트링(connection string)이 표기되어 있습니다. 가장 최적화된 결과를 위해서는 4-6을 이용하세요. diff --git a/docs/translations/kr/upgrade-node.md b/docs/translations/kr/upgrade-node.md index f0cf4033021..4d4fce7343e 100644 --- a/docs/translations/kr/upgrade-node.md +++ b/docs/translations/kr/upgrade-node.md @@ -34,7 +34,7 @@ _참고_: 이번 단계에서 문제가 발생하는 경우, 최신 스테이블 새로운 제네시스 파일을 `new_genesis.json`으로 저장하세요. 이후, 오래된 `genesis.json`을 `new_genesis.json`으로 바꾸세요. ```bash -cd $HOME/.gaiad/config +cd $HOME/.gaia/config cp -f genesis.json new_genesis.json mv new_genesis.json genesis.json ``` @@ -46,7 +46,7 @@ mv new_genesis.json genesis.json 만약 과거 네트워크 버전에서 노드를 운영하셨고 로컬 환경에서 과거 네트워크의 제네시스 파일을 내보내시는 경우, 다음 명령어를 사용하세요: ```bash -cd $HOME/.gaiad/config +cd $HOME/.gaia/config gaiad export --for-zero-height --height=<내보내는_블록_높이(export-height)> > new_genesis.json ``` diff --git a/docs/translations/kr/validators/validator-setup.md b/docs/translations/kr/validators/validator-setup.md index 49156a10c51..e6950746ef2 100755 --- a/docs/translations/kr/validators/validator-setup.md +++ b/docs/translations/kr/validators/validator-setup.md @@ -69,7 +69,7 @@ gaiad gentx \ --name ``` -__참고__: 이 명령어는 제네시스에서의 처리를 위해 `gentx`를 `~/.gaiad/config/gentx`에 저장합니다. +__참고__: 이 명령어는 제네시스에서의 처리를 위해 `gentx`를 `~/.gaia/config/gentx`에 저장합니다. ::: tip 명령어 플래그에 대한 정보는 `gaiad gentx --help`를 사용에 확인하십시오. @@ -84,15 +84,15 @@ __참고__: 이 명령어는 제네시스에서의 처리를 위해 `gentx`를 ` Fetch the `genesis.json` file into `gaiad`'s config directory. ```bash -mkdir -p $HOME/.gaiad/config -curl https://raw.githubusercontent.com/cosmos/testnets/master/latest/genesis.json > $HOME/.gaiad/config/genesis.json +mkdir -p $HOME/.gaia/config +curl https://raw.githubusercontent.com/cosmos/testnets/master/latest/genesis.json > $HOME/.gaia/config/genesis.json ``` __참고:__ 이 항목에서는 최신 테스트넷 관련 정보가 있는 [테스트넷 repo](https://github.com/cosmos/testnets)의 `latest` 디렉토리를 사용합니다. 만약 다른 테스트넷에 연결하신다면 이용하시는 파일을 확인하시기 바랍니다. 이제 다른 제네시스 밸리데이터들의 제네시스 트랜잭션을 가져옵니다. 현재 밸리데이터들이 본인들의 제네시스 트랜잭션을 제공할 수 있는 리포지토리가 없는 상태이나, 추후 테스트넷에서 검증 후 추가될 예정입니다. -모든 제네시스 트랜잭션을 받으시고 `~/.gaiad/config/gentx`에 저장하셨다면 다음 명령어를 실행하십시오: +모든 제네시스 트랜잭션을 받으시고 `~/.gaia/config/gentx`에 저장하셨다면 다음 명령어를 실행하십시오: ```bash gaiad collect-gentxs @@ -163,7 +163,7 @@ gaiad tx slashing unjail \ gaiad query tendermint-validator-set | grep "$(gaiad tendermint show-validator)" ``` -코스모스 테스트넷의 경우 코스모스 [익스플로러](https://explorecosmos.network/validators)를 통해서 밸리데이터가 운영되고 있는지 확인하실 수 있습니다. `~/.gaiad/config/priv_validator.json` 파일의 `bech32` 인코딩이된 `address` 항목을 참고하세요. +코스모스 테스트넷의 경우 코스모스 [익스플로러](https://explorecosmos.network/validators)를 통해서 밸리데이터가 운영되고 있는지 확인하실 수 있습니다. `~/.gaia/config/priv_validator.json` 파일의 `bech32` 인코딩이된 `address` 항목을 참고하세요. ::: warning 참고 검증인 세트에 포함되시기 원하신다면 125등 밸리데이터보다 보팅 파워(voting power)가 높아야 합니다. diff --git a/docs/validators/kms/kms_ledger.md b/docs/validators/kms/kms_ledger.md index 3a512ebf4b9..4c48a375484 100644 --- a/docs/validators/kms/kms_ledger.md +++ b/docs/validators/kms/kms_ledger.md @@ -41,7 +41,7 @@ chain_ids = ["gaia-11001"] ``` - Edit `addr` to point to your `gaiad` instance. -- Adjust `chain-id` to match your `.gaiad/config/config.toml` settings. +- Adjust `chain-id` to match your `.gaia/config/config.toml` settings. - `provider.ledgertm` has not additional parameters at the moment, however, it is important that you keep that header to enable the feature. *Plug your Ledger device and open the Tendermint validator app.* @@ -80,7 +80,7 @@ Take note of the validator pubkey that appears in your screen. *We will use it i ## Gaia configuration -You need to enable KMS access by editing `.gaiad/config/config.toml`. In this file, modify `priv_validator_laddr` to create a listening address/port or a unix socket in `gaiad`. +You need to enable KMS access by editing `.gaia/config/config.toml`. In this file, modify `priv_validator_laddr` to create a listening address/port or a unix socket in `gaiad`. For example: diff --git a/networks/remote/ansible/roles/clear-config/tasks/main.yml b/networks/remote/ansible/roles/clear-config/tasks/main.yml index 5b4504cfba7..9e853f1d6ef 100644 --- a/networks/remote/ansible/roles/clear-config/tasks/main.yml +++ b/networks/remote/ansible/roles/clear-config/tasks/main.yml @@ -1,12 +1,9 @@ --- - - name: Stop service service: name=gaiad state=stopped - name: Delete files file: "path={{item}} state=absent" with_items: - - /usr/bin/gaiad - - /home/gaiad/.gaiad - - /home/gaiad/.gaiacli - + - /usr/bin/gaiad + - /home/gaiad/.gaia diff --git a/networks/remote/ansible/roles/extract-config/tasks/main.yml b/networks/remote/ansible/roles/extract-config/tasks/main.yml index 02f2acf200f..2ec38e063da 100644 --- a/networks/remote/ansible/roles/extract-config/tasks/main.yml +++ b/networks/remote/ansible/roles/extract-config/tasks/main.yml @@ -1,13 +1,13 @@ --- - name: Fetch genesis.json - fetch: "src=/home/gaiad/.gaiad/config/genesis.json dest={{GENESISFILE}} flat=yes" + fetch: "src=/home/gaiad/.gaia/config/genesis.json dest={{GENESISFILE}} flat=yes" run_once: yes become: yes become_user: gaiad - name: Fetch config.toml - fetch: "src=/home/gaiad/.gaiad/config/config.toml dest={{CONFIGFILE}} flat=yes" + fetch: "src=/home/gaiad/.gaia/config/config.toml dest={{CONFIGFILE}} flat=yes" run_once: yes become: yes become_user: gaiad diff --git a/networks/remote/ansible/roles/setup-fullnodes/tasks/main.yml b/networks/remote/ansible/roles/setup-fullnodes/tasks/main.yml index ba9b22942c1..264bdd76fe1 100644 --- a/networks/remote/ansible/roles/setup-fullnodes/tasks/main.yml +++ b/networks/remote/ansible/roles/setup-fullnodes/tasks/main.yml @@ -30,7 +30,7 @@ become_user: gaiad register: initresult args: - creates: /home/gaiad/.gaiad/config + creates: /home/gaiad/.gaia/config - name: Get wallet word seed from result of initial transaction locally when: initresult["changed"] @@ -48,14 +48,14 @@ - name: Copy genesis file copy: src: "{{GENESISFILE}}" - dest: /home/gaiad/.gaiad/config/genesis.json + dest: /home/gaiad/.gaia/config/genesis.json become: yes become_user: gaiad - name: Copy config.toml file copy: src: "{{CONFIGFILE}}" - dest: /home/gaiad/.gaiad/config/config.toml + dest: /home/gaiad/.gaia/config/config.toml become: yes become_user: gaiad diff --git a/networks/remote/ansible/roles/setup-validators/tasks/main.yml b/networks/remote/ansible/roles/setup-validators/tasks/main.yml index d8cb4991350..a50ffa84410 100644 --- a/networks/remote/ansible/roles/setup-validators/tasks/main.yml +++ b/networks/remote/ansible/roles/setup-validators/tasks/main.yml @@ -30,7 +30,7 @@ become: yes become_user: gaiad args: - creates: /home/gaiad/.gaiad/config/gentx + creates: /home/gaiad/.gaia/config/gentx - name: Get wallet word seed from result of initial transaction locally when: gentxresult["changed"] @@ -46,7 +46,7 @@ connection: local - name: Find gentx file - command: "ls /home/gaiad/.gaiad/config/gentx" + command: "ls /home/gaiad/.gaia/config/gentx" changed_when: false register: gentxfile @@ -58,7 +58,7 @@ - name: Get gen-tx file fetch: dest: files/ - src: "/home/gaiad/.gaiad/config/gentx/{{gentxfile.stdout_lines[0]}}" + src: "/home/gaiad/.gaia/config/gentx/{{gentxfile.stdout_lines[0]}}" flat: yes - name: Compress gathered gen-tx files locally @@ -67,12 +67,12 @@ connection: local - name: Unpack gen-tx archive - unarchive: src=files/gen-tx.tgz dest=/home/gaiad/.gaiad/config/gentx owner=gaiad + unarchive: src=files/gen-tx.tgz dest=/home/gaiad/.gaia/config/gentx owner=gaiad - name: Generate genesis.json command: "/usr/bin/gaiad init --with-txs --name=node{{nodeid.stdout_lines[0]}} --chain-id={{TESTNET_NAME}}" become: yes become_user: gaiad args: - creates: /home/gaiad/.gaiad/config/genesis.json + creates: /home/gaiad/.gaia/config/genesis.json diff --git a/networks/remote/ansible/roles/upgrade-gaiad/tasks/main.yml b/networks/remote/ansible/roles/upgrade-gaiad/tasks/main.yml index 0022199350a..b52de9eb787 100644 --- a/networks/remote/ansible/roles/upgrade-gaiad/tasks/main.yml +++ b/networks/remote/ansible/roles/upgrade-gaiad/tasks/main.yml @@ -11,14 +11,14 @@ when: "GENESISFILE is defined and GENESISFILE != ''" copy: src: "{{GENESISFILE}}" - dest: /home/gaiad/.gaiad/config/genesis.json + dest: /home/gaiad/.gaia/config/genesis.json notify: restart gaiad - name: Download genesis.json URL, if available when: "GENESISURL is defined and GENESISURL != ''" get_url: url: "{{GENESISURL}}" - dest: /home/gaiad/.gaiad/config/genesis.json + dest: /home/gaiad/.gaia/config/genesis.json force: yes notify: restart gaiad diff --git a/sims.mk b/sims.mk index 6bea3f8774b..c17cd9560a0 100644 --- a/sims.mk +++ b/sims.mk @@ -12,8 +12,8 @@ test-sim-nondeterminism: test-sim-custom-genesis-fast: @echo "Running custom genesis simulation..." - @echo "By default, ${HOME}/.gaiad/config/genesis.json will be used." - @go test -mod=readonly $(SIMAPP) -run TestFullAppSimulation -Genesis=${HOME}/.gaiad/config/genesis.json \ + @echo "By default, ${HOME}/.gaia/config/genesis.json will be used." + @go test -mod=readonly $(SIMAPP) -run TestFullAppSimulation -Genesis=${HOME}/.gaia/config/genesis.json \ -Enabled=true -NumBlocks=100 -BlockSize=200 -Commit=true -Seed=99 -Period=5 -v -timeout 24h test-sim-import-export: runsim @@ -26,8 +26,8 @@ test-sim-after-import: runsim test-sim-custom-genesis-multi-seed: runsim @echo "Running multi-seed custom genesis simulation..." - @echo "By default, ${HOME}/.gaiad/config/genesis.json will be used." - @$(BINDIR)/runsim -Genesis=${HOME}/.gaiad/config/genesis.json -SimAppPkg=$(SIMAPP) -ExitOnFail 400 5 TestFullAppSimulation + @echo "By default, ${HOME}/.gaia/config/genesis.json will be used." + @$(BINDIR)/runsim -Genesis=${HOME}/.gaia/config/genesis.json -SimAppPkg=$(SIMAPP) -ExitOnFail 400 5 TestFullAppSimulation test-sim-multi-seed-long: runsim @echo "Running long multi-seed application simulation. This may take awhile!"