The problem is the transaction malleability attack, which will only change the txid of the transaction. It essentially duplicates your transaction but with a different txid so it is regarded as a separate transaction and thus a double spend by the network. Only one of those transactions will be confirmed though. It looks like the malleated transaction was the confirmed one. Its txid is 5c30bffebfdc8733884943551596bee2fb1faea063d675a456cac3e6470f224c.
Thanks for your help. So is there a chance of me getting the coin back? or will the transaction eventually go through? The transaction you sent will never confirm because the malleated version of it has already confirmed, thus making your transaction an invalid double spend. However, your coin has already confirmed and is spendable since the malleated version did confirm. The coins in a malleated transaction will always go to where it is supposed to since the attacker cannot change the inputs or outputs without rendering the transaction invalid. |
|
|
|
So at this point the "security" question is more of an account padlock and proves to be more of a detriment than anything..?
Does this mean if someone attempted to answer my secret question is would lock my account?
Only if they get it right. |
|
|
|
|
The problem is the transaction malleability attack, which will only change the txid of the transaction. It essentially duplicates your transaction but with a different txid so it is regarded as a separate transaction and thus a double spend by the network. Only one of those transactions will be confirmed though. It looks like the malleated transaction was the confirmed one. Its txid is 5c30bffebfdc8733884943551596bee2fb1faea063d675a456cac3e6470f224c.
|
|
|
|
I have a security question on my account and I didn't appear to have any problem changing/setting it recently.
Could this possibly be just for beginner's or did I get lucky and dodge a bullet?
It isn't with setting or changing it, but rather when you attempt to recover your password with it. If you try to recover your password using the secret question, you will be locked out. You can change it, and I would advise you to remove it completely. |
|
|
|
-snip-
Times change?
Uhhhhh, i've never touched the TX fee and I send and receive transactions on a daily basis.
Did the times JUST change? As in within' the last 12 hours?
I mean wtf?
I assume you use the slider (from normal - 15 blocks to fast - next block) to adjust the fee. It estimates the fee based on other unconfirmed transactions in the network and those that made it in the last blocks. If there are many unconfirmed transactions it increases the fee to meet the matched block as good as possible without overpaying. As you can see from the picture below the number of unconfirmed TX in the last few hours was higher than usual. Thus core has increased your fee. This happens from time to time and can have different reasons. Sometimes its just more people using bitcoin, sometimes its a full blown spam attack with ~100k transactions. The spam mostly pays a low fee though, so you will hardly notice it with core.  Along with this, if you start up BItcoin core to just send a transaction as soon as it is ready, there won't have been enough time for it to gather enough data about the number of unconfirmed TXes so it will estimate the wrong fee. If you are just starting up Bitcoin Core to send a transaction, then set a fee manually because the estimate will be too low. |
|
|
|
Username: Kn1ghtdk
Thanks!
Hi, 10 banx shares sent. Can you please confirm receipt in this thread? Thanks Got it thanks. |
|
|
|
|
Username: Kn1ghtdk
Thanks!
|
|
|
|
|
Don't trust the priority thing that blockchain gives, a lot of time it is inaccurate.
Your problem is the low fee. At this time, your fee is not enough for the transaction which is 796 bytes. You will just need to wait a while for it to confirm.
|
|
|
|
www.site.onion/order.php?id=450469&stat=1For the people who have messaged me this answer, it is not correct. I tried that before I even posted here. All it does is refresh the page without performing the action. As I said in my pm, you need to do a post request, which browsers do not do through the URL bar. You will need to put the URL in an HTML form that does post if it is on a webpage. Otherwise, it probably won't work. |
|
|
|
|
Can you post the raw hex of a transaction you are trying to send? I will try to broadcast it from my node. If that works, then there must be something wrong with your bitcoin core installation.
To get the hex, send the transaction normally then right click it in the transaction list and click view details. Then click copy hex and then paste that to a post.
|
|
|
|
The dust threshold is not hard coded. It is determined by the minrelaytxfee. The dust threshold changes with what is set as the minrelaytxfee, so you can set the minrelaytxfee in your own node to the original default of 0.00001 instead of the new default of 0.00005. That will change your dust threshold.
This seemed to provide a solution to my problem. Any ideas what the default minrelaytxfee was in 0.11.0 ? When I set it to 0.00000001 the minimal amount I was able to send was 3 satoshis. How to get 546 as it was in previous version? It was 0.00001 |
|
|
|
|
The dust threshold is not hard coded. It is determined by the minrelaytxfee. The dust threshold changes with what is set as the minrelaytxfee, so you can set the minrelaytxfee in your own node to the original default of 0.00001 instead of the new default of 0.00005. That will change your dust threshold.
|
|
|
|
|
There is something wrong with your bitcoin core installation which is making it reject the transactions. Do you have any special configuration for it that your are using?
|
|
|
|
|
I think I can do this. I will send you a PM. Will you escrow the funds?
|
|
|
|
|
Wangxinxi, you should update the OP so that the number of open slots are accurate.
|
|
|
|
That is an amazing list of stuff! OP, you should also use some of the references in the bitcoin whitepaper |
|
|
|
|
Yes. It's under expert mode.
|
|
|
|
|
There are tools to crack wallets but they only work if you have some idea of what the password is.
|
|
|
|
|
How about doing split key generation? If someone is generating a vanity address for someone, they should use split key so that the generator cannot steal bitcoin from that address.
|
|
|
|
|
Show Posts
