archon core — Python
The identity floor in Python: Ed25519 key bytes, one canonical text spelling, the SPKI and PKCS-8 codecs, and domain-separated signing.
pip install bitspark-archon-core
The distribution is bitspark-archon-core; the import is archon_core. The prefix is a
registry name only — PyPI, like crates.io, has a single flat namespace.
from archon_core import (
public_key_from_seed, encode_key, sign_in_domain, verify_in_domain,
)
seed = bytes(range(32))
pub = public_key_from_seed(seed)
encode_key(pub)
# 'ed25519:03a107bff3ce10be1d70dd18e74bc09967e4d6309ba50d5f1ddc8664125531b8'
sig = sign_in_domain(seed, "example.v1", b"hello")
verify_in_domain(pub, "example.v1", b"hello", sig) # True
verify_in_domain(pub, "other.v1", b"hello", sig) # False — domains do not cross
What it is
Two questions and no others: are these bytes that key, and is this signature that key's. Authority and custody belong to their own layers — see the repository README.
crypto |
public_key_from_seed, sign/verify, sign_in_domain/verify_in_domain |
hexbytes |
to_hex, and fixed-size decoders that accept exactly N bytes or fail |
keytext |
encode_key/decode_key — ed25519:<64 hex> |
keycodec |
RFC 5280 SPKI and RFC 5958 PKCS-8 v1 PEM, as a byte codec |
Agreement is the claim
This core is held to the same hand-authored oracle as the Go, Rust and TypeScript cores —
60 cases in vectors/identity.json,
recomputed rather than echoed. If it disagrees with the others about whether something is a
valid key, signature or key text, that disagreement is the defect.
Two places where Python needed care to agree, both recorded in the source:
sign_in_domainis Ed25519ph with the domain as the RFC 8032 §5.1 context.cryptographycannot express it — it offers only puresign(data). This package binds PyCryptodome, which can.- Small-order public keys are rejected. PyCryptodome's verifier accepts them; Go's
crypto/ed25519anded25519-dalekdo not. archon's profile is to reject, soverifychecks[8]Aagainst the identity using the library's own point arithmetic. Without it, two oracle cases pass in Python and fail everywhere else.
Verification
Signing raises rather than silently signing raw: an empty domain, or one over 255 bytes, is
an error. Verification is total — every shape failure returns False, so a caller cannot
mistake malformed for valid.
License
Release files for bitspark-archon-core 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bitspark_archon_core-0.7.0.tar.gz | 16.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bitspark_archon_core-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.2 kB
Release files / bitspark_archon_core-0.7.0.tar.gz
| Download URL | bitspark_archon_core-0.7.0.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcdd3d3292912cb4d0a2ab9f21300d1d769162b0eeccffa5a56c41aa2d6cd025
|
|
BLAKE2b-256 checksum How to use checksums |
622197cea04d5dc899cf7bed1a9f71759855006c0ec8d99d62400ab77b314c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / bitspark_archon_core-0.7.0-py3-none-any.whl
| Download URL | bitspark_archon_core-0.7.0-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a27386624f44a26581cd67147035267a7d85d82b0d59579a43ebf9f82dd4abc4
|
|
BLAKE2b-256 checksum How to use checksums |
164f6a919961a69276a67f26aaf2347b639f7fae132f5c52e29814d78f904ab6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log