Mycelium seems to be suffering from sync issues more and more frequently... additionally: I should note that in the time I waited for my funds to magically appear I just had the app on my Iphone, did not delete & reinstall. we both used the Iphone app.
The iPhone version was effectively "abandoned" for quite a while and lags a long way behind the Android version in terms of features and usability... While it is now receiving updates (most recent was Jan 9 2021), you might want to consider trying a different wallet on iOS and see if you can import your Mycelium 12 word seed backup into that. |
|
|
|
As per your other thread... all the .wallet files I have created with Armory begin with the bytes: BA 57 41 4C 4C 45 54 00 60 FE CD 00
 |
|
|
|
Armory wallet files will most definitely be encrypted, you cannot actually create Armory wallet files without a password... Also note that PyWallet will not be able to help you with Armory wallet files. As for using hexfiend... you'd be better off creating a raw image of the disk and then attempting to use file recovery software to try and locate the wallet files rather than relying on finding raw bytes. It seems that all the Armory .wallet files that I have created start with: BA 57 41 4C 4C 45 54 00 60 FE CD 00
 |
|
|
|
Aside from the "DB Error" issue with your blocks file not being "valid".... this is also of concern: (ERROR) ArmoryQt.py:2180 - ***WARNING: Wallet could not be loaded: C:\Users\enduser\AppData\Roaming\Armory\armory_2ot51ac3y_.wallet (skipping)
Traceback (most recent call last):
File "ArmoryQt.py", line 2140, in loadWalletsAndSettings
File "armoryengine\Timer.pyc", line 99, in inner
File "armoryengine\PyBtcWallet.pyc", line 2156, in readWalletFile
File "armoryengine\PyBtcWallet.pyc", line 2457, in doWalletFileConsistencyCheck
File "shutil.pyc", line 133, in copy
File "shutil.pyc", line 97, in copyfile
IOError: [Errno 13] Permission denied: u'C:\\Users\\enduser\\AppData\\Roaming\\Armory\\armory_2ot51ac3y_.wallet'
Seems like you have some Windows permissions issues... Armory is not able to read the wallet file... are you able to view the properties of that file and see who the "owner" is? Are you running Armory as "administrator"?  |
|
|
|
right lets start from beginning cos i no idea what i need to do.
i have my password and my 12 random words but when i open multibit hd it wont synchronise.
When you say it won't synchronise... how long did you wait? I just started up MultiBit HD and it was slow (it only found 1 peer to start with, but eventually increased to 11), but it synchronised an old wallet of mine from years ago... note that it may appear to be doing nothing for extended periods of time... and I actually had to shutdown and restart MultibitHD a couple of times when the sync "stalled". From your screenshot, your version has found 8 peers, so it should be possible to get synced. As far as finding out what your addresses are... it's likely to be a bit difficult without using other software, as MultiBitHD doesn't really provide any useful way of showing you all your receive addresses and, somewhat more importantly, your change addresses... aside from looking at the transaction history  Honestly, the easiest and fastest solution would be to simply recover your wallet using Electrum and your 12 word seed backup... it'll take a few minutes at most, and you'll be able to see your entire wallet history, all the addresses and the remaining balance etc. Plus you'll have the added benefit of being able to spend those coins without too many issues... MultibitHD doesn't allow for very good fee management and may result in a "stuck" transaction... so you're probably going to need to recover your wallet using Electrum (or some other solution) at some point anyway, so you may as well do it sooner rather than later 
How difficult is it to set up an SPV server for multibit? I could try making one for OP, but the problem is going to be the scarcity of documentation and possibly getting it synced with peers.
From what I gathered, it looks like I just need a full node (which I already have)?
There aren't specific SPV servers for MultibitHD... it uses BitcoinJ and connects directly to full nodes...  |
|
|
|
There is this "other" method of brute force, and it's commonly known as $5 wrench attack. Does not matter how many words you use if you will give it up to save your life or someone else's.
Aside from technical computer security and taking all proper precautions as well as OPSEC (don't go telling the world you have bitcoins or else someone will hunt you), do you also have physical security? Do you lock your doors at night and with what? Can someone kick the front door in? (use 3 inch or longer screws on your door hinges for example.)
If you have 12 or 24 words, don't worry about that part, worry about if someone can break a window and rob you or something.
Please don't go down this rabbithole... we'll be back to ridiculous scenario's about co-ordinated attacks on bank vaults and safety deposit boxes and whether we should split our seed across 5 banks vaults or 6... and what happens if a concrete truck drives into one bank and destroys one part of the seed while there is simultaneously a fire at 2 of the others and a flood at the 4th...  |
|
|
|
Also i dont save 600 word seed i only save few key pairs. Thats all i need
So you are effectively reducing your security to "only" the security of a standard bitcoin private key... You've really gone to an awful lot of trouble to simply generate a couple of private keys It's like taking a taxi around the block to get to the house next door... you could have just walked  |
|
|
|
I read the suggestions, but - as I was asking - I am looking for a script that runs in a browser: I want to keep the codebase as small as possible. Bigger codebase means more complexity and means less security. And how big do you think the codebase for a browser is? By using a browser you are exposing yourself to a huge attack surface that you have even less chance of being able to personally validate... unless you're going to audit the codebase for the browser and ensure that it isn't doing anything stupid (like NotATether mentioned above)... A simple bash script or 20-30 line Python script will be objectively a lot more secure than trusting browser code and javascript. |
|
|
|
If the first line starts with "U2F" and looks something like this: U2FsdGVkX18LSYm98B5HRgLWHgx35xMcsSpjjtdC9XG6iEYh9OC+vfyQA1fNmjEKs64cm/bntH7g
/AMeb5NNSEe9hzYAgp/DRvOR+GX9E95pGcl4Gb2AHGMyUfAww7uV
Then it is encrypted and you would need to know what the passphrase was that encrypted this file to be able to recover the key(s) that are stored in it. |
|
|
|
Well i found bitcoin files only under /usr/local/bin, i must be lucky ^^
Looking at the command it makes sense that you only found items in /usr/local/bin... As that command takes everything that was in bitcoin-0.21.0/bin/ and effectively "copied" them to /usr/local/bin... so to undo that, you'd just need a list of the files that were in bitcoin-0.21.0/bin/ and then manually delete them from /usr/local/bin |
|
|
|
what would be the search string for an armory wallet?
In what sense? To try and find the raw "bytes" on a harddrive? Or when using a file recovery application and filtering on file names? Not sure what the "bytes" would be... I don't even know if they have a unique byte sequence that you could search for. But the filenames are of the form: armory_xxxxxxxx_.wallet where xxxxxxxx are 8 or 9 characters that could be UPPER/lower or numbers... ie. 24thyQTeb or Xta7DzBg etc I assume you don't have your Armory "root key" backup if you're trying to recover wallet files? |
|
|
|
|
Given the age, it won't be an HD wallet... so it'll be comprised of "random" private keys/addresses and likely to only have a keypool size of 100.
If you have the passphrase, then running dumpwallet will output the entire contents of the wallet... otherwise, simply running PyWallet using the --dumpwallet option but without giving it a passphrase will dump out the addresses only.
|
|
|
|
Mine works well on a just created testnet wallet.
As far as I can tell, it works if the wallet already has the private key in it (ie. you create an imported wallet using the privkey)... but if you are attempting to sign a transaction using a wallet that doesn't contain the key, it won't work... even if you pass the private key. There is something weird happening in the sign_transaction() code that seems to make it ignore the privkey @Ali2k, you might need to create an issue on the Electrum Github: https://github.com/spesmilo/electrum/issues |
|
|
|
|
Yes... the addresses should probably still be visible when the wallet is locked... the only data that is actually encrypted in a wallet.dat is the private keys. Pretty much everything else is unencrypted, hence why you can open Bitcoin Core and load a password protected wallet file and see the contents without knowing what the passphrase is.
The only time you need the passphrase is when you need to execute actions that require private keys (signing message, signing transaction, dumping wallet or private keys etc)
|
|
|
|
When you put 2 of the 3 items... it should autofill the 3rd... So, if you put Quantity+Price... it should work out the total amount that you would need to have in your account to be able to buy that. If you put Price+Total... it should work out the quantity of BTC that you're going to receive. And if for some weird reason you put Quantity and Total, it will tell you the price |
|
|
|
How do you mean here, do I just copy the wallet.dat folder into the same directory?
Where is your "old" wallet.dat? You can either shutdown Bitcoin Core, then copy the "old" wallet.dat to the datadir shown in Bitcoin Core (Menu: Window -> Information) and replace the "new" wallet.dat. Then restart Bitcoin Core... or You can shutdown Bitcoin Core, then copy the "old" wallet.dat into the datadir and rename it something like "old_wallet.dat"... then restart Bitcoin Core and use the "File -> Open wallet..." menu and you should see "old_wallet.dat" shown in the menu. When you select that, you'll get a dialog pop up and it should automatically rescan the wallet for you. As always... only work with copies of your original wallet.dat file... |
|
|
|
Bitcoin Core doesn't really need to be running over Tor for your Electrum to connect to EPS via Tor. The issue you seem to have is Electrum connecting to your EPS via Tor, which seems like something isn't quite configured correctly with EPS and Tor... That's why I suggested trying one step at a time: 1. Get Electrum connecting and syncing to any Tor server to confirm your Electrum setup is OK 2. Get Electrum connecting and syncing to your Tor server 3. (optional) Get Bitcoin Core working on Tor I've managed to setup electrs + tor hidden service within Ubuntu (running under Windows Subsystem for Linux aka WSL)... and then I have managed to get Electrum on the Windows machine to connect to that hidden service (using the Tor Browser bundle proxy)... so it is indeed possible. |
|
|
|
I have the tor browser bundle but I have not done anything else or edited the torrc file (I have on the pi, but not on the pc though).
If you're using the browser bundle... I think you need to have the browser open and running (and a Tor circuit established)... and then use port 9150 in Electrum. Otherwise, you would need to install and configure the tor service on your Electrum PC to create a "permanent" Tor proxy that Electrum can connect to. If you're using Debian/Ubuntu maybe this will help: https://2019.www.torproject.org/docs/debian.html.enAlso, you might want to create a dummy wallet... and try connecting it to a "public" Electrum onion server first, just to make sure that your Electrum is connecting successfully via your local Tor Proxy first... Once, you have successfully got Electrum connecting/syncing via Tor, then try getting it to connect to your onion server. For instance... I am starting Tor Browser, let it build the circuit etc... then starting Electrum with: electrum --oneserver -s nuzcmy763qatxi7wx46mz3feeqqimyur3qhlvrnxl5auku4xd2ov6lad.onion:50002:s -p 127.0.0.1:9150
And (after a short delay after startup) I see the syncing symbols and then I get the "blue dot" to indicate that the Proxy connection is working:    |
|
|
|
Ok, I did like this, the transaction was launched (generated a txid) and the btcs disappeared from the wallet for a while.
But it didn't concretize and the btcs returned to my wallet.
Sounds like you used a fee that was too low and the transaction was not confirmed... it was then dropped by the network (likely purged because of a low fee) and you were able to see the BTC in your wallet again. Through the wallet feature I couldn't send the transaction (same *You have a confirmed balance of 0 BTC unable to send...* message appearing).
So I did it through +New > transaction tab and signed it in *Sign tab* later, and ended verifying it in *Verify tab*.
Maybe I should have done something else?
After signing and verifying... did you actually "Broadcast" the transaction? If it has not been broadcast, then the network has no knowledge of this transaction |
|
|
|
Oh right... I was thinking you were using SSH and then executing the "./electrum" command on the Pi terminal... but you're creating an SSH tunnel to the Pi, then using that to connect your local Electrum to the EPS server on the Pi. got it! Ok, so to clarify... the --server command is telling Electrum which server to connect to... so that should be something like "my.onion:50001:t"... the -p command is telling Electrum what the "local" Tor proxy is that it needs to connect to, to be able to reach the Tor network. So, do you actually have Tor setup on your Electrum PC? If so, how did you install it? Browser Bundle or a general Tor package install? |
|
|
|
|
Show Posts
