Cubewire LogoDeveloper
Support
Onboarding
Cubewire Developer Hub Logo
SOC 2 Compliant

Developer documentation and tools for Cubewire's digital wallet infrastructure. Built for developers, by developers.

developers@cubewire.com
TwitterGitHubDiscord

Developer Tools

  • API Documentation
  • API Reference

Resources

  • Documentation

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
© 2026 Cubewire. All rights reserved.
Developer Documentation Portal•Built with ♥ for developers
  1. Cubewire Wallet
  2. Manage Transactions
  3. Broadcast a signed transaction

Broadcast a signed transaction

Broadcast a pre-signed transaction directly to the blockchain network. This endpoint bypasses the standard workflow orchestration and policy evaluation, executing the transaction as-is.

Request Body

FieldTypeRequiredDescription
signedTransactionHexstringYesRLP-encoded signed transaction (0x prefix)
chainIdnumberYesBlockchain network ID (must match transaction)

Transaction Flow

  1. Decode — Parse and validate the signed transaction hex
  2. Verify — Confirm chain ID matches the transaction
  3. Balance Check — Verify sender has sufficient funds/gas
  4. Broadcast — Submit transaction to blockchain network
  5. Return — Provide transaction hash and metadata

Important: This endpoint does NOT perform policy evaluation or trigger approval workflows. The transaction is broadcast exactly as signed.

Response Fields

FieldTypeDescription
transactionHashstringBlockchain transaction hash (0x...)
fromstringSender address extracted from signature
tostringRecipient address (null for deployments)
noncenumberTransaction nonce
chainIdnumberNetwork where transaction was broadcast
gasLimitstringGas limit from transaction
gasPricestringGas price in wei (legacy pre-EIP-1559 transactions)
maxFeePerGasstringEIP-1559 max fee per gas in wei
maxPriorityFeePerGasstringEIP-1559 priority fee per gas in wei
valuestringTransaction value in wei
datastringTransaction data payload (0x for simple transfers)
statusenumBroadcast status (BROADCASTED)

Use Cases

  • Broadcast hardware wallet signed transactions
  • Submit transactions signed client-side for direct control over construction
  • Re-broadcast stuck transactions with higher gas parameters
  • Integrate with external signing solutions

Required Permission

transactions:create

On this page

  • Request Body
  • Transaction Flow
  • Response Fields
  • Use Cases
  • Required Permission
  1. Cubewire Wallet
  2. Manage Transactions
  3. Broadcast a signed transaction

Broadcast a signed transaction

Broadcast a pre-signed transaction directly to the blockchain network. This endpoint bypasses the standard workflow orchestration and policy evaluation, executing the transaction as-is.

Request Body

FieldTypeRequiredDescription
signedTransactionHexstringYesRLP-encoded signed transaction (0x prefix)
chainIdnumberYesBlockchain network ID (must match transaction)

Transaction Flow

  1. Decode — Parse and validate the signed transaction hex
  2. Verify — Confirm chain ID matches the transaction
  3. Balance Check — Verify sender has sufficient funds/gas
  4. Broadcast — Submit transaction to blockchain network
  5. Return — Provide transaction hash and metadata

Important: This endpoint does NOT perform policy evaluation or trigger approval workflows. The transaction is broadcast exactly as signed.

Response Fields

FieldTypeDescription
transactionHashstringBlockchain transaction hash (0x...)
fromstringSender address extracted from signature
tostringRecipient address (null for deployments)
noncenumberTransaction nonce
chainIdnumberNetwork where transaction was broadcast
gasLimitstringGas limit from transaction
gasPricestringGas price in wei (legacy pre-EIP-1559 transactions)
maxFeePerGasstringEIP-1559 max fee per gas in wei
maxPriorityFeePerGasstringEIP-1559 priority fee per gas in wei
valuestringTransaction value in wei
datastringTransaction data payload (0x for simple transfers)
statusenumBroadcast status (BROADCASTED)

Use Cases

  • Broadcast hardware wallet signed transactions
  • Submit transactions signed client-side for direct control over construction
  • Re-broadcast stuck transactions with higher gas parameters
  • Integrate with external signing solutions

Required Permission

transactions:create

On this page

  • Request Body
  • Transaction Flow
  • Response Fields
  • Use Cases
  • Required Permission