Withdrawal patterns in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Withdrawal patterns

User requests withdrawal

↓

Check user balance

↓

Is balance sufficient?

No→Reject withdrawal

Yes↓

Lock funds

↓

Process withdrawal transaction

↓

Confirm transaction success?

No→Unlock funds, notify failure

Yes↓

Update user balance

↓

Notify user of success

↓

END

This flow shows how a withdrawal request is handled step-by-step, checking balance, locking funds, processing, and confirming success.

Execution Sample

Blockchain / Solidity

def withdraw(user, amount):
    if user.balance < amount:
        return "Insufficient funds"
    user.lock_funds(amount)
    success = blockchain.send_transaction(user.address, amount)
    if not success:
        user.unlock_funds(amount)
        return "Transaction failed"
    user.balance -= amount
    return "Withdrawal successful"

This code handles a withdrawal by checking balance, locking funds, sending transaction, and updating balance.

Execution Table

Step	Action	Condition/Evaluation	Result/State Change	Output
1	Check if user.balance < amount	user.balance=100, amount=50	Condition False (100 >= 50)	Continue
2	Lock funds	Lock 50 units	Funds locked: 50	No output
3	Send transaction	Simulate blockchain.send_transaction	Transaction success = True	No output
4	Check transaction success	success == True	Proceed to update balance	No output
5	Update user.balance	user.balance = 100 - 50	user.balance = 50	No output
6	Return success message	N/A	N/A	Withdrawal successful
7	End	N/A	N/A	Process complete

💡 Withdrawal completes successfully after balance check, locking funds, transaction success, and balance update.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5	Final
user.balance	100	100	100	100	50	50
amount	50	50	50	50	50	50
funds_locked	0	0	50	50	50	50
transaction_success	N/A	N/A	N/A	True	True	True

Key Moments - 3 Insights

Why do we lock funds before sending the transaction?

Locking funds prevents the user from spending the same amount twice while the transaction is pending, as shown in step 2 of the execution_table.

What happens if the transaction fails after locking funds?

If the transaction fails, the locked funds are unlocked to restore the user's balance, as explained in the code and implied in the flow after the transaction check.

Why do we update the user balance only after confirming transaction success?

Updating balance only after success ensures the user’s balance reflects actual funds spent, preventing errors or double spending, as seen in step 5 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the user.balance after step 5?

A 0

B 50

C 100

D 150

💡 Hint

Check the 'Result/State Change' column at step 5 in the execution_table.

At which step is the transaction success evaluated?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for the step where 'Check transaction success' is performed in the execution_table.

If the user.balance was 40 and amount 50, what would happen at step 1?

A Funds locked anyway

B Condition False, withdrawal proceeds

C Condition True, withdrawal rejected

D Transaction sent immediately

💡 Hint

Refer to the condition check in step 1 of the execution_table and variable_tracker for balance values.

Concept Snapshot

Withdrawal Patterns in Blockchain:
- Check user balance before withdrawal
- Lock funds to prevent double spending
- Send transaction to blockchain
- Confirm transaction success
- Update user balance only after success
- Unlock funds if transaction fails

Full Transcript

This visual execution trace shows how a withdrawal request is processed in blockchain systems. First, the user's balance is checked to ensure sufficient funds. If enough, the requested amount is locked to prevent spending it elsewhere. Then, a transaction is sent to the blockchain network. If the transaction succeeds, the user's balance is updated by subtracting the withdrawn amount. If the transaction fails, the locked funds are released back to the user. This process ensures security and consistency in handling withdrawals.