QDUM Vault CLI
Command-line tool for managing your quantum-resistant Quantdum token vault.
Features
- 🔐 SPHINCS+-SHA2-128s post-quantum signatures (NIST FIPS 205)
- 🔒 Vault Locking with cryptographic challenges
- ✅ 11-Step Verification for on-chain signature validation
- 💸 Token Transfers with Token-2022 transfer hooks
- 🏷️ On-Chain Metadata management
- 🌐 Solana Integration via RPC (devnet/mainnet)
Tokenomics
The QDUM token has a fixed supply with no minting capabilities:
- 80% - Locked liquidity
- 17% - Protocol reserves
- 3% - Community airdrop
All tokens are created at genesis. There is no minting functionality.
Prerequisites
Before installing QDUM Vault, you need Rust and Cargo installed on your system.
Install Rust
Linux/macOS/WSL:
|
After installation, restart your terminal or run:
Windows:
We recommend using WSL (Windows Subsystem for Linux) for the best experience:
-
Install WSL (if not already installed):
- Open PowerShell as Administrator and run:
wsl --install - Restart your computer
- Open PowerShell as Administrator and run:
-
Launch WSL:
- Open "Ubuntu" from Start Menu, or
- Type
wslin PowerShell, or - Type
bashin Command Prompt
-
Install Rust in WSL:
|
Alternatively, you can use native Windows with Visual Studio C++ Build Tools, but WSL provides better terminal experience for the quantum-themed UI.
Installation
Install from crates.io (Recommended)
Once Rust is installed, simply run:
That's it! The qdum-vault command is now available globally.
Alternative Installation Methods
Build from Source (GitHub)
Local Development
Quick Install Script
Usage
1. Generate SPHINCS+ Keypair
Keys are saved to ~/.qdum/:
sphincs_private.key(64 bytes)sphincs_public.key(32 bytes)
2. Register Your Vault On-Chain
3. Lock Your Vault
4. Unlock Your Vault
This performs an 11-step SPHINCS+ signature verification on-chain.
5. Check Status
6. Check Balance
7. Transfer QDUM Tokens
Transfer QDUM tokens to another wallet:
- Amount in base units with 6 decimals
- Example: 10,000 QDUM = 10000000000 base units
- Utilizes Token-2022 transfer hooks for enhanced security
Configuration
Change RPC Endpoint
Use Different Program
Architecture
- Algorithm: SPHINCS+-SHA2-128s
- Public Key: 32 bytes
- Private Key: 64 bytes
- Signature: 7,856 bytes
- Verification: 11 transactions (chunked)
Security
⚠️ IMPORTANT: Keep your SPHINCS+ private key extremely safe!
- Store offline or in a hardware security module
- Never share or commit to version control
- Anyone with your private key can unlock your vault
Development
Build
Test
Install Locally
Uninstall
Troubleshooting
Command not found
Make sure ~/.cargo/bin is in your PATH:
Need SOL for transactions
License
MIT