OP_RETURN transaction returns error

[odolvlobo]

I am trying to use Electrum to burn some dust UTXOs (547 sats) by creating a custom OP_RETURN transaction. Everything seems fine until I broadcast, and then I get this error:

The server returned an error when broadcasting the transaction.
Consider trying to connect to a different server, or updating Electrum.

The transaction was rejected because it is too large (in bytes).

Here is the "pay to" line (basically OP_RETURN <random 16 bytes>, 0):

Code:

OP_RETURN B03240B863832E01B44D3BCBC8308E8F, 0

Also, when I export the transaction and try to broadcast it through various sites, they have problems with the transaction. Here is the raw transaction (go ahead and try to broadcast it if you like):

Code:

0200000000010166988a1d333797b5c3cbf24b26212205d023f0ff8c7392f41594b1dee4ea953c3801000000fdffffff010000000000000000126a10b03240b863832e01b44d3bcbc8308e8f02473044022055022ae713c275e3feb37dd48f19bf07bc190e2f382038e3328e6ad939f93bbf0220431bc40ba285e9f167d45afd62986358f461744d0c301423e09aa2e1dc5874c1012102b514df7be7511c3baf72afb6df5d5cdcbd9989ef0ef1b294c5be9c7b28f68f2018aa0a00

This has worked in the past, but now it doesn't. Does anyone know what might be wrong and how I can succeed?

I am using Electrum 4.1.4 on a Mac with various servers.

[1715002865]

1715002865

[1715002865]

1715002865

[1715002865]

1715002865

[pooya87]

This is very weird indeed.
It seems that the Electrum node running bitcoin core thinks that your transaction has a weight bigger than 400,000 and rejects it with a tx-size error message and your Electrum client translates it to The transaction was rejected because it is too large (in bytes)..

I can't find this particular error anywhere else.

P.S. blockcypher explorer usually bypasses some of the standard rules and it pushed the tx but it doesn't seem to be propagating well https://live.blockcypher.com/btc/tx/21f045ec1677f98f6d94503742b1a871aefd75499ceb6f5a5fbd32643ab3d5d5/

P.P.S. Looking at your transaction, it is too small (78 bytes stripped). You should add more bytes to the OP_RETURN output to increase it to at least 82 bytes. This is the actual reason why bitcoin core's mempool rejects your transaction.

[nc50lc]

I'm getting a different error which is: tx-size-small, in Bitcoin Core.

I think it has to do with this recent commit: https://github.com/bitcoin/bitcoin/commit/7485488e907e236133a016ba7064c89bf9ab6da3
I don't know how OP_RETURN is calculated to the MIN_STANDARD_TX_NONWITNESS_SIZE but adding 4 more bytes enables me to broadcast a similar transaction (in testnet).

Code:

OP_RETURN 00000000B03240B863832E01B44D3BCBC8308E8F, 0

[Coding Enthusiast]

I took the liberty of starting a new issue based on this: https://github.com/spesmilo/electrum/issues/7483
Update: This is fixed in 07bd2fe.

[odolvlobo]

I'm getting a different error which is: tx-size-small, in Bitcoin Core.

I think it has to do with this recent commit: https://github.com/bitcoin/bitcoin/commit/7485488e907e236133a016ba7064c89bf9ab6da3
I don't know how OP_RETURN is calculated to the MIN_STANDARD_TX_NONWITNESS_SIZE but adding 4 more bytes enables me to broadcast a similar transaction (in testnet).

Code:

OP_RETURN 00000000B03240B863832E01B44D3BCBC8308E8F, 0

I suspect that is the problem. I added 4 more bytes and electrum was able to broadcast the transaction.