rippled adds a subscribe stream for transactions touching chosen MPTs
Victoria Shinder2 min readA change that lets XRP Ledger clients subscribe to transactions affecting particular Multi-Purpose Tokens has been merged into rippled's development branch. Pull request 5671, opened in August 2025 by Shawn Xie, was merged on 2 October 2026.
What changes in the API. The subscribe WebSocket method gains an optional mpt_issuances field: an array of unique MPT issuance IDs. Once a client subscribes, the server sends a message of type mptTransaction whenever a validated transaction affects at least one of the listed tokens. unsubscribe accepts the same field to stop those messages. The pull request is explicit about one limit: unsubscribing only cancels a subscription made for those specific MPTs, and cannot be used to filter MPT activity out of the general transaction stream.
The stated purpose is to spare clients the work of client-side filtering. Until now, an application watching a token — an issuer tracking its own MPT, a wallet showing balances, an indexer — had to subscribe to a broad stream and discard everything irrelevant, or subscribe per account. With the new field the node does the matching.
Context. Multi-Purpose Tokens are the XRP Ledger's newer token standard, designed for fungible tokens with issuer controls such as transfer fees and authorisation, alongside the older trust-line tokens. The development branch is busy with them: the same day, rippled maintainers also merged a change implementing holder key updates for confidential MPTs, a fix so that unrelated confidential balances no longer block deleting an MPToken, and a change enabling the larger number mantissa together with the MPTokensV2 amendment.
Being merged into develop is not the same as shipping. The feature will reach node operators in a future rippled release, and API users will only see it on servers running that version. Client libraries such as xrpl.js and xrpl-py will also need to expose the new field and message type.
What it means
For teams building on MPTs, this removes a piece of plumbing they would otherwise write and run themselves. It is worth planning integrations around it now, but checking a server's version before relying on it, because public nodes will upgrade at different times.