Meet Arena 67: research and trade memecoins on Robinhood Chain by just chatting. Ask “What just launched?” or “Sell 50% of my DOLL” and get a clean card, not a wall of charts. Practice with paper money at real prices, then go live. Built with @openservai

An LLM reads every order. A human signs every trade. I built 𝐀𝐑𝐄𝐍𝐀 𝟔𝟕 with @Knowledge_JO for the @openservai SERV Reasoning hackathon. A chat-first trading agent for Robinhood Chain. You type what you want to trade, SERV handles the research and reasoning behind it, and one confirm gate is the only path money can move. We run it live against Robinhood Chain mainnet (chain 4663), with custodial wallets and every new account starting on a paper sandbox. How a trade gets made: > SERV reads your intent, searches the token, prices the amount, picks the pool, then re-prices one last time before you confirm. It never signs. > A research rail keeps the context fresh: trending, new-tokens, holder overlap, transfer folds, and per-token reports straight off the live chain. > The confirm gate takes the final quote, checks the session and the caps, and executes through the Uniswap Universal Router with a desk-held signer whose keys are encrypted at rest. Then we tried to break it. > Double-confirmed the same intent: the claim is idempotent, so it returned the same receipt and fired 0 extra swaps. > Injected a pool address straight into the confirm body: rejected. Quote ids are opaque and bound to the session that created them. Sent a confirm from a second session: 401. The intent store only answers its owning session. Pushed the trade past the cap: refused. MAX_TRADE_USD and MAX_SLIPPAGE_BPS hold even after the model has already produced its intent. 113 tests across 12 suites keep the gate honest. Each sponsor powers one job in the desk: @openservai - the reasoning layer: intent, pricing, requotes, and a refusal to sign. @RobinhoodCrypto - the rails: mainnet settlement through the Universal Router. @neondatabase - the state: accounts, the sandbox ledger, conversations, and migrations on boot. One desk, three distinct jobs. Check it out: App: agent67desk.work API: api.agent67desk.work GitHub: github.com/Knowledge-JO/aren… Demo walkthrough in the comments. CC: @openservai @RobinhoodCrypto @neondatabase @OnlyHades_

We’re building NimDares in public for the @miniappscomp competition with @Nimiq. NimDares basically turns personal commitments into on-chain dares inside Nimiq Pay. The user flow is simple: 1. Create a commitment and define clear acceptance criteria. 2. Choose a verifier, such as AI vision, GitHub, or Strava. 3. Select a stake and approve the native Nimiq Pay payment sheet. 4. The NIM stake moves into escrow on testnet. 5. Submit proof before the deadline. 6. Verification determines the outcome. 7. Winners receive their payout. Failed commitments are routed into the slash pool or charity destination. NimDares has three modes: > Solo A private commitment between you and yourself. Complete the goal and reclaim your stake. Fail to provide valid proof and the stake is slashed. > Team A private room shared through an invite code. Each participant funds their own seat, submits individual proof, and valid participants share the slashed pot. > Arena A public commitment room listed for anyone to join. Participants compete under the same criteria, deadline, escrow, and verification rules. The testnet build now includes native Pay funding, real NIM escrow transactions, AI/API verification, room mechanics, automatic settlement, payouts, and slash-pool routing. We’re looking for early testers to try the full flow and give honest feedback on the payment experience, proof submission, and room design. More progress and testnet demos coming soon. @miniappscomp @Nimiq #BuildInPublic #Nimiq

CPMM v2: new pools on DeDust🔸 Yesterday marked three years since we began building DeFi in TON — creating user-friendly and valuable products for both users and builders. Over the past few months, we’ve been working on a new type of liquidity pool — more rewarding for token creators while remaining just as convenient for traders. Today’s release addresses one of the key challenges for all liquidity providers: separating trading fees from the core LP position. The current model presents two main issues: it's hard to track how much you've actually earned, and token creators have no way to receive trading fees from locked liquidity. The new CPMM v2 pools solve both. Fees are collected and claimed separately — even if the liquidity is permanently locked. For now, this applies only to tokens migrated from our Uranus launchpad on @x1000_finance, but very soon it will be available for any token directly in the DeDust interface. Another key feature is the Creator Fee — a portion of the fee credited to the specified address and available to claim. It works like a tax, but without the need for a custom token contract and the compatibility issues that usually come with it. The address is set when the pair is created, and for now, this setup can only be done by us upon prior agreement. Sincerely, DeDust Team🔸