HostraCore logoHostra
Trust

Audit Trail

HostraCore maintains a tamper-evident audit log using a hash-chain: every audit event is hashed together with the previous event's hash, and a verify endpoint recomputes the chain to detect any tampering.

How the chain works

  • Every state-changing operation appends an immutable audit event.
  • Each event stores hash = H(previous_hash || canonical_event_payload).
  • Editing or deleting any historical event breaks every hash after it.
  • GET /v1/audit/verify recomputes the chain and reports the first divergence, if any.
  • GET /v1/audit/events streams the chain for external archival.

Verification

curl https://api.hostracore.com/v1/audit/verify \
  -H 'Authorization: Bearer hstra_...'

# → { "valid": true, "events_checked": 128401, "head_hash": "9f2c…" }

The audit surface requires the audit:read scope. Verification is deterministic: the same chain always yields the same head hash, so an external party can archive the head and re-check it later.

What is recorded

  • Authentication events: registration, login, password reset, API key creation and revocation.
  • Settlement lifecycle: intent creation, lease acquisition, provider call, terminal commit, reversal.
  • Saga transitions for card_to_crypto, including compensation.
  • Webhook deliveries and their signature material.