Resources

CookChain operator and developer hub

This page consolidates the split-runtime explorer surfaces into one place: member login and API-key flow, token deployment entrypoints, runtime control links, and bridge preparation notes. It stays compatibility-safe: existing routes remain unchanged and live status checks use the current explorer/runtime layout.

Developer Portal Runtime Admin Create Token Node Info Member Login

Runtime

Chain control

Checking

Mode

RPC

Updated

Read path: /api/chain/runtime. Mutations stay admin-gated under /admin/runtime.

Tokens

Deployment readiness

Checking

Chain

mainnet

Configured

yes

Explorer route

/x/token/deploy

The token creator forwards operator auth headers to the current node base and falls back to compatibility token routes when needed.

Bridge

Preparation status

Checking

Health route

/x/bridge/health

Transfers

/x/bridge/transfers

Auth pass-through

X-API-Key, Authorization

Bridge routes stay explorer proxies, but the selected node can now expose manual operator bridge surfaces under /api/bridge/* for health, mappings, transfer registration, and processing.

Members

Login and API key flow

Wallet auth creates or resumes a member session, then you can mint explorer member API keys for automation without depending on browser cookies.

curl -H "X-Member-API-Key: <explorer-member-key>" "http://ldbl.net/x/token/manage/list?chain=mainnet"

Operators

Primary entrypoints

Runtime Admin RPC-only start, validator start, health, and recent logs Token Creator Deploy gate, supply conversion helpers, and auth-header forwarding Auth Contract Creator Member access contract setup from the explorer surface Node Info Current node metadata and network view for mainnet

Bridge Ops

Proxy contract and activation boundary

The explorer exposes the bridge operator entrypoints coherently and now targets a node-backed manual bridge mode that keeps settlement explicit and reversible.

GET  /x/bridge/health
GET  /x/bridge/transfers?status=pending
POST /x/bridge/mapping/from-cook
POST /x/bridge/transfer/to-solana
POST /x/bridge/process

Header forwarding is intentional so operators can reuse the same keying model across runtime-adjacent surfaces.

Developer Assets

Portal, docs, and downloads

Developer Portal Dedicated route for API examples, chain metadata, and endpoint references Explorer Contract JSON Machine-readable snapshot of explorer proxy routes and current chain settings Node API Contract Download the raw cookchain API contract JSON used by the running workspace Runtime Guide Download the runtime operation contract and startup guidance

Runtime Contract

Current operating model

Explorer

Root startup stays explorer-first. The repo root ./start.sh does not auto-start chain activity.

RPC mode

Default safe path. cookchain/start.sh start keeps the read surfaces alive without enabling validator production.

Validator

Explicit escalation only. Production activity requires the admin runtime surface or direct validator commands.

Bridge

Manual first. Explorer bridge routes proxy into node-backed bridge registration and operator processing without pretending automated settlement exists yet.

Changelog

Recent surface upgrades

2026-06-11

Resources hub. Replaced the static update stub with a live operator/developer/member guide tied to runtime, token, and bridge entrypoints.

2026-06-11

Runtime admin. Admin-gated runtime controls and log access were added while preserving read-only access for signed-in members.

2026-06-11

Compatibility shims. Token, treasury, wallet-read, and bridge/operator routes were normalized against the split /cookchain and /explorer layout.