Salvium Supply Audit

< BACK TO ALL TOPICS

Comprehensive Audit Guide

Important message to all holders: You must audit your SAL coins in your wallet before the 4th March 2025. Any coins that aren’t audited will be lost. Please note: Please ensure that you resync from genesis (i.e. block 0) when using version 0.9.1. Or connect to a remote node to sync.

1. Overview and Rationale

The Salvium protocol is a fork of Monero with additional features and improvements. Recent vulnerabilities—most notably a flaw stemming from an incomplete zero-knowledge proof in our “commitment to a difference” system—highlighted the need for a full supply audit. This vulnerability, which allowed the possibility of undetected coin minting (and potential hidden inflation), prompted us to take immediate action to patch the system and implement a rigorous audit process.

Why the Audit?

  • Security Assurance: The primary goal is to ensure the integrity of the protocol. By auditing the entire coin supply, we can verify that no malicious activities (such as hidden inflation) have compromised the network.
  • Community Confidence: A transparent and thorough audit builds trust among users and stakeholders. By verifying every transaction, we reinforce that all funds are secure.
  • Protocol Resilience: The audit is part of a broader strategy to upgrade the protocol in phases, thereby maintaining security while allowing for continuous improvements.

2. Audit Process Details

2.1. Audit Trigger and Forks

The audit process started on the 4th February 2025 – with the hard fork at block 154,750. Please ensure you are running v0.9.1. Available from: https://github.com/salvium/salvium/releases/tag/v0.9.1

2.2. Guide to the Audit Process

  1. Fork and Audit Initiation:
    • At the fork height (block 154,750 in v0.9.1), the audit process was activated.
    • Holders must execute the CLI command audit index=all in their wallets.
    • The audit command sends all eligible coins into the verification process.
    • Once varified, coins will be converted in SAL1, fully usable (transfers, stakes, etc) after the 10 day period.
    • All coins mined after fork height will automatically be SAL1 (no audit needed).
  2. Audit Transaction Lifecycle:
    • Maturation Period: These audit transactions will be locked for 7,200 blocks (approx 10 days). During this time, they are processed and validated by the network and team.
    • Conversion: Successful audit transactions will convert your audited SAL to SAL1. This is an asset type within the protocol – but it will still be known as Salvium, and going forward this will still be referred to as SAL.
    • Unverified or unaudited funds will be rendered permanently unusable.

3. Technical and Operational Considerations

3.1. Node Synchronization and Blockchain Data Integrity

Full Chain Sync Requirement: When running version 0.9.1, all node operators must resynchronize their local blockchain from genesis. You can do this in one of two ways:
  1. Download a Snapshot: Download the latest data.mdb snapshot from our Downloads page and place it in your /lmdb folder. This is the fastest method.
  2. Re-sync by Deletion: Delete the local data.mdb file and restart your node. The blockchain will be re-downloaded and re-synced, typically taking between 1 and 4 hours.
  3. Connect to a remote node. See CLI guide for futher details

Typical Locations for data.mdb:

  • Windows: C:\ProgramData\salvium\lmdb
  • Linux: ~/.salvium/lmdb
  • Mac: /Library/Application Support/salvium/lmdb
Important: Never delete your .keys file.

Need Help?

  • For further assistance or detailed technical queries, please refer to our Discord support channel
  • The full technical documentation on GitHub
  • Join our Discord audit-discussion channel