Pith Number
pith:BMWRE3KE
pith:2022:BMWRE3KEFTSRK5FM2DMIEUDX74
not attested
not anchored
not stored
refs pending
Do we really need temporal convolutions in action segmentation?
arxiv:2205.13425 v2 · 2022-05-26 · cs.CV
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{BMWRE3KEFTSRK5FM2DMIEUDX74}
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-07-05T05:18:03.910195Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
0b2d126d442ce51574acd0d8825077ff283934f237c5420131eac2156b5cb4b0
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/BMWRE3KEFTSRK5FM2DMIEUDX74 \
| 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: 0b2d126d442ce51574acd0d8825077ff283934f237c5420131eac2156b5cb4b0
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "484170eadef7c0d4d2764eab13402a8f309fd78f46e2f5394210ad3a3844ec9a",
"cross_cats_sorted": [],
"license": "http://arxiv.org/licenses/nonexclusive-distrib/1.0/",
"primary_cat": "cs.CV",
"submitted_at": "2022-05-26T15:30:34Z",
"title_canon_sha256": "308e732edd8a237659ecf45b2cb5d5e149e446842fae45ad5278b91ef7ab9032"
},
"schema_version": "1.0",
"source": {
"id": "2205.13425",
"kind": "arxiv",
"version": 2
}
}