Contract blueprint · 23 h ago

佩佩 on BNB Chain

0x4ca1c59d5a5472edc11047d69495fb8063ceea80

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

What this means for you

佩佩 on BNB Chain: no owner switches found among its 14 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 佩佩 (佩佩).E3
Total supply: 1,000,000,000 tokens.E4
Besides the standard token functions it has increaseAllowance and decreaseAllowance.E2
We read 14 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: BNB Chain
Address: 0x4ca1c59d5a5472edc11047d69495fb8063ceea80
Token: 佩佩 (佩佩)
Supply: 1,000,000,000 tokens
Owner: no owner() function
Engine: REA inspect-evm-interface (in WSL)

All 14 functions

name()approve(address,uint256) · nonpayabletotalSupply()transferFrom(address,address,uint256) · nonpayabledecimals()increaseAllowance(address,uint256) · nonpayablebalanceOf(address)symbol()decreaseAllowance(address,uint256) · nonpayabletransfer(address,uint256) · nonpayable0xb3bcfa82()0xb7dd2623()allowance(address,address)0xe25f7597()

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.

2,663 bytes of contract code on BNB Chain

eth_getCode on BNB Chain · 0x4ca1c59d5a5472edc11047d69495fb8063ceea80 · sha256 b6f970149caa5995…

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

BNB Chain bytecode 0x4ca1c59d… · “14 selectors” · REA inspect-evm-interface (in WSL)

Token name/symbol: 佩佩 (佩佩)

eth_call name() / symbol() on BNB Chain · 0x4ca1c59d5a5472edc11047d69495fb8063ceea80

Total supply: 1,000,000,000 tokens

eth_call totalSupply() / decimals() on BNB Chain · 0x4ca1c59d5a5472edc11047d69495fb8063ceea80

No owner() function in the contract

BNB Chain 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 Sute5bfs.