cryptosnif
Nexo (NEXO)
Documentary contract0xb62132e35a6c13ee1ee0f84dc5d40bad8d815206
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 Nexo (NEXO) on the Ethereum network. The objective is to explain the stated aims found in registry records without adopting promotional claims or verifying live network operation.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Nexo with the symbol NEXO and contract address 0xb62132e35a6c13ee1ee0f84dc5d40bad8d815206. This record specifies eighteen decimal places for amount representation, a technical detail that does not measure supply or value. The entry is labeled ERC20 and active within the community-maintained registry. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts, including functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount, which can be overwritten by subsequent approvals. The specification also outlines transfer result handling and event logging. Name, symbol, and decimal metadata are optional under this standard. The wallet blockchain-information file confirms the network context as Ethereum, identified by the symbol ETH. The registry scope documentation states that inclusion does not imply a direct partnership with listed projects and that additional token information is optional and unavailable on-chain. Every project, economic, partnership, performance, supply, date, and adoption statement within the quoted registry description is an attributed claim from that source, not an independently established issuer statement or operational observation. No deployed implementation, rights, ownership, safety, supply, use, or investment outcome was checked during this review.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. The registry label establishes no independently checked compliance, actual deployed implementation, controller permissions, or security posture. No token transaction was performed in this review.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of live network observation means that operational strength remains unproven. The stated purpose of being a compliant token backed by underlying assets of a loan portfolio is a registry attribution that requires separate verification to confirm economic reality.
Verdict
Operational strength remains unproven; unrated with zero percent scoring coverage. Critical missing elements include identity verification, supply data, and control mechanisms. The dossier serves as a documentary explanation of registry claims without implying an independent audit has occurred.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond this unrated status. Calibration and editorial review following such verification would be necessary to assign a score.
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 Nexo
The pinned Trust Wallet Ethereum integration record names Nexo with symbol NEXO, contract 0xb62132e35a6c13ee1ee0f84dc5d40bad8d815206 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: "NEXO (NEXO) is a compliant token that is backed by the underlying assets of Nexo’s loan portfolio." 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.