WakaStart
Security & compliance

Stellar Module (blockchain proofs)

View integrity proofs anchored on the Stellar blockchain.

Version v1.02 min read

Stellar Module (blockchain proofs)

WakaStart regularly anchors a digital fingerprint of your audit logs on the Stellar blockchain. This fingerprint is a single hash per batch (concatenation then SHA-256 of the batch's logs), not a Merkle tree: it proves the overall integrity of the anchored batch, but does not provide a compact inclusion proof for an isolated entry — verifying a specific entry requires having the complete list of hashes for the batch, not just the transaction identifier.

[!WARNING] The evidentiary value of this anchoring depends on the configured Stellar network. By default, the platform anchors on the testnet network, which has no evidentiary value (a test network that can be reset). Only anchoring on the public network (mainnet) constitutes admissible proof. Check your environment's configuration with your CISO before relying on this module for a compliance obligation.

When do you use this section?

  • You need to prove to an external auditor that your logs have not been tampered with
  • You want to verify that synchronizations with the blockchain are proceeding normally
  • You want to view the history of recorded proofs

Accessing blockchain proofs

From the main menu on the left, click Security then Stellar.

The indicators at the top of the page give you a quick overview:

  • Number of recorded proofs: the total number of fingerprints anchored on the blockchain
  • Success rate: the percentage of successful anchoring operations
  • Last synchronization: the date and time of the last anchoring performed

Viewing proof details

The table lists all recorded proofs. You can filter by network, by status (success, error, pending), and by period.

Each row shows the anchoring date, the relevant network, and a blockchain transaction identifier. This identifier lets an auditor find the transaction on the relevant Stellar network (testnet or mainnet depending on configuration) and compare the anchored hash to the one recalculated from the corresponding batch of audit logs — it alone is not sufficient to prove the integrity of an individual entry without this complete batch.

Going further