กำลังเปิดหน้า
กำลังเตรียมข้อมูลของหน้านี้ โปรดรอสักครู่
กำลังเปิดหน้า
กำลังเตรียมข้อมูลของหน้านี้ โปรดรอสักครู่
API evidence · read-only
Privacy-safe IPFS batch summaries from the Go API. Protected diagnostics and private visit objects are deliberately not rendered.
No browser-side prepare or submit controls
Those API routes create new immutable IPFS/catalog state and may use a server-held reporter key, but the documented API has no wallet-signature authorization. Operations must stay in the trusted backend workflow until authorization is added.
Each stage has independent evidence. A URL or browser record never upgrades a later stage.
Local navigation context only; never verified attribution.
A visit ID returned after IPFS object and catalog persistence; it is not yet batched or on-chain.
A persisted public IPFS manifest, evidence URI/hash, Merkle root, and proof are available.
Confirmed only by AttributionTracker.getVisitBatch for a known ID.
The attribution-evidence endpoint reports pending, blocked, anchoring, and ready proof states.
An on-chain attributed order is a distinct later observation.
Loading visit-tracking health and evidence batches independently…
Persisted IPFS state and blockchain anchoring are shown independently.