SIZE

SIZE is an on-chain credit marketplace that runs on Ethereum and Base, offering fixed-rate lending and borrowing with unified liquidity across different markets. Instead of operating as separate pools, deposits made to one market can be reused to lend on other markets, which improves capital efficiency. The protocol focuses on three main areas: secured loans, where borrowers provide collateral, unsecured credit, enabled through rate-limit hooks that allow lenders or curators to manage exposure, and auto-closing loans, which are self-repaying positions that terminate when unrealized profit reaches a set target. The key problem SIZE addresses is the poor rate predictability and fragmented liquidity in existing DeFi lending. Traditional money markets rely on variable rates, making stable planning difficult for both lenders and borrowers, while siloed pools often leave idle liquidity. By separating tranches of credit and sharing a common liquidity backend through a special deposit token, the protocol lets users earn fixed yield or borrow at stable costs across assets. Security remains a core concern. The protocol relies on trusted infrastructure including Aave as a user vault, Chainlink price feeds, and a Uniswap TWAP fallback oracle. Governance and protocol roles such as admin, keeper, and pause functions are noted as trusted parties, and liquidity gaps or high volatility can still trigger unforeseen liquidations. The protocol also excludes rebasing or fee-on-transfer tokens and depends on pre-vetted assets, which limits flexibility but reduces certain risks. Over the past six months, development has focused on refining the mechanism for creating and managing collections of markets, curators, and rate providers, replacing an earlier limit-order-copying feature. There is no public record of hacks, exploits, or successful attacks against the protocol during this period. A known caveat is that $SIZE, a separate token associated with an Arbitrum-based project, is not affiliated with this credit marketplace, and users should avoid confusion between the two.