Another quick reminder for you is never click on Help > Check for updates. This feature of Electrum wallet was compromised in the past.
That feature wasn't compromised ever. The past " hacks" were due to a modified ( error) messages issued by a malicious server. As the matter of fact, there are servers that still try to display those messages but " safe versions" of Electrum wont display them the way they wanted. Update check's message is a lot different too. Here's the Pull Request and commit for more info: [Qt] Add optional update notification #4985 | [Qt] Add optional update notifications |
|
|
|
I tried to use: the full path, the directory, and also the filename on its own, but that didn't help.
Adding the wallet.dat itself to the path wont work, just the path to the wallet.dat just like in my example. In your case, its should be bitcoin-cli -testnet loadwallet D:\Bitcoin Core\testnet3\walletsBut since you've already included walletdir to the config, it should work now without using '-rpcwallet'. Figured that because core's createwallet doesn't create a renamed 'wallet.dat' but a folder with the name you've specified with a wallet.dat inside it. |
|
|
|
|
Just a bitcoin address, nothing else.
BTW, the one in your 'receive' tab will change once it received bitcoins once, it's the same as the one in your address tab (from top to bottom) if you enabled it.
|
|
|
|
|
Click receive tab and send the "receiving address" (starts with 'bc1' or '1') to the client, you don't have to create an invoice to receive bitcoins.
But if you wan't it to have a description in the history, create one with/without an amount.
To use the address tab which was suggested above, click "View->Show Addresses".
Note: There are services that still don't support native SegWit address (bc1).
|
|
|
|
You shouldn't have shared that ciphertext in the OP. I suggest you remove it or someone might attempt to bruteforce your password and succeed where you've failed!
You missed the part where he said that it's just a sample. ^ *Btw, the above is a sample of what my file looks like. not my actual wallet info*
@ suttonbitcoin Can you tell us the name of the wallet that exports that kind of " encrypted wallet"? So everyone here can search for the native app/tool to decrypt it. Although there are tons of ways like HCP's example. |
|
|
|
The wallet was made for me with a password that I changed after logging in and transferd the minimum investment fund of 500$ I was told that the earnings was 60$ a day for 30 days.
Anyone can make a watch-only wallet by pasting an random bitcoin address from the internet. In this case, they must have given you a watch-only wallet created from their own wallet's addresses which is in their control, they can take out the funds from it any time. They only given you the watch-only wallet because they wan't you to have a "false sense of security" that you now got the wallet,
but you didn't, you're just "watching their wallet".I was told that the earnings was 60$ a day for 30 days
The numbers don't add-up if you'll profit that much for a $500 " investment". Miners can barely earn $1 a day per Antminer S17, minus the electricity bill. For legit ( but not profitable) mining contracts, it's usually $40-60+ for 1TH for 12 months ( diff per cloud mining service), that's to cover the operating cost. You'll rent hashrates and earn what it can; not invest bitcoins to cloud mining service and earn a specific amount.A piece of advice: if you hear " invest" in crypto space, it's a scam 99% of the time. |
|
|
|
TL;DR: Try 'loadwallet' first before using '-rpcwallet' using full directory path on both commands. Refer below for the commands. Long " story" follows:
I've been trying to use the following commands: bitcoin-cli -testnet listunspent
bitcoin-cli -testnet createwallet XXX
bitcoin-cli -testnet getnewaddress
But they're all returning the same error: It worked initially for me even if I use a different 'walletdir' in the config file. But after using '-rpcwallet' once, only the two commands returned with the same error. The other one: bitcoin-cli -regtest createwallet xx still worked at my end. Any thoughts?
Wallets from a different directory like E:\AppData\testdir\wallet1 just returned with this error: error code: -18
error message:
Requested wallet does not exist or is not loaded But it worked ( with full directory path) after using 'loadwallet': bitcoin-cli -regtest loadwallet E:\AppData\testdir\wallet1 bitcoin-cli -regtest -rpcwallet=E:\AppData\testdir\wallet1 listunspent And my other test, I have other folders with wallet.dat in the same location as my custom wallet directory, using just that folder's name worked. Example: My custom wallet directory is in E:\AppData\testwalletdirMy other wallet is in E:\AppData\testwalletdir\wallettest1 | These commands worked: bitcoin-cli -regtest loadwallet wallettest1 bitcoin-cli -regtest -rpcwallet=wallettest1 getnewaddress Use 'loadwallet' only once.
|
|
|
|
|
If you need the last source code that didn't require 'secp256k1', I still have it.
File timestamps are Feb4 & 6 (I won't provide a link because of Electrum's false-positives).
That's as risky as using other's compiled 'libsecp256k1-0.dll', but you can review each of the files to check if something was tampered.
Also check if that bug fix was covered in that version.
|
|
|
|
The transaction was send to address unknown to me: 13k4rgQ6b9LdBt6pvgLR5MSV6wAhujFpgq -snip-
Looks like it's being used to receive hacked bitcoins not exclusive to Electrum, the chance of being fake Electrum the culprit slim. It was reported here: https://bitcoinwhoswho.com/address/13k4rgQ6b9LdBt6pvgLR5MSV6wAhujFpgq, expand the " scam alert" portion. What are the other installed applications you have in your phone? And please answer the question in post#2, where did you stored your 12-word seed phrase? <-- must be the issue. |
|
|
|
That's a genius way to use their famous brand to something low-cost but profitable. And look at the bright side: In Bitcoin, more mining pools means less accumulation of network hashrate to a single entity. If that pool makes it to the top, then the risk of a mining pool reaching the power enough of a 51% attack will drop significantly. It's a win-win in a 90-10 way  |
|
|
|
I don't know if number 1 is legit because I've requested a few times from there before and nothing was sent to my testnet address. Maybe out of funds that time? Now, it's just " internal server error". For the record, I've received quite a few from number 3 for lightning network tests but it's closed for now. mocacinno has his own testnet faucet: https://tbtc.mocacinno.com/ ( bct thread) |
|
|
|
This part of the title is just bugging me: " into unexpected wallet" So you knew that that address doesn't belong to your Electrum wallet? Can you follow this guide ( by Abdussamad) to confirm if your installer/executable is legit: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/? Does it seem someone here has the same issue(Related case) with the same version 3.38 from here? vovven already confirmed that it's a typo in this post. But yes, it's best to check if OP is using the real electrum. |
|
|
|
Okay, here's the procedure to create a cold-storage mobile Electrum wallet: - 1. Install Electrum on both devices, and create a standard wallet on the "cold storage" device, that will be your main wallet that contains all the keys and shouldn't be connected to the internet even once (a newly formatted device/new device is better).
Make sure that the seed was saved in a physical backup like a piece of paper. - 2. Click the wallet's name on top of the screen and click "Master Public key" twice to open the QR code.
- 3. On the online phone, create a new wallet using the option "Standard Wallet->Use a master key", then click the camera icon to scan the cold-storage wallet's QR code.
This will create a watch-only wallet version of your cold-storage wallet. - 4. Confirm if the address in the receive tab is the same.
Now to use those wallets: - You just have to create a transaction using the online watch-only wallet using the send tab.
- Fill out the recipient, amount, etc. then, click pay (select if you want to opt-in RBF, yes) and click the QR code icon below.
- In the cold-storage wallet, go to send tab and click the camera icon on the right side and scan the other device's QR code.
- The transaction will be imported to the cold-storage wallet, now click option->sign (enter your pin) and it will be marked as "signed" above.
- Click the QR code icon, then scan this using your online watch-only wallet and the signed transaction will be imported and now you can use options->broadcast button to send it to the network.
If you're not familiar with Electrum's defaut bitcoin denomination, you can change it from mBTC to BTC in the settings->denomination. |
|
|
|
To be more clear, did you mean to use it as a multisig wallet?
Uh, nope. What I described is a cold-storage set-up which is a lot secure than directly using a mobile as a wallet. You can use two Electrum mobile to do that and phones with working camera (Only download Electrum from: https://electrum.org/#download). One offline phone containing the seed and another one with just the master public key that can't be hacked. Please, do you have any article for this?
I'll edit this post / reply with the steps since I haven't found a tutorial for electrum mobile in the internet. |
|
|
|
|
2 Mobile phones? Then it's better to use the other one as a cold-storage for signing transactions,
and use the main online phone as the paired watch-only wallet for monitoring the balance and creating transactions.
It's a lot safer than just using one of the phones as a wallet.
|
|
|
|
My question: Is there some kind of an agreement out there (i.e. a BIP) which tells that the blocknumber should be stored for example in the "extra data"-field within the coinbase transaction?
BIP34, looks like you already knew the answer prior to posting this question because your guess too specific :p For the " blocknumber", the equivalent must be bitcoin's " block height". |
|
|
|
|
One thing that I've noticed is every fully encrypted wallet mostly starts with "QklFMQ" when opened using a text editor.
Starts with "42 49 45 31" when converted the full base64 string into hex.
But it starts with "51 6B 6C 46 4D 51" if you directly convert the wallet file into HEX, not the contents.
Those are varying in length so it will be hard to pin-point what you're looking for if you just have a hex dump of your disk.
|
|
|
|
So here was the problem, the BIP39 was wrong. I tried another one and it worked ! Thank you very much !
Ah, so it's simpler than most of our guesses. Actually that's what I initially though but most of the time, it's not the case. Congrats BTW. You can consider locking this topic now if you want, there's a small " lock topic" button at the lower-left side of this page. |
|
|
|
So far the first cryptocurrency is bitcoin, even, not only the first bitcoin wallet but the first crypto wallet ever is bitcoin core. Thanks for the link you sent, it was so helpful for me to know when and how bitcoin core started.
There are couple of older cryptocurrencies ( digital currency) that predates Bitcoin, HashCash is one of the most recognized among them. Some older ones didn't used a similar approach as HashCash or Bitcoin and IMO shouldn't be called " cryptocurrency". If OP wants us to google search and read a certain online article that's just been posted, he's succeeded  |
|
|
|
They're both mobile wallets, you won't be able to recover them on Electrum mobile if it's the only device op has...
That's too risky. Electrum will use a different derivation path to samouri and exodus so you can't use it to restore your wallet unless you have a desktop handy where you can change the path. I thought you knew that Electrum Mobile currently doesn't support BIP39 seed, only on the development build or next release, that's why you replied that he wont be able to recover it to Electrum. @Royse " too risky" as a reply to that post didn't made sense. |
|
|
|
|
Show Posts
