Tiago
696 posts

Tiago
@tiagobnova
@novadotmarkets | @threesigmaxyz













POKE-USDC has reached $50m total volume on HIP-3 testnet



Conviction Markets are coming to Hyperliquid Think a market is missing? Build it. I just submitted my first one: · $AVGO (Broadcom Inc.) · Fundamental for AI infrastructure, highly volatile and with strong momentum (check chart and support). Heavily Launch coded. @novadotmarkets @Kinetiq_xyz




Kinetiq will support KIP-3: Launch, enabling permissionless LST deployments with optional HIP-3 and HIP-4 opt-in for qualifying stake. This has been one of the most requested features since Kinetiq's inception. Prospective HIP-3 deployers will be able to crowdsource the HYPE needed to launch their own DEX, without deploying or managing their own LST, and its corresponding infrastructure and security. Launch is not limited to just aspiring HIP-3 / HIP-4 deployers. Validators, communities, and DeFi protocols of any kind will be able to launch their own LST, unlocking capital efficiency and composability for HYPE that would otherwise sit idle on HyperCore. Launch Deployers retain full control over validator selection for their underlying stake delegation. This creates an entire new stream of revenue for deployers of permissionless LST's, who can collect a portion of staking rewards on top of providing several DeFi opportunities for their communities. Kinetiq will earn 10% of the deployer share from every bonded DEX in perpetuity, making it the cheapest, fastest, and most aligned path to market for any deployer. This aligns Kinetiq with the success of deployers as the protocol generates no returns unless deployers do. 100% of revenue from Launch is used to programmatically purchase KNTQ from the open market (via HyperCore) and is distributed entirely to sKNTQ stakers. Anyone will be able to deploy an LST on Hyperliquid without permission or gatekeepers, with full optionality to graduate into HIP-3 and HIP-4 as stake grows. This is a foundational primitive for Hyperliquid's DeFi ecosystem, and unique to the Kinetiq protocol exclusively. Further documentation will be shared upon launch.



