ENTITY Documentation Portal
ENTITY security

Security protects authority and economic state together

ENTITY security is not limited to identity keys. The runtime must protect delegated authority, rights, encrypted information, signed market intents, balances, entitlements, revenue rules, settlement evidence, causal lineage, offline partitions and recoverable economic state.

Independent security assessment remains a separate evidence class. These pages describe implemented and operational controls, not an independent certification.

Authority & key security

Information security

Encrypted vaults

Owner-controlled AES-256-GCM content storage keeps plaintext outside ledger state and supports deletion/cryptographic-erasure states.

Purpose-bound access

Signed grants can constrain purpose, action, expiry and use count; use is recorded with evidence and revocation fails closed.

Retention & destruction

Retention records preserve commitments while controlled payload destruction, redaction, external-copy destruction and legal holds remain explicit.

Market integrity controls

Signed canonical intents

Instruments, orders, cancellations, RFQs, quotes, acceptances, revenue-rule sets and payment attestations use canonical signed shapes.

Replay resistance

Market actions use unique nonces/receipt state so duplicate signed execution paths do not silently become multiple economic events.

Rights/balance checks

Instrument issuance and execution are tied to underlying controllers, rights and balances rather than trusting venue possession.

Settlement verification

Payment attestations require authorized settlement verifiers and evidence hashes. The system preserves that verification is an attestation, not absolute external truth.

Revenue-rule integrity

Explicit rule sets bind allocation state to trades and reject allocation totals above 10,000 basis points.

Recoverable market state

Required exchange/participation tables are semantically hashed and restored as logical state rather than treating database bytes as authority.

Distributed and offline security

Partition checkpoints

Signed state roots and vector clocks allow causal comparison after partitioned operation.

No automatic last-writer-wins

Concurrent divergent sovereign state becomes an explicit conflict instead of silently discarding one branch.

Offline envelopes

Disconnected payloads remain signed, expiry-bounded and do not automatically gain merge authority merely because they verify.

Cryptographic agility

Crypto-suite migration supports activation, deprecation, retirement, dual-sign transition periods, verifier binding and downgrade resistance so identity continuity does not have to be replaced when cryptography evolves.

Evidence and supply-chain threats