Transaction Cost Considerations
Transaction costs in on-chain execution decompose into two components that can be analyzed separately, even though both can apply to the same trade:
- Execution cost (gas), driven by computational complexity
- Market impact (slippage), driven by trade size and liquidity
These components have different drivers and should be reasoned about on their own terms.
Gas Costs: Computation-Driven
Gas represents the cost of executing transactions on-chain.
- Operation-based pricing. Each instruction (transfers, swaps, contract calls) consumes gas.
- Independent of notional size. Moving $1,000 or $1,000,000 through the same execution path incurs the same gas cost.
- Scales with computational complexity. More steps, interactions, or contracts increase total gas usage.
As a result, gas behaves like a fixed cost per execution path, not a function of capital deployed.
Market Impact: Liquidity-Driven
Market impact captures how execution affects price.
- Market impact - Large trades can move prices, especially in less liquid markets.
- Price deviation - The execution price may differ from the expected price due to market conditions.
- Liquidity constraints - Insufficient liquidity can result in worse execution prices.
Orion addresses slippage through:
- Slippage controls - Hard limits on acceptable price deviation during execution.
- Batching and netting - Grouping transactions reduces individual market impact.
- Execution buffers - Absorbing small price differences between planning and execution.
See Slippage and Buffer for more details on how Orion manages execution risk.
Cost Efficiency Through Orion's Architecture
Orion's design further optimizes transaction costs through:
- Bundling - Multiple operations in a single transaction reduce total gas usage.
- Batching - Sharing gas costs across multiple vaults and participants.
- Netting - Internal matching of buy/sell orders before external execution reduces unnecessary trades.
These mechanisms are intended to keep transaction costs comparatively lower and more predictable relative to isolated per-vault execution, though actual costs still depend on network conditions and liquidity.