cryptosnif
Phoenix Global (PHB)
Documentary contract0x0409633a72d846fc5bbe2f98d88564d35987904d
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.
Examined promise
The documented subject is Phoenix Global (PHB), identified by the wallet integration record for smartchain network eip155:56. The pinned registry entry states that Phoenix Global is built for the enterprise, with the consumer in mind. It claims to develop and deploy decentralized consumer apps built to scale, fitting within existing customer experience. This description is an attributed registry claim from a community-maintained source. It does not constitute an independently verified operational statement or proof of current deployment. The dossier examines this stated purpose against the available documentary evidence.
Established facts
The Trust Wallet Assets README defines the registry as a community-maintained collection of token information and logos used by the wallet and other projects. Inclusion does not imply a direct partnership with listed projects, and additional token information is optional and unavailable on-chain. The specific record for PHB labels the entry BEP20 and active. BEP20 refers to the standard interface for fungible tokens on BNB Smart Chain, which is compatible with the ERC-20 specification. The ERC-20 standard defines 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, where repeated approval overwrites the previous amount. The registry record specifies 18 decimal places for PHB. Decimal places concern amount representation and do not measure supply or value. The network context confirms this is part of the community registry directory for BNB Smart Chain. Promotional statements, network performance, consensus behavior, current deployment and control are not verified from this context.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history remain unverified. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. 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 dossier may explain those stated aims with attribution, but no live-network validation exists.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. 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. Missing evidence does not make a project fraudulent or unsafe, but it prevents any assessment of operational strength.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. No public admission of operational status is provided. The calculated scores show zero coverage across all dimensions including technology, usage, economics, governance, resilience and liquidity. Essential missing data includes identity verification, supply confirmation and control analysis. The verdict reflects the absence of independent operational verification rather than a negative finding.
Evidence that 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 status. Concrete research questions include verifying the deployed bytecode at address 0x0409633a72d846fc5bbe2f98d88564d35987904d against the claimed ERC-20 interface, confirming current controllers and access controls, observing actual transaction volume and liquidity depth, and identifying any completed security audits or incident reports. Without these, the dossier remains limited to the supplied original summaries and their exact code documentation versions.
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 Phoenix Global
The pinned Trust Wallet BNB Smart Chain integration record names Phoenix Global with symbol PHB, documentary address 0x0409633a72d846fc5bbe2f98d88564d35987904d 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: "Phoenix Global is built for the enterprise, with the consumer in mind. Developed and deploy decentralized consumer apps built to scale, and fit within the existing customer experience." 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.