Bitcoin Forum
June 23, 2024, 05:07:10 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 514 »
1161  Bitcoin / Bitcoin Technical Support / Re: Damaged .dat file... Am I screwed ? on: March 02, 2021, 09:01:28 PM
How does the address generation works ? Can't this wallet help me to regenerate the key  Huh
Private Key generation in the older versions was completely random... none of the private keys were "linked" in any way. There is 0% chance of being able to regenerate the key. Undecided This is one of the reasons why Bitcoin Core moved to "Hierarchical Deterministic" (aka "HD") wallets.

The newer "HD" versions of Bitcoin Core use a "seed"... They are able to recreate all generated keys from the seed. However, the seed is not shown to the end user and cannot be easily extracted. The method to backup is still maintaining backup copies of wallet.dat... the HD functionality just means that you don't need necessarily need to make new backups when new keys are generated (ie. when the keypool is exhausted and refreshed).
1162  Bitcoin / Bitcoin Wallet for Android / Re: Old android backup private key don’t import all addresses from that account on: March 02, 2021, 08:44:51 PM
But even if I did import that address, the backup is dated after the screenshot
I meant as a "watching only" address... rather than importing the private key. But like I said, I don't know if this was ever possible... There doesn't appear to be any "import" functionality now.

Are the datetime stamps of the backup file and the screenshot in the same format? Is it possible that the month/day are being transposed on the screenshot? Huh I know the wallet backup is always YYYY-MM-DD...


And just to clarify... you have 4 private keys in the decrypted backup file, but the screenshot shows 5 addresses?
1163  Bitcoin / Electrum / Re: How to transfer BTC from papper wallet to native segwit ledger on: March 02, 2021, 09:54:41 AM
1
 I want transfer BTC from paper wallet to Ledger native segwit.
how to process in Electrum wallet?
I want just sent transaction from paper wallet to segwit wallet.
In Electrum:

- Create a "new" wallet (file -> New/Restore)
- Select "Import Bitcoin addresses or private keys"
- Enter you private key from the paper wallet
- Add a password, if desired (recommended!)
- After wallet is created, click "Send", then enter the details of the transaction you're trying to create (Address from Ledger Native SegWit wallet and amount etc)


2
I want to track balance on my paper wallet is this possible ?
I want to be sure that when I`m import private keys to Electrum Wallet the BTC will be not transferred to new wallet in electrum but will be stay on paper wallet.
If you just want to track the balance on the paper (and don't want to spend)... you can create a "watching only" wallet... Same as above, but just enter the Paper Wallet address (instead of the private key). This will create a watching only wallet in Electrum that shows the full paper wallet history, but cannot spend.

If you want to track and be able to spend, then just do the above with the private key as described... this will create a single address, imported wallet in Electrum with just your paper wallet private key and address. If you create any transactions, it will not create any "change" addresses... if you click "receive" it will not create any new "receive" addresses. It will only ever have your paper wallet address (unless you import more private keys/addresses).


NOTE: by entering your private key from your paper wallet into Electrum, you really should consider the paper wallet "compromised"... as the private key has been used on an "online" computer. I would recommend that you move all the funds to either the Ledger or to a new paper wallet (that was generated offline and where the private key has not been "exposed".)
1164  Bitcoin / Bitcoin Wallet for Android / Re: Old android backup private key don’t import all addresses from that account on: March 02, 2021, 05:28:02 AM
Assuming that:
- The backup was indeed taken after the screenshot
- The missing address had not been "imported" as watching only (not even sure this is/was ever possible with 'Bitcoin Wallet for Android' Huh)
- No modifications had been made to the wallet (ie. it had not been recovered from another earlier backup after the screenshot etc)

Then, theoretically, yes that private key should have been in the backup file.

I would have said that you should log an issue on the github, but I think you already did.? Huh Did you use the "report issue" feature in the wallet? It is probably the easiest way to contact the wallet devs...
1165  Bitcoin / Electrum / Re: I Don't understand on: March 02, 2021, 04:03:27 AM
After proceeding with the purchase, My wallet is now in debt? "[-0.000109 unconfirmed]".
You're not in "debt"... that is just showing the amount that will (eventually) be debited from your wallet when the transaction is finally confirmed. Basically, it is showing the total amount that has been spent but not yet confirmed.


Quote
I've never used electrum before, so im very confused. It now seems that i have no BTC in my wallet nor did i get what i was attempting to purchase. Anyone up to help??
When you say you've never used Electrum before... how exactly did you get the BTC into the wallet in the first place? Did you import a seed or private keys from another wallet to see your balance etc? Huh How was that $10 worth of BTC received? Did you receive it in one payment, or did you receive it over multiple payments? Huh

I'm just surprised that your fee paid was so high 0.00002300 BTC when you choose "Static" and set it as low as it would go... "Static" should have enabled you to send with 1 sat/vbyte... so if you did that, and the fee was still 2300 sats... it meant that your transaction's "data size" was ~2300 vbytes... which is quite large! Shocked Shocked The usual reason for this is that you have received a lot of small amounts over a period of time (from mining, faucets, micropayment services etc)... which can cause issues as the total fee paid on a transaction is a function of "data size" (and not the amount of BTC being transacted).

If you double click the transaction in the "History" tab in Electrum it will show you the transaction details, how many "inputs" are shown? what is the "size" that is displayed (in bytes)? what is the rate shown for the fee (in sat/byte)?
1166  Bitcoin / Bitcoin Technical Support / Re: pywallet install help on: March 02, 2021, 12:07:56 AM
just ignore the __db.001 files... they aren't really import in the grand scheme of things... but given they are in your "Downloads" folder... as well as in the "Pywallet" folder, suggests that you might not be in the correct location when attempting to run the scripts...

Just so we're on the same page, and can create the correct commands, can you please list the:

1. The full path (C:\blah\blah\foo\downloads\pywallet etc) of where the pywallet.py file is
2. The full path of where the recovered wallet.dat's are
3. The full names of the recovered wallet.dat files.
1167  Bitcoin / Bitcoin Technical Support / Re: Just was robbed on: March 02, 2021, 12:04:16 AM
I was using Bitcoin Core(non password protected) and MyCrypto was password protected.
Then all they required was a copy of your wallet.dat file to get access to your Bitcoins... Without a password on it, anyone with a copy of your wallet.dat would be able to access the private keys and create transactions sending the bitcoins wherever they wanted.

Do you store a backup of your wallet.dat on a cloud-based backup server like OneDrive, Google Drive, DropBox etc? Huh Or perhaps you sent yourself a copy of your wallet.dat to your email as a backup? Huh


Interestingly... the BTC address (12P5MtCHoyTJdJitAWSDkeb5fYHSQj7X3X) that the bulk of your coins got sent to, is tweeted by a "Bens Bitcoin Consulting LLC"... seems they also had funds stolen from them that went to the same address (but from Exodus wallet):
https://twitter.com/ben92994350/status/1288107762048577538


I already changed, my passwords and created new wallet.

And transferred cents that was left there in my wallet to new wallets.
If you never stored your wallet.dat backup online, then my guess would be malware of some description that has leaked your wallet.dat and/or your MyCrypto login credentials. I would consider the entire machine compromised... I would not be surprised if the thieves already have the details for your new wallets.

I would recommend that you format the PC and reinstall the OS.

If you stored your wallet.dat on a cloud server of some sort, then it's likely that your account on the cloud server was compromised. You'll need to change ALL your passwords.
1168  Bitcoin / Bitcoin Wallet for Android / Re: Old android backup private key don’t import all addresses from that account on: March 01, 2021, 11:46:18 PM
If the keys are not showing up in the backup file when it is decrypted, then the key was not included in the backup (for whatever reason) and there will be no way to recover it given what you currently have.

The old key backup format was exactly that... just a list of private keys in an encrypted text file.

Curiously, according to the recovery docs (https://github.com/bitcoin-wallet/bitcoin-wallet/blob/master/wallet/README.recover.md)... the protobuf backup file format was introduced in 2014. And you say your 2017 backup was in Base58 format? Huh
If it prints "org.bitcoin.production", you got the right password and the backup file uses the bitcoinj protobuf format. This backup format was introduced in v3.47 (May 2014). Skip to RECOVERING FROM PROTOBUF WALLET FORMAT.
openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-09-28 -out decrypted -md md5

What is the date of your screenshot? Huh
1169  Bitcoin / Bitcoin Technical Support / Re: Complicated help with crossed-client key compression. on: March 01, 2021, 10:09:54 PM
As I mentioned in your other thread regarding this... the private keys don't get compressed... the public keys do. As such, if you can use the --dumpwallet functionality of PyWallet, you should be able to get the raw hex values for the private keys from your wallet.dat relatively easily.

Once you have the raw hex private keys, there are lots of tools available to convert those into WIF keys that can be easily imported by most wallets. For instance, you can input the hex private keys into something like the "wallet details" tab on https://www.bitaddress.org/ (download and run offline) to get both the uncompressed and compressed addresses and WIF keys... or there are multiple python scripts/tools that should be able to do the same.

Alternatively, you can probably do the reverse... and use dumpwallet in Bitcoin Core and get the "compressed" WIF keys, put those into https://www.bitaddress.org/ and you will be able to see the "uncompressed" address and WIF key (and raw hex as well).

There are certainly tools out there that will take a WIF key, decode it from Base58check into the raw bytes, then drop the trailing checksum bytes and the leading "80" byte and give you the raw HEX private key... which you can then use to go back the other way.

In fact, here is a Python3 script that I just wrote that does exactly that... it will take in a file of "compressed" WIF format keys... and outputs a file of "uncompressed" WIF format keys:
Code: (https://keybase.pub/hcp/compWIF_to_uncompWIF.py)
import os
import ecdsa
import hashlib
import base58
import binascii
import argparse

def decode_WIF(comp_wif):

    #WIF to bytes
    decoded_bytes = base58.b58decode(comp_wif)
    
    #bytes to string
    decoded_string = binascii.hexlify(decoded_bytes)
    
    #remove all the extra bits
    raw_hex = decoded_string[2:-10] #-10 because need to drop the trailing 01 byte indicating "compressed" priv key as well as checksum
    
    return raw_hex


def encode_WIF(hex_key):

    #add '80' byte at start
    extended_key = b'80' + hex_key
    
    #calc checksum
    first_sha256 = hashlib.sha256(binascii.unhexlify(extended_key)).hexdigest()
    second_sha256 = hashlib.sha256(binascii.unhexlify(first_sha256)).hexdigest()
    checksum = second_sha256[:8].encode('utf-8')
    
    #append checksum
    final_key = extended_key + checksum
    
    #convert to WIF
    uncompressed_WIF = base58.b58encode(binascii.unhexlify(final_key))
    
    return uncompressed_WIF

def main():

    parser = argparse.ArgumentParser(
        description='Convert file of compressed WIF\'s to uncompressed WIF\'s.',
        formatter_class=argparse.ArgumentDefaultsHelpFormatter)
    parser.add_argument('infile', default="compressed_wif_keys.txt", nargs='?', help='File to read compressed WIF keys from')
    parser.add_argument('outfile', default="uncompressed_wif_keys.txt", nargs='?', help='File to write uncompressed WIF keys to')
    args = parser.parse_args()

    if (os.path.exists(args.infile)):

        f = open(args.infile, "r")
        out = open(args.outfile, "w")
        for x in f:
            hex_key = decode_WIF(x)
            uncompressed_WIF = encode_WIF(hex_key)
            out.write(uncompressed_WIF.decode('utf-8'))
            out.write("\n")

        f.close()
        out.close()
    else:
        print("ERROR: File not found: " + args.infile)
        print("\n")
        print(parser.format_help())

if __name__ == "__main__":
    main()
link: https://keybase.pub/hcp/compWIF_to_uncompWIF.py


Then, if you create a text file called "compressed_wif_keys.txt" in the same location as the .py file, and copy paste the following compressed WIFs into it, and then run the script without any arguments:
Code: (https://keybase.pub/hcp/compressed_WIF_keys.txt)
L5cg8tbrDAFX6obhWSMktPrwDTcBX8dQz1AAmhRqidft81vFAoyX
L53ygZ65TrHFVxMATRurYb43Cgp13cvV6XbkFPegYN65GFUH1x8p
KzPTbNXTxrKYoSuJPKiRpymdDRt7HUoCcMaHAPDJhU49YmLrAZ69
L1U6eG1YM6oV8jQVm4PFhQ5cU459XHBWeS2E5Enqq6RfLDGxYnqF
KyPeSN7498myZbsXnnXpQXvxmLavRnVctewv9MoRH6Zp8GV2tqjL
L5WvodSV8qK5fXrrqhLiKXEMd1eYaaSjk5FjwxCdgm44VcGWH91L
L3pPYUHPPJ8tgjk75uUMzfstxYKvArjH8FFrkPbhuSKeyqBaNCpp
KzT21SoRLe34jM9cQizNzmbknFdBfqc3vxw9diBkMHJFF3w9i9Rr
L43FTBxA7ddVnxXnRxdi2nw3BM4PVnpCk1fP7z7aU1Zofd1XdqM7
L2tjSeHgNZvJp8nDoBnsyJ1T1tGyJmDSq2Nqryep4kLKuNNsMjDW
link: https://keybase.pub/hcp/compressed_WIF_keys.txt


It should produce the following "uncompressed_wif_keys.txt" output file:
Code: ("uncompressed_wif_keys.txt")
5KicbsCyTmgza2wzD7CVyWCKB5DW7pwvTxmfvB4pHgaH7c17BYk
5KbCwGszeoWWZqnoYpLE3Ayso9ZrQFUyfQhVq7wkrFJ1WooMj2P
5JXv9hDnz4UK5dgVQdsAhn2xL8T5bYg1pS41VQcQwwAKhnpHFF8
5Jn7GEphdj6YkSU5FWmTtkHuScb22RWZzsXdwtA2YjvAbHujCmF
5JJpT8xJ2Pc7UKmypXhy44qUb4Xo6AQFUZcYyisPii8tTcKdVA6
5KhK5g4xmNNKGyqTFCrnABUVgsu1MkNh3WWd1fngaUerH6awWUh
5KJzDZv6yi3EyahaYvaPRr8uZ4vgEZZguPiRsACVJKRco258WUy
5JYiv7kbWpp96WwWmoDYidqf1jjdrafkiE8HTSeKtGUUF9wRZts
5KMuDH5Ljjjhxj2zREWcaV5YJkWmX5weYwyjAjr4xWaiPRjvsUE
5K6q8d691ot3gE6G8kE7Zh6zYvJfavyHj9U9offURs9TVHWiNxX



Also strange. 1 address is coming up different 1 digit shorter in all the dumps from BTC form.

1F2f3FubHQ7v8cvcSf81xkj4rQC4URKhF - 34 digits
18w2pc9PFUfmCaR4JdKaDery3Bentp6CYy - 35 all the rest
1LJAdG24ajwgBhitKJnFfyTiSF9NaA45Jy - 35 all the rest
That's not really unusual... a Bitcoin "legacy" address (aka the "1"-type addresses) can be anywhere from 26 to 34 characters long. Most are generally 33 or 34 characters in length. For the record, the examples you listed are actually 33, 34 and 34 characters Wink
1170  Bitcoin / Bitcoin Technical Support / Re: pywallet install help on: March 01, 2021, 09:44:55 PM
I now get ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.
In which case it sounds like the path to the wallet file might be incorrect... where exactly are the recovered_wallet.dat files located? and what are their exact names? Huh
1171  Bitcoin / Armory / Re: armory newb on: March 01, 2021, 09:38:48 PM
I have 32gb of ram and its ssd, ok database cashe increased to 16gb, think this around the max it wont let me do 17000. Much better progress now 2.5% ph, was 0.3, hopefully itll increase later in the day once people finnish work.
If you mean because then there will be more network bandwidth, the speed of the sync isn't really dependent on the network bandwidth much at all. Granted, it still has to download 350+ gigs of data, but ny "broadband" connection should not bottleneck the syncing process unless it is being severely throttled/rate limited... The main bottlenecks are really in the disk I/O and the CPU processing.

The disk I/O issue is somewhat countered by using SSD instead of HDD (massive uplift in read/write speeds) and by increasing the dbcache value (reduces overall reads/writes from and to the disk and keeps more data in RAM etc)... and, obviously, due to the sheer amount of number crunching involved, a poor CPU will struggle... but given your rig was a relatively new machine with 32gigs RAM, I would be very surprised if it wasn't relatively "powerful".
1172  Bitcoin / Electrum / Re: Lost Bitcoines In A Transaction to Coinbase on: March 01, 2021, 09:31:19 PM
It is entirely possible that the address you used for Coinbase back in 2016 was part of one wallet "cluster", was consolidated with other deposits to this cluster, and was used to process withdrawals from this cluster, while OP used an address in another "cluster", and the two clusters never mixed.
Yes, re-reading my post, I realise that I perhaps should have made it clear that just because it isn't currently "linked" to Coinbase... does not mean that it isn't a Coinbase wallet... it just means that there is currently no "easy" way to say "This is a Coinbase address/wallet".


...contact Coinbase, state they made a deposit to the address 1Q6Boa9VQxxcCCNDKK1dennXSud1m5ALAc, and ask why it was never credited to their account.
^^^ This
1173  Alternate cryptocurrencies / Altcoin Discussion / Re: Windows Cross-Compiling of a Bitcoin 0.21 Fork on: March 01, 2021, 09:22:05 PM
Unless you have some way of bundling a bitcoin.conf file with your installer... then it is something that needs to be manually created. Bitcoin Core doesn't create a bitcoin.conf when it is installed.

I created my own "altcoin" (basically Bitcoin code with some minor edits) a while back when I was trying to help BlackHatCoiner when they were attempting to do the same... Now it seems that BlackHatCoiner has created a nice little tutorial with the basics covered: https://bitcointalk.org/index.php?topic=5309100.msg56085433#msg56085433

As you can see, he mentions the fixed IP addresses in chainparams.cpp and the vSeeds/vFixedSeeds etc... So, modification of those in chainparams.cpp and replacing the values in chainparamsseed.cpp should allow you to create your own "fixed" seeds without requiring addnode entries in bitcoin.conf file.

Note: that if you simply delete the lines and use vFixedSeeds.clear() as per his tutorial, you won't have any seeds and will need to use addnode
1174  Bitcoin / Electrum / Re: Changing the Description of an Incoming Payment in the Receive tab of Electrum on: March 01, 2021, 08:56:50 PM
1. I found that a way to add the description is to open the wallet's .json file and fine the Message: "" field and add the description I wanted. I am assuming this json file is what Electrum uses to load values in the UI and as long as I don't go around changing things like the structure or fields I don't know about then I should be fine. Is there anything wrong with me doing this?
As you can see the json contents of your wallet file, I assume you either do not have a password set, or you did not check the "Encrypt wallet file" option when setting the password for your wallet (so only the seed/private keys are encrypted within the json file and everything else is plaintext).

Note that if you ever decide you want to use the "Encrypt wallet file" option, you will not be able to manually edit the json (wallet) file directly... as, obviously, the file will be fully encrypted Tongue
1175  Bitcoin / Electrum / Re: Lost Bitcoines In A Transaction to Coinbase on: March 01, 2021, 05:09:20 AM
Unfortunately, the address appears to be from an "unknown" service of some description: https://www.walletexplorer.com/wallet/00052e20f14c2c57?from_address=1Q6Boa9VQxxcCCNDKK1dennXSud1m5ALAc

As it is not linked to any wallets of the "big players", it may be quite difficult to identify exactly who is the owner Undecided
1176  Bitcoin / Wallet software / Re: base6 to base16 script beside bitaddress.org ? on: March 01, 2021, 12:45:37 AM
There is a simple bash script available here: https://github.com/swansontec/dice2key

It's not web-based, but it is very simple! Wink


They have a full writeup on creating keys from dice here: https://www.swansontec.com/bitcoin-dice.html
1177  Bitcoin / Armory / Re: Armory Not Scanning Transactions (Mac 10.15.7, Armory 0.96.5) on: March 01, 2021, 12:31:01 AM
Sorry, but I'll have to defer to @goatpig and hope that he can shed some light on what is happening at this point... I'm not 100% familiar with the very inner workings of Armory as I have not done a very in-depth inspection of the code, so I'm not exactly sure what Armory is attempting to do when the "Starting address registration process" debug is output. Undecided

1178  Bitcoin / Wallet software / Re: I have a multibit wallet and I don't see any funds on: March 01, 2021, 12:04:14 AM
Any suggestions?  The address on the paper wallet says there's just under two Bitcoins received and remaining at that address.
What do you want to do with the Bitcoin? Keep hold of them or transfer to an Exchange to convert to fiat?

If you're wanting to hold them, then it might be worth just leaving them exactly where they are... they haven't been "taken" in all this time, so the private key is likely still "safe". Then you can figure out if you want to move them to a different wallet or whatever later.

If you're wanting to convert them, you would need to import the private key into a wallet like Electrum, and then create a transaction to send the coins from there to the exchange of your choice.


I've now managed to look at my old computer and the wallet was Multibit 0.5.14 .  There's an address there which I've searched for using the links posted above and the address comes up as never having received or spent any Bitcoins. Huh  I'm totally confused.  
It was possible to create multiple wallets in MultiBit Classic... so you might want to use the "open wallet" menu in Multibit and see if there are other "xxxxxx.wallet" files... also check how many "xxxxx-data" folders are shown in the MultiBit data directory (multibit should default to this directory when you use the "open wallet" menu option)... each wallet should have it's own "xxxxx-data" folder.
1179  Bitcoin / Armory / Re: ArmoryDB always parsing blocks again on: February 28, 2021, 11:55:49 PM
I am done. I give up and will use Electrum.
Fair enough... I have a small guide for extracting the private keys from Armory here: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691

Once you have the PrivBase58 keys, you should be able to copy/paste them into Electrum (select the "Import Bitcoin Addresses or private keys" option when creating a new wallet) . NOTE: do not include the 'PrivBase58' part... you just want the text starting with a "5" (or "K" or "L'")

1180  Bitcoin / Armory / Re: armory newb on: February 28, 2021, 11:51:43 PM
Yes, that should be the correct setup... prune box unchecked and you should see the Bitcoin Core block directory filling up. In Bitcoin Core, in "Window -> Information" menu option, check the "Blocksdir" value and make sure that the drive that that folder is on actually has ~350+ Gigs worth of free disk storage to hold it all! Wink
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 514 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!