Topic: There was a problem sending your transaction: error: {u'message': u'TX rejected (Read 1401 times)
March 17, 2014, 09:59:31 AM
The transaction appears to be missing signatures. Did you sign the transaction?
March 16, 2014, 09:11:14 PM
Then it's a low fees issue, bitcoind on electrum servers is rejecting transaction due to low fees.
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
So the transaction has 2 inputs and 29 outputs. I just now tried with a fee of 0.001 BTC and it still returns the exact same error. How much of a fee do you think would be appropriate?
It shouldn't be that much.
Inputs are ~200 bytes each.
Outputs are ~40 bytes each.
Your tx is something on the order of 2KB so even 0.2 mBTC (maybe 0.3 mBTC) should be sufficient. There is something else the server doesn't like about it. If you decode the raw tx and paste the json some people may be able to help otherwise I would verify all the inputs are valid and haven't been double spent. Verify all the addresses are valid and there is no duplicated address in the output. Verify the input = output + intended fee.
This is what I get when I save into a .txn file
{
"hex": "01000000028e239d644e655a34b16f4fcc39e31b263b004752453da3a2f933a93915bf228b00000 0008a47304402201208e93b66c932dfd40112f26616bf3982c08edd3f91c763a1d945b8aed58416 02200e25419ef27eb57cf9f73b784967b527fcb7964a34255fb65b71211119c1038e01410421615 35d6fc2f11723af826bbd12bc87c9f1b31ce34a5b381dd6b0e7f6860b79c7da73288ccc3664f860 08f72d48ae3eaf5339ccbcebdcaac49264843a7118d2ffffffff49aed6daa569cbbe3e352c44b2f 3d159cdf52de0b11087bc5ad6353506a54ae8010000008a473044022006c30c320d9ee5897f60ad b179875f98d0dbaaf681fde84f80c44f2076907a2802203c4fb86c660c26160473a383cd08f6e56 a88a7a093e775ecb80870679baaf1370141042161535d6fc2f11723af826bbd12bc87c9f1b31ce3 4a5b381dd6b0e7f6860b79c7da73288ccc3664f86008f72d48ae3eaf5339ccbcebdcaac49264843 a7118d2ffffffff1d6ce20000000000001976a9140933b4c4307561fef76de8dc446f9147e4f04a 7988ac00a50200000000001976a9145f021e5b019cdc586963941c736dc7ae32b340f388aca07f0 a00000000001976a914d3f249f22996e4bccd478d9521c36cce9fe7fd6c88ac90b4040000000000 1976a9145f3905c286831a49810cc11623aa33614bb747b488acf8160000000000001976a914b17 81ae9f5a9957b844f1453c0d6d6bb49b93dd588aca4160000000000001976a914096a35acea7f71 3624a1d13008876d46ab9bf0ad88ac55150000000000001976a914200903347d96f7165e83d597d aee5240dc5a299c88ac33360100000000001976a9148b3c5341cb929d142397abd12c93cc49d017 fe5588ac887c0000000000001976a914050d54c8846ac18e836d41844752ca8f96529d2488ac0f8 10000000000001976a9140cc7588cd9c9cfcd10e236626973ab38222b911488ac8c2f0000000000 001976a9149b43ae848198d963445a02ad5d5b8d1bf2e77ff288ac0e360200000000001976a9141 8b2d5fc1da98b88e42d24a2be759262c7b98fd988ac33800600000000001976a91493a3f1b9b1be bbf82542d6c00a970e7bbf6c58ae88ac40b30000000000001976a9147dd4ea30b40c9b0c43d4d56 b10725b364cbfe9e788acdf3a0000000000001976a914cdf7a37df9d42551c6984f306a940efc3c 270df888acb3c40200000000001976a9141680415d29f091cdfd12f6e8628f23b17085872888aca e990200000000001976a914bdfbf2db3fa9f7f67cc13deec6a4c58a1e75b4a088ac5fc901000000 00001976a914250c4acb0f7d795dfb447db96d1400ef081ccfb488ac7b7f0b00000000001976a91 4559705f3fdfb1dabc6fbf3f9815170b9961a8b7788ac55150000000000001976a914085bc7458a 8e423014b8c836094a820ee44f829688ac9b380000000000001976a914102542a08a73613fee3d5 0af8b2416d48dbdc2f688ac41150000000000001976a91498d520d3b6bf71a544350413cdc98069 22e0ef6f88ace1a20100000000001976a914d3bdc10c8b9bc72b8a55f691966e29a489231fd688a c3f4f0000000000001976a9141a2cad83ca6762216a709b1fc180685673f3931c88acca3d000000 0000001976a91442ea2e5636bd9d49c2562e49fc06d42ed47ee63788ace3920200000000001976a 9144e36b96546b591e5eac1c57f69496e4a954b4bb288aca4e80400000000001976a914dcd3b9ba c3574f44b2e91b7ed128c34f25b4221e88ac6ce20000000000001976a914c53fc2d42fa741e6621 b960da9bf9e6a4e8eb21a88ac43010700000000001976a914e0f14ed165caa82c40d82c28b9b118 b5ee9245c788ac00000000",
"complete": true
}
March 16, 2014, 08:51:34 PM
Then it's a low fees issue, bitcoind on electrum servers is rejecting transaction due to low fees.
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
So the transaction has 2 inputs and 29 outputs. I just now tried with a fee of 0.001 BTC and it still returns the exact same error. How much of a fee do you think would be appropriate?
It shouldn't be that much.
Inputs are ~200 bytes each.
Outputs are ~40 bytes each.
Your tx is something on the order of 2KB so even 0.2 mBTC (maybe 0.3 mBTC) should be sufficient. There is something else the server doesn't like about it. If you decode the raw tx and paste the json some people may be able to help otherwise I would verify all the inputs are valid and haven't been double spent. Verify all the addresses are valid and there is no duplicated address in the output. Verify the input = output + intended fee.
March 16, 2014, 08:43:41 PM
Then it's a low fees issue, bitcoind on electrum servers is rejecting transaction due to low fees.
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
Just increase fees and try again or manually create and broadcast transaction but it can take some hours to some days, to get confirmations.
Ps: How big is your bulk transaction? I mean how many addresses?
So the transaction has 2 inputs and 29 outputs. I just now tried with a fee of 0.001 BTC and it still returns the exact same error. How much of a fee do you think would be appropriate?
March 16, 2014, 11:05:44 AM
Newly mined coins have to age 120 confirmations before you can use them.
The address that my coins are on has 617 confirmations.
Transactions have confirmations not addresses.
Sorry that's what I meant.
March 16, 2014, 05:56:10 AM
Newly mined coins have to age 120 confirmations before you can use them.
The address that my coins are on has 617 confirmations.
Transactions have confirmations not addresses.
March 15, 2014, 08:16:18 PM
Newly mined coins have to age 120 confirmations before you can use them.
The address that my coins are on has 617 confirmations.
March 15, 2014, 04:36:30 PM
I think your tx size is too big (due to several small inputs and outputs) and needs more fees.
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
Quote
code -22 is the default answer from bitcoind if it doesn't accept the tx. tx size could be too large for the fee or inputs could already be spent and so forth. The only easy way to debug is to get a server operator to look at the debug file of bitcoind when you send your tx.
They are from pool mining but they've gone through a few internal transactions after that. What exactly are newly mined coins?
I tried upping the tx fee to 0.0004 and it still doesn't like it. How high do you think I should go?
Newly mined coins have to age 120 confirmations before you can use them.
March 15, 2014, 03:29:19 PM
I think your tx size is too big (due to several small inputs and outputs) and needs more fees.
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
Quote
code -22 is the default answer from bitcoind if it doesn't accept the tx. tx size could be too large for the fee or inputs could already be spent and so forth. The only easy way to debug is to get a server operator to look at the debug file of bitcoind when you send your tx.
They are from pool mining but they've gone through a few internal transactions after that. What exactly are newly mined coins?
I tried upping the tx fee to 0.0004 and it still doesn't like it. How high do you think I should go?
March 15, 2014, 02:23:45 PM
I think your tx size is too big (due to several small inputs and outputs) and needs more fees.
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
or do you have newly mined coins?
Ps:
https://github.com/spesmilo/electrum/issues/548
Quote
code -22 is the default answer from bitcoind if it doesn't accept the tx. tx size could be too large for the fee or inputs could already be spent and so forth. The only easy way to debug is to get a server operator to look at the debug file of bitcoind when you send your tx.
March 15, 2014, 01:38:22 PM
Ah sorry I forgot to mention that I also tried changing the server, but I'll try again and check the thread, thanks!
Ah yes I remember that thread, but I'm actually not clear on what it's suggesting. How do I "prioritize" an address. I only have one address with coins in it on there right now.
I also tried increasing my tx fee to 0.0003, but still no joy =(
March 15, 2014, 01:22:48 PM
Ah sorry I forgot to mention that I also tried changing the server, but I'll try again and check the thread, thanks!
March 15, 2014, 01:18:53 PM
March 15, 2014, 01:14:44 PM
For the past week I've been trying to send a bulk transaction via CSV file and always get this error:
There was a problem sending your transaction:
error: {u'message': u'TX rejected', u'code': -22}
I also tried moving the funds into another wallet and tried from there, same thing.
It used to work fine before.
What can I do to address this?
There was a problem sending your transaction:
error: {u'message': u'TX rejected', u'code': -22}
I also tried moving the funds into another wallet and tried from there, same thing.
It used to work fine before.
What can I do to address this?
Jump to: