CUBE3 Documentation
  • CUBE3 Documentation
  • Detect Products
    • Inspector
    • Monitor
    • Sonar
      • Sonar Feeds
  • Protect Products
    • RASP
      • Quick Start
        • ERC-20 Non-Upgradeable (Foundry)
        • ERC-20 Non-Upgradeable (Hardhat)
        • ERC-20 Upgradeable (Foundry)
        • ERC-20 Upgradeable (Hardhat)
      • RASP Integration
        • 1. Installation
        • 2. Integration
        • 3. Deployment
        • 4. Registration
        • 5. Interaction
        • 6. Inspection
      • CUBE3 Protocol
      • CUBE3 SDK
  • Manage Products
    • Transactions
    • Alerts
      • Email Integration
      • Slack Integration
      • Telegram Integration
      • Discord Integration
      • Webhook Integration
    • Rules
  • API Documentation
    • Inspector API
    • Validation API
      • Troubleshooting
    • Management API
      • Monitor API
      • Alert API
      • Control lists API
    • Authentication
    • API Rate Limits
  • Risk Engine
    • Risk Scoring Introduction
    • Risk Scoring Detailed Overview
  • Settings
    • Billing
    • Organization
    • API Keys
  • Supported Blockchain Networks
    • CUBE3 Detect Products
    • CUBE3 Protect Products
  • Testing Guide
Powered by GitBook
On this page
  1. API Documentation
  2. Validation API

Troubleshooting

This table serves as a quick-reference guide to help understand and resolve common errors related to transaction validation.

PreviousValidation APINextManagement API

Last updated 5 months ago

Error Message
Description
Solution

No registered contract was found for this chain to sign the payload: {transaction_data}

If contarct is not registered we cannot provide the signature. You need the signature only when contract is . In order to fully integrate RASP solution follow instructions of .

To resolve this, either integrate RASP solution or set signTransaction to false

To/From address is missing in the transaction data: {transaction_data}

"To" or "From" address is absent in the transaction data. If the transaction payload does not include both the "To" and "From" addresses

Ensure that the transaction data contains both to and from addresses

Chain id is missing in the transaction data: {transaction_data}

The blockchain ID is absent in the transaction data. If the blockchain ID is not included in the transaction payload

Include a valid chainId in the transaction data

Transaction data is missing in the request: {transaction_data}

The transaction data is missing in the command. If the transaction validation payload is empty

Ensure the transaction command includes all necessary transactionData fields

registered and function protection is enabled
installation