Are you planning to launch a successful Web3 application? Think uniform scaling. Think Harmony.
As Web3 apps rise in popularity, here’s why you’ll be a winner with Harmony:
User experience. When you make a big launch on Harmony with 100K users, or a massive NFT airdrop, your users won’t face sticker shock like they would with other chains. That’s because we’re built to handle massive usage without increasing fees due to congestion.
Your business model. Model out the economics: will the business make sense, factoring in server costs, when your grant from another chain runs out and the speculative tokens lose their luster? Will you be able to attract enough users given the fees?
Think global: If you want to attract a million users, you’ll need to think globally, and Harmony is well-established to do so, with our forever-low fees and fiat gateway campaigns. Most gamers worldwide won’t want to spend more than $1-$2/month just for blockchain services, let alone $10/month. Which means that if you want to expand your user base to the other 98% not yet using Web3, you should launch on Harmony.
Scaling: Whatever you throw at us, we can take it (including DeFi Kingdoms, the #1 game in 2022 in Web3). We’re battle-tested and proven that we can handle multiple dapps with 1B requests/day (more than any other chain), 250k users/day, 1.5M wallets, 1B in-game transactions, and all with 2 second finality. And Harmony has all of the room for you to grow, whether you’re handling streaming payments, daily governance and voting, exchange lending, or fixed income products. Elastic RPC.
HARMONY’S UNIFORM SCALING SOLUTION IS THE BEST.
How much do you really want to worry about RPC, tokens, validators, and consensus?
Other blockchain scaling solutions have their disadvantages:
Fine-tuning the consensus algorithm on-chain for maximum throughput:
Tweaking block size and block generation time can cause miners receiving the block with long delay to waste computational power mining on top of the previous block, and it has security implications (many orphan blocks) and leads to centralization.
Alternative ways to reach consensus in a chain:
Some protocols take a modular, heterogeneous approach like an application chain. Whether leader or committee elections based on the Sybil-resistance mechanism, or permissioning the setting through something like Tendermint (like Binance, Crypto.com, and Terra users) to employ BFT consensus algorithms, it provides less security and decentralization and is limited by the fact that all nodes must exchange, verify, and store all on-chain data. The application chain is bounded by the IBC (Inter-Blockchain Communication Protocol) middle part they share; additionally, validators are a pain point: BTC has 10k, ETH has 20k validators, Solana has 5k.
Transferring the transaction load off-chain:
Payment channels are capital-hungry; parties are subject to denial-of-service attacks from others for short periods, keeping the revocation transaction from making it on-chain; and funds can be stolen from the channel when an adversary censors the revocation transaction during the dispute period, closing the channel in a previous more profitable state.
Sidechains (like Cosmos and Polkadot) make security your own responsibility, and they force each node to be responsible for verifying and confirming transactions, and choosing and running the consensus protocol.
Commit-chains and rollups:
ZK-rollups or optimistic rollups can be used for the operator to periodically commit on-chain compressed information about the off-chain transactions, but they face the great challenge of data availability, and they are bound by how fast the proof is off-chain.
But Harmony’s way of scaling for maximum throughput is the best for long-term scalability.
Uniform sharding, without limits.
Harmony shards the state on-chain, employing multiple chains in parallel all operating under the same consensus. Transactions to be processed in parallel by different subsets of nodes, reducing the resource requirements for each node in the system, enabling the chain to achieve massive horizontal scaling. Horizon’s expansion is linear and homogenous. Unlike ZK (bound by how fast the proof is off-chain) or application chains (bounded by the shared IBC), on Harmony, there’s no specific bottleneck, whatever the demand.
You can scale up globally without worry — no need to think about whether validators or requests for endpoints are different. If you have more demand, we have more shards, so everyone will look the same, and use ONE token. No need to worry about block finality (unlike optimistic solutions that can be rolled back). And our elastic RPC means that you won’t need to continually ask if your chain can handle the volume. Never mind the stopgap L2 workarounds: the future is uniform.