3 hours ago
Found a short PDF that documents what appears to be a persistent pricing inconsistency on Changelly when using Bitcoin as the source asset in a swap.
It seems that when an older, deprecated Node backend is manually injected through the browser console, the exchange interface begins quoting significantly higher-than-expected amounts in the destination currency — typically around 27% more than the current market rate.
For example:
Swapping the equivalent of $2000 in BTC would normally return ~$2000 worth of ETH (or other altcoins),
but with the legacy node active, the quoted return jumps to around $2540, effectively creating a one-sided gain in value.
This discrepancy doesn't affect other input currencies — it seems to be specific to BTC as the base asset.
Once the swap is completed and the altcoin received, the funds can, in theory, be exchanged back into BTC, allowing for the process to be repeated in a loop (although the exact profitability per iteration would vary depending on fees and timing).
The full explanation, including the script used to load the older backend and a working example, is documented in this write-up:
PDF:
It seems that when an older, deprecated Node backend is manually injected through the browser console, the exchange interface begins quoting significantly higher-than-expected amounts in the destination currency — typically around 27% more than the current market rate.
For example:
Swapping the equivalent of $2000 in BTC would normally return ~$2000 worth of ETH (or other altcoins),
but with the legacy node active, the quoted return jumps to around $2540, effectively creating a one-sided gain in value.
This discrepancy doesn't affect other input currencies — it seems to be specific to BTC as the base asset.
Once the swap is completed and the altcoin received, the funds can, in theory, be exchanged back into BTC, allowing for the process to be repeated in a loop (although the exact profitability per iteration would vary depending on fees and timing).
The full explanation, including the script used to load the older backend and a working example, is documented in this write-up:
PDF: