The key to Atomic Orders is not turning one pool of capital into many pools, but instead allowing the same yet-to-be-filled Vault liquidity to wait across multiple markets simultaneously for better matching opportunities. TermMax V2 summarizes the problems of V1 as Liquidity Fragmentation, Low Turnover, and Idle Capital; this indicates that what the term market faces is not simply “whether there’s money,” but whether capital can participate in more bids with different conditions without being re-lent redundantly.
You can understand this design along a timeline. Unmatched capital can be routed into base yield sources such as Aave or an ERC-4626 Vault to reduce idle time while waiting for fixed-rate orders; before any match occurs, the same Vault liquidity can be shown to multiple markets. Then, as soon as one market is matched, the other related orders will be atomically and synchronously reduced. What’s being added here is bid visibility and the breadth of capital competition—not duplicating the actual lendable capital into multiple copies.
This distinction is crucial for liquidity providers. If the interface displays depth across multiple markets at the same time, it should not be directly summed into a total that can be delivered concurrently; the truly lendable amount remains the original Vault liquidity. Atomic’s role is to prevent one market from filling first while other orders continue to incorrectly promise the same capital. It improves how capital participates across multiple candidate markets, but it does not create new capital out of thin air.
There’s one more layer that can’t be missed: when unmatched capital enters an external base yield source, capital efficiency and external protocol risk will both appear. When reading the design of @TermMax , you can split “visible depth,” “actual capital,” and “external dependency” into three columns to evaluate them separately. Only then won’t you misread higher presentation as a liquidity expansion with no cost.
#TermMax
You can understand this design along a timeline. Unmatched capital can be routed into base yield sources such as Aave or an ERC-4626 Vault to reduce idle time while waiting for fixed-rate orders; before any match occurs, the same Vault liquidity can be shown to multiple markets. Then, as soon as one market is matched, the other related orders will be atomically and synchronously reduced. What’s being added here is bid visibility and the breadth of capital competition—not duplicating the actual lendable capital into multiple copies.
This distinction is crucial for liquidity providers. If the interface displays depth across multiple markets at the same time, it should not be directly summed into a total that can be delivered concurrently; the truly lendable amount remains the original Vault liquidity. Atomic’s role is to prevent one market from filling first while other orders continue to incorrectly promise the same capital. It improves how capital participates across multiple candidate markets, but it does not create new capital out of thin air.
There’s one more layer that can’t be missed: when unmatched capital enters an external base yield source, capital efficiency and external protocol risk will both appear. When reading the design of @TermMax , you can split “visible depth,” “actual capital,” and “external dependency” into three columns to evaluate them separately. Only then won’t you misread higher presentation as a liquidity expansion with no cost.
#TermMax