transaction_v1_broadcast - Bittensor RPC Method
Broadcast a signed transaction to the Bittensor network using the new JSON-RPC v2 spec.
Broadcasts a signed, SCALE-encoded transaction to the Bittensor network via the new JSON-RPC v2 transaction API. Unlike the legacy author_submitExtrinsic, this method is designed for fire-and-forget submission -- it broadcasts the transaction to peers without waiting for pool validation results. Use transactionWatch_v1_submitAndWatch if you need to track the transaction lifecycle.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
transaction | string | Yes | Hex-encoded SCALE-encoded signed transaction. |
Response
| Field | Type | Description |
|---|---|---|
result | null | Acknowledges the transaction has been accepted for broadcast. Does not guarantee inclusion in a block. |
Code Examples
Use Cases
- Transaction submission -- Broadcast signed Bittensor transactions (TAO transfers, subnet registrations, staking operations) to the network.
- Fire-and-forget -- Submit transactions without maintaining a WebSocket connection to track their status.
- High-throughput submission -- Broadcast many transactions quickly without waiting for individual pool validation responses.
Notes
- This method is part of the new JSON-RPC v2 specification and may not be available on all node configurations.
- A successful response only means the transaction was accepted for broadcast. It does not guarantee pool acceptance or block inclusion.
- For transaction lifecycle tracking, use
transactionWatch_v1_submitAndWatchinstead. - The transaction must be properly signed with a valid nonce. Use
system_accountNextIndexto get the correct nonce.
Related Methods
author_submitExtrinsic-- Legacy method to submit and validate a transactiontransactionWatch_v1_unwatch-- Stop watching a transaction submitted via the watch APIsystem_accountNextIndex-- Get the correct nonce for transaction constructionauthor_pendingExtrinsics-- View pending transactions in the pool