QuipNetwork/quip-validatorPublic

A rust implementation of the Quip Protocol forked from Substrate

AI summary: A minimal, out-of-the-box Substrate node template for rapid blockchain prototyping in Rust.

Stars
5.6K
Forks
31
Watchers
7
Open issues
17
Open PRs
0
Contributors
~6
Commits
370
Branches
72

RustUnlicenseCreated Apr 2, 2026Last push 3d ago+-1 stars this week

Quick answers

What is quip-validator?
A minimal, out-of-the-box Substrate node template for rapid blockchain prototyping in Rust.
What does quip-validator do?
The Quip Protocol RS repository provides a streamlined, functional Substrate node template designed to serve as a starting point for building custom blockchains. It pre-configures essential components of the Substrate framework, allowing developers to immediately compile and run a local, single-node network without complex initial setup. The project focuses on minimizing boilerplate code, providing a clean slate for developers to integrate their own custom runtime logic, known as pallets. By offering a ready-to-run environment, it significantly accelerates the initial prototyping phase for decentralized applications and bespoke blockchain networks.
Who is quip-validator for?
Blockchain developers, Rust engineers, and students looking for a reliable, minimal starting point to build custom networks using the Substrate framework. Familiarity with the relevant ecosystem workflows is highly recommended for optimal usage.
How do I get started with quip-validator?
cargo build --release
How popular is quip-validator on GitHub?
QuipNetwork/quip-validator has 5,629 stars and 31 forks on GitHub, and gained -1 stars in the last 7 days.
What license does quip-validator use?
QuipNetwork/quip-validator is released under the Unlicense license.

Star history

since Jul 28, 2026
02K4KJul 2026Sep 2026Oct 2026Nov 2026
5.6K stars as of Nov 17, 2026. Measured daily since Jul 28, 2026; GitHub no longer exposes earlier star timestamps.

Update history

1 recorded
  • Oct 4, 2026Previously tracked as QuipNetwork/quip-protocol-rs; its 1 daily snapshot and 1 trending appearance were merged into this profile. Stars: 5,650 on 2026-07-28 under the old name, 5,636 on 2026-10-04 (-14).

Contribution activity

commits per day, last 52 weeks
NovDecJanFebMarAprMayJunJulAugSepOctNovMonWedFri2025-11-23: 0 commits2025-11-24: 0 commits2025-11-25: 0 commits2025-11-26: 0 commits2025-11-27: 0 commits2025-11-28: 0 commits2025-11-29: 0 commits2025-11-30: 0 commits2025-12-01: 0 commits2025-12-02: 0 commits2025-12-03: 0 commits2025-12-04: 0 commits2025-12-05: 0 commits2025-12-06: 0 commits2025-12-07: 0 commits2025-12-08: 0 commits2025-12-09: 0 commits2025-12-10: 0 commits2025-12-11: 0 commits2025-12-12: 0 commits2025-12-13: 0 commits2025-12-14: 0 commits2025-12-15: 0 commits2025-12-16: 0 commits2025-12-17: 0 commits2025-12-18: 0 commits2025-12-19: 0 commits2025-12-20: 0 commits2025-12-21: 0 commits2025-12-22: 0 commits2025-12-23: 0 commits2025-12-24: 0 commits2025-12-25: 0 commits2025-12-26: 0 commits2025-12-27: 0 commits2025-12-28: 0 commits2025-12-29: 0 commits2025-12-30: 0 commits2025-12-31: 0 commits2026-01-01: 0 commits2026-01-02: 0 commits2026-01-03: 0 commits2026-01-04: 0 commits2026-01-05: 0 commits2026-01-06: 0 commits2026-01-07: 0 commits2026-01-08: 0 commits2026-01-09: 0 commits2026-01-10: 0 commits2026-01-11: 0 commits2026-01-12: 0 commits2026-01-13: 0 commits2026-01-14: 0 commits2026-01-15: 0 commits2026-01-16: 0 commits2026-01-17: 0 commits2026-01-18: 0 commits2026-01-19: 0 commits2026-01-20: 0 commits2026-01-21: 0 commits2026-01-22: 0 commits2026-01-23: 0 commits2026-01-24: 0 commits2026-01-25: 0 commits2026-01-26: 0 commits2026-01-27: 0 commits2026-01-28: 0 commits2026-01-29: 0 commits2026-01-30: 0 commits2026-01-31: 0 commits2026-02-01: 0 commits2026-02-02: 0 commits2026-02-03: 0 commits2026-02-04: 0 commits2026-02-05: 0 commits2026-02-06: 0 commits2026-02-07: 0 commits2026-02-08: 0 commits2026-02-09: 0 commits2026-02-10: 0 commits2026-02-11: 0 commits2026-02-12: 0 commits2026-02-13: 0 commits2026-02-14: 0 commits2026-02-15: 0 commits2026-02-16: 0 commits2026-02-17: 0 commits2026-02-18: 0 commits2026-02-19: 0 commits2026-02-20: 0 commits2026-02-21: 0 commits2026-02-22: 0 commits2026-02-23: 0 commits2026-02-24: 0 commits2026-02-25: 0 commits2026-02-26: 0 commits2026-02-27: 0 commits2026-02-28: 0 commits2026-03-01: 0 commits2026-03-02: 0 commits2026-03-03: 0 commits2026-03-04: 0 commits2026-03-05: 0 commits2026-03-06: 0 commits2026-03-07: 0 commits2026-03-08: 0 commits2026-03-09: 0 commits2026-03-10: 1 commit2026-03-11: 0 commits2026-03-12: 0 commits2026-03-13: 0 commits2026-03-14: 0 commits2026-03-15: 0 commits2026-03-16: 0 commits2026-03-17: 0 commits2026-03-18: 0 commits2026-03-19: 0 commits2026-03-20: 0 commits2026-03-21: 0 commits2026-03-22: 0 commits2026-03-23: 0 commits2026-03-24: 0 commits2026-03-25: 0 commits2026-03-26: 0 commits2026-03-27: 0 commits2026-03-28: 0 commits2026-03-29: 0 commits2026-03-30: 0 commits2026-03-31: 0 commits2026-04-01: 2 commits2026-04-02: 0 commits2026-04-03: 0 commits2026-04-04: 0 commits2026-04-05: 0 commits2026-04-06: 0 commits2026-04-07: 1 commit2026-04-08: 1 commit2026-04-09: 0 commits2026-04-10: 1 commit2026-04-11: 0 commits2026-04-12: 0 commits2026-04-13: 0 commits2026-04-14: 0 commits2026-04-15: 1 commit2026-04-16: 0 commits2026-04-17: 0 commits2026-04-18: 0 commits2026-04-19: 0 commits2026-04-20: 0 commits2026-04-21: 0 commits2026-04-22: 0 commits2026-04-23: 0 commits2026-04-24: 0 commits2026-04-25: 0 commits2026-04-26: 0 commits2026-04-27: 0 commits2026-04-28: 0 commits2026-04-29: 0 commits2026-04-30: 0 commits2026-05-01: 3 commits2026-05-02: 0 commits2026-05-03: 0 commits2026-05-04: 0 commits2026-05-05: 0 commits2026-05-06: 0 commits2026-05-07: 0 commits2026-05-08: 0 commits2026-05-09: 0 commits2026-05-10: 0 commits2026-05-11: 0 commits2026-05-12: 0 commits2026-05-13: 2 commits2026-05-14: 0 commits2026-05-15: 2 commits2026-05-16: 0 commits2026-05-17: 4 commits2026-05-18: 4 commits2026-05-19: 0 commits2026-05-20: 8 commits2026-05-21: 6 commits2026-05-22: 3 commits2026-05-23: 0 commits2026-05-24: 0 commits2026-05-25: 1 commit2026-05-26: 0 commits2026-05-27: 1 commit2026-05-28: 0 commits2026-05-29: 0 commits2026-05-30: 0 commits2026-05-31: 0 commits2026-06-01: 2 commits2026-06-02: 0 commits2026-06-03: 1 commit2026-06-04: 0 commits2026-06-05: 0 commits2026-06-06: 1 commit2026-06-07: 0 commits2026-06-08: 0 commits2026-06-09: 0 commits2026-06-10: 3 commits2026-06-11: 5 commits2026-06-12: 0 commits2026-06-13: 0 commits2026-06-14: 0 commits2026-06-15: 0 commits2026-06-16: 0 commits2026-06-17: 0 commits2026-06-18: 0 commits2026-06-19: 4 commits2026-06-20: 0 commits2026-06-21: 0 commits2026-06-22: 11 commits2026-06-23: 9 commits2026-06-24: 8 commits2026-06-25: 1 commit2026-06-26: 0 commits2026-06-27: 0 commits2026-06-28: 5 commits2026-06-29: 10 commits2026-06-30: 0 commits2026-07-01: 0 commits2026-07-02: 0 commits2026-07-03: 13 commits2026-07-04: 2 commits2026-07-05: 0 commits2026-07-06: 0 commits2026-07-07: 0 commits2026-07-08: 2 commits2026-07-09: 0 commits2026-07-10: 0 commits2026-07-11: 0 commits2026-07-12: 0 commits2026-07-13: 0 commits2026-07-14: 0 commits2026-07-15: 0 commits2026-07-16: 0 commits2026-07-17: 0 commits2026-07-18: 0 commits2026-07-19: 0 commits2026-07-20: 0 commits2026-07-21: 1 commit2026-07-22: 0 commits2026-07-23: 1 commit2026-07-24: 0 commits2026-07-25: 0 commits2026-07-26: 0 commits2026-07-27: 0 commits2026-07-28: 1 commit2026-07-29: 1 commit2026-07-30: 0 commits2026-07-31: 0 commits2026-08-01: 2 commits2026-08-02: 0 commits2026-08-03: 0 commits2026-08-04: 0 commits2026-08-05: 0 commits2026-08-06: 0 commits2026-08-07: 0 commits2026-08-08: 1 commit2026-08-09: 0 commits2026-08-10: 0 commits2026-08-11: 0 commits2026-08-12: 1 commit2026-08-13: 10 commits2026-08-14: 0 commits2026-08-15: 0 commits2026-08-16: 0 commits2026-08-17: 0 commits2026-08-18: 0 commits2026-08-19: 4 commits2026-08-20: 3 commits2026-08-21: 2 commits2026-08-22: 5 commits2026-08-23: 0 commits2026-08-24: 0 commits2026-08-25: 1 commit2026-08-26: 0 commits2026-08-27: 0 commits2026-08-28: 7 commits2026-08-29: 0 commits2026-08-30: 0 commits2026-08-31: 9 commits2026-09-01: 3 commits2026-09-02: 4 commits2026-09-03: 2 commits2026-09-04: 0 commits2026-09-05: 3 commits2026-09-06: 0 commits2026-09-07: 0 commits2026-09-08: 2 commits2026-09-09: 0 commits2026-09-10: 0 commits2026-09-11: 10 commits2026-09-12: 0 commits2026-09-13: 0 commits2026-09-14: 12 commits2026-09-15: 0 commits2026-09-16: 0 commits2026-09-17: 0 commits2026-09-18: 4 commits2026-09-19: 0 commits2026-09-20: 0 commits2026-09-21: 2 commits2026-09-22: 12 commits2026-09-23: 1 commit2026-09-24: 2 commits2026-09-25: 0 commits2026-09-26: 0 commits2026-09-27: 0 commits2026-09-28: 0 commits2026-09-29: 0 commits2026-09-30: 0 commits2026-10-01: 0 commits2026-10-02: 0 commits2026-10-03: 0 commits2026-10-04: 0 commits2026-10-05: 0 commits2026-10-06: 0 commits2026-10-07: 0 commits2026-10-08: 0 commits2026-10-09: 0 commits2026-10-10: 1 commit2026-10-11: 4 commits2026-10-12: 0 commits2026-10-13: 0 commits2026-10-14: 1 commit2026-10-15: 0 commits2026-10-16: 0 commits2026-10-17: 0 commits2026-10-18: 0 commits2026-10-19: 0 commits2026-10-20: 0 commits2026-10-21: 0 commits2026-10-22: 0 commits2026-10-23: 0 commits2026-10-24: 0 commits2026-10-25: 0 commits2026-10-26: 0 commits2026-10-27: 1 commit2026-10-28: 0 commits2026-10-29: 0 commits2026-10-30: 0 commits2026-10-31: 0 commits2026-11-01: 0 commits2026-11-02: 6 commits2026-11-03: 1 commit2026-11-04: 1 commit2026-11-05: 0 commits2026-11-06: 0 commits2026-11-07: 1 commit2026-11-08: 0 commits2026-11-09: 1 commit2026-11-10: 3 commits2026-11-11: 7 commits2026-11-12: 7 commits2026-11-13: 4 commits2026-11-14: 0 commits2026-11-15: 0 commits2026-11-16: 3 commits2026-11-17: 0 commits2026-11-18: 0 commits2026-11-19: 0 commits2026-11-20: 0 commits2026-11-21: 0 commits
265 commits in the last yearLessMore

Signals and awards

derived from tracked data
  • Permissive license

    Unlicense

  • Continuous integration

    Automated checks passing

What quip-validator does

The Quip Protocol RS repository provides a streamlined, functional Substrate node template designed to serve as a starting point for building custom blockchains. It pre-configures essential components of the Substrate framework, allowing developers to immediately compile and run a local, single-node network without complex initial setup. The project focuses on minimizing boilerplate code, providing a clean slate for developers to integrate their own custom runtime logic, known as pallets. By offering a ready-to-run environment, it significantly accelerates the initial prototyping phase for decentralized applications and bespoke blockchain networks.

Blockchain developers, Rust engineers, and students looking for a reliable, minimal starting point to build custom networks using the Substrate framework. Familiarity with the relevant ecosystem workflows is highly recommended for optimal usage.

  • Minimalist node configuration: Provides a stripped-down, essential Substrate setup that avoids unnecessary pre-installed pallets and bloat.
  • Out-of-the-box compilation: Ensures the node can be immediately compiled and launched as a local development network using standard Rust tooling.
  • Custom pallet readiness: Offers a clean, documented runtime environment specifically structured for the easy integration of custom business logic.
  • Standardized Substrate architecture: Adheres strictly to the established design patterns and conventions of the broader Polkadot and Substrate ecosystem.
  • Local development focus: Optimizes the initial configuration for rapid, single-node testing rather than immediate production deployment.

Where teams use it

Rapid blockchain prototyping

A development team uses the template to quickly spin up a functional local network to demonstrate a new decentralized application concept.

Custom pallet development

Provide a clean, isolated environment to develop and test custom Substrate pallets before integrating them into a larger, complex network.

Educational experimentation

Allow developers to explore the Substrate framework and learn core blockchain architecture by modifying a working, minimal node.

Hackathon project acceleration

Accelerate the development of blockchain prototypes during hackathons by providing a reliable, ready-to-run node template.

Getting started: cargo build --release

README

main branch

Quip Network node

Quip Network solochain node (quip-network-node).

Chain specs

Omit --chain to join the live public Quip Testnet (EIP-155 20033). --chain=local is a disposable Alice-and-Bob chain. It is not the public testnet.

Flag Preset Network EIP-155
(omit --chain) quip-testnet live public testnet 20033
--chain=quip-testnet quip-testnet live public testnet 20033
--dev or --chain=dev Development Alice-only local 1337
--chain=local Local Testnet Alice and Bob local 1337
--chain=local3 Local Testnet (3 Validators) Alice, Bob, and Charlie local 1337

Aliases for the public testnet: quip_testnet, testnet. A path argument loads that JSON file and uses the chain ID in its genesis.

Runtime 117 is the H2/H4 chain-wipe relaunch. It starts from fresh genesis and is not an in-place upgrade of the earlier H1/H3 network. Operators must use a fresh chain database, re-insert the H4 BABE and H2 GRANDPA keys, and sync from the new genesis; old signed extrinsics are incompatible (transaction_version is 7).

Runtime 121 pauses new XQVM program admission pending a verifier update. Xqvm.store_program returns system.CallFiltered; executing stored programs and registering mempool specifications referencing them remain available. See the runtime compatibility and upgrade notes.

Getting Started

Depending on your operating system and Rust version, there might be additional packages required to compile this template. Check the Install instructions for your platform for the most common dependencies. Alternatively, you can use one of the alternative installation options.

Fetch solochain template code:

git clone https://github.com/paritytech/polkadot-sdk-solochain-template.git solochain-template

cd solochain-template

Build

🔨 Use the following command to build the node without launching it:

cargo build --release

Join the live public testnet

Omit --chain to select quip-testnet (EIP-155 20033).

# Live public testnet (EIP-155 20033). Default if you omit --chain.
./target/release/quip-network-node

Embedded Docs

After you build the project, you can use the following command to explore its parameters and subcommands:

./target/release/solochain-template-node -h

You can generate and view the Rust Docs for this template with this command:

cargo +nightly doc --open

Single-Node Development Chain

The following command starts a single-node development chain that does not persist state. --dev is the Alice-only local preset (EIP-155 1337), not the public testnet.

# Alice-only local chain (EIP-155 1337)
./target/release/solochain-template-node --dev

To purge the development chain's state, run the following command:

# Alice-only local chain (EIP-155 1337)
./target/release/solochain-template-node purge-chain --dev

To start the development chain with detailed logging, run the following command:

# Alice-only local chain (EIP-155 1337)
RUST_BACKTRACE=1 ./target/release/solochain-template-node -ldebug --dev

Development chains (--dev / --chain=dev):

  • Maintain state in a tmp folder while the node is running.
  • Use the Alice account as the sole validator authority.
  • Use the Alice account as the default sudo account.
  • Are preconfigured with a genesis state (/node/src/chain_spec.rs) that includes several pre-funded development accounts.
  • Use EIP-155 chain ID 1337.

To persist chain state between runs, specify a base path by running a command similar to the following:

// Create a folder to use as the db base path
$ mkdir my-chain-state

// Alice-only local chain (EIP-155 1337)
$ ./target/release/solochain-template-node --dev --base-path ./my-chain-state/

// Check the folder structure created inside the base path after running the chain
$ ls ./my-chain-state
chains
$ ls ./my-chain-state/chains/
dev
$ ls ./my-chain-state/chains/dev
db keystore network

Connect with Polkadot-JS Apps Front-End

After you start the node template locally, you can interact with it using the hosted version of the Polkadot/Substrate Portal front-end by connecting to the local node endpoint. A hosted version is also available on IPFS. You can also find the source code and instructions for hosting your own instance in the polkadot-js/apps repository.

Quip uses hybrid BABE and GRANDPA consensus keys. Polkadot.js Apps does not require custom types for Quip anymore.

Multi-Node Local Testnet

A scripted three-validator local network is available two ways. Both use --chain=local3 (EIP-155 1337). This is not the public testnet.

  • Native build: scripts/start-local3.sh builds the debug binary and starts three validators (Alice/Bob/Charlie) against the embedded local3 chain spec.
  • Docker: docker compose up --build starts the same three-validator topology in containers. See the Docker section below.

Both paths use the same hardcoded libp2p node-keys and bootnode peer ID, so they're interchangeable for development.

For background on multi-node consensus, see Simulate a network.

Template Structure

A Substrate project such as this consists of a number of components that are spread across a few directories.

Node

A blockchain node is an application that allows users to participate in a blockchain network. Substrate-based blockchain nodes expose a number of capabilities:

  • Networking: Substrate nodes use the libp2p networking stack to allow the nodes in the network to communicate with one another.
  • Consensus: Blockchains must have a way to come to consensus on the state of the network. Substrate makes it possible to supply custom consensus engines and also ships with several consensus mechanisms that have been built on top of Web3 Foundation research.
  • RPC Server: A remote procedure call (RPC) server is used to interact with Substrate nodes.

There are several files in the node directory. Take special note of the following:

  • chain_spec.rs: A chain specification is a source code file that defines a Substrate chain's initial (genesis) state. Chain specifications are useful for development and testing, and critical when architecting the launch of a production chain. Take note of the development_config and testnet_genesis functions. These functions are used to define the genesis state for the local development chain configuration. These functions identify some well-known accounts and use them to configure the blockchain's initial state.
  • service.rs: This file defines the node implementation. Take note of the libraries that this file imports and the names of the functions it invokes. In particular, there are references to consensus-related topics, such as the block finalization and forks and other consensus mechanisms such as BABE for block authoring and GRANDPA for finality.

Runtime

In Substrate, the terms "runtime" and "state transition function" are analogous. Both terms refer to the core logic of the blockchain that is responsible for validating blocks and executing the state changes they define. The Substrate project in this repository uses FRAME to construct a blockchain runtime. FRAME allows runtime developers to declare domain-specific logic in modules called "pallets". At the heart of FRAME is a helpful macro language that makes it easy to create pallets and flexibly compose them to create blockchains that can address a variety of needs.

Review the FRAME runtime implementation included in this template and note the following:

  • This file configures several pallets to include in the runtime. Each pallet configuration is defined by a code block that begins with impl $PALLET_NAME::Config for Runtime.
  • The pallets are composed into a single runtime by way of the #[runtime] macro, which is part of the core FRAME pallet library.

Custody vesting

Both runtimes include stock vesting at pallet index 32. Mainnet allocation amounts, custody identity, recipients and tranche terms remain unresolved and block mainnet export. Genesis creates no vesting schedules; later signed multisig custody transfers issue one schedule per tranche.

Vesting constrains the recipient's total balance, including held stake: ordinary transfers preserve total >= frozen. Held stake discounts the amount that must stay free, so a pre-bonded account with enough held stake can transfer a new grant immediately, even before its vesting start. Both initial bond and bond_extra from vested funds are intentionally allowed. Guaranteeing that the grant itself stays illiquid requires a new owner decision and a hold-based design; the current pallet does not provide that guarantee.

The minimum vested transfer is 100 * EXISTENTIAL_DEPOSIT (0.1 QUIP). This raises the cost of filling an account's 28 schedule slots: at the former ED floor, 28 × ED (0.028 QUIP) could fill them, while council Root force-remove is denied. The higher floor prices this attack; it does not prevent it. Completed schedules can be cleaned up with vest/vest_other; merging requires the recipient.

The metadata gate is anchored at the native stable2609 state in tests/fixtures/native-2609/manifest.json. It compares every metadata field exactly, including docs, paths, type names and registry IDs, with no historical delta allowances. Future metadata changes require a deliberate re-anchor. Reproduce the anchors with:

env -u SKIP_WASM_BUILD cargo test --locked \
  -p quip-protocol-runtime -p quip-testnet-runtime --test metadata_v16 \
  capture_native_2609_anchor -- --ignored --exact --nocapture

This explicit capture overwrites each runtime's SCALE metadata and sorted *-storage.json default-genesis key/value fixture, and writes their SHA-256 hashes and byte sizes into the manifest. Update capture provenance deliberately when accepting a new baseline. Normal tests rebuild default-genesis storage and require exact equality, with no omitted top-level keys; unexpected child storage fails until the capture format is deliberately extended. Normal tests only read the anchors and verify byte-for-byte reproduction from both native metadata and the Wasm Metadata_metadata and Metadata_metadata_at_version(16) APIs. Before accepting a new capture, run wasm_metadata_matches_native_2609_anchor in both runtimes with SKIP_WASM_BUILD unset and record that result in the manifest. The manifest test checks all four anchor SHA-256 digests and byte sizes and fails on missing files or pins. The compiler and lockfile hash under provenance are historical capture information only; they are not machine-enforced. If CI is set, missing Wasm is a test failure; local builds may soft-skip it.

Attach cargo run -p metadata-surface -- OLD.scale NEW.scale output to the re-anchor MR; add --types before the paths to expose named type layouts (see tool usage and limitations).

Deploy a stable2609-compatible eth-rpc proxy in lockstep with this runtime; ReviveApi v2 uses the SDK's versioned payload/result types.

Revive's native Deposit = () backend now mints a contract's existential deposit (ED) and marks that issuance inactive. The deployer no longer pays this ED as a metered storage deposit, so deployment charges and dry-run storage-deposit estimates drop by one ED. On termination, the SDK attempts to burn/reactivate it only when the account holds exactly the ED and no dust; otherwise it remains. It is never refunded to the terminating caller.

We deliberately keep the SDK's permissionless Revive.batch_map_accounts call. Explicit mapping remains the default with AutoMap = false, but this batch call is not gated by that setting: any signed non-contract caller can map eligible existing third-party accounts without a deposit. The call is fee-free when at least 90% of entries create mappings or release held mapping deposits. A batch caller may also release an existing mapping's held deposit back to its owner; the mapping remains. With OnKilledAccount = (), a mapping outlives its account being reaped. Each account's owner can reverse its mapping with unmap_account, although a later batch can map it again. This is an accepted property; Revive.batch_map_accounts remains permitted.

See runtime 120 compatibility for the release-specific event, call, storage, signing and weight changes.

Pallets

The runtime in this project is constructed using many FRAME pallets that ship with the Substrate repository and Quip-specific pallets defined in the pallets directory.

A FRAME pallet is comprised of a number of blockchain primitives, including:

  • Storage: FRAME defines a rich set of powerful storage abstractions that makes it easy to use Substrate's efficient key-value database to manage the evolving state of a blockchain.
  • Dispatchables: FRAME pallets define special types of functions that can be invoked (dispatched) from outside of the runtime in order to update its state.
  • Events: Substrate uses events to notify users of significant state changes.
  • Errors: When a dispatchable fails, it returns an error.

Each pallet has its own Config trait which serves as a configuration interface to generically define the types and parameters it depends on.

Alternatives Installations

Instead of installing dependencies and building this source directly, consider the following alternatives.

Nix

Install nix and nix-direnv for a fully plug-and-play experience for setting up the development environment. To get all the correct dependencies, activate direnv direnv allow.

Docker

A multi-stage Dockerfile builds the quip-network-node binary on top of debian:bookworm-slim (~80 MB runtime image). The image exposes the binary directly as ENTRYPOINT, so any Substrate CLI flag works at docker run time.

Build
docker build -t quip-network-node:local .

The first build compiles the full workspace and takes a while. BuildKit cache mounts (declared in the Dockerfile) keep the cargo registry and target directory between local rebuilds.

Pre-built images

Every push to main and every git tag publishes an image to the project's GitLab Container Registry, so you don't have to build locally:

docker pull registry.gitlab.com/quip.network/quip-validator/quip-network-node:latest

Tag scheme:

  • :latest — tip of main. Floating, advances on every merge.
  • :sha-<short> — pinned to a specific commit on main or to a tagged release.
  • :<git-tag> — pinned to a release tag (e.g. :v0.1.0).
Run as a validator
# Three-validator local chain (EIP-155 1337). Not the public testnet.
docker run --rm -v quip-data:/data -p 9944:9944 -p 30333:30333 \
  quip-network-node:local \
  --chain=local3 --base-path=/data \
  --validator --alice \
  --unsafe-rpc-external --rpc-cors=all

--unsafe-rpc-external is required because Substrate refuses to combine --rpc-external with --validator by default (a safety guard against exposing a validator's RPC to the public internet). For local development the unsafe flag is fine; for production validators you almost certainly do not want any external RPC at all.

Run as a full node

Same command, omit --validator (and the --alice/--bob/--charlie shortcut):

# Three-validator local chain (EIP-155 1337). Not the public testnet.
docker run --rm -v quip-data:/data -p 9944:9944 -p 30333:30333 \
  quip-network-node:local \
  --chain=local3 --base-path=/data \
  --bootnodes=/dns/<bootnode-host>/tcp/30333/p2p/<peer-id> \
  --rpc-external --rpc-cors=all
Local 3-node network via docker-compose

docker-compose.yml reproduces scripts/start-local3.sh in containers. Each service passes --chain=local3 (EIP-155 1337). This is not the public testnet.

docker compose up --build           # start local3 (EIP-155 1337)
docker compose down                 # stop, keep chain state
docker compose down -v              # stop and wipe state

Then connect Polkadot.js Apps to ws://localhost:9944 (node1), ws://localhost:9945 (node2), or ws://localhost:9946 (node3).

Public testnet

quip-testnet is the live public testnet ("AGLS" tokens, 12 decimals, EIP-155 20033). Omitting --chain, or using quip-testnet, quip_testnet or testnet, loads the exact raw artifact embedded from chain-specs/quip-testnet.json. Its historical runtime and genesis storage are independent of the runtime compiled into a new node binary.

The file is a byte-for-byte copy of the public testnet raw spec published as chain-specs/aglais-network.json in the nodes.quip.network repository. It is vendored here as quip-testnet.json because the local filename identifies the network it serves; the upstream name refers to the same network under its older AGLS label. The upstream file's SHA-256 was verified against GitLab's reported content hash at upstream commit d65ab5b7ad62dad2de603c2611c14a72b24c1537. Its pinned SHA-256 is 0aeeddaf5b546a491d96c35fd636614c6ab42d4e5d9724126182b52c8c694ad4; its genesis hash is 0x542a9915acf840b8940d35ca6de242f669a0c6e3b40f9a8d8c14b9bf7b8ebecb. The blocking live-testnet-spec CI job checks the file's exact bytes, including formatting. Node tests check all four aliases and the genesis hash.

The registered runtime quip_testnet preset remains available through GenesisBuilder for policy auditing. Exporting that preset with a newly compiled runtime does not reproduce the published live genesis. dev, local, local3 and rehearsal continue to use their runtime builders. The unfinished quip-mainnet and quip-testnet-relaunch presets have no built-in node chain aliases.

Quickstart (built node)

cargo build --release -p quip-network-node
# Live public testnet (EIP-155 20033). Omit --chain for the same artifact.
./target/release/quip-network-node --chain=quip-testnet --base-path=./quip-data

The three canonical bootnodes (bootnode-{1,2,3}.aglais.quip.network) are embedded in the raw file, with the live protocol ID agls-network and AGLS properties unchanged.

Using the raw file with an existing image

Explicit file loading also works with existing images; those images do not acquire this new embedded-artifact behavior merely because this repository changed. Validate the checked-out artifact before using its path:

python3 scripts/check-live-testnet-spec.py

docker run --rm -v "$PWD/chain-specs:/spec:ro" -v quip-data:/data \
  -p 9944:9944 -p 30333:30333 \
  registry.gitlab.com/quip.network/quip-validator/quip-network-node:v0.3.0 \
  --chain=/spec/quip-testnet.json --base-path=/data

The vendored path represents the public network currently selected by the four aliases. A future approved relaunch must replace the artifact and update its checksum, genesis-hash tests and provenance in the same reviewed activation commit. The old artifact remains in Git history and release provenance. A new genesis requires fresh databases; this change does not activate a relaunch.

CI also starts a non-validator against a temporary copy with only bootnodes removed, checks its genesis over RPC, and restarts the same genesis-only DB. Isolation relies on empty bootnodes and reserved-peer lists, disabled mDNS, and disabled ordinary peers. The pinned litep2p backend still runs periodic Kademlia queries. The smoke test therefore verifies empty bootnodes before launch, observes at least ten seconds after RPC readiness, requires a Kademlia query log marker, and rejects outbound dial logs across the full run. Missing discovery logging fails the smoke test instead of silently shortening coverage. This smoke test checks startup and DB reopen, not the shipped peer list, live sync, consensus, or compatibility with an existing production DB.

Running a validator

Operator validator slots are committed in runtime/src/genesis_config_presets.rs. The scripts/derive-operator-keys.sh helper derives operator keys.

View on GitHub

Recent activity

commits and pull requests

Recent open issues

view all

Code frequency

additions and deletions
+127.1K-127.1KWeek of 2026-03-08: +16,749 linesWeek of 2026-03-08: -0 linesWeek of 2026-03-15: +0 linesWeek of 2026-03-15: -0 linesWeek of 2026-03-22: +0 linesWeek of 2026-03-22: -0 linesWeek of 2026-03-29: +731 linesWeek of 2026-03-29: -3 linesWeek of 2026-04-05: +3,792 linesWeek of 2026-04-05: -3,145 linesWeek of 2026-04-12: +374 linesWeek of 2026-04-12: -39 linesWeek of 2026-04-19: +0 linesWeek of 2026-04-19: -0 linesWeek of 2026-04-26: +7,872 linesWeek of 2026-04-26: -213 linesWeek of 2026-05-03: +0 linesWeek of 2026-05-03: -0 linesWeek of 2026-05-10: +1,046 linesWeek of 2026-05-10: -59 linesWeek of 2026-05-17: +4,786 linesWeek of 2026-05-17: -1,715 linesWeek of 2026-05-24: +5,555 linesWeek of 2026-05-24: -1,370 linesWeek of 2026-05-31: +237 linesWeek of 2026-05-31: -6 linesWeek of 2026-06-07: +1,617 linesWeek of 2026-06-07: -179 linesWeek of 2026-06-14: +2,560 linesWeek of 2026-06-14: -411 linesWeek of 2026-06-21: +5,623 linesWeek of 2026-06-21: -657 linesWeek of 2026-06-28: +5,171 linesWeek of 2026-06-28: -649 linesWeek of 2026-07-05: +391 linesWeek of 2026-07-05: -246 linesWeek of 2026-07-12: +0 linesWeek of 2026-07-12: -0 linesWeek of 2026-07-19: +85 linesWeek of 2026-07-19: -64 linesWeek of 2026-07-26: +4,092 linesWeek of 2026-07-26: -469 linesWeek of 2026-08-02: +6,336 linesWeek of 2026-08-02: -761 linesWeek of 2026-08-09: +1,167 linesWeek of 2026-08-09: -421 linesWeek of 2026-08-16: +2,585 linesWeek of 2026-08-16: -1,301 linesWeek of 2026-08-23: +2,090 linesWeek of 2026-08-23: -585 linesWeek of 2026-08-30: +3,640 linesWeek of 2026-08-30: -906 linesWeek of 2026-09-06: +832 linesWeek of 2026-09-06: -219 linesWeek of 2026-09-13: +1,173 linesWeek of 2026-09-13: -401 linesWeek of 2026-09-20: +2,200 linesWeek of 2026-09-20: -1,172 linesWeek of 2026-09-27: +0 linesWeek of 2026-09-27: -0 linesWeek of 2026-10-04: +4,509 linesWeek of 2026-10-04: -339 linesWeek of 2026-10-11: +7,565 linesWeek of 2026-10-11: -3,017 linesWeek of 2026-10-18: +0 linesWeek of 2026-10-18: -0 linesWeek of 2026-10-25: +268 linesWeek of 2026-10-25: -8,887 linesWeek of 2026-11-01: +29,575 linesWeek of 2026-11-01: -2,346 linesWeek of 2026-11-08: +127,073 linesWeek of 2026-11-08: -11,050 linesWeek of 2026-11-15: +886 linesWeek of 2026-11-15: -91 linesMar 8, 2026Nov 15, 2026
+250.6K lines added, -40.7K removed over the last year.

Commits per week

last 52 weeks
300Week of 2025-11-23: 0 commitsWeek of 2025-11-30: 0 commitsWeek of 2025-12-07: 0 commitsWeek of 2025-12-14: 0 commitsWeek of 2025-12-21: 0 commitsWeek of 2025-12-28: 0 commitsWeek of 2026-01-04: 0 commitsWeek of 2026-01-11: 0 commitsWeek of 2026-01-18: 0 commitsWeek of 2026-01-25: 0 commitsWeek of 2026-02-01: 0 commitsWeek of 2026-02-08: 0 commitsWeek of 2026-02-15: 0 commitsWeek of 2026-02-22: 0 commitsWeek of 2026-03-01: 0 commitsWeek of 2026-03-08: 1 commitsWeek of 2026-03-15: 0 commitsWeek of 2026-03-22: 0 commitsWeek of 2026-03-29: 2 commitsWeek of 2026-04-05: 3 commitsWeek of 2026-04-12: 1 commitsWeek of 2026-04-19: 0 commitsWeek of 2026-04-26: 3 commitsWeek of 2026-05-03: 0 commitsWeek of 2026-05-10: 4 commitsWeek of 2026-05-17: 25 commitsWeek of 2026-05-24: 2 commitsWeek of 2026-05-31: 4 commitsWeek of 2026-06-07: 8 commitsWeek of 2026-06-14: 4 commitsWeek of 2026-06-21: 29 commitsWeek of 2026-06-28: 30 commitsWeek of 2026-07-05: 2 commitsWeek of 2026-07-12: 0 commitsWeek of 2026-07-19: 2 commitsWeek of 2026-07-26: 4 commitsWeek of 2026-08-02: 1 commitsWeek of 2026-08-09: 11 commitsWeek of 2026-08-16: 14 commitsWeek of 2026-08-23: 8 commitsWeek of 2026-08-30: 21 commitsWeek of 2026-09-06: 12 commitsWeek of 2026-09-13: 16 commitsWeek of 2026-09-20: 17 commitsWeek of 2026-09-27: 0 commitsWeek of 2026-10-04: 1 commitsWeek of 2026-10-11: 5 commitsWeek of 2026-10-18: 0 commitsWeek of 2026-10-25: 1 commitsWeek of 2026-11-01: 9 commitsWeek of 2026-11-08: 22 commitsWeek of 2026-11-15: 3 commitsNov 23, 2025Nov 15, 2026
265 commits in the last 52 weeks.

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 0 commitsSun 1:00 — 0 commitsSun 2:00 — 0 commitsSun 3:00 — 0 commitsSun 4:00 — 0 commitsSun 5:00 — 0 commitsSun 6:00 — 0 commitsSun 7:00 — 0 commitsSun 8:00 — 0 commitsSun 9:00 — 0 commitsSun 10:00 — 1 commitsSun 11:00 — 0 commitsSun 12:00 — 2 commitsSun 13:00 — 2 commitsSun 14:00 — 0 commitsSun 15:00 — 1 commitsSun 16:00 — 0 commitsSun 17:00 — 0 commitsSun 18:00 — 1 commitsSun 19:00 — 0 commitsSun 20:00 — 0 commitsSun 21:00 — 0 commitsSun 22:00 — 5 commitsSun 23:00 — 1 commitsMon 0:00 — 3 commitsMon 1:00 — 2 commitsMon 2:00 — 0 commitsMon 3:00 — 1 commitsMon 4:00 — 0 commitsMon 5:00 — 0 commitsMon 6:00 — 0 commitsMon 7:00 — 0 commitsMon 8:00 — 0 commitsMon 9:00 — 0 commitsMon 10:00 — 2 commitsMon 11:00 — 0 commitsMon 12:00 — 13 commitsMon 13:00 — 5 commitsMon 14:00 — 4 commitsMon 15:00 — 1 commitsMon 16:00 — 1 commitsMon 17:00 — 3 commitsMon 18:00 — 2 commitsMon 19:00 — 4 commitsMon 20:00 — 8 commitsMon 21:00 — 10 commitsMon 22:00 — 2 commitsMon 23:00 — 0 commitsTue 0:00 — 2 commitsTue 1:00 — 1 commitsTue 2:00 — 0 commitsTue 3:00 — 0 commitsTue 4:00 — 0 commitsTue 5:00 — 1 commitsTue 6:00 — 0 commitsTue 7:00 — 0 commitsTue 8:00 — 0 commitsTue 9:00 — 0 commitsTue 10:00 — 2 commitsTue 11:00 — 1 commitsTue 12:00 — 6 commitsTue 13:00 — 3 commitsTue 14:00 — 3 commitsTue 15:00 — 0 commitsTue 16:00 — 5 commitsTue 17:00 — 1 commitsTue 18:00 — 2 commitsTue 19:00 — 0 commitsTue 20:00 — 0 commitsTue 21:00 — 3 commitsTue 22:00 — 4 commitsTue 23:00 — 2 commitsWed 0:00 — 0 commitsWed 1:00 — 0 commitsWed 2:00 — 0 commitsWed 3:00 — 1 commitsWed 4:00 — 0 commitsWed 5:00 — 0 commitsWed 6:00 — 0 commitsWed 7:00 — 0 commitsWed 8:00 — 5 commitsWed 9:00 — 4 commitsWed 10:00 — 0 commitsWed 11:00 — 8 commitsWed 12:00 — 4 commitsWed 13:00 — 1 commitsWed 14:00 — 3 commitsWed 15:00 — 5 commitsWed 16:00 — 5 commitsWed 17:00 — 0 commitsWed 18:00 — 1 commitsWed 19:00 — 4 commitsWed 20:00 — 3 commitsWed 21:00 — 1 commitsWed 22:00 — 4 commitsWed 23:00 — 0 commitsThu 0:00 — 2 commitsThu 1:00 — 1 commitsThu 2:00 — 0 commitsThu 3:00 — 3 commitsThu 4:00 — 0 commitsThu 5:00 — 2 commitsThu 6:00 — 2 commitsThu 7:00 — 3 commitsThu 8:00 — 0 commitsThu 9:00 — 4 commitsThu 10:00 — 2 commitsThu 11:00 — 0 commitsThu 12:00 — 2 commitsThu 13:00 — 1 commitsThu 14:00 — 2 commitsThu 15:00 — 2 commitsThu 16:00 — 4 commitsThu 17:00 — 1 commitsThu 18:00 — 1 commitsThu 19:00 — 1 commitsThu 20:00 — 0 commitsThu 21:00 — 0 commitsThu 22:00 — 4 commitsThu 23:00 — 0 commitsFri 0:00 — 3 commitsFri 1:00 — 1 commitsFri 2:00 — 3 commitsFri 3:00 — 0 commitsFri 4:00 — 0 commitsFri 5:00 — 1 commitsFri 6:00 — 1 commitsFri 7:00 — 0 commitsFri 8:00 — 0 commitsFri 9:00 — 0 commitsFri 10:00 — 1 commitsFri 11:00 — 5 commitsFri 12:00 — 3 commitsFri 13:00 — 2 commitsFri 14:00 — 0 commitsFri 15:00 — 6 commitsFri 16:00 — 6 commitsFri 17:00 — 3 commitsFri 18:00 — 2 commitsFri 19:00 — 3 commitsFri 20:00 — 1 commitsFri 21:00 — 5 commitsFri 22:00 — 1 commitsFri 23:00 — 6 commitsSat 0:00 — 2 commitsSat 1:00 — 0 commitsSat 2:00 — 0 commitsSat 3:00 — 0 commitsSat 4:00 — 0 commitsSat 5:00 — 0 commitsSat 6:00 — 0 commitsSat 7:00 — 1 commitsSat 8:00 — 2 commitsSat 9:00 — 4 commitsSat 10:00 — 2 commitsSat 11:00 — 1 commitsSat 12:00 — 0 commitsSat 13:00 — 0 commitsSat 14:00 — 0 commitsSat 15:00 — 2 commitsSat 16:00 — 0 commitsSat 17:00 — 0 commitsSat 18:00 — 0 commitsSat 19:00 — 1 commitsSat 20:00 — 0 commitsSat 21:00 — 0 commitsSat 22:00 — 0 commitsSat 23:00 — 1 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.
DateListRankStars gained
Apr 10, 2026daily#9+332
  • ultraworkers/claw-code

    An agent-managed museum exhibit, built in Rust with Gajae-Code / LazyCodex — developed and maintained with no human intervention.

    194.8K stars · Rust

  • farion1231/cc-switch

    A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode,DeepSeek Harness and more. Only official website: ccswitch.io

    156K stars · Rust

  • openai/codex

    Lightweight coding agent that runs in your terminal

    136K stars · Rust

  • rust-lang/rust

    Empowering everyone to build reliable and efficient software.

    122.3K stars · Rust

  • pbakaus/impeccable

    The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

    114.1K stars · Rust

  • denoland/deno

    A modern runtime for JavaScript and TypeScript.

    109.1K stars · Rust