Did you use a downloaded "offline" copy of segwitaddress.org? Or did you do all of this while connected to the internet?

If you did all this while connected to the internet (or on a PC that was subsequently reconnected to the internet), then "the part you fucked up" was doing this online! You should consider that paper wallet compromised and you should not use it. Great care needs to be taken when generating paper wallets to avoid any possibility of the private key(s) being compromised.

Creating/storing "digital" copies of your key(s) using the "snipping" tool is also a very bad idea.

At the very least, the generating code should be run on an "offline" PC... preferably one that will never be connected to a network again.

I can't answer for certain... as I can't update at the moment But the release notes indicate that they've made some optimisations so that you can install more coin apps. They say it should be similar to the amount of space for apps that was available in the 1.4.2 firmware.

Have a read of the "Increased Capacity" section here: https://www.ledger.com/new-firmware-update-for-ledger-nano-s

Ok... so I think you need to read the "Unicode Support" part of the btcrecover docs (if you haven't already): https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#unicode-support

You will need the --utf8 commandline argument... and to make sure that your token file is saved in UTF-8 format.

Essentially that is correct... but you need to be aware that Electrum is somewhat of a "special" case... Electrum, by default, is NOT BIP39 compatible... While it uses the BIP39 wordlist to generate it's seed mnemonics, they are NOT BIP39 compatible.

However, Electrum can *import* a BIP39 seed... on the seed entry screen, you click "Options" button:



You then select the "BIP39 Seed" option:



And make sure that you read the warning:



Note also that Electrum will NOT store a BIP39 seed in the wallet file (unlike a native Electrum seed), so you cannot recover a BIP39 seed from a restored BIP39 wallet file ("Wallet -> Seed" option will be greyed out).

Whatever algorithm they're using, it's starting to be annoying. It's been days since I got the email... and I still don't see the update button in Ledger Live. Either their server infrastructure needs some massive upgrades to support the load or their userbase is HUGE... I know which one I'm betting my money on!

Given the limited storage on the device... how big can a Nano S firmware update actually be anyway?

Blockchain.com does support creating signed messages. However, it will only allow you to sign with an imported private key.

In the settings, select "Wallets and Addresses":



Click the "Import Bitcoin Address" button and follow the prompts:



Once the private key has been imported, you can click the "More Options" button on the right and select "Sign Message":



You can then enter your message, click "Sign" and you'll get the message signature:



NOTE: If you want to practice... you can use the private key found here: https://en.bitcoin.it/wiki/Private_key#Base58_Wallet_Import_format

It is a very "public" private key for the address "1CC3X2gu58d6wXUWMffpuzN9JAfTUWu4Kj" as seen in the screenshots above

There are ways to extract the private keys for the addresses already in your blockchain.com wallet (and then "import" them)... but I would NOT recommend it. The potential for your private keys to be compromised is high if you do not know what you're doing... which could result in loss of funds.

Easiest way is to look at: "Blocks"

If the blocks number is equal to the height of the longest chain... you're synced. You can double check on any of the common block explorers... like blockcypher: https://live.blockcypher.com/btc/




#Blocks == Height... you're synced. So what is the "blocks" value from your getblockchaininfo command?

^^-- THIS

A lot of people mistake Bitpay's "10 minute" timer for "I need to get a confirmation in 10 minutes"... but that is ridiculous because no amount of fees can guarantee a confirmation in 10 minutes... the size of your fee has no bearing on the miners ability to find blocks

The Bitpay 10 minute timer is simply the time limit to broadcast a valid transaction... it can then take however long for the transaction to confirm (within reason? )... Bitpay just won't confirm the payment to the merchant until you get at least 1 transaction.

I've had a payment via Bitpay take over 2 hours to confirm (was broadcast and received within 5 minutes) before... The merchant just didn't release the order until that confirmation came through.

Right... so the idea is you're wanting to gamble low for the first 10... and then because you believe the chances of winning are higher after 15, you can increase the bets to make back all your losess + big profit? You might want to read this: https://en.wikipedia.org/wiki/Gambler%27s_fallacy

Seriously tho... that shouldn't be too difficult to do... although attempting to code it as a dynamic system within the bot could be quite complex, depending on how complicated the system you're playing is.

In the "simple" 2x system... (only adjusting the bet amount and not multipliers/payouts etc)... the formula for total amount lost in 10 bets is simply: (Initial Bet * 2^10) - Initial Bet)

Say you initial bet is 1... that would give:
=> ((1 * 2^10) - 1)
=> ((1 * 1024) - 1)
=> (1024 - 1)
=> 1023

For an initial bet of 2000 that would give:
=> ((2000 * 2^10) - 2000)
=> (2000 * 1024) - 2000)
=> (2048000 - 2000)
=> 2046000

However, trying to work that backwards from a starting balance to derive what the starting bet should be is a bit more difficult... A formula like: (Starting Balance * 2^-10) would give you the initial bet you could make, and still have enough left for the 10th bet...

For instance... Starting balance of 3142547... then: 3142547 * 2^-10 => 3068.893555

Checking against the previous formula: (3068.893555 * 2^10) - 3068.893555 => Total loss of 3139478.107... which is just under 3142547. But to try and work that out across THREE different blocks of 10... with dynamic starting amounts gets messy very quickly. Especially if you want to be able to increase in the 2nd/3rd blocks...

Nevermind, the fact that even just 30 bets of a straight Martingale requires that you have an ENORMOUS starting balance (~11 BTC if you start with just a 0.00000001 initial bet )... If you try and increase in the 2nd/3rd blocks, the starting balance would need to be astronomical to try and make bets that could cover the losses!

You could try just flat betting the first 10... and then start increasing, but you run the risk of a lot of streaks <=9 with only smaller win streaks inbetween slowly eating your balance down until you can get to your "big bet" 15+ losses territory...

In a word... Yes.

That was basically one of the core reasons why I would not recommend Exodus to anyone. I'd be more inclined to recommend it now... Are users able to specify fees now as well? Or is that all still handled automagically based on network conditions?

Yeah... that comment about the 3.79M BTC being lost is more than a little deceptive... but hey... #marketing

However, people *are* losing seed mnemonics... I'm probably into at least double digits of helping people who have either written their seed down incorrectly to start with (wrong words or missed a word etc), had it partially lost through accidents or simply lost the entire thing altogether... Then there are the folks who have a perfectly valid seed, but for the wrong wallet.

There have been numerous instances of these things happening on these boards over the last couple of years. Granted, they are more likely to be a fraction of the "lost" bitcoins... but it still is relatively common. All that does is prove that there isn't a 100% fail safe way of backing things up... and I'm not convinced that Evercoin's method of "shards" is the best way to mitigate it.

But hey, if you already have a Yubikey... I guess it's probably better than simply having a wallet app on your phone ¯\_(ツ)_/¯

Looks like you're on the right track... at least btcrecover seems to be working ok!

As for the error, if you look at this page: https://theasciicode.com.ar/extended-ascii-code/acute-accent-ascii-code-239.html Do any of the characters you think might be in your password show up as having a code in the "Extended ASCII characters" section? ie. it has a "code" that is 128 to 255?

No... all those files are either encrypted (or not useful)... even the "unencrypted" wallet backups in the "wallet-unenc-backup" folder... you can tell because it has the .CIPHER extension... this is what happens when you add a password to a wallet file that WAS unencrypted:


You can see the full list of what all the different files are here: https://multibit.org/help/v0.5/help_fileDescriptions.html

Basically, without the password, you cannot recover the information from these files.



To use the char % in your password... you specify it in token file as: %%

as per the tutorial:

If I understand correctly you're trying to limit your exposure by only using X amount of your bank roll for each 10 rolls, but for the 2nd and 3rd blocks of 10... the only way cover all the loses from the previous 10 rolls is to continue on the same martingale betting pattern (or higher!).

In other words, it's just a straight 30 rolls with increasing martingale bets and you either hit green or you don't... it's the only way to do it and break even when you hit the green. (Unless you are wanting to actually increase the bets above the minimum required to break even in each block?)  

For instance... say your first 10 reds at 2x payout, are the following bet amounts:
1-2-4-8-16-32-64-128-256-512...

The only way to cover those first 10 losses are to continue the same betting pattern in the second block:
1024-2048-4096-8192...524288

or something higher like:
2000-4000-8000-16000...1024000

You'd then have to do the same in the 3rd block... same betting pattern or higher.

In that case, you just need to figure out what the max loss you want over 30 bets is... then calculate what the starting bet should be so that you don't exceed that value over 30 consecutive losses. This is probably easiest to actually just create a spreadsheet that does the math for you... and you can modify the start bet and/or the payout multiplier and then have it calculate projected losses for X number of bets and you can simply adjust the values to see what you want it to be.

Here is a simple one that is only useful for a 2x payout (should be around a chance of ~49.5 for most dice sites): https://docs.google.com/spreadsheets/d/10cC_ODRYde8nuWRMb4b5uQkI_-8uY37ktN5tjsf-CzM/edit?usp=sharing

As you can see... starting with a bet of just 0.00000001, you'd need a starting balance of 10.73741823 to be able to make 30 bets at 2x multiplier... and would make a profit of just 0.00000001 when you hit green!

NOTE: If you want to do other chance/payout values, you'd probably need to do a bit of editing to make the bet increases relate to the multiplier/payout properly.


So, I guess the real question, is what are you actually wanting to achieve by splitting into three different blocks of betting?

---

Just wanted to record this post for posterity before it gets nuked. WTF is a "Deep Web Database Officer"? Still... he must be some sort of cypto god... being able to "dragged the btc back into my wallet"

Bonus points for this: "even without authy my account is safe and cant have any stolen coin"  

As explained above, Exodus supports exporting of keys... but it also provides a BIP39 compatible seed mnemonic (aka "Recovery Phrase"). I've never been able to test it, because Exodus refuses to let you actually access the backup "recovery phrase" (and therefore test the backup) until you have deposited coins into the wallet.

So, as long as you have the 12 word "recovery phrase"... you can restore your wallet to another BIP39 compatible wallet should Exodus no longer work.

Which wallet did you send from exactly? Was it sending from a different wallet to your Bitcoin Core wallet? Or did you send from Bitcoin Core to Bitcoin Core?

I suspect that is to help reduce server load and prevent issues seen in previous updates where users were getting failures due to server overload and the updates failing.

Meanwhile... I'm back from my travels and was wanting to update to 1.6 to try it out... aaaaaaaaand no sign of it in my Ledger Live... I guess "3 days" is not quite "slightly later" enough for Ledger

The website says the Yubikey is actually "optional"... so it seems it is just "added" security on top of whatever the app itself provides?


They do... it's just that "shard" thing... It sounds like it is essentially a 2of2 "Shamir Secret Sharing" type scheme... you get 1 shard, they store the 2nd shard... you need both to be able to restore your wallet.


According to Yubico:

So you'd need to query the Evercoin peeps and find out from them... I couldn't find any support docs etc on the website to explain what the resolution is should you lose the yubikey.

It looks like you still have all the necessary files... so that's a good start. Now, it's really just a matter of finding the correct password.

Does the MultiBit install still work? As in, you can actually load up MultiBit and see the wallets etc? If so, that would suggest the files are hopefully not corrupt. Then, it's just a matter of getting the password.


Getting Python and btcrecover working can be a bit daunting if you're not experienced with commandline applications... but it's not impossible. You just need to make sure you use Python 2.7.x and follow the instructions as outlined on the btcrecover github: https://github.com/gurnec/btcrecover/blob/master/docs/INSTALL.md

If you're unable to get btcrecover working, then you're basically left with the option of engaging a 3rd party to try and recover things for you... my recommendation would be: https://walletrecoveryservices.com/


Also, in case it wasn't obvious, there are a lot of scammers here on Bitcointalk... so be VERY cautious if anyone offers to help via PM or Telegram etc and asks you to send your wallet files/passwords etc!

Are you running the 32bit or 64bit version of the OS? That sounds like the old issue with 4GB of RAM and 32bit operating systems...