after recovered damaged WIF key about a yr ago got abit passive and failed to download all wallet.aes.json in time for the walletID that are known (email) but password and seeds were unknown because fireproof bag was hidden and forgotten.

Long story short really old skewl stacks of 2013-'15 era blockchain.info printed paper wallets were recently found in fireproof bag, with wallet ID entered in the following format:
??-?-?-?-???
and password
and of 19 word non standard blockchain.info recovery seeds.

few walletID paper even had what I believed was backup: several QR code - no its not contain QR code to WIF (in earlier days you could print sheet with all P2PKH + WIF keys but this is not it), but after scanning each one consecutively and concatenate together it appears to be encrypted json backup of sort. pbkdf2_iterations version 2 payload "blahblahblahveryverylongstringcompleteblahblah" is shown.  This was dumped from javascript console from var/obj that believed to hold the encrypted wallet back in 2016 or so (before download-blockchain-wallet.py) was available, and extra attempts were made to try to backup from client side .js memory - as I believe (at the time) that blockchain.info is doing java script kung-fu in memory and session data had all the information needed relating to each wallet-guid instance.

knowing one day I would eventually encounter lost hand hodl (now diamond hand hodl) bag (just as predicted, by accident), back in 2022 I even made attempt to download wallet.aes.json for one that I remembered to have most balance (after scrolling thru email), and waited.

btw contrary to belief blockchain email don't actually contain backup of wallet.aes.json.  was using recovery download-blockchain-wallet.py 3 years ago to download encrypted wallet.aes.json but still unable to open it because did not have time to btcrecover with different wallet guid / possible password pairs.  Now password and non BIP39 mnemonic in the fireproof bag was found it should be super easy to recover if wallet.aes.json for each guid can be retrieved.

as BTC is approaching 99999 finally I started to think that blockchain.com won't easily make it diamond hand hodl friendly.  So I begin to unseal / access the fake make belief self-custody wallet.  Sure enough:

When hitting Blue Continue button, following messages (in the order which) appears briefly

obtain account info
Decrypt wallet data
obtaining encrypted data
Migrating Data

Then red "Invalid Token" is than shown below Email or Wallet ID Field!

the password is correct, because if incorrect password entered field  "Password" would throw different error - "Password doesn't match.  Try again." would appear

and when using login.blockchain.com/beta/auth/recovery "Input your Recovery Phrase" error - "Invalid Recovery Phrase" error was thrown.

I tried ?-?-?-?-???">https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=??-?-?-?-???

but it throws Unknown word rejecting
Unknown word midas or tickers
Unknown word incessant
...
...
and so on.

Then I tried to recover with wallet.aes.json from most valuable wallet I believe that was downloaded in 2022 with download-blockchain-wallet.py assist actually turned out to be super easy to recover, since no cracking was needed (passwords were correct as they were written down on wallet paper backup)

I did python3.11 btcrecover.py --wallet wallet.aes.json --dump-wallet wallet2.txt --correct-wallet-password mypasswordfoundinfireprofbagpaperwallets2024 and waalaa! all the WIF and Pubkey was found when cat wallet2.txt.

bcore28 importdescriptors (getdescriptorinfo "wpkh(WIF) found hasprivatekeys:true and has #?? checksum  ) works and recovery was successful

Now I wish there are ways to make ?-?-?-?-???">https://login.blockchain.com/beta/legacy-pages/forgot-password.html?guid=??-?-?-?-??? available again, or make download-blockchain-wallet.py work again (which it throws errors)
Traceback (most recent call last):
  File "download-blockchain-wallet.py", line 76, in <module>
    auth_token = do_request_json("sessions", "")["token"]  # a POST request
  File "download-blockchain-wallet.py", line 72, in do_request_json
    return json.load(do_request(query, body))
  File "download-blockchain-wallet.py", line 66, in do_request
    return urllib2.urlopen(req, cadefault=True)  # calls ssl.create_default_context() (despite what the docs say)
  File "/usr/local/lib/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/local/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/usr/local/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/usr/local/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/local/lib/python2.7/urllib2.py", line 1241, in https_open
    context=self._context)
  File "/usr/local/lib/python2.7/urllib2.py", line 1198, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error [Errno 8] Name does not resolve>

As bitcoin price hit new low it is getting hard to justify selling bitcoin to pay for GPU rentals - so I'm trying to think outside of the box for finding public key for damaged WIF backup (see post#https://bitcointalk.org/index.php?topic=5380095) that happened approx. an year ago -

but Since the address in question (P2PKH) contains newly generated block rewards from solo hashing over a good period of time, but none of which were spent (unfortunately, and neither do I have an signed message for this P2PKH address) - is there any reason why scriptSig from generation transaction recorded on main net not providing me my public key?  maybe the offset I'm copying is incorrect - or it is just impossible all together

The other place I think May be of help is digging thru stratum blocks logs on the server - which had been sit dormant for about an decade in storage - but this opens up whole range of new issues (log analysis, damage to hardware not used for long time, etc)

Hi Guys,

sometime meals/lodging were being paid but by default Bech32 (Segwit) were auto selected on the dropdown box of BCore 23.
this is creating a bit of confusion for our cashiers - had remember to either uncheck create bech32 address to change dropdown to select Base58 so it creates a bit of confusion.

This had to do with wallet implementations I think - because not all can process upper case bech32 addresses. some of them won't even allow prefix / substring that starts with bitcoin:BC1Q*******. (it is a bit irony that bitcoin: part is lower case, whilst address isn't)

did look for command line arguments on wallet options but to no avail (so can be specified when starting Bitcoin core).  Any tips on an work-around are appreciated!

my WIF paper wallet from around 2013 was damaged due to rats chowing thru area where it was stored, it held majority of my bitcoin holdings from years of solo-mining and after consulting various local experts it appears to require significant computing resources to have it recovered

Now I am giving bitcointalk a try to see if someone here could shed some light on actual algorithmic complexity so to have an idea when would it be technologically / economically feasable to have it recovered

I am using the following example to give you guys an idea on scope of damage:

Let

5KFE3ScWZMf4TdAuVNYKDU7UtTBmHf9M           LHs1AkbD

be the damaged key, and:

suppose the DHiTxZ8xUrg portion was damaged (rat chewed it away..), where the full key *if* successfully recovered in this example should be

5KFE3ScWZMf4TdAuVNYKDU7UtTBmHf9MDHiTxZ8xUrgLHs1AkbD

with 11 char missing now the complexity for recovery is somewhere around 2498664400016553792, or 2.5 x 10^19!

The problem is further complicated by the fact that WIF algorithmically requires 2 rounds of sha256 calculation, which is very slow to checksum in my poor attempt to "guess at" even with access to computing resources with large number of cores (like AWS).

Not sure if someone can offer some formal asymptotic analysis on the aforesaid situation.  Maybe I am not approaching this problem correctly, but I guess someone might have a better idea in similar situations

and of course Happy new year all! 恭喜發財!

cultural heritage are things invented in the past that can be considered as common asset of mankind, for current and future generations.

Some example:

Invention of Arabic numerals and its implication in modern mathematics.
The spirit of Greek / Rome empire
US Democracy (disputed: may soon to be lost due to communist/socialism globalist deep state take over)

will BTC be considered cultural heritage? if so what are its merit?

as of Fri Nov 13 05:12:46 UTC 2020
blocks were not full (block#656695, 656702,.. )
mempools are well within 5MByte

time to consolidate coins or reduce fee paid in your future transactions by converting non segwit coins into full segwit.

I think Feds might be actively figuring out ways to hi-jack Chipmixer non-onion .com site and interdict chipmixer users.  It didn't happen often before, but now occasionally I am getting invalid cert warning on Chipmixer's .com site.

so far since chipmixer isn't using CDN network such as cloudflare and Akamai; harvesting (or "leaks") of user session and address data isn't exactly easy (common tactics used in the past against crypto exchanges).

However, manually hijack and present an fake SSL using specialized MITM appliances to stole and to analyze chipmixer user's fund should be deemed plausible given mass surveillance and maturity of man-in-the-side operations given the past cyber incidents. (i.e., Fed Spy on chipmixer user, once session data's btc address were observed and funded, lets hit that and put it up for federal auction)



Would anyone able to analyze and provide genuine TLS signature value of Chipmixer?

thanks!