Pith Number
pith:JL42GEAC
pith:2018:JL42GEACETH5UN7NJCACEY2RVK
not attested
not anchored
not stored
refs pending
How does the AI understand what's going on
arxiv:1805.00851 v1 · 2018-04-27 · cs.AI
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{JL42GEACETH5UN7NJCACEY2RVK}
Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge
Record completeness
1
Bitcoin timestamp
2
Internet Archive
3
Author claim
· sign in to
claim
4
Citations
5
Replications
✓
Portable graph bundle live · download bundle · merged
state
The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same
current state with the deterministic merge algorithm.
Receipt and verification
| First computed | 2026-05-18T00:16:57.482656Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
4af9a3100224cfda37ed4880226351aa8961f183daeda6435fb122786ab8f35c
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/JL42GEACETH5UN7NJCACEY2RVK \
| jq -c '.canonical_record' \
| python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: 4af9a3100224cfda37ed4880226351aa8961f183daeda6435fb122786ab8f35c
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "894358b58344816383dd038e8b4d11a42f90fbda6fb89b7103f881e2028c862d",
"cross_cats_sorted": [],
"license": "http://arxiv.org/licenses/nonexclusive-distrib/1.0/",
"primary_cat": "cs.AI",
"submitted_at": "2018-04-27T11:06:29Z",
"title_canon_sha256": "afe11e68be935e7a8f8bdb4b2ba396861b2ab57db37f83546872aae7513292d4"
},
"schema_version": "1.0",
"source": {
"id": "1805.00851",
"kind": "arxiv",
"version": 1
}
}