Broadcasting
Transaction Broadcasting from SPV Wallet
Last updated
Was this helpful?
Transaction Broadcasting from SPV Wallet
Last updated
Was this helpful?
The SPV Wallet broadcasts all valid transactions it receives or creates to ARC.
We use the first endpoint to determine the correct fee model to use when creating a transaction.
Thereafter we simply broadcast to ARC and expect a SEEN_ON_NETWORK txStatus response in most cases.
Usually a callbackUrl would be set for async status updates - but if you'd like to manually check the most recent state of a given transaction, you can use this:
This endpoint is used to get the current status of a previously submitted transaction.
The transaction ID (32 byte hash) hex string
This endpoint is used to send a raw transaction to a miner for inclusion in the next block that the miner creates.
Default double spend and merkle proof notification callback endpoint.
Whether we should have full status updates in callback or not (including SEEN_IN_ORPHAN_MEMPOOL and SEEN_ON_NETWORK statuses).
Timeout in seconds to wait for new transaction status before request expires (max 30 seconds, default 5)
Whether we should skip fee validation or not.
Whether we should force submitted tx validation in any case.
Whether we should skip script validation or not.
Whether we should skip overall tx validation or not.
Whether we should perform cumulative fee validation for fee consolidation txs or not.
Access token for notification callback endpoint. It will be used as a Authorization header for the http callback
Callback will be send in a batch
Which status to wait for from the server before returning ('QUEUED', 'RECEIVED', 'STORED', 'ANNOUNCED_TO_NETWORK', 'REQUESTED_BY_NETWORK', 'SENT_TO_NETWORK', 'ACCEPTED_BY_NETWORK', 'SEEN_ON_NETWORK')
<transaction hex string>