Ok it seems to be gotten away. But out of interest we could still try what happens with Bitundo. Anyone would like to here explain a quick way how we sign and check a transaction with Windows Electrum?
I wouldn't like to send Bitundo a signed transaction that can be anything.
Topic: URGENT rivalling an unconfirmed unauthorized transfer of 52 BTC (Read 922 times)
How come can blockchain.info be outdated right at the same time? Does that happen often?
blockchain.info seems to have some difficulties in their database lately. This isn't the first time I've noticed this with them. It seems to happen most often when there is an orphaned block. They don't seem to switch over to the new longest chain properly in their database.
They've probably got a bug in their code that loads their database from the blockchain. It tends to cause a lot of confusion when it happens, since people who use their website and wallet start seeing confirmed transactions become unconfirmed, and unconfirmed transactions appear "stuck".
Hopefully they'll get the problem sorted out in the near future.
How come can blockchain.info be outdated right at the same time? Does that happen often?
Bitundo says it is still doable.
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
I suspect that bitundo is mistaken.
An orphan one block deep might still be possible to overcome. An orphan 2 blocks deep would be very difficult to overcome.
This transaction is now 14 blocks deep. Unless bitundo has access to more than 50% of the total global hash power, the odds that they can undo this transaction are less than 0.0001%.
As has been pointed out it won't hurt to try, but don't get your hopes up.
Bitundo says it is still doable.
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
Just give bitundo a try. I really don't think it will be undone.
But if it fails you don't pay anything so you have nothing yo lose.
You may be lucky.
Bitundo says it is still doable.
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
There seems to be an orphan block affecting the issue. Quite a coincidence.
https://blockchain.info/block-height/311023
What does this do to the case?
Edit: Nevermind, I see that blockchain.info has an out of date database. Looking at blockr.io I see that the transaction actually already has 12 confirmations. It is too late to do anything about it.
Thank you for the info. We were about to use this; http://www.bitundo.com/ but to no avail now.
A little too late.
But nice find.
Edit: Nevermind, I see that blockchain.info has an out of date database. Looking at blockr.io I see that the transaction actually already has 12 confirmations. It is too late to do anything about it.
Thank you for the info. We were about to use this; http://www.bitundo.com/ but to no avail now.
Is there a way to cancel or compete with an unconfirmed transaction to make the original one invalid?
https://blockchain.info/tx/22284fac41ed4e78cb531f020d8f21dd0285694809f1d048a02aae4915161ccd
That's a hacker transferring out 52 BTC fresh from DGEX exchange's payout account.
We are not expecting to get it back but it would be nice to know. Thank you for any advice.
https://blockchain.info/tx/22284fac41ed4e78cb531f020d8f21dd0285694809f1d048a02aae4915161ccd
That's a hacker transferring out 52 BTC fresh from DGEX exchange's payout account.
We are not expecting to get it back but it would be nice to know. Thank you for any advice.
Your only chance would be to contact the operators of the largest mining pools and convince them that the transaction should not be confirmed. Then submit directly to them an alternative transaction that spends the same inputs, but assigns the output to an address that you control, and convince them to confirm your replacement transaction instead.
This will be a very tough sell. Good luck.
Edit: Nevermind, I see that blockchain.info has an out of date database. Looking at blockr.io I see that the transaction actually already has 12 confirmations. It is too late to do anything about it.
Try the steps and approach used by Klee in this post
https://bitcointalk.org/index.php?topic=686275.new#new
he faced a similar ordeal lately.
But, yes, BTC transactions once made, can only be acquired back, if the person who received those BTC transfers it back.
https://bitcointalk.org/index.php?topic=686275.new#new
he faced a similar ordeal lately.
But, yes, BTC transactions once made, can only be acquired back, if the person who received those BTC transfers it back.
Is there a way to cancel or compete with an unconfirmed transaction to make the original one invalid?
https://blockchain.info/tx/22284fac41ed4e78cb531f020d8f21dd0285694809f1d048a02aae4915161ccd
That's a hacker transferring out 52 BTC fresh from DGEX exchange's payout account.
We are not expecting to get it back but it would be nice to know. Thank you for any advice.
https://blockchain.info/tx/22284fac41ed4e78cb531f020d8f21dd0285694809f1d048a02aae4915161ccd
That's a hacker transferring out 52 BTC fresh from DGEX exchange's payout account.
We are not expecting to get it back but it would be nice to know. Thank you for any advice.
Jump to: