
Ontology (ONT)
Documentary contract0xfd7b3a77848f1c2d67e05e54d78d174a0c850335
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 the Ontology (ONT) token as recorded in the Trust Wallet community registry for BNB Smart Chain. The stated purpose is to identify a pegged representation of the Ontology Token issued on this network. We examine only the documentary claims provided by the pinned integration record and its surrounding context. No independent verification of current network behavior, deployed bytecode, or active controllers has been performed. The analysis remains strictly within the bounds of the supplied original summaries.
Established facts
The pinned Trust Wallet BNB Smart Chain integration record identifies Ontology with the symbol ONT and the documentary address 0xfd7b3a77848f1c2d67e05e54d78d174a0c850335. The record specifies eighteen decimal places, which concern amount representation and do not measure supply or value. It labels the entry as BEP20 and active. The community-maintained description states that the BNB pegged Ontology Token is issued by Binance on Smart Chain and is pegged to Ontology Token at a ratio of one to one. These statements are attributed registry claims, not independently established issuer statements. The general ERC-20 specification defines a standard interface for fungible tokens, including totalSupply reads, transfers, and allowances. An allowance permits a named spender to use a specified amount, with repeated approvals overwriting previous amounts. This specification describes what a conforming implementation should do, but does not verify actual deployment. The Trust Wallet Assets README confirms this is a community-maintained registry where inclusion does not imply partnership and brand-new tokens are excluded from submissions. 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 active status is a metadata label with no live-network validation. No token transaction was performed in this review. The dossier may explain stated aims with attribution, but cannot confirm operational reality. Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The missing essential criteria include identity, supply, and control, leaving the project unrated with zero percent scoring coverage.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of independent verification means that promotional statements, network performance, consensus behavior, current deployment, and control are not verified or admitted from this context. Users relying solely on registry labels face uncertainty regarding the actual functionality and safety of the asset. The lack of criterion-specific evidence prevents any assessment of operational strength or resilience. Without independent dated network observations, the gap between registry claim and operational reality remains unbridged.
Verdict
Operational strength remains unproven. The project is unrated with zero percent scoring coverage. The documentary address matching establishes no current program behavior, deployed control, or safety. The verdict is based on the absence of independent verification rather than negative findings. The lack of evidence does not make the project fraudulent or unsafe, but it does prevent any positive assertion of reliability. The calculated scores reflect this empty state, with all dimensions showing null scores and zero coverage.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this status. Calibration and editorial review following such verification could assign a score. Specific research questions include verifying the actual deployed bytecode against the documentary address, confirming the peg mechanism through on-chain transactions, and assessing the current controller permissions. Independent audit reports or live network data demonstrating stable operation and transparent governance would also shift the assessment from unrated to rated. Until such evidence is provided, the dossier remains limited to the supplied original 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 BNB Smart Chain record for Ontology
The pinned Trust Wallet BNB Smart Chain integration record names Ontology with symbol ONT, documentary address 0xfd7b3a77848f1c2d67e05e54d78d174a0c850335 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: "BNB pegged Ontology Token (ONT BEP20) is a token issued by Binance on Smart Chain; its price is pegged to Ontology Token (ONT) at a ratio of 1:1." 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.