cryptosnif
Bluzelle (BLZ)
Documentary contract0x5732046a883704404f284ce41ffadd5b007fd668
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.
The documented promise
This dossier examines Bluzelle (BLZ) as identified in the Trust Wallet Ethereum integration record. The stated purpose is to provide a documentary explanation of the token's identity and its associated registry claims. This review does not constitute an independent audit, nor does it verify current network operation, controller access, or investment outcomes. The scope is limited to the provided source summaries and their exact code versions.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Bluzelle Token with the symbol BLZ and contract address 0x5732046a883704404f284ce41ffadd5b007fd668. The record specifies 18 decimal places for amount representation. Decimal places concern how amounts are displayed and do not measure total supply or monetary value. The entry is labeled ERC20 and active within the repository. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It outlines functions for reading total supply and balances, executing transfers, and managing allowances. An allowance permits a named spender to use a specified amount of tokens on behalf of the owner. Repeated approvals overwrite previous allowance amounts. The specification requires handling false transfer results and emits Transfer and Approval events. Name, symbol, and decimal metadata are optional under this standard. The wallet project describes its assets repository as a community-maintained registry used by the wallet and other projects. Inclusion does not imply a direct partnership with listed projects. The registry explicitly excludes brand-new tokens from submissions. The network context identifies Ethereum, symbol ETH, as the accompanying blockchain environment. 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.
Unknowns and limitations
No deployed implementation, rights, ownership, safety, supply, use, or investment outcome was checked. Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. A documentation review is not an independent operational verification. The general ERC-20 specification is separate from this specific token implementation. The 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 community-maintained description field contains only a dash, providing no additional project-specific aims or economic niche details. Treat the generic application family as a documentary contract 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 live-network observation means that the active metadata label does not confirm the contract is currently functional or controlled by the expected parties. Without independent verification of bytecode or controller keys, the distinction between the recorded identity and the operational reality remains unresolved. Scoring coverage is at zero percent due to missing essential criteria including identity, supply, and control.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. No public admission of operational status or audit results is available. The dossier provides a factual summary of registry entries without implying endorsement or safety.
Evidence that would change the verdict
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this documentary baseline. Calibration and editorial review following such verification would be necessary to assign any score. Until then, the status remains unrated based on the supplied summaries.
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 Bluzelle Token
The pinned Trust Wallet Ethereum integration record names Bluzelle Token with symbol BLZ, contract 0x5732046a883704404f284ce41ffadd5b007fd668 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: "-" 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.