Pith Number
pith:Z2SHS36M
pith:2017:Z2SHS36MYGQKZNMMZIXLHVERNX
not attested
not anchored
not stored
refs pending
Can Two-Way Direct Communication Protocols Be Considered Secure?
arxiv:1709.09262 v1 · 2017-09-26 · quant-ph · cs.CR
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{Z2SHS36MYGQKZNMMZIXLHVERNX}
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:34:12.361616Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
cea4796fccc1a0acb58cca2eb3d4916df78ebf9c28584f50a38148ad1fa9c356
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/Z2SHS36MYGQKZNMMZIXLHVERNX \
| 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: cea4796fccc1a0acb58cca2eb3d4916df78ebf9c28584f50a38148ad1fa9c356
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "fb7a5e5862e3331da3f5f8962b737f2e23750a9dda1e06c95a42280b1c41d97f",
"cross_cats_sorted": [
"cs.CR"
],
"license": "http://arxiv.org/licenses/nonexclusive-distrib/1.0/",
"primary_cat": "quant-ph",
"submitted_at": "2017-09-26T21:13:07Z",
"title_canon_sha256": "b49f90698560e8aa2e95d4aaf86a2076ba83773ce5c17560b6f45fe38ef0f6c8"
},
"schema_version": "1.0",
"source": {
"id": "1709.09262",
"kind": "arxiv",
"version": 1
}
}