cryptosnif
Kendu Inu (Kendu)
Documentary contract0xaa95f26e30001251fb905d264aa7b00ee9df6c18
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
This dossier examines the documented purpose and mechanisms of Kendu Inu (Kendu) on the Ethereum network. The goal is to explain the stated aims and technical context provided in the registry records, without implying that an independent audit or operational verification has occurred.
Established facts
The Trust Wallet Ethereum integration record identifies Kendu Inu with the symbol KENDU at contract address 0xaa95f26e30001251fb905d264aa7b00ee9df6c18. The record specifies 18 decimal places, a standard for amount representation that does not measure supply or value. The entry is labeled ERC20 and active within the community-maintained registry. The registry description states the project aims to unite six native Japanese dog breeds, positioning Kendu as a keeper of peace and protector of unity. These statements are attributed registry claims, not independently established issuer assertions. The underlying network is identified as Ethereum, which provides the blockchain context for this token record. The general ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount of tokens, with repeated approvals overwriting previous amounts. This specification outlines what a conforming implementation should do, but the wallet label establishes no independently checked compliance or actual deployed implementation status for this specific contract.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, total supply distribution, concentration of holdings, liquidity depth, and complete incident history remain unverified. No live network observation was performed to confirm bytecode behavior or current controller permissions. The registry scope notes that inclusion does not imply a direct partnership with listed projects and that additional token information is optional and unavailable on-chain. Consequently, the economic niche and scoring criteria for this asset remain unclassified.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Without independent verification of deployment, control, and usage, the stated purpose remains a descriptive claim rather than an operational reality. Users relying solely on registry labels cannot assume security, liquidity, or functional correctness based on the presence of the token in the wallet database.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. No public admission of operational status or independent audit results exists. The dossier serves as a documentary explanation of registry data only.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move from an unrated status to a scored assessment. Calibration and editorial review following such verification would determine if the token meets defined operational and security criteria.
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 Ethereum record for Kendu Inu
The pinned Trust Wallet Ethereum integration record names Kendu Inu with symbol KENDU, contract 0xaa95f26e30001251fb905d264aa7b00ee9df6c18 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "Uniting the six native Japanese dog breeds. Kendu is the keeper of peace, the preserver of life, and the protector of unity. Join the pack!" 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. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. 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 ↗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.