it was the bug everyone i got hit with some one told me i believe it now
ty for all the help and excuse me for getting upset it won't happen again .
cya
Topic: sent BTC with highest fee poss says i didn't (Read 1273 times)
Your low fee problem may be because you didn't leave bitcoin core up long enough. Bitcoin core needs to be up for some time in order to actually analyze the blockchain to determine the best fee. If you just start it up to send a transaction, then it won't have enough time to estimate the proper fee since it doesn't have enough data.
there is no low fee problem if you look up i got upset over some thing stupid sorry for that it was the bug . most of the time mine is up 8 to 9 hours a day and i normally don't send anything for maybe two hours after it's up .
I Know i read it , it upset me i shouldn't have let it upset me sorry for that .
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
There is no way to lost coins this way, at last one of the 2 transactions will always confirm.
I'm just learning about this kind of attack and what i can say is "It sucks".
[/quote
all ways remember nothing is a sure thing or 100 % even if it looks that way there is all ways that 1 to 2 % rather you or me except or not . unless your that higher power we wont go there about him
.
Your low fee problem may be because you didn't leave bitcoin core up long enough. Bitcoin core needs to be up for some time in order to actually analyze the blockchain to determine the best fee. If you just start it up to send a transaction, then it won't have enough time to estimate the proper fee since it doesn't have enough data.
I Know i read it , it upset me i shouldn't have let it upset me sorry for that .
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
There is no way to lost coins this way, at last one of the 2 transactions will always confirm.
I'm just learning about this kind of attack and what i can say is "It sucks".
I Know i read it , it upset me i shouldn't have let it upset me sorry for that .
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
but what would happen if it hit some one that has tons of coins and he or she lost them . we wouldn't hear the end of it. this stuff needs to be fixed before something really bad happens.
I didn't cause it but I 'm small fish think how a big fish would be he wouldn't lol it off either
Cya
my BTC wallet is set to send at fast ,i thought it did then i go look to see why it was taking so long and it sent it like.
Status: 0/unconfirmed, broadcast through 21 nodes
Date: 10/9/2015 01:05
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03581216 BTC
Transaction fee: -0.00000340 BTC
Net amount: -0.03581556 BTC
Transaction ID: c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a-000
and this was waiting when i went to look sorry forgot to put that in to .
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
whats up ? . NM
Guess this is why
https://bitcointalksearch.org/topic/new-transaction-malleability-attack-wave-another-stresstest-1198032
some one is playing around with the block chain again trying to make a point about some thing i guess .
sigh ..
Status: 0/unconfirmed, broadcast through 21 nodes
Date: 10/9/2015 01:05
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03581216 BTC
Transaction fee: -0.00000340 BTC
Net amount: -0.03581556 BTC
Transaction ID: c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a-000
and this was waiting when i went to look sorry forgot to put that in to .
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
whats up ? . NM
Guess this is why
https://bitcointalksearch.org/topic/new-transaction-malleability-attack-wave-another-stresstest-1198032
some one is playing around with the block chain again trying to make a point about some thing i guess .
sigh ..
Your transaction only got beaten by the malleability bug.
In easy words, you have the same transaction with 2 tx id's and only one of them will confirm.
https://tradeblock.com/bitcoin/tx/b7cc7d67d389a431dfdb7375a95e621895b97e57f0ea26c39005852dbfd89082 (confirmed)
https://tradeblock.com/bitcoin/tx/c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a (will never confirm)
You only need some time, maybe a couple of block to see that got fixed.
there is littte bar that lets you set it to fast which is one block so it says in the bitcoin core https://bitcoin.org/en/download
I have it set to fast but for some reason it keeps sending it at a low fee amount that just started so i checked my PC etc nothing on my PC, network etc is causing it i can find . I even went as far to do a new windows 10 install . so i will set it manually from now on and watch is as i send it i hate having coins tired up i need to make more coins with.
my problem is
how many day before that clears
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
and my wallet just resent the same thing again and it was at a ZERO balance . guess that good it looks like it just cleared . then the ass messing around with blockchain tried to send it i got this back but it cleared I got the coins back.
Status: conflicted, broadcast through 29 nodes
Date: 10/9/2015 20:03
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03543927 BTC
Transaction fee: -0.00037629 BTC
Net amount: -0.03581556 BTC
Transaction ID: c42aa518e0d35710e58b7851f56ccae7a449213f3229af0c7396e83afe52643a-000
see that fee thats what i thought it sent at .
here is were i got the coins back
Status: 2/unconfirmed
Date: 10/9/2015 20:03
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03543927 BTC
Transaction fee: -0.00037629 BTC
Net amount: -0.03581556 BTC
Transaction ID: b7cc7d67d389a431dfdb7375a95e621895b97e57f0ea26c39005852dbfd89082-000
so my fee was not low .
Time to get a hard ware wallet it looks like
cya sorry for all the heart ack but that was annoying.
now i double spend really
Warning! this transaction is a double spend. You should be extremely careful when trusting any transactions to/from this sender. 105767687
what a joke .
i got the coins that warning means jack to me i find it funny how it says you do something you don't .
cya
I have it set to fast but for some reason it keeps sending it at a low fee amount that just started so i checked my PC etc nothing on my PC, network etc is causing it i can find . I even went as far to do a new windows 10 install . so i will set it manually from now on and watch is as i send it i hate having coins tired up i need to make more coins with.
my problem is
how many day before that clears
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
and my wallet just resent the same thing again and it was at a ZERO balance . guess that good it looks like it just cleared . then the ass messing around with blockchain tried to send it i got this back but it cleared I got the coins back.
Status: conflicted, broadcast through 29 nodes
Date: 10/9/2015 20:03
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03543927 BTC
Transaction fee: -0.00037629 BTC
Net amount: -0.03581556 BTC
Transaction ID: c42aa518e0d35710e58b7851f56ccae7a449213f3229af0c7396e83afe52643a-000
see that fee thats what i thought it sent at .
here is were i got the coins back
Status: 2/unconfirmed
Date: 10/9/2015 20:03
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03543927 BTC
Transaction fee: -0.00037629 BTC
Net amount: -0.03581556 BTC
Transaction ID: b7cc7d67d389a431dfdb7375a95e621895b97e57f0ea26c39005852dbfd89082-000
so my fee was not low .
Time to get a hard ware wallet it looks like
cya sorry for all the heart ack but that was annoying.
now i double spend really
Warning! this transaction is a double spend. You should be extremely careful when trusting any transactions to/from this sender. 105767687
what a joke .
i got the coins that warning means jack to me i find it funny how it says you do something you don't .
cya
Do you really think 0.00000340 is a high fee? It should have been more around 0.0001 if you wanted a decent confirmation time.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
I clean it up some does that make better sense to you . I am well a ware 0.00000340 is to low that's not what i sent it at .
I'm confused, how can the fee from the broadcasted transaction be different than what you actually set?
What wallet software are you using?
Do you really think 0.00000340 is a high fee? It should have been more around 0.0001 if you wanted a decent confirmation time.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
I clean it up some does that make better sense to you . I am well a ware 0.00000340 is to low that's not what i sent it at .
SO now i am gonna keep it set at 0.00111000 manually, i can't trust that smart fee crap any more i see.
the standard fee is 10000 satoshi, it takes long time to get confirmed. don't pay fee less than that.
Do you really think 0.00000340 is a high fee? It should have been more around 0.0001 if you wanted a decent confirmation time.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
This transaction will take a while to confirm.
The malleability attack is definitely not the main cause.
my BTC wallet is set to send at fast ,i thought it did then i go look to see why it was taking so long and it sent it like.
Status: 0/unconfirmed, broadcast through 21 nodes
Date: 10/9/2015 01:05
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03581216 BTC
Transaction fee: -0.00000340 BTC
Net amount: -0.03581556 BTC
Transaction ID: c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a-000
and this was waiting when i went to look sorry forgot to put that in to .
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
whats up ? . NM
Guess this is why
https://bitcointalksearch.org/topic/new-transaction-malleability-attack-wave-another-stresstest-1198032
some one is playing around with the block chain again trying to make a point about some thing i guess .
sigh ..
Status: 0/unconfirmed, broadcast through 21 nodes
Date: 10/9/2015 01:05
To: miningrigrentals 1AFTf43ApNSqPvy5sES3GJfAWWaFhXQ6Nc
Debit: -0.03581216 BTC
Transaction fee: -0.00000340 BTC
Net amount: -0.03581556 BTC
Transaction ID: c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a-000
and this was waiting when i went to look sorry forgot to put that in to .
Transaction rejected by our node. Reason: Conflicting Transactions [DBBitcoinTx [txIndex=105767687, getEstimatedBTCSent()=0, isGeneratedBlockReward()=false, getTotalBTCSent()=0, getHash()=c3543e667f17f68c5ecab6081ec558b0c6e178465419d76f3b02f37b2dad315a, getVersion()=1, getSize()=339, toString()=
whats up ? . NM
Guess this is why
https://bitcointalksearch.org/topic/new-transaction-malleability-attack-wave-another-stresstest-1198032
some one is playing around with the block chain again trying to make a point about some thing i guess .
sigh ..
Jump to: