DeepBook Token (DEEP)

The promise on the table

This dossier examines one question: what does the documentary record actually establish about DeepBook Token, identified here as DEEP on the Sui network, before any score can be assigned. The subject is pinned to a single documentary contract string, 0xdeeb7a4662eec9f2f3def03fb937a663dddaa2e215b8078a284d026b7946c270::deep::DEEP, and to the identity deep-wallet-sui. That string identifies only the documented subject. It does not confirm that the matching program is currently deployed, who controls it, or how the network currently operates.

The stated purpose of this crash test is narrow. We look at what the supplied original summaries describe, name the exact versions and historical limits of those summaries, and separate documentary claims from operational observation. Everything below is either a source-based fact, a declared unknown, or an editorial interpretation, and each section marks which is which.

What the documents establish

A registry is an informational catalogue, not a live probe of a blockchain. The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by that wallet and other projects. It states that additional token information is optional and unavailable on-chain, that anyone can submit assets, and that inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so the registry cannot serve as an exhaustive inventory of recent launches. Its scripts and documentation use the MIT license. This is the wallet project's own integration registry, filled by community submissions, so its descriptions are documentary claims rather than independently verified issuer statements or operational observations.

Inside that registry, the pinned Sui integration record names DeepBook with the symbol DEEP, the documentary identifier 0xdeeb7a4662eec9f2f3def03fb937a663dddaa2e215b8078a284d026b7946c270::deep::DEEP, and 6 decimal places. Decimal places describe how amounts are represented and establish nothing about current supply or value. The entry is labelled SUI and active, where active is a metadata status label rather than a live-network validation. The Sui directory context that hosts this record names Sui, which establishes documentary directory context only.

The same pinned record carries a community-maintained description: DeepBook is presented as a decentralized central limit order book, or CLOB, built on Sui. A CLOB is an exchange model where buy and sell orders are recorded in an ordered list and matched by price and time priority, as opposed to a pool that prices trades by a formula. The description further claims that the project leverages Sui parallel execution and low transaction fees to bring a high-performance, low-latency exchange on chain. Every project, partnership, grant, economic, performance, supply, date and adoption element of that description is an attributed registry claim, and none of it has been verified with an issuer or through operation. The directory label does not establish a mainnet deployment, a functioning implementation, or present token rights.

What remains unknown

No live network observation was performed for this dossier. The documentary address matching establishes no current program behavior, deployed control or safety. The assessed criteria for identity, usage, token role, supply, concentration, value capture, control, security, governance, accountability, incidents, continuity and execution all remain unknown, with no admitted independent criterion observation in this documentary lot. Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity and complete incident history therefore stay unverified.

This registration also reflects a project with 0% scoring coverage and an unrated calculated status; there is no public admission of any deficiency, and none is implied. Coverage is a measure of how much applicable evidence has been admitted and independently reviewed. At 0%, a score cannot be computed. The missing essential criteria of identity, supply and control prevent a total even if partial evidence existed, which it does not.

Why this matters

The distinction between a documentary record and an operational fact is not pedantry. A registry entry can be accurate as metadata and still tell you nothing about whether a contract executes as described, who holds upgrade or mint authority, or whether the token has any live economic role. Treating a documentary match as proof of deployed behavior would import claims the sources never made. So the practical consequence is that a reader cannot move from this dossier to any conclusion about actual network behavior or investment outcomes, because no source here supports that step.

The Trust Wallet scope note is plain that inclusion does not imply partnership, that token information is optional and unavailable on-chain, and that descriptions are community documentary claims. Layered onto a pinned but dated record, this means even the basic promise of an on-chain exchange is currently a claim awaiting independent reproduction, not an established fact.

Verdict

DeepBook Token remains unrated with 0% scoring coverage, based on documentary material only. The documentary stack is real and internally attributed, but the operational strength of the subject is unproven. This is an honest statement about the present evidence lot, not a judgment of the project's quality. No incident, audit, ownership or performance claim is made here, and none should be read in.

What would change this

Three concrete steps would move this dossier beyond the documentary layer. First, reproduce the identity checks: independently confirm the contract string against deployed bytecode and current control addresses on sui:mainnet, and record dated observations. Second, gather criterion-specific evidence for the missing essentials, namely identity, supply and control, plus the remaining unknown criteria such as governance, incidents and continuity. Third, submit the resulting evidence to calibration and editorial review so that any score is computed, versioned and defensible.

Private catalogue research questions follow from that: who currently controls the documented program; is the referenced CLOB implementation live and used; what are the token's actual rights, if any; and what does a complete, dated incident record contain. Until those are answered with admissible evidence, the unrated status stands.