RESEARCH RECORD

Read-Only Chain Observation Boundary

Chain research · Verification

Mobile view is optimised for record-by-record inspection. Use the section menu below; desktop keeps the full route context visible.

Record sections

SUMMARY

Record summary

Record ID: fenrua-research:read-only-chain-observation
Category: Chain research
Date: 2026-07-12
Source revision: 390f7aeef778ce93db12e16028bc3a788b643c2d
Evidence revision: 85ecc97c026b01b576d735501795951dd293b3ca
Primitive: Verification
Maturity: Read-only live
Severity: Public-trust boundary

CLAIM

Primary claim

Chain 978 and Chain N521 can be exposed only as independently signed, bounded read-only observations.

NON-CLAIM

Boundary

A chain observation does not prove contract safety, bytecode identity, reserve state, or deployment correctness.

Public page exposes only sanitized, source-linked evidence. Private endpoints, secrets, and raw witness material remain out of scope.

THREAT / INVARIANT

Threat model

Threat: Public telemetry could be mistaken for contract assurance.

Invariant: No private endpoint, admin URL, RPC credential, peer detail, validator identity, or signing key appears in browser payloads.

Trigger: Query requests are rejected, private topology fields are excluded, and only the bounded observation schema is accepted.

Root cause: Public claims can drift when evidence, tooling, or telemetry are not adjacent to limitations.

TOOLING

Tools and implementation

Reference implementation: api/chain-progress.js, fixed per-chain observation-key endpoints, and scripts/test-chain-progress.mjs.

Tools used: Node.js API test harness and sanitized response assertions.

Tool versions: Node.js v24.18.0 plus pinned fenrua-kernel evidence links.

COMMANDS

Verification commands

node scripts/test-chain-progress.mjs

EVIDENCE

Evidence and result

Results: chain-progress public-feed test output.

Evidence confirmation: Browser payload states sanitized read-only observation only; it does not claim contract, bytecode, reserve, or deployment assurance.

Evidence hash: See linked evidence artifact.

Fix revision: Current website route generation.

REGRESSION

Regression fixture

Query requests are rejected, private topology fields are excluded, and only the bounded observation schema is accepted.

Kernel impact: Verification primitive boundary clarified.

Utility impact: Public interface remains maturity-labelled and limitation-adjacent.

LIMITATIONS

Remaining limitations

No stale contract claims are derived from the feed.

Supersession: Active; bounded observations remain separate from public release evidence.

REPRODUCTION

Reproduction instructions

node scripts/test-chain-progress.mjs