
Just because we've reached mainnet doesn't mean we've stopped improving. Quite the contrary.
With the platform now live, we're receiving daily feedback and gaining insights from real usage. This gives us an opportunity to identify areas that need extra attention, refine existing functionality, and push the platform beyond what we initially imagined.
A lot of that work has gone into the details: making swaps more predictable, improving how funds and channels are managed, and ensuring the infrastructure behaves as expected in production.
Mainnet remains invite-gated for now, but development certainly hasn't slowed down. Here's what we've been working on throughout October.
One area we've continued refining is how orders and swaps are handled, particularly when it comes to amounts, partial fills, and order completion.
Previously, quote amounts could be rounded to match the price precision. This meant that the precision used for a price could also affect the amount being traded, potentially creating small discrepancies between an order's requested amount and the sum of its individual fills.
That's now handled differently. Prices and quote amounts use separate precision rules: prices retain the precision defined for them, while quote amounts use the decimal precision of the quote currency. Each individual fill is calculated using its actual execution price multiplied by the filled base amount, with the result rounded down.
In practical terms, this means order values and individual fills are represented more accurately, so the amounts reported throughout a trade are consistent with how it was actually executed.
We've also changed how orders behave when they're only partially filled. Take an order that is filled as far as the available liquidity allows, with a remainder too small to go back on the order book. Previously, it showed as cancelled, even though part of it had executed. Now, the order completes once the executed portion has settled, and the unfilled remainder is released.
Another important improvement concerns the visibility of funds during a swap.
A swap isn't necessarily a single transaction that happens all at once. Depending on the route and the underlying channel states and operations, funds move through several stages before the trade is fully settled.
Previously, it wasn't always clear what had happened to your funds after a failed swap: whether they had been sent, returned, or were still involved in an ongoing settlement process.
Each swap now reports a dedicated funds status that shows where your funds stand at every stage:
A failed swap doesn't necessarily mean that nothing happened. Some failures never touch your funds; others need part of the settlement to finish before your funds are released back to you. Because swaps are secured by hashed timelock contracts, locked funds end up either settled or returned to you.
With this status now explicit, the app and external API integrations can respond correctly to each outcome, and you can see at a glance whether any action is needed.
Payment channels are a fundamental part of how Hydranet works. They provide the infrastructure that makes fast, cross-chain trading possible, and managing their capacity efficiently is essential to keeping the platform running smoothly.
One change concerns liquidity rented from Titans, the nodes that run the order book and rent out inbound liquidity to users' channels. Previously, rented liquidity could remain available beyond its lease period until the next scheduled lease check.
Now, payments through a leased channel extend the lease. Once the lease expires, the Titan can reclaim its liquidity as soon as your node is online. Only the Titan's own liquidity is reclaimed, never your funds.
In short: channels you actively use keep their rented liquidity; idle ones return it to the Titan once the lease ends, instead of keeping it longer than necessary. For Titans, this means more predictable control over the capital they make available.
We've also changed how the infrastructure evaluates channel capacity when matching and executing orders. If your channel lacks the sending or receiving capacity for an order, you now get a clear message before execution instead of a failed swap. You can then reduce the order size, add funds to your channel, or rent more inbound liquidity.
These improvements help reduce failed executions and make better use of the liquidity already available across the network.
October has been another month of turning feedback into improvements.
The improvements above are just a few examples from a much broader set of updates across the web app, backend, trading engine, and liquidity services. We've also continued work on error reporting, channel lifecycle management, and the reliability of communication between different parts of the platform.
Mainnet remains invite-only while we continue monitoring and addressing issues as they arise. We want to expand access responsibly and ensure that the infrastructure is ready to support more users and more trading activity. To get in, ask an existing mainnet user for an invite code and redeem it in the web app. Never pay for an invite code, and remember that the team will never DM you first.
For those who want to follow how things are developing, our stats page at stats.hydranet.ai remains the place to keep an eye on the latest trading activity and history. So far, mainnet has seen close to 70,000 trades and nearly 1 million USD in volume.
And don't forget to follow our official X accounts for announcements and updates:
For questions and feedback, join us on Discord: discord.gg/hydranet.
Reaching mainnet was a major milestone, but it's only the beginning. We'll keep building.