Privileged Roles in BOB Mainnet
BOB uses the OP Stack, just like Optimism Mainnet and Base. As a result, BOB is on the same Pragmatic Path to Decentralization.
For now, OP Stack chains still include "privileged" roles that allow certain addresses to carry out specific actions. Read this page to understand these roles, why they exist, and what risks they pose.
L1 Proxy Admin
The L1 Proxy Admin is an address that can be used to upgrade most BOB system contracts.
Risks
- Compromised L1 Proxy Admin could upgrade contracts to malicious versions.
- Compromised L1 Proxy Admin could remove or lock ETH or tokens in the Standard Bridge.
- Compromised L1 Proxy Admin could fail to mitigate a risk as described on this page.
Mitigations
- L1 Proxy Admin owner is a 4-of-6 multisig.
Address
L2 Proxy Admin
The L2 Proxy Admin is an address that can be used to upgrade most BOB system contracts on L2.
Risks
- Compromised L2 Proxy Admin could upgrade contracts to malicious versions.
- Compromised L2 Proxy Admin could remove or lock ETH or tokens in the Standard Bridge.
- Compromised L2 Proxy Admin could fail to mitigate a risk as described on this page.
Mitigations
- L2 Proxy Admin is a 4-of-6 multisig.
Address
System Config Owner
The System Config Owner is an address that can be used to change the values within the SystemConfig
contract on Ethereum.
Risks
- Compromised System Config Owner could cause a temporary network outage.
- Compromised System Config Owner could cause users to be overcharged for transactions.
Mitigations
- System Config Owner is a 4-of-6 multisig.
- System Config Owner can be replaced by the L1 Proxy Admin.
Address
Batcher
Description
The Batcher is a software service that submits batches of transactions to Ethereum on behalf of the current BOB Sequencer. BOB nodes will look for transactions from this address to find new batches of L2 transactions to process.
Risks
- Batcher address is typically a hot wallet.
- Compromised batcher address can cause L2 reorgs or sequencer outages.