Market data and current feature availability

Trade chart history and timeframes#

Trade charts offer 1H, 1D, 7D, 1M, 3M, 1Y, 5Y and All. The date range chooses the initial view; Candle interval chooses the size of each candle. Selecting a range resets to an interval suitable for that period. Intervals too small to cover a finite period within 5,000 candles are not offered.

History requests use the documented xrpl.to resolution, candle count and backward-page cursor. Drag the chart horizontally to pan through time. Approaching the oldest loaded candles automatically requests an earlier page. A selected finite timeframe is the starting view, not a restriction on browsing older pages. Mouse dragging and horizontal touch dragging are supported; vertical touch scrolling and page pinch zoom remain available. Double-click resets the latest view. Shift with left/right arrow keys pans, plus/minus zooms, and End resets the view. An empty older page ends pagination for that view. Missing data, newly launched assets and provider retention can limit coverage; All means available indexed history, not a guarantee of records from launch.

The chart retains up to 5,000 loaded candles rather than keeping only the latest 250. Dense datasets are grouped for display: the first open, highest high, lowest low, last close and total volume of each group are preserved. The trade chart keeps the history summary and candle-count text out of the interface; other informational charts may show a grouping notice. Select a larger candle interval to cover more history at the display limit.

Refresh discards the current request’s browser cache entry. Successful history remains visible if a later refresh fails, with a warning. Old responses are discarded when the network, asset, date range or candle interval changes. The separate swap panel still obtains its own executable quote; chart prices never authorize a transaction.

How market data reaches the screen#

XRPL.to provides indexed token and NFT market information. Its visible credit appears beside the data. XRPFrontend’s server forwards the read-only market requests used by the interface with a private provider credential. Responses can be reused briefly in session memory; no persistent provider dataset is maintained. The route is for the XRPFrontend interface, not a supported external integration API. Other prices and logos may come from separately identified providers.

Indexed data is informational. It may lag the ledger, be incomplete or contain owner-supplied content. NFT ownership/offers and executable token trades are checked independently on the ledger before wallet approval. A listing or logo does not verify an issuer, authenticity, backing, liquidity or a provider partnership.

When market data is limited#

A provider rate-limit response pauses further XRPL.to requests for its Retry-After interval. Seconds and HTTP-date values are honored; a documented body delay is used when the header is missing. Requests never retry during that cooldown. An active browser request can retry once after a cooldown of up to one minute; longer limits require a later manual retry. There are no alternate provider routes.

A cooldown timestamp can survive a reload in the same tab; market payloads are not saved. Market requests pass through XRPFrontend’s server so provider credentials stay private. If data is unavailable, wait for the displayed retry time or try again later.

Temporarily paused features#

The Developers navigation, console, converters, standalone faucet and TOML generator are hidden and blocked at their old routes. Public profile integration APIs remain paused. User-facing profiles, PayString, NFT trading and core wallet tools continue to use their existing flows. Token creation and NFT minting remain paused. Issuer metadata instructions link to the official TOML specification.

Batch swaps and NFT purchases#

Qualifying XRP swaps use one All-or-Nothing Batch containing the swap and disclosed platform fee. Customer authorization occurs in the customer wallet. Commission booking requires verified inner settlement metadata. XRP-priced NFT sell-offer purchases also use an all-or-nothing Batch. The connected Mainnet node must confirm the required Batch amendments, and the wallet must sign the full Batch. Token creation and NFT minting remain paused.

Policies and help#

Review the current Terms of Service and Privacy Policy using the links below. They explain platform purchases, wallet signing, public ledger data, third-party services, private business records and request/deletion limits. Contact admin@xrpfrontend.com about support, content concerns or service-held data. Never send a recovery phrase or private key.