Difference between revisions of "Op-geth"
Jump to navigation
Jump to search
(→Errors) |
|||
| Line 20: | Line 20: | ||
* <code>[[invalid memory]]</code> | * <code>[[invalid memory]]</code> | ||
* <code>[[segmentation violation code]]</code> | * <code>[[segmentation violation code]]</code> | ||
| − | + | * <code>[[Starting work on payload]]</code> | |
== Related == | == Related == | ||
Revision as of 14:43, 16 August 2024
op-geth creates and proposes new blocks on the Optimism L2
--syncmode= [ snap (default) | full ] --gcmode= [ archive (not default) ]
--rollup.sequencerhttp --rollup.historicalrpc --rollup.disabletxpoolgossip
Errors
no peers ready to handle block requests for more P2P requests for L2 block historSIGEGVpanic.goinvalid memorysegmentation violation codeStarting work on payload
Related
See also
op-geth, consecutive5xxErrors, op-geth --rollup.sequencerhttp, genesis.json- OP Stack:
op-, op-geth, op-node, op-proposer, op-batcher, op-contracts, op-challenger, op-heartbeat, op-ufm, op-service, op-deployer, Snap Sync, op-conductor, op-dispute-mon - 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:
