That only goes as far back as to version 1.8 from 2015. Electrum's GitHub releases date back to 0.56 from 2012 (
https://github.com/spesmilo/electrum/tags?after=0.57a). I am not sure if it's possible to find versions of the software that are older than that. I think anything older than 3.3.4 can't connect to servers anyway.
For older versions, he can look for a specific commit in GitHub and browse the repository at that point.
For example; from initial commit onwards:
github.com/spesmilo/electrum/commits/master?after=bdbd59300fbd35b01605e66145458e5f396108e8+14035By clicking "<>" (
Browse repository at this point), you can get to the source code at that time to try to run it with old version of Python. (
only useful if the seed is complete)
For example; v0.31:
github.com/spesmilo/electrum/tree/eaedbae083529fc12044ecfb5b0b613c32c70691But, if the notion of what we have been nudging at is true, that the version of Electrum I used had it's own way of using the same 2048 words but NOT implementing the BIP 39 standard, then not only do I have a unique situation, I also have a very difficult path to get the mnemonic correct.
I was using anything from Electrum version 0.29 to 0.46. Maybe there is some backwards compatibility in those versions. I will have to research more
The good news is, Electrum keeps backward compatibility from v0.34 to the latest, the old mnemonic will be detected as "
old" and can be restored in the latest version without issues.
The bad news is, older versions than those have a key derivation bug that had to be patched which causes the private keys derived in those versions different than the keys derived in the newer versions.
In case it was v0.34~v1.9.8, BTCRecover can still be used with the right options when prompted: specifically seed type: "
Electrum 1.x".
But before doing it, double-check the words if those are included to the "
old_mnemonic" in my reply above.
Otherwise, it's newer that you thought or from a different wallet entirely.