ipor-fusion 4.0.0.dev319__tar.gz → 4.0.0.dev327__tar.gz

{ipor_fusion-4.0.0.dev319 → ipor_fusion-4.0.0.dev327}/AGENTS.md

@@ -79,6 +79,11 @@ supports only that release, so there is no live-pair generation. It needs
 `IPOR_FUSION_CONTRACTS_DIR` at that revision; a checkout without `node_modules` also
 needs `IPOR_FUSION_FOUNDRY_REMAPPINGS` for OpenZeppelin. `test_crosschain_ccip_events.py`
 mirrors the CCIP event registry from a checkout at its own `CONTRACTS_REVISION`.
+`test_simulate_examples_crosschain.py` runs the crosschain example against the deployed
+(unconfigured) release factory and fuses: it builds the executor and dispatcher creation
+codes from the same checkout, linked against the example's `RELEASE_LIBRARIES`, proves the
+deployed runtimes are that build, and needs `ARBITRUM_PROVIDER_URL`,
+`HYPEREVM_PROVIDER_URL` and `IPOR_FUSION_CONTRACTS_DIR` (a missing one is an `_live` skip).
 `test_solidity_compiler.py` unit-tests that compiler helper (`tests/_foundry.py`)
 offline, with `forge` and `git` mocked. The checkout-based tests above skip when their
 external prerequisites are unavailable. `test_hypercore_live.py`,

{ipor_fusion-4.0.0.dev319 → ipor_fusion-4.0.0.dev327}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ipor-fusion
-Version: 4.0.0.dev319
+Version: 4.0.0.dev327
 Summary: The IPOR Fusion SDK for Python
 Project-URL: homepage, https://ipor.io
 Project-URL: repository, https://github.com/IPOR-Labs/ipor-fusion.py
@@ -392,6 +392,10 @@ ever signed or broadcast.
 - [External-state margin leg](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/external_state_margin_leg_base.py) — a vault whose capital
   sits off-chain: typed market-50 substrates, a dual-custodian propose/confirm marking the NAV,
   the scheduled-withdrawal prep an alpha performs, and a mismatched confirmation being rejected.
+- [Crosschain CCIP vault, Arbitrum hub and HyperEVM spoke](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/crosschain_ccip_usdc_arbitrum_hyperevm.py) —
+  the released crosschain contracts as deployed: configure the CCIP factory pair as its owner,
+  create both vaults and the executor, wire the crosschain market and NAV pre-hook, deploy the
+  dispatcher, then supply → attest → DEPOSIT → REDEEM → recall → claim USDC (preview feature).
 - [HyperCore vault on the official deployment](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/hypercore_vault_official_deployment_hyperevm.py) —
   a HyperEVM vault that trades on Hyperliquid Core (market 55, preview): wiring the published
   HyperCore fuses, pre-hooks and grants on a factory clone, and building the Core leg (bridge,
@@ -404,6 +408,17 @@ uv run python examples/advanced_euler_v2_credit_market_base.py
 uv run python examples/external_state_margin_leg_base.py
 ```
 
+The crosschain example needs Arbitrum and HyperEVM archive RPCs and the executor and dispatcher
+creation codes built with Foundry from the contracts release it pins; run without them, it prints
+the `forge inspect` commands that build them:
+
+```bash
+export ARBITRUM_PROVIDER_URL="https://arb-mainnet.g.alchemy.com/v2/YOUR_KEY"
+export HYPEREVM_PROVIDER_URL="https://YOUR_HYPEREVM_ARCHIVE_NODE"
+export CCIP_EXECUTOR_CREATION_CODE_FILE=executor.hex CCIP_DISPATCHER_CREATION_CODE_FILE=dispatcher.hex
+uv run python examples/crosschain_ccip_usdc_arbitrum_hyperevm.py
+```
+
 No RPC key? `BASE_PROVIDER_URL=https://mainnet.base.org` (Base's public RPC) runs the examples out of
 the box — it supports `eth_simulateV1` and serves their pinned blocks. It is rate-limited, so use a
 dedicated archive node for repeated or CI runs.

{ipor_fusion-4.0.0.dev319 → ipor_fusion-4.0.0.dev327}/README.md

@@ -343,6 +343,10 @@ ever signed or broadcast.
 - [External-state margin leg](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/external_state_margin_leg_base.py) — a vault whose capital
   sits off-chain: typed market-50 substrates, a dual-custodian propose/confirm marking the NAV,
   the scheduled-withdrawal prep an alpha performs, and a mismatched confirmation being rejected.
+- [Crosschain CCIP vault, Arbitrum hub and HyperEVM spoke](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/crosschain_ccip_usdc_arbitrum_hyperevm.py) —
+  the released crosschain contracts as deployed: configure the CCIP factory pair as its owner,
+  create both vaults and the executor, wire the crosschain market and NAV pre-hook, deploy the
+  dispatcher, then supply → attest → DEPOSIT → REDEEM → recall → claim USDC (preview feature).
 - [HyperCore vault on the official deployment](https://github.com/IPOR-Labs/ipor-fusion.py/blob/main/examples/hypercore_vault_official_deployment_hyperevm.py) —
   a HyperEVM vault that trades on Hyperliquid Core (market 55, preview): wiring the published
   HyperCore fuses, pre-hooks and grants on a factory clone, and building the Core leg (bridge,
@@ -355,6 +359,17 @@ uv run python examples/advanced_euler_v2_credit_market_base.py
 uv run python examples/external_state_margin_leg_base.py
 ```
 
+The crosschain example needs Arbitrum and HyperEVM archive RPCs and the executor and dispatcher
+creation codes built with Foundry from the contracts release it pins; run without them, it prints
+the `forge inspect` commands that build them:
+
+```bash
+export ARBITRUM_PROVIDER_URL="https://arb-mainnet.g.alchemy.com/v2/YOUR_KEY"
+export HYPEREVM_PROVIDER_URL="https://YOUR_HYPEREVM_ARCHIVE_NODE"
+export CCIP_EXECUTOR_CREATION_CODE_FILE=executor.hex CCIP_DISPATCHER_CREATION_CODE_FILE=dispatcher.hex
+uv run python examples/crosschain_ccip_usdc_arbitrum_hyperevm.py
+```
+
 No RPC key? `BASE_PROVIDER_URL=https://mainnet.base.org` (Base's public RPC) runs the examples out of
 the box — it supports `eth_simulateV1` and serves their pinned blocks. It is rate-limited, so use a
 dedicated archive node for repeated or CI runs.

{ipor_fusion-4.0.0.dev319 → ipor_fusion-4.0.0.dev327}/examples/README.md

@@ -38,6 +38,17 @@ transaction.
   brings the margin home and releases it for a user's scheduled withdrawal, then
   demonstrates the executor rejecting a confirmation that does not match its
   proposal.
+- [`crosschain_ccip_usdc_arbitrum_hyperevm.py`](crosschain_ccip_usdc_arbitrum_hyperevm.py) --
+  a crosschain vault on the released CCIP contracts as they are deployed: an
+  Arbitrum hub vault, a HyperEVM spoke vault and USDC over Chainlink CCIP. It
+  configures the deployed (unconfigured) factory pair as its owner would --
+  creation codes, asset, route, dispatcher deployment gas limit through the
+  factory's 24 h timelock, the creator allowlist -- creates both vaults and the
+  executor, wires the crosschain market (the four fuses, the executor and
+  spoke-vault substrates, the NAV pre-hook), deploys the dispatcher through the
+  factory's deployment ticket, then drives supply, two-key attestation, DEPOSIT,
+  REDEEM, recall and claim. The crosschain SDK is a preview feature. It has
+  extra prerequisites, listed below.
 - [`hypercore_vault_official_deployment_hyperevm.py`](hypercore_vault_official_deployment_hyperevm.py) --
   a vault that is itself a Hyperliquid Core account (HyperCore, market 55; a
   preview feature). No live vault uses the official HyperCore contracts yet, so
@@ -69,6 +80,21 @@ transaction.
   your Arbitrum archive RPC endpoint. Never commit it or share it.
 - `HYPEREVM_PROVIDER_URL` (required by the crosschain example) -- your HyperEVM
   archive RPC endpoint. Never commit it or share it.
+- `CCIP_EXECUTOR_CREATION_CODE_FILE` and `CCIP_DISPATCHER_CREATION_CODE_FILE`
+  (required by the crosschain example) -- files holding the hex creation code of
+  `CcipCrosschainExecutor` and `CcipCrosschainDispatcher`, built with Foundry
+  (`forge`) in a checkout of
+  [ipor-fusion](https://github.com/IPOR-Labs/ipor-fusion) at the release commit
+  the example pins (`RELEASE_COMMIT`), after `npm ci`. Run the example without
+  them and it prints the two `forge inspect` commands, which link the deployed
+  release libraries; it refuses codes whose hashes differ from the release's.
+
+The crosschain example's own test (`tests/test_simulate_examples_crosschain.py`)
+builds those codes itself, so it needs `ARBITRUM_PROVIDER_URL`,
+`HYPEREVM_PROVIDER_URL`, `forge` and `IPOR_FUSION_CONTRACTS_DIR` -- that checkout
+-- (plus `IPOR_FUSION_FOUNDRY_REMAPPINGS` when it has no `node_modules`). Pull
+request CI supplies neither the HyperEVM RPC nor the checkout, so it skips there;
+run it locally.
 
 ## Running