Can you give me your contact information, or you can PM me via Telegram: https://t.me/MrIces910 I really need your help guiding me. I tried as you said but it still doesn't work and it seems that according to the results your Wallet_type and mine are different. Wallet Type: btcrpass.WalletElectrum2
-snip-
All possible passwords (as specified in your tokenlist or passwordlist) have been checked and none are correct for this wallet. It appears to be a bug in BTCRecover. I successfully reproduced the issue by creating a wallet with the same set-up in Electrum v4.3.4 mainnet ( and other 4.x versions) It shows the same wallet type " btcrpass.WalletElectrum2" and failed to find the password. Upon fully encrypting the wallet file, password recovery works. I used 3rdIteration's fork, both the latest master branch and the last release version behave the same. Wallet file from Electrum v3.3.8 works regardless of the level of encryption used. On the other note: I don't use Telegram, if there's someone contacted you claiming that he's me, it's a scammer. As o_e_l_e_o said, you'd better keep the conversation public so everyone can participate.
Interesting - Could you confirm what version of Electrum you have used for this test?
v4.3.4 - latest. But I found out that the wallet type: " WalletElectrumLooseKey" indicates that it's an " imported" wallet which only consist of private keys since it's the type of wallet that I've tested in that reply. |
|
|
|
nc50lc reports getting the same error independently of me and it does seem to be at or near the last block.
It always happens exclusively at the last blk.dat file which in my case " blk03531.dat" ( differs per node), not necessarily the last block height. Node isn't running. I've tested the latest code, master branch. Here's the error in case someone needs a comparison: Traceback (most recent call last):
File "T:\blockchain-parser-master\blockchain-parser.py", line 246, in <module>
tmpHex = merkle_root(tx_hashes).hex().upper()
File "T:\blockchain-parser-master\blockchain-parser.py", line 30, in merkle_root
return merkle_root([hash_pair(x,y) for x, y in zip(*[iter(lst)]*2)])
File "T:\blockchain-parser-master\blockchain-parser.py", line 30, in merkle_root
return merkle_root([hash_pair(x,y) for x, y in zip(*[iter(lst)]*2)])
File "T:\blockchain-parser-master\blockchain-parser.py", line 30, in merkle_root
return merkle_root([hash_pair(x,y) for x, y in zip(*[iter(lst)]*2)])
[Previous line repeated 995 more times]
File "T:\blockchain-parser-master\blockchain-parser.py", line 27, in merkle_root
if len(lst) == 1: return lst[0]
RecursionError: maximum recursion depth exceeded while calling a Python object |
|
|
|
-snip-
Electrum will only ask for password when access to the encrypted data: the master private key or seed are required.
When making a bitcoin transfer, Electrum still requires a password to sign. So I really need help. That's what that line is all about. Electrum will have to derive the required private key from the master private key to be able to sign a transaction. Since the master private key is encrypted, you'll have to provide the password to gain access to it. I've tried creating a similar wallet that doesn't encrypt files with the password I generate. I then put a password I know into the password list and tried running BTCRecover to see if it could find my password, but it couldn't find it. So I think BTCRecover only works with encrypted Electrum wallets with a password.
It works: I tried it with a test wallet which is not encrypted but has a password: 12345 ( BTCRecover referred to it as "WalletElectrumLooseKey") Here's the command that I've used: btcrecover --wallet test_wallet12345 --tokenlist test_wallet12345.txt Here's the contents of " test_wallet12345.txt": Here's the result: Wallet Type: btcrpass.WalletElectrumLooseKey
Wallet difficulty: 2 SHA-256 iterations
2023-04-12 12:18:30 : Using 8 worker threads
225 of 325 [#############################--------------] 0:00:00, ETA: 0:00:00
-snip-
Password found: '12345' |
|
|
|
-snip- If you're not planning to mine Bitcoin there's no reason for you to make use of Bitcoin Core,
Bitcoin Core isn't a hard requirement if you're planning to mine bitcoins, it doesn't have native ASIC or even GPU mining tool/function. Users can mine even without it, some pools doesn't even use it but use their own implementation of Bitcoin. So please don't associate " not mining" with the reason of not choosing Bitcoin Core. -snip-
Depends on the beginner, if your friend can understand instructions properly, Then he can easily set the reference client Bitcoin Core with the help of the basic instructions already provided by other users. Issues will arise depending on what he intended to do with the node. So ask him his end goal before recommending any software and hardware since it'll depend on the expected load. If just as a wallet software, then reading the instructions in bitcoin.org provided by others is good enough. |
|
|
|
|
I got the same error with my node's last blk.dat file that's expected to have a lower size and lower number of blocks from the rest of the blk.dat files.
Perhaps, that error occurred after parsing your second-to-last blk.dat file.
Was the last "Start blknnnnn.dat in 2023..." the last blk.dat file in your blocks folder?
|
|
|
|
But how did he manage to know the balance? I thought that the seeds and private keys are encrypted using AES-256-CBC, and therefore if you only have the file and without a password, you will not be able to know your balance.
The same way blockexplorers check for balance, just from the addresses or master public key. Users do not need to paste their seed or private key to check their balance. Electrum's wallet file is just a long .json human-readable data containing the addresses, transaction history, seed, master keys, some settings and other data. If the user didn't encrypted the wallet file but set a password as seen here:  All those data are still accessible by Electrum and still human-readable except the seed and master private key. Electrum will only ask for password when access to the encrypted data: the master private key or seed are required. |
|
|
|
If i cannot use Electrum, is there any other way i can speed up the transaction using bitcoin core wallet or ordinal?
Electrum can only import TapRoot Address to create a watching-only wallet. ( for now) With that, you can perform CPFP/RBF if it's possible but since it's lacking private key, it'll only create an unsigned PSBT ( partially signed bitcoin transaction). I'm not using Ordinal wallet, but if it supports psbt import, try that by exporting the " bump" transaction created by Electrum. But AFAIK, it needs more than just the address to properly create a TapRoot transaction, so chances that it cannot be signed is high. Warning: if the transaction that you want to RBF is NFT-related, do not perform RBF on it or you might mess-up your NFT. |
|
|
|
Further to that, I was attempting to run the command without rescan, and tried timestamp "now", but it gave an error:
When using the non-integer value " now", you'll have to enclose it with \"now\" or it'll fail to parse the whole json array. For the range, it's what the message said; if you've previously imported the same descriptor, you'll have to at least increase the range by 1 to include previously imported descriptor's range. |
|
|
|
Hello I have just tried to get my Electrum wallet and got my seed and repeated them...but I could not proceed any further
Pro tip: During that " Confirm Seed" step, Electrum will show you possible words while you're typing. If you've typed enough letters and there's no list of words presented, chances that there's a typo is high. It'll only take two to three characters to see a list of possible word. With that, check if you're typing any word incorrectly by checking if Electrum can't auto-fill the remaining characters. I'd also suggest to just pick from the selection of word instead of typing all the remaining characters to lessen the chances of typographic errors. |
|
|
|
Check your peers using the command: getpeerinfoSeed if all of them are " outgoing" by checking the line "inbound": false/true of each peer. In the GUI, it in your " Window->Peers". If all are outgoing, your node isn't reachable. Follow this guide to configure your network and node for inbound connections: https://bitcoin.org/en/full-node#enabling-connections |
|
|
|
If I want to run the vanitysearch program to search for private keys from 1 to a specific number and output the results, how can I do that?
You mean provide an argument to search on a specific range? If so, VanitySearch can't do that but there are forks and other tools that has the feature that you're looking for. To name two: |
|
|
|
-snip- I find it hard to believe they don't offer their customers the possibility to change their deposit address after each received transation. Most other exchanges offer this feature, correct?
I don't think most Exchanges offer such feature, I only know 2 major Exchange that do this. They only offer the ability to manually change your deposit address but it's not done automatically in every deposit. Even so, there's no complete privacy advantage on changing your Exchange deposit address since the Exchange and the authorities can easily identify all of your deposits as yours even though those are sent from/to different addresses. But against other regular users, it may offer some level privacy. |
|
|
|
You can sign that transaction if you add the " prevtxs" argument when using signrawtransactionwithwallet or signrawtransactionwithkey command. Such thing happens if the transaction is created manually. For example in signrawtransactionwithwallet, it's the json array next to the raw transaction hex string: signrawtransactionwithwallet "02000---RAW_TXN---00000" "[{\"txid\":\"TXID_OF_THE_TO_BE_SIGNED_INPUT\",\"vout\":N,\"scriptPubKey\":\"OF_THE_INPUT\",\"amount\":N}]"To get those required data: use decoderawtransaction on the time locked signed raw transaction used as input. |
|
|
|
I found this "puzzle" by a student who wondered if it is possible for the keys to be sequential, the answer to this is that it could be possible that a mathematical formula was used for this.
-snip-
That's an interesting theory and probably useful with the current bruteforcing tools. However, the creator of the puzzle already disclosed that there's no solution to the " puzzle" nor made the PrvKeys sequentially. For reference, here's his only post in the forum ( confirmed by most users): https://bitcointalk.org/index.php?topic=1306983.msg18765941#msg18765941Here's my take on what he meant by " masked with zeroes": https://bitcointalk.org/index.php?topic=1306983.msg61997068#msg61997068answer: RED.
I answered Green :D |
|
|
|
is it done using OP_RETURN or how they attach the exchange name to the address as this might be another solution for my idea?
There's no way to attach or tag names to an address in the blockchain. That must be that blockexplorer's feature that identifies Exchange addresses to be able to tag them. Those data must be stored in their own server and not in any Bitcoin nodes. BTW, Blockchain blockexplorer isn't affiliated with Bitcoin nor the blockchain of bitcoin.
If you want another idea aside from OP_RETURN, try this: - Use a "Vanity Address" with the message that you want; e.g.: 1HBDbob
However, this will be computationally expensive since the longer the message, the harder it is to create a vanity address that starts with it.
In average hardware, you can only easily include a 6-character message to the address. (7 if you're lucky)
You can make vanity address using this tool: VanitySearch (Yet another address prefix finder)
Then send bitcoins to that address and spend it as input of the transaction to the recipient of the message.
Hopefully, the recipient will notice that the sender's address has a message.
|
|
|
|
I'm scared a.f. to make a mistake there  So should i convert my privkey to WIF or it is WIF by standard? It's easy to determine if it's WIF. If it starts with '5' and consisting of 51 base58 characters, then it's WIF that's common for older wallets. If it starts with 'L' or 'K' consisting of 52 base58 characters, then it's also WIF but flagged for compressed public keys which is today's standard. If it's not, tell us how many characters it has and only the first character. I'm scared a.f. to make a mistake there When importing the private key to an offline Bitcoin Core, you're just basically copying it to that offline wallet.dat so it's quite safe. Mistakes are bad when " sweeping" a private key since it'll directly send all of the associate funds to the new wallet. |
|
|
|
I have some issues with this node. I think is a issue with mergerfs. I tested the system, filled all of the ~1 TB pool space with 100MB files and worked fine.
Started syncing from scratch, have downloaded around 20GB and occurred a irrecoverable error, because -reindex did not worked:
Why are you using -loadblock=boostrap.dat? Have you downloaded a bootstrap file containing the full blockchain? Asked this because you've mentioned that you " started from scratch". If you didn't intended to use -loadblock, I'd suggest you to just let the node sync normally by skipping that command line option. Also, try to set the default start-up block verification first and just change them to your preference later once it's stable. Specifically: checkblocks="24" which is set a bit high from the default ( 6) and checklevel="0" which skips all verification of checkblocks. If you can afford to discard the 20GB of already downloaded blocks and since -reindex didn't work, you can try to start with fresh datadir. ( backup your current datadir before doing so) |
|
|
|
-snip-
It also show that it has a total of 7 transactions in and none of them out. First transaction made in 2010 and others in 2019-2022.
When i sync bitcoin full node wallet, i can only see those 6 transactions that happened in 2019-2022, but not the one that has been in 2010
I have imported the address and re- synced the wallet. -snip-
This must have happened because your coins from 2010 are locked in P2PK ( pay-to-public-key) script which doesn't have an address. So, by importing only the address, you'll only be able to see those new coins in P2PKH ( with the address start with '1'). If you want to scan your coins from 2010 properly, import its public key. You can use Bitcoin Core in offline and online machines to create a cold-storage set-up for safety reasons: [ Offline Machine] - Open Bitcoin Core, create a New wallet with "File->Create Wallet..."
- Tick the options "Make Blank Wallet", "Descriptor Wallet", (enable encryption if you want) and create the wallet
- Open the console, make sure the wallet's name is selected in the console's "Wallet:" drop-down menu
- Type the command: getdescriptorinfo "pk(YOUR_WIF_PRIVATE_KEY)" and take note of the "checksum" which looks like this "#2ny75tj9".
Replace "YOUR_WIF_PRIVATE_KEY" with your private key, since it's offline, doing so should be relatively safe. - Type the command: importdescriptors "[{\"desc\": \"pk(YOUR_WIF_PRIVATE_KEY)#CHECKSUM\",\"timestamp\": 0\"}]"
- After that, the offline machine should now able to sign transactions that you'll create in the online machine.
- Now, to get the public key that you need to set-up the watching-only wallet in your online machine, type: listdescriptors
- Take note of the "pk" descriptor in the result, it should the the same as the one you've imported but has PubKey instead of PrvKey.
[ Online Machine] - Open Bitcoin Core, create a New wallet with "File->Create Wallet..."
- Tick the options "Disable Private Keys", "Make Blank Wallet", "Descriptor Wallet", (enable encryption if you want) and create the wallet
- Open the console, make sure the wallet's name is selected in the console's "Wallet:" drop-down menu
- Type the command: importdescriptors "[{\"desc\": \"pk(YOUR_PUBLIC_KEY)#CHECKSUM\",\"timestamp\": 0\"}]"
It's the pk descriptor from "listdescriptors" command in the steps above. - After it finished rescanning, the funds should now displayed excluding the 6 early dust transactions.
[ To Create Transactions] - Create an Unsigned transaction in the send tab of the watching-only wallet, save it in your flash drive or other methods of offline file transfer.
Note: you might need to provide a "Custom change address" if you're not sending the entire amount since you don't have one. (or just "Use available balance") - Import it to the offline machine via "File->Load PSBT from file...", Sign it, export the signed raw transaction just like what you did above.
- Import the Signed raw transaction to Watching only copy and click broadcast to send it.
For the blockexplorer result: Most blockexplorers tend to correlate transactions with P2PK outputs to its P2PKH counterparts by deriving an address from that public key. But it's not the proper way to show them, P2PK outputs should be searched in a blockexplorer by its TXID. |
|
|
|
-snip- I think an expert can break into the wallet using the data from the phone, so in gonna list it on ebay.  Without any information about the password, even an expert with good hardware for bruteforcing wallets wont be able to break into it. That's unless the password is short or consists of few simple dictionary words. Since you're already considering giving it away with the phone, at least let " experts" try to break into it. I'd recommend you this service which won't charge a fee right away ( only until the wallet is cracked): https://www.walletrecoveryservices.com/Take note that Dave wont accept the job unless you're certain that it has funds and at least know few parts of the password. is there a way to get the pin code using the USB connection?
You can copy that file for your personal backup and then list it on ebay as you intended. ( surprise for the buyer?) But it's recommended to wipe the device first since you might remember a part of the password that you've used ( not yours?). |
|
|
|
|
Show Posts
