Difference between revisions of "Optimism Censorship Bug Disclosure"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* {{Sequencer}} | * {{Sequencer}} | ||
* {{Optimism}} | * {{Optimism}} | ||
| + | |||
| + | [[Category:Crypto]] | ||
Revision as of 14:19, 23 August 2024
- Chain ID was not validated
- proxyd, a custom JSON-RPC load balancer, which restricts the volume of requests the main sequencer has to manage.
- Transactions are discarded before contributing to the rate limit if the nonce is lower than the account’s current nonce
- LayerZero’s Executor and Oracle accounts, Across’ Relayer, Synapse’s Executor, Hop Bridge’s ETH Bonder, LayerSwap’s Relayer, Aave’s Deployer, Uniswap’s Deployer, and even many of Optimism’s multisig owners and the usual wallet transaction executor
Related
See also
- Sequencer, Sequencer Level Security (SLS), Zircuit, Hypernative.io, Replica, Single-sequencer protocols
- Optimism,
OP, OP Stack, OP Architecture,op-, Superchain, Optimism Bedrock, Proxyd, Crypto sequencer, rollup, Optimistic Rollup Protocol, Optimism Blobs, Optimism monitorism, fault-mon,eth-optimism/sdk,L2OutputOracle.sol, OptimismPortal.sol, OP Sepolia Testnet (11155420), OP Labs, Optimism Foundation, Fault Proof, Ecotone, Fjord, Rollup node, L2 Chain Derivation Specification, Fastnode.io, OP Contracts Manager (OPCM)
Advertising:
