Scores
Methodology
Post breakdown
Onchain anchor
NOT YET SEALED
This epoch has not been anchored onchain yet. Sealing occurs automatically at the epoch boundary.
Snapshot hash
f7ab60a4fa8b89207502c93470d93ac11c3784cbb98af1b55736cae9f51d092b
SHA-256 of the canonical scoring snapshot. This hash is what gets written onchain.
How to verify this score
Anyone can independently reproduce this hash and confirm it matches what is stored onchain. If the hash matches, the score has not been altered since sealing.
01 — Copy the snapshot JSON
The full scoring snapshot is stored in the database and visible via the API at /api/audit/3c79abf3-6b56-42de-830d-db9d3fe0a447. The snapshot_json field contains every input used to produce this score.
02 — Reproduce the hash
Run the following Python snippet with the snapshot JSON:
import json, hashlib
# Paste snapshot_json here
snapshot = { ...paste full JSON object... }
canonical = json.dumps(
snapshot,
sort_keys=True,
separators=(',', ':'),
ensure_ascii=False
)
result = hashlib.sha256(canonical.encode('utf-8')).hexdigest()
print(result)
# Should match: f7ab60a4fa8b89207502c93470d93ac11c3784cbb98af1b55736cae9f51d092b03 — Check onchain
If the hash you computed matches the snapshot hash above, and that hash matches the snapshotHash argument in the Snowtrace transaction, the score is verified. No tampering has occurred.
Changing any score by 0.01, altering a post count, or modifying any field in the snapshot produces a completely different hash — making the discrepancy immediately detectable. The scoring rules (prompt version, methodology version, model) are also written into the snapshot, so any change to the classification logic is visible in the hash.
Tessera does not evaluate truthfulness, moral alignment, or content quality. It evaluates structural behavioral properties only.