Honestly, I’m super bullish on @pudgypenguins 🐧 rn. It’s not just another cute PFP – the team is actually building: toys in Walmart, a web3 game, even infra moves with Abstract. That’s real IP expansion, not just hype.
Now compare it to @hypurr – yeah, the launch was crazy, $45M+ volume in 24h, insane floor pump. But it feels very “degen casino” vibes – low supply, high FOMO, but no proven track record yet. Could moon, could nuke. Still like the product, just my thoughts.
Pudgys on the other hand survived multiple bear cycles and are still delivering. To me, that’s a safer long-term bet vs chasing pure launch hype. 🧊✨
The HyperEVM is live. This is a major step toward the vision of housing all finance by bringing general-purpose programmability to Hyperliquid’s performant financial system. The initial mainnet release of the HyperEVM includes:
1. HyperEVM blocks built as part of L1 execution, inheriting all security from HyperBFT consensus.
2. Spot transfers between native spot HYPE and HyperEVM HYPE. As a reminder, HYPE is the native gas token on the HyperEVM.
3. A canonical WHYPE system contract deployed at 0x555...5 for defi applications. The source code can be found at https://t.co/pXmVRNpqov
Effective immediately, the bug bounty program will pay mainnet bounty amounts for reports within the scope of the points above. See https://t.co/KamzgZAYWh for details.
For API and wallet users: the mainnet HyperEVM has chain ID 999. A JSON-RPC server for the mainnet HyperEVM is hosted at https://t.co/BB0W8L4cXp. Node operators and other builders are encouraged to host their own RPC servers.
Tooling and analytics around mainnet HyperEVM may not be polished on day one. However, there are many talented builders working to solve these developer pain points. To help with these efforts, raw HyperEVM block data is streamed realtime to S3 so that running a node is not required to index the HyperEVM. More technical details can be found here: https://t.co/h6GeFo8HIl
General ERC20 native transfers and precompiles will be enabled on a future network upgrade. Any ongoing feedback for these features on testnet is greatly appreciated. While these features are implemented on testnet, the mainnet releases are staggered for minimal disruption to existing users on the L1. The HyperEVM is composable with the L1 state while not affecting the low latency trading experience of existing users.
Thank you to all the builders and users who have shared feedback on testnet so far. It will be exciting to see new applications leveraging and building upon the existing onchain financial system of Hyperliquid.
The Hyper Foundation is proposing a validator vote to formally recognize the Assistance Fund HYPE as burned, removing the tokens permanently from the circulating and total supply.
For context, the Assistance Fund converts trading fees to HYPE in a fully automated manner as part of the L1 execution. The Assistance Fund uses the system address 0xfefefefefefefefefefefefefefefefefefefefe. Similar to the zero address, the Assistance Fund system address has never had a private key with control over its funds. Funds are mathematically irretrievable without a hard fork.
By voting “Yes,” validators agree to treat the Assistance Fund HYPE as burned. No onchain action is required, as the tokens are already in a system address with no private key. This vote is binding social consensus to never authorize a protocol upgrade to access this address.
Voting process:
+ Validators should signal their intent in the governance forum by December 21 at 04:00 UTC (i.e., reply with Yes or No)
+ Users can stake to a validator who matches their view by December 24 at 04:00 UTC
+ The result will be based on stake-weighted consensus as of December 24 at 04:00 UTC