Never share your keystore files - they contain your encrypted private keys
Use strong passwords for keystore encryption - Back up your keystore
securely - The ethPassword only protects the keystore file - your actual
private key is stored encrypted within the keystore - Never share your wallet
private key. In case of accidental public exposure - remove any funds &
change your wallet immediately
Many of the public RPCs apply rate-limits, including the third-party providers.
These free-tier RPC’s should be sufficient to run a single Gateway with the latest versions of Livepeer.Chainlist provides a full list of public Arbitrum One RPCs (including the Arbitrum public RPC):
If scaling beyond one Gateway, or running a large number of concurrent requests, you will need to pay for additional RPC capacity on one of the RPC providers.Some popular third-party RPC providers include:
Alternatively, you can also self-host your own Arbitrum node.Self-hosting an RPC is covered in the Arbitrum Self-Hosting Guide
3
ETH Account `-ethAcctAddr`
Blockchain wallets (accounts) have both a public account address (starting with “0x…”) and a private key.This field is for your public wallet address.
ONLY use your PUBLIC Wallet Address in this field.NEVER use your PRIVATE key. A public address is akin to your bank account number, a private key is like your bank PIN or password.
Livepeer automatically creates a wallet for you if this field is empty.-ethAcctAddr=""
Your public wallet address: 0x...Example: 0xc7653d426f2ec8bc33cdde08b15f535e2eb2f523
See All Account Setup Options
You can
Use an existing Ethereum wallet address (e.g., from MetaMask, hardware wallet, etc.)
Let Livepeer automatically create a new wallet address. See code accountmanager.go
Existing Address
Automatic Wallet
You can use any existing Ethereum wallet address which can transact on Arbitrum.You will use Arbitrum One Mainnet to transact on the Livepeer network as this is significantly cheaper than using Ethereum, so ensure your wallet can transact on Arbitrum.
It’s advisable to use a wallet you own the private keys for rather than an exchange wallet.
The following guides are provided as a reference only - no recommendation is made for any specific wallet provider.
Livepeer will automatically create a new wallet for you if you do not provide an existing wallet address.
Simply leave the -ethAcctAddr flag empty and Livepeer will create a new wallet (and keystore) for you.
复制
询问AI
# Automatic Account Address-ethAcctAddr=""
4
ETH Password `-ethPassword`
This is NOT your wallet private key.Choose a strong password to secure your keystore file.Make sure to never share or lose access to either the password or the keystore
file
Think of this flag as -keystorePassword - it is the path to a password.txt file containing a (strong) password chosen by you.This password is used to decrypt the keystore file and access the (encrypted) private key.
Livepeer will create the keystore automatically on running the Gateway if you leave this flag empty: -ethKeystorePath=""
To bring your existing Ethereum account to Livepeer, you need to create a keystore file
with your private key and place it in the correct directory structure.The keystore files follow Ethereum’s UTC-timestamp-address format.
These files, often referred to as “UTC / JSON Wallets” or “Web3 Secret Storage Definition” files,
are encrypted local files that contain your Ethereum private key, allowing access to your account.Livepeer uses standard Ethereum keystore encryption, so any tool that creates Ethereum keystores will work.
Create a keystore file using Livepeer devtools or Ethereum tooling.
# Create directory mkdir %USERPROFILE%\.lpData\keystore # Run Livepeer - it will create account and prompt for password livepeer.exe -gateway -network arbitrum-one-mainnet -ethUrl=<RPC_URL>
Otherwise you can use Ethereum tools to create the keystore - instructions below.
If you are here, It is assumed you understand the security implications of exporting your private key and are able to vet & install any required software and convert linux bash commands to your own OS.Livepeer does not endorse or recommend any particular site or tools provided.
See Ethereum Tooling Setup
To create the keystore file, you can use one of the following methods:
Using Docker: Run the container interactively
Using geth (Ethereum’s development tool)
Using eth-cli (Ethereum’s command line tool)
Using node
Using web-based sites (not recommended)
You will need to:
Export your private key from your existing wallet
Create a keystore file with your private key
Create a password file with a strong password
Place the keystore file and password file in the correct directory
Create a password.txt file containing a (strong) password chosen by you.
This password is used to decrypt the keystore file and access the private key.
Make sure to never share or lose access to either the password or the keystore file
复制
询问AI
# Create password file with the same password you just usedecho "YOUR_PASSWORD" > ~/.lpData/eth-secret.txt# Secure it (Linux/Mac)chmod 600 ~/.lpData/eth-secret.txt
4
Create Password File & Configure Directory
After creating the keystore with geth or eth-cli, you must manually create the password file.
复制
询问AI
# geth creates the keystore but does NOT save the passwordgeth account import --datadir ~/.lpData/arbitrum-one-mainnet/# Enter private key: xxxxxx# Enter password: yourpassword# ✓ Keystore created# YOU must manually create the password fileecho "yourpassword" > ~/.lpData/eth-secret.txt
Place it in Livepeer’s keystore directory & configure Livepeer to use your account.
An Ethereum private key is a 256-bit random integer.
For user presentation and interoperability across most software,
this number is nearly always represented as a 64-character hexadecimal string
Create Livepeer Gateway ETH accountIn this step we need to start the Gateway in order to create an Ethereum
account.
复制
询问AI
docker compose run -it gateway
When prompted for the ETH password, enter a strong password to secure your
Ethereum account. This password is used to decrypt and access the ETH private
key.
Make sure to never share or lose access to either the password or
the keystore file.
Keep this password handy, we will use it in the following steps.
After you see the message that the Ethereum account has been unlocked, CTRL+C to
exit the Livepeer docker instance.Using the previously created ETH password, create the eth-secret file
This password is used to decrypt the keystore file and access the private key.
Make sure to never share or lose access to either the password or the keystore
file
After confirming your password close the terminal.