Contract blueprint · 26 Oct 2026

BNC on Base

0xea7249685da406a37d529c65e29ccf7bf693e874

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

What this means for you

BNC on Base: the code has 1 control switch that can still be used.E6 E5

Mint new tokens: Can create new tokens, which adds to the supply and can dilute holders.E6 E5
An owner wallet is set (0xc7b5cfe1e8dbdcf51ee0a2a78352175e46db2303), so owner-only switches can be used by that wallet.E5
1 functions that change state have no public name, so we can't say what they do.E8

What it is

It's a token called Binance Nasdaq Copper (BNC).E3
Total supply: 1,000,000,000 tokens.E4
Besides the standard token functions it has metadata, increaseAllowance, mint, burn, renounceOwnership, burnFrom, owner, decreaseAllowance and 1 more.E2
We read 20 functions from its public code with REA inspect-evm-interface (in WSL).E2 E1

What the owner can do

Mint new tokens

can be used

Can create new tokens, which adds to the supply and can dilute holders.E6 E5

mint(address,uint256)

Transfer ownership

info

Ownership can be handed to another wallet or given up (renounced).E7 E5

renounceOwnership()transferOwnership(address)

1 state-changing functions have no public name: 0x918b5be1 E8

Chain: Base
Address: 0xea7249685da406a37d529c65e29ccf7bf693e874
Token: Binance Nasdaq Copper (BNC)
Supply: 1,000,000,000 tokens
Owner: 0xc7b5cfe1e8dbdcf51ee0a2a78352175e46db2303
Engine: REA inspect-evm-interface (in WSL)

All 20 functions

name()approve(address,uint256) · nonpayable0x0e9447d5()totalSupply()transferFrom(address,address,uint256) · nonpayabledecimals()metadata()increaseAllowance(address,uint256) · nonpayablemint(address,uint256) · nonpayableburn(uint256) · nonpayablebalanceOf(address)renounceOwnership() · nonpayableburnFrom(address,uint256) · nonpayableowner()0x918b5be1(bytes) · nonpayablesymbol()decreaseAllowance(address,uint256) · nonpayabletransfer(address,uint256) · nonpayableallowance(address,address)transferOwnership(address) · nonpayable

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.

5,150 bytes of contract code on Base

eth_getCode on Base · 0xea7249685da406a37d529c65e29ccf7bf693e874 · sha256 7ff6feb2ee87face…

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

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

Token name/symbol: Binance Nasdaq Copper (BNC)

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

Total supply: 1,000,000,000 tokens

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

owner() returns 0xc7b5cfe1e8dbdcf51ee0a2a78352175e46db2303

eth_call owner() on Base · 0xea7249685da406a37d529c65e29ccf7bf693e874

Owner switch 'Mint new tokens': mint(address,uint256)

Can create new tokens, which adds to the supply and can dilute holders.

Base bytecode 0xea724968… · “mint(address,uint256)” · REA inspect-evm-interface (in WSL)

Owner switch 'Transfer ownership': renounceOwnership(), transferOwnership(address)

Ownership can be handed to another wallet or given up (renounced).

Base bytecode 0xea724968… · “renounceOwnership(), transferOwnership(address)” · REA inspect-evm-interface (in WSL)

1 state-changing function(s) with no public name

Base bytecode · “0x918b5be1” · 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 dacnUND9.