Polymarket U.S. App Adds 5-Minute Markets for BTC, ETH, SOL and XRP
The short answer
Polymarket has added five-minute crypto up/down prediction markets to its U.S. app, initially covering BTC, ETH, SOL and XRP, according to October 28 reports from ChainCatcher and PANews. For a trader examining the new contracts, the first job is to read the exact observation window and settlement rule: a view on a coin's next move is useful only if it matches the contract being offered. PANews
ChainCatcher reports that pricing uses CF Benchmarks data, ties settle as Up, and taker charges are separate from the bid-ask spread. Those details deserve a place beside the entry quote before any order is considered. The launch reports establish the product announcement; they do not provide a complete contract specification or a live executable quote. ChainCatcher
Show less
Four coin markets, one short observation window
ChainCatcher published its report at 04:45:01 SGT on October 28, naming BTC, ETH, SOL and XRP. PANews also reported the five-minute launch, attributing it to Polymarket’s announcement. PANews ChainCatcher
That product description gives a reader a narrow question to investigate: how the specified crypto price is classified over the stated interval. A person interested in ETH over the rest of the day should first decide whether a five-minute question answers their actual trading objective. The duration belongs in the decision before the direction. Choosing a familiar ticker does not resolve that mismatch.
For an existing BTC or SOL holder, keep the proposed prediction contract separate from the position already held. Write down what would make the prediction contract resolve Up or Down, then compare that question with the exposure in the existing account. Without the complete rules and quoted terms, the launch alone gives no basis for calculating whether a second position offsets the first.
The four names also set the scope of this announcement. Readers interested in another coin need to find its own market and terms. Neither report establishes a broader launch list, a schedule for more assets, or automatic availability across other Polymarket products.
Read the benchmark before comparing charts
ChainCatcher identifies CF Benchmarks as the pricing-data source. Its short report does not identify the complete benchmark methodology, all observation timestamps, or the treatment of unavailable data. Those missing details matter when a reader tries to reproduce the result of a specific contract.
Payward's October 27 announcement supplies original context for the benchmark relationship. It says CF Benchmarks indices are integrated into prediction contracts from Polymarket USA. The announcement also says each index has a published methodology describing its underlying sources and how inputs are screened and combined. For core crypto benchmarks, inputs include data taken directly from constituent exchanges. Payward
That is a reason to look up the index named by the contract before comparing an exchange quote with its settlement reference. Payward says each index has one publication frequency available to all clients. A reader trying to reproduce an observation should therefore look for that index's publication schedule as well as its methodology. The statement confirms the broader Polymarket USA benchmark relationship; it does not independently confirm this launch's five-minute interval or tie provision.
Begin with the contract's stated reference. Look for the full benchmark name and the exact start and end of the observation interval. If the app supplies a rules document, keep that document beside the displayed market. A chart on a separate exchange can help you examine a market, but a comparison requires matching its timestamps and reference with the contract's own terms.
Record the timezone too. A screenshot marked only with an hour and minute is a poor record for comparing two observations later. Keep the date and timezone with both endpoints. For a personal note, Singapore Time can sit beside the app's original timestamp so that the comparison remains readable without changing the source time.
If the reference price on your exchange differs from the contract display, identify what each number represents before treating the difference as an error. The reports do not establish that an exchange's last trade, its chart candle and the contract's benchmark are interchangeable. The practical question is which published reference the contract says it will use.
A useful record for a contract under review contains the coin, the named benchmark, the observation interval and the rule text saved at the time. If any of those fields is unclear, the next step is to locate the product terms that answer it. A headline containing BTC and five minutes cannot supply the missing specification.
The reported tie rule needs exact reading
ChainCatcher says a tie settles as Up. That gives equal start and end values a stated direction in its account of the launch. PANews's shorter item confirms the product and asset list but does not independently describe this rule.
For someone reading the order screen, the follow-up is concrete: find how the contract defines equality. Check whether the rules specify precision or rounding, and locate the values used for the comparison. The media report does not answer those questions. Two rounded numbers that look equal on a display are insufficient evidence to reproduce a settlement calculation.
This distinction is especially relevant when reviewing a finished interval. Keep the contract identifier and its final reference values together. If a result looks different from a chart you watched, compare the rule and observations before drawing a conclusion about settlement. A complaint is easier to assess when it identifies the exact contract and the values being disputed.
The tie provision also belongs in any comparison with another short-duration product. Read that product's equality clause separately. The opened reports establish a reported rule for this launch; they do not establish a common rule for every crypto prediction market.
A quoted price leaves a cost question
ChainCatcher reports that taker fees are charged separately from the bid-ask spread. It gives no fee percentage or complete fee formula in the opened item. A reader therefore needs the actual fee schedule or order preview to calculate the cost of a proposed trade.
When reviewing an order, write down the quoted price and quantity, then find the separately displayed charge. Read what the final confirmation says will be debited. If the screen offers several order choices, inspect the terms of the one you intend to use rather than carrying a cost assumption across from another choice.
For a comparison with an exchange position, use the same intended cash amount and time horizon in your notes. Identify the entry cost on each product and how each position would end. The launch reports contain no payout table, early-exit conditions or fee formula, so they cannot support a numerical ranking between a prediction contract and an exchange trade.
Keep any fee assumption visible in a calculation. If you have only the headline or a screenshot of one side of the market, leave the cost calculation unfinished until you can read the relevant charge. Calling a position inexpensive from its displayed contract quote alone would skip the separate fee reported by ChainCatcher.
The rates board is a separate place to examine exchange data. Use it for the instrument and measure actually displayed there. It does not supply the missing terms of this five-minute contract.
In Polymarket’s U.S. app, open the intended BTC, ETH, SOL or XRP market and check its interval and settlement reference. Then read the order preview for the quoted quantity and separately charged fee.
Match the five-minute question to the event you are watching
For a trader following a scheduled economic release, first compare the release time with the proposed contract's interval. The market calendar can be part of that preparation. Then read the contract's own endpoints. A market question that ends before the event you want to evaluate does not answer the same question as one covering the release.
Avoid turning an expectation about a day's direction into an assumption about a particular interval. Write the intended observation period in full before reviewing a quote. If the reason for considering the trade concerns a later development, revise the question you are asking rather than stretching the meaning of five minutes.
The same approach applies to a reader watching BTC while holding ETH. Select the actual asset named by the contract, then determine whether that is the asset your decision concerns. The launch includes both tickers, but the two reports provide no correlation estimate that would justify substituting one exposure for the other.
For an interval already completed, separate the original reason for the trade from the observed outcome. Save the opening reference and the rule alongside the closing reference. That record lets you ask whether you understood the contract correctly without rewriting the original rationale after seeing the result.
What the launch reports leave open
The announcement is specifically about the U.S. app. Neither opened item supplies a complete account-eligibility list, state-by-state access rules, account limits or funding instructions. Readers should check the terms attached to the account and product they actually see. The U.S. label alone cannot establish access for an individual reader.
There is also no supported market-reaction figure in the two product reports. They do not show trading volume in the new contracts or demonstrate that the launch moved BTC, ETH, SOL or XRP. The coin names identify the initial markets; they are not evidence of demand or a price catalyst.
The next useful product evidence would be the applicable contract specification and fee schedule. Those documents would let a reader resolve the benchmark details, equality definition and actual order cost that the short launch reports leave unanswered.
Quick answers
Which coins are included?
The reported initial list is BTC, ETH, SOL and XRP.