mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-12-02 17:45:54 +00:00
Add words from new features such as NFTs to the spell checker (#1615)
* Add words from new features such as NFTs to the spell checker * Add more proper nouns and general purpose words * Add more proper nouns and general purpose words * Update to use backticks * Update proper nouns and generic words * Fix style for words based on style checker report * Style/spelling fixes * Fix links broken by style/spelling updates * More edits for style * Finish updates to get style checker to pass Co-authored-by: mDuo13 <mduo13@gmail.com>
This commit is contained in:
Amarantha Kulkarni
committed by
GitHub
GitHub
parent
4c9ca0f219
commit
845422da7f
@@ -8,7 +8,8 @@ status: not_enabled
|
||||
---
|
||||
# Connect MetaMask to XRP Ledger Sidechain
|
||||
|
||||
MetaMask is an extension for accessing Harmony-enabled distributed applications (_dapps_) from your browser. The extension injects the XRP Ledger EVM sidechain Web3 API into every website's Javascript context, so that Web3 applications can read from the blockchain.
|
||||
MetaMask is an extension for accessing Harmony-enabled distributed applications (_dapps_) from your browser. The extension injects the XRP Ledger EVM sidechain Web3 API into every website's Javascript context, so that Web3 applications can read from the blockchain. <!-- SPELLING_IGNORE: dapps -->
|
||||
|
||||
This tutorial walks through the process of installing MetaMask, configuring it on the XRP Ledger EVM sidechain network, and importing an existing account using a previously generated private key.
|
||||
|
||||
## 1. Installing MetaMask
|
||||
|
||||
@@ -10,7 +10,7 @@ status: not_enabled
|
||||
|
||||
## Create Your Validator
|
||||
|
||||
Use your node consensus public key (`exrpvalconspub...`) to create a new validator by staking XRP tokens. You can find your validator pubkey by running:
|
||||
Use your node consensus public key (`exrpvalconspub...`) to create a new validator by staking XRP tokens. You can find your validator public key by running:
|
||||
|
||||
```bash
|
||||
exrpd tendermint show-validator
|
||||
@@ -36,17 +36,17 @@ exrpd tx staking create-validator \
|
||||
**Note** When specifying commission parameters, the `commission-max-change-rate` is used to measure % *point* change over the `commission-rate`. For example, 1% to 2% is a 100% rate increase, but only 1 percentage point.
|
||||
|
||||
|
||||
**Note** `Min-self-delegation` is a strictly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A `min-self-delegation` of `1000000` means your validator will never have a self-delegation lower than `1 axrp`.
|
||||
**Note** `Min-self-delegation` is a strictly positive integer that represents the minimum amount of self-delegated voting power your validator must always have. A `min-self-delegation` of `1000000` means your validator will never have a self-delegation lower than `1 axrp`. <!-- STYLE_OVERRIDE: will -->
|
||||
|
||||
You can confirm that you are in the validator set by using a third-party explorer.
|
||||
|
||||
## Edit Validator Description
|
||||
|
||||
You can edit your validator's public description. This info is to identify your validator, and is relied on by delegators when they decide to stake XRP tokens to a particular validator. Make sure to provide input for every flag below. If a flag is not included in the command, the field defaults to empty (`--moniker` defaults to the machine name), if the field has never been set, or remains the same, if it has been set in the past.
|
||||
You can edit your validator's public description. This info identifies your validator, and _delegators_ use it when they decide to stake XRP tokens to a particular validator. Make sure to provide input for every flag below. If a flag is not included in the command, the field defaults to empty (`--moniker` defaults to the machine name), if the field has never been set, or remains the same, if it has been set in the past. <!-- SPELLING_IGNORE: delegators --><!-- STYLE_OVERRIDE: defaults to -->
|
||||
|
||||
The <key_name> specifies which validator you are editing. If you choose to not include certain flags, remember that the --from flag must be included to identify the validator to update.
|
||||
|
||||
The `--identity` can be used as to verify identity with systems like Keybase or UPort. When using with Keybase `--identity` must be populated with a 16-digit string that is generated with a [keybase.io](https://keybase.io/) account. It is a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.
|
||||
The `--identity` can be used as to verify identity with systems like Keybase or UPort. When using with Keybase `--identity` must be populated with a 16-digit string that is generated with a [keybase.io](https://keybase.io/) account. It is a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile. <!-- SPELLING_IGNORE: uport -->
|
||||
|
||||
```bash
|
||||
exrpd tx staking edit-validator
|
||||
@@ -83,8 +83,9 @@ exrpd query slashing signing-info <validator-pubkey> --chain-id=<chain_id>
|
||||
```
|
||||
|
||||
## Unjail Validator
|
||||
<!-- SPELLING_IGNORE: unjail -->
|
||||
|
||||
When a validator is "jailed" for downtime, you must submit an `Unjail` transaction from the operator account in order to restore block proposer awards (depending on the zone fee distribution).
|
||||
When a validator is "jailed" for downtime, you must submit an `Unjail` transaction from the operator account to restore block proposer awards (depending on the zone fee distribution).
|
||||
|
||||
```bash
|
||||
exrpd tx slashing unjail --from=<key_name> --chain-id=<chain_id>
|
||||
@@ -98,7 +99,7 @@ Your validator is active if the following command returns anything:
|
||||
exrpd query tendermint-validator-set | grep "$(exrpd tendermint show-address)"
|
||||
```
|
||||
|
||||
You should now see your validator in one of the Exrp explorers. You are looking for the `bech32` encoded `address` in the `~/.exprd/config/priv_validator.json` file.
|
||||
You should now see your validator in one of the Exrp explorers. You are looking for the `bech32` encoded `address` in the `~/.exprd/config/priv_validator.json` file. <!-- SPELLING_IGNORE: exrp -->
|
||||
|
||||
**Note** To be in the validator set, you must have more total voting power than the 100th validator.
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ status: not_enabled
|
||||
---
|
||||
# EVM Sidechain Validator Security
|
||||
|
||||
Each validator candidate is encouraged to run its operations independently, as diverse setups increase the resilience of the network. Validator candidates should commence their setup phase now, in order to be on time for launch.
|
||||
Each validator candidate is encouraged to run its operations independently, as diverse setups increase the resilience of the network. Validator candidates should begin their setup phase now, to be on time for launch.
|
||||
|
||||
## Horcrux
|
||||
|
||||
@@ -22,15 +22,15 @@ For information on how to upgrade your validator infrastructure with Horcrux, re
|
||||
|
||||
## Tendermint KMS
|
||||
|
||||
Tendermint KMS is a signature service with support for Hardware Security Modules (HSMs), such as YubiHSM2 and Ledger Nano. It is intended to be run alongside XRP Ledger EVM Sidechain validators, ideally on separate physical hosts, providing defense-in-depth for online validator signing keys, double signing protection, and a central signing service that can be used when operating multiple validators in several zones.
|
||||
Tendermint KMS is a signature service with support for Hardware Security Modules (HSMs), such as YubiHSM 2 and Ledger Nano. It is intended to be run alongside XRP Ledger EVM Sidechain validators, ideally on separate physical hosts, providing defense-in-depth for online validator signing keys, double signing protection, and a central signing service that can be used when running multiple validators in several zones. <!-- SPELLING_IGNORE: kms, hsms, yubihsm, yubikey -->
|
||||
|
||||
## Hardware Security Modules (HSM)
|
||||
|
||||
You must ensure that an attacker cannot steal a validator's key. Otherwise, the entire stake delegated to the compromised validator at risk. Hardware security modules (HSM) help mitigate this risk.
|
||||
|
||||
HSMs must support `ed25519` signatures for Evmos. The [YubiHSM 2](https://www.yubico.com/products/hardware-security-module/) supports `ed25519` and can be used with this YubiKey [library](https://github.com/iqlusioninc/yubihsm.rs).
|
||||
HSMs must support **`ed25519` signatures for Evmos**. The [YubiHSM 2](https://www.yubico.com/products/hardware-security-module/) supports `ed25519` and can be used with this YubiKey [library](https://github.com/iqlusioninc/yubihsm.rs). <!-- SPELLING_IGNORE: evmos -->
|
||||
|
||||
**IMPORTANT**: The YubiHSM can protect a private key but **cannot ensure** in a secure setting that it will not sign the same block twice.
|
||||
**IMPORTANT**: The YubiHSM can protect a private key but **cannot ensure** in a secure setting that it will not sign the same block twice. <!-- STYLE_OVERRIDE: will -->
|
||||
|
||||
## Sentry Nodes (DDOS Protection)
|
||||
|
||||
@@ -38,11 +38,11 @@ Validators are responsible for ensuring that the network can sustain denial of s
|
||||
|
||||
One recommended way to mitigate these risks is for validators to carefully structure their network topology in a sentry node architecture.
|
||||
|
||||
Validator nodes should only connect to full-nodes they trust; either they operate these nodes themselves, or the nodes are run by other validator administrators they know personally. A validator node typically runs in a data center. Most data centers provide direct links to the networks of major cloud providers. The validator can use those links to connect to sentry nodes in the cloud. This shifts the burden of denial-of-service from the validator's node directly to its sentry nodes, and might require new sentry nodes be spun up or activated to mitigate attacks on existing ones.
|
||||
Validator nodes should only connect to full-nodes they trust; either they run these nodes themselves, or the nodes are run by other validator administrators they know personally. A validator node typically runs in a data center. Most data centers provide direct links to the networks of major cloud providers. The validator can use those links to connect to sentry nodes in the cloud. This shifts the burden of denial-of-service from the validator's node directly to its sentry nodes, and might require new sentry nodes be spun up or activated to mitigate attacks on existing ones.
|
||||
|
||||
Sentry nodes can be quickly spun up or change their IP addresses. Because the links to the sentry nodes are in private IP space, an internet-based attacked cannot disturb them directly. This ensures that the validator's block proposals and votes always make it to the rest of the network.
|
||||
|
||||
To setup your sentry node architecture:
|
||||
To set up your sentry node architecture:
|
||||
|
||||
1. Edit your validator node's `config.toml` file:
|
||||
|
||||
|
||||
@@ -11,6 +11,7 @@ status: not_enabled
|
||||
This getting started tutorial walks you through the steps to set up your account and transfer funds using the EVM sidechain bridge.
|
||||
|
||||
## 1. Create an Account Using an EVM Compatible Wallet
|
||||
<!-- STYLE_OVERRIDE: wallet -->
|
||||
|
||||
In order to interact with the network, you need to create an account in the EVM sidechain. To create and manage this account you can use any EVM compatible wallet such as MetaMask.
|
||||
|
||||
@@ -61,7 +62,7 @@ To connect a MetaMask wallet to the bridge, go to the [EVM Sidechain bridge](htt
|
||||
|
||||
|
||||
|
||||
### 2. Initiate the Transfer of Funds
|
||||
### 2. Start the Transfer of Funds
|
||||
|
||||
Now that both Xumm and MetaMask wallets are connected to the bridge, you can select the direction of the bridge, the amount to send, and the destination address.
|
||||
|
||||
@@ -71,7 +72,7 @@ Now that both Xumm and MetaMask wallets are connected to the bridge, you can sel
|
||||
- Commission: The bridge applies a commission for every transaction completed. This is to prevent spam and distributed denial of service attacks (DDOS).
|
||||
- **Destination address**: The address on the destination chain where you want to receive funds.
|
||||
|
||||
|
||||
|
||||
|
||||
Enter the details for your transaction and click **Transfer**. Review the details of the transaction carefully before accepting the transaction in the corresponding wallet.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user