cryptosnif
EVAA (EVAA)
Documentary contract0xaa036928c9c0df07d525b55ea8ee690bb5a628c1
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 evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
The supplied Trust Wallet registry describes EVAA as a governance and utility token for a lending protocol. Governance refers here to the registry's stated voting role, while its description also mentions staking and fee benefits. These statements remain attributed registry claims; none of those token rights or economic outcomes has been independently observed. This dossier examines their documentary scope on BNB Smart Chain.
Established facts
The pinned Trust Wallet BNB Smart Chain integration record identifies Evaa protocol with the symbol EVAA and a documentary address of 0xaa036928c9c0df07d525b55ea8ee690bb5a628c1. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. It labels the entry as BEP20 and active. The community-maintained description states that the $EVAA token is the governance and utility token of the EVAA lending protocol. It claims holders can participate in decentralized governance by voting on protocol upgrades, stake tokens to earn passive income, and enjoy lower fees for platform services. 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 general ERC-20 specification defines a standard interface for fungible tokens in smart contracts, including 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. The pinned Trust Wallet smartchain network-context record identifies the community registry directory for BNB Smart Chain, supplying 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. 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.
Unknowns
Current controllers, beneficial ownership, product use, circulating supply, holder concentration, liquidity and the completeness of incident history remain unverified. The supplied material also contains no independent observation of voting, staking or the described fee benefits. Those are research questions for further review, and no operational criterion has been independently admitted.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The active status is a metadata label, with no live-network validation. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. Inclusion in the registry does not imply a direct partnership with the listed projects. The general ERC-20 specification is separate from this token implementation. Operational strength remains unproven; unrated with 0% scoring coverage.
Verdict
EVAA remains unrated with 0% scoring coverage. Its wallet identity and attributed lending description provide a documentary starting point. The described governance and utility roles still need independent verification, and a numerical score would require reviewed criterion observations and calibration.
What would change it
Reproduced identity checks, independent dated network observations and criterion-specific evidence, followed by calibration and editorial review, would be required to move beyond this documentary assessment. Concrete research questions include verifying the deployed bytecode against the documentary address, identifying current controllers through on-chain data, observing actual usage patterns, checking supply distribution for concentration risks, and confirming whether any security audits have been completed. Without these independent verifications, the registry claims remain unverified promotional statements rather than established operational facts.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured BNB Smart Chain record for Evaa protocol
The pinned Trust Wallet BNB Smart Chain integration record names Evaa protocol with symbol EVAA, documentary address 0xaa036928c9c0df07d525b55ea8ee690bb5a628c1 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: "The $EVAA token is the governance and utility token of the EVAA lending protocol. It allows holders to participate in decentralized governance by voting on protocol upgrades, stake their tokens to earn passive income, and enjoy lower fees for platform services." 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.
Inspect the primary source ↗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.
Inspect the primary source ↗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.
Inspect the primary source ↗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.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.