testermike - e/acc retweeted
"To bankrupt a fool, give him information." - Nassim Nicholas Taleb in The Bed of Procrustes
testermike - e/acc retweeted
TxFlow is Hyperliquid from Temu
They forked Hyperliquid's Arbitrum bridge and changed the name. They copied HyperUnit too and forgot to change the name: txrelay[.]com literally says "Unit is the asset tokenization layer on TxRelay". The frontend, the API and the fees are Hyperliquid's. Even the slogan. The L1 is closed source, with Hyperliquid's naming on everything: TxCore, Tx-BFT, TIPs
Hyperliquid is closed source too, but it has 27 validators that each post prices, and anyone can run a node to check them. TxFlow has 5 validators, all its own, nothing you can run, and one key that acts as the entire oracle. The same key sits on the bridge multisig
So it's a centralized exchange secured by a 3/4 multisig. Their own audit says those keys "can propose arbitrary withdrawals"
And the growth plan is KOLs shilling ref codes
testermike - e/acc retweeted
"what's your biggest impact on the internet?"
drawing mulder and scully with courage
testermike - e/acc retweeted
HyperMeat x @0xmylanta and the S3 Special🥩
00:00 Intro
01:25 Meet 0xMylanta | HyperMeat's First Anon Guest
03:02 Why Season 3 Is Bullish for Hyperliquid
08:01 Decentralization as a Competitive Advantage
14:44 Hyperliquid's Liquidity and Trading Fees
17:21 Funding HYPE Staking Rewards with Fees
19:20 Staking Risks and Token Dilution
22:36 Sponsors: @silhouette_ex, @AwakenTax, @hlnames, @ripdotxyz, @BuoyFinance
24:58 The Case Against Season 3
28:25 Will TradeXYZ Launch a Token?
29:10 Season 3 Odds and Breadcrumbs
30:22 Portfolio Margin: 10M to 35M HYPE
32:06 Xulian Moves to Hyper Foundation
33:26 Validator Expansion and Node Changes
34:11 Hyperliquid's Community Ownership Vision
35:57 Hypurr #62: November 29 Theory
38:28 SEC, Airdrops and Regulatory Clarity
42:57 Hypersound Money: The HYPE Bull Case
47:29 Hypurr NFT Season 3 Rewards?
47:54 Favorite Cut of Meat
48:50 Final Thoughts
Follow @HLMedia_io! Next guest is @eqxlabs 👀
testermike - e/acc retweeted
There will be a breakup after which you lose your ability to love. That is when you become an economic unit and your sole purpose is to boost GDP per capita (nominal) till you die.
testermike - e/acc retweeted
Normalize cutting the tension in a meeting by ending it with, “We’re all gonna die one day, so none of this really matters.”
testermike - e/acc retweeted
Dünyanın en zor işlerinden biri, alelâde biri olduğunu kabullenmektir. İnsan, kendisini istisna sanmaya meyillidir. Gerçek olgunluk, sıradanlığını kabulle başlar.
testermike - e/acc retweeted
We're about to enter a period where not reading or writing becomes as ubiquitous as smoking once was. We can hope people will eventually realize this is bad for them, as they did with smoking. But this is far from certain; the cost may not be as obvious.
testermike - e/acc retweeted
Payward, the parent company of Kraken, announced its intention to be the first CFTC-regulated deployer on HIP-3* markets. Payward will use Hyperliquid as the infrastructure layer to deploy perpetual futures markets for US clients. Subject to regulatory approval, Bitnomial, Payward’s CFTC-regulated DCM and DCO, would act as the HIP-3* deployer: creating, owning, and administering the markets and clearing and settling the contracts. If approved, NinjaTrader Clearing, Payward’s CFTC-registered FCM, would carry client accounts.
HIP-3 will support optional deployer configuration for permissioned markets in a future network upgrade. This set of additional deployer functionality is collectively called HIP-3*. At its core, HIP-3* activation involves an onchain allowlist managed by the deployer or its sub-deployers. The functionality is strictly additive to HIP-3; its use is optional and up to the deployer. Existing markets remain unchanged. The initial release is available on testnet, where specifications are preliminary and subject to change based on feedback.
Hyperliquid is a neutral infrastructure layer with the goal of supporting large parts of the financial system. HIP-3* gives deployers additional functionality to operate deployments consistent with the requirements applicable to them. As with HIP-3, HIP-3* deployers are independent operators who use Hyperliquid as the onchain infrastructure layer for their own markets, while retaining control and responsibility over their deployment.
































