TECHNOLOGIES

Solana

A high-throughput, low-fee blockchain with a runtime distinct from the EVM. Different programming model, different trade-offs.

Last reviewed: 2026-05-24 byKevin Riedl wiki β†—

Solana is not EVM-compatible. Smart contracts (called "programs" on Solana) are written in Rust, deployed as BPF bytecode, and executed by the Solana runtime. The architecture optimises for throughput (thousands of TPS) and low fees, at the cost of higher hardware requirements for validators and a different (some say more centralised) decentralisation profile.

For consumer applications where the user pays sub-cent fees and confirmation is sub-second, Solana is hard to beat. For deep DeFi composability with the EVM ecosystem, the lift to bridge across is non-trivial. The right chain depends on which trade-off matters more for your product.

Wavect ships in both Solana and EVM. We have no chain bias; we have a use-case bias.

// FAQ

FAQs

FAQs

Solana wins on throughput and per-transaction cost; EVM wins on DeFi composability and developer ecosystem. For consumer payments and high-volume consumer apps Solana is hard to beat. For deep DeFi integrations the lift to bridge is non-trivial.
The programming model. Solana’s account-based architecture is different from Ethereum’s contract-state model: you pass accounts explicitly, you manage rent, you think about parallelism. Engineers fluent in Solidity routinely under-estimate the ramp-up to ship safely on Solana.
Depends on what you need. Validator hardware requirements are higher than Ethereum’s, so the validator set is smaller; outages have happened historically, fewer recently. For consumer apps the trade-off is usually fine; for systems where censorship resistance is the core promise, examine the threat model carefully.