Sai

What is Sai?

Sai, or SAI, is the legacy Single-Collateral Dai stablecoin contract from MakerDAO, originally designed to let users borrow a dollar-targeted ERC-20 token against overcollateralized ETH without relying on a conventional bank issuer. Its specific problem was crypto-native credit: it converted volatile ETH collateral into a transferable synthetic dollar through smart contracts, liquidation incentives, oracle inputs, and Maker governance rather than through cash reserves held by a centralized custodian.

That design gave Sai an early moat as one of DeFi’s first functional overcollateralized stablecoin systems, but that moat is historical rather than current, because the live Maker/Sky ecosystem migrated from Sai to Multi-Collateral Dai in 2019 and then to the broader Sky architecture in 2024–2025; the old Sai contract remains on Ethereum, but the system that created and governed new Sai has been shut down. (makerdao.com)

Sai’s present market position is therefore unusual: it is not a growth-stage stablecoin, not a current Layer 1 asset, and not the primary stablecoin of the Maker/Sky ecosystem.

Market-data sites still list it because unredeemed tokens continue to trade in thin secondary markets; as of late August 2026, CoinGecko’s Sai page showed a residual market capitalization in the low tens of millions of dollars, a rank in the mid-hundreds, and only negligible daily DEX volume, which is consistent with an illiquid legacy claim rather than an actively used monetary instrument. DefiLlama’s live “Sai” protocol entry refers to a different derivatives venue on Nibiru, not Single-Collateral Dai, so it should not be used as TVL evidence for Maker’s old Sai system; the relevant contemporary scale belongs instead to Sky and to legacy DAI/USDS stablecoin supply, not to SAI itself. (coingecko.com)

Who Founded Sai and When?

Sai emerged from MakerDAO, the decentralized stablecoin project associated most closely with Rune Christensen and the Maker Foundation, with early protocol engineering also tied to the broader Maker developer community that built the first Dai credit system.

Maker’s own materials describe the project as beginning in 2015, with the first formal white paper published in December 2017 and the original Dai, now called Sai, launched as an ETH-only collateralized debt system.

The launch came during the 2017 crypto-market expansion, when Ethereum applications were beginning to move from token issuance toward on-chain financial primitives; Sai was one of the earliest serious attempts to create a blockchain-native dollar unit without a bank deposit backing every token. (makerdao.com)

The project’s narrative evolved from “decentralized stablecoin backed by ETH” into a broader collateral and governance system. In November 2019, MakerDAO launched Multi-Collateral Dai, renamed the original ETH-only Dai as Sai, and encouraged users to migrate because the new system introduced additional collateral types and the Dai Savings Rate. By May 2020, Maker governance had shut down Single-Collateral Dai, leaving Sai as a settled legacy instrument redeemable through the shutdown process rather than an expanding stablecoin network. The subsequent Maker-to-Sky rebrand and USDS/SKY migration are relevant to the institutional history of the protocol family, but they do not revive Sai as a production asset; they underscore that Sai is a predecessor system whose economic design informed later Maker/Sky architecture. (prnewswire.com)

How Does the Sai Network Work?

Sai does not have its own blockchain or validator set; it is an ERC-20 token and a set of Ethereum smart contracts, so its transaction settlement, censorship resistance, and finality are inherited from Ethereum. At launch, Sai operated on Ethereum under proof-of-work, but since Ethereum’s 2022 Merge the legacy token transfers and contract interactions settle under Ethereum proof-of-stake.

Technically, Sai was a Layer 1 application protocol rather than a Layer 1 network: users opened collateralized debt positions, locked ETH-derived collateral, generated Sai as debt, and were subject to liquidation if collateral value fell below risk parameters. Its security model was therefore a composite of Ethereum consensus, Maker smart-contract correctness, collateral-market liquidity, oracle reliability, and governance control. (makerdao.com)

The core technical features were not sharding, rollups, or zero-knowledge proofs, but overcollateralized credit, liquidation incentives, oracle-mediated risk management, and emergency shutdown. Maker’s Sai documentation describes a target price of one U.S. dollar, collateral auctions or liquidity mechanisms for undercollateralized positions, keepers that arbitraged liquidation and peg opportunities, price oracles selected by MKR voters, and emergency oracles that could trigger shutdown in the Single-Collateral system. The GitHub repository now describes Sai bluntly as a simple single-collateral stablecoin dependent on a trusted oracle address and a kill switch, which is an important caveat for institutional readers: Sai was decentralized relative to bank-issued stablecoins, but it still relied on privileged governance and oracle roles. (github.com)

What Are the Tokenomics of sai?

Sai’s tokenomics differ from ordinary fixed-supply cryptoassets because SAI was originally minted as debt and burned when debt was repaid.

There was no meaningful “max supply” in the Bitcoin-style sense while the system was live; supply expanded when users generated Sai against ETH collateral and contracted when they closed CDPs. After Single-Collateral Dai shutdown, however, new Sai issuance effectively ceased, and the remaining circulating supply represents residual tokens that were not fully migrated or redeemed. As of late August 2026, CoinGecko reported roughly 2.7 million SAI as tradable supply, but that should be interpreted as a legacy accounting figure for an illiquid token rather than as evidence of an active stablecoin economy. (coingecko.com)

SAI does not provide staking yield, validator revenue, governance rights, or fee accrual to holders. Its utility was historically monetary: borrowers used it to access liquidity without selling ETH, traders used it as a crypto-native dollar proxy, and arbitrageurs helped restore the peg when SAI traded away from target. Value accrual in the old system flowed primarily through stability fees and risk management into the Maker/MKR architecture, while Sai itself was intended to remain near one dollar rather than appreciate.

That model broke from common token-investment logic: holding SAI was not a claim on protocol profits, and in its post-shutdown state it is better analyzed as a thinly traded legacy settlement claim with smart-contract and liquidity frictions than as a productive yield-bearing asset. (makerdao.com)

Who Is Using Sai?

Current Sai usage appears overwhelmingly residual and speculative rather than operational. The old Single-Collateral Dai system no longer supports fresh credit creation, and market data in August 2026 showed only trivial daily volume on Uniswap V2, suggesting that most observed activity is likely from legacy holders, arbitrageurs, token collectors, or wallets interacting with stale balances rather than from real payment or DeFi demand. This is materially different from DAI or USDS, which remain integrated into lending, RWA, savings, and liquidity venues across the Sky/Maker ecosystem; institutional analysis should therefore avoid conflating Sai’s historical role in DeFi with present-day active usage. (coingecko.com)

There is no meaningful current enterprise adoption case for Sai itself. The institutional adoption story belongs to Maker/Sky’s later products, including DAI, USDS, Spark, RWA collateral programs, and the Sky governance stack, while Sai’s integrations were largely phased out after Multi-Collateral Dai launched. In 2019 Maker described hundreds of Dai ecosystem integrations, but that statement related to the broader Dai transition, not to a durable post-shutdown SAI market. For Sai, the legitimate adoption record is historical: it proved that overcollateralized on-chain credit could maintain a soft dollar target for a period of meaningful market use, but it has since been superseded by more flexible collateral systems. (prnewswire.com)

What Are the Risks and Challenges for Sai?

Sai’s regulatory exposure is best understood through two lenses: stablecoin regulation generally and legacy-token operability specifically. In the United States, the 2025 GENIUS Act created a federal framework for payment stablecoins, and 2026 SEC guidance stated that payment stablecoins, subject to the terms of that law, are generally not securities; however, Sai is not a contemporary issuer-backed payment stablecoin seeking regulatory approval, and there is no ETF pathway or active public enforcement case specific to SAI that defines its status.

The more practical regulatory risk is that exchanges, front ends, custodians, and compliance teams may choose not to support a deprecated stablecoin contract with thin liquidity and no live issuer-style compliance program. In the current Sky ecosystem, regulatory concerns focus more on USDS access restrictions, RWA collateral, sanctions compliance, and possible freeze-function governance than on Sai. usc-cdn.house.gov

The centralization and technical risks are also legacy-specific. Sai depended on trusted oracle infrastructure, governance-selected emergency actors, and a shutdown mechanism; these were pragmatic design choices for an early DeFi system, but they mean Sai was never a purely autonomous monetary asset.

Its main economic competitors are no longer other ETH-only CDP systems but the entire modern stablecoin market: fiat-backed coins such as USDT and USDC dominate liquidity, decentralized alternatives such as DAI and USDS offer broader collateral and protocol support, and newer yield-bearing or RWA-linked stablecoins compete for institutional balances. Sai’s market-share threat has already materialized: it lost its functional role when Maker moved to Multi-Collateral Dai, and its remaining trading premium or discount can be driven by illiquidity, redemption complexity, stale metadata, and speculative interpretation of the residual ETH settlement claim. (github.com)

What Is the Future Outlook for Sai?

Sai has no verified roadmap comparable to an active protocol upgrade cycle.

There were no major Sai-specific hard forks, emissions changes, staking-yield changes, or technical upgrades in the last twelve months; the relevant protocol development has occurred in Sky/Maker governance, including the MKR-to-SKY conversion architecture, SKY staking, oracle updates, Smart Burn Engine parameter changes, and broader USDS/Sky product rollout.

Those changes may affect the Maker/Sky ecosystem’s long-term competitive position, but they do not restore Sai’s original CDP engine or turn SAI into a modern stablecoin. The most realistic outlook is continued archival relevance: Sai remains important as the first production version of Maker’s stablecoin mechanism, but its infrastructure viability as a live asset is constrained by shutdown status, thin liquidity, lack of integrations, and the absence of a forward development path. (v2.vote.makerdao.com)

For institutional users, the analytical conclusion is conservative.

Sai should be treated as a deprecated Ethereum token and historical DeFi artifact, not as a current stablecoin substitute for DAI, USDS, USDC, or USDT. Its future depends less on innovation than on whether remaining holders can or want to redeem, trade, or custody the residual token, and whether data providers continue to display markets that are economically small and potentially misleading. No price forecast is warranted; the relevant question is not appreciation potential but whether the residual contract, liquidity venues, and redemption assumptions are reliable enough for any operational use.