MEV resistant
Conversions are processed together at consensus, preventing front-running, back-running, and sandwich attacks.
DeFi and payments
Fair DeFi without MEV exploitation. Low fees, secure payments, and protocol-level privacy, without smart contracts.
Low fees
Use 0.025% fees for reserve-to-basket conversions and 0.05% fees for reserve-to-reserve conversions.
Protocol-level security
DeFi operations are verified by miners and stakers without smart contract bug or approval risk.
Basket currencies
Create basket currencies backed by up to 10 reserves, with configurable reserve ratios from 5% to 100%.
Final payments
Send and receive payments with no chargebacks, no custodial intermediaries, and predictable settlement.
Multi-currency support
Accept VRSC, PBaaS currencies, and bridged Ethereum assets with native conversion support.
QR code integration
Package invoices into deeplinks and QR codes for mobile-friendly scan-to-pay experiences.
Cross-chain conversions
Convert across PBaaS chains and Ethereum bridge-connected assets through unified network liquidity.
Fee distribution
Fees are distributed transparently between miners, stakers, and reserves without MEV middlemen.
Build DeFi applications protected from MEV attacks
Verus DeFi solves the MEV problem by processing conversions simultaneously at the protocol level. Every trade in a block gets the same fair price, eliminating front-running, back-running, and sandwich attacks.
Unlike DeFi platforms that rely on smart contracts and sequential transaction processing, Verus handles DeFi operations through consensus.
MEV protection
- No front-running or sandwich attacks
- Same price for all trades in a block
- No value extraction by bots
Fee structure
- 0.025% for reserve-to-basket conversions
- 0.05% for reserve-to-reserve conversions
- 50% to miners and stakers, 50% to reserves
Basket currencies
Basket currencies combine liquidity pools, reserve backing, and cross-chain conversion into one protocol-level primitive.
Reserve currencies
Create basket currencies backed by up to 10 reserve currencies. Configure reserve ratios from 5% to 100% and let the protocol handle supply management.
Liquidity pools
Every basket currency functions as an automated market maker with built-in liquidity pools and MEV-resistant conversion logic.
Cross-chain trading
Trade across PBaaS chains and Ethereum bridge-connected assets with unified liquidity and protocol-level security.
Build cross-chain payment infrastructure with simple APIs
Implement standardized payment solutions and financial protocols with straightforward API commands.
Payment infrastructure
The VerusPay invoice specification enables standardized formats for creating and interpreting invoices across the ecosystem.
- Universal implementation across languages
- Standardized serialization format
- Multiple payment destinations
- Metadata and memo support
Mobile and QR integration
Enable scan-to-pay functionality with QR codes and deeplinks that work with compatible wallets.
- Easy-to-scan QR code generation
- URL-based deeplinks for instant payment
- Direct-to-wallet payment flows
- Cross-platform compatibility
DeFi integration
Integrate DeFi features into applications with API commands instead of complex smart contract programming.
- Currency conversion commands
- Liquidity pool management
- Cross-chain transaction support
- Programmatic basket currency creation
Multi-currency support
Accept payments in any currency with native conversion support, so receivers can get the currency they expect.
- VRSC and PBaaS currencies
- Bridged Ethereum assets
- Multiple currency types in one transaction
- Fixed, predictable transaction fees
Compare financial protocols for your dApp
Verus replaces contract-heavy financial infrastructure with native protocol operations, predictable fees, and consensus-level validation.
Feature
Verus DeFi
EVM-chain DeFi
Architecture
Protocol-level implementation
- DeFi built directly into L1 consensus
- Operations validated by miners and stakers
- No separation between native and token accounting
Smart contract based
- DeFi implemented as contract code
- Operations validated by contract execution
- Native coin and token accounting are separate
Programming required
Launch currencies, pools, and DeFi operations using API commands.
Requires Solidity programming or existing audited contract systems.
Smart contract risk
None from DeFi contracts. Operations are built into consensus instead of custom contract code.
High. Protocols depend on contract correctness, approvals, upgrade paths, and external dependencies.
MEV protection
All conversions are processed simultaneously, preventing transaction reordering exploits.
Vulnerable to front-running, sandwich attacks, and value extraction by builders or bots.
Swap and trade fees
0.025% for currency-to-liquidity-pool conversions and 0.05% for currency-to-currency conversions.
Typically higher swap fees plus gas fees, depending on protocol and network congestion.
Network fees
Fixed and predictable transaction fees without fee auctions or congestion pricing.
Variable fees that can rise sharply during periods of demand.
Multi-currency support
Native support for VRSC, PBaaS currencies, bridged Ethereum assets, and basket currencies.
Contract-based token support, usually centered around specific token standards.
Liquidity pools
Protocol-level basket currencies with up to 10 reserves, configurable reserve ratios, and automatic supply management.
Contract-based pools, often limited to fewer assets and vulnerable to transaction ordering.
Identity integration
Built-in VerusID support with human-readable addresses, recovery, revocation, and data capabilities.
Identity usually depends on add-on services and external naming systems.
Throughput
Scale-out architecture with 75-800 TPS per chain and horizontal scaling through PBaaS.
Base-layer throughput is limited, with scaling commonly pushed to layer 2 systems.
The comparison focuses on application architecture, risk surface, and cost predictability for builders choosing a financial protocol layer.