Contract blueprint · 6 h ago

UFDT on Base

0x88b9733e274ba0c81fb6638348d9e14a13ce459a

Template-written 5 evidence items REA inspect-evm-interface (in WSL)

What this means for you

UFDT on Base: no owner switches found among its 13 functions.E2 E5

The contract has no owner() function, so there's no single owner wallet to check.E5

What it is

It's a token called United Fund Dividend Trust 🔥 (UFDT).E3
Total supply: 100,000,000,000 tokens.E4
Besides the standard token functions it has DOMAIN_SEPARATOR, nonces, eip712Domain and permit.E2
We read 13 functions from its public code with REA inspect-evm-interface (in WSL).E2 E1

What the owner can do

No functions match known owner powers (mint, pause, block wallets, change fees or limits, open/close trading, replace the code).E2

Chain: Base
Address: 0x88b9733e274ba0c81fb6638348d9e14a13ce459a
Token: United Fund Dividend Trust 🔥 (UFDT)
Supply: 100,000,000,000 tokens
Owner: no owner() function
Engine: REA inspect-evm-interface (in WSL)

All 13 functions

name()approve(address,uint256) · nonpayabletotalSupply()transferFrom(address,address,uint256) · nonpayabledecimals()DOMAIN_SEPARATOR()balanceOf(address)nonces(address)eip712Domain()symbol()transfer(address,uint256) · nonpayablepermit(address,address,uint256,uint256,uint8,bytes32,bytes32) · nonpayableallowance(address,address)

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

6,997 bytes of contract code on Base

eth_getCode on Base · 0x88b9733e274ba0c81fb6638348d9e14a13ce459a · sha256 4e3240d43381ba08…

13 functions extracted with REA inspect-evm-interface (in WSL)

Base bytecode 0x88b9733e… · “13 selectors” · REA inspect-evm-interface (in WSL)

Token name/symbol: United Fund Dividend Trust 🔥 (UFDT)

eth_call name() / symbol() on Base · 0x88b9733e274ba0c81fb6638348d9e14a13ce459a

Total supply: 100,000,000,000 tokens

eth_call totalSupply() / decimals() on Base · 0x88b9733e274ba0c81fb6638348d9e14a13ce459a

No owner() function in the contract

Base bytecode · “no 0x8da5cb5b selector” · REA inspect-evm-interface (in WSL)

Limits

Powers are read from the contract's function list. A power hidden behind an unnamed function can't be explained, only counted.
Who holds a power is only checked through owner(). Roles, multisigs and proxy admins may hold powers too.
This describes what the code allows, not what anyone will do. It isn't financial advice.
This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id MqO3ooxM.