Cardano Node Opens Built-In UTxO RPC to Developers

cardano-node can now serve structured blockchain data through an integrated gRPC interface called cardano-rpc. Developers can retrieve UTxOs, evaluate and submit transactions, and receive live block and rollback updates from the node process itself.

The interface has been developing inside the node since version 10.7.0. Documentation published on September 17 includes quickstart examples for Go, Haskell, Python, Rust and TypeScript. The current setup with gRPC reflection requires a node built from the master branch at commit e95d55e or later.

Cardano Node Streams Typed Chain Data

cardano-rpc is disabled by default and can be activated through the node configuration.

Its query functions return protocol parameters, UTxO records, genesis information and era summaries. Submit functions accept and evaluate transactions, while synchronization services provide the current chain tip and individual blocks.

The FollowTip method maintains a live connection with the node, delivering fully parsed blocks as the chain advances. The stream includes rollbacks, allowing applications to update their local state when Cardano selects a different valid continuation of the chain.

Connections can run through a local Unix socket or use TCP with TLS. The server also supports gRPC reflection, allowing standard tools such as grpcurl and grpcui to discover and call available services.

Why UTxO RPC Matters for Cardano

Application backends often use an additional process to convert data from Cardano’s node-to-client protocols into formats suitable for wallets, exchanges and decentralized applications.

The built-in RPC layer moves part of that work into the node. A backend can use a typed protobuf interface to read chain state, evaluate ADA transactions and submit them without maintaining a custom adapter for basic node operations.

cardano-rpc implements the open UTxO RPC specification created through TxPipe’s Catalyst Fund 11 work. The same interface is supported by infrastructure associated with Dolos, Blink Labs and Demeter, allowing compatible client code to connect to different servers.

The implementation is built on cardano-api, which handles Cardano eras, CBOR data, ledger queries and transaction processing. Protocol changes introduced through future hard forks must therefore be reflected in the RPC layer during node development, reducing the risk of external integrations lagging behind a new era.

For infrastructure operators, the integration can remove one process from deployments that currently use a separate bridge. Development teams gain a shared interface for services working with ADA and Cardano native tokens.

SDK and Indexing Limits Remain

The RPC interface does not replace every existing infrastructure component. Ogmios uses JSON-RPC rather than UTxO RPC, so migration requires client changes. Kupo and other indexers remain necessary for searches that depend on additional indexes covering credentials, assets or historical activity.

SDK compatibility is also incomplete. Published providers for MeshJS and Lucid Evolution still depend on older packages exposing the previous v1alpha API. Support for the new interface has been merged into the UTxO RPC specification, but the corresponding package release remains pending. Direct quickstarts and standard gRPC tools provide the current access route. UTxO RPC specification update

No production performance benchmarks accompanied the announcement, and existing Ogmios, Kupo and indexer deployments remain supported.

The immediate change is operational: cardano-node can now stream parsed blocks and rollbacks, answer ledger queries, and evaluate and accept transactions through one typed interface. The next expansion point is the SDK layer, where updated UTxO RPC packages will determine how quickly this access reaches regular Cardano application development.