Rhizen Crypt

If you missed today’s Builder Session with @0xironyAditya, @emreyeth and @dmitrysssss, here’s what stood out to me about the @dreamDEXSomnia Perps Builder Bounty 👇 Most of my time on dreamDEX lately has been spent trading and completing quests. But this session gave me a better understanding of what developers are working with, where they’re running into problems, and what the team wants to see built next. There’s a $3,000 pool across two independent tracks, and you don’t need to build an entire app to contribute. 1️⃣ Two ways to take part The feedback track has a $1,500 cap: $40 for accepted critical or major issues and $15 for other accepted reports. It covers API and SDK issues, documentation gaps, bugs and missing features. No MVP or X posts are required for this track. The report needs to explain what happened, what should have happened, and how to reproduce it, with transaction details where relevant. Only the first valid report gets paid. Duplicates and known issues don’t count, and payouts stop once the budget is reached. Security vulnerabilities are handled separately. The second track offers three $500 MVP prizes, plus a breakdown post on the dreamDEX X account. You can enter one track or both. 2️⃣ The MVP prize comes in two parts Each $500 prize is split into $300 at announcement and another $200 once the MVP places orders on mainnet, within 30 days of the perps mainnet launch. I like this detail. There’s an incentive to keep working on the product after the results are announced. The team wants a clear use case, evidence of building, and a reason for people to use the product again or share it. Working orders on Tokyo, transaction hashes, a repository or a demo help show the progress. Builders also need 2–3 accurate X posts explaining what they’re making. Somnia Reactivity and Somnia Agents are encouraged. 3️⃣ Use the right network and keep the funds separate The bounty runs on Somnia Tokyo testnet, chain ID 50383. Builders need test USDso for margin and STT for gas. Development funds can be requested from the team through a ticket or support, using a separate build wallet. If you’re also participating in Perps Arena, pay attention to this: bounty USDso must not be moved into your Arena account. It breaks the rules, and the presentation mentions accounts already being banned for doing it. 4️⃣ What your bot can actually do Your USDso margin stays in your dreamDEX account. The bot uses a separate key to sign orders and pay gas, with permissions granted per market. It can place, cancel and reduce orders. It cannot withdraw your funds, change leverage or arm stop orders. There’s another detail worth knowing: TP/SL managed by the bot depends on the bot staying online. Those stops aren’t armed on the exchange or displayed in the app like app-set TP/SL. Having a bot connected doesn’t mean every part of managing the position happens automatically. You need to understand which actions the bot handles and what happens if it stops running. 5️⃣ Builders are already finding useful things According to the presentation, the first 48 hours brought around 75 join requests and more than 20 reports. One builder had three findings accepted from a single ticket: missing documentation on quantity scaling, gas requirements and an error absent from the published ABIs. Another published a full feedback repository with reproducible tests. I’m glad these examples were included. They show exactly what a useful contribution looks like and give the next developer a better starting point. The slides also cover partial fills, different decimals across markets and gas limits that can cause orders to fail. These are practical issues people encounter while trying to get a bot working.