FAQ
This page answers common questions about the ZENANET network, token usage, AI services, and development tools.
1. What is ZENANET?
ZENANET is an EVM-compatible Layer-1 blockchain with fast block times, low fees, and support for AI-powered token creation.
Developers can deploy smart contracts, run dApps, and interact with the network using standard Ethereum tools.
2. What token does the network use?
The native token ZNNT is used for:
- Gas fees
- Smart contract deployment
- AI-driven token creation
- Wallet operations
- dApp interactions
3. Is ZENANET compatible with Ethereum tools?
Yes. ZENANET supports:
- MetaMask
- Hardhat
- Foundry
- Remix
- Web3.js / Ethers.js
No modifications are required—Ethereum tooling works out of the box.
4. Can I create my own token?
Yes.
The AI service allows users to create and deploy their own tokens without writing Solidity code.
After deployment:
- The token is registered to your ZENANET Wallet
- You can view and manage it in your Profile → Wallet
AI service URL:
https://zenaai.io
5. Does AI token creation require gas?
Yes.
Even though the AI automates deployment, all on-chain operations consume ZNNT as gas.
The AI service may also consume Credits, depending on the action.
AI interface:
https://zenaai.io
6. How do I check my tokens?
Go to:
Profile → Wallet (ZENANET Wallet)
inside the AI platform.
AI service:
https://zenaai.io
You can view:
- ZNNT balance
- Custom tokens
- Contract addresses
- Transaction history
7. How do I add ZENANET to MetaMask?
Use the RPC settings shown in:
Get Started → Add to MetaMask
You can add Mainnet or Testnet manually via the network settings.
8. Where can I view blockchain activity?
Visit the official Explorer:
https://scan.zenanet.io
You can browse transactions, blocks, addresses, smart contracts, and token data.
9. Are new features planned for the AI service?
Yes.
The platform will continually expand with additional features and improved automation.
AI service:
https://zenaai.io
Summary
The FAQ covers key questions about tokens, AI creation, wallets, RPC connections, and developer tools.
If you need detailed guidance, refer to the specific technical documentation sections.