What version of Armory are you running and where did you download it from?

The latest version is 0.96.5 and is available here: https://btcarmory.com/

NOTE: versions on bitcoinarmory.com is OLD and OUTDATED... DO NOT USE!


Also, do you have the latest Bitcoin Core 0.19.0.1 installed and fully synced? Armory relies on Bitcoin Core. You will not be able to "see" the coins in your Armory wallet unless you have a fully synced Bitcoin Core as well.

You'd need to check the log files for that service to see why it is shutting down.

It's quite possible that BitcoinSV is being retarded and is trying to usurp the Bitcoin Core datadir/blocks by default. So, it might pay to use the "-datadir" argument with that particular service to force it to use a separate directory.

Just as a "headsup" to the other "Train Wreck Watchers"™... The bot is back up and running. This update was posted on Telegram:

Will be interesting to see what happens with the next trades... I'm guessing another week or so of "non-trading" while BTC hovers around the $7400 mark... but then, I'm shit at predicting markets and stuff, so who knows we could be $10K by the end of the week!

It depends on the website you downloaded it from. There is no "standard" format for what a wallet will put in their wallet file... it might have your backup phrase... or it might have the xprv or private keys.

Where exactly did you download it from and what wallet was it for?


Blockchain.com (aka Blockchain.info) wallets use the .json file format for backups. (it'll be downloaded as wallet.aes.json)... They even have a decryption tool available: https://github.com/blockchain/my-wallet-backup-decryption-tool
and a wallet import feature available here: https://login.blockchain.com/wallet/import-wallet

Of course they do... but it is a proprietary, closed-source system. So it isn't at all strange that no one knows what they're doing or how they're doing it outside of the coinbase development team

Actually, that is a pretty valid point... and not something I had actually considered until now.

The halvening is likely to have a massive impact on Bitcoin (and by proxy, all cryptocurrency)... Perhaps it would be wise to commence after it occurs so there is less chance of a massive "event" in the middle of the experiment that could wildly skew the values?

Maybe try and use "bitcoin-cli stop" instead of just CTRL-C to shutdown bitcoind in the future?

It may or may not improve the situation... but it definitely won't make it worse as it will shutdown bitcoind in the most graceful manner possible and hopefully avoid any data corruption.

Also, to clarify, "Burst posting" isn't so much about the amount of time between posts... it is clumping all your posts into one block of time and is generally a signature campaign specific metric. Mods don't care if you come online once a week, make 30 posts in 1 hour time period and then disappear again (assuming you're not posting off-topic replies or spam etc).

However, to most of the campaign managers, this would be classified as "burst posting"... you're basically just coming online to make your min/max quota of posts for the week in one short "burst". The burst posting "rule" is designed to encourage users to participate in the forum in a normal/organic way on a daily or semi-regular basis... rather than attempting to simply meet minimum requirements (and/or maximise returns) by throwing up a lot of posts all at once before the weekly cut-off.

I still stand by my original assertion that anyone who is concerned about the minimum time between posts "to avoid getting banned, red trust or brust posting ?" is not here to contribute to the forum in a meaningful way.

Unfortunately, that is not very descriptive of what your issue actually is. Can you be more specific?

Is the Ledger device communicating with Electrum OK? Do you see a "green Ledger icon":



or a "red Ledger icon"?



Where/when exactly does it fail? When you're trying to create the transaction? When you're trying to "sign" the transaction? or when you're trying to broadcast the transaction?

What version of Electrum are you using?
What Ledger device are you using?
Are you getting any error messages?

They're lying to you. They cannot retrieve the wallet passphrase from a wallet.dat using a hex editor.

The only solution is to attempt to bruteforce it. You can use something like btcrecover or hashcat or "John The Ripper"... but they are not exactly "newbie" friendly. They require a bit of technical skill and are all commandline programs.

Another option is a "trusted" password cracking service like Wallet Recovery Services... The owner (Dave) has been on these forums for a while and has a number of successful attempts at password recovery for numerous users. They also have a thread here on BitcoinTalk: https://bitcointalk.org/index.php?topic=240779.0

No. Wallet passphrase's are not stored in the wallet.dat. They're used to encrypt information within the wallet.dat file.

If someone claimed this, they either have no idea what they're talking about or they're probably hoping to get someone who doesn't know any better to "prepay" a recovery fee.


EDIT: Just realised this is in BitcoinJ board... So are you referring to a "Bitcoin Core" wallet.dat? or were you asking about a wallet file for a different wallet?

Most likely it will be "faster"... but bear in mind that is a relative term. If the internal drive is still a HDD and not an SSD, then the gains aren't likely to be very big.

Also, your CPU+RAM is relatively weak... That might be causing RAM Paging, which will be placing further strain on your HDD and memory controllers etc.

I guess the best answer is "sort of"... As near as I can figure, the bot bases the "size" of the trades on your balance etc.

So, for the most part, the "sizes" of the trades are "relative" to what your individual balance was/is... and of course, some users have biggers/smaller overall percentage losses because they started up at different times. I hit a nice little 15% increase right at the start of my trading, so then when the big 30% loss came, it only put me at about 20% down from my initial position. Someone who started a day or 2 after me, would not have had that initial boost, so would be suffering more. Likewise, someone who had started a month before more, would be in a better position.

As for the timings.... They seem to be "the same", making allowances for timezones and latency... at least, from what I've seen of publicly posted trades. Like the differences in timestamps between my trades and guigui371's trades for the last batch seem to be measured in seconds (generally 1 or 2)... Note that I am assuming the 11hr difference on the timestamps is simply the result of different timezone settings.

There are some subtle differences, like a trade in guigui371's that I don't have... where an order got amended at "6:46:11 PM"... not sure why mine did not? Possibly the VPS I was on didn't get the same trading info so didn't move?

Unfortunately, I don't see this being the end result of your advice.

Based on the OPs other thread/posts:
https://bitcointalk.org/index.php?topic=5206632.0
https://bitcointalk.org/index.php?topic=5206632.msg53502533#msg53502533



It would appear that they got removed from the "cryptotalk/yobit" campaign for offering spamming services... no doubt this is the reason behind asking such a question.

This appears to be your problem right here... You're NOT running 0.96.5! You're actually running an old, outdated version of Armory.  Where did you download it from?

You need to download and install the one from here: https://btcarmory.com/0.96.5-release/

Once you have 0.96.5 installed and running, it will hopefully work ok.

try:

You'll probably find that it's picking up the bitcoind from /usr/local/bin instead of running the "bitcoind" in the local directory. If you want to override the "path"... use ./ notation to indicate you wish to run from the local dir (or provide the full path to the executable)...

For instance, from your "~/Downloads/bitcoin-sv-1.0.0.beta/src" directory

or, from anywhere

Assuming there is actually a "bitcoind" in your "~/Downloads/bitcoin-sv-1.0.0.beta/src/" directory

Going to be interesting to see what squad Klopp puts out for the FA Cup tie with Everton... I know he's probably more concerned about PL and UCL... but, it's Everton! If it had been any other team he'd probably field the youngsters again like they did with Villa.

Getting back to the PL chit chat... seems Harry Kane could be out for a lengthy spell... If that is indeed true, that's going to make things harder for Spurs against Liverpool next week. Although, what probably concerns me more is that Son will be back... he's going to be champing at the bit after his red card suspension and will be hard to contain And then of course... you have Jose's "tactics" to deal with... I expect a fair bit of bus parking to be involved

Most likely Bitcoin Core is not configured to allow incoming connections from Armory, so Armory thinks Bitcoin Core is "offline". Can you please post the settings from the "Settings -> Options -> Network" screen in Bitcoin Core and also the settings you have in your "bitcoin.conf" file.

Also, can you please post the contents of your "armory.log"? It'll be in your "%AppData%\Armory" folder... (which looking at your screenshot is going to be C:\Users\Udeshs\AppData\Roaming\Armory). There might be an error in there.

Open the armory.log file with a text editor... then copy/paste the contents to: www.pastebin.com and click "Create new paste". Then post the unique URL generated by pastebin.

Open "Ledger Live"... connect your Ledger Nano S... unlock it with the PIN... DO NOT select anything on the Nano S. Then in Ledger Live, click on "Manager"... and when prompted on the Nano S, click to "Allow Manager".

The Manager should start in Ledger Live and should show you the list of coin apps available... find the "Bitcoin" one and click on the Trashcan. That should uninstall the Bitcoin app from your device. You should then be able to update the firmware.

---

To be honest, you should be able to update the firmware without needing to remove the app. It's only recommended as the firmware updates can be quite large and with the limited memory on the device, if you have 5 or 6 coin apps installed, there is not enough room to upload the new firmware.

Avoiding scammers? You can't... They're all over the marketplace in this forum.

All you can do is mitigate the problem... Be VERY paranoid. Insist users send you "validation" PMs from a Bitcointalk account using either signed messages from a staked address or using a unique codeword that you make up on the spot so you can be confident that you're dealing with the correct person and not an imposter.

Don't deal with newbies if possible.

Try and avoid Telegram. Document everything (screenshots of PMs and Telegram where users can unilaterally delete entire conversations at any time! ).

Use Trusted Escrow!... Avoid anyone who refuses to use escrow.

Avoid any "auto buy" deals like selly.gg.

Be wary of users using self-moderated or locked threads that want to deal offsite.

Be very suspicious of extreme discounts (likely stolen, fake or carded)