chippr-robotics

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.

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.

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.

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.

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.

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.

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.

Safely edit a Fukuii node's HOCON configuration and choose an operating mode — network selection, datadir, RPC apis/ports, sync mode (SNAP vs fast), mining, and resource settings — with a back-up-then-restart discipline. Use when asked to change config, enable an RPC namespace, switch sync strategy, set the datadir, or pick an operating profile. Editing config and restarting is an irreversible/disruptive action under the guarded-write protocol.

This skill should be used when the user wants to "use Logseq", "create knowledge graph", "analyze relationships", "set up graph database", "manage notes with Logseq", "build knowledge management system", or needs to integrate structured note-taking and graph visualization.

FROST threshold signature operations for multi-chain support. Use for DKG ceremonies, Taproot/Ed25519/Ristretto255 signing, and managing FROST-based child disks. Covers Bitcoin Taproot, Solana, Cosmos, and Zcash shielded transactions.

Model Context Protocol server for Sigil MPC signing. Use for deploying Sigil as a universal agent-compatible signing server that works with Claude Desktop, VS Code, and any MCP-compliant client.

Sign blockchain transactions using MPC presignatures stored on floppy disks. Requires physical disk insertion for each signature. Use when signing Ethereum transactions, checking disk status, managing presignatures, or working with air-gapped MPC wallets.

Bring the FairWins gasless Cloud Run infrastructure (the alto ERC-4337 bundler and the relay/paymaster signer gateway on Polygon) up or down to control cost, and check its status, health, and config. Use whenever the user wants to start/stop/turn on/turn off the bundler, gateway, paymaster, relayer, or "signers"; ask whether they're running; scale them to zero to save money; or bring them up before testing passkey gasless transactions. The SPA runs itself and is out of scope.

Manage encrypted multi-chain cryptocurrency keys stored on floppy disks. Supports Ethereum, Bitcoin, Zcash, Monero, and Solana. Use when working with floppy disk keystores, deriving keys for multiple blockchains, mounting/unmounting floppy drives, or configuring secure air-gapped key storage. One mnemonic, all chains.