Acala Network decision checklist
Before integrating with the Acala Network, evaluate the following criteria to ensure your infrastructure aligns with your project's needs.
| Criterion | What to check | Why it matters |
|---|---|---|
| Network type | Mainnet or testnet (e.g., Acala Mandala) | Testnet is essential for development; mainnet for production. |
| RPC endpoint reliability | Uptime, rate limits, and latency | Unreliable endpoints cause transaction failures and poor user experience. |
| EVM compatibility | Solidity support, precompiles | Acala's EVM+ allows Ethereum tooling; verify compatibility with your contracts. |
| Data archival depth | Full, archive, or pruned node | Archive nodes are needed for historical queries; full nodes suffice for most dApps. |
| Provider reputation | Documentation, support, SLAs | A responsive provider reduces downtime and troubleshooting effort. |
| Pricing model | Pay-as-you-go, subscription, or dedicated node | Match cost structure to your traffic patterns and budget. |
What is the Acala Network?
Acala Network is a decentralized finance (DeFi) platform built on Polkadot. It functions as a parachain, meaning it leverages Polkadot's shared security and interoperability while maintaining its own execution environment. Acala provides a suite of DeFi primitives including a liquid staking protocol (Homa), a decentralized exchange (DEX), and a cross-chain stablecoin system (Honzon). It is EVM-compatible, allowing developers to deploy Solidity smart contracts with minimal changes.
Key components:
- ACA token: The native utility and governance token.
- aUSD (now AUSD): A decentralized, multi-collateral stablecoin.
- LDOT: Liquid staked DOT, representing staked DOT plus staking rewards.
- Euphrates: A unified liquid staking platform.
- EVM+: An enhanced Ethereum Virtual Machine with Substrate-native features.
Acala Network architecture
Acala is built using the Substrate framework, which provides flexibility and modularity. It connects to the Polkadot Relay Chain via a parachain slot. The network uses collators to produce blocks and relay them to Polkadot validators for finalization. This design gives Acala high throughput, low fees, and the ability to customize its runtime.
EVM+ and Substrate dual environment
Acala supports both Substrate-native pallets and Ethereum-compatible smart contracts. Developers can write contracts in Solidity and deploy them via MetaMask or Hardhat, while also accessing Substrate-specific features like on-chain governance and custom pallets.
How to connect to the Acala Network
To interact with Acala, you need an RPC endpoint. Below are examples of connecting using common tools.
Using curl
curl -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \
https://acala-rpc.publicnode.com
Using ethers.js
const { ethers } = require("ethers");
const provider = new ethers.providers.JsonRpcProvider(
"https://acala-rpc.publicnode.com"
);
provider.getBlockNumber().then(console.log);
Using web3.py
from web3 import Web3
w3 = Web3(Web3.HTTPProvider("https://acala-rpc.publicnode.com"))
print(w3.eth.block_number)
Choosing an RPC provider for Acala
When selecting an RPC provider, consider the following factors:
- Reliability: Look for providers with transparent uptime statistics and redundant infrastructure.
- Rate limits: Ensure the plan matches your request volume. Free tiers often have strict limits.
- Geographic distribution: Low-latency endpoints improve user experience for global audiences.
- Support: Access to technical support can be critical during development and incidents.
OnFinality offers RPC endpoints for Acala mainnet and testnet, with flexible pricing options suitable for projects of all sizes. For high-traffic applications, a dedicated node provides isolated resources and consistent performance.
Common pitfalls and troubleshooting
1. Incorrect chain ID
Acala's chain ID is 787. Using the wrong chain ID in MetaMask or other wallets will cause transaction failures.
2. Insufficient gas for EVM transactions
Acala uses a gas model similar to Ethereum. Ensure your account has enough ACA to cover gas costs. You can estimate gas using eth_estimateGas.
3. Block finality delays
Acala blocks are finalized after being included in a Polkadot relay chain block. This may take a few seconds longer than Ethereum. Use eth_getTransactionReceipt to confirm finality.
4. Rate limiting on public endpoints
Public RPC endpoints often have rate limits. For production dApps, consider a private endpoint or dedicated node to avoid throttling.
Key Takeaways
- Acala Network is a DeFi parachain on Polkadot with EVM compatibility.
- It offers liquid staking, a DEX, and a stablecoin protocol.
- Developers can connect using standard Ethereum tools via Acala's EVM+.
- Choosing a reliable RPC provider is crucial for dApp performance.
- OnFinality provides Acala RPC endpoints and dedicated node solutions.
Frequently Asked Questions
What is the Acala Network RPC URL?
The public RPC URL for Acala mainnet is https://acala-rpc.publicnode.com. For testnet (Mandala), use https://acala-mandala-rpc.publicnode.com.
Is Acala EVM-compatible?
Yes, Acala supports the Ethereum Virtual Machine (EVM+) with additional Substrate features. You can deploy Solidity contracts with minor adjustments.
How do I get ACA tokens for testnet?
Use the Acala faucet available on their official website or community channels. Testnet tokens have no real value.
Can I run my own Acala node?
Yes, you can run a full node using Substrate. However, for production dApps, using a managed RPC provider like OnFinality saves operational overhead.
What is the difference between Acala and Karura?
Karura is the sister network of Acala on Kusama, serving as a canary network for experimental features. Acala is the mainnet on Polkadot.
Next steps
- Explore the Acala documentation for detailed integration guides.
- Test your dApp on Acala Mandala testnet using a reliable RPC endpoint.
- Compare RPC providers on OnFinality's network page to find the best fit for your project.
- Consider a dedicated node for high-throughput applications requiring consistent performance.
Related resources
Originally published at OnFinality.
Top comments (0)