Contract blueprint · 27 Oct 2026
SEALS AS 2028 on Base
0x181af73baf6568cfe730e4fc0c545b559cd17af3
What it is
What the owner can do
No functions match known owner controls (mint, pause, block wallets, change fees or limits, open/close trading, replace the code).E2
- Chain
- Base
- Address
- 0x181af73baf6568cfe730e4fc0c545b559cd17af3
- Token
- Save The Seals 2028 (SEALS AS 2028)
- Supply
- 1,000,000,000 tokens
- Owner
- no owner() function
- Engine
- REA inspect-evm-interface (in WSL)
All 0 functions
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.
E1
44 bytes of contract code on Base
eth_getCode on Base · 0x181af73baf6568cfe730e4fc0c545b559cd17af3 · sha256 0ab4a12f1ce0cdb7…
E2
0 functions extracted with REA inspect-evm-interface (in WSL)
Base bytecode 0x181af73b… · “0 selectors” · REA inspect-evm-interface (in WSL)
E3
Token name/symbol: Save The Seals 2028 (SEALS AS 2028)
eth_call name() / symbol() on Base · 0x181af73baf6568cfe730e4fc0c545b559cd17af3
E4
Total supply: 1,000,000,000 tokens
eth_call totalSupply() / decimals() on Base · 0x181af73baf6568cfe730e4fc0c545b559cd17af3
E5
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 zi1IXXX9.