Uniswap opens TJAR to apps for converting fees into a chosen token

A shared container for scattered fees

On October 29, 2026, Uniswap Labs introduced TJAR, infrastructure that lets applications pool fees received in different assets and collect a chosen token instead. A technical explanation published the following day details how it works. It addresses scattered revenue: an app may accumulate multiple tokens through user activity while its treasury wants to hold just one. TJAR provides a shared conversion mechanism rather than requiring each team to build its own system.

The system relies on two contracts with different roles. The first, called the Token Jar, receives assets. The second defines the terms on which those assets can be obtained in exchange for the token selected by the operator. The final destination is configurable: it may be a treasury or another route specified by the application. This architecture repurposes infrastructure originally designed for Uniswap protocol fees, making it reusable by other teams without mixing their revenue with that of the original protocol.

A fixed price for contents that change

External operators monitor the contracts' contents. When they find an exchange attractive, they supply the requested quantity of the chosen token and collect the accumulated assets. Their motivation is economic: the value received must cover the amount supplied and the transaction cost. Conversion therefore depends on more than fees arriving. A participant must find it worthwhile to carry out the exchange under the available terms when observing the contract.

The release threshold is central. A low amount can speed up conversions but makes the mechanism sensitive to a large deposit arriving all at once. Conversely, a high threshold can leave assets in the contract longer, extending their exposure to price changes. The technical document does not offer a universal setting. The operator, or an authorized manager, must adapt parameters to the pace of revenue and the usual size of incoming amounts.

A stated use case at Robinhood

Uniswap Labs says Robinhood already uses this system for fees generated through its API, with contracts configured to receive USDC and USDG. This describes a specific use case; it does not mean all Robinhood activities depend on TJAR. The launch also announces availability across multiple blockchains. Teams considering integration still need to check the relevant deployment documentation for addresses and networks actually supported.

The owner retains powers to change settings, including the token, threshold and destination, unless those powers are renounced. These rights are part of the system to examine alongside its code. Open, audited infrastructure guarantees neither instant conversion nor additional yield. Its contribution is to organize a market for revenue already collected, with a visible trade-off between exchange frequency, intervention costs and exposure of assets awaiting conversion.