>=0.5.28
, connecting to Arbitrum Mainnet after the
LIP-73 block
.
migrate
transaction.
If you do not have ETH in your wallet, you can add some using another wallet
or an on-ramp so you can buy enough for the migrate
transaction.
livepeer_cli
,
instead.
go-livepeer
release >= 0.5.28
.RPC url
for
Arbitrum:
RPC url
using a third-party service (e.g.,
Alchemy or Infura).
RPC url
for
Arbitrum. We recommend using
the Offchain Labs public testnet endpoint.
Alternatively, you can:
RPC url
using a third-party service,For example:
migrate
transaction.
Note: You do not have to use the same wallet you use for your orchestrator. However, if you are using a different wallet to submit the transaction, you will still need to access the wallet that you use for your orchestrator so that you can sign a typed data message.For example:
migrate
transaction:
You can sign to authorize the migration transaction with one of the
following:
4a. Sign using a connected wallet.
If you prefer to sign using the wallet that you have connected to the
explorer, click “Approve Migration” and approve the transaction using your
browser extension.
livepeer_cli
.
If you prefer to sign a typed data message through the livepeer_cli
,
connect your wallet to the explorer with any other account. You will be
prompted to enter the public address of the orchestrator you wish to migrate.
Note: If you are signing with the CLI and your connected wallet is NOT your orchestrator wallet, the stake amount will not appear until after you enter your Ethereum account address.
Windows
users, after pasting the typed data you will need to
type ctrl+Z
, instead of ctrl+D
.
Approve Migration
to send the transaction to Ethereum. The connected
browser wallet will pay gas, but it will use the provided signature.
migrate
transaction has been confirmed (this usually takes up to
10 minutes between mainnet and Arbitrum), you should see a link to your
profile where you will be able to see your newly claimed balances.
You will see an Arbiscan link to the transaction id
to view the submitted transaction.
Note: If you prefer to run your own Arbitrum node, you should start it at this time. Otherwise, you should find the Arbitrum RPC Url that you created at the beginning of this guide.5b. Restart your Orchestrator with an updated configuration Once you are ready, you should restart your orchestrator using your usual flags, changing only the
network
and ethUrl
.
chainID of 4
, but got 421611
instead. You may have
changed networks without changing network name
or datadir
.
This indicates your testnet setup is trying to access the same .lpData
that it
used for mainnet, and it is finding a conflict on chainId
.
To fix this error:
-datadir
flag when you start your
Orchestrator. Specify only the directory, not the file.
Additionally, you may need to copy your keystore to
/.lpData/arbitrum-one-< mainnet / rinkeby >/keystore
.
Set orchestrator config
:
6a. Select the following option using livepeer_cli
:
13: Set orchestrator config
6b. Acquire some arbETH
to pay for the transaction: