Practical Analysis of Kraken's Migration from Native to Synthetic Trading Pairs

Share
A financial trading screen with a candlestick chart
Contents

At a glance

A detailed examination of Kraken's planned transition from native to synthetic trading pairs, focusing on reconciliation processes, order state implications, availability considerations, execution comparisons, and the balance versus pair listing distinctions.

Understanding Reconciliation in Kraken’s Transition

Reconciliation is a critical process in Kraken's upcoming replacement of approximately 176 native trading pairs with synthetic pairs. This process involves ensuring that account records, open orders, and balances remain accurate and consistent throughout the migration. Since Kraken plans to cancel all remaining native pair orders from November 6 to 9, reconciliation must verify that no residual native pair orders persist after the delisting. It is also essential to confirm that balances remain intact, as the exchange asserts assets remain unaffected despite delisting. Proper reconciliation prevents discrepancies between the actual holdings and what is displayed on user interfaces, enabling a seamless transition to synthetic pairs while maintaining trust and operational integrity. [1]

Order State and Management Amid Pair Replacement

The order state during the migration is a significant concern for Kraken users. Kraken has scheduled a cancel-only phase beginning November 6 at 14:00 UTC, followed by full cancellation of remaining orders and native pair delisting through November 9. Importantly, Kraken states that "Open orders do not carry over to the synthetic pairs," which means every open order placed on native pairs will be voided rather than transferred automatically. This approach ensures that users have clear knowledge of their order statuses and can avoid unintended executions on synthetic pairs. It also means active traders need to monitor their orders closely and possibly recreate them once synthetic pairs become available at the end of November 9. [1]

Availability Considerations During the Migration Window

Availability of trading pairs and order functionalities will undergo scheduled disruptions in the November 6 to 9 window. Native pairs will enter a cancel-only mode starting 14:00 UTC on November 6, limiting new order placements to cancellations only, which helps orderly wind down native pair activity. Subsequently, Kraken plans to cancel any remaining open orders and delist native pairs entirely by November 9. No orders for native pairs will remain active beyond this period. Synthetic pairs are planned for listing at the end of November 9, restoring availability for trading those instruments. A separate November 10 maintenance window is indicated on the Kraken status card, but it should not be interpreted as overlapping or replacing the migration timeline regarding pair availability. [1]

What to compare when a replacement pair appears

Compare the published trading rules for the old and replacement pairs. Record the symbol, minimum order size, price increment and supported order types. Check which of those settings your interface or API actually exposes. A matching symbol can make the replacement look familiar, but the old order identifier will not move with it. If you use a trading integration, distinguish a response that accepts a request from a confirmed fill. Save the exchange’s response and check the order history before repeating a request whose result is uncertain. Kraken’s notices set out the listing timetable. They give no basis for estimating execution speed, depth or spreads on the replacement pairs. [1]

Pair listings and account balances

Kraken says the underlying assets will remain on the platform and that changing the pair type will leave balances unaffected. Check the pair list and the account ledger separately. A pair can disappear from the trading screen while both assets still appear in the account. A partial fill before cancellation can also change balances independently of the listing change. To reconcile those movements, match executed quantities and fees to individual trade records. The announced change concerns the selected trading pairs. The notices do not establish the availability of unrelated pairs, funding methods or withdrawals. [1]

Summary and User Implications for Upcoming Changes

Kraken’s transition from native to synthetic pairs involves a carefully structured timeline enforcing order cancellation and pair delisting before new synthetic pairs launch. Users must actively monitor their open orders starting November 6, as open orders will not carry over and must be manually recreated on synthetic pairs. The reconciliation process aims to preserve account integrity by ensuring balances remain intact throughout. Availability will be interrupted in the transition window but restored by synthetic pair listings planned for November 9. Understanding the distinction between asset balances and pair listings helps users navigate the migration without fearing balance loss. Careful attention to these details will facilitate a smoother experience during this significant structural change on Kraken.

Before the scheduled cutoff, export the orders for the affected pairs. Keep the pair symbol, order identifier, side, quantity and filled quantity together. An order can be partially filled before its remainder is cancelled, so compare the fills and the remaining quantity separately. After the transition, reconcile the trade history against the balance history. If a replacement pair appears, check its trading rules and available order types before assuming that an old order could be recreated with the same terms. [1]

Evidence & sources

Source record: · Checked:

Record limits · All migration events described are future plans and have not been completed as of November 3, 2026.

  1. [1]Source reported

    Kraken plans to replace affected native pairs and says open orders do not carry over.

    Supporting excerpt: Kraken support notice

    Original quotation

    Open orders do not carry over to the synthetic pairs.
    Kraken support notice ↗

    Source language: EN · Captured Nov 3, 2026