Before TGE
Hyperliquid Improvement Plan 1 was live
Hyperliquid Improvement Plan 2 was live
(Season 1 & Season 2)
Now after TGE
Hyperliquid Improvement Plan 3 is live
Hyperliquid Improvement Plan 4 is live
(Season 3 & Season 4)
HIP-(S3/4)
HIP-4 update. This one is big.
Hyperliquid just removed the need for external oracles on prediction markets. The validator set itself is now the oracle.
The same 24 validators that sign blocks every 70ms, secure $3B+ in deposits, and vote bridge withdrawals now deploy and settle prediction markets natively. Automated newsfeed software running as part of regular chain operations. Deployment and resolution through onchain validator vote.
No Chainlink. No Pyth. No UMA. No third party. Closed circuit.
Polymarket uses UMA. Kalshi is centralized. Hyperliquid just made real-world event resolution a native chain function.
Hyperliquid.
One underrated issue that will show its face a lot more going forward: ease of doing business
There will be so many more software products and startups being built, but if it's still difficult/time-consuming to register your company or get banking/payment-processing set up...
...you end up with a cohort of new founders able to build something useful but can't get it up and running solely because of outdated government bureaucracy
Stalled projects will be a huge issue in dozens of countries
Cycles Pay is the first privacy-preserving crypto payment app for businesses.
This is possible because of few specific design choices:
First, the private keys stay on your mobile device. User actions are cryptographically signed by your private key before being submitted on-chain. The financial data is encrypted with that key and doesn’t leave your mobile device.
Second, Cycles Pay uses a shielded pool to hide account balances on-chain. They are tracked as encrypted commitments and no one can see the underlying amounts or participants.
Third, when you make a payment, a ZK proof is generated and verified on-chain to confirm the transaction is valid without revealing the amount or the counterparty. Users get blockchain integrity without exposing the transaction details.
So what are we doing?
Lowest hanging fruit: embed shielded pool protocols into the wallet layer in a seamless, intermediary-free way.
This is what Kohaku's SDK is about. Support Tornado Cash, Railgun, Privacy Pools integrations in wallets with simple interfaces for wallet devs
I want to get a bit more public about the work we at the Kohaku Initiative inside the EF are doing
I notice there's hype but there's also confusion. Best way to clarify things is to speak candidly and openly about what I'm working on day-to-day
🧵time (bc i dont pay twitter $)
We must, then, avoid the “Babel syndrome,” namely the idolatry of profit that sacrifices the weak, a uniformity that neutralizes differences, and the pretense that a single language — even a digital one — can translate everything, including the mystery of the person, into data and performance. This is the risk of dehumanization: building a future that excludes God and reduces the other to a means.
Trump has two realistic options:
1. Agree to a deal where Iran keeps their enriched uranium and control of the Strait of Hormuz.
2. Escalate the war, and we have $150 a barrel oil and a global recession.
He's fucked.