cryptosnif
Shrub (SHRUB)
Documentary contract0x3b991130eae3cca364406d718da22fa1c3e7c256
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.
Examined promise
This dossier examines the documented purpose and mechanisms of Shrub (SHRUB) on the Ethereum network, identified by contract address 0x3b991130eae3cca364406d718da22fa1c3e7c256. The objective is to explain the stated aims of this token based on available registry data. We do not verify deployed bytecode, current controllers, or live network operation. The analysis remains strictly within the scope of documentary evidence provided by community-maintained sources.
Established facts
The primary source for this identity is a pinned Trust Wallet Ethereum integration record. This document names Shrub with the symbol SHRUB and assigns it the contract address 0x3b991130eae3cca364406d718da22fa1c3e7c256. It specifies eighteen decimal places for amount representation. Decimal places concern how amounts are displayed and do not measure total supply or monetary value. The record labels the entry as ERC20 and active. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It outlines functions for reading total supply and balances, executing transfers, and managing allowances. An allowance permits a named spender to use a specified amount of tokens. Repeated approvals overwrite previous allowance amounts. The specification also describes Transfer and Approval events. Name, symbol, and decimal metadata are optional within this standard. A wallet label of ERC20 establishes no independently checked compliance or actual deployed implementation. The Trust Wallet Assets repository is a community-maintained registry used by the wallet and other projects. Inclusion does not imply a direct partnership with listed projects. The registry explicitly excludes brand-new tokens from submissions, meaning it cannot provide an exhaustive inventory of recent launches. Scripts and documentation in this registry use the MIT license. The network context identifies Ethereum, symbol ETH, with its project website and explorer. 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 through this source.
Unknowns
Present independent control, beneficial ownership, usage patterns, client adoption, total supply, concentration of holdings, liquidity depth, and complete incident history remain unverified. The registry description states the project is the internet’s hedgehog mascot and a community-driven initiative focused on fun, memes, and good vibes. Every economic, partnership, performance, supply, date, and adoption statement within this quoted description is an attributed registry claim. These are not independently established issuer statements or operational observations. No deployed implementation rights, safety guarantees, or investment outcomes were checked. The general ERC-20 specification is separate from this specific token implementation. Treat the generic application family as a documentary contract subject. Its economic niche and scoring criteria remain unclassified and unknown. A documentation review is not an independent operational verification. Missing evidence does not make a project fraudulent or unsafe; it simply prevents verification.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. Without independent verification of control, supply, or usage, the stated community-driven nature and meme-focused purpose remain unproven assertions. The absence of live-network observation means we cannot confirm if the contract behaves according to the ERC-20 standard or if any other deviations exist. Investors or users relying solely on this registry entry face uncertainty regarding asset safety, liquidity availability, and governance structure. The unrated status reflects zero percent scoring coverage across all dimensions including technology, usage, economics, governance, resilience, and liquidity. Essential criteria such as identity, supply, and control are missing from the evidentiary base.
Verdict
Operational strength remains unproven. The asset is unrated with zero percent scoring coverage. No public admission of risk or safety has been made because no independent assessment has occurred. The documentary record provides only a registry label and a community-submitted description. It does not constitute an audit, price target, return forecast, or affiliate recommendation. The calculated scores indicate a lack of essential data required for any meaningful evaluation. Until independent dated network observations and criterion-specific evidence are provided, the project remains outside the scope of verified classification.
Evidence that would change it
Reproduced identity checks confirming the contract address matches the claimed project. Independent dated network observations verifying live transaction activity, balance distributions, and transfer mechanics. Criterion-specific evidence demonstrating actual control mechanisms, supply limits, and governance structures. Calibration and editorial review following the receipt of these verifiable data points would allow for a transition from unrated to rated status. Current market data, adoption metrics, or third-party endorsements without technical verification would not suffice to alter 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 Ethereum record for Shrub
The pinned Trust Wallet Ethereum integration record names Shrub with symbol SHRUB, contract 0x3b991130eae3cca364406d718da22fa1c3e7c256 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: "The internet’s hedgehog mascot. A community-driven project with fun, memes, and good vibes." 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.