Submit Intent (Rebalancing Orders)
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 (e.g., Parquet)
Plain (Transparent) Intent
orion submit-order plain \
--portfolio-path ../portfolio-manager/output/optimized/1.parquet
Use when allocations can be public.
Encrypted (Private) Intent
orion submit-order encrypted \
--portfolio-path ../portfolio-manager/output/optimized/1.parquet \
--fuzz
Encrypts allocation details; --fuzz adds obfuscation noise that masks exact values 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). |
Example Parquet content (converted to CSV for clarity):
address,percentage_of_tvl
0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2,30
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48,50
0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599,20
Tip:
- For transparent vaults, these values will be visible onchain once submitted.
- For private vaults, values are encrypted and only revealed at the next rebalance.