How we read a contract, and how the score is built
Nothing in Tibyar is a matter of taste: every point in the score has a declared source and a fixed weight. This is the whole method.
The source
The contract's public security data, read as it stands and not interpreted. The network is inferred from the shape of the address, and an explorer link gives us both at once.
One shape
Solana's fields are mapped onto the same shape: a transfer block reads as a honeypot, a freeze authority as pausable transfers. One scan, every supported network.
Caps and floors
Points are summed and capped at one hundred, and the fatal flags carry a floor: a honeypot cannot score below ninety, and a balance you cannot sell in full cannot score below eighty.
The full rubric · weights from heaviest to lightest
18 weighted signals, printed from the same table the scorer adds up. Each bar is that weight against the heaviest one (40 points).
Supported networks
Contract data read from public on-chain sources — and from a TON indexer on TON
BNB Smart ChainBEP20
EthereumERC20
BaseERC20
SolanaSPL
TRONTRC20
TONJettonAnd 15 more EVM networks you pick by hand — 21 in all. The first three are swept automatically when a 0x address could belong to any of them, and Solana, TRON and TON are read from the address itself.
Score bands
The band judges the data, not the project: a contract that is clean technically can still be a failing venture, and the reverse does not hold.
Unknown is not safe
Every field the data does not return is recorded as unknown and lowers the coverage figure. Below 50% coverage the report says so at the top of the page, before any number.
Open a full report