If you are Still using Omniston v1beta7? It’s time to migrate.
STONfi is planning to discontinue v1beta7 support on October 1, with v1beta8 now being the version to move to.
And this isn't simply a version number change.
v1beta8 changes how Omniston models the trading lifecycle.
Instead of thinking mainly in terms of a quote followed by trade statuses, the newer API separates the flow into clearer protocol objects: RFQ → Quote → Swap or Order → Execution.
That matters because orders are now treated as persistent objects with their own lifecycle, while executions can represent individual settlement progress, including partial fills.
There are also terminology changes builders need to account for, such as input/output replacing bid/ask, integrator replacing referrer, and separate types for chain addresses and asset IDs.
So if you're still using v1beta7, this isn't just about changing an API endpoint.
It's about updating your integration to the newer Omniston execution model.
The migration guide walks through the major protocol, terminology and flow changes so builders can make the transition before support ends.
v1beta7 → v1beta8 migration guide: ↓↓
https://docs.ston.fi/developer-section/omniston/v1beta7-to-v1beta8-migration-guide
If you're building with Omniston, now is a good time to check which version your integration is actually running.
$ETH #BTC Price Analysis# $XRP #Altcoin Season#
STONfi is planning to discontinue v1beta7 support on October 1, with v1beta8 now being the version to move to.
And this isn't simply a version number change.
v1beta8 changes how Omniston models the trading lifecycle.
Instead of thinking mainly in terms of a quote followed by trade statuses, the newer API separates the flow into clearer protocol objects: RFQ → Quote → Swap or Order → Execution.
That matters because orders are now treated as persistent objects with their own lifecycle, while executions can represent individual settlement progress, including partial fills.
There are also terminology changes builders need to account for, such as input/output replacing bid/ask, integrator replacing referrer, and separate types for chain addresses and asset IDs.
So if you're still using v1beta7, this isn't just about changing an API endpoint.
It's about updating your integration to the newer Omniston execution model.
The migration guide walks through the major protocol, terminology and flow changes so builders can make the transition before support ends.
v1beta7 → v1beta8 migration guide: ↓↓
https://docs.ston.fi/developer-section/omniston/v1beta7-to-v1beta8-migration-guide
If you're building with Omniston, now is a good time to check which version your integration is actually running.
$ETH #BTC Price Analysis# $XRP #Altcoin Season#
