> For a complete page index, fetch https://docs.conduit.xyz/llms.txt # Changelog ## September 11, 2026 ## Monitor bundler activity in the Conduit app You can now monitor Conduit Bundler activity from your chain's **bundler** page. Summary cards and graphs provide current and historical views of UserOperation and bundle activity. ## What's new ### Summary cards and graphs The page includes **UserOp submissions (last 30 days)**, **UserOps awaiting inclusion (current)**, and **Bundle inclusion rate (5m avg)** summary cards. Historical graphs show **UserOp submissions**, **UserOps awaiting inclusion**, and **Bundle inclusion rate** across selectable time ranges and granularity options. Learn more about Conduit Bundler metrics ## September 9, 2026 ## Detailed RPC performance graphs for chains You can now see more detail about RPC traffic and response times on your chain's **Metrics** page. The updated graphs help you identify who is using your RPC endpoint and understand latency beyond a single average. ## What's new ### RPC requests by traffic source The RPC Requests graph now groups accepted traffic into authenticated requests that use a Nodes API key, public requests to the unauthenticated endpoint, and requests from Conduit internal services. The graph opens in a stacked view, and you can switch to a line view or hover over the legend to highlight a traffic type. ### Response-time percentiles The Response Time graph now shows average, P95, and P99 latency. Compare the series to distinguish typical performance from slower requests at the upper end of the latency distribution. ## August 24, 2026 ## Filter RPC metrics by JSON-RPC method You can now filter the RPC metrics page by one or more JSON-RPC methods. The selected methods apply across request volume, compute unit usage, response time, success rate, and breakdown charts, helping you compare the performance and usage of specific RPC methods. On the **Metrics** page, use the **Method** dropdown to select the methods you want to analyze. ## July 29, 2026 ## Interactive JSON-RPC API reference The Conduit Nodes documentation now includes an interactive JSON-RPC API reference and method playground, generated from Conduit's OpenRPC specification with Fern's OpenRPC support. * **Explore supported methods** -- Browse the Conduit Nodes JSON-RPC API by method, with descriptions, parameters, response schemas, and examples in one place. * **Try requests in the playground** -- Build JSON-RPC requests from the documented schemas and test them against your Conduit endpoint. * **See method pricing** -- Each method displays its Compute Unit cost so you can understand request cost while integrating. * **Use a machine-readable specification** -- The same OpenRPC source powers the reference, keeping the public API specification and rendered documentation aligned. [Explore `eth_blockNumber` in the JSON-RPC API playground](https://conduit-preview-feat-add-openrpc-json-rpc-docs.docs.buildwithfern.com/rpc-nodes/json-rpc-reference/eth-block-number). ## July 27, 2026 ## Upcoming explorer migration (August 3) On **August 3, 2026**, Conduit transitions managed Blockscout deployments to Conduit Explorer. Every Conduit chain includes Conduit Explorer at no additional cost, with support for inspecting blocks and transactions, viewing transaction traces, verifying contracts, and interacting with contracts. Conduit imports verified contracts from existing Blockscout deployments into its hosted contract verification server, so they remain available in Conduit Explorer. If a contract is missing after the migration, you can verify it again or contact Conduit support for help with bulk imports. Conduit Explorer reads data directly from your chain's RPC endpoint, so it doesn't provide indexing-backed features such as address transaction history, token holder and transfer analytics, NFT browsing, or public APIs. If you need these features, you can contract directly with Blockscout Hosted, and Conduit can provide an introduction and access to preferred partner pricing. Contact your Conduit representative or [submit a support request](https://portal.usepylon.com/conduit-xyz/forms/support-request) before August 3 if you need a migration deferral or want an introduction to Blockscout Hosted. [Compare Conduit Explorer and Blockscout](/chains/explorer). ## July 23, 2026 ## Upcoming RPC access policy changes (August 4) Starting **August 4, 2026 at 12:00 PM PST**, Conduit is updating RPC access rules to improve platform stability and security. Keyed traffic on Pro and Enterprise plans is unaffected. * **`debug_*` and `trace_*` methods require an API key** -- Unauthenticated calls to these methods are rejected. * **WebSocket connections require an API key** -- Anonymous WSS connections are rejected. Append your key to the WSS URL to keep subscriptions running. * **Lower rate limits for Public and Free traffic** -- Public drops to 25 req/s; Free drops to 250 req/s. Pro and Enterprise limits are unchanged. Retry gracefully on HTTP 429 responses. Later this quarter, per-plan WebSocket connection and subscription session limits take effect (Free: 100/100, Pro: 5,000/2,000, Enterprise: 25,000/5,000). [Read the updated docs](/rpc-nodes/information/throughput). [Create a free API key](https://app.conduit.xyz/). ## July 8, 2026 ## Interactive RPC request builder on the API key page You can now build and send an RPC request straight from your API key page, without copying anything into a terminal first. Pick a method and network inline in the example request, then send it and see the response rendered inline. * **Inline method and network selectors** -- Switch the JSON-RPC method and the target network directly in the curl example; the request URL fills in with your API key appended. * **Send from the dashboard** -- Use the send button to run the request against the selected endpoint and view a syntax-highlighted, expandable JSON response. * **Copy the full command** -- The copy button still copies the complete curl command so you can run it anywhere. ## July 2, 2026 ## Request Count by Method chart and line or stacked chart views Added a Request Count by Method chart to the Nodes Metrics page and a toggle to switch the usage breakdown charts between stacked and line views. ## What's new ### Request Count by Method chart A new chart on the Nodes Metrics page, below Requests, showing request volume broken down by RPC method over time. * **Per-method request counts** -- Visualizes how many requests each RPC method receives as a stacked area chart over your selected time range * **Percent of total** -- The tooltip shows each method's share of total requests for the hovered time interval * **Method filter** -- Use the **Method** dropdown to focus on specific methods, with the total request count updating to reflect the filtered selection ### Line or stacked chart views You can now switch the Request Count by Method, CU Usage by Network, and CU Usage by API Key charts between a stacked area view and a non-stacked line view. Use the toggle button in the chart header. Charts open in the stacked view by default. ### Busiest methods and networks by default The Request Count by Method and CU Usage by Network charts now surface your highest-usage series automatically. * **Sorted by usage** -- The filter dropdowns list methods, networks, and API keys ordered by highest total usage first * **Top 10 preselected** -- When a chart has more than 10 methods or networks, it preselects the 10 busiest so the view stays readable * **Selected share** -- When you filter to specific series, the header shows the selected total as a percentage of the full total ## June 22, 2026 ## CU usage by API key breakdown chart Added a new CU Usage by API Key breakdown chart to the Nodes Metrics page. ## What's new ### CU Usage by API Key Breakdown Chart A new chart on the Nodes Metrics page showing compute unit usage broken down by API keys over time. * **Per-API Key CU usage** -- Visualizes compute unit consumption across all API keys as a stacked area chart over your selected time range * **Zero-usage normalization** -- API keys with no usage on a given day are explicitly represented as `0`, so the chart accurately shows when usage drops to zero rather than hiding gaps * **Filtered tooltips** -- Hovering over a time interval only shows API keys with actual usage, keeping the tooltip clean. A **Total** row at the bottom sums all visible API keys * **API Key filter** -- Use the **API Key** dropdown to filter the chart to specific API keys, with the total CU count updating to reflect the filtered selection ## March 12, 2026 ## CSV metrics export and CU usage by network chart Added CSV export for RPC metrics and a new CU Usage by Network breakdown chart to the Nodes Metrics page. ## What's new ### Export Metrics as CSV You can now export your RPC metrics data directly from the Nodes Metrics page. Click the **Export CSV** button in the filters bar to download a zip containing three CSVs: * **timeseries\_metrics.csv** -- Request counts, success rate, latency percentiles (avg, p90, p95, p99), and compute unit cost per time interval * **network\_usage.csv** -- Compute unit usage broken down by network (e.g. eth-mainnet, arb-mainnet) per time interval * **methods\_breakdown.csv** -- Aggregated request count and compute unit cost per RPC method over the selected time range The export respects your current time range and API key filters. The downloaded zip file is named using the selected filter and API key for easy identification (e.g. `conduit_metrics_LAST_7_DAYS_my-production-key.zip`). ### CU Usage by Network Breakdown Chart A new chart on the Nodes Metrics page showing compute unit usage broken down by network over time. * **Per-network CU usage** -- Visualizes compute unit consumption across all networks (e.g. eth-mainnet, arb-mainnet) as a stacked area chart over your selected time range * **Zero-usage normalization** -- Networks with no usage on a given day are explicitly represented as `0`, so the chart accurately shows when usage drops to zero rather than hiding gaps * **Filtered tooltips** -- Hovering over a time interval only shows networks with actual usage, keeping the tooltip clean. A **Total** row at the bottom sums all visible networks * **Chain filter** -- Use the **Chain** dropdown to filter the chart to specific networks, with the total CU count updating to reflect the filtered selection ## January 7, 2026 ## Rollups renamed to Chains, plus Bundler updates Renamed Rollups to Chains and updated navigation URLs. Added a dedicated Bundler page and new installation flow for Conduit Account Abstraction. ## What's new ### Rollups renamed to Chains Rollups are now called Chains throughout the platform. Updated URLs from `/view-network` to `/chains` for cleaner navigation. ### Account Abstraction updates Added a dedicated Bundler page and a new installation flow for Conduit Account Abstraction. [Learn more about Account Abstraction](/account-abstraction/overview). ## December 10, 2025 ## RPC Nodes rate-limiting changes To improve the reliability and throughput of the RPC product, rate-limiting now works differently. Rate limits are now enforced in Compute Units per second (CU/s). The documentation has been updated to reflect these changes. [Read more here](/rpc-nodes/information/throughput) ## December 9, 2025 ## Tempo Testnet support and app improvements Launched a new chain for RPC Nodes and quality of life and performance improvements to the app. ## What's new ### Added support for Tempo Testnet Added support for Tempo Testnet to the RPC Nodes offering. [Get an API key and start building on Tempo](/rpc-nodes/getting-started/tempo-rpc-quickstart). ### Quality of life improvements * Added quick actions from chain overview to quickly navigate to Access controls, custom domains, and to delete the deployment ### Performance improvements * Updated the app framework to increase speed of navigation * Updated the data visualization library for better graphs and visualization ## November 26, 2025 ## Introducing the Conduit Changelog We're kicking off changelogs and release notes along with our brand new documentation site! #### New Features * New Network Access Control List configuration for RPC keys Restricting an API key to specific networks is now significantly easier. Logic for restrictions has been consolidated into the Access Controls tab, and active networks are now configured through a slide-over sidebar. * New Endpoints pages on Nodes Seeing a quick overview of usage and RPC URLs across all Conduit-supported chains is now easier. The Endpoints page lists all networks in a compact way, with their RPC URL and the selected API key appended for easy copying. Switch between WebSocket and HTTP endpoints at the top of the list. * ACLs for Public RPC for your chain Restrict access to a chain's RPC. This update enables restricting the public RPC to only allowed API keys (e.g., giving early access to beta testers), as well as restricting which addresses are allowed to deploy smart contracts on the chain. Visit our [Conduit Nodes](https://www.conduit.xyz/nodes) page or the [docs page](/rpc-nodes/overview) for more info. #### Updates/Enhancements * Improved latency metrics for RPC performance P95 and P99 measurements have been added on top of the average to the Response time graph. This provides an even better view of performance across RPC usage. #### Upgrades * Fusaka Ready We upgraded all testnets on the Conduit platform as part of our preparation for Ethereum's Fusaka upgrade.