Difference between revisions of "Snap Sync"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* <code>[[geth]]</code> | * <code>[[geth]]</code> | ||
* <code>[[op-geth]]</code> | * <code>[[op-geth]]</code> | ||
| + | * [[geth removedb]] | ||
== See also == | == See also == | ||
Revision as of 12:55, 13 August 2024
Snap Sync is a native feature of go-ethereum and can by optionally enabled in op-node and op-geth
Related
See also
- 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 - OP Stack,
op-, Superchain, Fault Proofs Explainer, Optimism monitorism - 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:
