v3.6.9

v3.6.9 fixes how the SDK finds the addresses of a newly created vault. It applies to code that deploys vaults with FusionFactory.

Fixes

1. Vault addresses after creation

Before: the deployment flow took the new vault’s addresses from an eth_call preview made before broadcasting clone(). FusionFactory component clones use CREATE. Another clone transaction could land between the preview and the broadcast. The flow then configured, approved and deposited against addresses that the caller’s transaction did not create.

Now: FusionFactory.decode_clone_receipt() reads the vault and manager addresses from the creation events in the mined receipt. The quickstart and the deploy skill use it.

Impact: deployed addresses come from FusionFactory.decode_clone_receipt() on the receipt of the broadcast clone(). An earlier .call() preview is no longer part of the flow.

---

Upgrade with pip install -U ipor-fusion. Full changelog: v3.6.9 on GitHub.

These notes describe changes to the IPOR Fusion SDK. They are not operational or financial advice. Operators are responsible for testing changes against their own vaults and configuration before use.