General FAQs
This document addresses some common inquiries regarding Prom zkEVM. For more in-depth information, please refer to our comprehensive documentation.
What Exactly is Prom zkEVM?
Prom is a modular ZkEVM Layer 2 that enables interoperability across various chains, including both EVM and non-EVM compatible networks. Prom submits its proof of transaction to the additional chains on top of the chosen Settlement chain, building the bridge between ecosystems.
Key Features of Prom zkEVM?
Multichain support: Prom can submit its proof of transaction across multiple networks, including both EVM and non-EVM compatible chains, which ensures a high level of decentralization and 100% uptime;
Efficiency & Scalability: reduced costs and enhanced scalability with zkSNARKs;
High-Speed Transactions: Polygon Zero's tech brings exceptional speed to every transaction;
Robust Security: Inheriting Ethereum's Layer 2 security, Prom ensures the highest level of data integrity;
EVM Compatibility: Seamless integration in a familiar EVM environment;
Gas Fee Reduction Expectations with Prom zkEVM?
Users can look forward to a significant reduction in gas fees relative to Ethereum Layer 1. Prom's Layer 2 protocols batch multiple transactions, spreading the cost of a single Layer 1 transaction over numerous Layer 2 transactions.
How Do zkRollups Operate?
zkRollups work by consolidating a large batch of transactions and validating them on the Ethereum network through a single zero-knowledge validity proof.
What Sets zkEVMs Apart?
zkEVMs once thought to be a distant future technology, have become a reality thanks to the technological advancements made by Prom Labs. Full EVM equivalence, combined with superior performance (in terms of throughput, latency, and cost), sets Prom zkEVM apart from other Layer 1 solutions, optimistic rollups, and ZK-Rollups.
Prom zkEVM's Comparative Edge Over Other zkEVMs?
Vitalik Buterin's neutral analysis offers a great reference point. Prom zkEVM differentiates itself with its efficient prover and notable Ethereum equivalence. While others employ an arithmetic circuit approach, Prom zkEVM's zkProver utilizes a State Machine approach.
Does Prom zkEVM Utilize a Separate Token for Transactions?
Yes, transactions in Prom zkEVM will utilize the PROM token for gas fees. Prom zkEVM also accommodates Account Abstraction via ERC-4337, enabling transparent fee payment with any token from the user’s perspective.
Suitable dApps for Deployment on Prom zkEVM?
Any dApp that's EVM-compatible can be deployed on Prom zkEVM, with the exception of those requiring specific precompiled contracts not currently supported. Detailed information on compatible precompiled contracts is available in our documentation.
Prom zkEVM’s Capability for Cross-Chain Interactions?
At present, Prom zkEVM does not support cross-chain functionalities. However, our future roadmap includes enabling asset movement across various Layer 2 networks, though not available at launch.
Principal Use Cases for Prom zkEVM?
DeFi Applications: High security and efficient capital utilization make it suitable for DeFi.
NFT, GameFi, and Enterprise Applications: Beneficial for these sectors due to low gas fees, fast transaction speeds, and robust security.
Payments: Ideal for users seeking real-time transactions with minimal fees.
How Reliable are Prom zkEVM's Proofs on Layer 1?
The accuracy of these proofs is assured by our zkRollup smart contract. Their reliability stems from data availability and the ease of verifying the SNARK proofs.
Compatibility of Prom zkEVM with Solidity and Vyper?
Yes, Prom zkEVM supports all languages that compile to EVM opcode, including Solidity and Vyper.
What Constitutes an RPC Node in Prom zkEVM?
An RPC (Remote Procedure Call) node in Prom zkEVM is a JSON-RPC interface compatible with Ethereum, enabling seamless integration with existing tools like Metamask, Etherscan, and Infura. Its operation is akin to Ethereum nodes such as geth.
Prom zkEVM’s Support for JSON-RPC EVM Query Specifications?
Prom zkEVM supports all standard queries (eth_* endpoints). Efforts are underway to extend support to additional endpoints like debug_*.
Last updated