KULA ERC Suite
Live · Ethereum Sepolia Testnet

How the Compliance
Event Log Works

Every compliance action — KYC decisions, freezes, transfers, policy changes — is written append-only to the blockchain as an immutable event. Nothing can be deleted. Corrections are transparent and traceable.

Diagram — how a compliance event is recorded

An actor submits an event type, outcome, and evidence hash. These are packed into an on-chain record assigned a sequential index. The log is append-only — no record can ever be modified or removed.

COMPLIANCE ACTOR — client-side inputsETHEREUM SEPOLIAEVENT TYPEKYC_APPROVEDstandardised event kindOUTCOMEAPPROVEDresult of the actionEVIDENCE HASH0xf3a1…9b2cSHA-256 of off-chain docspack +signEvent Recordidx #0047append-only · immutablerecordEvent()on-chain tx · append onlyOn-Chain Eventappend-only · cannot be alteredEvent Index#0047Event TypeKYC_APPROVEDOutcomeAPPROVEDEvidence Hash0xf3a1…9b2cRecorded atBlock #5,109,224Actor0x4a7b…1E3f

Diagram — correction chain

Errors are corrected by appending a new CORRECTION event that references the original via correctsIndex. The original is marked with correctedByIndex. Both events remain readable on-chain — the correction history is fully traversable.

Original Event · #0031KYC_APPROVEDevidenceHash: 0xaa1b…cc2dcorrectedByIndex: 32Supersededstill readable · never deletedcorrected byCorrection Event · #0032CORRECTIONoutcome: KYC_APPROVED → DENIEDevidenceHash: 0xdd3e…ee4fcorrectsIndex: 31⏎ Corrects #31correction is itself immutableboth eventsremain on-chainFull Audit Trail#0031 — original (superseded)#0032 — correction (active)linked via correctsIndex /correctedByIndex pointers✓ Traversable

Live smart contract · Ethereum Sepolia

Compliance Event Log

Stores compliance events indexed sequentially per subject. Events are immutable once written. Corrections are first-class events with bidirectional index pointers, giving any auditor a complete, tamper-proof history.

Contract Address · Sepolia

0xC4e9F1a2B5d8E3c7A0f6D2b4E8c1F5a3B7d9E0c2
Append-Only

Events are indexed sequentially and cannot be edited or deleted after recording.

Auditable

Corrections are chained via index pointers, giving regulators a complete and traversable event history.

Verifiable

Any party can re-hash off-chain documents and confirm they match the evidence hash stored on-chain.