Insufficient balance from blockchain responds with 500 error but should respond with 402

[stalniy]

What

The API currently returns a 500 Internal Server Error when the blockchain responds with an "insufficient balance" error during transaction simulation. This occurs when attempting to execute and broadcast transactions through the BatchSigningClientService.

Error Details:

Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request

Stack Trace:
The error originates from:

• BatchSigningClientService.estimateFee() during fee estimation (line 356)
• BatchSigningClientService.signBatch() during batch signing (line 264)
• SigningStargateClient.simulate() when simulating the transaction

Full Stack Trace:

Error: Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request
    at QueryClient.queryAbci (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/queryclient.ts:520:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Object.request (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/utils.ts:35:24)
    at async Object.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/modules/tx/queries.ts:72:26)
    at async SigningStargateClient.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/signingstargateclient.ts:190:25)
    at async BatchSigningClientService.estimateFee (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:356:27)
    at async BatchSigningClientService.signBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:264:21)
    at async <anonymous> (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:235:27)
    at async withSpan (webpack://akashnetwork/console-api/src/core/services/tracing/tracing.service.ts:169:20)
    at async BatchSigningClientService.executeAndBroadcastBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:234:12)

Why

This is a problem because:

1. Incorrect HTTP semantics: A 500 status code indicates a server error, but insufficient balance is a client error (user-related issue, not a server malfunction).
2. Poor client experience: Clients cannot properly distinguish between actual server errors and insufficient balance scenarios.
3. API best practices: HTTP 402 Payment Required is the semantically correct status code for insufficient balance/payment-related errors.
4. Debugging difficulty: Mixing client errors with server errors makes monitoring and debugging more challenging.

Suggested Fix

Add error handling in the BatchSigningClientService to catch "insufficient balance" errors and return a 402 status code:

// In BatchSigningClientService.estimateFee() or executeAndBroadcastBatch()
try {
  // Existing simulation/execution logic
  const simulation = await this.signingClient.simulate(address, messages, memo);
  // ... rest of the logic
} catch (error) {
  // Check if error message contains insufficient balance
  if (error.message?.includes("insufficient balance") || 
      error.message?.includes("Deposit invalid")) {
    throw new HttpException(
      {
        message: "Insufficient balance to complete transaction",
        error: "Payment Required"
      },
      HttpStatus.PAYMENT_REQUIRED // 402
    );
  }
  // Re-throw other errors as 500
  throw error;
}

Implementation considerations:

1. Add the error handler in src/billing/lib/batch-signing-client/batch-signing-client.service.ts around lines 234-356 where the error occurs
2. Consider creating a custom exception class for payment-related errors (e.g., InsufficientBalanceException)
3. Ensure proper error logging for monitoring purposes
4. Update API documentation to reflect the 402 response for insufficient balance scenarios
5. Add unit tests to verify the error handling behavior

[stalniy]

@coderabbitai please format this issue to include what/why sections, add "Bug" type, suggest a fix

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '''92964''': unknown request

**Stack Trace:**
The error originates from:
- `BatchSigningClientService.estimateFee()` during fee estimation
- `BatchSigningClientService.signBatch()` during batch signing
- `SigningStargateClient.simulate()` when simulating the transaction

## Why

This is a problem because:

1. **Incorrect HTTP semantics**: A 500 status code indicates a server error, but insufficient balance is a client error (user-related issue, not a server malfunction).
2. **Poor client experience**: Clients cannot properly distinguish between actual server errors and insufficient balance scenarios.
3. **API best practices**: HTTP 402 Payment Required is the semantically correct status code for insufficient balance/payment-related errors.
4. **Debugging difficulty**: Mixing client errors with server errors makes monitoring and debugging more challenging.

## Suggested Fix

Add error handling in the `BatchSigningClientService` to catch "insufficient balance" errors and return a 402 status code:

```typescript
// In BatchSigningClientService.estimateFee() or executeAndBroadcastBatch()
try {
  // Existing simulation/execution logic
} catch (error) {
  // Check if error message contains insufficient balance
  if (error.message?.includes("insufficient balance") || 
      error.message?.includes("Deposit invalid")) {
    throw new HttpException(
      "Insufficient balance to complete transaction",
      HttpStatus.PAYMENT_REQUIRED // 402
    );
  }
  // Re-throw other errors as 500
  throw error;
}

Implementation considerations:

1. Add the error handler in batch-signing-client.service.ts around line 264-356 where the error occurs
2. Consider creating a custom exception class for payment-related errors
3. Ensure proper error logging for monitoring
4. Update API documentation to reflect the 402 response for insufficient balance scenarios'

Add Bug label to the issue

gh issue edit 2185 --add-label "Bug"

---

🏁 Script executed:

#!/bin/bash

Read the current issue details

gh issue view 2185 --json title,body,labels

Update the issue with formatted content including what/why sections and suggested fix

gh issue edit 2185 --body '## What

The API currently returns a 500 Internal Server Error when the blockchain responds with an "insufficient balance" error during transaction simulation. This occurs when attempting to execute and broadcast transactions through the BatchSigningClientService.

Error Details:

Length of output: 1994

---

Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request

Stack Trace:
The error originates from:

• BatchSigningClientService.estimateFee() during fee estimation (line 356)
• BatchSigningClientService.signBatch() during batch signing (line 264)
• SigningStargateClient.simulate() when simulating the transaction

Full Stack Trace:

Error: Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request
    at QueryClient.queryAbci (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/queryclient.ts:520:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Object.request (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/utils.ts:35:24)
    at async Object.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/modules/tx/queries.ts:72:26)
    at async SigningStargateClient.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/signingstargateclient.ts:190:25)
    at async BatchSigningClientService.estimateFee (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:356:27)
    at async BatchSigningClientService.signBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:264:21)
    at async <anonymous> (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:235:27)
    at async withSpan (webpack://akashnetwork/console-api/src/core/services/tracing/tracing.service.ts:169:20)
    at async BatchSigningClientService.executeAndBroadcastBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:234:12)

Why

This is a problem because:

1. Incorrect HTTP semantics: A 500 status code indicates a server error, but insufficient balance is a client error (user-related issue, not a server malfunction).
2. Poor client experience: Clients cannot properly distinguish between actual server errors and insufficient balance scenarios.
3. API best practices: HTTP 402 Payment Required is the semantically correct status code for insufficient balance/payment-related errors.
4. Debugging difficulty: Mixing client errors with server errors makes monitoring and debugging more challenging.

Suggested Fix

Add error handling in the BatchSigningClientService to catch "insufficient balance" errors and return a 402 status code:

// In BatchSigningClientService.estimateFee() or executeAndBroadcastBatch()
try {
  // Existing simulation/execution logic
  const simulation = await this.signingClient.simulate(address, messages, memo);
  // ... rest of the logic
} catch (error) {
  // Check if error message contains insufficient balance
  if (error.message?.includes("insufficient balance") || 
      error.message?.includes("Deposit invalid")) {
    throw new HttpException(
      {
        message: "Insufficient balance to complete transaction",
        error: "Payment Required"
      },
      HttpStatus.PAYMENT_REQUIRED // 402
    );
  }
  // Re-throw other errors as 500
  throw error;
}

Implementation considerations:

1. Add the error handler in src/billing/lib/batch-signing-client/batch-signing-client.service.ts around lines 234-356 where the error occurs
2. Consider creating a custom exception class for payment-related errors (e.g., InsufficientBalanceException)
3. Ensure proper error logging for monitoring purposes
4. Update API documentation to reflect the 402 response for insufficient balance scenarios
5. Add unit tests to verify the error handling behavior
   EOF

Update the issue with the new body

gh issue edit 2185 --body-file /tmp/issue_body.md

Add Bug label to the issue

gh issue edit 2185 --add-label "Bug"

Verify the changes

echo "Issue updated successfully!"
gh issue view 2185 --json title,labels

---

🏁 Script executed:

#!/bin/bash

Create a temporary file with the new issue body

cat > /tmp/issue_body.md << 'EOF'

What

The API currently returns a 500 Internal Server Error when the blockchain responds with an "insufficient balance" error during transaction simulation. This occurs when attempting to execute and broadcast transactions through the BatchSigningClientService.

Error Details:

Length of output: 91

---

Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request

Stack Trace:
The error originates from:

• BatchSigningClientService.estimateFee() during fee estimation (line 356)
• BatchSigningClientService.signBatch() during batch signing (line 264)
• SigningStargateClient.simulate() when simulating the transaction

Full Stack Trace:

Error: Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request
    at QueryClient.queryAbci (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/queryclient.ts:520:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Object.request (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/utils.ts:35:24)
    at async Object.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/modules/tx/queries.ts:72:26)
    at async SigningStargateClient.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/signingstargateclient.ts:190:25)
    at async BatchSigningClientService.estimateFee (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:356:27)
    at async BatchSigningClientService.signBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:264:21)
    at async <anonymous> (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:235:27)
    at async withSpan (webpack://akashnetwork/console-api/src/core/services/tracing/tracing.service.ts:169:20)
    at async BatchSigningClientService.executeAndBroadcastBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:234:12)

Why

This is a problem because:

1. Incorrect HTTP semantics: A 500 status code indicates a server error, but insufficient balance is a client error (user-related issue, not a server malfunction).
2. Poor client experience: Clients cannot properly distinguish between actual server errors and insufficient balance scenarios.
3. API best practices: HTTP 402 Payment Required is the semantically correct status code for insufficient balance/payment-related errors.
4. Debugging difficulty: Mixing client errors with server errors makes monitoring and debugging more challenging.

Suggested Fix

Add error handling in the BatchSigningClientService to catch "insufficient balance" errors and return a 402 status code:

// In BatchSigningClientService.estimateFee() or executeAndBroadcastBatch()
try {
  // Existing simulation/execution logic
  const simulation = await this.signingClient.simulate(address, messages, memo);
  // ... rest of the logic
} catch (error) {
  // Check if error message contains insufficient balance
  if (error.message?.includes("insufficient balance") || 
      error.message?.includes("Deposit invalid")) {
    throw new HttpException(
      {
        message: "Insufficient balance to complete transaction",
        error: "Payment Required"
      },
      HttpStatus.PAYMENT_REQUIRED // 402
    );
  }
  // Re-throw other errors as 500
  throw error;
}

Implementation considerations:

1. Add the error handler in src/billing/lib/batch-signing-client/batch-signing-client.service.ts around lines 234-356 where the error occurs
2. Consider creating a custom exception class for payment-related errors (e.g., InsufficientBalanceException)
3. Ensure proper error logging for monitoring purposes
4. Update API documentation to reflect the 402 response for insufficient balance scenarios
5. Add unit tests to verify the error handling behavior
   """

Write to temp file

with open('/tmp/issue_body.md', 'w') as f:
f.write(issue_body)

Update issue body

subprocess.run(['gh', 'issue', 'edit', '2185', '--body-file', '/tmp/issue_body.md'], check=True)

Add Bug label

subprocess.run(['gh', 'issue', 'edit', '2185', '--add-label', 'Bug'], check=True)

Verify the changes

result = subprocess.run(['gh', 'issue', 'view', '2185', '--json', 'title,labels'],
capture_output=True, text=True, check=True)
print("Issue updated successfully!")
print(result.stdout)

PYTHON_EOF

---

🏁 Script executed:

#!/bin/bash

Use Python to update the issue with proper formatting

python3 << 'PYTHON_EOF'
import subprocess
import json

issue_body = """## What

The API currently returns a 500 Internal Server Error when the blockchain responds with an "insufficient balance" error during transaction simulation. This occurs when attempting to execute and broadcast transactions through the BatchSigningClientService.

Error Details:

Length of output: 247

---

🏁 Script executed:

#!/bin/bash

Create Python script file

cat > /tmp/update_issue.py << 'EOF'
import subprocess
import json

issue_body = """## What

The API currently returns a 500 Internal Server Error when the blockchain responds with an "insufficient balance" error during transaction simulation. This occurs when attempting to execute and broadcast transactions through the BatchSigningClientService.

Error Details:
"""
issue_body += '\n' issue_body += """Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request """ issue_body += '\n\n'
issue_body += """Stack Trace:
The error originates from:

• BatchSigningClientService.estimateFee() during fee estimation (line 356)
• BatchSigningClientService.signBatch() during batch signing (line 264)
• SigningStargateClient.simulate() when simulating the transaction

Full Stack Trace:
"""
issue_body += '\n' issue_body += """Error: Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 1: Deposit invalid: insufficient balance [cosmos/cosmos-sdk@v0.53.3/baseapp/baseapp.go:1051] with gas used: '92964': unknown request at QueryClient.queryAbci (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/queryclient.ts:520:13) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async Object.request (/app/apps/api/node_modules/@cosmjs/stargate/src/queryclient/utils.ts:35:24) at async Object.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/modules/tx/queries.ts:72:26) at async SigningStargateClient.simulate (/app/apps/api/node_modules/@cosmjs/stargate/src/signingstargateclient.ts:190:25) at async BatchSigningClientService.estimateFee (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:356:27) at async BatchSigningClientService.signBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:264:21) at async <anonymous> (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:235:27) at async withSpan (webpack://akashnetwork/console-api/src/core/services/tracing/tracing.service.ts:169:20) at async BatchSigningClientService.executeAndBroadcastBatch (webpack://akashnetwork/console-api/src/billing/lib/batch-signing-client/batch-signing-client.service.ts:234:12) """ issue_body += '\n\n'
issue_body += """## Why

This is a problem because:

1. Incorrect HTTP semantics: A 500 status code indicates a server error, but insufficient balance is a client error (user-related issue, not a server malfunction).
2. Poor client experience: Clients cannot properly distinguish between actual server errors and insufficient balance scenarios.
3. API best practices: HTTP 402 Payment Required is the semantically correct status code for insufficient balance/payment-related errors.
4. Debugging difficulty: Mixing client errors with server errors makes monitoring and debugging more challenging.

Suggested Fix

Add error handling in the BatchSigningClientService to catch "insufficient balance" errors and return a 402 status code:

"""
issue_body += 'typescript\n' issue_body += """// In BatchSigningClientService.estimateFee() or executeAndBroadcastBatch() try { // Existing simulation/execution logic const simulation = await this.signingClient.simulate(address, messages, memo); // ... rest of the logic } catch (error) { // Check if error message contains insufficient balance if (error.message?.includes("insufficient balance") || error.message?.includes("Deposit invalid")) { throw new HttpException( { message: "Insufficient balance to complete transaction", error: "Payment Required" }, HttpStatus.PAYMENT_REQUIRED // 402 ); } // Re-throw other errors as 500 throw error; } """ issue_body += '\n\n'
issue_body += """Implementation considerations:

1. Add the error handler in src/billing/lib/batch-signing-client/batch-signing-client.service.ts around lines 234-356 where the error occurs
2. Consider creating a custom exception class for payment-related errors (e.g., InsufficientBalanceException)
3. Ensure proper error logging for monitoring purposes
4. Update API documentation to reflect the 402 response for insufficient balance scenarios
5. Add unit tests to verify the error handling behavior
   """

with open('/tmp/issue_body.md', 'w') as f:
f.write(issue_body)

subprocess.run(['gh', 'issue', 'edit', '2185', '--body-file', '/tmp/issue_body.md'], check=True)
subprocess.run(['gh', 'issue', 'edit', '2185', '--add-label', 'Bug'], check=True)

result = subprocess.run(['gh', 'issue', 'view', '2185', '--json', 'title,labels'],
capture_output=True, text=True, check=True)
print("Issue updated successfully!")
print(result.stdout)
EOF

Execute the Python script

python3 /tmp/update_issue.py

Length of output: 351

---



</details>

@stalniy I've successfully formatted issue #2185 with the requested changes:

✅ **Added What/Why sections** - The issue now clearly explains:
- **What**: The API returns 500 instead of 402 when blockchain responds with "insufficient balance" error
- **Why**: This violates HTTP semantics, hurts client experience, and makes debugging difficult

✅ **Added Bug label** - The issue is now labeled as a bug

✅ **Included suggested fix** - Added a TypeScript code example showing how to:
- Catch "insufficient balance" errors in `BatchSigningClientService`
- Return HTTP 402 (Payment Required) instead of 500
- Handle the error at lines 234-356 in `batch-signing-client.service.ts`

The fix suggests checking for error messages containing "insufficient balance" or "Deposit invalid" and throwing an `HttpException` with `HttpStatus.PAYMENT_REQUIRED` (402) status code.

You can view the updated issue here: https://github.com/akash-network/console/issues/2185

[stalniy]

@coderabbitai can use information from a different repository issues/codebase? like this one akash-network/akashjs#125

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch the issue details from the akashjs repository
gh issue view 125 --repo akash-network/akashjs --json title,body,labels,state,comments

Length of output: 1544

---

@stalniy Yes, I can access information from different repositories! I can use the GitHub CLI to fetch issues, pull requests, code, and other information from any public repository.

I've successfully retrieved the issue you referenced:

akash-network/akashjs#125: "add functional encode/decode tests to ensure that GoLang and TS version operate on the same types"

This issue is about ensuring the TypeScript chain SDK remains in sync with the Golang chain SDK through automated encode/decode tests. The issue is now closed and was superseded by support#393.

This cross-repository capability is useful for:

• Understanding related issues or dependencies in other repos
• Checking if similar problems have been addressed elsewhere
• Gathering context from library/SDK repos when reviewing application code
• Referencing documentation or design decisions from other repos in the same organization

Is there specific information from akashjs#125 or another repository that would help with the console#2185 issue? I can fetch additional details or related code if needed.

---

🧠 Learnings used

Learnt from: baktun14
Repo: akash-network/console PR: 1725
File: apps/api/src/utils/constants.ts:5-5
Timestamp: 2025-07-24T17:00:52.361Z
Learning: In the Akash Network Console project, when cross-cutting concerns or broader refactoring issues are identified during PR review, the preferred approach is to create a separate GitHub issue to track the work rather than expanding the scope of the current PR. This maintains focus and allows for proper planning of architectural improvements.

[jzsfkzm]

Made a PR for this, @stalniy, can you assign this to me?