NFT Marketplace v6.2.7

Release Date: August 28, 2026 Tags: PERFORMANCE, RPC

Overview

A rate-limit release for the gas estimator, and the only thing it changes is that the marketplace stops asking your RPC provider the same question over and over.

Wherever the marketplace shows an estimated gas cost, it asked the chain for a current gas price on every request. Nothing in that answer is specific to the customer looking at it, so on a busy marketplace it was one provider call per visitor — sometimes two — against an endpoint that is usually rate-limited and often metered. The answer is now held for thirty seconds and shared across every visitor and every backend process.

The figures customers see can therefore be up to thirty seconds behind the chain. Gas prices only move when a block lands, and the estimator has always been approximate and says so on screen, so this does not change what it is good for. There is nothing to configure and nothing to run.

Requires Core v6.7.2.

Update Instructions

Restart the backend.

---

Changed

Gas price estimates are cached for thirty seconds

The gas endpoint went to the chain provider on every single request, and the congestion reading it returns alongside the price is a second call on top of the first. Because none of it varies by customer, each visitor was paying for a fresh round trip to be told what the visitor before them had just been told.

• Changed gas price estimates are cached per chain for thirty seconds. A page view no longer costs an RPC call of its own, and the estimate a customer sees is at most thirty seconds behind the chain.
• Removed a second handler that was registered against the same gas endpoint and never served. Responses are unchanged — the endpoint returns exactly what it returned before, field for field — but a duplicate registration on a live route is the kind of thing that only stays harmless until something reorders it.