You realise that the ViaBTC "minimum" is a fee rate of 10 sats/byte right? It isn't a minimum calculated on total fee... unless something has changed "recently" and their page hasn't been updated correctly?

Most likely demand... or preceived demand... if you have 1 user from a state wanting to use your service, you're not going to jump through all the regulatory hoops to make that happen... if you have 100,000 users from a state wanting to use your service, then you probably would

And then, to a lesser extent, possibly also where the company is actually headquartered or incorporated and the various regulatory/legal ramifications of that.

If your state is on the "restricted" list of a given exchange, I'd suggest contacting that exchange and asking them why they don't offer services. If it is because of the lack of demand, perhaps you could publicise this in crypto forums and try and get a show of support from other users in your state to show the exchange that the demand is actually there. Who knows, you might do all the other users in your state a big favour and get added to the permitted states

Of course, if your particular state is run by luddites and/or troglodytes, then you're probably S.O.L. There is an election coming up... maybe start asking candidates what their thoughts on cryptocurrency are before you vote

Yeah... there is... it's right there when you tap on the wallet name at the top of the screen after you have opened the wallet file...



You can see the "Seed" option says: "tap to show"... tapping on it gives you the warning and asks to confirm...



And then your seed is displayed back on the wallet info screen:



The "Save Backup" button gives you the option to save a copy of the wallet file to the "normal" storage of your device (ie. not /data/data)... Note that you have to enable the "Backups" option in "Settings" for this to function.

I've tested this with the "Coinbase Wallet App"... created a "new" wallet... got the following seed:

This gave me the following address in coinbase: bc1q4hjyxu8vnrqqeygz0laj4h4492je4qd6s5sdux


I then tried the seed mnemonic in both IanColeman's:






and in Electrum:





I also uninstaled/wiped the app and restore the wallet in that as well, and all 3 wallets yielded the correct addresses:








So, it is very strange that your friend has been unable to recover their wallet from the seed mnemonic. The only possibility I can think of, is that they have restored with a different seed mnemonic than the one they were using previously... however, coinbase assigns the username to the seed mnemonic somehow (I assume by attaching the username to the Master Public Key), so if you wipe the app and restore from your seed mnemonic, it will automatically reassign you the old username (ie. if you use my seed mnemonic above to restore a Coinbase wallet, it should give you the username @bct_test).

So, if the @ghfcvvhh username that it is showing when he restored the wallet in the coinbase app is identical to his previous username, then it should be the same seed mnemonic with the same addresses.

Generally "app data" on Android goes into a /data/data/"app.name.space" folder structure... so for Electrum it should be in: /data/data/org.electrum.electrum

This is the top directory and the structure will also includes a bunch of stuff like the APK and cache etc etc...

The Electrum data like "blockchain_headers" file and the "wallets" directory will be stored in: /data/data/org.electrum.electrum/files/data

NOTE: /data/data requires root privileges, so you won't be able to see any files/folders below /data/data without root.

I have checked with an old copy of 0.8.6 as I don't have 0.8.3... and it has the console available (Help -> Debug Window -> Console) and dumpprivkey works as it should:


Note: the first address is not in the wallet so "code -4" is the correct response.

If you are getting the "Private key for address XXXX is not known (code -4)" error, then you are most likely using the wrong address with the command... Click on the "receive" tab and then try the dumpprivkey command with one of the addresses shown there, to confirm that it is all working OK.

Figuring out which addresses in your wallet the bitcoins are actually on is going to be the next challenge... as they could be on change addresses, which I believe are not show on that "receive" tab. I'd probably be inclined to just use PyWallet to dump the contents of the entire wallet, extract ALL the private keys and then import them all into Electrum... and let it do the job of find which keys have coins

Sorry for your loss... but I would point out that an "international unified regulatory legal framework", kind of goes against the entire philosophy of Bitcoin.

At what point did anyone in this thread advise the OP to delete anything?

OP was advised that they could simply open the file with a text editor (or spreadsheet) and see what was in it... but any Transaction export from Bitcoin Core would not contain any private keys and would be of very little value in coin/wallet recovery (at best, you'd get a list of addresses that you could view on a block explorer to see if they held any coins)

AdolfinWolf is correct, your question as it currently stands makes very little sense...

If you already have "known privkey", then what exactly are you trying to "crack"?

As TryNinja mentioned, you require Bitcoin Core for Armory to function properly. Do you have Bitcoin Core installed, running and fully synced?

Also, can you post your Armory log files? (Copy/paste contents of Armory log files to pastebin.com then post generated pastebin link here)

Finally, there is a dedicated Armory wallet subboard here: https://bitcointalk.org/index.php?board=97.0

The irony is strong with this one...

Investigating Wasabi because they have dark market funds transferring through them is like investigating Fedex or USPS because they deliver packages sent from dark market

Hell, using their logic, Europol should probably investigate the electricity companies for providing electricity to dark market computers/servers... and the ISPs for providing them internet access while they're at it

Did you read the quote in my post?

It's NOT a .csv from Electrum... it's a .csv exported from Bitcoin Core... it's pretty much useless as far as wallet/coin recovery is concerned.


So, no... he can't import them in Electrum... because it's not a file full of private keys


No. Pywallet creates wallet.dat's in the BerkeleyDB format that Bitcoin Core uses. These files are NOT compatible with Electrum. Electrum uses an entirely different wallet file format (JSON text with optional encryption).

While not as super obvious as actually wrapping it in [ quote ] tags... at least they led with a direct link to the article that they've taken the text from. So, it's at least somewhat obvious where the text has come from.

Yeah... it's not exactly clear at what point in the process the OP "found out they needed to update to newer version of Electrum"... They "wanted to transfer everything", but it's difficult to know if they were actually trying to transfer when they discovered they needed to update (by way of scam message) or if they discovered they needed to update because Electrum just wouldn't work and they started googling things.

OP hasn't been back on since they said they solved the problem... so I'm not holding out much hope of them returning to let us know

If you have recovered "wallet.dat" files... just open them with a fully sync Bitcoin Core... You can either shutdown Bitcoin Core, switch "wallet.dat" in datadir, restart Bitcoin Core... or you can shutdown Bitcoin Core and start it from the commandline specifying which wallet file to read using the -wallet option:


So you could even try and load all of them at once, assuming you're using one of the newer "multi-wallet" capable versions.


A ".csv" file is simply text file in "comma separate values" format... You should be able to open it in any text editor to review the contents. Also, any spreadsheet app like Excel should be able to open it as well (and possibly make it slightly easier to read)

Even if you could import it back into Bitcoin Core (note: you can't), it wouldn't be much of much use in attempting to recover any funds... it's simply a list of transaction data (ie. transactionIDs and amounts etc)... it won't contain any private keys or anything like that.

Ummmm what? They only started the test and release process after the deadline was reached??!? They had nearly 3 months to sort this out... and apparently had the "fix" done but not tested on deadline day??!? 

Ledger
 |
 |
 |
 |
 v
Ball

Depends on how you want to set it up and use it...

You can either run it as a "LiveOS", but connected to the internet... in which case, it isn't a "cold storage" setup, but likely to have increased privacy due to Tails/Tor use etc...
or
You can use it purely as an offline, transaction signing setup... in which case you'd need to install "watching-only" Electrum on your normal OS, use that to create unsigned transactions, then boot up "offline" into Tails, sign the transaction, boot back into normal OS and broadcast the signed transaction

It can be done either way, you just need to figure out which option is best suited to your particular use-case. The first one is less hassle, but arguably less "secure"... the second option is more secure, but also more hassle.

Your solution basically just describes exactly what happens with transaction now, ie. you put them into a "pool" and they get grouped... in a block!

As all the transactions need to be signed, there is no way to "join" them together into one big transaction to "save space" without breaking the signatures (or more than likely adding even more overhead)... in any case, the space savings will be minimal. The major components of a transaction (in terms of bytes) are the Inputs and, to a lesser extent, the outputs... the actual "fixed" overheads are a small fraction of a transactions size. For old legacy transactions it was around 10-12 bytes per transaction regardless of total transaction size.

I don't know how many times or ways to try and explain to you... you CAN NOT recover data from an encrypted wallet.dat file unless you have the password.

The data is, after all, encrypted... so you need to recover the password first. Your options are:

btcrecover: https://github.com/gurnec/btcrecover
hashcat: https://hashcat.net/hashcat/
or
a (trusted) wallet password recovery service like: https://www.walletrecoveryservices.com/

NONE of the private key extraction scripts on this forum will be of use to you, unless you have the password