Submit Rebalancing Order Intents

Submit portfolio allocation intents that the protocol executes on the next rebalancing cycle.

Prerequisites

• A deployed vault (see Vault Deployment);
• Portfolio file generated by your strategy.

Use when allocations can be public.

Intent Submission

orion submit-order \
  --order-intent-path order_intent.json \
  --fuzz

Encrypts allocation details; the optional --fuzz flag provides additional obfuscation to the intent without meaningfully modifying the underlying strategy.

Notes

• Intents are collected and executed at the next rebalance, enabling bundling, batching, and netting.
• Ensure portfolio inputs match the expected schema for your strategy/vault.

Expected Portfolio File Schema

Column Name	Type	Description
address	string	Token contract address (checksummed).
percentage_of_tvl	decimal	Percentage of total vault value to allocate (0-100).

{
  "0x5BA134aBc8BA11Cf7868F4Dfb02497A3f1544Eb5": 0.25,
  "0x490a81a1939762E6AA87C68C346A0be5E21B466c": 0.02,
  "0x8A359aAfbf0DF440B34bb97445d981C1944CD053": 0.015,
  "0xbD39EeAd46c3f28EB8309A74641ab9Ef947FFc83": 0.0255,
  "0x6b2741F97Ea3EA9C5bFeEa33575d1E73c4481010": 0.06,
  "0x58f7aaE7B2c017F74B7403C9e89537f43B13bE87": 0.40,
  "0x28345814d210f2FE11C8de03236f0Ba7b603D282": 0.22,
  "0x484fF4FB5Ca053b47e5e0490C363b5ea38bB2adF": 0.0095
}

Tip:

• For transparent vaults, these values will be visible onchain once submitted.
• For private vaults, values are encrypted and only known to curators.