4

It seems that the fee provided by you is too low and it's total amount is lower than relay fee (==the minimum fee amount that can guarantee that your transaction would be retranslated to the net). You can find this amount by calling getinfo function and taking "relayfee". Currently "relayfee" is 0.00001000 at BTC Mainnet.


4

The easiest way to do this by importing the address you generated on the offline Bitcoin Core client into an online fully synced Bitcoin-Core. The command is: bitcoin-cli importaddress <address>. The benefit of importing this address into the synced Bitcoin-Core machine is that you can use it as a watch-only address which will allow you to see all the ...


3

The fee is whatever you define in the raw transaction, based on the difference between inputs and outputs. sendrawtransaction never changes it. However, as a safety measure, it will normally reject your transaction if the fee exceeds a certain "absurd" threshold, so that you don't accidentally lose a lot of coins by miscalculating your raw transaction. If ...


3

What exactly is the high fee that Bitcoin Core is talking about? Does this client have exactly fixed number? Bitcoin Core has a hard limit for what it considers to be an absurdly high fee, which is 0.1. Other node software may not impose this limit, or may have a different value for it. Note that this is not part of the standard tx rules. It is simply a ...


3

Bitcoind does not index transactions for non-wallet addresses. If you wish to build this yourself, you will need to: Enable txindex=1 in your bitcoin.conf Rescan the chain Set up blocknotify and then parse the chain block by block, building an index of which outputs have been spent, and which haven't, and which addresses are involved in each transaction ...


3

You provided the amount incorrectly. The amount is 0.54551 not 545500. This is important as Segwit inputs include the previous output's amount in the signature. Providing the wrong amount will result in the wrong signature which will then fail validation.


2

After writing up this question I finally figured out the answer from here: https://bitcointalk.org/index.php?topic=1680640.0. I will answer my own question for anyone who might be having the same problem. It turns out I needed to specify the amount of each input in signrawtransaction. bitcoin-cli signrawtransaction ...


2

EDIT: based on OPs request, I put examples in here: there are a lot of examples for different tx types on bitcoin.org, in the developer examples. Basically you will need three steps. Assuming you are on OpenBSD/MacOS/Linux, you can go this way: 1.) createrawtransaction - this is what you have already, and it looks ok. I don't know if the previous tx ID or ...


1

That error means you did not provide a high enough transaction fee on your transaction.


1

That error means that you are trying to spend more money than you have inputs for. In other words, value in < value out. You need to add more inputs so the total input value exceeds the total output value. You need to get unspent outputs from previous transactions which you have received at the address your trying to send from. Have a look at ...


1

Postdata must be String, not Object. ('tx_hex=...')


1

First of all, these are not P2SH-P2WPKH, these are normal P2WPKH outputs. They are not related to P2SH at all. The problem here is probably that the amount is incorrect. If you are providing the previous output data yourself, then the amounts is incorrect. You have it as 0.000560 but the actual amount is 0.00055999. Since Segwit commits to the amount in the ...


1

You can use signrawtransaction, this method accept an array of private keys as an argument. Parameter #3—private keys for signing: An array holding private keys. If any keys are provided, only they will be used to sign the transaction (even if the wallet has other matching keys). If this array is empty or not used, and wallet support is enabled, ...


1

You need to be running a full bitcoin node like Bitcoin Core, or use a wallet that connects to a bitcoin node. Bitcoin nodes connect to multiple other nodes and distribute the transaction and block data between each other according to the Bitcoin protocol. Blockchain.com is also running a bitcoin node, and will receive the transaction through the network ...


1

I had the same error, but perhaps different problem. See: Trying rawtransaction BCC/BCH with failed CHECK(MULTI)SIG. What is wrong? It is important that the hash used for signing is based on the same data actualy send + sigscript. Any difference will result in a different signature. Also for the signature the amounts of the outpoints need to be used and ...


1

Since i'm sure others will encounter the same problem, the solution is that BCC requires you to put in the amount-tag when signing a transaction. You have to put in the full amount that is shown on the listunspent-command though, else you won't be able to send the transaction.


Only top voted, non community-wiki answers of a minimum length are eligible