Artifacts

The ticket-side artifact registry — congruency holds the metadata and the provenance, the forge holds the blob. Kind is the tag: open a kind to list its artifacts, or an artifact to see every location its content sha is registered at.

artifacts › sha cafa1a965b59

Name
noble-arm64-base
Kind
forge-vm
Version
cafa1a965b59
Forge sha
cafa1a965b591b7c4184b484ffd8e625981a79d48f9b4ae8a4adf7b4c5ade927
Locations
1 registration · minted by #455
First seen
2026-07-16 05:21 UTC

This sha is the content address of the blob itself, so it is shown in full: it is what the universal resolver takes as input — python3 tools/resolver.py cafa1a965b591b7c4184b484ffd8e625981a79d48f9b4ae8a4adf7b4c5ade927 — which probes forge-artifacts and returns every place those bytes live. The registry below lists every place they were registered.

Every location this sha is registered at
#MINTING TICKETNAMEVERSIONKINDREGISTERED
8#455noble-arm64-basecafa1a965b59forge-vm2026-07-16 05:21 UTC

These bytes are registered at exactly one location. Were the same sha registered again — under another ticket, name or version — it would appear here as a second location of this one artifact, not as a second artifact.

← all kinds