Topic: [ANN] Litecoin - a lite version of Bitcoin. Launched! - page 278. (Read 1467278 times)
ShapeShift has added a buy/sell feature to the real time market data website CoinCap.io! You can now buy or sell Litecoin straight from the market data website. Learn more about this here: http://bit.ly/1UVFZ7m
Code:
"vout": [
{
"value": [b]0.00020000,[/b]
{
"value": [b]0.00020000,[/b]
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
https://github.com/litecoin-project/litecoin/commit/72707115a7d968674866a1ddfc45348c4cb3e712
Litecoin: Anti-spam mechanism adds 1000 bytes to the fee for each output smaller than DUST_THRESHOLD
Litecoin's stock policy has had this fee penalty for each too small output since 2011. Your code must calculate fees in the same manner or it will fail to relay or be mined by nodes operating under the stock policy. Nothing stops submitting a raw transaction to your own node, and some explorers accept non-standard transactions such as this, but the vast majority of the network will not accept it. You can test this by watching debug.log of any standard node.
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?
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)"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 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
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 am testing out atomic swaps of LTC and to do this, I needed to make custom p2sh redeemscripts.
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
Not there
blockr.io saw it: http://ltc.blockr.io/tx/info/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
as did bchain.info: https://bchain.info/LTC/tx/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
But a couple of other explorers did not have a page for the transaction.
it does seem like it is a bug
There is a 0.001 txfee, so that should be enough. I dont want to raise false alarm, but if this one tx can get into the rawmempool and stay there forever, what prevents a million of them to explode all the nodes?
James
Hi James,
I'll bring this to the devs attention. Thanks
Andrew
I am testing out atomic swaps of LTC and to do this, I needed to make custom p2sh redeemscripts.
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
Not there
blockr.io saw it: http://ltc.blockr.io/tx/info/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
as did bchain.info: https://bchain.info/LTC/tx/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
But a couple of other explorers did not have a page for the transaction.
it does seem like it is a bug
There is a 0.001 txfee, so that should be enough. I dont want to raise false alarm, but if this one tx can get into the rawmempool and stay there forever, what prevents a million of them to explode all the nodes?
James
No fee trades not included.
Halvings are buy before the rumor, sell before the news.
well I would say that rumor of halving was when LTC prices were in the $7-$10 range. So before that ----> higher than $10.
Sell before actual halving $5-$7.
No that seems to not have worked out to be a profitable trade assuming we use your methodology as I described it.
I am testing out atomic swaps of LTC and to do this, I needed to make custom p2sh redeemscripts.
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
Not there
blockr.io saw it: http://ltc.blockr.io/tx/info/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
as did bchain.info: https://bchain.info/LTC/tx/3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
But a couple of other explorers did not have a page for the transaction.
I am testing out atomic swaps of LTC and to do this, I needed to make custom p2sh redeemscripts.
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
It is working fine with BTC, but with LTC even though it was accepted into the getrawmempool, it is not being confirmed
txid: 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3
010000000183565265d738d7afa08440294d62060ad9cec3394bd92eda5ca788488291a71301000 0006a47304402205b06b4a4471314cc423214088bd6c75546a0c3765d61405e6e2550674a474e17 022043b73e6357381fbd9c8ac81dcc364e34d46560983bfdb08b162f54f019ec3b180121031e8ab 7edc770169773bb1716904b70ed79a171d11e9af75340949c8949d72a26ffffffff02204e000000 00000017a914557ae5bf81ec20138026548ddca5654ac8af27cf87d2fa0703000000001976a9141 c660332b01b497e9f3e8a04da866e66bd99505e88ac00000000
It might be due to lack of txfee, but not sure if it should have been accepted locally without enough fees.
My question is if txid 3b90916d8442342813c4b6415f699cdd2846f668881c7ce8f5966a16a3bf47f3 has propagated into other nodes or if it is just stuck in my node.
I would appreciate if somebody could run getrawmempool and see if this txid is there. If it is, this would be an attack vector to overflow the rawmempool globally.
The more advanced question is why it isnt being confirmed.
James
I am now offering litecoin node hosting over a https://cryptospout.com/cryptonode.php It's 100% automated have a node up and running in minutes.
Anyway LTC no mather what we will see 20 dollar soon
Due enlighten us in your wisdom, how can you know
It starts with bitcoin rise ltc will follow
You can also watch the video litecoin halving
http://www.litecoinblockhalf.com/ no need for wisdom
you are an heromember to shame you ask such a question.
Im 99.99% sure litecoin wil sky rocket.
These things could happend in 1month maybe 3months or longer like year
Of course depends on popularity and buyers bitcoin litecoin.
So basically, it's just speculation, because you went from sure to 99% from 3 months to a year, those predictions are bullshit, halving mostly doesnt lead to price increase, the latest price bubble is created by the big holders of ltc, research that, it's pure manipulation, nothing to do with actual value...
Anyway LTC no mather what we will see 20 dollar soon
Due enlighten us in your wisdom, how can you know
It starts with bitcoin rise ltc will follow
You can also watch the video litecoin halving
http://www.litecoinblockhalf.com/ no need for wisdom
you are an heromember to shame you ask such a question.
Im 99.99% sure litecoin wil sky rocket.
These things could happend in 1month maybe 3months or longer like year
Of course depends on popularity and buyers bitcoin litecoin.
Anyway LTC no mather what we will see 20 dollar soon
Due enlighten us in your wisdom, how can you know
This ain't bullshit coin this is Litecoin we wil see positive signs in short time
Sorry I couldnt resist after reading that
exactly
This ain't bullshit coin this is Litecoin we wil see positive signs in short time
Sorry I couldnt resist after reading that
This ain't bullshit coin this is Litecoin we wil see positive signs in short time
Halvings are buy before the rumor, sell before the news.
Halving day and nothing happened to price lol fingers crossed though.
Jump to: