Cryptospecting

FACTS // VERIFIED 2026-10-19

PRVX: the ProveX token, read from the code

Short answer

PRVX is the ProveX token on PulseChain at 0xF6f8Db0aBa00007681F8fAF16A0FDa1c9B030b11, the only address named on provex.com. Its whole supply was minted once at deployment on 2026-03-13; the contract has no owner, no mint, no pause and no blacklist. Holders can burn their own tokens, and a two-day launch restriction on transfers to contracts ended by itself.

What are the key facts about PRVX?

Item Value
Address (PulseChain) 0xF6f8Db0aBa00007681F8fAF16A0FDa1c9B030b11
Deployed 2026-03-13 00:34:45 UTC, block 26,009,137
Deployer 0xF6976f0355D510DC1C8239F8A1b31EA7b513926A (single-key address)
Source verified Sourcify, exact match of creation and runtime code, 2026-03-14 00:10:12 UTC
Compiler Solidity 0.8.24
Supply minted 1,272,716,813,971.881727192781030214 PRVX, once
Total supply on 2026-10-17 (block 27,821,251), unchanged on 2026-10-19 (block 27,837,197) 1,272,716,781,156.127436374907142312 PRVX
Burned by then 32,815.75 PRVX, plus 12,334.91 PRVX sitting at the 0x…dEaD address

The address is confirmed by provex.com, the site the official @ProveXCom account names as its own: it shows this address under “Buy $PRVX on PulseX” and its buy link opens PulseX with this token. All values in the table are on-chain readings for the dates shown.

Can anyone mint, pause or freeze PRVX?

No. The constructor mints the entire supply once to a single address (ProveX.sol:75-86); there is no other mint path, no owner, no pause, no blacklist and no upgrade proxy. Holders can burn their own tokens (ERC20Burnable, :45). The rest is standard functionality built from OpenZeppelin parts: ERC-20 transfers, signed approvals (EIP-2612), signed transfers (EIP-3009 / ERC-7598) and transfer-and-call (ERC-1363) (:27-45). The contract rejects PLS sent to it directly (:156-158).

What was the two-day launch rule?

For two days after deployment — until 2026-03-15 00:34:45 UTC — PRVX could not be sent to a contract (for example a liquidity pool) unless the sender or the receiver was on a list in a separate Allowed registry (ProveX.sol:134-151). The end time was set automatically at deployment to “deployment time + 2 days” because the deployer passed 0 (:82). After that moment the rule switched itself off for good; no one has to — or can — switch it back on. Transfers between ordinary wallets were never restricted.

How was PRVX distributed?

The deployer received the whole supply and started sending it out at block 26,009,524 (2026-03-13 01:42:15 UTC) in direct transfers — 7,465 of them in the first 20,000 blocks. On 2026-10-19 the deployer held 0 PRVX. Richard Heart described the token as given free to those in the sacrifice set (00:00–00:31); how sacrifice points were converted into PRVX amounts, and whether every recipient was a sacrificer, cannot be checked without the final points list, which is not public. More: The ProveX sacrifice.

Is PRVX being bought back and burned?

Not by the app contracts so far. provex.com says the app’s 2 % fee is used automatically to buy PRVX and burn it. On-chain on 2026-10-19, the fee goes to a single-key address, the current app contracts contain no buy-and-burn logic, and that address had never sent or received PRVX (details). Richard Heart said in December 2025 that the token can launch before the burn mechanisms exist (34:31–35:30).

The 32,815.75 PRVX removed from the supply went through the token’s own burn function, which any holder can use; who burned them has not been attributed.

Is anything about the contract still unchecked?

Two points. No audit report has been found; the source comment “[M-01 fix]” (ProveX.sol:140) suggests some review, but nothing is published. And PRVX was compiled for the Cancun version of the Ethereum virtual machine; its bytecode contains one MCOPY instruction, an opcode that PulseChain’s Shanghai rules do not include. Ordinary transfers work. Whether the code path that uses MCOPY can be reached, and what happens there, has not been analysed.

How do I recognise the real PRVX?

By the address. Several tokens on PulseChain use the names “ProveX”, “PRVX” or similar, and some look official. Only 0xF6f8Db0aBa00007681F8fAF16A0FDa1c9B030b11 on PulseChain is named by provex.com. Compare the full address before you trade, and do not copy addresses from transaction histories. More: Security.

Where can I use PRVX?

PRVX has no app of its own: the ProveX app settles trades in eUSDC and does not use PRVX. It trades on PulseX — the route provex.com links — and its contract can be called directly on PulseScan.

Interfaces that call these contracts, checked on 2026-10-19 — official ones first. A listing is not an endorsement: open apps from a bookmark, check the domain before you connect a wallet and read the risk line. Domains to avoid and what to do when an app is down: Interfaces.

Frequently asked questions

Can more PRVX be created?

No. The whole supply was minted once in the constructor, and the contract has no other mint function and no owner.

Why is PRVX not in this portal's token list?

It was deployed on 2026-03-13 and does not meet the first listing test, at least two years on PulseChain. It is described here, in the ProveX section, instead.

Sources // last verified 2026-10-19

  1. T1 · Primary PRVX on PulseChain (PulseScan)
  2. T1 · Primary Sourcify — PRVX verified source, exact match
  3. T1 · Primary Sourcify — Allowed registry used by the launch restriction
  4. T1 · Primary PulseChain RPC — deployment, supply and burn readings, 2026-10-17 and 2026-10-19
  5. T2 · Official provex.com — PRVX address and buy link
  6. T2 · Official Richard Heart, 2025-12-02 — token launch before burn mechanisms (34:31–35:30)

Source tiers are explained in Sources & methodology.