ECDSA P-256 · NIST FIPS 186-4 · Merkle Inclusion Proofs

SentinelChain
Signed Audit Infrastructure

A private blockchain purpose-built for government audit trails. Every security event is signed by the node that reports it, sealed into a hash-linked block and given a Merkle inclusion proof an auditor can recompute.

Request Live Demo
2.13M+
Blocks Notarized
63
Nodes Admitted

Fleet figures as of August 28, 2026 · kbsoftware.org/api/chain/stats

// Live API Response
Query the Chain
# Verify chain integrity — independently auditable by any party
# chain: sentinel-mainnet-1 (demo chain) — check run 2026-08-28
GET /chain/verify

{ "verified": true,
  "blocks_checked": 63842,
  "hash_algorithm": "SHA-256 Merkle",
  "signature_algorithm": "ECDSA P-256 (NIST FIPS 186-4)",
  "last_block_hash": "a3f8c2e1...",
  "hash_links": "OK" }
// Technical Architecture
How SentinelChain Works
01

Event Submission

Security events (audit actions, build completions, access logs) are submitted via REST API. Each event is hashed with SHA-256 and signed with ECDSA P-256 by the submitting node using its registered private key.

02

Pending Transaction Pool

Signed transactions enter a pending pool. Each transaction includes: event_type, event_data JSON, ECDSA signature, node_id, and timestamp. Each one is stored with its event hash and signature.

03

Block Signing

Each sealed block is signed by three of the chain's five block-signing keys. Today all five keys are hosted on the same server, so this is not an independent quorum; moving them to separate hosts is on the roadmap.

04

Block Sealing + Merkle Tree

Sealed transactions are organized into a Merkle tree. The root hash, previous block hash, block signatures, and timestamp are committed to a new block. Block heights are sequential, and each block carries the previous block's hash.

05

Inclusion Proof Generation

For every sealed transaction, a Merkle inclusion proof is generated and stored. Any auditor can look up a transaction hash and receive the Merkle proof that places it in a specific block, then recompute that proof themselves.

06

Independent Audit API

Auditors connect directly via REST API: GET /verify/tx/{hash} returns the inclusion proof. GET /chain/verify validates the entire chain. No proprietary software required — standard ECDSA and SHA-256 tools suffice.

// REST API Endpoints
Full API Reference

POST /transactions/submit

Submit a signed audit event. Requires: node_id, event_type, event_payload, event_hash, ECDSA signature. Returns: tx_id for tracking.

AuthenticationECDSA

GET /chain/verify

Chain linkage check: recomputes every block hash and confirms each block points to the previous one. Returns pass/fail with block count. A full audit of Merkle roots and signatures is run offline; an on-line full verifier is in development.

AuditPublic

GET /audit/{event_hash}

Returns the transaction, its block and its Merkle inclusion proof, so an auditor can recompute that the event is part of that block.

ProofZero-Trust

GET /blocks/{height}

Retrieve full block data: all sealed transactions, Merkle root, block signatures, previous block hash, timestamp.

Chain Data

POST /nodes/register

Register an agency or contractor node. Provide hardware fingerprint, ECDSA public key (DER), and organizational metadata.

Node EnrollmentECDSA P-256

GET /demo/audit-report

Pre-built government demonstration endpoint. Returns 90-day simulated audit timeline with attack detection events and chain proof.

DemoGovernment
// Compliance + Standards
Built to Government Standards

NIST FIPS 186-4

ECDSA P-256 digital signature standard. The same curve used by US government systems, TLS 1.3, and modern HSMs. Keys generated with OS cryptographic entropy.

CMMC Level 2+ Alignment

Signed, hash-linked audit records, access logging, cryptographic evidence of actions — requirements SentinelChain's design is aimed at.

Independent Verification

Every production record carries the submitting node's ECDSA signature. Auditors can recompute block hashes and Merkle proofs from the raw data themselves.

On-Premises Only

Entire chain runs on KB Software-owned infrastructure in Boca Raton, FL. No data transmitted to third-party clouds. Full data residency control available.

// Government Demo Available

See it Live in 30 Minutes

We walk you through a live chain verification: submit an event, watch it anchor, verify the Merkle proof. Every claim we make, demonstrated in real time.

Schedule a Demo