cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-RABBIT-001

Rabbit Finance (RABBIT)

BNB Smart Chain · Token contract · Documentation reviewed

Documentary contract0x95a1199eba84ac5f19546519e287d43d2f0e1b41

The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

The documented promise

Rabbit Finance (RABBIT) is presented as a governance token for the Rabbit Finance protocol on the BNB Smart Chain network. The pinned registry entry claims the asset captures economic benefits of the protocol. This description originates from community submissions to the Trust Wallet Assets repository. Such statements are documentary claims, not independently verified issuer assertions or operational guarantees.

Established facts

The documentary record identifies the asset with symbol RABBIT and address 0x95a1199eba84ac5f19546519e287d43d2f0e1b41 on eip155:56. The integration uses 18 decimal places, which defines amount representation precision but does not measure supply or value. The entry is labeled BEP20, indicating conformity with the ERC-20 interface standard adapted for this network. An allowance allows a named spender to use a specified amount of tokens, subject to approval rules defined in that standard. The Trust Wallet smartchain context confirms this directory serves as a community-maintained registry. Inclusion does not imply partnership, direct verification, or endorsement by the wallet project. The README explicitly excludes brand-new tokens, limiting the inventory scope.

Unknowns

Independent control, beneficial ownership, actual usage, client adoption, total supply distribution, concentration, liquidity depth, and complete incident history remain unverified. No deployed bytecode analysis, current controller identification, or live network observation was performed. The active metadata label lacks live-network validation. Documentary mechanisms alone cannot establish actual network behavior, safety, or investment outcomes.

Consequences

Without independent verification, the stated governance and economic capture aims remain unproven. Users cannot assess risk based on this dossier alone. The absence of audit data, supply transparency, or control documentation prevents any scoring assignment. The unrated status reflects zero coverage across all essential criteria including identity, supply, and control.

Verdict

Operational strength remains unproven. The asset is unrated with 0% scoring coverage. No public admission of security, compliance, or performance exists. The dossier identifies only the documented subject; deployed bytecode, current controllers, and network operation remain unverified. Research must proceed with caution given the lack of independent evidence.

Evidence that would change it

Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required. Calibration and editorial review following such verification could alter the unrated status. Concrete research questions include verifying the deployed contract at 0x95a1199eba84ac5f19546519e287d43d2f0e1b41, confirming controller permissions, assessing supply concentration, and documenting actual usage patterns on BNB Smart Chain.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured BNB Smart Chain record for RABBIT

The pinned Trust Wallet BNB Smart Chain integration record names RABBIT with symbol RABBIT, documentary address 0x95a1199eba84ac5f19546519e287d43d2f0e1b41 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BEP20 and active. Its community-maintained description states: "RABBIT token is a governance token of the Rabbit Finance. It will also capture the economic benefits of the protocol." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 299ce40f60f6c53388854d86fe1fa6d6df9d583d4b62774160039dad985dfa9d

Trust Wallet: pinned BNB Smart Chain directory context

The pinned Trust Wallet smartchain network-context record identifies the community registry directory for BNB Smart Chain. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 9888dd19b8ace07b4a705771770ab5140129ba43ec4ce6e95932dd63af204278

Trust Wallet Assets: README.md (bbe582d25a22)

The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

Ethereum ERC-20: pinned token interface specification

The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation