@meteora-ag/dynamic-bonding-curve-sdk 1.5.11 → 1.5.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (8) hide show
  1. package/README.md +2 -2
  2. package/dist/index.cjs +802 -1405
  3. package/dist/index.cjs.map +1 -1
  4. package/dist/index.d.cts +735 -1349
  5. package/dist/index.d.ts +735 -1349
  6. package/dist/index.js +798 -1401
  7. package/dist/index.js.map +1 -1
  8. package/package.json +1 -1
package/README.md CHANGED
@@ -37,8 +37,8 @@ The generic flow of how Dynamic Bonding Curve works is as follows:
37
37
  1. The partner creates a config key for the pool.
38
38
  2. The creator creates a pool.
39
39
  3. The pool is tradeable on the Dynamic Bonding Curve.
40
- 4. Meteora's migrator service migrates the pool to either DAMM V1 or DAMM V2 based on the config key once the quote reserve is more than or equals to the migration quote threshold.
41
- 5. The graduated pool is tradeable on either DAMM V1 or DAMM V2.
40
+ 4. Meteora's migrator service migrates the pool to DAMM V2 based on the config key once the quote reserve is more than or equals to the migration quote threshold. Existing DBC pools created with `MigrationOption.MET_DAMM` can still graduate to DAMM V1; new configs and new pools cannot use that option.
41
+ 5. The graduated pool is tradeable on DAMM V2. Existing DAMM V1-graduated pools remain tradeable on DAMM V1.
42
42
 
43
43
  ## Flow of migration
44
44