Testnet Peggo
Last updated
Last updated
First, update the PEGGO_ETH_RPC in the .env file with a valid Sepolia EVM RPC Endpoint.
To set up your own Sepolia full node, follow the instructions . It's possible to use an Alchemy or Infura RPC, but keep in mind that the Peggo bridge is still under development, and the request amount it makes to the RPC is not optimized. Ensure it does not incur high costs on your account.
Peggo also requires access to your validator's Cosmos and Ethereum credentials to sign transactions for the corresponding networks.
There are two ways to provide the credential access - a keyring with encrypted keys, or just private key in plaintext.
Update the PEGGO_COSMOS_FROM to your validator key name (or account address) and PEGGO_COSMOS_FROM_PASSPHRASE to your Cosmos Keyring passphrase. Please note that the default keyring backend is file and it will try to locate keys on disk.
Keyring path must be pointing to homedir of your injectived node, if you want reuse the keys from there.
Learn more about Keyring setup .
Simply update the PEGGO_COSMOS_PK with your Validator's Account private key.
To obtain your validator's Cosmos private key, run injectived keys unsafe-export-eth-key $VALIDATOR_KEY_NAME.
This method is insecure and is not recommended.
There are two ways to provide the credential access - a Geth keystore with encrypted keys, or just private key in plaintext.
Simply create a new private key store and update the following env variables:
PEGGO_ETH_KEYSTORE_DIR
PEGGO_ETH_FROM
PEGGO_ETH_PASSPHRASE
Example is provided below.
Now, you can set env variables like this:
Simply update the PEGGO_ETH_PK with a new Ethereum Private Key from a new account.
You can verify successful registration by checking for your Validator's mapped Ethereum address on https://staking-lcd-testnet.injective.network/peggy/v1/valset/current.
This starts the Peggo bridge (relayer / orchestrator).
Add peggo.service file with below content under /etc/systemd/system/peggo.service
Then, run the following commands to configure Environment variables, start and stop the peggo relayer.
This is an advanced DevOps topic, consult with your sysadmin.
Some sections of the Injective Staking documentation will guide you through using this key for governance purposes, i.e., submitting transactions and setting up an Ethereum bridge. In order to protect the keys from unauthorized access, even when the keyring passphrase is leaked via configs, you can set OS permissions to allow disk access to injectived / peggo processes only.
In Linux systems like Debian, Ubuntu and RHEL, this can be achieved using POSIX Access Control Lists (ACLs). Before beginning to work with ACLs, the file system must be mounted with ACLs turned on. There are some official guides for each distro:
First, update the PEGGO_ETH_RPC in the .env file with a valid Ethereum EVM RPC Endpoint.
Peggo also requires access to your validator's delegated Injective Chain account and Ethereum key credentials to sign transactions for the corresponding networks.
Your peggo relayer can either
Use an explicitly delegated account key specific for sending validator specific Peggy transactions (i.e. ValsetConfirm, BatchConfirm, and SendToCosmos transactions), or
Simply use your validator's account key.
For isolation purposes, we recommend creating a delegated Cosmos key to send Injective transactions instead of using your validator account key.
To create a new key, run:
Then, ensure that your orchestrator inj address has INJ balance.
To obtain your orchestrators's inj address, run:
You can transfer INJ from your validator account to orchestrator address using this command:
Example:
You can then verify that your orchestrator account has INJ balances by running:
peggoPeggo supports two options to provide Cosmos signing key credentials - using the Cosmos keyring (recommended), or by providing a plaintext private key.
In the .env file, first specify the PEGGO_COSMOS_FROM and PEGGO_COSMOS_FROM_PASSPHRASE corresponding to your peggo account signing key.
If you are using a delegated account key configuration as recommended above, this will be your $ORCHESTRATOR_KEY_NAME and passphrase, respectively. Otherwise, this should be your $VALIDATOR_KEY_NAME and associated validator passphrase.
Please note that the default keyring backend is file and that, as such, peggo will try to locate keys on disk by default.
To use the default injectived key configuration, you should set the keyring path to the home directory of your injectived node, e.g. ~/.injectived.
In the .env file, specify the PEGGO_COSMOS_PK corresponding to your peggo account signing key.
If you are using a delegated account key configuration as recommended above, this will be your orchestrator account's private key. Otherwise, this should be your validator's account private key.
To obtain your orchestrator's Cosmos private key (if applicable), run:
To obtain your validator's Cosmos private key (if applicable), run:
Again, this method is less secure and is not recommended.
peggoPeggo supports two options to provide signing key credentials - using the Geth keystore (recommended), or by providing a plaintext Ethereum private key.
Simply create a new private key store and update the following env variables:
PEGGO_ETH_KEYSTORE_DIR
PEGGO_ETH_FROM
PEGGO_ETH_PASSPHRASE
For convience, an example is provided below.
Make sure you heed the warnings that geth provides, particularly in backing up your key file so that you don't lose your keys by mistake. We also recommend not using any quote or backtick characters in your passphrase for peggo compatibility purposes.
You should now set the following env variables:
Then, ensure that your Ethereum address has enough ETH.
Simply update the PEGGO_ETH_PK with a new Ethereum Private Key from a new account.
Then, ensure that your Ethereum address has ETH.
You can register orchestrator and ethereum address only once. It CANNOT be updated later. So Check twice before running below command.
To obtain your validator's inj address, run, injectived keys list $VALIDATOR_KEY_NAME
To obtain your orchestrators's inj address, injectived keys list $ORCHESTRATOR_KEY_NAME
Example:
You can verify successful registration by checking for your Validator's mapped Ethereum address on https://testnet.lcd.injective.dev/peggy/v1/valset/current.
This starts the Peggo bridge (relayer / orchestrator).
Add peggo.service file with below content under /etc/systemd/system/peggo.service
Then, run the following commands to configure Environment variables, start and stop the peggo relayer:
This is an advanced DevOps topic, consult with your sysadmin.
Some sections of the Injective Staking documentation will guide you through using this key for governance purposes, i.e., submitting transactions and setting up an Ethereum bridge. In order to protect the keys from unauthorized access, even when the keyring passphrase is leaked via configs, you can set OS permissions to allow disk access to injectived / peggo processes only.
In Linux systems like Debian, Ubuntu and RHEL, this can be achieved using POSIX Access Control Lists (ACLs). Before beginning to work with ACLs, the file system must be mounted with ACLs turned on. There are some official guides for each distro:
You can find instructions for securely creating a new Ethereum account using a keystore in the Geth Documentation .
Next, ensure that your Ethereum addresss has Sepolia ETH. You can request Sepolia ETH from the public faucet .
Next, ensure that your Ethereum addresss has Sepolia ETH. You can request Sepolia ETH from the public faucet .
Learn more about Cosmos Keyring setup . Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually, the keyring is located within node's homedir, i.e. ~/.injectived/keyring-file.
To create your own Ethereum full node, you can follow our instructions . It's possible to use an external Ethereum RPC provider such as Alchemy or Infura, but keep in mind that the Peggo bridge relayer uses heavy use of eth_getLogs calls which may increase your cost burden depending on your provider.
You can also read more about the Cosmos Keyring setup .
You can find instructions for securely creating a new Ethereum account using a keystore in the Geth Documentation .
Learn more about Cosmos Keyring setup . Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually, the keyring is located within node's homedir, i.e. ~/.injectived/keyring-file.
If you'd like to inspect the Peggo orchestrator source code and contribute, you can do so at