What's your secret for timing the captcha and submission?

Every time I try, it either pops up the stupid "slide" captcha... and by the time I get that sent, it then just gives back the "10000ms timeout exceeded" error, if I resubmit == "submissions beyond limit".

I used to be able to get it fairly reliably maybe 1 in every 3 tries... but I tried for like 6 times yesterday and just nothing

Sounds like this "old" wallet.dat is either:

- corrupted, so that the encrypted private keys are unable to be decrypted properly. You might be able to use the "wallet-tool" (look in same directory as bitcoin-qt and/or bitcoind) and use the salvage command. It might be able to recover some of your wallet. If it doesn't work, there likely isn't really much else that can be done with this wallet.dat unless you happen to have other backup copies you can use

or

- it is one of those fake wallet.dat's that have been altered to appear to contain hundreds of BTC, and are then sold for like 0.1 BTC claiming you could get 10's/100's of BTC for cracking the password... however the encrypted data to the keys with the 10s/100s of BTC is "fake"/junk data so it is unable to be decrypted.


Did you buy this wallet? or is it legitimately your original wallet? If you bought this wallet.dat or downloaded it from some website, please be honest, otherwise you will be wasting everyone's time trying to help with a "fake" wallet.

seems like it might be an issue with the bot communicating with Wolf.bet... the bot has attempted to make a bet with the site, but has not received any response.

It is possible that Wolf.bet have made a modification to their API or something which is causing the bot to be unable to make the bet successfully... or it's not returning the data in a way that the bot can deal with it (although, if that were the case, the bot would likely throw an error).

It's a bit puzzling really... have you contacted Wolf.bet support to see if they know why it might not be working properly?

If it shows up on block explorers, then it will be in the mempool of other nodes... so no, you won't be able to delete it. At best, if it was RBF enabled, you could try and "replace" it by using RBF.

If it is only in the mempool of your local node, then shutting down Armory and your instance of Bitcoin Core, then deleting the mempool.dat file from the Bitcoin Core data directory and then restarting Bitcoin Core and restarting Armory should wipe the mempool of your local node, effectively removing that transaction.

I'd say the chances are fairly good that if your local node accepted it, it would also have been broadcast to the wider network and is likely in other mempools... so, RBF might be your only option.

Either that... or waiting the 14 days that default nodes wait until they purge unconfirmed transactions.

The "good news" is that the transaction "399f7843fdfb4aedf56353730bacba5f9ff9aad5d462a3e245de07ac8373b8a3" was confirmed a couple of blocks ago!

as were all the child transactions all the way to 33d7037366ef418c5b97f7cbc877ac2f0c8b7a1f34db26f1e607f69ac38d9071...

All the transactions were included in block 680200. I'm assuming that the fee levels dropped to a point that the combined CPFP, kicked in and then everything got picked up by a miner wanting the 600/900/1500 sats/byte fees etc

In any case, all your transactions are now confirmed and your Electrum wallet should be showing that all the transactions have been seen/received as confirmed etc.

it will give up some of your privacy and link some addresses (and possibly some BTC value) to your Bitcointalk account (and any linked accounts)... but no one will be able to edit the transaction, steal coins or access your private keys.

It seems like one of the transactions that you sent previously did indeed make it onto the network (or at least as far as the mempool of your Bitcoin Core node) and this is why you are getting the "mempool conflict" error.

You could also try searching on a block explorer for the addresses you are sending from/to and see what unconfirmed transactions currently exist for those addresses to try and identify the previous transaction causing the conflict

Crazy that the fees made such a huge difference to the balance! That's quite a substantial amount spent!


The only reasons I could see for them no appearing in the fast sync would be some sort of "Gap Limit" limitation (ie the system was simply not generating enough "new" addresses to check and missed those 3 transactions) or it was caused by some sort of timeout in the sync process.

I'm not overly familiar with BRD as I haven't used it in years (As I recall the app wouldn't run on rooted devices and I was heavily involved in Android Custom ROM development at the time so was using rooted devices) so you would need to talk to the app Dev(s) and ask them why the fast sync misses those transactions... fastsync is some custom system they have developed to replace SPV, so it might be a bug that they can fix.

check the network status here: https://mempool.space/

you can see that anything less than 20.8 sats/vbyte is being "purged"... the network is insanely busy 200,000+ unconfirmed transactions and fees are at very very high levels... ~150-200 sats/vbyte seems to be the "normal"

That won't work... the OP's original transaction only had a fee of 7.1 sats/vbyte... so it will be below the 10 sat/byte threshold that ViaBTC have on their accelerator (nevermind the fact that the accelerator is almost impossible to use at the moment )

It's not simply because the Trezor was open source... that "helps", because it is easier for attackers to be able to find the documentation for the hardware and software used in the Trezor and identify possible attack vectors. But that doesn't mean that the Ledger doesn't have flaws... it just might be more difficult to find them as the starting point is relatively unknown (ie. security through obscurity).

Note, the Trezor still uses a "chip"... they just don't use a "Secure Element" like the Ledger does. You can see the Trezor ONE microcontroller details (including a link to the manual for the chip) here: https://wiki.trezor.io/Microcontroller

Do you usually run Bitcoin Core manually and then run Armory? Or do you have Armory configured to "Let Armory run bitcoind/Bitcoin Core in the background"?

When you run Armory, does it show "Connected" in green in the bottom right corner of the Armory screen?


Can you please copy/paste the contents of your "armorylog.txt" file from "Roaming\Armory" folder to pastebin and then post the pastebin URL here.

At this rate of 25 sats/vbyte... and given the current state of the network... it will likely take days to confirm that transaction.


You need to try it in the very first second of every hour (not just 00.00)... so every single hour you can try (00.00, 01.00, 02.00, 03.00... 23.00 24.00)... but you have to remember, there are like 200,000+ unconfirmed transactions at the moment... and ViaBTC only allow 100 slots every hour.

There will be literally thousands of people (and bots) competing for those 100 slots. No one said it would be easy... but it does work. And to be honest, it seems like it is literally your only shot of getting any of your transactions sorted, unless you want to pay ridiculous sums to ViaBTC or BTC.com to use their paid services.


A transaction sent now... only requires about 200+ sats/vbyte... the problem is that you're also having to pay for the ridiculous 148 inputs transaction AND the 64 input transaction that both only paid 25 sats/vbyte.

That's what CPFP is: "Child Pays For Parent"... you are trying to pay enough to cover ALL the unconfirmed parent transactions. And because those unconfirmed parent transactions are so large in data size... and paid such small fees... it drags down the "effective" fee rate paid by the CPFP transactions you have been trying to make

If you were using multibit "classic", then you need either need the ".wallet" file or a ".key" file (and the relevant passwords for those files) to have any chance of recovering your bitcoins.

"Classic" looks like this:



If you were using multibit "HD", then you need either the "mbhd.wallet.aes" file (and the password)... or you need your 12 word "recovery phrase".

"HD" looks like this:



Do you remember which one you were using?


Is this "password" made up of 12 words? or it just the normal sort of password you'd use, something like "password123" etc?

The reason no one talks about the antpool one is because it doesn't work any more... and it hasn't for quite some time.

While it says "transaction accelerated" (or "acceleration successful" or whatever), when you submit a transaction, it does not actually do anything. I've tried it previously, got the "accelerated" message and then watched Antpool mine around 10+ blocks while the transaction sat unconfirmed for a week.

I'm not sure how I can be any more clear than: "accelerate the '399f78' transaction"?

But this one... https://mempool.space/tx/399f7843fdfb4aedf56353730bacba5f9ff9aad5d462a3e245de07ac8373b8a3

You need to get that transaction confirmed before ANY of your transactions are going to be able to be confirmed. So, try and get that accelerated using https://www.viabtc.com/tools/txaccelerator


It isn't the one nc50lc mentioned, because the one nc50lc mentioned is a "child" of this unconfirmed transaction.

I think it is because you missed an unconfirmed transaction in the chain... the last one in your list ("22d63c") has an unconfirmed parent: 399f7843fdfb4aedf56353730bacba5f9ff9aad5d462a3e245de07ac8373b8a3

It has 64 inputs, 2 outputs and a fee rate of 25.1 sat/vbyte and it creates one of the 148 inputs used in the "22d63c" transaction


So, if you manage to accelerate the "399f78" transaction and get that one confirmed, you will then be able to accelerate the "22d63c" one.

No... it is impossible to "guess" a private key based on a public key... if that were possible, Bitcoin would be worthless... anyone could spend any coins they liked.

Javascript-based generators are not necessarily the greatest (poor RNG etc)... and some were found to be giving out "used" keys and/or pre-generated keys which caused coins to get stolen (there was a high profile, popular paperwallet site that got sold and turned "bad").

You also should not use "online" generators... Paper wallets should be securely generated offline... otherwise you're defeating the entire purpose of a paper wallet (which is to make sure that the private key never touches an online computer until you are trying to spend the contents of the wallet).

Also, the first letters of the private keys being the same is not that unusual... they should all start with a "K" or "L" (or a "5" if for some weird reason it was generating uncompressed keys)...


Personally, unless you've very familiar with Bitcoin and paper wallets... I would not recommend them. It is very easy to mess up and either lose your coins via theft... or via misplacing keys... or via not unstanding how "change" works and losing coins if only partial spending the contents of a paper wallet.

You won't be able to use ViaBTC because there is an unconfirmed parent (which also has an unconfirmed parent )... ViaBTC accelerator does not work in cases like this

My advice is to try and accelerate the grandparent... wait for that to confirm, then accelerate the parent, wait for that to confirm, then try accelerating your transaction (although, theoretically, the fee you have used for your transaction should get it included in a block without needing acceleration, but it won't be picked up until those parent transactions are confirmed )

Unconfirmed Grandparent: a3256f2c23efe100505b4f14580ee6a6025fcd9e162ecacaa37a4fc45f1b663f
Unconfirmed Parent: 4ba88675584ea4b59545f3c7ee76781dc34578b717aade2f9765761c233b165c
Your Transaction: 6d7de85010b73512b7fc2ac49ad8b549f3cfe670be75cdf0fafc96877a2442df

Thankfully, both the unconfirmed parents have an 80 sats/vbyte fees, so will be accepted by the ViaBTC accelerator. You just have to be insanely quick and hit that submit button in the first second of a new hour... remembering that you are competing with literally thousands of other people in the same situation as you... and probably also bots

Good luck!

Although I wouldn't recommend it as an ongoing solution, you could just gamble with a >10 sats/byte fee (NOTE: byte, not vbyte!) and then use the free ViaBTC.com accelerator to try and accelerate the transaction.

Downsides are:
- It's hard to ensure 10 sats/byte fee as most wallets these days use vbytes... and a 10 sats/vbyte fee may not result in a >10 sats/byte fee... in which case your transaction will be stuck and you won't be able to accelerate it as ViaBTC accelerator uses the sats/byte fee value to determine if you meet the minimum threshold One solution is just send with >=40 sats/vbyte and you should be good.

- It's still a gamble... You're basically reducing your pool of possible miners to one... ViaBTC.com

- It's incredibly difficult to get a slot. You basically have to submit your transaction within the first second of a new hour or you will miss out on the 100 hourly slots. I'm sure there are people "botting" this service!

- There is still a queue... given how insane fees are and the number of unconfirmed transactions, services like this are severely oversubscribed. They have a backlog of transactions, so it could still take ViaBTC a couple of blocks before your transaction is actually included.


Honestly, I would prefer to have a delayed payment than being paid in an altcoin. So, I would check with the payees and see if they would be happy to rollover payouts to fortnightly (or even monthly) to help reduce costs and also make things easier on them as they will end up with less UTXO's which will save them fees as well.

The address will allow you to look up the balance on a blockexplorer (blockchain.com, blockchair.com, btc.com, live.blockcypher.com etc) but you will not be able to spend your coins, nor are you able to derive the private key from just the address.

To recover your coins you need at least one of the following:

- the private key to the address in question; OR
- the .wallet file from MultiBit (and any password used to encrypt it); OR
- a .key file from MultiBit (and any password used to encrypt it)

It would appear that you have none of these

Given you have already searched the computer and have been able to locate any .wallet or .key files, then the chances of recover of your coins are very very low

What software did you use to try and search for deleted files?