appchain-quickstart

Launch and configure Nethereum AppChains with sequencer, follower sync, and RocksDB storage.

2.3k|744|Updated Nov 23, 2015
One-click install
npx skills add https://github.com/Nethereum/Nethereum --skill appchain-quickstart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: appchain-quickstart
Source: https://github.com/Nethereum/Nethereum/tree/main/plugins/nethereum-skills/skills/appchain-quickstart
Command: npx skills add https://github.com/Nethereum/Nethereum --skill appchain-quickstart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a domain-specific Ethereum chain with a sequencer, follower nodes, and persistent storage involves many moving parts. This Skill guides you through launching and configuring Nethereum AppChains using the CLI or the programmatic AppChainBuilder API in .NET/C#.

Core Features & Use Cases

  • CLI and Programmatic Launch: Start a sequencer or follower node via the nethereum-appchain CLI tool, or embed a chain in-process with AppChainBuilder and presets for gaming or testing.
  • Storage Options: Choose between in-memory stores for tests and RocksDB-backed persistent storage for production chains.
  • Multi-Peer Sync and Finality: Configure follower nodes that re-execute transactions, verify state roots against the sequencer, and track L1-anchored finality.
  • Use Case: A game studio needs a high-frequency custom chain for in-game state updates. Use the gaming preset to spin up an AppChain with an operator key, connect via standard Nethereum Web3 calls, and deploy contracts as on any Ethereum network.

Quick Start

Ask the AI to launch a Nethereum AppChain sequencer on port 8546 with chain ID 420420 and show how to connect to it from a C# application.

Frequently Asked Questions about appchain-quickstart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch a custom Ethereum chain with .NET?

Install the nethereum-appchain CLI tool and run it with a port, chain ID, genesis owner key, and sequencer key to start producing blocks. For embedded use, build a chain programmatically with AppChainBuilder from the Nethereum.AppChain.Sequencer package.

How do I sync a follower node with an AppChain sequencer?

Start the follower with the same chain ID and genesis owner address as the sequencer, then point --sync-peers at the sequencer URL. The follower re-executes transactions locally and validates state roots against the sequencer.

Should I use in-memory or RocksDB storage for an AppChain?

Use in-memory storage for tests and demos where persistence is not needed. Use RocksDB via Nethereum.CoreChain.RocksDB for anything requiring durable blockchain data, and note the CLI defaults to RocksDB unless --in-memory is passed.

Can I interact with an AppChain without running an HTTP server?

Yes. Create an AppChainNode and AppChainRpcClient in-process, then pass the RPC client to a standard Web3 instance. All Nethereum calls work normally without HTTP overhead.

Why does my AppChain follower reject blocks from the sequencer?

Followers reject blocks when the re-executed state root does not match the sequencer, which happens if the genesis owner address or chain ID differs between nodes. Enable RejectOnStateRootMismatch only when both nodes share identical genesis configuration.