Can you recall the original addresses? Do they start with "1", "3" or "bc1"?
Also, you said you've tried to enable the "BIP39" option, right?
If it happened to be a BIP39 SEED, was the message on the left side of the option said "BIP39 (checksum: failed)" or "BIP39 (checksum: ok)"?
Because any of the two will enable you to press "next" button to create the wallet but real BIP39 SEED will display as "ok".
If not, you might have miss-clicked one or changed the order (now or during the 1st wallet creation backup).
It's not bip39 because he says above that there are words that are not a part of the bip39 wordlist. |
|
|
|
...but then it pops up this messege and says: Wallet file corruption detected. Please restore your wallet from seed, and compare the addresse…
This means that your wallet file is corrupted and could possibly be creating addresses that are not backed up by your recovery seed. There was an old issue that was fixed whereby you could end up with a situation like this: When creating a new wallet, the path would be set to the path of an existing wallet, as due to os.path.exists failing, the wizard would think there is no file there yet. However in the wallet storage constructor, os.path.exists would suddenly work and the existing file would get opened. The wizard would then start modifying the existing file, thinking it's a new one. The wizard would put a new seed and xpub there. Then, the task that creates the addresses for the xpub (create_addresses) would be a no-op, as it would find that there are already "enough" addresses generated in the file (corresponding to the old wallet!).
When the wizard finished, the wallet would then get opened as normally. The wallet file would contain the new seed, new xpub, but old addresses. It would appear that you might have had something similar happen... You should create a new wallet ("File -> New\Restore -> NEW_WALLET_NAME -> Standard wallet -> I already have a seed"), as suggested by nc50lc... and see if it generates the same addresses as the wallet that is giving you the corruption warning. If it does not, then your seed will not be able to restore your wallet file. You should immediately create a new wallet (with new seed) and send all your Bitcoins from "corrupt" wallet to new wallet. He should definitely attempt a restore but if his seed doesn't generate the same addresses he won't be able to send coins from the old to the new one. That's because the old wallet doesn't have the corresponding private keys/precursor seed either. |
|
|
|
No, some of them are not in there.
You did check both lists right? If yes then it's not an electrum seed. |
|
|
|
I compared my seed with the list and all the words are there...I triple checked when writing it down.
what software was originally used to create the seed? |
|
|
|
are all the words in this list? this is the old electrum wordlist and is different from the bip39 one. |
|
|
|
|
aunt's daughter as in cousin?
|
|
|
|
Did they stop the new rollout that came with the version 0.18 where they said they were going to reduce it to 0.25 sat per byte? Am I dreaming or was this not a thing a while back (speculation if nothing else).
I don't see anything about that here: https://bitcoincore.org/en/releases/0.18.0/ |
|
|
|
|
Instead of installing it just untar the tarball, change to the directory that is created and ./run_electrum.
|
|
|
|
See here for things you can try. |
|
|
|
|
Bitcoin core's default policy for minimum relay fee is 1000 sats per kb (1sat/byte - 1000 bytes per kb here). This is the default but can be customized by every full node operator. Most don't change it though so that's why you won't find many servers willing to accept a lower fee transaction. If you need to make such transactions on a regular basis you should make some arrangement with a miner. Such a low fee transaction can be mined and once mined it will be accepted by the whole network. Of course an arrangement with a miner will cost you more than 1sat/byte unless you are a very heavy user.
|
|
|
|
The sort of people who fall for phishing scams or fake electrum ads on search engine results pages don't know about this forum and never visit it. Wait that's not entirely correct. They look up this forum after they get robbed  |
|
|
|
It works! Thank you so much but I would like to know if this forum is save for newbie because you actually help me while user "racquemis" is trying to take advantage of me through PM by sending scam link to download electrum 3.3.6.
Use the report link in the PM to alert the moderators about that. The bitcoin world is full of minefields like these. You will have to learn to navigate around them. |
|
|
|
|
Usually this happens because users are confused about the unit of account electrum is using. By default that's mbtc which is 1/1000th of a bitcoin. You can change this via tools > preferences > general tab > base unit option.
|
|
|
|
hi Yuri. This is an English part of the forum. You may try to ask in your language's subforum too (Russian?) https://bitcointalk.org/index.php?board=10.0Electrum 3.2.3 does not connect to the correct servers. Please download latest Electrum from electrum.org and only from there. The electrum 4.0 from your images is a FAKE electrum and will steal your money. I hope that you did not install the fake electrum 4.0.... wrong thread |
|
|
|
Its realy helpful
what is command return hex information?
i don't understand what you mean. if you're asking what is the hex code in my post above then that's the signed raw transaction. it's the output of a payto command. |
|
|
|
|
you can export your private keys via wallet menu > private keys > export. you only do this if you're migrating to different software. if you're looking to use electrum on android instead then just restore from seed there.
|
|
|
|
payto 0.01 some address
I get txid on the exit, just only in one line
then used
broadcast txid
and nothing happens, sometimes log out of wallet
When I tried it with a testnet wallet I got this: {
"complete": true,
"final": false,
"hex": "0200000001cb82ec8472ed20c673981b6e3a16412bdb2ed74e83e3de276cc682f899897be300000 0006a473044022049d847289909e34a48108227b7e758099597d8b5c76e14c5962e32f35719dcea 02201eba17af8474f3c197380f715d8576bf68da3285d2e13f402f9882a808bdbba901210336818 23e6685f066665bf4055f5e57fc31f5d7ac0cc41481c36d5c713c8d542efdffffff0240420f0000 0000001976a91404854d7d6026cb44cbe5c2383c2a51697eac54ba88ac5ece8800000000001976a 914dc75f929a516d15ba6a93c45f60ef029734cead888ac00000000"
}
Then you copy that hex code and broadcast it. For example in the above case I did a "electrum broadcast 0200000...000". That hex code is not the tx id. It's the signed raw transaction. |
|
|
|
|
keep trying different servers. right click on a server and click use server to switch servers.
|
|
|
|
|
Show Posts
