cryptosnif
heyAura (ADX)
Documentary contract0x6bff4fb161347ad7de4a625ae5aa3a1ca7077819
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 heyAura (ADX), identified by the pinned Trust Wallet registry entry for BNB Smart Chain. The registry describes the project as an AI Infrastructure company building frameworks for Web3, with a flagship Agentic copilot designed to research, plan, execute and orchestrate on-chain tasks securely and privately. This description represents a community-maintained registry claim rather than an independently verified operational statement or issuer admission. The dossier scope limits itself to examining this stated purpose without validating current network behavior, deployed bytecode, or active controller status.
Established facts
The documentary record identifies the asset as heyAura with symbol ADX on the eip155:56 network, corresponding to BNB Smart Chain. The specific contract address listed in the registry is 0x6bff4fb161347ad7de4a625ae5aa3a1ca7077819. The token is labeled as BEP20, which refers to the fungible token standard implemented on BNB Smart Chain, analogous to the ERC-20 standard on Ethereum networks. The registry specifies 18 decimal places for amount representation; this technical detail defines precision but does not measure supply, value, or economic utility. The Trust Wallet Assets README confirms that inclusion in this community-maintained registry does not imply a direct partnership with the listed projects, nor does it validate deployment bytecode, current controllers, or safety mechanisms. The generic application family identifies only a documentary token subject, leaving its economic niche and scoring criteria unclassified.
Unknowns
Independent verification of control, beneficial ownership, actual usage, client adoption, total supply, concentration, liquidity, and complete incident history remains absent. No live network observation was performed to confirm that the documented address corresponds to active smart contract logic or that the described Agentic copilot functionality is currently deployed and operational. The gap between the registry description and actual network state means that promotional statements, performance metrics, and partnership claims within the registry entry cannot be treated as established facts. The dossier explicitly notes that documentary address matching establishes no current program behavior, deployed control, or safety guarantees.
Consequences
Relying solely on documentary mechanisms from a community registry cannot establish actual network behavior, investment outcomes, or security posture. Without independent dated network observations or criterion-specific evidence, the operational strength of heyAura (ADX) remains unproven. Users or researchers cannot infer functional capabilities, risk levels, or economic viability from the registry label alone. The absence of verified data on supply, control, and incidents creates a significant information asymmetry, where the stated aims of the project are disconnected from any confirmed implementation or audit trail.
Verdict
heyAura (ADX) is unrated with 0% scoring coverage. The calculated scores reflect a lack of essential evidence across identity, supply, and control dimensions. The editorial verdict is based strictly on the absence of independent verification; the missing evidence does not make the project fraudulent or unsafe, but it prevents any assessment of operational strength or reliability. The status remains pilot-grade, requiring reproducible identity checks and independent network observations before any future evaluation can proceed.
Evidence that would change it
A shift in this assessment would require reproduced identity checks confirming the active controller of the documented address, independent dated network observations verifying the deployed bytecode matches the claimed functionality, and criterion-specific evidence covering identity, supply, control, security, and governance. Calibration and subsequent editorial review would be necessary to assign a meaningful score. Until such evidence is provided, the dossier maintains its position of non-verification, treating all registry claims as unverified assertions rather than operational realities.
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 heyAura
The pinned Trust Wallet BNB Smart Chain integration record names heyAura with symbol ADX, documentary address 0x6bff4fb161347ad7de4a625ae5aa3a1ca7077819 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: "heyAura is an AI Infrastructure company that’s working to build reliable AI frameworks for Web3 projects. heyAura’s flagship product is the very first Agentic copilot that can securely and privately research, plan, execute and orchestrate on-chain tasks." 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.