ENTITY Documentation Portal
Operator manual · current release

Install ENTITY v3.4.3

Legacy URL note: this page keeps its historical filename for link compatibility. The supported tagged release is v3.4.3; v3.4.2 and earlier remain immutable historical evidence. Newer main enhancements require separate qualification.

Current operator status: Current implementation and qualification status. Do not apply local wallet/formula migrations by running installation commands for the protected tag without a separate tested procedure.

Reference environment

Use Python 3.11+ for the reference implementation. Install into an isolated virtual environment. Do not put operational identity keys, recovery material, production databases or private backups inside the Git repository.

git clone https://github.com/blackmore-technology-group/ENTITY.git
cd ENTITY
git checkout v3.4.3
python -m venv .venv
# Windows: .\.venv\Scripts\Activate.ps1
# Linux/macOS: source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -r requirements.txt
python -m compileall -q src sdk protocol
python -m unittest discover -s tests -v

Verify release identity

Before production use, confirm the checkout resolves to tag v3.4.3 and compare the protected release commit 528b70aabd05b1e930b77e4933f157731e47274f. The release tree is f13e42f515dcc4cd985e9b832e0ecfec416ce423.

State placement

Keep mutable runtime state outside the source tree. Separate at minimum: source checkout, ENTITY state, BTDU state, backups/exports, evidence archives and any hardware-key-protector configuration. Set filesystem permissions so ordinary application users cannot read private key material.

BTDU prerequisites

The BTDU operator CLI requires the ENTITY state directory, BTDU state directory and a qualified ADAM runtime root. The CLI verifies ENTITY authorization before mutating BTDU state.

python tools/entity_btdu_cli.py --entity-state E:\ENTITY_STATE --btdu-state E:\BTDU_STATE --adam-root D:\ADAM_ROOT --git-bin git status

Post-install checks