I built SODAX Terminal across three sessions over about a month. It's a professional trading terminal with cross-network swaps, tokenized equities, limit orders, lending and borrowing, staking, leverage-yield vaults, a cross-network portfolio, and live protocol analytics. 3,648 lines of app code, 38 SDK hooks, 21 chains in config, 28 money-market reserves live.
The goal was specific: a viewer thinks "this looks like a real product I'd deposit into" and a builder thinks "I could ship this."
Session one was 37 minutes. Scaffold to working product with analytics, trading, earn, and portfolio tabs. About five minutes per major feature area. The ordering mattered: analytics came first because it needs no wallet. The app is useful and demonstrable before a single connection exists. Every tab after that layered onto something that already worked.
Session two is the better story because it starts with the build being thrown out. The first version had 2,500 lines of hand-written CSS, a DIY dropdown/modal/token-picker, and a hand-drawn SVG chart. The feedback was blunt: it looks cheap. The diagnosis: the design decisions were fine, the problem was hand-rolling things that have well-built libraries. Bespoke primitives miss the details that read as quality: focus traps, portalling, keyboard semantics, tooltip engines. No amount of restyling fixes that. So it got rebuilt on Tailwind v4, shadcn/ui on Base UI, TanStack Table, and ECharts. Same afternoon.
SODAX SDK
Hi there! I'm Min, founder of SODAX.
We are excited to share the first stable release candidate for the SODAX SDK with Product Hunt. Our team has been actively developing software to support execution coordination across blockchain networks for more than 8 years, recently rebranding as SODAX we have shifted focus to opening up these tools to developers. We made this move because every builder we talked to was stuck gluing together bridges, wrapped assets, and one-off integrations just to let users act across blockchain networks with the composability expected. SODAX is the execution system that takes care of that coordination: solvers quote and fill, we coordinate routing and settlement, and one integration gives builders reach across the stablecoin, RWA and crypto assets of 20+ networks.
Beyond access to assets, the SDK also provides all of the context to build transaction flows for swapping between these assets, providing collateral and borrowing against it, and deposits into specific yield-bearing vaults.
In the SDK’s development, we have also taken care to ensure that all of these features are available to developer’s own workflows. The documentation has been written with agentic support in mind so that Claude, Cursor and other agentic tooling can readily understand the system, aided further by our Builders MCP server. The full logic of the SDK can be connected to your agent to quickly, using this MCP, to build and deploy.
We invite all developers to explore our release, a full walkthrough of a vibe coding workflow with the SDK and to share your feedback on our cross-network execution system. Our team will be in the comments, ready to answer your questions.
Thank you for visiting and reading,
Min Kim
Is this audited / how do you handle security.
No offense but there are so many exploits in the space recently, how do you protect your user?
SODAX SDK
@leo404 Thanks for commenting, and yes, with recent events security is of massive concern for developers, users and us.
To start, SODAX is non-custodial and the protocol never takes custody of user funds. Solvers only fill intents, don't custody of your assets in between, and failure modes should an operation not succeed are built into the infrastructure. If a user can't receive the promised quote, then the operation will fallback to their originating wallet.
SODAX also ensures that all contracts are audited, both externally, and continually tested from within. For the specifics on audits, the most current info lives in our docs at docs.sodax.com and I am happy to point you to the right page or specific audit if you can't find it.
@jhooley I see okay, trust is earned so I will keep you guys on my radar. Best of luck !
SODAX SDK
@leo404 And all the best to you building with the SDK.
If you have any further questions or feedback, please feel free to reach out.
SODAX SDK
@leo404 Thanks for checking us out. Building on what @jhooley mentioned, the entire industry is currently facing an unprecedented volume of exploits. Third party audits are essential, but they are just one component of our broader security framework. We continuously invest in advanced threat detection tools, employing real time monitoring along with automated guardrails and circuit breakers to mitigate risk and minimize impact.
How is this different from a bridge?
The tech behind is sounds interesting but why should anyone use sodax and not any exisitng bridge?
Good luck with the launch
SODAX SDK
@hanbaobaozen Thanks for commenting.
A bridge just moves a token from network A to network B and stops there. SODAX coordinates the whole action end to end: a user states what they want (for instance a specific swap, or to swap and then deposit into a particular yield-bearing vault), and then independent solvers compete to fill it. SODAX handles transactions routing flows and settlement across 21 networks.
As a developer, you can fine tune what you want to enable for users through this system and we hope it enables developers to be creative in their design choices with more infrastructure to lean back on.
@jhooley Gotcha, I will check it out
SODAX SDK
@hanbaobaozen You will find me here all day if you have any further questions or feedback while you do.
SODAX SDK
@hanbaobaozen To add to what @jhooley mentioned, bridge is one part of the cross-network execution system. SODAX is compatible with existing bridges like Layerzero and Circle's CCTP. However, we also have our own bridge for networks not supported by those existing bridges.
How much customization do developers get over the transaction flow and UI?
SODAX SDK
@tumblar_kevin Hi there,
Full customization. The SODAX SDK provides the infrastructure to build the transaction flows that the user desires. These could be simple asset swaps, lending and borrowing, deposits into particular vaults, or some combination of these steps depending on the requirements.
As for UI, this is entirely for the user to decide for their application. SODAX does provide some tooling (an app-kit) to help build an app if required, but for an already designed app SODAX will usually just be back-end infrastructure. Though we are always thankful of a branded lock-up for features powered by SODAX.
Overall the SDK is free-to-use unopinionated infrastructure for digital asset flows. You can see case studies for some of the products using the SDK on https://www.sodax.com/partners#case-studies
SODAX SDK
@tumblar_kevin Thanks for checking us out. As @jhooley mentioned, full customization. If there's anything you need while building, please let us know. We'd love to get feedback and work with you to improve.
SODAX SDK
One of the things SODAX nails is reducing the amount of chain-specific infrastructure developers need to manage themselves. The SDK and Builders MCP bring that execution layer into both traditional and agentic development workflows.
Mailwarm
Hi Sodax team, congrats on your launch and I wish y'all the best today🙌
SODAX SDK
@daniel_nwankwo Thank you Daniel.
Please feel free to try our SDK out. Our hope is that it is user friendly for anyone to be able to build production-ready applications 🙏
SODAX SDK
@daniel_nwankwo Thank you for checking us out and leaving kind words. Have a great day!