Quote from: jl777 on September 10, 2015, 06:07:04 AM

Quote from: wtogami on September 10, 2015, 03:10:32 AM

Code:

2015-09-07 16:23:58 ERROR: AcceptToMemoryPool : not enough fees 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3, 100000 < 200000

It is not propagating because it has insufficient fees. There is no bug here.

Can you dumprawtransaction and paste the output here? If you do I can explain why the fees are insufficient. I'm guessing it has an output that is too small and thus triggering the fee penalty? BTW, what client created this transaction?

I generated this tx with my code, but it was an earlier version and might have had some problems. I was not awareof a fee penalty, it is as follows:

Code:

{
"txid": "3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3",
"version": 1,
"locktime": 0,
"vin": [
{
"txid": "13a791824888a75cda2ed94b39c3ced90a06624d294084a0afd738d765525683",
"vout": 1,
"scriptSig": {
"asm": "304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b1801 031e8ab7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26",
"hex": "47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26"
},
"sequence": 4294967295
}
],
"vout": [
{
"value": 0.00020000,
"n": 0,
"scriptPubKey": {
"asm": "OP_HASH160 557ae5bf81ec20138026548ddca5654ac8af27cf OP_EQUAL",
"hex": "a914557ae5bf81ec20138026548ddca5654ac8af27cf87",
"reqSigs": 1,
"type": "scripthash",
"addresses": [
"39UzauyJ9iDQy4wS1UFDx1LUFP48HnMYsY"
]
}
},
{
"value": 0.50854610,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 1c660332b01b497e9f3e8a04da866e66bd99505e OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9141c660332b01b497e9f3e8a04da866e66bd99505e88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"LMp7PY4ymHLnaECvbWxZB245uKsr3jK9zz"
]
}
}
]
}

I used the latest QT Litecoin Core version v0.10.2.2 (64-bit)

I guess my question is how did this tx get accepted locally (and in other nodes) if it has insufficient fees to be confirmed? And why isnt 0.001 enough of a fee? Are you saying that if the output was bigger, the fee would have been enough?

James

Yes I think the tx will pass through if you sign it again with bigger output, or you just pay a larger fee.