Waves Blockchain
Blockchain payment systems
Blockchain software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if Waves Blockchain and its alternatives fit your requirements.
Pay-as-you-go
Free Trial unavailableFree version unavailable
Small
Medium
Large
-
What is Waves Blockchain
Waves Blockchain is a public blockchain platform used to issue and transfer digital assets and build decentralized applications. It supports token creation, on-chain transactions, and smart-contract functionality through its ecosystem components. Typical users include developers building Web3 applications and organizations that need a blockchain network for asset issuance and payments. The platform centers on the Waves protocol and related tooling for wallets, nodes, and application integration.
Asset issuance and transfers
Waves supports creating and managing custom tokens on its network, which fits use cases such as asset issuance and internal settlement. It provides on-chain transfer capabilities that can be used for payment-like flows and token distribution. This positions it as a general-purpose network for moving value, rather than a single-purpose payment rail.
Developer-oriented blockchain tooling
The ecosystem includes components for running nodes and interacting with the network via APIs and client software. This helps development teams integrate blockchain transactions into applications without building all infrastructure from scratch. Compared with products focused primarily on wallets or custody, Waves is oriented toward network-level development and deployment.
Public network and ecosystem
As a public blockchain, Waves enables third parties to deploy applications and assets without requiring permission from a central operator. This can reduce onboarding friction for multi-party use cases where participants are not under one organization. It also allows interoperability patterns common in public-chain ecosystems (for example, using external wallets and exchanges), subject to the network’s supported standards.
Public-chain governance tradeoffs
As with other public blockchains, protocol changes and network parameters depend on ecosystem governance and validator participation rather than a single enterprise owner. This can complicate change management for organizations that require fixed roadmaps, contractual SLAs, or controlled upgrade cycles. Enterprises may need additional controls and policies to use it in regulated environments.
Smart-contract model constraints
Waves’ smart-contract approach and language choices differ from other widely adopted smart-contract ecosystems, which can affect developer availability and portability of existing code. Teams may face a learning curve and fewer off-the-shelf libraries compared with more common environments. This can increase implementation time for complex decentralized applications.
Operational and compliance burden
Running production workloads on a public blockchain introduces operational considerations such as key management, transaction fee management, and monitoring for network conditions. Organizations also need to assess compliance requirements (for example, sanctions screening, AML/KYC obligations, and data handling) that are not provided by the base protocol. These responsibilities typically fall on the implementer or third-party service providers.
Plan & Pricing
Pricing model: Pay-as-you-go (per-transaction fees denominated in the network token) Free tier/trial: No permanently free plan; no time-limited trial (see notes)
Example costs (public Waves mainnet, fees paid in WAVES unless noted):
- Transfer: 0.001 WAVES (minimum). Increased by 0.004 WAVES for transfers involving a smart account or smart asset (e.g., 0.005 WAVES or higher depending on smart-asset/script factors).
- Invoke Script (dApp call): 0.005 WAVES + K (where K is number of non-NFT assets issued by the invocation). Additional 0.004 WAVES may apply for smart-account/dApp sender complexity.
- Exchange (DEX) transaction: 0.003 WAVES (minimum). Fees increase when smart assets are involved.
- Issue (token issuance): 1 WAVES for a regular token; 0.001 WAVES for a non-fungible token (NFT).
- Mass Transfer: 0.001 WAVES + 0.0005 × N (N = number of transfers). For smart-asset transfers the base may increase (see docs).
- Data transaction: 0.001 WAVES per kilobyte (size rounded up to whole KB).
- Set Asset Script: 1 WAVES.
- Set Script: 0.001 WAVES per kilobyte of script (rounded up).
Notes / behavior:
- Many transaction fees are fixed minima; senders may specify higher fees to prioritize inclusion.
- Sponsorship: an asset issuer can enable sponsorship so users may pay fees in the sponsored asset; the issuer sets an equivalence so fees remain pegged to the WAVES minimum. This is the primary mechanism to allow end-users to avoid paying in WAVES directly.
Discount options: No documented subscription/volume/commitment discounts on the public Waves network; fee-reduction mechanisms rely on sponsorship (sponsored assets) rather than committed discounts.
Waves Enterprise (official enterprise offering): fees are denominated in the enterprise system token (WEST) and have different minima (examples from Waves Enterprise docs: Transfer 0.01 WEST; Issue 1 WEST; MassTransfer/minima differ). See Waves Enterprise docs for exact WEST-denominated fee table.
Source: Official Waves documentation pages (transaction fee and fees docs).
