or OP_RETURN It's easier than that. All you need is in the Pay to field, type OP_RETURN deadbeef, and in the description, type your message, and make sure the value is zero because it is an invalid transaction and your coins will be burned.
Take note that the " message" should be in hexadecimal, in which a normal text should be converted into HEX. " deafbeef" just incidentally consists of hexadecimal characters that's why it's valid. |
|
|
|
You can also use iancoleman's BIP39 tool to extract the private key based from the "master private key" (xprv) and derivation path included in the descriptor.
It seems iancoleman's BIP39 tool was last updated on 2021[1] and there's no support for BIP 86 which about deriving key P2TR. Have you tried extracting private key from P2TR address with this tool? He just need the private key(s) derived from the xprv with the correct derivation path. He don't necessarily have to derive the correct addresses with the tool, just have to type the correct path m/86'/0'/0'/0 in " BIP32" tab and the private key list below should correspond to his TapRoot receiving addresses. |
|
|
|
My question is, what's the safe version of Electrum currently, or just simply, what's the stable version of Electrum with no issues? I remember before that there was a version of Electrum where it leads to phishing or malicious activities (am I remember it right?) or something related to that.
Those versions below v3.3.3, since yours is old, it may be affected by that. Here's the release notes: https://github.com/spesmilo/electrum/blob/c049b461bbd26c04c77448a01f506ca66257cbe1/RELEASE-NOTES#L778Any newer versions doesn't have that specific vulnerability. Take note that you may not be able to connect to any server when using affected versions; if you're able to connect, the server where you're connected to may not have patched or a malicious one. Current security concerns are listed here, including the affected versions: https://github.com/spesmilo/electrum/security |
|
|
|
Dumpprivkey doesn't work for becuase it's not a legacy wallet, I can do dumpwallet and get something called a descriptor, how do I decode wif key from that if possible.
Use listdescriptors true command, find the proper descriptor for your addresses and find a way to import the descriptor to Sparrow. Since it's all TapRoot, it must be your " tr" descriptor that isn't 'internal' since that's for your change addresses. For example, you're looking for: "desc": "tr(xprv.../86'/0'/0'/0/*)#nnnnnnnn",
-snip-
"internal": false, You can also use iancoleman's BIP39 tool to extract the private key based from the " master private key" ( xprv) and derivation path included in the descriptor. After exporting that from Bitcoin Core, it's altcoin territory and you might need to create a new topic in Altcoin Boards on how to spend it. |
|
|
|
C:\Program Files\Bitcoin\daemon>bitcoin-wallet --wallet="C:\Users\My Username\AppData\Roaming\Bitcoin\wallets\My Wallet\wallet.dat" salvage
Failed to load database path 'C:\Users\My Username\AppData\Roaming\Bitcoin\wallets\My Wallet\wallet.dat'. Data is not in recognised format.
Am I still doing something wrong?
This time, bitcoin-wallet tool ran successfully but since there's an error, it can't salvage your wallet file since the keys are unrecoverable. That usually happen if the deleted data that you've recovered ( the wallet.dat file) were already immensely overwritten by new files. So your option now is to use other wallet/private key recovery tools. One option is to use pywallet's --recover option to check if there are data similar to private keys or intact private keys recoverable from your drive/wallet file. But as a heads-up, it's not as " easy" as bitcoin-wallet tool to setup and use, read this topic for some info about the tool and command: https://bitcointalk.org/index.php?topic=5408068.msg60653031#msg60653031 |
|
|
|
The address I'm looking for is a P2PKH (starts with "1....."). ***MATCHING SEED FOUND***, Matched on Address at derivation path: m/84'/0'/0'/0/0
Search Complete
Try to restore it using these options: - Restore your BIP39 seed with "BIP39 seed" option ticked.
- Select the script type "legacy (p2pkh)" but change the derivation path below from m/44h/0h/0h into m/84h/0h/0h
- Finish the rest of the steps.
Electrum will derive both receiving addresses m/84'/0'/0'/0/0-19 and change addresses m/84'/0'/0'/1/0-9 with it. |
|
|
|
I think this is where it went wrong: So the first thing you'll need to do is convert from base58 to binary and then throw away the first byte (this is the version) and the last 4 bytes (these are the checksum). What you'll have left is a binary representation of the private key. This part is specific to uncompressed private keys which starts with " 5", yet the rest of the steps are for compressed address. To properly decode a compressed WIF private key, you'll also have to remove the 0x01 compressed flag concatenated before the checksum. So I'm thinking that your code might have used an invalid private key with extra byte and somehow managed to compute the public key without an error. So when i created a script with the above methods with the same private key i get the correct address but the same private key shows different addresses on online converters, bitaddress etc... I am not a programmer or cryptographer its all very confusing to me
-snip- So what i did was i took a script from chatgpt yesterday to convert compressed wif to bitcoin coin address with a method i saw in one of the topics it gives the correct address. Yes i remember it saving for the correct addresses.
Last time I asked ChatGPT to make a python script that requires specific Bitcoin Core RPC commands, I ended up spending 30minutes teaching it why it wont work. ( about 3 iterations) So it's not recommended to use it unless you can correct what it provided. So the script that you've created is based from ChatGPT's AI-generated code? Care to share it to us so we can check which part is faulty? ( either use [code][/code] tags or pastebin website) |
|
|
|
What i have from all these ?!
None of the above are related to owning Bitcoins, you just need private keys. Those part of the Bitcoin whitepaper are about " double-spend", " Bitcoin mining" and how the network operates. As mentioned above ----->>> Signatures x509 certificates - Tokens - time stamp - hash file - private keys
Probably a file which is part of your operating system, web server or from a browser. Your Wikipedia link even shows that it's not related to Bitcoin. I think you're looking at the wrong file again. |
|
|
|
-snip-
Why is there a difference in the address created on Electrum Mobile and the one on the Windows version? I mean, when trying to import the seed that was obtained when making the mobile version to the windows version, in option, I have selected BIP39. Is it because I chose Native SegWit, while the mobile type is p2wpkh? This is for the standard wallet type. To be clear, have you selected " BIP39 seed" option in Windows version and not in the Mobile version? It'll be different because the derivation from the 'seed phrase' to 'seed' is different in BIP39 and Electrum's native seed. Specially the default passphrase which is " mnemonic" for BIP39 seed and " electrum" for electrum seed. Anyways, since it's not related to the topic, it's best to create a new one for further concerns/questions. |
|
|
|
-snip- not really a computer person is there a good/simple tutorial i can follow?
It's pretty straightforward: First, download Armory from https://btcarmory.com/Install it on an offline machine. Then, here are the steps to restore your paper backup: - Launch Armory and click "Import or Restore Wallet" (right-hand side)
- Select "Single-Sheet Backup (printed)", click continue
- Since it's from 2012, I take that it has a "Chain Code" and doesn't indicate the backup version, right?
If so, you can try to restore it with the option "Version 1.35 (4 lines)". Then type the "Root Key" and "Chain Code" below. - Click "Restore Wallet" and finish the rest of the steps.
Then to extract the private keys, refer to the link in the reply above. But it's safer to set-up Electrum with your private keys on an offline machine and restore only the addresses on an online machine as watching-only wallet. Then, here's how to spend from that set-up: https://electrum.readthedocs.io/en/latest/coldstorage.html#create-an-unsigned-transaction ( has outdated images but should be similar to the latest) |
|
|
|
|
Which lightning client/wallet are you using?
It could mean that you or users are sending requests in quick succession but it could be anything else depending on the client.
|
|
|
|
Explain to me like a baby.
A SegWit transaction has " Witness" data in it, those data will only be counted as 1 " Weight Units" ( WU) per Byte whilst non-witness data counts as 4WU per Byte. With that Weight Units, you can get the transaction's virtual size ( vByte) by dividing it by 4. ( I hope babies know division) But the size of the transaction ( in Bytes) is the actual size of the transaction is your disk. Here's the " Detailed Example" of which part of a SegWit transaction are Witness data: https://en.bitcoin.it/wiki/Weight_units#Detailed_exampleThe units " sat/vByte" and " sat/Byte" are the fee rate based from those units above: absolute fee divided by vByte or Byte. Take note that the majority of Miners are using the virtual size when prioritizing transactions. |
|
|
|
Ok, I got to the point of the list below & clicked on the path to my wallet folder highlight and copy it (Ctrl+C) I then pasted the command in command prompt: salvage --wallet="<CTRL+V>\wallet.dat" salvage <Enter>
'salvage' is not a recognised as an internal or external command, operable program or batch file.
My bad ( I typed salvage instead of bitcoin-wallet), the command should be: bitcoin-wallet --wallet="<CTRL+V>\wallet.dat" salvage <Enter>But my screenshot shows the correct command anyways:  |
|
|
|
Hi, this is where I am lost, I cannot seem to locate the 'bin' file in the install directory in Program Files on C:
Is the 'bin' file created after making a new wallet?, currently I have no wallets loaded.
In C:Program Files/Bitcoin I have:
deamon folder
share folder
bitcoin.conf
bitcoin.qt
COPYING
readme
uninstall
In the daemon folder I have:
bitcoin-cli
bitcoind
bitcoin-tx
bitcoin-wallet
test_bitcoin
Thanks.
I've mentioned twice already, there's no " bin file". It's the folder where bitcoin-wallet is located and the directory where you should use " cd" ( change directory) in command prompt. Please check my previous replies in this thread since I've already addressed most of these concerns and separate whanau's replies with mine. To answer this shortly: it's your old installation since there's a " daemon" folder, which is equivalent to the " bin" folder of the new version. And in your reply, there's a " bitcoin-wallet" file inside it; which is what you need to perform salvage. ( if the version is too old, it may not contain the salvage command) The workflow is this simple ( without repeating the already given instructions): - Find Bitcoin Core's installation directory (where you installed Bitcoin Core), not the 'bitcoin' data directory in your 'appdata/roaming' folder.
- Open cmd and cd to the directory above. The trailing "C:\Users\YOUR_USERNAME>" in command prompt will change into that directory after entering the cd command.
- Use the provided salvage command.
- Load the salvaged wallet to Bitcoin Core.
Take note that salvage's success still depends if the keys/master key in your wallet.dat are still intact. |
|
|
|
I have just checked & Bitcoin Core is still the same, I have looked in open wallet & it's blank/greyed out, no wallets are available.
A sole 'wallet.dat' file inside wallets folder should be automatically loaded as " default wallet" once Bitcoin Core is started. (update note: this is not applicable to the later versions.)Since it's in the 'wallets' folder, it should also be available in the Open wallet menu. So it seems like there's an issue with your restored wallet.dat file. Can you try to load it via " File->Restore..."? Close Bitcoin Core, move your wallet.dat file somewhere else, Open Bitcoin Core and use that restore menu then in the file explorer that popped-up, browse to the location of the wallet.dat file and select it. If it loaded, a new wallet file will be created with the same keys from your wallet file; if not, it's corrupted and you should use salvage as I've instructed. |
|
|
|
now if your .dat file is not in the correct format what to do is:
* open the bitcoin core wallet
* press Help in the menu
* the debug window is finished
* next is wallet repair
* When you click on wallet repair, select the .dat file that has been recovered
* then click the repair button
There's no clikable " repair" option in Bitcoin core; also, " debug window" is the " console" of the old versions. Where did you get this guide? If it wasn't cut in the original installation, yes it can still be used in a pruned blockchain wallet it just needs to scan the blockchain for transactions that happened before the wallet was lost.
He wouldn't be sure if his unpruned blocks are enough to scan his wallet.dat file, In situations like this, having a full blockchain is worth to have since he'll be rescanning restored wallet.dat files. It's also corrupted so it may have to be rescanned from scratch after a salvage attempt. |
|
|
|
Description of Problem:
I get a message "gpg: BAD signature from *insert dev*" when trying to verify the PGP signatures of for my bitcoin core installation.exe. Is this a clear sign that my software has been tampered with? Or is there another explanation?
You're supposed to verify " SHA256SUMS" file with " SHA256SUMS.asc" signature file. So command should be: gpg --verify SHA256SUMS.asc SHA256SUMS Then after verifying that " SHA256SUMS" file is legit, open it as text, then find and take note of the line: 9485e4b52ed6cebfe474ab4d7d0c1be6d0bb879ba7246a8239326b2230a77eb1 bitcoin-22.0-win64.zipGet your downloaded " bitcoin-22.0-win64.zip" file's sha256 hash and see if it matched with the sha256 sum in the file. For example, using this PowerShell tool: learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/get-filehash?Windows Power Shell command and result ( with matching SHA256 hash): Get-FileHash Desktop/bitcoin-22.0-win64.zip | Format-List
Algorithm : SHA256
Hash : 9485E4B52ED6CEBFE474AB4D7D0C1BE6D0BB879BA7246A8239326B2230A77EB1
Path : C:\Users\<username>\Desktop\bitcoin-22.0-win64.zip |
|
|
|
Command prompt as stated above in Windows: is not recognized as an internal or external command,
operable program or batch file. It means that you've entered an invalid command in Command Prompt or tried to launch a non-existing program. Usually caused by trying to launch something while still using the default directory " C:\Users\<username>". In my instructions, use change directory command " cd" to the correct folder where bitcoin-wallet tool is located, in that case, follow the step with the " cd" command. Command as stated above in the Bitcoin QT: Method not found (code -32601)
It means that the command that you've used with Bitcoin-qt isn't correct or not-existing. -salvagewallet was removed in bitcoin-qt and moved to bitcoin-wallet tool; I've also instructed to use bitcoin-wallet tool to salvage so I can't find any reason why you've used bitcoin-qt with the command. There is still no 'bin' file. There's no " bin" file and I haven't stated to find any 'bin' file. You're looking for " bitcoin-wallet.exe" in 'bin' folder, but since you're using the old version, it's in the 'daemon' folder.
Update: I have a fresh installation of Windows 10, laatest BIOS & drivers, all diagnostics check out fine & Bitcoin Core 24.0.1 is apporoximately 11 hours from completion on an unpruned blockchain on C:
Good, then use that latest version instead of the old installation; preferably after Bitcoin Core is synced since your system must have been freezing while its syncing. Since it's quite buried in the first page, I'll quote my post here for reference: ( plus additional comments since it looks like you're new in using commands) If the recovered file is corrupted, try to use salvage command of Bitcoin Core's bitcoin-wallet tool: - Go to Bitcoin Core's install directory, open "bin" folder;
Since you're on Windows, it's in "C:\Program Files\Bitcoin\bin" folder by default.
-> that is only the default, if you've installed Bitcoin Core in different directory, browse to that directory instead.
And inside that folder, there should be a bitcoin-wallet file inside it which is the tool that you're going to use. - Open your command prompt and cd to that directory, enter: cd "C:\Program Files\Bitcoin\bin"
-> this is important since this will change command prompt's working directory where bitcoin-wallet.exe tool is located, in this case, inside "bin" folder.
Of course, as stated above, if Bitcoin Core is installed to a different directory, cd to its 'bin' folder instead. - Then to use salvage command with bitcoin-wallet tool: bitcoin-wallet --wallet="full path to your wallet.dat" salvage
For example: if your corrupted wallet.dat is saved in "D:\testdir\wallet.dat", it should be --wallet="D:\testdir\wallet.dat"
-> To create the example, create a temporary folder in "D:", name it "testdir" and paste your corrupted wallet.dat in it.
That's only for the example, you can use any folder that you want and make sure to enter its path in "--wallet=<path>" arg. - Command should finish without any response, otherwise, there's an error.
- If it finished without errors, load the wallet.dat to Bitcoin Core and see if it's now fixed.
-> If there's no error, go to your "testdir" where the corrupted wallet.dat is, if salvage command is successful, there should be a backup file there named "wallet.dat.nnnnnnn.bak"
which is the original corrupted wallet.dat.
In that case, open Bitcoin Core and use the menu: "File->Restore Wallet", browse to that "testdir" directory and open wallet.dat.
Bitcoin Core will try to restore that salvaged wallet, and if there's no issue, it should load and rescan.
|
|
|
|
-snip-
What about how long usually it takes to mempool gonna drop transactions with low fees like this The default in Bitcoin Core is 2 weeks but it's configurable so it may take more time than that for the whole network to forget your transaction. Coinbase may also have a system that re-broadcasts transactions the moment it's dropped from their node's mempool. But since they are custodial and closed-source, there's no way of confirming that. |
|
|
|
|
Show Posts
