v0.1.0-alpha

Initial alpha release of the Sankofa Engine.

v0.1.0-alpha

Release date: 2026-04-03 Status: Pre-release (Alpha)

Summary

Initial alpha release of the Sankofa Engine — a sharded, privacy-preserving financial ledger engine for digital assets.

Features

Core Ledger

  • Sharded transaction processing with FNV-1a hash-based routing
  • Block-based transaction batching with in-memory balance cache
  • SHA-256 audit hash chain per account
  • ECDSA P-256 signed transaction receipts
  • Exactly-once processing via NATS JetStream deduplication and idempotency keys

Multi-Asset Support

  • Fungible token registration, minting, burning, and transfer
  • NFT class registration, instance minting, transfer, burn, and provenance tracking

Privacy & Compliance

  • AES-GCM-256 envelope encryption with KMS-derived keys
  • Zero-knowledge proof generation: proof-of-liabilities, proof-of-provenance, proof-of-compliance
  • Proof verification endpoint
  • Asset attestation support

API

  • REST API via Fiber v3 with JWT authentication
  • ECDSA P-256 transaction signing for self-custody model
  • RFC 7807 Problem Details error format
  • Casbin v2 RBAC authorization

Infrastructure

  • 8 microservices: API Gateway, Shard Worker, Shard Orchestrator, Projection, Compliance, Settlement, Archival, DevCtl
  • Kubernetes-native deployment with HPA, health probes, network policies
  • ScyllaDB (ledger), PostgreSQL (projections), NATS JetStream (messaging), OpenBao (key management)
  • Hot/cold tier archival with configurable retention policies

Known Issues

  • OpenBao KMS service integration is in progress
  • ZKP backend is placeholder — proof generation logic is stubbed
  • Durable Local Queue (NATS failover buffer) is not implemented — messages published while NATS is disconnected will be lost until reconnection

Dependencies

  • Go 1.25+
  • ScyllaDB 6.2
  • PostgreSQL 16
  • NATS 2.11+ with JetStream
  • OpenBao (Vault fork)

Breaking Changes

None — initial release.