GET is a token deployed on HyperEVM (chain ID 999), branded as GET/HYPE, with its primary contract at 0x9f5f9265628c902def23e418045747803a7ee061. The official website getonhype.xyz describes it as a community-focused token where holders receive trading fees streamed in $HYPE via the Signal launchpad. The project states liquidity is locked forever and emphasizes a ‘flywheel’ model without lore or narrative—only mechanics. Its native explorer is hyperevmscan.io, and social presence includes Twitter (@getonhype_xyz) and Telegram (t.me/getonhype). Per source_2, total supply is ~995 million tokens, max supply 1 billion, and circulating supply is reported as zero—suggesting no tokens are yet in active circulation. No documentation, repositories, or audits are linked from the website or API snapshot.
Key evaluation questions remain: Is the claimed fee-distribution mechanism verifiably implemented and operational? Does the ‘liquidity locked forever’ claim reflect an immutable, audited lock, or is it subject to unilateral control? What counterparty risk arises from dependence on Signal launchpad—and who operates or governs it?
GET/HYPE presents itself as a HyperEVM-native token where holders receive trading fee streams in $HYPE via the Signal launchpad. The architecture relies entirely on HyperEVM’s execution layer and Signal’s off-chain or third-party distribution mechanism — neither of which is described, audited, or linked to technical documentation in the supplied evidence. No source explains how fees are captured, converted, or streamed; the website states only that “trading fees stream to holders in HYPE” (getonhype.xyz), while the API snapshot repeats this as an unverified claim and adds no implementation detail (CoinGecko). There is zero evidence of onchain fee routing logic, contract-level streaming mechanics, or integration with Signal beyond naming.
Execution dependencies
The token contract resides on HyperEVM (eip155:999), confirmed via explorer links and API metadata. However, no source verifies whether the deployed bytecode implements fee redistribution, nor whether Signal is a verified, trust-minimized protocol or a centralized service.
Data availability & settlement
All fee streaming depends on Signal — but Signal is not described, linked, or attested in any supplied material. Its role, custody model, upgrade path, or failure modes remain unknown.
This is a pure claims-based architecture: no verifiable mechanism, no audit, no code, no operational trace. Without evidence of how the core value proposition executes, the thesis remains speculative.
Overall score: 4/10 Confidence: Low