Methodology

Base-specific scope

We compare the relevant product surface on Base. Solana, Ethereum or other-chain features do not automatically apply. A chain-specific unknown is not filled with another chain’s value.

Evidence labels

Confirmed features require supporting evidence. A confirmed absence is distinct from an unknown. Not applicable is reserved for a feature that genuinely cannot apply to the architecture, not missing research.

Fees and execution

Exact platform rates, ceilings, ranges and tiered fees are separate models. Network fees, slippage, tips, discounts and rewards need their own context. UI controls do not prove successful execution, private routing, custody architecture or measured protection.

Why we do not publish our own speed benchmarks

A speed measurement from our setup would reflect more than the platform alone. Our internet connection, network route, distance to the infrastructure and temporary congestion at data centres or network nodes can affect the result. Another user may see substantially faster or slower results, including when their connection takes a shorter route to the relevant infrastructure. We therefore do not present measurements from our environment as a universal platform speed or use them to rank products.

Our research focuses on verifiable product capabilities, chain-specific behavior, fees, documented architecture and observed interface controls, with the limits of each check stated. Where a provider publishes a speed or latency claim, we may report it with a clear attribution, source and stated conditions. Confirming that source verifies what the provider claims; it does not turn the claim into our independent performance measurement or make it directly comparable with another provider’s figure.

Freshness and limits

A check date describes the evidence checked on that date. A feed-generation date or current calendar label does not mean every product fact was reverified. We preserve supporting research privately and publish selected sources and material uncertainties rather than private audit logs.

Corrections

Send a page-specific correction and supporting source through our contact page.