transaction not accepted

[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.

[1714046328]

1714046328

[1714046328]

1714046328

[1714046328]

1714046328

[1714046328]

1714046328

[1714046328]

1714046328

[1714046328]

1714046328

[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.