🛡️ AetherIdentity v2.0.0
A Falsification-First Investigation of Decentralized Agent Identity in the Aether Family
Identity Proof, Continuity, Reputation, Sybil Resistance, and Delegation in Multi-Agent Software Ecosystems
"AetherIdentity is a candidate, not a result."
"Not falsified is a weaker status than confirmed."
How to cite
If you use AetherIdentity in your research, please cite:
- Paper (v1.0.0): Baladi, S. (2026). AetherIdentity: A Falsification-First Investigation of Decentralized Agent Identity in the Aether Family (Version 1.0.0). Zenodo. 10.5281/zenodo.24102739
- Software (v2.0.0): Baladi, S. (2026). AetherIdentity v2.0.0: Reference Implementation of the Falsification-First Identity Architecture (Version 2.0.0). PyPI. pypi.org/project/aetheridentity
- OSF Preregistration: Baladi, S. (2026). AetherIdentity: A Falsification-First Investigation of Decentralized Agent Identity in the Aether Family. OSF. 10.17605/OSF.IO/B6AEN
Full BibTeX entries are in the BibTeX section below.
Table of Contents
- Overview
- Version series
- What v2.0.0 supports
- Test results
- Experimental results
- What v2.0.0 does not claim
- Project Structure
- Installation
- Reproduction
- How to cite
- BibTeX
- Related Aether Records
- Author
- License
Overview
AetherIdentity is the eighth functional dimension (candidate, provisional) of the Aether family: a formal architecture for identity proof, continuity, reputation, Sybil resistance, and delegation in multi-agent software ecosystems.
The Aether family currently comprises seven foundational dimensions (AetherGit, AetherFlow, AetherProof, AetherMesh, AetherGovern, AetherRuntime, AetherOrchestrate). All rely on a notion of who acts, but none treats identity itself.
The framework investigates whether those five concerns amount to a genuine gap that justifies an eighth dimension, or are an artifact of how the existing dimensions were scoped.
The five layers:
| Layer | Question |
|---|---|
| L1 — Identity | Who is the agent, and can it prove it? |
| L2 — Continuity | Does the identity persist across restarts and key changes? |
| L3 — Reputation | What is the agent's behavioral history? |
| L4 — Sybil resistance | Are multiple identities controlled by one entity? |
| L5 — Delegation | Can authority be transferred with bounded scope? |
Version series
| Version | Status | Artifact |
|---|---|---|
| v0.1.0 | Architectural Hypothesis | Original draft |
| v1.0.0 | Formal Architecture Proposal | 33-page paper, published on Zenodo and Figshare |
| v2.0.0 | Experimental Reference Implementation | Code, tests, experiments, report |
The paper (v1.0.0) is not modified by v2.0.0. v2.0.0 implements it, and reports where it cannot be implemented.
What v2.0.0 supports
| Component | Status |
|---|---|
| L1 — Identity | ✅ Implemented |
| L2 — Continuity | ✅ Implemented |
| L3 — Reputation | ✅ Implemented |
| L4 — Sybil resistance | ✅ Implemented |
| L5 — Delegation | ✅ Implemented |
| Simulator | ✅ Implemented |
| Signer interface | ✅ Implemented |
| Record types | ✅ Implemented |
Not implemented (out of scope for v2.0.0):
- Network transport and consensus
- AetherMesh integration (optional, S7)
- Fork resolution
- Recovery after total key loss
- Single-instance enforcement
- Byzantine behavior
See SPECIFICATION.md §11.
Test results
| Metric | Value |
|---|---|
| Tests collected | 35 |
| Tests passed | 35 |
| Tests failed | 0 |
| Coverage | 93% |
All 12 core invariants (I1–I12) are covered. See REPORTS/v2.0.0/test_report.md and INVARIANTS.md.
Experimental results
| Scenario | Purpose | Result |
|---|---|---|
| S1 — Bootstrap | Test P2 (irreducible trust anchor) | P2 not falsified (bootstrap requires an anchor) |
| S6 — Governance overlap | Test F3 (boundary with governance) | F3 inconclusive (fragile: holds in some uses, fails in others) |
| S2–S5 | Deferred | Not run; reported as deferred |
Scenarios S2–S5 are deferred and reported as such. See REPORTS/v2.0.0/evaluation_report.md.
The evaluation plan was preregistered on OSF: 10.17605/OSF.IO/B6AEN.
What v2.0.0 does not claim
- It does not claim that AetherIdentity is confirmed.
- It does not claim that F1–F5 are "not falsified".
- It does not claim that P1–P2 are proven.
- It does not claim that the architecture is production-ready.
- It does not claim that the simulator is representative of real deployments.
This is a research artifact, not a product.
Project Structure
AetherIdentity/
├── README.md
├── SPECIFICATION.md
├── INVARIANTS.md
├── TESTS.md
├── ROADMAP_v2.md
├── pyproject.toml
├── src/
│ └── aetheridentity/
│ ├── __init__.py
│ ├── records.py
│ ├── signer.py
│ ├── simulator.py
│ ├── identity.py
│ ├── continuity.py
│ ├── reputation.py
│ ├── sybil.py
│ └── delegation.py
├── tests/
│ ├── conftest.py
│ ├── test_smoke.py
│ ├── test_continuity.py
│ ├── test_reputation.py
│ ├── test_sybil.py
│ └── test_delegation.py
├── experiments/
│ ├── S1_bootstrap/
│ └── S6_governance_overlap/
├── DATA/
│ └── synthetic/
├── ANALYSIS/
│ └── coverage.json
├── REPORTS/
│ └── v2.0.0/
├── RELEASE/
│ └── RELEASE.md
├── docs/
│ └── figures/
└── paper/
└── AetherIdentity_Research_Paper.pdf
Installation
Requires Python 3.10+. Runtime dependency: cryptography >= 41.0.
PyPI package: aetheridentity
# From PyPI (once published)
pip install aetheridentity
# From source (development)
git clone https://github.com/gitdeeper15/aetheridentity.git
cd aetheridentity
pip install -e ".[dev]"
# Run tests
pytest
# Run experiments
python experiments/S1_bootstrap/run.py
python experiments/S6_governance_overlap/run.py
Reproduction
# Full test run with coverage
pytest tests/ -v --cov=src/aetheridentity --cov-report=term-missing
# S1 — Bootstrap (P2)
python experiments/S1_bootstrap/run.py
cat experiments/S1_bootstrap/results.json
# S6 — Governance overlap (F3)
python experiments/S6_governance_overlap/run.py
cat experiments/S6_governance_overlap/results.json
The expected output matches REPORTS/v2.0.0/test_report.md and REPORTS/v2.0.0/evaluation_report.md.
BibTeX
Paper — AetherIdentity v1.0.0 (Zenodo)
@techreport{baladi2026aetheridentity,
author = {Baladi, Samir},
title = {AetherIdentity: A Falsification-First Investigation of
Decentralized Agent Identity in the Aether Family},
institution = {Ronin Institute / Rite of Renaissance},
type = {Research Paper},
year = {2026},
month = {November},
version = {1.0.0},
doi = {10.5281/zenodo.24102739},
url = {https://doi.org/10.5281/zenodo.24102739},
note = {Formal Architecture Proposal --- No implementation claimed.}
}
Software — AetherIdentity v2.0.0
@software{baladi2026aetheridentity_v2,
author = {Baladi, Samir},
title = {{AetherIdentity} v2.0.0: Reference Implementation of the
Falsification-First Identity Architecture},
year = {2026},
month = {November},
version = {2.0.0},
doi = {10.5281/zenodo.24102739},
url = {https://doi.org/10.5281/zenodo.24102739},
note = {Reference implementation. Paper: v1.0.0.}
}
OSF Preregistration
@misc{baladi2026aetheridentity_osf,
author = {Baladi, Samir},
title = {{AetherIdentity: A Falsification-First Investigation of
Decentralized Agent Identity in the Aether Family}},
year = {2026},
month = nov,
day = {11},
publisher = {OSF},
doi = {10.17605/OSF.IO/B6AEN},
url = {https://doi.org/10.17605/OSF.IO/B6AEN},
note = {OSF Preregistration for the v2.0.0 evaluation plan.
Associated project: https://osf.io/5y783}
}
Related Aether Records
| Dimension | Focus | DOI |
|---|---|---|
| AetherGit | Storage and versioning | 10.5281/zenodo.23966896 |
| AetherFlow | Integration and verification | 10.5281/zenodo.23979129 |
| AetherProof | Specification and evidence | 10.5281/zenodo.24013124 |
| AetherMesh | Distribution and consistency | 10.5281/zenodo.24038038 |
| AetherGovern | Authority and policy | 10.5281/zenodo.24054524 |
| AetherRuntime | Monitoring and assurance | 10.5281/zenodo.24078477 |
| AetherOrchestrate | Orchestration | 10.5281/zenodo.24095399 |
| AetherIdentity (candidate) | Identity and continuity | 10.5281/zenodo.24102739 |
Package: aetheridentity on PyPI — v2.0.0 reference implementation.
Author
Samir Baladi Interdisciplinary AI Researcher, Ronin Institute / Rite of Renaissance
| Research area | Distributed Systems / Security / Multi-Agent Systems |
| Research domain | Identity, Continuity, Reputation, Sybil Resistance, Delegation |
| Research type | Formal Architecture Proposal + Reference Implementation |
| gitdeeper@gmail.com | |
| ORCID | 0009-0003-8903-0029 |
| GitHub | gitdeeper15/aetheridentity |
| GitLab | gitlab.com/gitdeeper15/aetheridentity |
| Codeberg | codeberg.org/gitdeeper15/aetheridentity |
| Bitbucket | bitbucket.org/gitdeeper15/aetheridentity |
| PyPI | pypi.org/project/aetheridentity |
| Website | aetheridentity.netlify.app |
License
| Scope | License |
|---|---|
| Code | MIT License, Copyright © 2026 Samir Baladi |
| Documentation, manuscript, and figures | CC-BY-4.0 |
MIT License — full text
MIT License
Copyright (c) 2026 Samir Baladi
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
AetherIdentity v2.0.0 — Experimental Reference Implementation. © 2026 Samir Baladi — Ronin Institute / Rite of Renaissance — MIT (code) + CC-BY-4.0 (docs). Zenodo: 10.5281/zenodo.24102739 · Figshare: 10.6084/m9.figshare.34981891 · OSF: 10.17605/OSF.IO/B6AEN · PyPI: aetheridentity · Website: aetheridentity.netlify.app
Metadata
Release files for aetheridentity 2.0.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 | Provenance | Actions |
|---|---|---|---|---|
| aetheridentity-2.0.0.tar.gz | 2.0 MB | Without provenance | Details for aetheridentity-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aetheridentity-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for aetheridentity-2.0.0-py3-none-any.whl |
Total release size: 2.0 MB
Release files / aetheridentity-2.0.0.tar.gz
| Download URL | aetheridentity-2.0.0.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cde8dec3689575c498ec68c1f45ed8a923932b0ef7da0eb3b74a128e1e112b9a
|
|
BLAKE2b-256 checksum How to use checksums |
203f8a1cc1bc697e8b46a642e65258d9743717a4acba6c213aa741bd1b54e4d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.33.1
|
Release files / aetheridentity-2.0.0-py3-none-any.whl
| Download URL | aetheridentity-2.0.0-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1841144ec91fb82b4965de2d48075ac913eca096d17ce7669198be14ac1f5d28
|
|
BLAKE2b-256 checksum How to use checksums |
660792750dfee2b243760a4705f904623472ca5cf9092e9a7c5513836ab3d3ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.33.1
|
Security for aetheridentity 2.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.