Makerdao
Makerdao controls map to separate vault, token and wallet state changes.
Makerdao is now known as Sky, yet a vault’s controls still correspond to specific state changes on Ethereum. Compare actions by the ledger entries they alter, then match the confirmed transaction with the resulting vault and wallet values. Before signing, record the connected account, network, collateral, outstanding DAI debt, collateral ratio and live risk parameters. Separate a collateral deposit from a DAI repayment, a debt generation from a collateral withdrawal and a token approval from the action it enables. After confirmation, compare the transaction status, changed balances and updated vault state with that record. A changed button state alone does not prove that every requested change reached the chain.
· last updatedBottom line: Compare the state each vault control changes, then match the transaction receipt with updated collateral, debt and wallet balances.
Choose the State Change Before the Control
Begin with the ledger entry that you intend to change. A larger collateral buffer can come from adding collateral or reducing debt, while greater wallet liquidity can come from generating DAI or withdrawing available collateral.
A basic wallet connection gives an interface an address and network context. It does not deposit collateral, generate debt or transfer a token. A message signature may establish consent without changing Ethereum state, whereas a transaction signature authorizes a call that can change it.
Depositing approved collateral raises the amount locked in the vault. Repaying DAI lowers outstanding debt. Both actions can improve the collateral ratio, but only repayment reduces the debt on which future stability fees accrue. Only a deposit adds more collateral to the position.
Generating DAI and withdrawing collateral move the ratio in the other direction. Generation raises debt and credits DAI to the designated wallet, while withdrawal removes available collateral from the vault. The choice must satisfy the vault’s live constraints when the transaction executes, not only when the interface prepares its preview.
What Does Each Vault Control Change?
Each vault control changes a distinct balance, debt entry or permission. Reading the action by its effect helps separate a completed vault operation from an approval or wallet prompt that merely prepares one.
- Deposit moves an approved collateral asset from the wallet into the selected vault.
- Withdraw moves available collateral from the vault back to the wallet, subject to the resulting position remaining valid.
- Generate increases the vault’s DAI debt and creates a corresponding DAI balance for the chosen recipient.
- Repay spends DAI from an authorized wallet balance and reduces the vault’s outstanding debt.
- Approve changes an ERC-20 allowance for a specified spender. It does not itself deposit collateral or repay debt.
A compound control may package more than one call, such as repayment followed by collateral withdrawal. In that case, inspect every proposed effect before signing. After execution, confirm each component separately because one visible control can represent several state transitions.
Closing a position describes an outcome rather than a single universal call. The debt, including the accrued stability fee, must be settled before all remaining collateral becomes withdrawable. An empty vault can continue to exist as a record even after its balances reach zero.
Read Live Constraints Before Signing
Governance sets a separate liquidation ratio for each vault type. The ratio is a boundary for liquidation eligibility, not a recommended operating target. Compare it with the position’s current collateral-to-debt ratio and with the estimated ratio after the proposed action.
Debt generation can also encounter a debt ceiling or a minimum debt requirement. These parameters apply to the selected vault type and can change through governance. A saved screenshot or old percentage cannot establish the conditions that apply to a later transaction, so preserve the live values used by the actual preview.
Costs sit in different parts of the operation. The stability fee affects vault debt, while Ethereum gas pays for transaction execution. An ERC-20 approval can require its own transaction and gas payment before the main vault call. Compare the wallet’s prompts with the intended sequence so a completed approval is not mistaken for the completed vault action.
Deposit or Repay Against the Same Target
In this hypothetical case, a vault starts with collateral valued at 928 DAI and debt of 348 DAI before any further stability fee accrues. Its displayed collateral ratio is about 266.7%, calculated as 928 divided by 348 and multiplied by 100.
One option adds hypothetical collateral valued at 128 DAI. The recorded collateral value becomes 1056 DAI and the ratio becomes about 303.4%, while debt remains 348 DAI. The other option repays a hypothetical 44 DAI. Debt becomes 304 DAI and the ratio becomes about 305.3%, while collateral stays unchanged. Both choices approach the same ratio range, but one requires more approved collateral and the other requires DAI.
If reducing debt is the selected objective, the repayment provides the closer fit. When exactly 44 DAI settles and no other debt change intervenes, confirmation consists of a successful receipt, vault debt of 304 DAI and a 44 DAI decrease in the paying wallet. Gas is paid separately. Accrued fees or a revised collateral valuation can change the final display, so use the execution-time values for the final comparison.
How Do You Confirm the Onchain Result?
Confirm the result by pairing a successful transaction receipt with the resulting contract state for the same account, network and vault. Neither the interface notification nor a changed wallet balance is enough on its own.
The receipt identifies the transaction status, sender, destination and block of inclusion. The transaction’s call data and the receipt’s event logs should correspond to the requested vault action. A successful receipt for an allowance transaction shows that the call did not revert; read the resulting allowance to confirm the permission. It does not prove that a later deposit or repayment also ran.
Next, compare the state variables that the action should have changed. A deposit should raise vault collateral and reduce the wallet’s collateral balance. A repayment should lower vault debt and reduce the paying wallet’s DAI balance. For a bundled action, verify every expected change rather than relying on one updated total.
A reverted Ethereum transaction does not commit its attempted contract changes, although it can still consume gas. A pending or replaced transaction also lacks a final state to reconcile. Once the receipt succeeds, compare values at its inclusion block when possible. If only later values are available, account for intervening transactions, stability fee accrual, price updates or parameter changes. Do not mix an earlier interface snapshot with a later wallet balance.
Limits of Interface Evidence
The stability fee accrues on outstanding vault debt and is settled in DAI when that debt is reduced or closed. An interface can round values, cache an earlier block or bundle several calls behind one control. The receipt and contract state establish what executed, but they cannot freeze collateral prices or governance parameters after that block. A later reading therefore describes a new state, not permanent proof of the earlier ratio.
Things people ask about Makerdao
Can a Makerdao Token Approval Remain After the Vault Action?
Yes. An ERC-20 approval is a separate onchain allowance and can remain after the deposit or repayment that used it. The vault action may spend part or all of the allowance, but it does not necessarily reduce the remaining allowance to zero. Check the token, approved spender and remaining amount as separate state. Reducing or revoking an allowance requires another transaction and therefore another gas payment.
Why Can a Makerdao Withdrawal Fail After a Successful Preview?
A withdrawal can fail when the execution-time state no longer satisfies the vault’s constraints. Collateral valuation, accrued debt, a governance parameter or another transaction may have changed after the preview was calculated. A stale account or network selection can also point the call at the wrong context. Read the failed receipt or revert data, refresh the vault state and prepare a new amount from those values.
Does a Failed Makerdao Transaction Alter the Vault State?
No. A reverted Ethereum transaction does not commit the attempted collateral or debt changes, although the sender can still pay gas for the failed execution. Rejecting a wallet prompt usually prevents the transaction from being broadcast at all. Pending and replaced transactions are different states, so identify the final receipt before deciding whether the vault needs another transaction.
When Should a Makerdao Action Produce a Transaction Hash?
Submitting a signed Ethereum transaction should return a transaction hash, but the hash alone does not show that the transaction succeeded. Connecting a wallet or signing an offchain message generally does not create one. A token approval may produce its own hash before the intended vault action creates another. Look up each hash and match its transaction destination and call so the preparatory permission is not confused with the deposit, withdrawal, generation or repayment.
Which Block Should Be Used to Reconcile Two Makerdao Displays?
Use a common confirmed block when comparing values from two interfaces or an interface with a direct contract reading. One display may use a cached block while another follows a newer chain head, so both can show internally valid but different values. The transaction receipt supplies the inclusion block. Compare the resulting vault and wallet state at that block. If only a later confirmed block is available, account for intervening transactions, stability fee accrual, price updates or parameter changes.