transaction not accepted

[Roccdrummer]

Hello, I've been receiving bitcoin properly from my miner/pool.  But i cannot send bitcoin!  I've tried everything.  Rebooting, restarting, starting bitcoin-qt manually with the setting unchecked,  rescanning , rescanning and rebuilding....   It always says transaction not accepted and shows a link to the blockchain where it says transaction not found.  Please help.  Thanks.

[1714790040]

1714790040

[1714790040]

1714790040

[1714790040]

1714790040

[1714790040]

1714790040

[1714790040]

1714790040

[ranochigo]

What mining pool are you using? If you are using a pool which pay the user by including their addresses in the coinbase, you need at least 120 confirmations for it to be spent. Could you post the address in question? Is your Bitcoin Core on the latest version? Are the transactions all confirmed when you check the blockchain?

[Roccdrummer]

I am using Antpool.   I just received my payment from today and it was 4/6 confirmations when i last looked, on the Armory (within 1/2 hour).   All other daily received payments are fully confirmed.  It lists all my bitcoins as available except the payment I just received that had 4/6 confirmations.  I have been mining there for almost a year.  

I have the latest Bitcoin core and Armory.

I just rechecked the setting to allow bitcoind and bitcoin qt to run in the background through Armory and am rescanning/rebuilding right now.   Maybe I could try a different address to send to because the address I am trying to send to is no good for some reason?  Is there a way to check the address?
This is actually the first time I've tried to send bitcoin.  I have the default 0.0001 transaction fee.  I tried once with a 0.0002 fee.




Thanks much.

[Roccdrummer]

Can I send you or somebody like 0.001 bitcoin to see if it works with another address?  Is that too small of a transaction?  The default fee of 0.0001 would be fine right?

Or i guess i could send it to myself.   Just waiting on the rebuild/rescan.

[achow101]

There is something wrong with your bitcoin core installation which is making it reject the transactions. Do you have any special configuration for it that your are using?

[Roccdrummer]

I used all default everything.  No special paths or anything.  Does that mean I have to uninstall and reinstall bitcoin core?  For sure?   Just wondering.... how do you know that?  Thanks.

[Roccdrummer]

It seemed like when I installed bitcoin core, it took less than 5 hours to do everything and be ready and it was all automatic, while with armory, it took like 72 hours and I had to figure out a crapload of things to do over and over in order to make it work though...

[Roccdrummer]

I tried to send you the bitcoin but I still got the same transaction not accepted message.   (I took a screenshot but i guess i prob have to have an image host to link it here ya?  I can't remember which one i used its been so long, i'll figure that out later)

The popup window says:

-Transaction not accepted-

The transaction that you just executed, does not appear to have been accepted by the Bitcoin network yet. This can happen for a variety of reasons.

On some occasions the transaction actually will succeed and this message is displayed prematurely. To confirm whether the the transaction actually succeeded, you can try this direct link to blockchain.info:

https://blockchain.info/tx/ed2416ba06870c2a6d28...

If you do not see the transaction on that webpage within one minute, it failed and you should attempt to re-send it. If it does show up, then you do not need to do anything else -- it will show up in Armory as soon as it receives one confirmation.

If the transaction did fail, it is likely because the fee is too low. Try again with a higher fee. If the problem persists, go to "Help" and select "Submit Bug Report". Or use "File" -> "Export Log File" and then attach it to a support ticket at https://bitcoinarmory.com/support




When i click the link , it says "transaction not found"


thx for help

[Carlton Banks]

Isn't AntPool like p2pool, in that your share payouts are coinbase? If so, remember that you have to wait at least 100 blocks subsequent to a given coinbase reward before any Bitcoin client will relay that output as a transaction. Are you sure you're using old enough coinbase to send a valid transaction?

[Roccdrummer]

Yep.   I've never spent any bitcoin and i've been mining almost a year.

[goatpig]

What's the top block advertized on Bitcoin Core? Armory?

[Roccdrummer]

I'm sorry.  I don't know how to check that.   How do i do it?   thanx


lol i was looking through the log files

[ranochigo]

Isn't AntPool like p2pool, in that your share payouts are coinbase? If so, remember that you have to wait at least 100 blocks subsequent to a given coinbase reward before any Bitcoin client will relay that output as a transaction. Are you sure you're using old enough coinbase to send a valid transaction?

If I'm correct, AntPool doesn't pay the users using Coinbase. All the Coinbase are sent to one address which makes it unlikely for them to be paying users using it. https://www.blocktrail.com/BTC/pool/antpool. I have addressed this above already.

I'm sorry.  I don't know how to check that.  How do i do it?   thanx

I don't use armory often but you need to check the number of blocks on the bottom right of Armory for it.

[Roccdrummer]

Just now opened Armory again.  Last block received is 4 seconds ago upon opening.  Connected 379749 blocks....  

Just opened Bitcoin qt ...  connected up to date...  379749 blocks of transaction history.     @  9:34 am EST

 

a minute later bitcoinqt goes up to 379750 blocks on its own

on armory at 9:44 it says 379751 blocks... last block received 6 minutes ago...

[Holliday]

Are you trying to send dust?

[Roccdrummer]

definitely not

[achow101]

Can you post the raw hex of a transaction you are trying to send? I will try to broadcast it from my node. If that works, then there must be something wrong with your bitcoin core installation.

To get the hex, send the transaction normally then right click it in the transaction list and click view details. Then click copy hex and then paste that to a post.

[CircusPeanut]

This might be related to the "lowS" fix for a transaction maleability issue. The fix "lowS" fix is in Bitcoin 0.11.1. Armory currently does not apply the "lowS" fix, so Bitcoin 0.11.1 will refuse to relay some Armory transactions.

For now you should be able to just downgrade 0.10.2 (Edit: Actually 0.11 should work too) to broadcast, however as more nodes upgrade to 0.11.1 some Armory transactions will fail to propagate through the network.

We are working on a fix, and plan to release 0.93.3 with that fix and a few others by the end of the week.

[Holliday]

We are working on a fix, and plan to release 0.93.3 with that fix and a few others by the end of the week.

.93? What happened to .94 which was in "testing" since May?

https://bitcointalk.org/index.php?topic=1059942.0

[Stroto]

I have the same issue... but only with some of the transactions I make. I made no changes in paths or whatever and the problem continues after updating Bitcoin Core from v11.0 to v11.1. It has nothing to do with the address I send to or from or the amount send because sometimes it works sometimes it don't  

@CircusPeanut I had the issue before updating to v11.1 so I don't think it is caused by v11.1

To work around this problem when I really need to send asap I make an offline tx - sign it- copy the raw hex - and broadcast it on https://blockchain.info/pushtx it gets broadcasted but 90% the tx changes because of a conflicting tx.

[goatpig]

To work around this problem when I really need to send asap I make an offline tx - sign it- copy the raw hex - and broadcast it on https://blockchain.info/pushtx it gets broadcasted but 90% the tx changes because of a conflicting tx.

I fixed that in 0.94, but as Holliday puts it, it's been delayed a lot.

.93? What happened to .94 which was in "testing" since May?

https://bitcointalk.org/index.php?topic=1059942.0

There could be closure on this situation soon.

[Carlton Banks]

This might be related to the "lowS" fix for a transaction maleability issue. The fix "lowS" fix is in Bitcoin 0.11.1. Armory currently does not apply the "lowS" fix, so Bitcoin 0.11.1 will refuse to relay some Armory transactions.

Does Armory sign all transaction with +ve S, or just some? And is this the first time this has been announced publicly?

[CircusPeanut]

@CircusPeanut I had the issue before updating to v11.1 so I don't think it is caused by v11.1

There is more than one reason why transactions might not be accepted by core.

To be certain that you are encountering the same issue that I'm fixing right now, you have to find this string in bitcoin/debug.log

ERROR: AcceptToMemoryPool : nonstandard transaction: scriptpubkey

For instance if you attempt a double spend, everything acts the same failing to use "lowS", but you find this in bitcoin/debug.log:

ERROR: AcceptToMemoryPool : inputs already spent

Another one that I think is probably what you encountered is:

ERROR: AcceptToMemoryPool : free transaction rejected by rate limiter

0.93.2 has a bug in it that provides a very old age for inputs when it tries to verify the fee you specified. So instead of telling you that the fee paid is not enough for a transaction with many inputs, it thinks that since all of the inputs very old, it should be free and doesn't warn you need a bigger fee. Then transaction gets rejected by core, and you don't know why unless you look at the log.

Goatpig... please make sure your fix for that gets into this bug fix release.

[CircusPeanut]

@CircusPeanut I had the issue before updating to v11.1 so I don't think it is caused by v11.1

...
ERROR: AcceptToMemoryPool : nonstandard transaction: scriptpubkey
...
ERROR: AcceptToMemoryPool : inputs already spent
...
ERROR: AcceptToMemoryPool : free transaction rejected by rate limiter

All of these error messages may be wrong. I was getting multiple different issues on my test cases.

I think scriptpubkey was for unnecessary 0x00 padding (a different malleability issue).

I'm pretty sure the ERROR for Low S violation in 0.11.1 is:

ERROR: .... Non-canonical signature: S value is unnecessarily high

[mullick]

@CircusPeanut I had the issue before updating to v11.1 so I don't think it is caused by v11.1

...
ERROR: AcceptToMemoryPool : nonstandard transaction: scriptpubkey
...
ERROR: AcceptToMemoryPool : inputs already spent
...
ERROR: AcceptToMemoryPool : free transaction rejected by rate limiter

All of these error messages may be wrong. I was getting multiple different issues on my test cases.

I think scriptpubkey was for unnecessary 0x00 padding (a different malleability issue).

I'm pretty sure the ERROR for Low S violation in 0.11.1 is:

ERROR: .... Non-canonical signature: S value is unnecessarily high

How many utxo's are in the wallet? it may be failing due to being to large of a tx in kb. You say you have been mining for a year and havent moved any. Im assuming you have a hefty build up of utxo's. Try sending multiple smaller amounts and see if they go through. If you know your average utxo size try sending that * 100

[CircusPeanut]

Here's a work around that you should be able to use until we release a fix:

When creating a transaction check the box for "create unsigned transaction" and click continue. Export the transaction, then import it and sign it. If you use cold storage you are already doing these steps.

Then instead of broadcasting the transaction, click the link labeled "For more information about this transaction". That opens up a Transaction Info dialog. At the bottom, click the "Copy raw TX (hex)" button.

Paste the raw transaction to https://blockchain.info/pushtx  and click submit transaction.

Basically blockchain has already made the necessary fix to guarantee that the "Low S" is used, and applies it to raw transactions.

[Stroto]

Here's a work around that you should be able to use until we release a fix:

When creating a transaction check the box for "create unsigned transaction" and click continue. Export the transaction, then import it and sign it. If you use cold storage you are already doing these steps.

Then instead of broadcasting the transaction, click the link labeled "For more information about this transaction". That opens up a Transaction Info dialog. At the bottom, click the "Copy raw TX (hex)" button.

Paste the raw transaction to https://blockchain.info/pushtx  and click submit transaction.

Basically blockchain has already made the necessary fix to guarantee that the "Low S" is used, and applies it to raw transactions.

You don't need to export it. In expert mode:
- create unsigned tx
- copy to clipboard
- continue
- paste
- sign
- copy raw tx (the button is just there in expert mode so no need to open additional info)
- https://blockchain.info/pushtx
- submit

[bertani]

In my case armory (last version, bitcoind 0.11.0) armory is often creating the tx with malleated inputs (which were then not confirmed) so txid is invalid and the tx is rejected by any node

[yslyung]

Here's a work around that you should be able to use until we release a fix:

When creating a transaction check the box for "create unsigned transaction" and click continue. Export the transaction, then import it and sign it. If you use cold storage you are already doing these steps.

Then instead of broadcasting the transaction, click the link labeled "For more information about this transaction". That opens up a Transaction Info dialog. At the bottom, click the "Copy raw TX (hex)" button.

Paste the raw transaction to https://blockchain.info/pushtx  and click submit transaction.

Basically blockchain has already made the necessary fix to guarantee that the "Low S" is used, and applies it to raw transactions.

You don't need to export it. In expert mode:
- create unsigned tx
- copy to clipboard
- continue
- paste
- sign
- copy raw tx (the button is just there in expert mode so no need to open additional info)
- https://blockchain.info/pushtx
- submit

thx for the workaround ... i was also thinking about manually pushing it out & yes it works.

was working normally till qt upgraded to 11.1

looking fwd to a fix.

thx again guys. got me worried for a couple of mins.

[Carlton Banks]

Well, I don't quite get this bug. Even when I'm connected to 11.1 nodes, transactions with Armory confirm ok for me. Got a couple of rejections, but that was a day or two before this thread appeared anyway (and 11.1 nodes weren't very significant on the network then). All been fine since then, and 11.1 is ~ 20% of the network.

[jacubo]

Here's a work around that you should be able to use until we release a fix:

When creating a transaction check the box for "create unsigned transaction" and click continue. Export the transaction, then import it and sign it. If you use cold storage you are already doing these steps.

Then instead of broadcasting the transaction, click the link labeled "For more information about this transaction". That opens up a Transaction Info dialog. At the bottom, click the "Copy raw TX (hex)" button.

Paste the raw transaction to https://blockchain.info/pushtx  and click submit transaction.

Basically blockchain has already made the necessary fix to guarantee that the "Low S" is used, and applies it to raw transactions.

You don't need to export it. In expert mode:
- create unsigned tx
- copy to clipboard
- continue
- paste
- sign
- copy raw tx (the button is just there in expert mode so no need to open additional info)
- https://blockchain.info/pushtx
- submit

Unfortunately this has not worked in my case. I have received a message 'Non-canonical signature: High S Value' from blockchain.info.

What else can be done to send this transaction?

Is there ETA on fixing this issue in newer version of Armory?

[Carlton Banks]

Is there ETA on fixing this issue in newer version of Armory?

High-S signing is fixed in 0.93.3, but if you're after official Mac binaries, you're not necessarily going to get them just yet. Downloads for Linux and Windows are in the top post of the thread "Armory 0.93.3  with BIP62 compliance"

[jacubo]

Is there ETA on fixing this issue in newer version of Armory?

High-S signing is fixed in 0.93.3, but if you're after official Mac binaries, you're not necessarily going to get them just yet. Downloads for Linux and Windows are in the top post of the thread "Armory 0.93.3  with BIP62 compliance"

Good news. Thank you.

I have finally managed to send mentioned transaction but during second attempt with much higher fees.