Pith Number
pith:4Z4RNXGQ
pith:2019:4Z4RNXGQPYA33JG4BQFP76SS6M
not attested
not anchored
not stored
refs pending
How Should I Orchestrate Resources of My Slices for Bursty URLLC Service Provision?
arxiv:1912.00579 v4 · 2019-12-02 · cs.NI · eess.SP
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{4Z4RNXGQPYA33JG4BQFP76SS6M}
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-05T01:49:48.578927Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
e67916dcd07e01bda4dc0c0afffa52f324d01ce32e8c68438cd78d40179b657d
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/4Z4RNXGQPYA33JG4BQFP76SS6M \
| 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: e67916dcd07e01bda4dc0c0afffa52f324d01ce32e8c68438cd78d40179b657d
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "d3e38339decad121e91d39a6a01e5453936da983519e0a809af5bccbbf0d9237",
"cross_cats_sorted": [
"eess.SP"
],
"license": "http://arxiv.org/licenses/nonexclusive-distrib/1.0/",
"primary_cat": "cs.NI",
"submitted_at": "2019-12-02T05:03:06Z",
"title_canon_sha256": "444a911c88ee31b3aa1e91bb47895a5b4dfb71b0ad41df2fa1fbdafc542f350e"
},
"schema_version": "1.0",
"source": {
"id": "1912.00579",
"kind": "arxiv",
"version": 4
}
}