ABS Core v3.5.0

Ledger Anchoring

How ABS Core handles eventual consistency and immutable anchoring on Public L2 / Ethereum.

Ledger & Proof of Accountability (PoA)

While the Hot Path handles sub-5ms enforcement, the Ledger Path implements Proof of Accountability (PoA). This cryptographic model ensures that every action is irreversible and verifiable by third-party auditors.

Tiered Immutability Model

ABS Core uses a three-tier model to guarantee integrity:

  1. L1: Local Chaining (Hot): HMAC-SHA256 chaining of events at the moment of enforcement.
  2. L2: Batch Merkle Roots (Internal): Periodic Merkle Tree generation to provide summary proofs of 5,000+ events.
  3. L3: Sovereign Anchoring (External): Merkle Roots are anchored to Public Blockchain Infrastructure. Currently:
    • Bitcoin (Mainnet): Final integrity anchor via OpenTimestamps for high-value audit chains.
    • Polygon Amoy (Testnet): Used for low-latency proof-of-concepts and developer sandboxes. Mainnet L2 bridges are available for institutional deployments requiring high-throughput on-chain state updates.

Why PoA beats simple Logging

Traditional logs can be deleted by a Root administrator. Proof of Accountability ensures that:

  • Any deletion breaks the hash chain (visible to auditors).
  • The public anchor proves the state of the logs at a specific point in time.
  • The Agent's signature (via OID) is bound to the intent, making the action legally irrefutable.

[!TIP] This "Bifurcated" design allows us to claim both Industrial Performance and Regulatory-Grade Accountability simultaneously.

On this page