Uniswap Labs introduced TJAR on October 29, a framework that allows applications to convert fees collected in multiple cryptocurrencies into one selected token. The launch was announced in a post on X. By eliminating the need for separate conversion infrastructure across different assets and networks, the system streamlines fee handling for developers. The framework has now been deployed across seven networks, with additional chains planned, and it already processed more than $15.3 million in conversions last month.

Searchers Compete to Convert Accumulated Fees

The Token Jar framework lets applications accumulate fees denominated in different cryptocurrencies before converting them into a preferred asset. Developers select their payout token, set a conversion threshold, and specify where the proceeds should be delivered.

Searchers then compete to carry out these conversions by supplying the required amount of the selected token. In return, they receive the accumulated assets held inside the Token Jar, while the chosen token is sent to the destination configured by the application. Because execution is handed to competing searchers, operators do not have to route trades or time conversions themselves; the competitive process determines who fills each order.

Those destinations can include company treasuries, burn addresses, or bridges to other networks. Operators are free to adjust conversion thresholds and destinations whenever necessary, or they can lock these settings permanently.

Uniswap originally developed TJAR to power its own protocol fee conversion and UNI burning mechanism. The framework has since grown into reusable infrastructure serving other applications, hooks, chains, and API integrations, turning an internal tool into shared onchain plumbing for other teams.

Robinhood Adopts TJAR Through the Uniswap API

Robinhood already relies on TJAR for fees collected through the Uniswap API. Its integration converts incoming fees into USDC and USDG across the supported chains, meaning the platform receives payouts in two stablecoins rather than a mix of fee assets.

The Token Jar and Releaser contracts use deterministic deployment, which allows operators to maintain identical addresses on every supported network. OpenZeppelin has audited the framework, and anyone can create a Token Jar through the TJAR Factory in a single transaction.

Conversion Thresholds Determine When Execution Occurs

TJAR applies a fixed release threshold that governs when searchers can collect the assets accumulated in a jar. The jar's value, however, changes continuously as deposits arrive and cryptocurrency prices fluctuate.

According to Uniswap's documentation, lower thresholds generally allow more frequent conversions but increase sensitivity to individual deposits. Higher thresholds reduce that sensitivity, although the assets remain exposed to market movements for longer periods.

Operators can therefore tune their configurations as fee volumes and deposit patterns evolve, weighing more frequent execution against prolonged exposure to price swings. With additional networks planned and adoption already flowing through the Uniswap API, the new deployments, integrations, and threshold configurations that follow are the details to track as TJAR expands.