Chris Ling | NLH
901 posts

Chris Ling | NLH
@chrisling_dev
Investing @nolimithodl // building a pretty good hyperliquid frontend @try_supercexy


Earlier today, a user attempted to buy AAVE using $50M USDT through the Aave interface. Given the unusually large size of the single order, the Aave interface, like most trading interfaces, warned the user about extraordinary slippage and required confirmation via a checkbox. The user confirmed the warning on their mobile device and proceeded with the swap, accepting the high slippage, which ultimately resulted in receiving only 324 AAVE in return. The transaction could not be moved forward without the user explicitly accepting the risk through the confirmation checkbox. The CoW Swap routers functioned as intended, and the integration followed standard industry practices. However, while the user was able to proceed with the swap, the final outcome was clearly far from optimal. Events like this do occur in DeFi, but the scale of this transaction was significantly larger than what is typically seen in the space. We sympathize with the user and will try to make a contact with the user and we will return $600K in fees collected from the transaction. The key takeaway is that while DeFi should remain open and permissionless, allowing users to perform transactions freely, there are additional guardrails the industry can build to better protect users. Our team will be investigating ways to improve these safeguards going forward.


Earlier today, a user attempted to buy AAVE using $50M USDT through the Aave interface. Given the unusually large size of the single order, the Aave interface, like most trading interfaces, warned the user about extraordinary slippage and required confirmation via a checkbox. The user confirmed the warning on their mobile device and proceeded with the swap, accepting the high slippage, which ultimately resulted in receiving only 324 AAVE in return. The transaction could not be moved forward without the user explicitly accepting the risk through the confirmation checkbox. The CoW Swap routers functioned as intended, and the integration followed standard industry practices. However, while the user was able to proceed with the swap, the final outcome was clearly far from optimal. Events like this do occur in DeFi, but the scale of this transaction was significantly larger than what is typically seen in the space. We sympathize with the user and will try to make a contact with the user and we will return $600K in fees collected from the transaction. The key takeaway is that while DeFi should remain open and permissionless, allowing users to perform transactions freely, there are additional guardrails the industry can build to better protect users. Our team will be investigating ways to improve these safeguards going forward.


NEW: KRAKEN ANNOUNCES THE KRAKEN CLI - "AN OPEN-SOURCE, SINGLE-BINARY EXECUTION ENGINE BUILT BY KRAKEN THAT GIVES AI AGENTS AND DEVELOPERS DIRECT, NATIVE ACCESS TO CRYPTO MARKETS" SOURCE: blog.kraken.com/news/industry-…


*TRUMP TELLS ALL AGENCIES TO STOP USE OF ANTHROPIC’S TECHNOLOGY


Seeing more financial protocols ship CLIs is a good sign. Instead of every agent wiring directly into the API and rebuilding signing, retries, nonce handling, and state reconciliation, you get a shared execution surface that strategies can call deterministically. That's why at @nolimithodl we've recently shipped a @HyperliquidX CLI, the complete command-line interface with full HIP-3 support and low latency trading setup that has already seen thousands of downloads. Try it out! Hyperliquid.







$100M trading volume since launch. 24/7 frontier technology markets. Hyperliquid.



Hyperliquid does more notional trading volume than Coinbase 👀 We are seeing the fundamentals show up in the charts $HYPE $COIN



We heard that builders and API traders are struggling with integration of HIP-3 markets, multisig support and/or EVM<>Core interaction. Therefore, we built an SDK for Hyperliquid, one SDK to rule them all. github.com/infinitefield/…






