The supplied address is UMA’s UMA Voting Token v1, not an oracle contract. Polymarket’s own help center says its markets are resolved by UMA’s Optimistic Oracle, and Polymarket’s separate adapter repository describes that oracle-to-market-resolution path. That supports an UMA oracle relationship, but does not make the token contract itself the oracle. Token contract on Etherscan · Polymarket resolution explainer · UMA adapter source

$UMAEtherFiEthenaOct 6, 2026, 22:31 UTC

The supplied address is UMA’s UMA Voting Token v1, not an oracle contract. Polymarket’s own help center says its markets are resolved by UMA’s Optimistic Oracle, and Polymarket’s separate adapter repository describes that oracle-to-market-resolution path. That supports an UMA oracle relationship, but does not make the token contract itself the oracle. Token contract on Etherscan · Polymarket resolution explainer · UMA adapter source

Polymarket announced V2 canary markets for October 5–30, with new markets tentatively switching on November 2. Its migration overview describes new position, trading and resolution contracts, but the cited V2 materials do not specify whether V2 uses the existing UMA adapter. The linked post’s UMA contract address therefore identifies the token, not the documented resolution integration. V2 announcement · V2 migration overview

The EtherFi–Ethena stablecoin announcement is a separate story: EtherFi announced ether.fi USD powered by Ethena Whitelabel, with Ethena handling reserves, minting, redemptions and compliance. It does not establish a connection to UMA. EtherFi announcement · Ethena announcement

The supplied evidence does not establish whether the existing UMA adapter is used by Polymarket V2.

Ask your own

Case file

$UMAUMA Voting Token v1, ethereum, 0x04fa…f828

EtherFi

Ethena

Answered Oct 6, 2026, 22:31 UTC

Sources 7

Token contract on Etherscanetherscan.io
Polymarket resolution explainerhelp.polymarket.com
UMA adapter sourcegithub.com
V2 announcementx.com
V2 migration overviewdocs.polymarket.com
EtherFi announcementx.com
Ethena announcementx.com

Research trace 26

Who owns 0x04fa…f828
Latest posts of @ether_fi
Latest posts of @ethena
The supplied material is about EtherFi’s stablecoin partnership, but the resolved UMA subject is a Polymarket oracle claim in the quoted post. Check what Polymarket has announced about its V2 migration since the stated trial and mainnet dates, and whether UMA or its oracle has a documented role.
The X search and news-wire checks did not confirm Polymarket V2 or its claimed UMA oracle role. Check Polymarket’s own account posts and UMA’s account posts for a direct announcement.
UMA's own account confirms its Optimistic Oracle still serves prediction markets, including Polymarket, but the quoted post describes a new protocol architecture. Check the linked announcement directly and look for the claimed UMA contract or integration details in its source.
Polymarket’s developers confirm the V2 canary and tentative November 2 switch, but the claim that this UMA contract is integrated as an oracle remains unverified. Check the linked migration documentation for the named oracle and contract role.
The V2 migration overview confirms new position, trading and resolution contracts but does not identify UMA as the oracle. Check Polymarket’s technical blog and repository references for whether this exact UMA token contract is used by V2 or the quoted post confuses the oracle address with the UMA token address.
The V2 migration overview documents new resolution contracts, while the quoted address is UMA’s voting-token contract. Check Polymarket’s UMA adapter documentation and the token’s metadata to distinguish the token from the oracle integration.
The address is UMA’s voting token, and Polymarket’s materials identify a separate UMA CTF Adapter for market resolution. Check the adapter’s contract repository and deployment references to see whether V2’s resolution path uses it, and distinguish that from the token address quoted in the post.
Polymarket’s V2 documentation confirms a new position system, while its UMA adapter repository describes UMA’s oracle integration with the older Conditional Tokens Framework. Check the official V2 contract list and migration details for any stated UMA adapter or oracle connection.
Polymarket’s V2 docs describe new resolution contracts, while the existing UMA adapter repository ties UMA resolution to Conditional Tokens. Check the official V2 contract list and any announcement follow-up to establish whether V2 names UMA or its adapter.
Polymarket’s V2 materials and adapter repository have not established whether V2 keeps using UMA for resolution. Check Polymarket’s own V2 technical announcement and current contract documentation for an explicit oracle or adapter reference.
Polymarket’s materials say UMA handles market resolution, but the supplied Ethereum address is specifically UMA’s voting-token contract. Check recent transfers of that token to see whether they support a direct V2 integration claim.
The supplied address is UMA’s voting token, while UMA market resolution runs through its oracle adapter. Read the token’s recent transfer logs in the requested window to see whether on-chain activity supports a direct V2 integration claim.
The UMA token contract itself is distinct from UMA’s oracle adapter, and Polymarket’s docs say UMA resolves markets. Check UMA’s request explorer for activity around the V2 canary launch to see whether recent oracle use supports the quoted integration claim.
UMA’s docs and Polymarket’s adapter repository establish UMA as a resolution provider, but the V2 change may have a different module or adapter path. Read the V2 technical announcement and repository source for explicit resolution-oracle details.
The V2 migration is underway, but the exact UMA role remains unclear: the cited Ethereum address is UMA’s voting token, while UMA resolution uses a separate adapter. Check Polymarket’s V2 resolution documentation and a direct recent announcement for whether V2 still uses UMA.
Polymarket’s V2 migration and adapter evidence so far confirms a new trading/position system and a separate UMA-based resolution adapter for CTF. Check contract and deployment documentation for whether the V2 rollout explicitly keeps that adapter or points to another oracle.
The evidence confirms Polymarket uses UMA’s Optimistic Oracle for market resolution, while the cited Ethereum address is UMA’s voting token. The remaining question is whether V2’s resolution path is explicitly connected to the existing UMA adapter; the V2 announcement and migration notes identify new trading and position contracts but do not name an oracle.
The supplied UMA address is its voting token, while UMA’s Optimistic Oracle is the market-resolution service. Check the official V2 announcement and migration material for any direct statement that V2 uses UMA or its adapter, so the token-address claim can be distinguished from the broader oracle relationship.
The supplied UMA address is its voting token, and the evidence so far links UMA’s Optimistic Oracle to Polymarket resolution through a separate adapter. Check the V2 announcement’s linked technical article and current V2 position documentation for any explicit change to that oracle path.
The V2 materials confirm new position and resolution contracts but still do not say whether the existing UMA adapter serves V2 markets. Check Polymarket’s live V2 contract-address documentation and the adapter’s published deployments for a direct connection.
The prior findings establish that UMA’s Optimistic Oracle resolves Polymarket markets through a separate adapter, while V2 introduces a new position system. Check official V2 materials for a direct link between that adapter and V2.
The earlier findings show that Polymarket V2 has new position and resolution contracts, while UMA’s existing adapter resolves CTF markets. Check whether V2’s live documentation or published source explicitly links its resolution path to UMA, and distinguish the oracle service from the supplied UMA voting-token address.
The prior findings distinguish UMA’s voting-token contract from its Optimistic Oracle and adapter, but do not establish a direct V2 link. The available prior evidence is sufficient to identify the address mismatch and report the verified connection without treating the token contract as the oracle.