If i remember correctly... you also said you had 14 words to choose from (as opposed to just the normal 12)... Given that you're unsure of the actual words used in your seed menmonic and their order, is it also possible that you had a seed mnemonic where a word was used twice? I've seen seed mnemonics like this before... in fact, I helped a guy recover his seed mnemonic where he only had 23 words out of 24... turns out he failed to notice a duplicate word when he was writing them down! What process were you using to store/record your mnemonic that resulted in confusion of words and order?  One other thing to consider... the possibility that you used a passphrase? I know that Mycelium doesn't allow for passphrase functionality as standard... but I believe it is possible to "restore" an HD account using a passphrase with Mycelium |
|
|
|
I don't need to reinstall my OS as I believe my antivirus would detect if there's some traces left,
Given that your antivirus failed to actually inform you about the malware wallet in the first place, resulting in monetary loss, are you sure that your faith in your antivirus is correctly warranted? It has been stated multiple times that antivirus/malware software are generally only good at detecting known threats that have identified signatures. There are certain things they cannot really protect you from... like a piece of software that contains "normal" functionality (ie. software sends/receives "data" over the internet) but abuse/use this functionality in a malicious manner (ie. software sends "wallet seed/private key" information over the internet). Chances are simply deleting the wallet will be "OK", as it seems like the malware wallet, in this instance, was only used to immediately send out a transaction emptying the wallet and/or sending the users seed to the attackers... it doesn't look like it installed any additional malware... BUT if you want to be completely certain the threat is gone... reformat your PC and reinstall the OS. |
|
|
|
Just FYI, you shouldn't multipost bump your advertising thread... and you definitely shouldn't bump more than once in a 24 hour period. You should edit the previous post and add in the new info instead of creating a new post. 13. Bumps, "updates" are limited to once per 24 hours.[2]
Also, was it really necessary to create three different threads to advertise your product? |
|
|
|
... and I find option for sign message in Bitcon App with many addresses, pick one and use it for receive payment. What I did know at that time is that this address is change address, and that Ledger will not check that address - so my transaction history never show that transaction, nor did the balance increase for the amount received.
Yeah, it seemed like there were a LOT of users that used that "sign message" option to get a Bitcoin address to send out as a receive address?!? I'm still not sure why people would do that and not simply click "receive"?   In addition, it really didn't help that the addresses in that dropdown box were order "alphabetically" rather than in actual address index order (as per derivation path)... this often lead to users getting an address that was a change address (as in this case) or out past the gap limit on other wallets etc Then for the first time I see how bad is Ledger support, they had no idea how to solve this problem and they are probably in same situation today.
I've no idea regarding the size of the Ledger company... but their support seems to leave a lot to be desired... especially for a device which isn't exactly cheap. A lot of the documentation in the knowledge base was/is outdated and I've seen stories from people who have emailed and had to wait days (if not weeks) to get a response. It's possible that their popularity meant that they just got overwhelmed by a lot of new users and/or that they simply failed to invest enough resources into the support side of the business. I'm very lucky in that I've been able to solve any issues that I've had (mostly while updating the firmware with things not quite going according to plan etc)... so I have not personally had to deal with the support. but they also make something (at least in my case), with this firmware which is crushing Ledger Live on Windows 7. Do you know what Ledger support say to me? To try with Windows 10, as if I did not even know it myself...
Dropping support for older operating systems is always a contentious issue... a lot of companies seem to underestimate how many users are actually still running really old operating systems on really old hardware. Still, the reality always seems to be that the majority of people can and do upgrade... but of course you don't hear about it, because they don't complain. You only ever see complaints from the (very) vocal minority who don't/can't upgrade  I'm happy with my Nano S (aside from the current issue with the ETH app hogging the limited memory)... and I'm happy with my Trezor ONE. Honestly, at the end of the day, I'd happily recommend either. |
|
|
|
I do use the Ledger Live app and I will try to do as you suggested and look at the incoming transactions but I believe that the receiving address is the correct one because I did receive BTC that I bought from Coinbase to this exact address.
It is also possible that you sent the coins directly from Coinbase to a deposit address on <insert exchange> and your deposit to this address was then collated by the exchange with other deposits that they had received. The online tax service that you used might now be detecting the other input addresses in this collation transaction as belonging to you. I would suggest checking the addresses that are created from the master public key for your Ledger... see if you can find this address that has the 5000+ BTC. Chances are that you won't find it... as I suspect it is a flaw in tax service that you're using. You could also try and connect your Ledger to Electrum and see what addresses/transactions it is able to find... |
|
|
|
I suspect their API is broken and is returning an old rate... or it just hasn't updated for a while... Their twitter feed hasn't been updated since July 2018 and their facebook hasn't been updated since June 2018. It's quite possible the ANXPRO API just doesn't work anymore. Maybe log an issue with Mycelium devs... In other news, check the "BitcoinVenezuela.com" rate... US$4,957,820!!?!  Wooooo I'm a millionaire! |
|
|
|
This error means either that your Bitcoin Core node is not running, or that it has not been configured to accept incoming RPC connections. Armory absolutely relies on Bitcoin Core for receiving transaction data (from Bitcoin Core block files) and also for creating/sending transactions out to the network (via Bitcoin Core RPC methods)... The data flow would look something like this: [BITCOIN NETWORK] <---> Bitcoin Core <---> Armory To allow incoming RPC connections on Bitcoin Core, you need to start it up using the -server command line argument when starting bitcoind or put server=1 in the bitcoin.conf configuration file that lives in the Bitcoin Core data directory (same directory as your wallet.dat file).
Tell me how to transfer my money and I will forget about your wallet.
If your end goal is now to just get your coins out of Armory wallet, you can export your private keys for the addresses that hold coins and then import/sweep them into the wallet of your choice. I wrote a guide a while ago (with screenshots) that shows how to export private keys from Armory: https://bitcointalk.org/index.php?topic=2803610.msg30229612#msg30229612 |
|
|
|
|
Yes, I can confirm that after I updated to the 1.8.0 firmware (using beta-wallet)... and installed the 2.0.25 bridge, that I am still able to connect via the "normal" wallet.trezor.io site.
|
|
|
|
Electrum-Server... or ElectrumX? "Electrum Server" hasn't been maintained in quite a while... and as per the note on the Electrum Server GitHub, you should be using ElectrumX:
|
|
|
|
Hello, is any way to get private key from bitcoin.com Windows wallet?
If I export BTC wallet with private key to file, I get this aes.json file
Is any way to decode only private key?
Yes... you can decrypt the wallet information. See detailed explanation below. Did you use some decryption tool from the method above to extract the private keys?
Unfortunately, I don't think the old decryption tool (made for blockchain.info and/or multibit JSON formats) will work... it is a completely different format for the export file... and it is actually using a slightly different encryption mode (AES-256-CCM instead of AES-256-CBC) as well... 
However, all is not lost! I did some digging... and found that the BitGo wallet uses this same format... and that the BitGo API supports decrypting the wallet file... So, off to the BitGo GitHub I went... and discovered that the bitgo.decrypt() call is ACTUALLY just calling the decrypt method in "SJCL" (Stanford Javascript Crypto Library)! return sjcl.decrypt(params.password, params.input); That makes our job sooooooo much easier... we can just import SJCL, then pass it the export password and export data! 
So, how do we do that? Well, firstly I created a test export from bitcoin.com wallet for windows... NOTE: Password is: 123{"iv":"aE6b04cM1BcUMBesRei9+Q==","v":1,"iter":10000,"ks":128,"ts":64,"mode":"ccm","adata":"","cipher":"aes","salt":"uSmPalXNcnA=","ct":"g5S6gbETdClu1e4hlcfmYPg04W367A0OpDSL3jYKEs76B5mXVnRBRY/VmodbHyhwaNvfc/aI1cjtqc57QJ3OLmFXyU0Y+XBJejAsIqLIIRXN5Ad42k38SmBy9j9XiTeoJGlLwtbVnExGlhovT0Yb7UiELHPaAxQUsvABC3Eo+tk86AcLEYhQWRuyCcjrJR+hHOz0iMoihV6WMgp7j3QYpD4arlDLDcwx9NtXuiUEYETTOX+ByQuYJVSuLlSw23WVzTtkqb+l3YAN0+zweS/JRdQGL/ep77R+xCtJLMnWcqRjLh2XVpzhkFCLbnVhVPDpV6CCg8OD5o9lB3GncDHHACU0f1FhrqNH/7lF6X5KnRlLPCys1BUuWHzaxwb5s5Nk7QXzFNLnAUw7tjgV2oGOhb/4NgBhELESzvv2eqOe1IUvPT1HOt3npZGYwiBIQgBu2CRzYlLIJ4DUKtrNFQjqg038ugbOq2hSo/QzqyLE/mP2Z0qMhTY6DBfiw1t8tfwGcisS52ZwOl8bnGknnlWIf97dtx2e55D69zaNnykzmjrTkJ4boqz0hS4Wlpu2Wzg0rOlOzFB0+4cBCwVSZYhfPTzxUYPkcxq3JfyhmZo3XYzYFOXAWvqccIpVXiwYych69gPiOEABGxeL5fB4g/C06WiSoXSrlWTMjm1+7gEYdrAyHDdRwDtuO81LpT7PE6hfEI9l3x5L68df4dHhZhMuaoTAz+9iKUGZSNmmrL8qOwIjfdnxq9PX1yFU136/V0sMvYN9GXwALEUk5TZDMMK6/+wBlCDYzucnw7nW6kZzZi2B/F0NsCWp4tVI8g1gkLA3iXQRrrAqha3h3C3jlVPWgU5bd65YROqM/FHjpClDTJmSexnXm1zPDOEiWLU1p2s4oD4RBU5XozdSj2gjJs+fhfmo+pDLraX+i6RN2v40iLGuhtv2Oze6gxpMvEYdOJyuFNn15BZMVHYwHZMTHVJo925+JLUzzg30ryUV2hNIfUov18j0tihsErkoWmjNfg/OnvvUVVQJBwIbz01LwpYbQ12jMT5X+ORKUKgjhUAwUlFxf5A4FX1lM0SFyduEkIWnDEllppbzIXNYofMW8XTydt3gWUer+iljxUmDCX8LFZJCGQ93Xx7OsXYTP/VRLzqcHrxIieKDZ1SCPYoZsLj2pqZqX62yl4oRn028GmqsrwxPbFe9xS8VzaU1kGG0Ykj3kWQyq1/U8eODiIPto+/15QN3NcH0WFU2zJFJi2JC41nTiltn7etkLXfu+zaEv5zEEcGxK7EFVxv1m9uxtrFbAtzr/HwNqP46rQxUt9Kl30RF/qlsI30g/unsg+AFmN+zkF5PoM41U3osdbpwN+3ZrsbiMk0wxL678gEVz8/TC5AzeNRjj2nKGILdn67xaCNBGrZ0EF/t6q2E4QsJtUMBOwyvbyABebT7ZgI5kF6iTIi6NlGw7CeY0MFI9ZQOysoaufuc4XyCn3zXlq6EDtw15aVUDiHngrUYSsJKWeG6tAa2SSl/9SvBIXC/eZ6r8Cb39f5FwfIH4igPL3w7A08wAlny6Gpq3uoWQ5Q8Mtg34afWkdW/IQ2SV4rMv7e6kAbvnTvtFuZopcMfCYGpyfHN/vMktHOk/inaVMqlx1jrHJGkbVjeGTOElVQf70OdURa6s3qCMeaqJGuntVjJwRt4oD+o1pyda12FlajbZ7weZIVTd6XDIGJNUeYlJgqF3hav/tzTyB0sUnfsUX4+1E8cBBVzeW3rOM0cxCQ+T3uh0UntJLOXBBVGWK27hL0BTiMihypwMbaAkVC+se6d1EO6G1vfwLkU9UBMoIDmek454w=="}
Then, based on what I learnt from Abdussamad regarding running javascript directly in the browser... I opened up the javascript console in Chrome (press F12)... and imported the SJCL library: var script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://cdnjs.cloudflare.com/ajax/libs/sjcl/1.0.8/sjcl.min.js';
document.head.appendChild(script);
Then imported the contents of wallet.aes.json into a variable called "encryptedString": var encryptedString = '{"iv":"aE6b04cM1BcUMBesRei9+Q==","v":1,"iter":10000,"ks":128,"ts":64,"mode":"ccm","adata":"","cipher":"aes","salt":"uSmPalXNcnA=","ct":"g5S6gbETdClu1e4hlcfmYPg04W367A0OpDSL3jYKEs76B5mXVnRBRY/VmodbHyhwaNvfc/aI1cjtqc57QJ3OLmFXyU0Y+XBJejAsIqLIIRXN5Ad42k38SmBy9j9XiTeoJGlLwtbVnExGlhovT0Yb7UiELHPaAxQUsvABC3Eo+tk86AcLEYhQWRuyCcjrJR+hHOz0iMoihV6WMgp7j3QYpD4arlDLDcwx9NtXuiUEYETTOX+ByQuYJVSuLlSw23WVzTtkqb+l3YAN0+zweS/JRdQGL/ep77R+xCtJLMnWcqRjLh2XVpzhkFCLbnVhVPDpV6CCg8OD5o9lB3GncDHHACU0f1FhrqNH/7lF6X5KnRlLPCys1BUuWHzaxwb5s5Nk7QXzFNLnAUw7tjgV2oGOhb/4NgBhELESzvv2eqOe1IUvPT1HOt3npZGYwiBIQgBu2CRzYlLIJ4DUKtrNFQjqg038ugbOq2hSo/QzqyLE/mP2Z0qMhTY6DBfiw1t8tfwGcisS52ZwOl8bnGknnlWIf97dtx2e55D69zaNnykzmjrTkJ4boqz0hS4Wlpu2Wzg0rOlOzFB0+4cBCwVSZYhfPTzxUYPkcxq3JfyhmZo3XYzYFOXAWvqccIpVXiwYych69gPiOEABGxeL5fB4g/C06WiSoXSrlWTMjm1+7gEYdrAyHDdRwDtuO81LpT7PE6hfEI9l3x5L68df4dHhZhMuaoTAz+9iKUGZSNmmrL8qOwIjfdnxq9PX1yFU136/V0sMvYN9GXwALEUk5TZDMMK6/+wBlCDYzucnw7nW6kZzZi2B/F0NsCWp4tVI8g1gkLA3iXQRrrAqha3h3C3jlVPWgU5bd65YROqM/FHjpClDTJmSexnXm1zPDOEiWLU1p2s4oD4RBU5XozdSj2gjJs+fhfmo+pDLraX+i6RN2v40iLGuhtv2Oze6gxpMvEYdOJyuFNn15BZMVHYwHZMTHVJo925+JLUzzg30ryUV2hNIfUov18j0tihsErkoWmjNfg/OnvvUVVQJBwIbz01LwpYbQ12jMT5X+ORKUKgjhUAwUlFxf5A4FX1lM0SFyduEkIWnDEllppbzIXNYofMW8XTydt3gWUer+iljxUmDCX8LFZJCGQ93Xx7OsXYTP/VRLzqcHrxIieKDZ1SCPYoZsLj2pqZqX62yl4oRn028GmqsrwxPbFe9xS8VzaU1kGG0Ykj3kWQyq1/U8eODiIPto+/15QN3NcH0WFU2zJFJi2JC41nTiltn7etkLXfu+zaEv5zEEcGxK7EFVxv1m9uxtrFbAtzr/HwNqP46rQxUt9Kl30RF/qlsI30g/unsg+AFmN+zkF5PoM41U3osdbpwN+3ZrsbiMk0wxL678gEVz8/TC5AzeNRjj2nKGILdn67xaCNBGrZ0EF/t6q2E4QsJtUMBOwyvbyABebT7ZgI5kF6iTIi6NlGw7CeY0MFI9ZQOysoaufuc4XyCn3zXlq6EDtw15aVUDiHngrUYSsJKWeG6tAa2SSl/9SvBIXC/eZ6r8Cb39f5FwfIH4igPL3w7A08wAlny6Gpq3uoWQ5Q8Mtg34afWkdW/IQ2SV4rMv7e6kAbvnTvtFuZopcMfCYGpyfHN/vMktHOk/inaVMqlx1jrHJGkbVjeGTOElVQf70OdURa6s3qCMeaqJGuntVjJwRt4oD+o1pyda12FlajbZ7weZIVTd6XDIGJNUeYlJgqF3hav/tzTyB0sUnfsUX4+1E8cBBVzeW3rOM0cxCQ+T3uh0UntJLOXBBVGWK27hL0BTiMihypwMbaAkVC+se6d1EO6G1vfwLkU9UBMoIDmek454w=="}';
Then executed the .decrypt() method, passing in the export file password (password used was 123) and the "encryptedString" variable that we just created: var decryptedString = sjcl.decrypt('123', encryptedString);
decryptedString.toString();
... et voilà! "{"coin":"btc","network":"livenet","xPrivKey":"xprv9s21ZrQH143K4VZrA3w1qp44fNDNgeTNBKdt5f5MpBifWo78rbhP84w8qaTybdZsdmDFUExT2M4P4gxFDnEHCUq91AG1PjNXadWZPfvAEaf","xPubKey":"xpub6Bw8UNcpHwE6rWM6tQ1FQzvy5KX2vZeDfk3G49WFc19PSkuPKbRrbJSrJMRnJUQqopYKeQQgorpaUugvmEsnYbjgvojrdXUoJB5FU1vuCgc","requestPrivKey":"1755ea2209fa3a4e56b9f771de6db5088aaa82ae73aa3f34e9f3cb6fce30fa0a","requestPubKey":"0229d30db3ada53ee802eca52bf434ed25a4895610bf10535ebf1e88a63386e2db","copayerId":"f1d2eac1db62e2103e955d0bee7114cf0980de19a507f5c1a399378f0d8d47e2","publicKeyRing":[{"xPubKey":"xpub6Bw8UNcpHwE6rWM6tQ1FQzvy5KX2vZeDfk3G49WFc19PSkuPKbRrbJSrJMRnJUQqopYKeQQgorpaUugvmEsnYbjgvojrdXUoJB5FU1vuCgc","requestPubKey":"0229d30db3ada53ee802eca52bf434ed25a4895610bf10535ebf1e88a63386e2db"}],"walletId":"0d380f2b-f41e-4132-b614-dbd094903313","walletName":"My BTC Wallet","m":1,"n":1,"walletPrivKey":"f1a26f143543c9ef006c7b2a42d1cf576c25e8ce06dce0f496c4bd37e661b4a2","personalEncryptingKey":"XlgcaJ18PcxxSw9Ik2/YmQ==","sharedEncryptingKey":"JVkW3jRTA+b4Bja5srQv7Q==","copayerName":"me","mnemonic":"chronic indoor basket wrist urban base average peasant ensure park educate tower","entropySource":"00dfda1fc9a7fcda66898bb882de3ad6295c04c4e037b5efb070df3a60f1825b","mnemonicHasPassphrase":false,"derivationStrategy":"BIP44","account":0,"compliantDerivation":true,"addressType":"P2PKH","addressBook":[]}"
You can see it in action here:  As you can see, the decrypted file contains the xprv, xpub and also the 12 word mnemonic for the wallet... It's BIP39/BIP44 compatible, so you can use the mnemonic on Ian Coleman's Mnemonic Code Converter to get all your addresses/keys... or even import it into a BIP39-compatible wallet. Note, this should also work in Firefox (press CTRL+SHIFT+K to open Javascript console)... |
|
|
|
Another box popped up
- Fatal error detected
Error loading Python DLL 'C:\Program Files(x86)\Electrum\python36.dll'. LoadLibrary: The specified module could not be found
I remember this happening last time when I updated from 2.7 to 3.someting and someone advised me to go back to 2.9.3 which has worked for me for the past 8 or so months.
That is trying to run on Windows 7 right? Nevermind, sorted that part out!
I assume you just installed the Universal C Runtime stuff to fix that? Did you manage to get 3.3.4 running then? |
|
|
|
Edit: Actually you can use your browser's developer tools to decrypt the priv key.
Took some messing around to make this work on Chrome (Press F12 to get console)... It doesn't seem to have the CryptoJS stuff auto imported? I had to first of all copy/paste this code snippet into the console to get access to the CryptoJS library... the source code for which is no longer available on code.google.com So, I'm using some random link I found while googling for it var script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://cdnjs.cloudflare.com/ajax/libs/crypto-js/3.1.2/rollups/aes.js';
document.head.appendChild(script);
Then, I could copy/paste the following code into the console and it would pop up the alert showing the private key. var mencrypted = "enter encrypted priv key here";
var mpassword = "enter password here";
var decrypted = CryptoJS.AES.decrypt(mencrypted, mpassword);
alert(decrypted.toString(CryptoJS.enc.Utf8));
If you try and copy/paste the whole lot in one go... it'll complain that CryptoJS doesn't exist: Uncaught ReferenceError: CryptoJS is not defined at <anonymous>:8:17 But, if you just copy/paste it again, it'll work... What is interesting, is that I attempted to use the OPs example: Here is an example of an encrypted wif key and it's corresponding wif key and password that i have generated here (https://coinb.in/#newAddress) for testing purpose
WIF key : "KyYEjVKDcbUrgfrpdpzaZBm1szWbzTmrBvxsQzDWgCAAZnd6uw8S"
AES-256 Encrypted WIF key : "U2FsdGVkX187FiUTQ0lMNeO5AkYQS9xU874h0g4AWch3ZfLuKEiUndejRQ0uRGw03sY5tOlTiVyiLf4oax+6IGF7hJUAjOMEomCGOxd8jvg="
Password : "123"
And I just get a blank alert... but when I use a randomly generated one from coinb.in... it works! WIF Key : "L3pLNp7KgZAT2LSuue4RPkum6XGCgeZFE2Dk37xPvxnN8TAEtQX1"
AES-256 Encrypted WIF key : "U2FsdGVkX1/fN3CAnYeGfVPhdq8G/MM+u8U4K7nR1xm3iHwXQwOojQmzyF3Zp/e4N5l8T+iNFSw8OGxC5P67+Jil8HR/Tb64QJfX0qUDxSg="
Password : "123"
I'm guessing the OPs example is broken? bad AES encrypted key or bad password?
EDIT: I tried as your suggestion it doesn't work in firefox it always shows "ReferenceError: CryptoJS is not defined"
I was getting the same... I think maybe Abdussamad already had the CryptoJS stuff loaded (browser extension maybe?)... try running my little code snippet to load the aes.js script and see if that helps! |
|
|
|
You'd need to follow the process for converting those AEZ words back into a seed... then use that seed to generate the private keys that match the addresses that your coins are on (assuming that you can somehow close the lightning channels to "return" the remaining coins to the wallet). I found this encoder/decoder: https://gugger.guru/blockchain-demo/#!/aezeed was linked by the devs here: https://github.com/bitcoin-s/bitcoin-s-core/issues/342 but as they note: So, use at your own risk etc. Also, theoretically, it SHOULD work with LND... as they seem to be using the same process. |
|
|
|
Ahhhh OK... you have 2FA... yeah, that IS a problem... it doesn't store the full seed (as that recovers 2 of the 3 private keys in a 2FA wallet). You should still be able to upgrade OK without the seed. But I highly recommend that you move the coins to a new wallet where you DO have access to the seed ASAP. So, I would recommend: 1. Make a backup or two of your wallet file (refer here for location: http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located) 2. Update to latest version from here: https://electrum.org/#download3. Sync your wallet 4. Create a new wallet (standard or 2FA is your choice) with a seed... WRITE THE SEED DOWN (and keep it safe! ) 5. Move all your coins to new wallet |
|
|
|
If you know your wallet password, you should be able to extract the seed from the wallet by simply using the "Wallet -> Seed" menu item. If your wallet is password protected, it'll prompt for the password, then show you the seed... if it isn't password protected, it'll just show you the seed. Just wondering if there’s anything I can do to:
1. Synchronize on this wallet
You'll definitely need to upgrade to be able to sync. However, you *should* be able to upgrade without knowing the seed... simply make a backup of your wallet file and then install the latest version. It shouldn't overwrite the file, and the should just open your old wallet file for you. 2. Check to see if the transaction went through
Check the address on a block explorer (like blockchain.com or blockcypher) 3. Recover BTC if I’m unable synchronize/update without the seed
As mentioned, upgrading shouldn't wipe your wallet (make a backup anyway)... however, if all else fails you should be able to extract your private keys (as long as you know the wallet password)... and you can then import/sweep them into a different wallet. In any case, I'd recommend that if, for whatever reason, you are unable to recover your seed, that you move those coins to a new Electrum wallet ASAP. That seed is your guaranteed recovery tool! Without it, you're asking for a world of hurt if your wallet file becomes inaccessible for whatever reason (harddrive failure, accidental deletion, file corruption etc) |
|
|
|
|
Also... ensure that you do this when Bitcoin Core is NOT running!!
If you try and restore the file when it is running, there is a high chance you will corrupt the file.
|
|
|
|
I also have a question,
My question still unanswered. As majority of voters have voted yes (including reputed users) can this be translated into a factor to consider before joining a paid signature campaign?. If the community believe making spreadsheet public is very important should users be discourage from joining campaigns that don't publicize their spreadsheets.
I would go ahead and say Why? If users which to join campaigns that don't have public spreadsheets... that is their choice. Just like I believe it is the choice of the campaign manager (and/or campaign owner) to decide whether or not the spreadsheet should be public (or even exist... who knows, maybe they do it all on napkins, post-its and old receipts ) I have a question (or three) for you... There are a lot of "it helps stop campaign abuse" claims being made here, but why should the general public care? Should that not be the campaign manager's responsibility to "police" their campaign? Isn't that what they're being paid to do? I still don't understand why it is that people who have no vested interest in these campaigns get so worked up about so-called campaign abusers... it's akin to wandering around a random store trying to catch shoplifters like some sort of voluntary store security!!?! |
|
|
|
Firstly, DON'T use bitcoinarmory.com... it is very old and outdated! https://btcarmory.com/ is the website for current versions of Armory. You haven't explicitly stated which versions of Bitcoin Core and Armory you are using (and unfortunately you've chopped out the parts of the log file which show them)... so, if you aren't already, make sure you are using v0.17.1 of Bitcoin Core... and 0.96.5 of Armory. As for showing the hidden "AppData" directory... follow the instructions here for your version of Windows: https://support.microsoft.com/en-us/help/14201/windows-show-hidden-filesAfter doing this, you should be able to see AppData (and other hidden files/directories). Your logs indicate that Armory is unable to find your Bitcoin Core blocks folder (I'm assuming you have configured Bitcoin Core to store blocks in a non-standard location). It appears that you already know the best way to get Armory to find the right path is using the .conf file in the AppData directory... You can also use commandline arguments to get Armory to find the correct path (you can edit the Armory shortcut to do this on Windows). There is more specific info here: https://btcarmory.com/docs/pathing |
|
|
|
... Your wallet depends on LND which in turn creates the seeds for you (based on my understanding) and the seed scheme is not BIP39 but instead a modified version of it which they call AEZSeed (AEZ = easy authenticated-encryption method made easy) differences include addition of a version byte, a timestamp and using scrypt instead of PBKDF2 and using AEZ encryption! [2] This is why you are getting "BIP 39 (checksum:failed)" exception in Electrum. ... [2] https://github.com/lightningnetwork/lnd/blob/d541ebe3765bc0db9fe568332f7aabd3a2014612/aezeed/README.mdThanks very much for this... I had gone digging through the code looking for the mnemonic generation sections, but had been unable to find anything... apparently, I didn't dig quite as far as you! So, while they are still using the standard BIP39 wordlist, they have a custom "seed <--> mnemonic" process which implements a couple of extra features... and results in "non-BIP39 compatible" seed mnemonics. |
|
|
|
|
Show Posts
