Runner626

Built Chorus at the NEAR HACKATHON. Many people. One purpose. Intelligent execution. Bringing people, shared resources, and AI agents together to turn collective goals into real outcomes. Building on NEAR. 🚀 @NEARProtocol #NEARHackathon

1/ I’ve been testing Percolator Trade V2 on Devnet, and these are my 5 favorite things about it so far. No hype. Just what actually stands out. 🧵

@PercolatorTrade @0xSquid_Sol

DAY 30/30 — THE FULL PERCOLATOR VISION 1/ 30 days ago, we started with a simple idea: What if anyone could create a perpetual market? Now we’ve seen the architecture behind that idea. And with devnet v2 launching today… This is the full Percolator picture. 🧵

DAY 29/30 — WHY PERMISSIONLESS PERPS MATTER 1/ For years, perpetual markets followed a familiar model: A platform decides what gets listed. Percolator asks a different question: What if the infrastructure itself was permissionless? 🧵

DAY 28/30 — THE PERCOLATOR STACK 1/ Percolator isn’t just a perp trading interface. Underneath a single trade is a stack of systems working together: Token → Market → Oracle → Risk Engine → Keeper → Settlement Here’s how all the pieces connect. 🧵

DAY 27/30 — LIQUIDITY: THE CAPITAL BEHIND THE MARKET 1/ A perp market can exist on-chain. But without liquidity, trading becomes difficult. For Percolator, this raises an important question: Where does the liquidity behind a permissionless market come from? 🧵

DAY 26/30 — HOW A PERMISSIONLESS MARKET GETS CREATED 1/ What does it actually take to create a perp market on Percolator? The idea is deliberately simple: Choose an eligible SPL token → configure the market → deploy. No listing committee. No central approval. 🧵

DAY 25/30 — ONE ENGINE. MANY MARKETS. 1/ Percolator is trying to solve two problems at once: Anyone should be able to create a perp market. And those markets shouldn’t require a completely different risk system every time. And this is where it gets really interesting . 🧵