$NVDAB TermMax’s fixed-rate is like a thin sheet of ice—after three hours on it, I’m not too confident about going heavy.
I ran TermMax against Pendle and Notional under the same settings for three hours. TermMax’s fixed-rate quotes look good on the front end, but in practice the execution slippage is noticeably higher than Pendle’s AMM. The order book depth is insufficient: even placing a medium-sized order can skew the annualized rate by about 0.4 percentage points. More incentives are pushed to front-end interaction for the TERM token, but the backend market-making incentives don’t form a closed loop. It didn’t follow Notional’s older playbook; its liquidity structure is closer to an early-stage order-book DEX.
The main issues are concentrated around maturity handling. The assets at TermMax maturity require manual redemption; unlike Notional, they don’t automatically roll into the next term. Gas costs across multiple accounts add up—notably so for cross-chain deployments. Compared with Aave’s flexible rates, TermMax’s term certainty is an advantage, but the added redemption path means the real net annualized return will be lower. Mainnet and L2 settlement parameters aren’t unified: with the same collateralization ratio, trigger thresholds differ across chains, making strategy deployment very easy to mess up.
Among competitors, Pendle keeps arbitrageurs by separating YT and PT, while TermMax’s order book discourages them during the cold-start phase. On the other hand, TermMax supports a wider range of collateral assets than Notional; long-tail and medium-to-long-tail assets can be listed. If this liquidity gets built up, the governance value of the TERM token might become more apparent. But currently there are too few governance proposals—the token is more like a reward voucher.
My take: TermMax suits people who are willing to tolerate a bit of slippage in exchange for fixed rates. High-frequency arbitrageurs and users with large capital will likely feel uncomfortable. The direction is fine, but the execution is short by half a step—liquidity and maturity automation still need work. #termmax @TermMax
I ran TermMax against Pendle and Notional under the same settings for three hours. TermMax’s fixed-rate quotes look good on the front end, but in practice the execution slippage is noticeably higher than Pendle’s AMM. The order book depth is insufficient: even placing a medium-sized order can skew the annualized rate by about 0.4 percentage points. More incentives are pushed to front-end interaction for the TERM token, but the backend market-making incentives don’t form a closed loop. It didn’t follow Notional’s older playbook; its liquidity structure is closer to an early-stage order-book DEX.
The main issues are concentrated around maturity handling. The assets at TermMax maturity require manual redemption; unlike Notional, they don’t automatically roll into the next term. Gas costs across multiple accounts add up—notably so for cross-chain deployments. Compared with Aave’s flexible rates, TermMax’s term certainty is an advantage, but the added redemption path means the real net annualized return will be lower. Mainnet and L2 settlement parameters aren’t unified: with the same collateralization ratio, trigger thresholds differ across chains, making strategy deployment very easy to mess up.
Among competitors, Pendle keeps arbitrageurs by separating YT and PT, while TermMax’s order book discourages them during the cold-start phase. On the other hand, TermMax supports a wider range of collateral assets than Notional; long-tail and medium-to-long-tail assets can be listed. If this liquidity gets built up, the governance value of the TERM token might become more apparent. But currently there are too few governance proposals—the token is more like a reward voucher.
My take: TermMax suits people who are willing to tolerate a bit of slippage in exchange for fixed rates. High-frequency arbitrageurs and users with large capital will likely feel uncomfortable. The direction is fine, but the execution is short by half a step—liquidity and maturity automation still need work. #termmax @TermMax
