cryptosnif
Basenji (BENJI)
Documentary contract0xbc45647ea894030a4e9801ec03479739fa2485f0
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 Basenji (BENJI) on the eip155:8453 network. The objective is to evaluate the identity basenji-wallet-base against available documentary records. We assess whether the pinned registry entries establish a verifiable operational framework or remain unverified claims.
Established facts
The Trust Wallet Assets registry contains a pinned entry for Basenji with the symbol BENJI. This record specifies the documentary contract address 0xbc45647ea894030a4e9801ec03479739fa2485f0 and defines eighteen decimal places for amount representation. Decimal places concern how numbers are displayed and do not measure total supply or market value. The registry labels this entry as active within the BASE network context. The community-maintained description notes that the contract is deployed on the Base chain and references a Basescan link. It also includes a user comment about inputting the Base chain as Ethereum due to interface limitations. 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 ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It requires functions for reading total supply and balances, executing transfers, and managing allowances. 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 Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains. It states that 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 explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The general ERC-20 specification is separate from this token implementation.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history remain unverified. The dossier identifies only the documented subject; deployed bytecode, current controllers and network operation remain unverified. Documentary address matching establishes no current program behavior, deployed control or safety. No live network observation was performed. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent verification means that promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established. The status is unrated with zero percent scoring coverage. No public admission of operational strength exists.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. The evidence provided consists solely of community-submitted registry data and standard interface definitions. These sources do not constitute an independent operational verification. The project claims regarding its specific utility and deployment details are scoped as unverified registry claims. Without independent dated network observations, the dossier cannot assign a score or confirm the token's functional reality beyond its listing in the wallet asset directory.
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 alter this verdict. Verification of deployed bytecode against the stated address, confirmation of active controllers, and observation of actual token transactions on the eip155:8453 network would establish operational reality. Independent audits confirming security posture and clear documentation of governance structures would reduce the current uncertainty surrounding control and accountability.
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 Base record for Basenji
The pinned Trust Wallet Base integration record names Basenji with symbol BENJI, documentary address 0xbc45647ea894030a4e9801ec03479739fa2485f0 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BASE and active. Its community-maintained description states: "The contract is deployed on Base chain. I can't find any option to input Base chain so i input it as Ethereum. Hope this is ok. Thanks. basescan link: https://basescan.org/token/0xbc45647ea894030a4e9801ec03479739fa2485f0" 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 Base directory context
The pinned Trust Wallet base network-context record identifies the community registry directory for Base. 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.