cryptosnif
Bilibili (Ondo Tokenized) (BILIon)
Documentary contract0x7e08ce07aca80cefe61ebbfa0cedfe5c7b07edb9
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 Bilibili (Ondo Tokenized) (BILIon) on the Ethereum network. The objective is to explain the stated aims and concrete research questions for this token based solely on supplied original summaries. We do not verify deployed bytecode, current controllers, or live network operation. The analysis remains strictly within the bounds of the provided documentary record.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Bilibili (Ondo Tokenized) with the symbol BILIon and contract address 0x7e08ce07aca80cefe61ebbfa0cedfe5c7b07edb9. The record specifies eighteen decimal places for amount representation. This metadata does not measure supply or value. The entry is labeled ERC20 and active within the community-maintained registry. The registry description states that BILIon is the Ondo Tokenized version of Bilibili, giving tokenholders economic exposure similar to holding BILI and reinvesting any dividends. It notes that additional restrictions apply and directs users to ondo.finance for more information. These statements are attributed registry claims, not independently established issuer statements. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It outlines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval, and remaining allowance. An allowance is the amount a named spender may use, and repeated approval overwrites that amount. The specification requires handling false transfer results and describes Transfer and Approval events. Name, symbol, and decimal-place metadata are optional in the standard. A wallet ERC20 label establishes no independently checked compliance or actual deployed implementation. The Trust Wallet Assets README confirms the registry is community-maintained, uses an MIT license, and excludes brand-new tokens from submissions. Inclusion does not imply a direct partnership with listed projects.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No live network observation was performed. The dossier cannot confirm if the contract implements the generic ERC-20 interface described in the specification. The operational strength of the token remains unproven. There is no public admission of audit results or security assessments. The scoring coverage is zero percent, resulting in an unrated status. Missing essential criteria include identity verification, supply confirmation, and control structure documentation.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Relying on registry labels without independent verification risks misinterpreting metadata as operational reality. The absence of verified supply data prevents assessment of concentration or liquidity risks. Without confirmed control structures, the potential for unilateral changes to token mechanics cannot be evaluated. Users assuming the token functions identically to the underlying asset face unquantified risk due to the stated additional restrictions.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. The documentary record provides only attributed claims from a community-maintained registry. No independent operational verification has occurred. The gap between the stated promise of economic exposure and the unverified technical implementation constitutes a critical uncertainty. The verdict stands until independent evidence bridges this gap.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would alter this assessment. Verification of the deployed bytecode against the claimed interface would clarify technical compliance. Confirmation of supply, control, and usage patterns by independent observers would reduce the unknowns. Calibration and editorial review following such evidence submission would allow for a scored evaluation. Until then, the dossier maintains its position of suspended judgment based on available documentary data.
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 Bilibili (Ondo Tokenized)
The pinned Trust Wallet Ethereum integration record names Bilibili (Ondo Tokenized) with symbol BILIon, contract 0x7e08ce07aca80cefe61ebbfa0cedfe5c7b07edb9 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: "BILIon is the Ondo Tokenized version of Bilibili, giving tokenholders economic exposure similar to holding BILI and reinvesting any dividends. Additional restrictions apply. Learn more at https://ondo.finance/gm." 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.