JSPM

@chainsafe/lodestar-types

0.34.0-dev.60+e274b2139d
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 113
  • Score
    100M100P100Q76368F
  • License Apache-2.0

Typescript types required for lodestar

Package Exports

  • @chainsafe/lodestar-types
  • @chainsafe/lodestar-types/altair
  • @chainsafe/lodestar-types/altair.js
  • @chainsafe/lodestar-types/bellatrix
  • @chainsafe/lodestar-types/bellatrix.js
  • @chainsafe/lodestar-types/lib/allForks
  • @chainsafe/lodestar-types/lib/allForks/index.js
  • @chainsafe/lodestar-types/lib/allForks/types
  • @chainsafe/lodestar-types/lib/allForks/types.js
  • @chainsafe/lodestar-types/lib/index.js
  • @chainsafe/lodestar-types/lib/phase0
  • @chainsafe/lodestar-types/lib/phase0/index.js
  • @chainsafe/lodestar-types/phase0
  • @chainsafe/lodestar-types/phase0.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@chainsafe/lodestar-types) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

lodestar-types

npm License ETH2.0_Spec_Version 1.0.0 ES Version Node Version

This package is part of ChainSafe's Lodestar project

Lodestar defines all datatypes defined in the Ethereum Consensus / Eth2 spec. This tooling can be used for any Typescript project looking to operate on these types. Both Typescript interfaces and Simple Serialize (SSZ) methods are exported for consumers.

Installation

npm install @chainsafe/lodestar-types

Usage

The lodestar types library organizes datatypes on several dimensions:

  • Typescript interfaces vs SSZ objects
  • By fork

Typescript interfaces

Lodestar types are all defined as typescript interfaces. These interfaces can be used independently, and are used throughout downstream Lodestar packages (eg: in the beacon node).

These interfaces are accessible via named exports.

import {Epoch} from "@chainsafe/lodestar-types";

const x: Epoch = 5;

SSZ objects

Lodestar types are also defined as SSZ objects. These "Type" objects provide convenient methods to perform SSZ operations (serialization / deserialization / merkleization/etc). The library exports a singleton object containing all SSZ objects.

import {Type} from "@chainsafe/ssz";
import {ssz, Epoch} from "@chainsafe/lodestar-types";

const EpochType: Type<Epoch> = ssz.Epoch;

const e = EpochType.defaultValue();

By fork

Lodestar types support multiple different consensus forks. In order to easily differentiate types that may change across forks, types are organized in namespaces according to the fork in which they're introduced. Types introduced in phase 0 are available under the phase0 namespace. Types introduced in altair are available under the altair namespace.

import {altair, phase0, ssz} from "@chainsafe/lodestar-types";

const phase0State: phase0.BeaconState = ssz.phase0.BeaconState.defaultValue();
const altairState: altair.BeaconState = ssz.altair.BeaconState.defaultValue();

Primitive types are directly available without a namespace.

import {Epoch, ssz} from "@chainsafe/lodestar-types";

const epoch: Epoch = ssz.Epoch.defaultValue();

In some cases, we need interfaces that accept types across all forks, eg: when the fork is not known ahead of time. Typescript interfaces for this purpose are exported under the allForks namespace. SSZ Types typed to these interfaces are also provided under an allForks namespace, but keyed by ForkName.

import {ForkName} from "@chainsafe/lodestar-params";
import {allForks, ssz} from "@chainsafe/lodestar-types";

const state: allForks.BeaconState = ssz.allForks[ForkName.phase0].BeaconState.defaultValue();

License

Apache-2.0 ChainSafe Systems