mirror of https://github.com/ChainSafe/lodestar.git synced 2026-01-09 15:48:08 -05:00

Files

Nico Flaig 889b1c4475 chore: remove merge transition code (#8680 )

**Motiviation**

All networks have completed the merge transition and most execution
clients no longer support pre-merge so it's not even possible anymore to
run a network from a genesis before bellatrix, unless you keep it to
phase0/altair only, which still works after this PR is merged.

This code is effectively tech debt, no longer exercised and just gets in
the way when doing refactors.

**Description**

Removes all code related to performing the merge transition. Running the
node pre-merge (CL only mode) is still possible and syncing still works.
Also removed a few CLI flags we added for the merge specifically, those
shouldn't be used anymore. Spec constants like
`TERMINAL_TOTAL_DIFFICULTY` are kept for spec compliance and ssz types
(like `PowBlock`) as well. I had to disable a few spec tests related to
handling the merge block since those code paths are removed.

Closes https://github.com/ChainSafe/lodestar/issues/8661

2025-12-12 10:18:23 +07:00

src

chore: remove merge transition code (#8680 )

2025-12-12 10:18:23 +07:00

test

feat: implement epbs state transition (#8507 )

2025-12-04 08:35:47 -08:00

LICENSE

Rename package-level directories (#2230 )

2021-03-23 17:44:17 -05:00

package.json

chore: bump package versions to 1.37.0

2025-11-28 10:17:20 -05:00

README.md

feat: support and test node 24 (#8645 )

2025-12-03 13:32:11 -05:00

tsconfig.build.json

deps: upgrade tyepscript to 5.7 (#7160 )

2025-02-25 14:24:14 +01:00

tsconfig.json

chore: fix broken type check for test files (#7567 )

2025-03-13 13:47:22 +00:00

README.md

lodestar-params

This package is part of ChainSafe's Lodestar project

Lodestar defines all constants and presets defined in the Ethereum Consensus spec. This can be used in conjunction with other Lodestar libraries to interact with the Ethereum consensus.

Installation

npm install @lodestar/params

Usage

The Lodestar params package contains several items used in all downstream Lodestar libraries:

Fork names
Constants
Presets

Fork names

Many downstream components are namespaced on fork names, or otherwise rely on knowing the fork names ahead of time. The Lodestar params package exports an enum ForkName the enumerates all known fork names.

import {ForkName} from "@lodestar/params";

// dummy data
let forkName = "phase0";

switch (forkName) {
  case ForkName.phase0:
  case ForkName.altair:
  case ForkName.bellatrix:
  default:
}

Constants

All constants defined in the spec are exported verbatim.

import {GENESIS_SLOT} from "@lodestar/params";

Presets

Presets are defined in the spec as "constantish" and can only be configured at build-time. These are meant to be treated as constants, and indeed are treated as constants by all downstream Lodestar libraries. The default preset is mainnet. The only other preset defined is minimal, used only in testing environments.

The active preset is exported under the ACTIVE_PRESET named export.

import {ACTIVE_PRESET, SLOTS_PER_EPOCH} from "@lodestar/params";

The preset may be set in one of two ways:

by setting the LODESTAR_PRESET environment variable
by executing the setActivePreset(preset: Preset) function

Important Notes:

Interacting with and understanding the active preset is only necessary in very limited testing environments, like for ephemeral testnets
The minimal preset is NOT compatible with the mainnet preset.
using setActivePreset may be dangerous, and only should be run once before loading any other libraries. All downstream Lodestar libraries expect the active preset to never change.
Preset values can be overridden by executing setActivePreset(presetName: PresetName, overrides?: Partial<BeaconPreset>) and supplying values to override.
The Lodestar CLI exposes setActivePreset through --presetFile flag which allows to override the active preset with custom values from file.

License

Apache-2.0 ChainSafe Systems