RougeChain Documentation
Welcome to RougeChain — a post-quantum secure Layer 1 blockchain built with real NIST-approved cryptography.
What is RougeChain?
RougeChain is among the first blockchains designed from the ground up to be resistant to quantum computer attacks. It uses:
- ML-DSA-65 (CRYSTALS-Dilithium) for digital signatures
- ML-KEM-768 (CRYSTALS-Kyber) for key encapsulation
- SHA-256 for hashing
All cryptographic primitives are NIST FIPS 204/203 compliant.
Key Features
| Feature | Description |
|---|---|
| Post-Quantum Security | Protected against both classical and quantum attacks |
| Client-Side Signing | Private keys never leave your browser |
| AMM/DEX | Uniswap V2-style liquidity pools and token swaps |
| Token Burning | Official burn address with on-chain tracking |
| Proof of Stake | Energy-efficient consensus with validator staking |
| P2P Network | Decentralized peer-to-peer block and transaction propagation |
| qETH Bridge | Bridge ETH from Base Sepolia to qETH on RougeChain |
| Custom Tokens | Create your own tokens on the network |
| RC-721 NFTs | NFT collections with royalties, batch minting, and freezing |
| Encrypted Messenger | E2E encrypted messaging with PQC, media support, self-destruct |
| PQC Mail | Encrypted email with @rouge.quant addresses and threading |
| Browser Extensions | Chrome/Firefox wallet extensions with vault lock |
| PWA Support | Installable progressive web app for mobile and desktop |
| Social Layer | Posts, timeline, reposts, likes, follows, comments, tips |
| CLI Wallet | Command-line wallet with full chain access and social commands |
| SDK | @rougechain/sdk v1.0.0 npm package for building dApps |
| EIP-1559 Dynamic Fees | Base fee auto-adjusts per block, fee burning for deflationary pressure |
| Token Mint Authority | Ongoing minting for custom tokens with supply cap enforcement |
| Validator Slashing | Slash penalties for misbehavior, unbonding queue with 500-block delay |
| BFT Finality Proofs | Serializable quorum certificates with ≥2/3 validator stake |
| WebSocket Subscriptions | Topic-based real-time event streaming (blocks, txs, accounts, tokens) |
| HD Wallet Derivation | BIP-44-like PQC key derivation from master seed (HMAC-SHA256) |
| Open Source | Apache 2.0 licensed node software |
Quick Links
- Getting Started
- Running a Node
- API Reference
- P2P Networking
- Staking & Validators
- Browser Extensions
- CLI Wallet
- SDK
- Architecture
- GitHub (Node Source)
Network Info
| Network | API Endpoint |
|---|---|
| Testnet | https://testnet.rougechain.io/api |
| Devnet (local) | http://127.0.0.1:5100/api |
Tokens
XRGE
XRGE is the native token that powers transactions, secures the network through staking, and fuels the post-quantum economy.
| Role | How it works |
|---|---|
| Gas Token | Every transaction pays fees in XRGE. Fees go to the block proposer. |
| Staking Primitive | Validators must stake XRGE to propose blocks. More stake = more proposals = more rewards. |
| DeFi Base Pair | AMM liquidity pools trade against XRGE. It's the default quote currency on the built-in DEX. |
| Bridge Asset | XRGE exists on both RougeChain (native) and Base (ERC-20) via the cross-chain bridge. |
qETH
qETH is a bridged representation of ETH on RougeChain. It uses 6 decimal places and can be bridged in from Base Sepolia or withdrawn back.
| Property | Value |
|---|---|
| Decimals | 6 |
| Bridge Source | Base Sepolia |
| Bridge Contract | Configured per-node via --bridge-custody-address |
Fees
| Action | Fee |
|---|---|
| Transfer | ~0.1 XRGE (base fee, adjusts per block) |
| Token Creation | 100 XRGE |
| Pool Creation | 10 XRGE |
| Swap | 0.3% (to LPs) |
| Minimum Stake | 10,000 XRGE |
| Unbonding Period | 500 blocks |
EIP-1559 Fee Model: The base fee adjusts ±12.5% per block based on transaction volume (target: 10 txs/block). The base fee portion is burned, and only the priority tip goes to validators. Check current fees via
GET /api/fee.
Burn Address
Tokens can be permanently burned by sending to the official burn address:
XRGE_BURN_0x000000000000000000000000000000000000000000000000000000000000DEAD
Burned tokens are tracked on-chain and can be queried via the /api/burned endpoint.
Security
Client-Side Signing
RougeChain uses a secure v2 API where all transactions are signed client-side:
- Your wallet creates a transaction payload
- The payload is signed locally using ML-DSA-65
- Only the signature and public key are sent to the server
- Your private key never leaves your browser
This ensures maximum security even when interacting with untrusted nodes.