hikari-ledger
Proof-of-Resonance distributed consensus for genesis-os node networks — a CREP-weighted alternative to Proof-of-Work and Proof-of-Stake.
Instead of energy-intensive hash computation (PoW) or capital-based staking (PoS), Proof-of-Resonance (PoR) validates blocks based on each node's CREP harmonic state — the same Coherence/Resonance/Emergence/Poetics tensor used throughout the GenesisAeon ecosystem. Nodes whose CREP state is in higher harmony with the network (higher Γ) earn proportionally more validation weight; a block is accepted once weighted agreement crosses the classic Byzantine fault tolerance threshold of 2/3.
Installation
pip install hikari-ledger
Usage
from hikari_ledger import HikariLedger
ledger = HikariLedger(seed=42)
result = ledger.run_cycle(n_nodes=50, n_blocks=100)
print(result["acceptance_rate"])
print(ledger.get_crep_state()) # {"C": ..., "R": ..., "E": ..., "P": ..., "Gamma": ...}
print(ledger.get_utac_state()) # {"H": ..., "H_star": 0.667, "K": 1.0, ...}
print(ledger.get_phase_events()) # consensus failures / forks
print(ledger.to_zenodo_record())
Or via the CLI:
hikari-ledger run --nodes 50 --blocks 100
hikari-ledger simulate-attack --byzantine-fraction 0.30
hikari-ledger energy-comparison --vs-pow --vs-pos
Physical mapping (UTAC)
| UTAC symbol | Meaning in PoR |
|---|---|
H(t) |
network consensus strength (fraction of weighted agreement) |
K |
1.0 (perfect consensus) |
H* |
2/3 (Byzantine fault tolerance threshold) |
Γ |
per-node CREP coupling, derived from coherence/resonance/emergence/poetics |
Γ_PoR = arctanh(2/3) / σ ≈ 0.367. CONSENSUS_THRESHOLD=2/3 is a genuine
mathematical fact (Byzantine fault tolerance), but σ=2.2 is a shared
default reused unchanged across unrelated GenesisAeon UTAC packages and
never independently derived for distributed-consensus systems — so
Γ_PoR is not independently comparable to other domains' Γ values.
Its apparent closeness to the Manna sandpile SOC value (0.376,
sandpile-utac) is a coincidence of similar threshold magnitudes both
passing through the same shared σ, not evidence that PoR consensus and
sandpile dynamics share underlying physics — see constants.py's
GAMMA_POR docstring for the full reasoning.
Role in the GenesisAeon Ecosystem
hikari-ledger is P29 in the GenesisAeon CREP Criticality Spectrum,
representing the distributed-systems domain. It implements the
Proof-of-Resonance consensus layer used to coordinate genesis-os node
networks, weighting validation rights by each node's measured CREP state
rather than computational work or staked capital.
Citation
Metadata
Release files for hikari-ledger 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hikari_ledger-1.0.1.tar.gz | 86.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hikari_ledger-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 103.2 kB
Release files / hikari_ledger-1.0.1.tar.gz
| Download URL | hikari_ledger-1.0.1.tar.gz |
|---|---|
| Size | 86.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
965be432dddf613c400515bcfe2b14ab7a60ae0c3c185e3769f807c3ed7c2e0d
|
|
BLAKE2b-256 checksum How to use checksums |
313dcd5a0ab67ddb03708b7cada90a7dc1af70a822883f5a319f35dc8bb5140b
|
| 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 15, 2026.
Transparency logRelease files / hikari_ledger-1.0.1-py3-none-any.whl
| Download URL | hikari_ledger-1.0.1-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51f1efb6585923f6f650183c822cff0f171b5ff2b7a9678675da8256d6ec28bd
|
|
BLAKE2b-256 checksum How to use checksums |
cc2dfc07511a2018b16ce33654e70ac22d07671a624eb91297768a852512acf7
|
| 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 15, 2026.
Transparency log