Skip to main content

Vexidus Blockchain Technical Whitepaper

Next-Generation Layer 1 Infrastructure Version: 2.1 Date: February 2026 Status: Beta Testnet Live | Mainnet Target 2026

Executive Summary​

Vexidus is a Layer 1 blockchain built from the ground up to solve real problems: quantum vulnerability, cross-chain fragmentation, developer complexity, and bridge security. It runs a live 3-validator testnet that has processed over 936,000 transactions with zero crashes and zero manual restarts.

Vexidus is built on seven pillars that work together as a unified system:

  1. IntentVM (Patent-Pending) -- 1 intent, 1 signature, N operations. Declarative execution.
  2. HyperSync Consensus -- Leader rotation with weighted selection, jailing, and reputation scoring.
  3. VexBridge (Patent-Pending) -- Vaultless canonical token bridge using burn-and-mint and stateless/limbo resolution.
  4. VSA v2 -- Smart accounts with Ed25519 + Dilithium3 dual-signature quantum hardening. Includes VNS (.vex name service) as an identity extension.
  5. VexForge -- Five token standards (VSC-7, VSC-21, VSC-55, VSC-LAUNCH, VSC-REP) with protocol-level anti-rug protection.
  6. VexiDEX -- Native on-chain AMM with constant-product pools and LP token management.
  7. ElasticState -- Intelligent 3-tier storage engine (Hot/Warm/Cold) with automatic data lifecycle management. State grows without degrading performance.

Current Status: Solo founder-built from concept to live testnet in 16 months. 15 Rust crates, 70+ RPC endpoints, 176 passing tests, 5 deployed frontends.

Table of Contents​

  1. The Problem
  2. The Seven Pillars
  3. Architecture Overview
  4. Performance and Benchmarks
  5. Security Model
  6. Token Economics
  7. Ecosystem and Applications
  8. Roadmap
  9. Competitive Analysis
  10. Team and Development

1. The Problem​

Scalability vs. Decentralization​

Ethereum processes ~15 TPS with 12-minute finality. Bitcoin manages ~7 TPS. "Fast" L1s like Solana achieve 65K TPS but face periodic outages and centralization concerns. No chain has proven it can sustain high throughput while remaining reliable and decentralized.

Quantum Vulnerability​

NIST estimates quantum computers could break current blockchain cryptography by 2030-2035. Over $3 trillion in cryptocurrency assets rely on ECDSA or Ed25519 alone. No major L1 has implemented post-quantum cryptography at the protocol level alongside classical signatures.

Bridge Security Crisis​

$1.1B+ lost in bridge hacks in 2022 alone (Wormhole $320M, Ronin $625M, Nomad $190M). Every major hack targeted the vault -- the smart contract holding locked tokens. The vault-based bridge model is fundamentally broken.

Developer and User Complexity​

Users must understand gas optimization, transaction construction, and chain-specific tooling. "Swap 100 USDC for ETH" requires multiple transactions, multiple signatures, and MEV awareness on most chains.

2. The Seven Pillars​

Pillar 1: IntentVM (Patent-Pending)​

The Problem: Traditional blockchains require users to specify exact execution steps. A simple "swap then stake" requires 2 transactions, 2 signatures, and 2 consensus rounds.

The Solution: IntentVM accepts a single intent -- expressed as structured JSON or natural language -- and decomposes it into the optimal sequence of native operations, executed atomically in one block slot.

User: "swap 100 VXS for USDC and stake the rest"

IntentVM decomposes:
  1. Swap (VXS -> USDC via VexiDEX)
  2. Stake (remaining VXS to validator)

Result: 1 intent, 1 signature, 2 operations, 1 block slot

Key Advantage -- 1 Intent, 1 Signature, N Operations:

On Solana or Ethereum, "swap then stake" = 2 transactions, 2 signatures, 2 consensus rounds. On Vexidus, it is 1 bundle, 1 signature, 1 round. This gives Vexidus 3-5x effective throughput per user action compared to per-transaction chains.

Provenance: IntentVM was first built and tested as a Solana on-chain program (Program ID: AcfdgJoduQxLLPwFDVTi3FWrqEERPhmQ9UAwNkrkYfnJ). Real transaction proofs exist from Solana localnet (slot 331,223, 12,099 compute units). It was then rebuilt as a core protocol feature on Vexidus -- not a theoretical design, but a port of working code.

Supported Goals:

  • Swap -- Token exchange via VexiDEX pools
  • Stake -- Delegate VXS to validators
  • Provide Liquidity -- Add to AMM pools
  • Bridge -- Cross-chain with tier-aware proof verification
  • Composite -- Atomic multi-step (bridge + swap + stake in one intent)
  • Custom -- VNS registration, future LLM-parsed intents

RPC Endpoints:

  • vex_submitIntent -- Submit natural language or structured JSON
  • vex_getExecutionPlan -- Preview execution steps and gas estimate before submission
  • vex_getIntentStatus -- Query result by hash

Pillar 2: HyperSync Consensus​

Architecture: Weighted leader rotation with Byzantine fault tolerance. Validators take turns proposing blocks based on stake weight and performance score.

How It Works:

  1. Leader selection uses blake3(block_height + validator_set_hash) seeded randomness
  2. Weight = stake * performance_score (0.5-1.0 range)
  3. Leader proposes block containing up to 10,000 transactions
  4. Block is gossiped to all peers via GossipSub (QUIC transport, TLS 1.3)
  5. Validators verify proposer signature (Ed25519) and execute transactions
  6. Block finalized after gossip consensus

Block Production:

  • 12-second block intervals (configurable)
  • Pressure-aware micro-blocks: 2s normal, 1s high load, 500ms extreme
  • Up to 10,000 transactions per block

Validator Economics:

  • Minimum stake: 1,000 VXS
  • Block rewards: ~4.94 VXS/block (Year 1-2 rate, auto-adjusting 10-year schedule)
  • Transaction fees: 100% to block proposer (no burn -- fixed supply)
  • Commission: 0-50%, configurable per validator

No Slashing -- Jailing Instead: Vexidus does not slash validator stake. Misbehaving validators are jailed (removed from rotation for 5 minutes after 50 consecutive missed blocks). This protects delegators from losing funds while still incentivizing uptime. Reputation scoring (7-factor, 100-point scale) affects leader selection weight and future reward multipliers.

Reputation Factors:

FactorWeightMeasures
Uptime25 ptsBlock production consistency
Commission fairness15 ptsReasonable rates, stability
Self-stake15 ptsSkin in the game
Governance participation15 ptsUpgrade voting activity
Tenure10 ptsTime active on network
Delegator trust10 ptsStake attracted from others
Reliability10 ptsHistorical jail count, missed blocks

Pillar 3: VexBridge -- Vaultless Canonical Token Bridge​

The Core Innovation: Tokens are never locked in vaults. They are either burned on the source chain or rendered stateless (provably unspendable). Vexidus then mints a canonical equivalent -- a first-class native token, not a wrapped representation.

Traditional bridges:  User -> Vault (holds tokens) -> Mint wrapped token
                      Risk: Vault hack = total loss

VexBridge:            User -> Burn/Limbo (tokens destroyed) -> Mint canonical token
                      Risk: Nothing to hack (no vault exists)

Two Token Categories:

Burnable tokens (USDC, USDT, DAI, WBTC, etc.) -- tokens with burn functions on their source chain. Flow: burn on source -> ZK proof verifies burn -> Vexidus mints canonical equivalent. Bridge back is possible via burn on Vexidus -> mint on source.

Non-burnable tokens (native SOL, ETH, BTC) -- the "Stateless/Limbo" innovation. User sends tokens to their VSA address on the source chain. Since VSAs exist on Vexidus, NOT on Solana/Ethereum, the destination does not exist on the source chain. The tokens become stateless -- sent but never landed anywhere. They are in limbo: provably not in anyone's possession. ZK proof verifies the transaction happened AND that the destination is a non-existent VSA address.

Bridgeability Classification:

  • Full Round-Trip -- Can bridge in and out (burnable tokens, controlled tokens)
  • Limbo-Locked -- Can bridge in; out requires liquidity matching (native SOL, ETH, BTC)
  • One-Way In -- Can come in, no established path back (unknown tokens)

VexBridge tells users their bridgeability BEFORE they act on the source chain -- honest by design.

Three-Tier Verification:

  • Tier 1 (Coordination): Multi-chain native tokens you control. Ed25519 signature. Zero trust.
  • Tier 2 (Light Client): Major chains with finality proofs. Merkle proof verification. Trust finality only.
  • Tier 3 (Oracle Consensus): Other chains. 7-of-10 oracle threshold with real Ed25519 signature verification.

Per-Chain Fee Model:

ChainFeeMinimum
Ethereum0.3%1 unit
Solana0.1%0.1 unit
Bitcoin0.5%5 units
Default0.25%0.5 unit

Pillar 4: VSA v2 -- Quantum-Hardened Smart Accounts​

Dual-Signature Architecture: Every Vexidus account uses Ed25519 (classical, Solana-compatible) alongside Dilithium3 (NIST-approved post-quantum lattice-based signatures). This provides quantum resistance TODAY while maintaining compatibility with existing Ed25519 wallets.

Address Derivation (Same Key, Three Views):

Ed25519 Keypair -> pubkey (32 bytes)
  +---> Vx0:    SHA256(pubkey)[0..20] -> base58 -> "Vx0abc..."   (native)
  +---> 0x:     last 20 bytes -> "0x71C7..."                     (EVM/MetaMask)
  +---> base58: raw pubkey -> "7xKXtg..."                        (Solana/Phantom)
       All resolve to the same internal Address([u8; 32]).

Key Management:

  • AddKey, RemoveKey, RotateKey -- hot-swap signing keys without changing your address
  • Guardian recovery -- 3-of-5 trusted guardians can recover access (7-day delay, cancelable)
  • No seed phrase required for recovery (protocol-level, not a service)

Key management operations (disc 6-12) are defined in the protocol and live on testnet. Guardian recovery with timelock is functional end-to-end.

Pubkey Revelation: Accounts created by receiving transfers get a dummy public key. On first send, the wallet includes the real Ed25519 pubkey (sender_pubkey field). The protocol verifies SHA256(pubkey)[0..20] matches the address, registers the key, and proceeds -- seamless to the user.

Why Not ML-KEM? Dilithium3 is a signature scheme; ML-KEM is a key encapsulation scheme. Blockchains need signatures. Vexidus uses Ed25519 for speed and compatibility, Dilithium3 for quantum hardening, and a proposer_signature_pq field on blocks for future dual-sig enforcement.

VNS -- Vexidus Name Service (Identity Extension):

VNS provides human-readable .vex names as an extension of the VSA identity system. Each .vex name IS a VSC-21 NFT -- ownership of the NFT IS name resolution. Transfer the NFT, transfer the name. No separate registry update needed.

  • Register chris.vex -> mints NFT in global VNS collection -> stored as vns:chris in RocksDB
  • Resolve chris.vex -> find the NFT -> the owner's address IS the resolved address
  • Pricing: 3-4 chars = 1,000 VXS, 5-7 chars = 100 VXS, 8+ chars = 10 VXS
  • RPC: vex_registerName, vex_resolveName, vex_reverseResolve, vex_getNameInfo

VNS is a natural complement to VSA -- it adds a human-readable layer to the account system that VSA already manages. What makes Vexidus different is that VNS names compose atomically with IntentVM -- "send 10 VXS to chris.vex and stake the rest" is one intent, one signature.

Pillar 5: VexForge -- Five Token Standards​

VexForge provides protocol-level token creation without smart contracts. All standards are live on testnet.

StandardPurposeOperations
VSC-7Fungible tokensCreate, mint, transfer, burn (disc 1-4)
VSC-21NFTsCreate collection, mint, transfer, burn (disc 19-22)
VSC-55Multi-token (ERC-1155 equivalent)Create, mint, batch mint/transfer, burn (disc 23-29)
VSC-LAUNCHPresale with anti-rugCreate, contribute, finalize, refund (disc 31-36)
VSC-REPToken reputation scoringDeterministic 7-factor scoring, grade A+ to F

Anti-Rug Protection (VSC-LAUNCH): Presale funds are held in protocol-level escrow. If the presale fails to meet its goal, contributors can claim refunds directly -- no trust in the creator required. On finalize, liquidity is automatically locked in VexiDEX.

Token Metadata: On-chain mutable metadata (name, symbol, image, social links) with a one-way LockTokenMetadata operation (disc 42). Once locked, metadata is permanently immutable -- useful for establishing trust in community tokens.

Pillar 6: VexiDEX -- Native On-Chain AMM​

VexiDEX is a constant-product automated market maker built into the protocol (disc 38-41).

  • Pools: Any VSC-7 token pair. 0.3% swap fee.
  • LP Tokens: Minted on deposit, burned on withdrawal. Track proportional pool share.
  • Create Pool -> Add Liquidity -> Swap -> Remove Liquidity -- all native operations.
  • RPC: vex_createPool, vex_addLiquidity, vex_removeLiquidity, vex_swap, vex_quoteSwap, vex_getPool, vex_listPools

VexiDEX integrates with IntentVM -- a user can say "swap 100 VXS for USDC" and IntentVM routes through the optimal pool automatically.

Pillar 7: ElasticState -- Intelligent 3-Tier Storage Engine​

The Problem: Every blockchain today treats all state equally. A validator that transacted 5 seconds ago and a wallet that has not moved in 3 years sit in the same data structure, consuming the same resources. As chains grow, state bloat becomes the dominant bottleneck.

The Solution: ElasticState automatically routes account data through three storage tiers based on activity, giving sub-microsecond access to hot data while compressing dormant accounts by up to 90%.

+------------------------------------------------------+
|  HOT TIER -- DashMap (in-memory)                      |
|  Active accounts (last 7 days)                       |
|  Access: <1us | Capacity: 100K entries / 8 GB        |
+------------------------------------------------------+
|  WARM TIER -- RocksDB (LZ4 compression)               |
|  Recent accounts (7-90 days inactive)                |
|  Access: ~100us | Fast SSD reads                     |
+------------------------------------------------------+
|  COLD TIER -- RocksDB (ZSTD max compression)          |
|  Dormant accounts (90+ days inactive)                |
|  Access: ~1-10ms | 90% storage reduction             |
|  Includes Merkle proofs for light client verification|
+------------------------------------------------------+

Key Design Decisions:

  • Feature-flagged (--elastic-state CLI flag). Backward-compatible.
  • State root integrity preserved. The main RocksDB default CF is the ONLY input to compute_state_root(). ElasticState is a read cache that cannot affect consensus.
  • No state rent. Vexidus will never charge users to keep their accounts alive.
  • Merkle proofs for cold accounts. Enables future light client verification.

3. Architecture Overview​

System Layers​

+-----------------------------------------------------+
|            APPLICATION LAYER                         |
|  VexSpark | VexScan | VexForge | VexiDex | VexSwap  |
+-----------------------------------------------------+
|            API LAYER (JSON-RPC)                      |
|  70+ endpoints: vex_* (native) + eth_* (EVM compat) |
+-----------------------------------------------------+
|            EXECUTION LAYER                           |
|  IntentVM | VexForge | VexBridge | VexiDEX | VNS    |
+-----------------------------------------------------+
|            CONSENSUS LAYER (HyperSync)               |
|  Leader Rotation | Vote Signing | Epoch Management   |
+-----------------------------------------------------+
|            STATE LAYER (ElasticState)                 |
|  Hot (DashMap) -> Warm (LZ4) -> Cold (ZSTD) -> RocksDB |
|  StateMachine | WriteBatch Atomics | Checkpoints     |
+-----------------------------------------------------+
|            NETWORK LAYER (libp2p)                    |
|  QUIC Transport | GossipSub | Bulk Sync              |
+-----------------------------------------------------+

Implementation​

  • Language: Rust -- 15 crates, memory-safe, zero-cost abstractions
  • Database: RocksDB with atomic WriteBatch commits (crash-safe, no partial state)
  • Storage: ElasticState 3-tier engine -- Hot (DashMap, <1us), Warm (RocksDB LZ4), Cold (RocksDB ZSTD). Zero-copy checkpoints every 1K blocks.
  • Networking: libp2p with QUIC transport (TLS 1.3, multiplexing over UDP)
  • State Root: Blake3 Merkle computation (once per block, not per transaction)
  • Transaction Model: Account-based with bundle semantics (atomic multi-operation)

Transaction Lifecycle​

1. User submits bundle (signed Ed25519)
      |
2. RPC validates signature + format
      |
3. Bundle enters mempool (100K capacity, TTL: 120s)
      |
4. Leader drains mempool -> proposes block
      |
5. begin_block() -> execute bundles -> commit_block() (WriteBatch)
      |
6. recompute_state_root() -> flush()
      |
7. Block gossiped to peers -> verified -> finalized
      |
8. Explorer indexes updated (RocksDB "explorer" CF)

Wallet Compatibility​

WalletStatusRPC LayerSignature
VexSpark (native)Livevex_*Ed25519
MetaMaskLiveeth_*secp256k1/ECDSA
PhantomPlannedsvm_*Ed25519 (same curve)

One Ed25519 keypair works on both Vexidus and Solana. The same key generates three address formats (Vx0, 0x, base58) that all resolve to the same internal account.

4. Performance and Benchmarks​

Proven Results (February 2026, 3-Validator Network)​

TestDurationTransactionsSuccess RateAvg Latency
100 TPS10 minutes60,000100%0.7ms
500 TPS10 minutes300,000100%0.8ms
1,000 TPS10 minutes576,000 / 600,00096%--

Total: 936,000 transactions processed. Zero node crashes. Zero manual restarts.

The 1K TPS test achieved 96% success -- the 4% that failed were MempoolFull errors (capacity hit, not crashes). No state corruption, no chain stalls.

Transaction Cost​

OperationGasCost (at $1/VXS)
VXS Transfer~21,000~$0.00021
Token Create~50,000~$0.0005
Swap~80,000~$0.0008
Bridge Deposit~100,000~$0.001
Name Registration~60,000~$0.0006 + name fee

Gas price: 10 nanoVXS per gas unit. 100% of fees go to the block proposer.

What We Claim vs. What Is Proven​

MetricProvenTarget (Pre-Mainnet)
Sustained TPS1,000 (3 validators)5,000-10,000 (testing planned)
Block time12 secondsConfigurable (target: sub-second)
Finality~12 secondsImproved with validator count
Uptime24h+ soak test passedContinuous
Crash recoveryZero crashes in 936K txsOngoing validation

We will publish updated benchmarks after 5K and 10K TPS load tests. We do not claim numbers we have not proven.

5. Security Model​

Consensus Security​

  • Byzantine Fault Tolerance: Tolerates up to 1/3 malicious validators
  • Block Proposer Signatures: Every block is Ed25519-signed by its proposer. Invalid signatures result in instant peer banning.
  • PeerGuard: Per-peer scoring system. Replay detection (200-hash ring buffer), rate limiting, validator allowlisting. Score drops to 0 = permanent ban.
  • Validator Set from State: No self-adding. Validators loaded from on-chain staking state only.

Quantum Resistance​

AlgorithmPurposeSecurity Level
Ed25519Transaction signing, block proposingClassical (Solana-compatible)
Dilithium3Post-quantum signatures (dormant, ready for activation)NIST Level 3 (quantum-safe)
Blake3Hashing (state root, tx hash, address derivation)256-bit (quantum-resistant)

Vexidus is quantum-hardened today: the Dilithium3 infrastructure exists at the protocol level. When quantum computers threaten Ed25519, Vexidus can activate dual-signature enforcement without a hard fork -- the proposer_signature_pq field is already on every block.

Bridge Security​

The fundamental security advantage of VexBridge: there is no vault to hack.

Bridge HackAmountAttack VectorVexBridge Equivalent
Wormhole ($320M)Minted without depositImpossible -- no vault to bypass
Ronin ($625M)Compromised vault keysImpossible -- no keys to compromise
Nomad ($190M)Faulty Merkle rootMitigated -- tier-aware verification

The only attack vector is compromising the proof verification itself (ZK/light client/oracle), which is fundamentally harder than stealing from a vault.

No Slashing​

Vexidus deliberately avoids slashing. Validators who miss 50 consecutive blocks are jailed (temporarily removed from rotation for 5 minutes), not economically punished. This protects delegators and removes the "slashing insurance" overhead that exists on other chains. Bad actors lose opportunity cost (missed rewards) and reputation, not principal. An upgrade grace period (100 blocks) prevents jailing during network upgrades.

6. Token Economics​

Token Overview​

PropertyValue
SymbolVXS
Total Supply1,618,000,000 (Golden Ratio: 1.618B)
Decimals9
InflationNone -- fixed supply, unburnable
Fee Model100% to block proposer (no burn, no treasury cut)

Why 1.618 Billion?​

The golden ratio (1.618...) appears throughout nature and mathematics. It is memorable, distinctive, and provides ample supply for a global network while maintaining meaningful per-token value.

Genesis Allocations​

96% of total supply (1,553.28M VXS) is allocated at genesis across 8 accounts:

AccountVXS%Status
Public Distribution (0x...01)614,840,00038%Circulating (Pre-sale 20% + TGE 18%)
Ecosystem & DeFi (0x...02)242,700,00015%Circulating (grants, LP incentives)
Foundation Treasury (0x...03)161,800,00010%Circulating (operations)
Team & Founders (0x...04)161,800,00010%Locked (4-year vest, 1-year cliff)
Marketing & Community (0x...05)113,260,0007%Circulating (airdrops, campaigns)
SAFT Round (0x...06)48,540,0003%Locked (12-month vest, 6-month cliff)
Testnet Rewards (0x...07)48,540,0003%Circulating (beta testers)
Staking & Strategic (0x...08)161,800,00010%Governance-controlled
Genesis Total1,553,280,00096%73% circulating at TGE

Block Reward Schedule​

~64.72M VXS emitted over 10 years (~4% of total supply). Annual inflation: 0.8%.

PeriodAnnual EmissionPer-Block (at 12s)
Year 1-213M VXS/yr~4.94 VXS
Year 3-56.5M VXS/yr~2.47 VXS
Year 6-103.9M VXS/yr~1.48 VXS
Year 11+00

Block rewards are distributed to the block proposer. Per-block reward auto-adjusts proportionally if block time changes.

Transaction Fees​

Solana-competitive pricing:

ParameterValue
Gas price10 nanoVXS per gas unit
Typical transfer cost0.00021 VXS ($0.0002 at $1/VXS)
Fee destination100% to block proposer
Burn mechanismNone -- fixed supply forever

Staking​

ParameterValue
Minimum stake1,000 VXS
Unbonding period21 days
Commission range0-50%
Max validators100 (configurable)
Epoch duration300 seconds

7. Ecosystem and Applications​

Live Frontends​

ApplicationURLPurpose
VexSparkwallet.vexspark.comNative Ed25519 wallet (send, receive, tokens, IntentVM)
VexScanvexscan.ioBlock explorer (blocks, transactions, validators, tokens)
VexForgevexforge.xyzToken creation studio (templates, terminal, JSON editor)
VexiDexvexidex.comDEX interface (swap, pools, liquidity)
VexSwapvexswap.xyzTestnet faucet + IntentVM natural language demo

Developer Tools​

  • Rust SDK (vexidus-sdk) -- WalletKeypair, BundleBuilder (all 50 discriminants, disc 0-49), IntentBuilder, ValidatorClient, DEX client
  • CLI (vexidus) -- 13 command groups, 65+ subcommands
  • 70+ RPC Endpoints -- Full vex_* native API + eth_* EVM compatibility
  • VexVisor -- Upgrade governance module: schedule upgrades via RPC, stake-weighted voting, automatic halt at upgrade height, binary download with SHA256 verification, auto-rollback on crash within 60 seconds. Two modes: seed-authority (auto-approve) and full (67% quorum). All validators run via VexVisor wrapper in production.

How the Pillars Work Together​

The seven pillars are not isolated features -- they compose:

Example: "Bridge 10 SOL from Solana and swap to VXS"

  1. IntentVM parses the natural language -> Goal::Composite([Bridge, Swap])
  2. VexBridge verifies the SOL limbo proof (Tier 2 light client)
  3. VexForge credits canonical SOL token to the user's account
  4. VexiDEX routes the SOL to VXS swap through the best pool
  5. VSA v2 verifies the single Ed25519 signature over the entire bundle (VNS resolves chris.vex to the user's address)
  6. HyperSync includes the bundle in the next block (weighted leader selection)
  7. ElasticState serves the user's account from the hot cache (<1us) -- no RocksDB lookup needed. The bridge proof is written through to warm tier for later archival.

All of this happens atomically -- one intent, one signature, one block slot. If any step fails, the entire operation rolls back.

8. Roadmap​

Completed​

PhaseStatusKey Deliverables
Core ArchitectureDone15 Rust crates, StateMachine, RocksDB, account model
ConsensusDoneHyperSync leader rotation, vote signing, epoch management
Token StandardsDoneVSC-7, VSC-21, VSC-55, VSC-LAUNCH, VSC-REP
StakingDone9 operations, weighted selection, jailing, commission, reputation
IntentVMDoneGoal decomposition, atomic execution, NL parser, 3 RPC endpoints
VexBridgeDoneThree-tier architecture, burn/limbo model, oracle Ed25519, 8 RPC endpoints
ElasticStateDone3-tier storage (Hot/Warm/Cold), auto-promotion/demotion, checkpoints, feature-flagged
VNSDoneNFT-backed .vex names (VSA identity extension), 4 RPC endpoints
VexiDEXDoneConstant-product AMM, 7 RPC endpoints
P2P SecurityDoneBlock proposer signatures, PeerGuard, sync validation
Gas and FeesDoneSolana-competitive pricing, 100% to proposer
ExplorerDoneRocksDB indexing, 11 query endpoints
EVM CompatDoneeth_* RPC translation (MetaMask works)
FrontendsDoneVexSpark, VexScan, VexForge, VexiDex, VexSwap
Load TestingDone936K txs, 0 crashes, 1K TPS sustained
3-Validator NetworkDoneLeader rotation, 24h+ soak test
VexVisorDoneUpgrade governance, auto-halt, binary download, SHA256 verify, auto-rollback

Current Phase: Beta Testnet​

  • 5K and 10K TPS load testing
  • Clean genesis restart
  • Public documentation site
  • Validator rewards program (testnet reputation -> mainnet VXS airdrops)
  • Public GitHub

Next Phases​

PhaseFocus
Beta HardeningReputation consequences, SVM adapter (Phantom), monitoring, governance
Bridge IntegrationSolana devnet SPL bridge, BSC testnet BEP-20 bridge
Security AuditsExternal audit of core protocol, bridge, cryptography
Mainnet PrepDynamic gas, delegation pools, 200K TPS optimization, security hardening
Mainnet LaunchGenesis block, validator onboarding, exchange listings

9. Competitive Analysis​

What Is Unique About Vexidus​

No other L1 combines all seven:

FeatureVexidusEthereumSolanaAptosSui
Intent-based executionIntentVMNoNoNoNo
Quantum hardeningEd25519 + Dilithium3NoNoNoNo
Vaultless bridgeBurn/limboWrappedWrappedWrappedWrapped
3-tier state engineElasticState (Hot/Warm/Cold)Single trie (300M+ accounts)Flat store (500+ GB, rent)Single treeSingle store
Protocol-level anti-rugVSC-LAUNCHNoNoNoNo
Native AMMVexiDEXUniswap (dApp)Raydium (dApp)NoCetus (dApp)
No slashingJailing onlySlashingSlashingSlashingNo slash
No state rentElasticState compresses, never evictsDebated since 2017Account rent requiredNo rentStorage rebates
Multi-wallet compatVx/MetaMask/PhantomMetaMaskPhantomPetraSui Wallet

Competitive Moats​

  1. Patent-Pending IntentVM -- Legal protection for intent-based execution. Competitors must license or design around.
  2. Vaultless Bridge Model -- The stateless/limbo mechanism for non-burnable tokens is a novel contribution to bridge security. No other bridge eliminates vaults for native tokens like SOL/ETH.
  3. Quantum-Ready Infrastructure -- Ed25519 + Dilithium3 dual-signature is live in code. When quantum migration is urgent, Vexidus has a 5+ year head start.
  4. ElasticState -- No State Rent, Ever -- Ethereum has debated state expiry since 2017 without resolution. Solana charges rent. Vexidus solves state bloat at the infrastructure level: inactive accounts are compressed, not evicted. Users never pay to exist.
  5. Seven-Pillar Integration -- Features that are separate dApps on other chains (DEX, presales, reputation) are protocol-level on Vexidus, enabling atomic composition via IntentVM.

10. Team and Development​

Founder​

CJ -- Founder and CEO

  • Built Vexidus blockchain solo from concept to live testnet in 16 months
  • Designed and implemented IntentVM (patent-pending, proven on Solana first)
  • Founded Vexidus Corporation (Delaware C-Corp, est. 2019)
  • Founded Mashiyu Technologies LLC (Arizona, development partner)
  • MBA student (ongoing)

Development Structure​

EntityRole
Vexidus Corporation (Delaware C-Corp)IP, patents, investor capital, strategy
Mashiyu Technologies LLC (Arizona)Engineering, infrastructure, operations

Codebase​

  • Language: Rust (15 crates)
  • Tests: 176 passing
  • RPC Endpoints: 70+
  • CLI Subcommands: 65+
  • Deployed Frontends: 5
  • Lines of Rust: 50,000+
  • Repository: github.com/Mashiyu-Devs/Vexidus

Open Source​

  • Core blockchain: Open source (post-beta)
  • IntentVM: Patent-pending (proprietary until patent grant)
  • SDK, CLI, frontends: Open source

Appendix A: Technical Specifications​

Validator Requirements​

ResourceMinimumRecommended
CPU4 cores8+ cores
RAM8 GB16+ GB
Storage100 GB SSD500 GB NVMe
Network100 Mbps1 Gbps
Stake1,000 VXS5,000+ VXS

Network Parameters​

ParameterValue
Chain ID1618032 (0x18b070)
Block time12 seconds (configurable)
Max transactions/block10,000 (configurable via --max-txs-per-block)
Mempool capacity100,000 bundles
Bundle TTL120 seconds
P2P transportQUIC (TLS 1.3 + multiplexing, UDP)
Gas price10 nanoVXS/gas (configurable)
Auto-checkpoint intervalEvery 1,000 blocks
Checkpoints retainedLast 5

ElasticState Parameters​

ParameterDefaultCLI Flag
Hot cache entries100,000--elastic-hot-entries
Hot cache memory8 GB--elastic-hot-memory-mb
Hot to Warm threshold7 days inactive--
Warm to Cold threshold90 days inactive--
Demotion intervalEvery 100 blocks (~20 min)--
Warm compressionLZ4 (fast)--
Cold compressionZSTD (max, ~90% reduction)--
Feature flagOff (backward-compatible)--elastic-state

Address Formats​

FormatExampleUsed By
Vx0 (native)Vx0abc...xyzVexSpark, native SDK
0x (EVM)0x71C7...MetaMask, eth_* RPC
System (32-byte hex)0x000...0001Genesis accounts, internal

Appendix B: Resources​

ResourceURL
Walletwallet.vexspark.com
Explorervexscan.io
Token Studiovexforge.xyz
DEXvexidex.com
Faucetvexswap.xyz
GitHubgithub.com/Mashiyu-Devs/Vexidus

Document Version: 2.1 Last Updated: February 2026 Status: Beta Testnet Live

Vexidus: Seven Pillars. One Chain. No Compromises.

Copyright 2026 Vexidus Corporation. All rights reserved.