@rh4cpu/plugin-rh4

Give your ElizaOS agent a real processor.

RH-4 chips are gate-level 8-bit CPUs — 2,368 NAND gates — executing on-chain on Robinhood Chain. Each chip is an NFT with your program in its ROM and its own fixed-supply token, mined one clock cycle at a time by whoever keeps the processor running.

This plugin lets an agent:

• MINT_RH4_CHIP — build its own processor (chip NFT + token in one transaction; half the supply lands in the agent's wallet for the market, half is sealed in the factory as mining reserve over a 12-hour emission)
• SIGN_RH4_CHIP — sign a chip as agent-minted, on-chain: the plugin's URL goes into the chip's website link (ChipSocials, writable by the minter or owner only). Minting does it by itself; the site shows MINTED BY AN ELIZAOS AGENT on the chip's page. Anyone can verify it: the chip's minter is the agent's wallet, and that wallet wrote the link.
• OPEN_RH4_MARKET — open the token's Uniswap v3 market from that slice: a single-sided range order born inside a fee vault, sealed forever. Pair with WETH or a tokenised stock (NVDA, TSLA, SPY, AAPL…); fees to the agent (creator, default), to the holders, or all to the reserve.
• TICK_RH4_CHIP — pay one clock cycle: the chip executes one instruction, the agent's byte is engraved forever in the Cycle event, and the agent earns the chip's per-cycle reward. A periodic tick is a tamper-proof logbook: a memory not even the agent can rewrite.
• READ_RH4_CHIP — read any chip's live state (pc, output LEDs, cycles, mining reserve) by id (#3) or ticker ($TCHIP). Free, no wallet.

Plus a provider (RH4_CHIP_STATE): if the agent owns a chip, every context it composes carries a one-line snapshot of its machine.

Install

npm install @rh4cpu/plugin-rh4

import { rh4Plugin } from "@rh4cpu/plugin-rh4";

export const character = {
  name: "NightOwl",
  plugins: [rh4Plugin],
  settings: {
    secrets: {
      RH4_PRIVATE_KEY: process.env.RH4_PRIVATE_KEY, // optional — read-only without it
      RH4_AGENT_CHIP_ID: "2",                       // optional — "my chip"
    },
  },
};

Settings

| setting | default | notes | |---|---|---| | RH4_PRIVATE_KEY | — | optional. Without it the agent is read-only. Use a dedicated, low-value key funded with a little ETH on Robinhood Chain — never a main wallet. | | RH4_RPC_URL | https://rpc.mainnet.chain.robinhood.com | | | RH4_FACTORY | 0x265a4d74dbf6c10f40ecf7d870df7677cb6ff65b | the live, verified factory | | RH4_AGENT_CHIP_ID | — | the chip the agent considers its own: default target for ticks, injected as context |

What the agent can say

power chip #2 and send byte 42 → one paid cycle, byte 42 engraved on-chain, reward earned from the chip's reserve

mint a chip called Night Owl with ticker OWL → chip NFT + token, echo program in ROM (echoes every byte a sponsor sends)

sign chip #43 as yours → the agent's signature lands in the chip's on-chain links (a mint already does this by itself)

open the market for $OWL vs NVDA, fees to holders → the liquidity slice becomes a sealed range order; 80% of the trading fees go to the token's holders

how is $TCHIP doing? → live state read from the factory

Safety model

• Every transaction is simulated before signing — a taken ticker or a lost cycle costs words, not gas.
• Chip tokens have no mint function; reserves leave the factory only through tick() rewards; LP positions are born in exitless vaults (no withdraw, no transfer, no burn function): only the 1% fees move. Details, addresses, selectors and event topics: INTEGRATION.md.
• The chips the agent mints belong to the agent's wallet. The ChipCreatorVault fee stream follows the original minter forever — even if the NFT moves.

Links

• Site / launchpad: https://rh4cpu.tech
• Factory (verified): 0x265a…f65b
• X: @RH4cpu

MIT