cryptosnif
Hum(AI)n (DOME)
Documentary contract0x475bfaa1848591ae0e6ab69600f48d828f61a80e
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
The documented subject is Hum(AI)n (DOME), identified by the asset identifier everdome-wallet-smartchain on the eip155:56 network. The pinned registry entry attributes a specific purpose to this token, stating that Everdome will provide a destination for Metahero’s technology to live, interact and flourish. This description frames the project as a gateway into a metaverse experience intended to blur the line between virtual and physical reality. These stated aims are attributed solely to the community-maintained registry description and remain unverified operational claims. No independent observation confirms whether the deployed bytecode or current controllers execute these functions.
Established facts
The documentary record from the Trust Wallet Assets repository identifies the token with the symbol DOME and the contract address 0x475bfaa1848591ae0e6ab69600f48d828f61a80e. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. The entry is labeled BEP20 and active within the BNB Smart Chain context. The ERC-20 specification defines a standard interface for fungible tokens in smart contracts, including functions for totalSupply, balanceOf, transfers, and allowances. An allowance is the amount a named spender may use, and repeated approval overwrites that amount. The specification notes that name, symbol, and decimal metadata are optional. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply, or security. The general ERC-20 specification is separate from this specific token implementation.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. The dossier may explain those stated aims with attribution, but 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. Inclusion in the community registry does not imply a direct partnership with the listed projects, and additional token information is optional and unavailable on-chain. No live network observation was performed to verify current program behavior or deployed control.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The active status is a metadata label with no live-network validation. Without independent verification of the deployed bytecode, current controllers, and network operation, the project's ability to deliver on its stated metaverse goals remains theoretical. The absence of verified data on supply, concentration, and liquidity means that risk assessment cannot proceed beyond the documentary layer. Users relying on this registry entry must recognize that it serves as a directory reference rather than an endorsement of operational safety or economic viability.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. The calculated scores indicate a status of unrated due to missing essential evidence regarding identity, supply, and control. All criterion observations for usage, token-role, concentration, value-capture, security, governance, accountability, incidents, continuity, and execution are marked as unknown. This verdict reflects the limitation of the source material to documentary records without independent operational verification. The dossier does not constitute an audit, price target, return forecast, or affiliate recommendation.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move beyond the unrated status. Verification of the deployed bytecode against the documented address, confirmation of current controllers, and observation of actual network transactions would establish operational reality. Evidence of independent audits, clear supply mechanics, and transparent governance structures would address the current gaps. Calibration and editorial review following such verification could result in a scored assessment. Until then, the project remains a documentary subject with unverified claims.
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 Everdome
The pinned Trust Wallet BNB Smart Chain integration record names Everdome with symbol DOME, documentary address 0x475bfaa1848591ae0e6ab69600f48d828f61a80e 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: "Everdome will provide a destination for Metahero’s remarkable tech to live, interact and flourish. Taking Metahero from the gateway into the metaverse, together with Everdome, to a fully ubiquitous web3 experience - to the point when you take off your VR headset you won’t be able to tell what’s real and what’s not." 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.