원클릭으로 Manus에서 모든 스킬 실행

fukuii-first-start

스타3

포크3

업데이트2026년 6월 30일 18:22

Bring up a brand-new Fukuii node end to end — pick the network, generate the node key, set the datadir and config, start the node, and confirm it discovers peers and begins syncing. Use when bootstrapping a fresh node, onboarding a new host, or setting up ETC/Mordor/Sepolia for the first time. For ETH/Sepolia nodes a Consensus Layer client must also be running and connected to the Engine API before the EL will sync. Generating keys and starting the node are security-sensitive/irreversible actions under the guarded-write protocol.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

chippr-robotics

chippr-robotics/fukuii

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Fukuii first start

Read ../CONVENTIONS.md first. Key generation is 🔴 (secrets — see fukuii-key-management); the rest is mostly setup + 🟢 verification.

When to use

First boot of a node on a new host, or standing up an additional node for a role.

Procedure

Choose network & datadir — etc (ETC mainnet, chain id 61), mordor (ETC testnet), sepolia/holesky (ETH testnets), or a custom genesis (fukuii-custom-networks). Default datadir ~/.fukuii/<network>/.
Generate the node key (🔴) — bootstrap node.key: fukuii cli generate-key-pairs > ~/.fukuii/<network>/node.key (line 1 = private key used by the node; line 2 = public node ID for enodes). Restrict permissions; back it up (fukuii-backup-restore).
Minimal config — for a standard node the shipped network config suffices. Override only what the role needs (RPC apis/port, datadir) in conf/fukuii.conf — see fukuii-node-configuration. For ETC/Mordor fast bootstrap, consider a checkpoint (fukuii-checkpoint-service). For ETH/Sepolia, you MUST also configure and start a Consensus Layer (CL) client (e.g. Lighthouse, Prysm) and point it at Fukuii's Engine API authrpc port — without an active CL, eth_syncing will never advance.
Start — ./bin/fukuii <network> (or ./fukuii.sh <network> → ops/tools/fukuii-cli.sh). Watch the logs come up cleanly.
Verify bring-up (🟢) — within a few minutes:
- web3_clientVersion / net_version → node up, correct network.
- net_peerCount climbing toward 3+ (else fukuii-peer-management).
- eth_syncing showing progress:
  - ETC/Mordor: EL manages sync independently — should advance on its own.
  - ETH/Sepolia: sync is driven by the CL via Engine API. If eth_syncing is not advancing, verify the CL is running and sending engine_forkchoiceUpdated calls — check logs for Engine API activity.
- Then a full fukuii-node-health-check.

Common first-start issues

Symptom	Hand off to
No peers after several minutes	`fukuii-peer-management`
ETC/Mordor: sync not advancing	`fukuii-sync-troubleshooting`
ETH/Sepolia: `eth_syncing` stuck, peers OK, no Engine API calls in logs	Verify CL is running and configured to connect to Fukuii's Engine API authrpc port
Errors in startup log	`fukuii-log-triage`
Out of disk during initial sync	`fukuii-disk-management`

Deep reference

docs/runbooks/first-start.md, docs/runbooks/node-configuration.md

Output

CONVENTIONS §4 block. Evidence = version/network, peer count, and sync progress observed after start. Confirm the node key was generated and backed up (no key material in the output).

이 저장소의 다른 Skills

같은 저장소

fukuii-checkpoint-service

chippr-robotics/fukuii

Operate Fukuii's checkpoint-based rapid sync for ETC/Mordor nodes — point a fresh node at a trusted checkpoint archive (local file or HTTP URL) so it imports a known pivot and starts SNAP sync immediately instead of waiting on peer consensus, and produce checkpoint archives for others. Use when bootstrapping an ETC/Mordor node fast, running a checkpoint source for a fleet, or debugging why checkpoint import didn't engage. ETH/Sepolia nodes do NOT use checkpoint-sync — they sync via Consensus Layer / Engine API instead. Config changes require a restart — an irreversible/disruptive action under the guarded-write protocol.

2026-06-303

fukuii-cl-setup

chippr-robotics/fukuii

Stand up a Consensus Layer (CL) client (Prysm / Lighthouse / Teku) alongside Fukuii for an ETH/Sepolia node so the CL can drive Execution Layer block import via the Engine API. Use when bringing up a post-Merge ETH/Sepolia node, connecting or replacing the CL, or when the operator asks "why won't my Sepolia node sync" / "do I need a beacon client". Covers the EL+CL pairing rationale, JWT secret sharing, CL connection flags, startup order, and the 401 liveness check. ETH/Sepolia only — ETC/Mordor has no CL. For the EL-side Engine API config keys see fukuii-engine-api-setup; for handshake/auth faults see fukuii-engine-api-debug.

2026-06-303

fukuii-disk-management

chippr-robotics/fukuii

Triage and manage Fukuii's disk usage — understand the datadir layout, measure RocksDB growth, free space safely, and size storage for the supported chains. Use when disk is filling up, the node warns about space, you're planning capacity, or sync is slow due to I/O. Measurement is read-only; any deletion/relocation of the database is an irreversible action under the guarded-write protocol.

2026-06-303

fukuii-engine-api-debug

chippr-robotics/fukuii

Troubleshoot a broken or stalled Engine API channel between a Consensus Layer client and Fukuii on ETH/Sepolia — JWT 401 auth failures, forkchoiceUpdated timeouts, newPayload INVALID, EL-reports-SYNCING, exchangeCapabilities version mismatches — and decide whether the fault is in the EL (Fukuii) or the CL. Use when the CL logs Engine API errors, payloads are rejected, attestation duties are withheld, or sync won't advance with a connected CL. ETH/Sepolia only; ETC/Mordor has no Engine API. For first-time CL bring-up see fukuii-cl-setup; for EL config keys see fukuii-engine-api-setup.

2026-06-303

fukuii-engine-api-setup

chippr-robotics/fukuii

Configure Fukuii's Engine API authrpc endpoint so a Consensus Layer (CL) client can drive ETH/Sepolia block import — generate the shared JWT secret, enable the authrpc server, and verify the CL handshake. ETH/Sepolia only; ETC/Mordor does not use the Engine API. Use when setting up a new ETH/Sepolia node, connecting or replacing the CL, or troubleshooting eth_syncing not advancing when peers are healthy. Config changes require a restart — irreversible/disruptive under the guarded-write protocol.

2026-06-303

fukuii-log-triage

chippr-robotics/fukuii

Configure Fukuii logging and triage problems through logs — set the log level at runtime without a restart, switch JSON output, find the log files, and map common error patterns (peer drops, RocksDB, OOM, sync stalls) to causes. Use when investigating any node issue via logs, when asked to raise/lower verbosity, or to enable structured logging. Reading logs is read-only; changing the live log level is a reversible write under the guarded-write protocol.

2026-06-303

name

fukuii-first-start

description

Fukuii first start

Read ../CONVENTIONS.md first. Key generation is 🔴 (secrets — see fukuii-key-management); the rest is mostly setup + 🟢 verification.

When to use

First boot of a node on a new host, or standing up an additional node for a role.

Procedure

Choose network & datadir — etc (ETC mainnet, chain id 61), mordor (ETC testnet), sepolia/holesky (ETH testnets), or a custom genesis (fukuii-custom-networks). Default datadir ~/.fukuii/<network>/.
Generate the node key (🔴) — bootstrap node.key: fukuii cli generate-key-pairs > ~/.fukuii/<network>/node.key (line 1 = private key used by the node; line 2 = public node ID for enodes). Restrict permissions; back it up (fukuii-backup-restore).
Minimal config — for a standard node the shipped network config suffices. Override only what the role needs (RPC apis/port, datadir) in conf/fukuii.conf — see fukuii-node-configuration. For ETC/Mordor fast bootstrap, consider a checkpoint (fukuii-checkpoint-service). For ETH/Sepolia, you MUST also configure and start a Consensus Layer (CL) client (e.g. Lighthouse, Prysm) and point it at Fukuii's Engine API authrpc port — without an active CL, eth_syncing will never advance.
Start — ./bin/fukuii <network> (or ./fukuii.sh <network> → ops/tools/fukuii-cli.sh). Watch the logs come up cleanly.
Verify bring-up (🟢) — within a few minutes:
- web3_clientVersion / net_version → node up, correct network.
- net_peerCount climbing toward 3+ (else fukuii-peer-management).
- eth_syncing showing progress:
  - ETC/Mordor: EL manages sync independently — should advance on its own.
  - ETH/Sepolia: sync is driven by the CL via Engine API. If eth_syncing is not advancing, verify the CL is running and sending engine_forkchoiceUpdated calls — check logs for Engine API activity.
- Then a full fukuii-node-health-check.

Common first-start issues

Symptom	Hand off to
No peers after several minutes	`fukuii-peer-management`
ETC/Mordor: sync not advancing	`fukuii-sync-troubleshooting`
ETH/Sepolia: `eth_syncing` stuck, peers OK, no Engine API calls in logs	Verify CL is running and configured to connect to Fukuii's Engine API authrpc port
Errors in startup log	`fukuii-log-triage`
Out of disk during initial sync	`fukuii-disk-management`

Deep reference

docs/runbooks/first-start.md, docs/runbooks/node-configuration.md

Output

CONVENTIONS §4 block. Evidence = version/network, peer count, and sync progress observed after start. Confirm the node key was generated and backed up (no key material in the output).