Salvium One Hard Fork – Complete Guide
Overview
Salvium One is the most significant upgrade in our project’s history, delivering the foundation for a compliant privacy ecosystem. It introduces the Carrot address system, SPARC, and major improvements to privacy and compliance — laying the groundwork for private DeFi, staking, and exchange support.
The hard fork is scheduled for:
- Block Height: 334750
- Date/Time: October 13th, 2025 (Approx. 2pm GMT)
- Required Version: v1.0.0 or higher
➡️ Download the latest binaries ℹ️ Read the Salvium One Blog Post
What is Salvium One?
Salvium One is the culmination of 15 months of development, designed to deliver:
- Privacy-first transactions compatible with regulatory compliance
- Carrot address format – a new address system required for future features
- SPARC integration – private, anonymised return payments
- Full DeFi readiness – foundations for private tokens, DEXs, and lending protocols
Key Features
Carrot Address System
- New address prefix:
SC1...
- Enables refundable transactions without revealing sender addresses
- Critical for exchange compliance and interoperability
- Legacy CryptoNote addresses (
SaLv...
) become invalid at fork
SPARC Integration
- Private refund mechanism for exchanges
- Allows returns of unauthorized deposits without exposing transaction history
T-CLSAG
- Updated version of Monero’s CLSAG ring signatures
- Maintains anonymity while enabling Carrot address support
View-Only Wallets
- Full visibility of incoming and outgoing transactions
- Meets compliance and audit requirements
⚠️ Critical Change: Wallet Address Migration
What Happens at the Fork
- Your wallet will automatically generate a Carrot address (
SC1...
) - Your old CryptoNote address (
SaLv...
) becomes a legacy address - After the fork, only Carrot addresses will be accepted for mining and payouts
Balances remain untouched. You do not need to move your coins — only update your software and addresses.
How to Find Your Carrot Address
1. CLI Wallet v1.0.0 and above Open your wallet and you’ll see both the legacy and Carrot addresses displayed, for example:
2. CLI Command Run:
This will display your primary address in both formats.
3. RPC (from v1.0.1 onward)
Use the get_address
RPC call:
🛠️ Guidance for Miners
- Update your miner config (xmrig, etc.) with your Carrot address before the fork
- If you continue mining with a legacy address after block 334750, shares will be rejected
- If supported by your pool, you may enter both old and new addresses during the pre-fork period to ensure a smooth switch
🛠️ Guidance for Pools
- Update your pool payout wallet to a Carrot address before the fork
- Accept Carrot addresses only after block 334750. Legacy addresses must be rejected
-
Manage unpaid balances:
-
Flush outstanding balances to legacy addresses before the fork, or
- Collect Carrot addresses from miners in advance and map
{old → new}
in your DB
Regex patterns for validation:
- Legacy:
- Carrot:
❓ Frequently Asked Questions
Will my balance change after the fork? No. Your coins and balances remain the same. Only the wallet address format changes.
Do I need to move coins before the fork? No. You don’t need to move anything. Just update your wallet software.
How can I find my new address?
Open v1.0.0+ of the CLI wallet, or run address 0
. RPC users can call get_address
from v1.0.1.
What happens if I mine to my old address after the fork? Your shares will be rejected. Pools will not accept legacy addresses post-fork.
I’m a pool operator. How do I handle unpaid balances? Either flush them to old addresses before the fork or collect new Carrot addresses in advance.
Does this affect staking or SPARC? Yes. Both require Carrot addresses. Make sure your infrastructure is updated.
📚 Resources
- GitHub v1.0.0 Binaries
- Introducing Salvium One Blog Post
- Explorer
- Salvium One White Paper (PDF)
- Join the Community on Discord
✅ Salvium One is not just a hard fork — it’s the beginning of a new era for private, compliant DeFi. Update your binaries, switch to your Carrot address, and be ready for October 13th, 2025.