@perena/vault-sdk 1.0.29 → 1.0.31

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 (4) hide show
  1. package/README.md +1 -1
  2. package/dist/index.d.ts +720 -14
  3. package/dist/index.js +684 -130
  4. package/package.json +2 -1
package/README.md CHANGED
@@ -411,7 +411,7 @@ The builder auto-detects external liquidity slot 0 and, when it finds an active
411
411
  Marginfi position for the asset, emits `execute_withdraw_from_external` instead
412
412
  of `execute_withdraw`. That route can pull from the vault's external position in
413
413
  the same transaction, so it draws on far more liquidity than the plain
414
- `execute_withdraw`: the external-liquidity integrity service keeps only ~1% of
414
+ `execute_withdraw`: the external-liquidity integrity service keeps only ~0.5% of
415
415
  each holding in the vault's own token account (see
416
416
  `DEFAULT_TARGET_LOCAL_BPS`) and deploys the rest into Marginfi, so a plain
417
417
  withdrawal is capped at that small local buffer and will fail for anything