Basket currencies
Create reserve-backed currencies with 5-95% reserve ratios, fully backed liquidity pools, and up to 10 reserve currencies.

Create powerful currencies, tokens and liquidity pools, secured by consensus instead of vulnerable smart contracts.
Create reserve-backed currencies with 5-95% reserve ratios, fully backed liquidity pools, and up to 10 reserve currencies.
Create standard tokens with fixed or flexible supply, with the option to bridge them to Ethereum as ERC-20 tokens.
Conversions are solved simultaneously at consensus, providing MEV resistance and fair pricing for participants.
Configure carve-outs, discounts, preallocations, registration fees, and referral systems.
Launch with premine allocations, vesting schedules, timelocks, automatic VerusID distributions, and referral rewards.
Set funding levels in multiple currencies, refund automatically if targets are not met, and reward early supporters.
Export currencies to Ethereum as ERC-20s or import existing ERC-20s with non-custodial 1:1 mapping.
Launch currencies with built-in liquidity pools so trading can begin without external market makers.
Currencies inherit PBaaS chain security, with transactions and conversions protected by 50/50 PoW/PoS consensus.
Choose between reserve-backed basket currencies or standalone token currencies based on the needs of your project.
Basket currencies operate like automated market makers with reserve backing, dynamic supply, and consensus-enforced conversions.
Function like automated market makers with one or more reserve currencies backing them.
Supply expands when people convert into the basket currency and contracts when they convert out.
Currencies can be fully backed or partially backed by reserves, with reserve ratios as low as 5%.
Value is linked to reserves and reserve ratio without external oracles or price feeds.
All conversions in the same block get the same fair price with no front-running or sandwich attacks.
Conversion fees are 0.025% when converting to or from reserves, and 0.05% when converting between reserves.
Simple tokens are standalone currencies without backing reserves, with supply behavior determined by the selected control model.
Standalone currencies without backing reserves.
For decentralized tokens, the supply is fixed unless tokens are burned.
Can be used as reserves in other basket currencies
Can be exported as ERC-20 to Ethereum
Every currency launch includes a preconversion phase before the currency begins operating. It bootstraps initial liquidity, distribution, and value from day one.
Users contribute currencies to the reserves and receive a proportional share of initial supply based on contribution value.
Users send currency to the creator at a predetermined exchange rate to receive tokens when the currency launches.
The preconversion period lasts at least 20 blocks, approximately 20 minutes, and can run longer depending on project needs.
If a minimum funding requirement is set and not met, the currency does not launch and contributors receive automatic refunds minus network fees.
The preconversion period establishes real backing and market participation before a new currency becomes active.
Decide between decentralized and controlled currencies, with launch requirements tied to a VerusID namespace.
Every Verus currency can include a crowdfunding phase during launch, creating immediate liquidity and fair distribution.
Use standard API commands and flexible parameters to create powerful financial instruments.
# Creating a community currency with multiple reserve currencies
./verus definecurrency {
"name": "Community Currency",
"options": 33, // basket currency
"currencies": ["VRSC", "tBTC.vETH"],
"initialcontributions": [5000, 1],
"minpreconversion": [10000, 2],
"initialsupply": 10000,
"prelaunchcarveout": "0.1",
"preallocations": [
{ "Marketing Fund@": 2000 }
]
}
Creates a basket currency with reserve backing
Defines which currencies back the basket currency
Initial reserve amounts developers must provide
Minimum funding thresholds for the preconversion phase
Percentage of reserves sent to developers before launch
Verus currencies enable financial applications beyond traditional cryptocurrencies.
Create personalized currencies that connect creators with their communities through direct ownership and engagement.
Build local economic systems with currencies designed specifically for community needs and values.
Every Verus currency can serve as a namespace for self-sovereign identities called SubIDs. Users can register identities like Username.Currency@ for your community or project.
SubIDs inherit core VerusID features. They can hold funds, store data, and serve as authentication credentials.
VerusIDs can serve as membership credentials, giving users verifiable proof of belonging to your community.
VerusIDs can hold tokens, NFTs, and other digital assets so users can prove ownership and transfer assets securely.
Use VerusIDs for password-free login and access control based on identity ownership.
Build reputation and trust systems around VerusIDs for contributions, engagement, and standing.
If your currency is named COMMUNITY, users can register SubIDs like alice.COMMUNITY@ or dao.COMMUNITY@. These SubIDs function like VerusIDs but cannot create new currencies or blockchains.