From 3c69b6b7a1ccb6167fb7477f5cb27f98d6ba6900 Mon Sep 17 00:00:00 2001 From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com> Date: Mon, 16 Dec 2024 11:14:49 +0200 Subject: [PATCH 1/4] typos adr-001-interchain-accounts.md --- docs/docs/architecture/adr/adr-001-interchain-accounts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/architecture/adr/adr-001-interchain-accounts.md b/docs/docs/architecture/adr/adr-001-interchain-accounts.md index 906ec81bc2b..3809e983a00 100644 --- a/docs/docs/architecture/adr/adr-001-interchain-accounts.md +++ b/docs/docs/architecture/adr/adr-001-interchain-accounts.md @@ -18,7 +18,7 @@ REJECTED Not Implemented ## Abstract -This is the Core Interchain Accounts Module. It allows the Cosmos Hub to act as a host chain with interchain accounts that are controlled by external IBC connected "Controller" blockchains. Candidate chains include Umee, Quicksilver, Sommelier. It is also a necessary component for a Authentication Module that allows the Cosmos Hub to act as a Controller chain as well. This will be recorded in a separate ADR. +This is the Core Interchain Accounts Module. It allows the Cosmos Hub to act as a host chain with interchain accounts that are controlled by external IBC connected "Controller" blockchains. Candidate chains include Umee, Quicksilver, Sommelier. It is also a necessary component for an Authentication Module that allows the Cosmos Hub to act as a Controller chain as well. This will be recorded in a separate ADR. ## Rationale @@ -91,4 +91,4 @@ There are future releases of Interchain Accounts which are expected to be backwa ## Additional Research & References - [Why Interchain Accounts Change Everything for Cosmos Interoperability](https://medium.com/chainapsis/why-interchain-accounts-change-everything-for-cosmos-interoperability-59c19032bf11) -- [Interchain Account Auth Module Demo Repo](https://github.com/cosmos/interchain-accounts) \ No newline at end of file +- [Interchain Account Auth Module Demo Repo](https://github.com/cosmos/interchain-accounts) From b0fa6393141dcb87ace0fc53eddf56b1e065f1d0 Mon Sep 17 00:00:00 2001 From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com> Date: Mon, 16 Dec 2024 11:15:20 +0200 Subject: [PATCH 2/4] typos adr-001-interchain-accounts.md --- docs/docs/architecture/adr/adr-001-interchain-accounts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/architecture/adr/adr-001-interchain-accounts.md b/docs/docs/architecture/adr/adr-001-interchain-accounts.md index 3809e983a00..36c3f74037f 100644 --- a/docs/docs/architecture/adr/adr-001-interchain-accounts.md +++ b/docs/docs/architecture/adr/adr-001-interchain-accounts.md @@ -30,7 +30,7 @@ The hub can be used trustlessly as a host chain in the configuration of Intercha ## Consequences -There has been preliminary work done to understand if this increases any security feature of the Cosmos Hub. One thought was that this capability is similar to contract to contract interactions which are possible on virtual machine blockchains like EVM chains. Those interactions introduced a new attack vector, called a re-entrancy bug, which was the culprit of "The DAO hack on Ethereum". We believe there is no risk of these kinds of attacks with Interchain Accounts because they require the interactions to be atomic and Interchain Accounts are asynchronous. +There has been preliminary work done to understand if this increases any security feature of the Cosmos Hub. One thought was that this capability is similar to contract interactions which are possible on virtual machine blockchains like EVM chains. Those interactions introduced a new attack vector, called a re-entrancy bug, which was the culprit of "The DAO hack on Ethereum". We believe there is no risk of these kinds of attacks with Interchain Accounts because they require the interactions to be atomic and Interchain Accounts are asynchronous. #### Backwards Compatibility From 689c92ad4c53ae5ddc17648be29f782eed61d18c Mon Sep 17 00:00:00 2001 From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com> Date: Mon, 16 Dec 2024 11:15:55 +0200 Subject: [PATCH 3/4] typos delegator-faq.md --- docs/docs/delegators/delegator-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/delegators/delegator-faq.md b/docs/docs/delegators/delegator-faq.md index 50fe61b2e4b..fedeb1e9952 100644 --- a/docs/docs/delegators/delegator-faq.md +++ b/docs/docs/delegators/delegator-faq.md @@ -89,7 +89,7 @@ When tokenization is disabled, a lock is placed on the account, effectively prev ## Risks -Staking Atoms is not free of risk. First, staked Atoms are locked up, and retrieving them requires a 3 week waiting period called unbonding period. Additionally, if a validator misbehaves, a portion of their total stake can be slashed (i.e. destroyed). This includes the stake of their delegators. +Staking Atoms is not free of risk. First, staked Atoms are locked up, and retrieving them requires a 3-week waiting period called unbonding period. Additionally, if a validator misbehaves, a portion of their total stake can be slashed (i.e. destroyed). This includes the stake of their delegators. There is one main slashing condition: From 637ac141deff4394952e2549d908878b3fa647f9 Mon Sep 17 00:00:00 2001 From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com> Date: Mon, 16 Dec 2024 11:16:21 +0200 Subject: [PATCH 4/4] typos ledger.md --- docs/docs/resources/ledger.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/resources/ledger.md b/docs/docs/resources/ledger.md index 449b6651ad9..230026a4b8d 100644 --- a/docs/docs/resources/ledger.md +++ b/docs/docs/resources/ledger.md @@ -49,7 +49,7 @@ That's it! You can now use Keplr with your Ledger Nano S. You can use the [Keplr ### (Optional) Confirm your address -You can double check that Keplr is displaying the correct address directly on your Ledger Nano device. To do so: +You can double-check that Keplr is displaying the correct address directly on your Ledger Nano device. To do so: 1. Connect your Ledger to your computer and open the Cosmos application on the device. 2. Once the Cosmos app is open, click on the right button to access the `Show Address` option.