Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@chainsafe/lodestar-types

Package Overview
Dependencies
Maintainers
5
Versions
840
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@chainsafe/lodestar-types

Typescript types required for lodestar

  • 0.38.0-dev.f74f9ef087
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
77
decreased by-92.24%
Maintainers
5
Weekly downloads
 
Created
Source

lodestar-types

npm License Eth Consensus Spec v1.1.10 ES Version Node Version

This package is part of ChainSafe's Lodestar project

Lodestar defines all datatypes defined in the Ethereum Consensus 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

Keywords

FAQs

Package last updated on 07 Jun 2022

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc