Contract Ecosystem
The UFG ecosystem consists of a fixed-supply token, two treasuries, a factory for other coins' treasuries, and a revenue system. Most contracts are on Robinhood Chain (chain ID 4663). The sfrxETH funding helper runs on Ethereum.
Treasury v1 and Treasury v2 have fixed rules, no upgrade path and no pause switch. The revenue system has different controls: its splitter is upgradeable through a seven-day timelock, and its operators can pause settlement. Those powers do not extend to assets already held by either $UFG treasury
How the contracts connect
$UFG's own creator fees go directly from the Pons fee escrow to Treasury v1. Coins using the UFG factory have a separate path: each coin's router divides its creator fees between that coin's treasury and UFG's platform revenue.
The 50/50 split is the splitter's deployed allocation of incoming assets. Conversion and bridge costs affect what reaches each destination. These steps require separate transactions; revenue at the splitter or in transit is not yet backing in Treasury v2.
$UFG and its treasuries
$UFG coin
Fixed-supply ERC-20 token launched through Pons V2.
Treasury v2
Holds sfrxETH, supports redemption through both treasuries, and lends against $UFG collateral.
Pons minted 1,000,000,000 $UFG at launch. There is no mint function after launch. Tokens sent to the dead address, 0x000000000000000000000000000000000000dEaD, leave the effective supply used by the treasuries.
Treasury v1
v1 holds ETH and claims $UFG's creator fees from the Pons escrow. Anyone can call collect() to claim credited fees. A holder calls redeem(amount, minOut, to) to burn $UFG and receive its pro-rata share of the ETH, less a 2% exit fee retained in v1. Anyone can call burnStray() to burn $UFG sent to v1 by mistake.
Read-only functions include treasury(), effectiveSupply(), backing() and quoteRedeem(amount). The admin had one power: bind the token once. That step ran at launch on August 30, 2026, leaving no ongoing administrative power.
See Treasury v1 for its accounting and redemption rules.
Treasury v2
v2 holds Frax's sfrxETH token on Robinhood Chain. A redemption through v2 burns $UFG once and pays both v1's ETH payout, after v1's 2% fee, and 85% of the holder's share of v2's assets as sfrxETH. The other 15% stays in v2. If either payout fails, including because v2 lacks liquid sfrxETH, the whole transaction reverts.
Holders can also post $UFG as collateral and borrow sfrxETH. v2's asset accounting includes held sfrxETH plus outstanding loan principal. Its supply calculation excludes the permanently locked $UFG in the Pons launch locker; v1's calculation includes those tokens.
v2 has no owner or configuration role. Its reserve token, v1 connection and loan parameters are fixed. See Treasury v2 for the borrowing and liquidation rules.
UFG factory
The factory was deployed on October 27, 2026. It gives a qualifying Pons coin its own UFGLaunchFeeRouter and UFGLaunchTreasury. The factory's launches(token) record identifies the contracts for each coin.
The router claims creator fees, reserves UFG's platform share and sends the remainder to that coin's treasury. Anyone can trigger the release of accumulated platform fees to the revenue splitter. Each coin's reserve stays separate from $UFG's reserves.
The platform share is a fixed fraction of creator fees, calculated for a target of 0.03% of trading volume under the coin's standard fee terms. Special launch taxes and conversion price impact can change the effective percentage of volume. Redemption fees remain in the coin's own treasury.
The factory, routers and launch treasuries have no owner or upgrade path. The splitter they pay has its own governance, described below.
Revenue and governance
The revenue module was deployed on October 17, 2026. Its splitter allocates 50% of each incoming asset to corporate and 50% to Treasury v2 funding. The configured corporate payment is USDG to the Corporate Safe; the treasury payment is ETH to the funding collector.
Revenue splitter proxy
Receives revenue and keeps each destination's allocation. Use this address to interact with the splitter.
Revenue converter
Converts allocated assets through configured routes.
Revenue governance
Handles proposals, execution and controller/guardian roles.
ProxyAdmin
Owned by the timelock; performs splitter upgrades.
The splitter's deployed implementation is 0xB47A1fA3dBbf00e58F05b031cFa13db4d731Ae3B. It supplies the code behind the proxy; it is not the revenue receiving address.
Anyone can trigger settlement when the input already matches the destination asset. A payment requiring conversion needs an authorized keeper. The converter uses configured routes, amount limits and minimum outputs; routes can also use Chainlink-based price floors. Deployment of a route does not by itself activate it.
Controller
Proposes changes; can cancel proposals, pause activity and remove keepers.
Guardian
Can cancel proposals, pause or unpause activity and remove keepers. Cannot choose destinations or propose upgrades.
Timelock
Applies approved changes after seven days, including destinations, routes, keepers, converters and splitter upgrades. Anyone can execute a matured proposal through the governance contract.
Keeper
Triggers conversions within configured rules. Cannot choose a different recipient or route.
The revenue module's recorded Safe addresses are:
The revenue split is not immutable. The deployed implementation has no percentage setter, but an upgrade can change its rules, including allocations and destinations. The delay provides time to inspect a proposal, and the guardian can cancel it. These controls govern revenue still in the revenue system; they cannot withdraw assets from Treasury v1, Treasury v2 or a factory coin's treasury.
Treasury v2 funding
Anyone can call the collector's sendBatch() when its minimum and pause conditions allow. The selected route moves ETH to the helper on Ethereum. The helper's public process() function mints sfrxETH and sends it through Frax's bridge to Treasury v2. Only the sfrxETH that arrives becomes v2 backing.
The collector has separate controller and guardian roles. A new route requires a seven-day delay. Either role can pause new batches for 30 days at a time or switch immediately to the fixed fallback route. Changing a route can change the path of future funding; it gives no control over assets already in v2.
The deployed routes and helper have fixed destinations. The helper has no owner, upgrade or general rescue function. A failure in its external dependencies can leave funds there unable to complete the journey.
External dependencies
Launch records and validation of coins using the UFG factory.
Creator fees claimed by Treasury v1 and factory fee routers.
Permanently locked tokens excluded from v2 and factory treasury supply calculations.
Market trading and revenue conversion routes.
Treasury v2's reserve asset; its token contract is upgradeable by Frax.
USDG and supported quote assets
Corporate payments and assets received as platform revenue.
Chainlink-compatible feeds
Reference prices for configured revenue routes.
Across, the canonical bridge and Frax's minting and bridging contracts
Moving revenue between chains and delivering sfrxETH to v2.
UFG does not control these external systems. Fixed treasury code does not remove token issuer, bridge, liquidity or chain risks. See Risks and the Treasury v2 disclosures.
Last updated
Was this helpful?