roadmap.html

---
layout: default
title: Roadmap
redirect_from:
- /roadmap.html
- /road-map/
---

<main class="relative z-10">
    <!-- Hero Section -->
    <section class="relative bg-[#1e1e1e] overflow-hidden">
        <div class="absolute inset-0">
            <picture>
                <source srcset="{{ site.baseurl }}/images/newimages/Roadmap.webp" type="image/webp">
                <img src="{{ site.baseurl }}/images/newimages/Roadmap.png" alt="Roadmap Header"
                    class="w-full h-full object-cover opacity-30">
            </picture>
            <div class="absolute inset-0 bg-gradient-to-b from-[#1e1e1e]/80 to-[#1e1e1e]"></div>
        </div>
        <div class="relative z-10 py-24 lg:py-32">
            <div class="container mx-auto px-4">
                <div class="max-w-4xl mx-auto text-center">
                    <h1 class="text-4xl md:text-5xl lg:text-6xl font-bold text-white mb-6">
                        Salvium <span class="gradient-text">Roadmap</span>
                    </h1>
                    <p class="text-xl text-gray-300 mb-8">
                        Our journey to revolutionize decentralized finance
                    </p>
                </div>
            </div>
        </div>
    </section>

    <!-- Roadmap Content -->
    <div class="container mx-auto px-4 py-12">
        <div class="roadmap-container">
            <div class="roadmap-section aos-init aos-animate" data-aos="fade-up">
                <h2>Phase 1: Launch Salvium</h2>
                <p><strong>Staking and Yield Generation</strong><br>
                    Since launch, users have been able to stake their SAL tokens to earn a share of the block rewards,
                    fostering a secure and engaged network.</p>
                <p><strong>Compliance</strong><br>
                    Salvium introduced refundable transactions, allowing recipients to return unauthorized or incorrect
                    funds to the sender (minus a standard transaction fee) without requiring a separate address request.
                    This feature marks a significant step toward regulatory compliance for a Monero-based chain.</p>
            </div>

            <div class="roadmap-section aos-init aos-animate" data-aos="fade-up">
                <h2>Phase 2: Enhancing Compliance Features</h2>
                <p><strong>Private Blockchain with Compliance Capabilities</strong><br>
                    Salvium will evolve to meet stringent regulatory requirements, particularly the EU's MiCA
                    regulations. Users will retain transaction privacy while authorized entities, such as exchanges, can
                    access a view key to verify transaction history—striking a balance between privacy and regulatory
                    compliance.</p>
                <p>The development team is committed to advancing Monero and Cryptonote technologies, incorporating
                    compliance-friendly innovations such as Full Chain Membership Proofs and CARROT where applicable, as
                    well as the Salvium-specific SPARC.</p>
            </div>

            <div class="roadmap-section aos-init aos-animate" data-aos="fade-up">
                <h2>Phase 3: DeFi Integration</h2>
                <p><strong>Smart Contract Functionality and Private Token Issuance</strong><br>
                    Salvium will leverage <strong>protocol_tx</strong> innovations to enable smart contract
                    functionality, allowing secure and private DeFi applications to operate within its network.</p>
                <p><strong>Middleware for Solidity Compatibility</strong><br>
                    To facilitate adoption and development, Salvium will introduce middleware that enables DApps written
                    in Solidity—Ethereum's primary programming language—to be easily adapted and deployed on its
                    network. This initiative aims to lower the entry barrier for developers, streamlining the transition
                    of existing Ethereum-based projects to Salvium.</p>
            </div>

            <div class="roadmap-section aos-init aos-animate" data-aos="fade-up">
                <h2>Phase 4: Ecosystem Growth</h2>
                <p><strong>Developer Ecosystem</strong><br>
                    Building a comprehensive suite of tools, documentation, and support resources to enable developers
                    to create privacy-preserving applications on Salvium.</p>
                <p><strong>Interoperability</strong><br>
                    Expanding Salvium's reach through strategic partnerships and cross-chain functionality while
                    maintaining the core privacy and compliance features that define the project.</p>
            </div>
        </div>
    </div>
</main>
<!-- CTA Section -->
<section class="py-16 relative overflow-hidden bg-[#0B272C] mt-4">
    <!-- Background Decoration -->
    <div class="absolute inset-0">
        <img src="{{ site.baseurl }}/images/pools-1024.webp" alt=""
            class="absolute w-full h-full object-cover opacity-20">
        <div class="absolute inset-0 bg-gradient-to-b from-[#0B272C]/95 via-[#0B272C]/80 to-[#0B272C]/95"></div>
    </div>

    <div class="container mx-auto px-4 text-center relative z-10">
        <h2 class="text-4xl md:text-5xl font-bold mb-8" data-aos="fade-up">
            Ready to Take the <span class="gradient-text">Pill</span>?
        </h2>
        <p class="text-xl text-white/80 mb-10 max-w-2xl mx-auto" data-aos="fade-up" data-aos-delay="100">
            Start your journey with Salvium today and be part of the next generation of Private DeFi.
        </p>
        <a href="{% link about.html %}"
            class="btn-primary px-12 py-4 text-lg font-semibold hover:opacity-90 transition-opacity inline-block"
            data-aos="fade-up" data-aos-delay="200">
            Get Started Now
        </a>
    </div>
</section>

<!-- Scripts -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/aos/2.3.4/aos.js"></script>

<script>
    // Initialize AOS
    AOS.init({
        duration: 800,
        once: true
    });
</script>