Configuration

The agent is configured by a single config.json (generate one interactively with npm run generate:config; template in config.example.json). Secrets are never written into the file — use ${ENV_VAR} substitution and put values in .env.

Blocks

Block	Purpose
chain	RPC/WS endpoints, Router & Coordinator addresses, wallet (keystore path + receiving address). Addresses per network: Registry & deployments
containers[]	The Docker images this agent can run — see Container contract
verifiers[]	Verifier contracts this agent serves, each optionally paired with a proof-service container
scheduler / retry	Scheduled-subscription interval commitment and retry policy
payload	Large input/output storage (below)
vrf	Opt-in NoosphereVRF epoch serving (pair with the registry's noosphere-vrng container)
x402Seller	The separate per-call selling rail — configured here but documented with its own product: Sell from an agent

chain

"chain": {
  "enabled": true,
  "rpcUrl": "https://sepolia.hpp.io",
  "wsRpcUrl": "wss://sepolia.hpp.io",
  "routerAddress": "0x480a4f7506548773040d47dd7b6372dbf71358d4",
  "coordinatorAddress": "0xeda4a7957e8f5de6cd6bd747c3ccd5e1c295302c",
  "deploymentBlock": 295062,        // start scanning from here — use a recent block
  "processingInterval": 5000,       // ms between chain-processing passes
  "wallet": {
    "keystorePath": "./.noosphere/keystore.json",
    "paymentAddress": "0xYourReceivingWallet"   // written by setup:wallet, or set by hand
  }
}

npm run generate:config fills the addresses for the network you pick (from its built-in per-network presets; the community registry supplies the container/verifier catalog). It leaves paymentAddress as the zero address — set it, or let npm run setup:wallet fill it when you create the agent's payment wallet.

note

config.json is parsed as plain JSON against the agent's TypeScript types — there is no schema validation, so a misspelled key is silently ignored. ${ENV_VAR} substitution works in any string value; an unset variable is left as the literal ${…} with only a console warning.

containers[]

"containers": [
  {
    "id": "hf-sentiment",            // referenced by subscriptions / registry ID
    "name": "hf-sentiment",          // docker name (agent prefixes it)
    "image": "hf-sentiment:latest",
    "port": "8090",                  // where /computation listens inside
    "env": { "HF_TOKEN": "${HF_TOKEN}" }
  }
]

verifiers[]

Serve proof-checked subscriptions: each entry names the on-chain verifier contract and, when the proof is produced off-chain, the companion proof-service container. PROOF_SERVICE_PRIVATE_KEY in .env signs proof submissions.

scheduler / retry / containerExecution

"scheduler": { "enabled": true, "cronIntervalMs": 60000, "syncPeriodMs": 3000 },
"retry":     { "maxRetries": 3, "retryIntervalMs": 30000 }

An optional containerExecution block (timeout, connectionRetries, connectionRetryDelayMs) tunes how the agent calls your containers.

payload

Large inputs/outputs stay off-chain; the agent resolves URI-based payloads:

Scheme	Use case	Env
data:	Inline base64 below payload.uploadThreshold	—
ipfs://	IPFS / Pinata	PINATA_API_KEY, PINATA_API_SECRET, IPFS_GATEWAY
https://	S3-compatible storage (R2/S3/MinIO)	R2_ENDPOINT, R2_BUCKET, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_PUBLIC_URL_BASE

"payload": { "uploadThreshold": 1024, "defaultStorage": "s3" }

Defaults when the block is omitted: uploadThreshold: 1024, defaultStorage: "ipfs". IPFS/S3 backends can also be configured inline via payload.ipfs { … } / payload.s3 { … } instead of env vars.

Environment variables

Variable	Purpose
KEYSTORE_PASSWORD	Decrypts the agent keystore (required)
(any)	${ENV_VAR} substitution is generic — reference any variable from a config.json string value
EXPRESS_PORT	Agent API port (default 4000)
PROOF_SERVICE_PRIVATE_KEY	Only for verifiers with a proof service
R2_* / PINATA_* / IPFS_*	Payload storage backends (above)

Networks

Network	Chain ID	RPC
HPP Mainnet	190415	https://mainnet.hpp.io
HPP Sepolia	181228	https://sepolia.hpp.io

Full contract addresses: Registry & deployments.