Twitxy Saved

yippie

Verified account This account is verified. Learn more

@Yippun

Joined March 2022
2.1K Following 4.5K Followers 15K Posts

Latest posts 5

Pinned post

yippie Verified account @Yippun
If USD 5k worth of tokens was all it took for a KoL to sell their souls, you need to re-think whether they are real content creators or audience farmers.

x.com/i/status/20124…
VietnamPenguin Verified account @VietnamPenguin Jan 17
Here are the @TroveMarkets badge holders (some have since been removed).
These “gentlemen” (apparently for money and with minimal due diligence) were promoting this project for Hyperliquid community.
View quoted post on X
7 replies 3 reposts 27 likes 8.7K views View on X
yippie Verified account @Yippun
No crying in the casino.
FrothyBeverage Verified account @frothybeverage Nov 9
@HyperliquidX's IOC speed-bump mechanism has a flaw. Normally designed to protect makers in the interests of a more liquid market, it breaks down in periods of high activity. When blocks become full, pending modifies and cancels queue up for later blocks, so their latency increases. However, IOCs behave as though they have a separate blockspace dedicated for them, and their latency barely budges. You can see this in the lower left chart, showing latency of different order types during 19 activity bursts.

The result is that under relatively modest load (25-30k tps), IOC + 8 bps (priority fee) orders can pick off resting liquidity before it has a chance to get out the way. Meanwhile, under higher load (35-40k tps), even IOCs without any priority fee can pick off resting liquidity.

This, in my opinion, is antithetical to the ethos and design of the ALO and cancel prioritization mechanism and needs investigation by the team. It exists to reduce toxicity from HFT takers, and is breaking down precisely when most needed.

It may also be exploitable. If IOCs really are insulated from the congestion affecting cancels and modifies, a malicious user could spam orders, delaying makers’ cancels while their own IOCs go through, and taking the liquidity left stale.

One single example that occurred on AVAX today caused 1.3M$ of volume to be adversely selected for a total loss of ~13k$ over the subsequent 10 seconds. This affected us materially. Faced with such episodes of adverse selection, spreads and liquidity are undoubtedly worse than they could be otherwise.

Would appreciate if anyone with a contact at HL could share this with the team.
View quoted post on X
yippie Verified account @Yippun
Yup majority of crypto are retards not realising rfq is literally an execution tool to request for a quote.

It's like requesting for a proposal (rfp) but anyone can be the counterparty. It can be multiple desks or just 1 dominate desk.
Loris Verified account @0xLoris Nov 1
ok fine, you want to know how i know none of you understood this?

you keep saying "we all know this, you fucking moron. it's an RFQ model."

oh, it's an RFQ model?

RFQ stands for "request for quote"

it does NOT imply that there is only one counterparty quoting. in fact, by default in most tradfi cases, there are many

all it means is a customer asks for a quote, the middleware forwards that request to market makers, the market makers reply with a quote, and the customer picks the best one(s).

the "middleware" here can be software or human brokers. in fact we used human rfq brokers all day long every day in options market making (where i learned to trade), since they had the largest orders.

and guess what - it was malpractice (they have best execution duty) NOT to get quotes from multiple MMs in that scenario

rfq absolutely has a use-case in markets, is appropriate and good, and variational seems to have built a highly profitable business around it

but if you just parrot the "rfq model" line without understanding what that means, go back and read the docs. and then i would suggest reading about the risks related to a single party being counterparty to all trades on an entire platform.

and then after that, if you still think it's a good idea to trade there, by all means
View quoted post on X