Perps RFQ is now live on HyperCore.
Request a quote, accept it, and the trade prints on the @HyperliquidX order book.
- BTC and HYPE to start, HIP-3 markets next
- Up to $100k per quote, higher caps coming
Which market should we add? UX feedback welcome too.
Size finds size. 🖤
Ciaran retweeted
This is the livestream for Network State Conference 2026.
xitter.cf/i/broadcasts/1qKVmyeOl…
Ciaran retweeted
Size finds size. 🖤
Silhouette's RFQ is live on Hyperliquid with @xStocksFi.
Request a quote, execute, settle onchain.
Ciaran retweeted
Hyperion DeFi has entered into a new HYPE Asset Use Service (HAUS) agreement with @silhouette_ex, a newly launched shielded trading platform built for Hyperliquid.
Silhouette is built on the premise that traders should have access to trading infrastructure that does not compromise privacy for cost efficiency. By pooling staked HYPE at scale, Silhouette delivers Hyperliquid's lowest available fee tier for every user on its platform, regardless of individual account size and trading volume.
ir.hyperiondefi.com/news-eve…
$HYPD. More than just HYPE.
Ciaran retweeted
We're going native with @nativemarkets.
USDH is live as a quote asset for all available Shielded spot markets on Silhouette.
app.silhouette.exchange
I run openclaw on arch, btw.
Bought a new Mac mini to properly tinker with claws over the weekend. The apple store person told me they are selling like hotcakes and everyone is confused :)
I'm definitely a bit sus'd to run OpenClaw specifically - giving my private data/keys to 400K lines of vibe coded monster that is being actively attacked at scale is not very appealing at all. Already seeing reports of exposed instances, RCE vulnerabilities, supply chain poisoning, malicious or compromised skills in the registry, it feels like a complete wild west and a security nightmare. But I do love the concept and I think that just like LLM agents were a new layer on top of LLMs, Claws are now a new layer on top of LLM agents, taking the orchestration, scheduling, context, tool calls and a kind of persistence to a next level.
Looking around, and given that the high level idea is clear, there are a lot of smaller Claws starting to pop out. For example, on a quick skim NanoClaw looks really interesting in that the core engine is ~4000 lines of code (fits into both my head and that of AI agents, so it feels manageable, auditable, flexible, etc.) and runs everything in containers by default. I also love their approach to configurability - it's not done via config files it's done via skills! For example, /add-telegram instructs your AI agent how to modify the actual code to integrate Telegram. I haven't come across this yet and it slightly blew my mind earlier today as a new, AI-enabled approach to preventing config mess and if-then-else monsters. Basically - the implied new meta is to write the most maximally forkable repo and then have skills that fork it into any desired more exotic configuration. Very cool.
Anyway there are many others - e.g. nanobot, zeroclaw, ironclaw, picoclaw (lol @ prefixes). There are also cloud-hosted alternatives but tbh I don't love these because it feels much harder to tinker with. In particular, local setup allows easy connection to home automation gadgets on the local network. And I don't know, there is something aesthetically pleasing about there being a physical device 'possessed' by a little ghost of a personal digital house elf.
Not 100% sure what my setup ends up looking like just yet but Claws are an awesome, exciting new layer of the AI stack.
Ciaran retweeted
i'm a growth guy. i don't code.
but i just built a working shielded swap (@sillyswap_xyz) for mobile on Hyperliquid using ai and silhouette's API.
a small thread 🧵
Stoked to see @extropic launching a new take on AI compute. @beffjezos pushing us up the Kardashev scale.
I also got a chance to chat with @Optalysys earlier this year - who are building literal sci-fi tech for Fully Homomorphic Encryption.
Makes one optimistic man.
Physical attacks on TEEs (excluding Nitro Enclaves) are making the rounds again. It’s a good moment to revisit what TEEs actually protect and what they don’t.
TEEs exist on a security spectrum and are not actually "Trusted" for all use cases. They primarily provide confidential computing environments with the condition that they must have good physical security (i.e. in a secure cloud).
Confidentiality is different to integrity (security). One would not want a TEE to have unilateral control over funds for example, but one would want to use a TEE to process transactions confidentially (very different threat models).
When using TEEs in high-stakes contexts where the outputs have serious implications, a good thing to do is to constrain the TEE as part of a posture that primarily leverages confidentiality.
Constraining a TEE means not treating it as a KMS, and requiring it to prove that its outputs are correct. This means ZK in the strong form. But if we don't trust the TEE to hold funds or to give us correct outputs, what are we doing?
Well, TEEs are fast, and they have enough resources to get a lot done. So they are well suited to a particular set of tasks. These include performant privacy.
A TEE-hosted confidential computing environment can give us a lot of private horsepower, while not being relied upon for things it doesn't do perfectly.
ZK, FHE and TEEs are all actually still maturing. There is no clear winner for all use cases at this exact moment. Use the appropriate tools for the job at hand.
Ciaran retweeted
I think @silhouette_ex will be a top 5 HL eco project.
Ciaran retweeted
Behind the Shield: An Update
Privacy Backend:
> API service deployed to Marlin and wired to our testnet contracts
> Wallet-signed bearer auth ensures each user can only access their own data
> Deposits are detected and allocated near-instantaneously
> Users can view balances, submit spot orders (market/limit on HYPE/USDC), manage open orders, cancel, and withdraw
Observability & Integration:
> New observability stack for API behaviour, error reporting, and investigations (no customer data exposure)
> OpenAPI spec live for programmatic integrations
> Python SDK progressing as a drop-in replacement for Hyperliquid’s SDK
App Development:
> Core infrastructure complete: wallet integration, deposits, balance sync, chain switching, and static UI framework
> End-to-end deposit flows live
> Withdrawals in progress: dialog built, SDK integration under review, balance updates and position tabs advancing
> TradingView widget integrated; styling and config underway
> Focus now on refining withdrawals, positions, and charting while polishing UI
Next Up:
We’re relaunching our doc site and website. Development starts today.
Nice. the HyperCore <> HyperEVM interaction is really powerful but takes a little getting used to, so it's great to see this constant stream of contributions from the community.
