PROM

Prom Explained: A Polygon CDK zkEVM With PROM Gas and Governance Roles

Prom is a zero-knowledge Layer 2 designed to run Ethereum-compatible applications while batching activity away from Ethereum. Its main open questions concern operational centralization, bridge availability, governance execution, and how the PROM token’s older data-market role relates to the newer network design.

What Prom is designed to do

Prom presents itself as a scalable network built with Polygon CDK and zero-knowledge proofs. Its stated purpose is to execute transactions and smart contracts off-chain, then use cryptographic proofs to verify the resulting state. The project describes Prom as EVM-equivalent, meaning that applications compiled for the Ethereum Virtual Machine can be deployed with limited changes, although the documentation excludes applications that depend on unsupported precompiles.

The practical target is familiar to users of other Ethereum Layer 2 networks: reduce the amount of computation and settlement data handled directly by Ethereum while retaining a verification path to a settlement chain. Prom’s documentation says transactions are grouped into batches and verified through a zkRollup smart contract. That design can reduce per-transaction costs, but the resulting user experience depends on the sequencer, prover, bridge contracts, data availability, and the settlement process working as intended.

How the architecture works

Prom’s protocol documentation describes a transaction path that begins with users submitting signed transactions to a Trusted Sequencer through a JSON-RPC endpoint. The sequencer orders valid transactions, applies them to the network state, and packages them into batches. A prover then converts the resulting computation into a proof that can be checked by a smart contract on the settlement layer. The documentation distinguishes between trusted state, virtual state, and verified state; withdrawals require the final verified state rather than only the sequencer’s immediate result.

This architecture is not fully decentralized according to Prom’s own protocol FAQ. The project states that the sequencer and prover were initially centralized, with plans to decentralize the sequencer and create a market for provers. That distinction matters because a valid zero-knowledge proof can protect state correctness without, by itself, proving that transaction ordering, censorship resistance, liveness, or infrastructure access are already decentralized.

PROM’s role inside the network

PROM is described by the project as the native currency of the Prom network. Its primary stated function is paying gas for transactions and smart-contract interactions. The documentation also assigns PROM roles in governance, access to network services, and validation-related participation. Prom’s account-abstraction documentation says users may be able to have fees paid in another token from the user’s perspective, but the protocol still identifies PROM as the network gas asset.

PROM also exists as an established Ethereum ERC-20 token. Etherscan identifies the Ethereum contract as 0xfc82bb4ba86045af6f327323a46e80412b91b27d and reports a verified PROMToken contract. That on-chain token should not be confused automatically with every representation used on another network or with bridged assets. Users and applications need to check the network, contract address, bridge route, and wallet configuration before treating two PROM balances as interchangeable.

Governance and upgrade control

Prom’s governance materials describe Prom DAO as a token-based system in which PROM holders can propose and vote on initiatives. The published memorandum specifies a linear voting model, so voting power is generally proportional to token holdings. It also describes delegated voting, expert roles, validators, proposal thresholds, and a possible second review stage for proposals that have passed member voting.

The governance scope described by Prom is broader than community discussion: it includes potential decisions about core-contract upgrades, vulnerabilities, performance, treasury use, grants, service providers, and liquidity support. The memorandum also assigns operational responsibilities to an off-chain Council where execution requires activity outside smart contracts. As a result, PROM ownership can provide governance influence, but the practical effect of a vote depends on proposal rules, delegate concentration, validator participation, execution delays, and the division between on-chain actions and Council-managed operations.

Users, developers, and dependencies

The intended users are developers deploying EVM-compatible applications, users moving assets into a lower-cost execution environment, and participants who want to help govern or validate the network. Prom publishes mainnet connection details including RPC URL, chain ID 227, the PromScan explorer, and PROM as the network currency. Its documentation also describes a bridge interface and lists Ethereum, BNB Smart Chain, Optimism, Arbitrum, and Polygon as supported routes.

There is a documentation inconsistency around interoperability. The bridge guide describes live asset transfers across several networks, while the general FAQ says cross-chain functionality was not available at launch and frames asset movement as a future capability. This may reflect different publication dates or changing product status, so bridge availability and supported assets should be confirmed through the current interface and transaction records rather than inferred from a single documentation page.

Earlier Prometeus roots and present scope

Prom’s public code history also contains an earlier Prometeus Network design focused on decentralized data exchange. That documentation described Ignite and Stoa applications, encrypted data storage, service nodes, validators, and smart-contract distribution of PROM payments among data owners and service providers. This history helps explain why PROM has an older data-market identity, but it should not be treated as proof that those products remain the main source of current network activity. The current Prom site and documentation instead emphasize the Polygon CDK zkEVM network.

Key takeaways

• Prom is an EVM-compatible zero-knowledge network built with Polygon CDK.
• PROM is presented as the native gas, governance, access, and validation-related token of the network.
• The protocol documentation says the initial sequencer and prover were centralized, with decentralization planned for later stages.
• Prom DAO uses token-weighted governance with delegation, expert roles, validators, and possible off-chain Council execution.
• Prom’s bridge documentation and general FAQ give different accounts of cross-chain availability, so current route support requires direct confirmation.
• PROM also has an Ethereum ERC-20 representation whose contract address should be checked before using bridges or applications.

Risks and open questions

• Initial reliance on a Trusted Sequencer and centralized prover creates operational and censorship-resistance dependencies until decentralization milestones are demonstrated.
• Zero-knowledge verification does not remove risks from bridge contracts, settlement contracts, data availability, RPC infrastructure, or withdrawal processes.
• The published documentation is internally inconsistent about whether cross-chain functionality is currently available, creating a practical risk of using unsupported routes or assets.
• Token-weighted voting can concentrate influence among large holders or delegates. Governance outcomes may also depend on validators and an off-chain Council.
• The reviewed sources did not establish a current independent security-audit record for the full Prom network, bridge, prover, sequencer, and governance stack.
• The relationship between Prom’s earlier decentralized data-market software and the current Polygon CDK network is not fully documented as a continuing production dependency.