> I offer to KYC to get @HyperliquidX to unban my wallets from the official frontend
they ignore all my messages on my discord ticket and I get left on read on TG
+ today I find out that not only did they close my ticket, they banned me from the discord with no warning (I hadn’t sent a message in any public channels and I hadn’t sent a message in the ticket for weeks)
> all the .hl’s: “you can’t expect hyperliquid, a chain with no KYC, to take your KYC. it will set a precedent and make it easier for regulators to come after them. you are one small fish, you are not worth jeopardising an eMpIre over, just uSe aNoThEr fRoNtEnd (and forget your airdrop)”
> I tell the .hl’s (and I still consider myself a hyperliquid maxi) that their silence towards, and in many cases, approval of hyperliquid blindly banning any wallet with the slightest blemish on @chainalysis
(NB: chainalysis doesn’t even blanket flag any wallet that has ever touched HTX, or a wallet that has touched HTX, or a wallet that touched that wallet etc, after may 26th as high risk
they take into account what % of that wallet’s funds came from HTX, how many transfers etc
but hyperliquid set all their tolerance thresholds to 0)
> now there will be functionality AT THE CHAIN LEVEL for blocking wallets, geoblocking (yes, they can geoblock wallets because they can see which wallets deposited to US CEXs onchain) and most probably enforcing KYC
the .hl’s are actually celebrating because they assume it means that coinbase can now make a KYC’d builder frontend on top hypercore for US users and send HYPE to 3 digits
but this is NOT about frontends, this is HIP-3 deployers blocking wallets AT THE CHAIN LEVEL from sending txns
so no, you will not be able to just uSe aNoThEr fRoNtEnd in the future
what if tradexyz ban wallets that have touched HTX from actually sending txns?
and if it’s there at the chain level for HIP-3 deployers, the door is open for regulators to force hyperliquid to implement it for validator perps too
how can they use the defence of “we are a decentralised blockchain, we can’t control who sends txns on it, we can only control who accesses the frontend” anymore?
TLDR:
1) @chameleon_jeff@xulian_hl@iliensinc@jchervinsky@HyperliquidPC even CEXs allow for extra KYC to unfreeze funds deposited to them from a wallet that had touched HTX
there is no company/protocol that offers 0 recourse to overturn a ban
please respond to my case and unban me from the discord
2) if you are a .hl and my case doesn’t matter to you, you should at least recognise that your silence and tacit or explicit approval partially paved the way for hypercore to eventually become a permissioned blockchain
hyperliquid
Idk I'm not so convinced about a DEX built by an underwater CEX
Feels like the main CEX is not printing enough, so they pivot and create another project with another token.
Having 2 tokens is extractive from my point of view.
+ Too much BD and a huge team inevitably finishes into a Dango-like
Whitelisted HIP-3 deployments are coming.
CT is speculating about a KYC for Hyperliquid.
imo it's not entirely wrong, but it's more likely feedback from CEXs that want to become deployers.
Regulated CEXs need to control who uses their products.
Good thing, HL is expanding
new feature observed on hl testnet: stars
afaict stars let deloyers make a hip-3 dex address-allowlisted for trading. testnet allowlist size currently is max 10k addresses. non-allowlisted addresses can still submit reduce-only orders / fund accounts.
see ktob ("BTC Star DEX")
some relevant txs:
0x851e0bc62988fe9e8697042529220801080023abc48c1d7028e6b718e88cd889 (register ktob:BTC)
0x54c1a9c94451ac7e563b0425292214010100c1aedf54cb50f88a551c03558668 (activate star)
0x875b29d555ffdba188d4042529221c01030041baf0f2fa732b23d52814f3b58c (approve trader address)
0x9dbce81f1a86dc269f360425292224010c000004b589faf841859371d98ab611 (unhalt ktob:BTC)
0x3130533baff0a23a32aa0425292ce1010a006b214af3c10cd4f8fe8e6ef47c24 (unapproved address funded)
0x8923485ccfdea73b8a9d0425292d2c01010060426ad1c60d2cebf3af8ed28126 (unapproved address attempts to place order and fails)
0x326fcd720ba84bd833e90425292e06010400e557a6ab6aaad63878c4caac25c2 (approved trader address funded)
0xe070d0c9f5aca692e1ea0425292e33010300e8af90afc56484397c1cb4a0807d (approved trader address places order successfully)
can think of a few reasons why this might be useful, but will refrain from speculation for the time being.