PROM valued at $5 million reportedly sold for $71: check the swap output

What the $71 report actually measures

Odaily reports three separate quantities: the 908,793 PROM sent into the pool, an approximate $5 million valuation of that holding, and the 0.0316 ETH received. Keeping those quantities separate matters. The valuation describes how the tokens were marked; the ETH amount describes what the reported sale produced. The report does not establish that a buyer elsewhere had offered $5 million for that whole position. Odaily on the reported valuation.

ChainCatcher describes the destination as a Uniswap V2 liquidity pool with almost no liquidity. It does not provide the pool's precise reserves in the report we opened. We therefore cannot turn “nearly empty” into an exact depth figure, reconstruct the pool's state before the trade, or identify the seller's intended minimum return from this text. ChainCatcher on the received ETH.

The dollar figures are approximate and belong to the report's observation. They are not current executable PROM or ETH quotes. A reader checking a transfer now needs a fresh quote for their own amount and route; copying the reported dollar conversion into a wallet calculation would combine observations from different moments. Odaily's reported amounts.

Why a token valuation can exceed a pool's buying capacity

Uniswap's official V2 pricing documentation explains that a pair is backed by a pool holding two tokens. The ratio of those balances, together with the constant-product rule, determines the price at which a swap executes. A dollar valuation on a news page does not add ETH to that pool. The trade must be priced against the balances available to the route actually used. Uniswap V2 pricing documentation.

That mechanism gives the PROM report its practical significance. The input holding can have a quoted dollar value while a particular pool offers very little of the output asset. Selling a large input amount into that venue does not create a matching buyer with an equally large dollar budget. This is our interpretation of the reported result using Uniswap's documented pool mechanics, rather than a reconstruction of this specific transaction. Uniswap's explanation of pool pricing.

The distinction also changes how to read the headline. A reported sale of tokens valued at $5 million does not mean the seller received $5 million, and the $71 proceeds do not establish a market-wide PROM price. Each statement answers a different question: how the holding was valued, what this route delivered, and what another trade might obtain. Only the first two are described in the opened incident reports. ChainCatcher's PROM account.

For someone who already holds PROM, the next useful check is the quotation for the amount they actually intend to exchange. A quote for a small amount cannot establish the output for a much larger order because the pool balances and pricing rule govern the swap. Keep the quoted input, quoted output and chosen route together when comparing alternatives. Uniswap on pricing an exact-input trade.

Check the output before signing

Start with the asset you expect to receive. Read the output quantity in token units before focusing on its dollar equivalent. In this report, the concrete output is 0.0316 ETH. The approximately $71 label is a valuation of that output. For your own proposed trade, write down the exact input and quoted output so that a changing dollar display does not obscure the exchange you are authorizing. Odaily's input and output figures.

Then compare that quote with a separate market observation. Uniswap's documentation warns against relying on pool reserves alone without an external price reference. Its example explains how a trade can execute at an unfavorable rate when the pool's price changes before execution. That warning supports checking the quote against another price observation; it does not establish that front-running caused this reported PROM result. Uniswap's external-price discussion.

Next, examine the minimum output, where the proposed transaction exposes it. The V2 documentation distinguishes calculations for an exact input from calculations for an exact output, and identifies minimum-output calculations for slippage. A usable check asks how much of the receiving token the transaction permits you to accept. An attractive portfolio balance cannot answer that question. Uniswap's exact-input and exact-output guidance.

A tolerance setting also needs a sensible starting quote. If the proposed route already gives an unacceptable output, permitting a small further deviation does not repair that quote. Compare the amount shown with the amount you intended to receive before deciding whether to proceed. This recommendation follows from the documentation's distinction between an observed price and the permitted execution rate. Uniswap's pricing and tolerance explanation.

If the output looks inconsistent with your intended sale, stop before submitting and review the route and amount. Requesting a new quote is a check, not a promise that a better one exists. We have not inspected current PROM routes or measured the depth of other pools, so this report makes no claim that another venue could absorb the full reported holding at its stated valuation. Uniswap's reserve-based pricing explanation.

For a proposed PROM swap, use this sequence before signing:

1. Record the exact PROM input and expected receiving-token amount from the same quote. Keep the route and observation time beside them.
2. Compare the output with an external price observation. If the implied exchange rate differs sharply, pause and check the amount and route before requesting another quote.
3. Read the minimum receiving-token amount permitted by the proposed swap. Proceed only if that amount matches what you intend to accept. After execution, compare the received amount with the recorded quote. These are suggested checks based on Uniswap’s pricing documentation.

Keep exchange transfers separate from a swap decision

The reported PROM transaction concerns an on-chain sale. It does not determine whether a particular reader's Binance withdrawal is pending, completed or available. If you are investigating your own transfer, preserve the asset, selected network, destination address and transaction reference shown in your account. Use that specific record when checking status instead of treating the PROM sale as an account-level answer. The scope of Odaily's report.

For a transfer that would be followed by a swap, treat those as separate decisions. First establish what your own transfer record says. Then obtain a quote for the intended swap amount. The PROM report documents neither your deposit status nor the current output you would receive. Combining the two checks would turn an observation about one sale into an unsupported assumption about another person's funds. ChainCatcher's description of the reported sale.

A message offering “Binance compensation” is not evidence of a recovery process. Our recommended response is to use the official channels already accessible from your account, rather than links delivered in unsolicited messages. Neither opened PROM report establishes a compensation application, a wallet-connection requirement or a recovery payment. There is no basis here for asking a reader to send assets or sign a recovery transaction. Odaily's report.

What would establish the cause of the bad execution

A transaction-level explanation would need the transaction record and the relevant pool state, with input and output assets identified. The reports we opened give a token quantity and a received ETH amount, but do not supply enough detail in their article text to inspect the exact route or contract call. Those details would be needed before attributing the outcome to particular transaction settings. ChainCatcher's account.

Uniswap's documentation describes front-running as a risk when swaps use a reserve-derived price without an adequate external reference. That is a mechanism readers should understand. It remains separate from the cause of this event: the opened PROM reports do not demonstrate a sandwich trade, identify a trading bot, or establish why the seller used this pool. We have not assigned any of those explanations to the transaction. Uniswap's pricing risk example.

The attribution to a Binance-linked attacker also remains the outlets' description, drawn from Lookonchain. We are reporting that attribution, rather than independently identifying the wallet owner. The new fact under examination is the reported PROM execution result. Broader conclusions about the total incident loss, remaining assets or customer repayment cannot be calculated from this sale alone. Odaily's attribution.

Quick answers for PROM holders

Did the seller receive $5 million?

The reports say the seller received 0.0316 ETH, worth about $71. About $5 million is their valuation of the 908,793 PROM sold, rather than reported cash proceeds. The output amount is the relevant figure when assessing this particular execution. ChainCatcher's reported proceeds.

Does this mean all PROM can only be sold at that rate?

The opened reports describe a sale into one nearly empty Uniswap V2 pool. They do not establish the available price or buying capacity across all PROM markets. Uniswap's pricing rules make the chosen pool and trade size relevant to an execution quote. Uniswap V2 pricing.

Does a transaction completing prove the quoted valuation was realized?

Uniswap V2 pairs enforce their trading invariant, accounting for fees, according to the official documentation. That check is distinct from the seller obtaining a particular external dollar valuation. Compare the receiving-token amount with your intended outcome before signing, then inspect the actual received amount after execution. Uniswap's explanation of V2 checks.