Versions and migrations
Separate deployed DEX contract generations from npm SDK upgrade paths.
Contract generations and npm package versions answer different questions. Select the deployed pool/router first, then use the matching wrapper in your installed @ston-fi/sdk package.
Contract integration
DEX v2 setup and current operations use API router metadata with the npm SDK 2.x family.
DEX v1 integration targets existing v1 contracts; it is not a requirement to install npm package major 1.
DEX v1 to v2 integration explains changing the target contract generation.
Contract reference remains available for both generations.
npm SDK upgrades
For npm 1.x/2.x package changes, use the official SDK changelog, independently of which deployed contract generation you use.
When updating a wrapper, keep the contract addresses, metadata, amounts, and network aligned with the selected deployment.
Last updated