Pangolin (PNG)

The documented promise

Pangolin is examined here as a documentary subject only. The dossier name is Pangolin, the trading symbol is PNG, the documentary network identifier is eip155:43114, and the pinned Trust Wallet Avalanche C-Chain integration record ties that name and symbol to the address 0x60781c2586d68229fde47564546784ab3faca982 with 18 decimal places. A decimal place is a unit of amount representation, so it says how a quantity is written, not how much supply exists or what anything is worth.

The stated token-specific purpose comes from that registry entry and stays an attributed registry claim. Its community-maintained description presents a community-driven decentralized exchange for Avalanche and Ethereum assets, with fast settlement, low transaction fees, and a democratic distribution. Those are stated aims in the registry description, not facts we checked, and they are repeated here with attribution for that reason. A decentralized exchange is a venue where users trade through software rather than a single operator; that label describes intended function, and this review did not observe a deployment performing it.

Documentary facts

Three points are established at the documentary level. First, the pinned integration record names Pangolin with symbol PNG, the documentary address above and 18 decimal places, labels the entry AVALANCHE and active, and carries the quoted description. Its project, economic, partnership, performance, supply and adoption statements are registry claims, not independently established issuer statements or operational observations.

Second, the pinned network-context record identifies the community registry directory for Avalanche C-Chain, which supplies documentary network context for entries in the same pinned directory. Third, 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 listed projects. That README also excludes brand-new tokens, so it cannot be an exhaustive inventory of recent launches, and its scripts and documentation use the MIT license.

On mechanism, the pinned ERC-20 specification defines a standard interface for fungible tokens in smart contracts, with totalSupply and balanceOf reads, transfers, authorised third-party transfers, approval and remaining allowance. An allowance is the amount a named spender may use, and a repeated approval overwrites it. Callers must handle a false transfer result, and Transfer and Approval events are described. Name, symbol and decimal-place metadata are optional in the standard. The specification and the generic application family are vocabulary and documentary scope, not evidence about this token.

What remains unknown

The documentary address match establishes no current program behaviour, deployed control and safety. This lot admitted no independently reviewed criterion observation, so the dossier carries 0% scoring coverage and the calculated result stays unrated, with identity, supply and control listed as missing essentials and thirteen dimensions still unknown. Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history remain unverified. Deployment bytecode, controllers, supply, reserves, concentration, liquidity, security audits and incident completeness were not examined. The documentary review performed for this dossier is not an independent operational verification, and a metadata label of active carries no live-network validation. The absence of admitted evidence means gaps in coverage, not that the project is fraudulent or unsafe.

Consequences of the documentary record

A registry entry defines a documentary subject, and that is its limit. The README's rule that anyone can submit and that inclusion implies no partnership means the entry cannot be read as an endorsement, a relationship or an operational guarantee, and its exclusion of brand-new tokens means the register is not a complete map of the space. The ERC-20 specification describes what a conforming implementation should do, so an ERC20 label in wallet metadata establishes no independently checked compliance, no actual deployed implementation, no controller permissions, no token use and no supply. Because the dossier examined no token transaction and no dated network observation, the documented mechanisms alone cannot establish how the token is used in practice, who can change it, or what outcome a user would face. No current market, return, supply, performance, adoption or ownership claim is made here, and no audit, incident or public admission is asserted. What this leaves is a clean documentary identification with an unproven operational core.

Verdict

Unrated, with 0% scoring coverage. The record identifies Pangolin, symbol PNG, on eip155:43114 at the documentary address 0x60781c2586d68229fde47564546784ab3faca982 with 18 decimal places, and attributes a stated purpose to a community-maintained registry entry. Beyond that identification the operational picture is unproven: no deployed implementation, controller, supply, use, safety or liquidity was verified, so no score can be assigned. This is a documentary verdict, not a statement about risk or intent.

Evidence that would change this assessment

Concrete research could move this dossier forward. Reproduce the identity checks against the pinned records and re-confirm the address match at an independent source. Obtain dated network observations of deployed bytecode, callable functions, controller permissions and upgrade paths, without treating a local readiness threshold or a documentation review as consensus or independent operational verification. Sample holder distribution and transfers against the ERC-20 interface requirements to assess whether the implementation follows the standard it is labelled with, remembering that patched versions and vulnerable versions are different things and that a genesis hash is not a signature. Seek criterion-specific evidence on usage, token role, value capture, governance, accountability, incidents and continuity. Each item would then need calibration and editorial review before any score is calculated, and the score would still be a computed result rather than an endorsement.