cryptosnif
MetFi (METFI)
Documentary contract0x3e7f1039896454b9cb27c53cc7383e1ab9d9512a
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
MetFi (METFI) presents itself as a decentralized investment vehicle designed to give everyday people early-stage access to promising Web3, Metaverse, and AI startups. The stated aim is to share all profits with the community. This dossier examines the documented purpose of this asset on the BNB Smart Chain network.
Established facts
The pinned Trust Wallet registry entry identifies MetFi with the symbol METFI and the documentary contract address 0x3e7f1039896454b9cb27c53cc7383e1ab9d9512a on the eip155:56 network. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. It labels the entry BEP20 and active. BEP20 is the token standard for BNB Smart Chain, analogous to ERC20 on Ethereum. The ERC20 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. The Trust Wallet Assets README describes a community-maintained registry where anyone can submit assets. Inclusion does not imply a direct partnership with listed projects. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified.
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 dossier may explain those stated aims with that attribution. No public admission of operational status exists. Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. A documentation review is not an independent operational verification.
Consequences
Because the registry description contains promotional statements about profit sharing and startup access, these are attributed claims rather than independently established issuer statements. Without verified deployment bytecode or controller data, the actual flow of funds or governance remains unknown. The active metadata label carries no live-network validation. Users relying on this registry entry cannot infer security, audit completion, or return potential from the provided source material.
Verdict
Operational strength remains unproven. The asset holds an unrated status with 0% scoring coverage. Critical missing elements include identity verification, supply data, and control mechanisms. The current evidence base supports only a documentary classification of the token subject.
What would change it
Reproduced identity checks, independent dated network observations and criterion-specific evidence would be required to move beyond this documentary assessment. Calibration and editorial review must follow any new operational data to adjust the verdict.
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 MetFi
The pinned Trust Wallet BNB Smart Chain integration record names MetFi with symbol METFI, documentary address 0x3e7f1039896454b9cb27c53cc7383e1ab9d9512a 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: "MetFi is a decentralized investment vehicle for the masses - giving everyday people early-stage access to some of the world’s most promising Web3, Metaverse, and AI startups, long before the public knows about them – all profits are shared with the MetFi community." 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.