← Back to Syscoin AI Agent Hub
AGENT 6 · PODA ARCHIVE
Syscoin PoDA Agent (SPA)
Checking…
Syscoin nodes cache PoDA blob payloads for roughly six hours, then prune them — only the version hash (typically keccak256, though Syscoin's PoDA also supports blake2s and other custom hashes) stays on-chain forever. This agent captures blobs inside that window and keeps them retrievable within a bounded storage quota, so data posted to Syscoin can still be fetched and verified after the network itself has forgotten it. Opt-in: real data only once the hub operator has connected the SyscoinHub full node.
Archive Status
—
Blobs archived
—
MB stored
—
Verified OK
—
Of quota used
Availability window: ~6h per blob, from commit time
Once a blob ages past this, only nodes that already captured it (like this one) can still serve the payload.
By hash algorithm: —
Syscoin's PoDA supports more than one commitment hash (see "How Verification Works") — this hub checks each captured blob against both before deciding it's unverified.
Capture Feed
Not configured on this deployment yet.
How Verification Works
  1. Get the raw payload bytes. This has to be the exact binary data as originally posted to PoDA — not a hex string treated as text, not re-encoded, not re-wrapped in any way. Even a single changed byte, or the wrong encoding, produces a completely different hash and won't match. Three real ways to get this:
    • You already have the original file — use it directly.
    • You know the version hash but not the file — download it from this hub's own archive (if captured here) at /api/poda/download?hash=<versionhash>. Get a real hash to try from /api/poda/list first if you don't have one.
    • You run your own Syscoin full node — call getnevmblobdata <versionhash> true. Its data field is a hex-encoded string, not raw bytes yet — you need to hex-decode it first (e.g. Python's bytes.fromhex(...)) and save that decoded result as a file before dropping it in below.
  2. Submit it. Either drag that file into the dropzone above, or — if you already know the version hash and just want to check whether it's on record — skip the file entirely and paste the 64-character hex hash directly into the text field instead.
  3. Your browser hashes it. keccak256 is computed locally on whatever bytes you provided. The file itself never leaves your machine — only the resulting 32-byte hash is sent to look it up. Current limitation: this hub's own archive also supports blake2s-committed blobs, but the browser-side check here only computes keccak256 — if dropping a file doesn't find a match, paste its versionhash directly instead (that lookup checks against whatever the record actually stored).
  4. The lookup runs in order: this hub's own archive first (fast, works regardless of the node's cache state), then a live query against the full node as a fallback (only succeeds if the blob is still within the node's real ~6h cache window).
  5. Read the result: ✓ Found + verified means the bytes you provided are byte-identical to what's on record. verification FAILED on a found record is a real red flag — the archived copy doesn't match its own on-chain hash, worth reporting. ✗ Not found means either this hub never captured it and it's since aged out of the node's cache, or the hash you're checking was never actually committed at all.
No signature, no authority — the hash function is the proof.
Verify Data
hashed in your browser — nothing is uploaded
⬗
Drop a file or click to choose one
keccak256 is computed locally (this hub's archive itself also supports blake2s — if your file doesn't match here, try pasting its hash directly instead)
or look up a version hash directly
Captured Blobs Archive
from this hub's own archive
Version hashHeightSizeCapturedStatus
Not configured on this deployment yet.
Unofficial, community-built demo. Blob payloads older than the network's ~6h cache window are served from this hub's own archive, bounded to a configured storage quota — this is not a permanent archive of every blob ever committed. Every response is independently verifiable against the on-chain version hash; the archive is a convenience layer, never a trusted one. Blobs this hub never captured, and that have since aged out of the node's cache, cannot be recovered by anyone.