Difference between revisions of "Op-geth"
Jump to navigation
Jump to search
| Line 33: | Line 33: | ||
* [[30303]] | * [[30303]] | ||
* [[Snap Sync]] | * [[Snap Sync]] | ||
| − | |||
| − | |||
* [[geth (no options)]] | * [[geth (no options)]] | ||
| + | * [[alpine:latest]] | ||
== See also == | == See also == | ||
Revision as of 16:55, 15 October 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
INFO Chain head was updatedINFO Started P2P networkingno peers ready to handle block requests for more P2P requests for L2 block historSIGEGVpanic.goinvalid memorysegmentation violation codeStarting work on payloadBlock building is interruptedUnclean shutdown detectedBlockchain stoppedINFO HTTP server started
Related
See also
op-geth, consecutive5xxErrors- OP Stack:
op-, op-geth, op-node, op-proposer, op-batcher, op-contracts, op-challenger, op-heartbeat, op-ufm, op-service, 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
Advertising:
