Dai Stablecoin (DAI) Smart Contract Risk

Permit No-Op / Non-Standard Permit

⚡ MEDIUM severity

Vulnerability

DAI implements a non-standard permit function (using nonces differently and with a different signature format than EIP-2612). Protocols assuming standard EIP-2612 permit may encounter unexpected behavior.

Related: Unchecked Return Values

Safe integration

If using permit with DAI, use DAI-specific permit parameters (holder, spender, nonce, expiry, allowed). Do not assume EIP-2612 compatibility.

Contract addresses

ChainAddress
Ethereum 0x6b175474e89094c44da98b954eedeac495271d0f

Audit any contract that interacts with DAI: SmartContract.us automatically detects DAI integration risks →

What this contract permits today

Read live from Ethereum on 2026-10-14. This is a different question from the integration risk above: not how to call the token safely, but what the holders of its keys are able to do to the people holding it.

QuestionAnswer
Can new tokens be created?Yes
Can transfers be blocked?No
Is there a trading tax?No
Can the logic be replaced?No
Can liquidity be withdrawn?Yes

No privileged address could be identified. This is not the same as there being none — see the limitation below.

See the full check, with the evidence behind each answer →

← Back to Token Risk Profiles