Record Withdrawal

curl -X POST "https://api.strike.markets/withdraw" \
  -H "Content-Type: application/json" \
  -d '{
    "walletAddress": "0x742d35cc6C6C7532B1140Da4C8A2f6C8ECfC9B46",
    "amount": "250.0",
    "txHash": "0x1234567890abcdef1234567890abcdef12345678901234567890abcdef123457",
    "timestamp": "2024-01-15T15:45:00Z"
  }'

{
  "success": true,
  "message": "Withdrawal verified and recorded successfully"
}

​

Overview

​

How Withdrawals Work

​

Process Flow

1. Withdrawal Request: Initiated through Strike Protocol frontend or smart contract
2. On-chain Execution: Withdrawal transaction executed on blockchain
3. Record Withdrawal: Call this endpoint with transaction details
4. Verification: API verifies the transaction on-chain
5. Balance Update: Your Strike Protocol balance is debited

​

Withdrawal Types

• Standard Withdrawal: Normal withdrawal of available balance
• Emergency Withdrawal: Withdrawal of all funds during emergencies
• Partial Withdrawal: Withdrawal of portion of available balance

​

Request Body

​

Response Fields

​

Verification Process

​

On-Chain Validation

1. Transaction Existence: Confirms withdrawal transaction exists on-chain
2. Contract Interaction: Verifies transaction interacted with Strike Protocol contract
3. Amount Matching: Confirms withdrawn amount matches request
4. Wallet Verification: Ensures withdrawal was sent to specified wallet
5. Duplicate Prevention: Prevents double-counting of the same withdrawal
6. Balance Validation: Ensures sufficient balance existed before withdrawal

​

Verification Criteria

• Block Confirmations: Minimum confirmations required for security
• Contract Address: Must originate from official Strike Protocol contract
• Asset Type: Must be supported asset (USDC)
• Transaction Success: Withdrawal must have completed successfully

​

Withdrawal Mechanics

​

Balance Updates

• Account Balance: Decreased by withdrawal amount
• Withdrawable Balance: Reduced accordingly
• Reserved Balance: Remains unchanged (margin for open positions)

​

Withdrawal Limits

• Available Balance: Can only withdraw non-reserved funds
• Open Positions: Must maintain sufficient margin for positions
• Minimum Balance: May have minimum balance requirements

​

Processing Time

• Verification: Usually instant if transaction is confirmed
• Balance Update: Immediate after verification
• Blockchain Settlement: Funds available in wallet immediately

​

Error Responses

{
  "error": 400,
  "message": "Transaction verification failed: withdrawal not from Strike Protocol contract"
}

{
  "error": 409,
  "message": "Withdrawal transaction already recorded"
}

{
  "error": 503,
  "message": "Unable to verify withdrawal transaction, please try again"
}

​

Usage Examples

​

Standard Withdrawal

{
  "walletAddress": "0x742d35cc6C6C7532B1140Da4C8A2f6C8ECfC9B46",
  "amount": "500.0",
  "txHash": "0x...",
  "timestamp": "2024-01-15T15:45:00Z"
}

​

Partial Withdrawal

{
  "walletAddress": "0x742d35cc6C6C7532B1140Da4C8A2f6C8ECfC9B46",
  "amount": "100.0",
  "txHash": "0x...",
  "timestamp": "2024-01-15T15:45:00Z"
}

​

Large Withdrawal

{
  "walletAddress": "0x742d35cc6C6C7532B1140Da4C8A2f6C8ECfC9B46",
  "amount": "5000.0",
  "txHash": "0x...",
  "timestamp": "2024-01-15T15:45:00Z"
}

​

Making a Withdrawal

​

Step 1: Check Available Balance

​

Step 2: Initiate Withdrawal

​

Step 3: Get Transaction Hash

​

Step 4: Record Withdrawal

​

Step 5: Verify Balance

​

Integration Examples

​

Web3.js Integration

// Initiate withdrawal through contract
const tx = await strikeContract.withdraw(withdrawAmount);
const receipt = await tx.wait();

// Record withdrawal with API
const response = await fetch('https://api.strike.markets/withdraw', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    walletAddress: userAddress,
    amount: withdrawAmount.toString(),
    txHash: receipt.transactionHash,
    timestamp: new Date().toISOString()
  })
});

​

Frontend Integration

// After successful withdrawal transaction
async function recordWithdrawal(txHash, amount, userAddress) {
  try {
    const response = await fetch('https://api.strike.markets/withdraw', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        walletAddress: userAddress,
        amount: amount,
        txHash: txHash,
        timestamp: new Date().toISOString()
      })
    });
    
    if (response.ok) {
      console.log('Withdrawal recorded successfully');
      // Update UI balance
      await refreshAccountBalance();
    }
  } catch (error) {
    console.error('Failed to record withdrawal:', error);
  }
}

​

Balance Management

​

Available vs Reserved

• Available Balance: Funds available for withdrawal
• Reserved Balance: Margin locked in open positions
• Total Balance: Available + Reserved

​

Withdrawal Constraints

• Not reserved as margin for open positions
• Not pending in other operations
• Above any minimum balance requirements

​

Position Impact

• Open position margins
• Position sizes or leverage
• Liquidation prices
• Unrealized PnL

​

Best Practices

​

Transaction Handling

• Confirm Success: Ensure withdrawal transaction succeeded before recording
• Wait for Confirmations: Allow sufficient block confirmations
• Gas Management: Use appropriate gas limits for withdrawal transactions
• Error Handling: Implement proper error handling for failed withdrawals

​

Balance Management

• Check Availability: Always verify available balance before withdrawal
• Reserve Calculation: Account for margin requirements in open positions
• Timing: Consider market conditions and position status

​

Security Considerations

• Amount Verification: Double-check withdrawal amounts
• Contract Verification: Ensure interaction with correct contract
• Wallet Security: Verify withdrawal destination wallet
• Transaction Monitoring: Monitor withdrawal transactions for completion

​

Troubleshooting

​

Common Issues

1. “Insufficient withdrawable balance”
   • Check available balance vs. reserved margin
   • Close positions to free up margin
   • Verify account balance is sufficient
2. “Transaction verification failed”
   • Ensure transaction hash is correct
   • Verify transaction succeeded on-chain
   • Check if withdrawal came from Strike Protocol contract
3. “Withdrawal transaction already recorded”
   • Withdrawal was already processed
   • Check account balance for debit
   • Don’t resubmit the same transaction
4. “Unable to verify withdrawal transaction”
   • Blockchain RPC may be experiencing issues
   • Wait for more confirmations
   • Retry after a few minutes

​

Verification Steps

1. Check Transaction: View transaction on block explorer
2. Confirm Source: Ensure withdrawal came from Strike Protocol contract
3. Verify Amount: Confirm withdrawal amount matches request
4. Check Status: Ensure transaction completed successfully

​

Next Steps

1. Verify Balance - Check Account Info for updated balance
2. Monitor Wallet - Confirm funds arrived in your wallet
3. Review Activity - Track transaction in Dashboard
4. Plan Trading - Consider impact on available trading balance