Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 2.3 KB

File metadata and controls

57 lines (41 loc) · 2.3 KB

Signet Node Components

CI License: MIT

Note: The legacy branch is under long-term maintenance and may receive active work. The main branch contains current work.

A collection of components for building the Signet node. These components implement core node functionality, but are potentially independently useful.

What's new in Signet?

Signet is a pragmatic Ethereum rollup that offers a new set of ideas and aims to radically modernize rollup technology.

  • No proving systems or state roots, drastically reducing computational overhead.
  • Market-based cross-chain transfers for instant asset movement.
  • A controlled block inclusion mechanism to combat block construction centralization.
  • Conditional transactions for secure, atomic cross-chain operations.

Signet extends the EVM, and is compatible with all existing Ethereum tooling. Using Signet does not require smart contract modifications, or Signet-specific knowledge. Signet does not have a native token.

Signet is just a rollup.

See the Signet docs for more info.

What's in the Components?

  • signet-node-types — Shim types wrapping reth's internal node types system to make it more usable in Signet.
  • signet-blobber — Blob retrieval and parsing, using blob explorers, Signet's Pylon, and the local node transaction API.
  • signet-rpc — An Ethereum JSON-RPC Server for Signet nodes. Makes heavy use of reth internals.
  • signet-host-reth — Reth ExEx implementation of the HostNotifier trait for signet-node.
  • signet-host-rpc — RPC-based implementation of the HostNotifier trait for signet-node.

Contributing

Please see CONTRIBUTING.md.

Note on Semver

This repo is UNPUBLISHED and may NOT respect semantic versioning between tagged versions. In general, it is versioned to match the signet-sdk version with which it is compatible. I.e. node-components@0.8.x is expected to be compatible with any signet-sdk 0.8.x version. However, a release of node-components@0.8.1 may have breaking changes from node-components@0.8.0.