การจัดการข้อผิดพลาดด้วย Revert/Require

Welcome to error handling in Solidity! Writing smart contracts requires extreme care, as they often manage valuable assets and are immutable once deployed.

Effective error handling is crucial for creating robust and secure decentralized applications (dApps). It helps prevent unexpected behavior and protects users.

The require() function is your primary tool for validating conditions that must be true before a function executes.

• It checks pre-conditions and user inputs.
• If the condition is false, it reverts all state changes made in the current transaction.
• It refunds any remaining gas to the caller, effectively canceling the transaction.

Use require() for external conditions and user-provided data checks.

Let's see require() in a simple contract. This function only allows users older than 18 to register.

The revert() statement offers more flexibility than require(), especially when you need to handle complex error logic or integrate with custom error types.

• Like require(), it reverts all state changes and refunds gas.
• It's often used inside if statements for more intricate conditional checks.
• It can be called directly or with a string message, similar to require().

Solidity 0.8.4+ introduced Custom Errors. These are more gas-efficient than string messages and provide better clarity for off-chain applications.

You define custom errors at the contract or file level, then use them with revert(). They help reduce transaction costs and improve contract readability.

Here's how to define and use a custom error with revert(). Notice the error keyword.

The assert() function is used for a very specific purpose: checking internal invariants.

• It verifies conditions that should never be false if your code is working correctly.
• If an assert() fails, it indicates a bug in your contract logic.
• Crucially, a failed assert() consumes all remaining gas, unlike require() and revert() which refund gas.

Use assert() for post-conditions or internal consistency checks, not for user input validation.

Choosing the right error handler is key:

• require(): For validating user inputs, external conditions, or state changes before execution. Refunds gas.
• revert(): For more complex error logic, often with custom errors. Also refunds gas.
• assert(): For internal consistency checks and invariants. Indicates a bug if it fails and consumes all gas.

Prioritize require() and revert() for expected errors, and reserve assert() for unexpected, internal errors.

You're building a function that transfers tokens. Before sending, you need to ensure the sender has enough balance. If not, the transaction should fail and refund any unused gas.

You've learned how to make your Solidity contracts robust with proper error handling:

• require() is for validating external conditions and user inputs.
• revert() offers flexibility, often used with gas-efficient custom errors.
• assert() is for internal invariants, signaling a bug if it fails.

Mastering these ensures your smart contracts are secure and predictable. Great job!