yo guys, I’m back in da hood
due to a few issues with my old account @censarboyzzz (if you remember or not)
btw this is my new one. if you’re a Somniacs, researcher or airdrop hunter, let’s connect and interact with each other. always happy to meet more people in the space ^^
761
a decentralized exchange can still have centralized points of failure in its trading interface. if an API or WebSocket connection drops, can users still monitor and manage their open orders reliably? onchain settlement alone doesnt guarantee an uninterrupted trading experience
10
I think, fast order execution gets attention, but cancellation handling deserves the same scrutiny. during sudden market moves, traders may cancel dozens of orders at once. how does dreamdex handle cancellation spikes without leaving users with stale or unexpected open orders?
12
“3ms” execution on Somnia Tokyo is impressive. but how much of the actual trading process does that cover? order submission, matching, confirmation and finality are different stages. breaking down end-to-end latency would give traders a clearer picture of dreamdex performance.
1
1
38
fast block production doesnt guarantee accurate data for users. if indexers lag behind or miss events, dashboards can show outdated balances, volumes or positions. for defi apps, that can lead to poor decisions. Somnia data layer needs to scale as seriously as its execution layer
1
30
for newcomers, dreamdex interface can feel overwhelming. order books, margin settings and multiple trading options need clearer navigation. a simpler layout would make the platform more accessible.
btw I’m top 222 despite having tried so hard, perhaps I should stake everything.
2
2
35















