|
There has been attempts in the past to sell them, some people bought and some people made money on coins that can disappear tomorrow
Even though faucets only sends hundredths of a coins, testing a service with 1000 satoshis or 1000000000 satoshis doesn't change anything
But you're right, free market, so yeah people can choose to pay for what they want, they can even send coins to 1111111111111111111114oLvT2
|
|
|
|
|
Do you have the private key of the address?
If so then it's easy, just import it in a wallet like Electrum
|
|
|
|
I pushed a new version that support BIP32 key derivation with ranges in path (red) $ python pywallet.py --dump_bip32 xprv9s21ZrQH143K31xYSDQpPDxsXRTUcvj2iNHm5NUtrGiGG5e2DtALGdso3pGz6ssrdK4PFmM8NSp SBHNqPqm55Qn3LqFtT2emdEXVYsCzC2U m/0/2147483647H/0-2/2147483646H/1-3
m/0/2147483647'/0/2147483646'/1: Kwjbf2aNxQn9Z5kW3FTjWoPVcVVxcT5aAZ6iv2TNT7hxx2YncHYU
m/0/2147483647'/0/2147483646'/2: KzDrZyWjeXR9X1EsccdiikgwUCfJXrS3b4p9hoH8QxzwzxA7peSK
m/0/2147483647'/0/2147483646'/3: L12hzsCFyhkJf7jnnZRMQJyw1ifKi6ZhkGJXD9v54sErS4HjzbdU
m/0/2147483647'/1/2147483646'/1: L1YELgqFKLb3fHbjtBf8n733nbCcFKFHdoWvrHmDBY4JTuXk9Qi5
m/0/2147483647'/1/2147483646'/2: L3WAYNAZPxx1fr7KCz7GN9nD5qMBnNiqEJNJMU1z9MMaannAt4aK
m/0/2147483647'/1/2147483646'/3: L31UHxF3kqYjzE3ucNWCapFYt12oynYeoFAYGUyKGW8WxLkLfxtw
m/0/2147483647'/2/2147483646'/1: L3f4m5XVRTgryT2cMzhzhzQeWZErNSPww6RuvnxtpfzMvfxnNB9y
m/0/2147483647'/2/2147483646'/2: L18MSoLXyxN4xrMyw8FSAn3Hvhpu4ZrUcPhAdXy537QLKNT7KmxE
m/0/2147483647'/2/2147483646'/3: KxmL9CcpGNtUAKARTJQVjgY499pdsfk6iSy2aRHfXomLZwvdaqGS
$ python pywallet.py --dump_bip32 xprv9s21ZrQH143K31xYSDQpPDxsXRTUcvj2iNHm5NUtrGiGG5e2DtALGdso3pGz6ssrdK4PFmM8NSp SBHNqPqm55Qn3LqFtT2emdEXVYsCzC2U m/0/2147483647H/0-2/2147483646H/1-3 --bip32_format=addr
m/0/2147483647'/0/2147483646'/1: 1KYQU8kvknvN8DQVdqQrPcjxiq8qQ2AjW1
m/0/2147483647'/0/2147483646'/2: 1MdrWZnF5bwM5zxBKZVEHn8rvKbGDjLXX2
m/0/2147483647'/0/2147483646'/3: 1P8fQNc1q3Bqq2BWde7ZSkSyuQLy5YTW2b
m/0/2147483647'/1/2147483646'/1: 17FFNNBCNSrHpp71Xaf136NgN4Q9fzsRu5
m/0/2147483647'/1/2147483646'/2: 14UKfRV9ZPUp6ZC9PLhqbRtxdihW9em3xt
m/0/2147483647'/1/2147483646'/3: 1PK6Ke6kRCxd2Wbj3n16UR7TPZfmxWzJh
m/0/2147483647'/2/2147483646'/1: 1NoJNJjTDmNMHWQyX9z47WV2VWqy3tjeAY
m/0/2147483647'/2/2147483646'/2: 1G3qeLrL5oxjYucUWmFwQzvoZa7p4hgFHL
m/0/2147483647'/2/2147483646'/3: 115NPN9HKQtkiCuiiueQhFkAjNcPPL653x
The blue lines are one of the BIP32 test vector BIP32 test vectors: https://en.bitcoin.it/wiki/BIP_0032_TestVectors |
|
|
|
Nobody could legitimately double your money in 24h.
Except maybe if you joined very early in the Ponzi sch super investment website |
|
|
|
Wouldnt it be suspicious if the account password was changed and then the email? For security reasons, your current password is required to make changes to your account. My account was hacked because of a real stupid password and I also realized that Microsoft refuses any new device to login to my email account so I changed them both recently So yeah maybe suspicious but definitely can be legitimate Definitely putting an address here later, I only had a couple of posts with addresses I still have control of, better choose an address specifically for this |
|
|
|
|
It's because transactions must be used as a whole as per the protocol
So when you send an amount to someone, the wallet takes an incoming transaction with a higher amount (the one with $460, to 15CTQfNhp5DBnVowSVk5isy1pZTQDQqwjk) and sends the remaining coins to a "hidden" address (12BwatpDHMp9EM3aF4dxiC91DGEdPCiHTB) from your wallet
|
|
|
|
|
Hey there I'm back
I was focusing on pywallet but I just remembered I made this script
If there is some demand I can revive it
Not that that'd be a pleasure to dive into those really old 2k lines but I need to do a user script for myself anyway (e.g. for giving merit without exiting the current page)
|
|
|
|
Base58 isn't used at all in the Bitcoin protocol so there isn't even a problem to use base57 right now It's only used to represent "redeeming scripts" (not really but close enough) as human readable addresses, which you can write in whatever base you'd like as long as people sending coins your way agree on that format By the way we now use Bech32 addresses so you'll see less and less base58 https://en.bitcoin.it/wiki/BIP_0173Motivation
For most of its history, Bitcoin has relied on base58 addresses with a truncated double-SHA256 checksum. They were part of the original software and their scope was extended in BIP13 for Pay-to-script-hash (P2SH). However, both the character set and the checksum algorithm have limitations:
Base58 needs a lot of space in QR codes, as it cannot use the alphanumeric mode.
The mixed case in base58 makes it inconvenient to reliably write down, type on mobile keyboards, or read out loud.
The double SHA256 checksum is slow and has no error-detection guarantees.
Most of the research on error-detecting codes only applies to character-set sizes that are a prime power, which 58 is not.
Base58 decoding is complicated and relatively slow.
Example of changing the base of a random address: - classical base 10, 0123456789: 03208201879866765930316939846674310105672575856186728793269 - classical base 16, 0123456789abcdef: 082d730c471a94aa1ca711a72f5b7ea80faa9d28f97ce44b5 - Bitcoin base 58, 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz: 1CvpddsyKHQs5VHuvVBjAHZqc4z2r1FbV6 - a random base 57 I found on the web, 0123456789abcdefghijkmnopqrstvwxyzABCDEFGHJKLMNPQRSTVWXYZ: 0kN8M5TDvkniYc4NsY0rdtC2Hy9RVtfaVQ All these encode the same information |
|
|
|
About keeping on paper: be subtle, don't write what it is You can "cut" the paper in several pieces, mark them as outlook.com password, store them in a password manager, etc About hardware wallets: Ledger is a big no IMO Its a unice password, never use it for anything else and I think its very hard to break. I see what you are saying, no one should ever be 100% sure that they are free from virus and malware. But the risk should be closer to 0.00000001 % than 90% I hope? There is still some risk, better use an offline wallet as ranochigo said If you're using Windows it is suicide But if I would remember it (or write it down in a safe or somewhere other safe place) it would as good as having a cold storage-thing? Writing it down make it possible for other people to find it Otherwise if you have a 100% reliable memory, the only possible way to lose them is you dying Whatever you do, make (encrypted) backups |
|
|
|
Bitcoin’s unexpected 11% decline  Good one |
|
|
|
Je vais me faire insulter par toute la communauté crypto qui me suit mais je le dis quand même parce qu'on parle à tout le monde, ceux qui ont les moyens et ceux qui n'ont pas les moyens : le Bitcoin c'est pour ceux qui sont prêts à y investir l'argent dont ils n'ont pas besoin C'est juste ce qu'on dit en permanence  il faut les mettre sur ce qu'on s'appelle un hardware wallet, notamment construit par la start-up française Ledger, et là vous serez sûrs qu'on vous les volera pas Bon vos numéros de téléphone, noms et adresse postale, ça par contre hein...  En tout cas merci, je vais suivre un peu ça |
|
|
|
You can try using the recovery feature of Pywallet mkdir test_recovery ; python pywallet.py --recover --recov_device=/path/to/wallet.dat --recov_size=10Mio --recov_outputdir=./test_recovery If there are private keys left with some header+footer bytes, it will find them Output example: Enter the passphrase for the wallet that will contain all the recovered keys (can't be empty): ***********************
Enter the possible passphrases used in your deleted wallets.
Don't forget that more passphrases = more time to test the possibilities.
Write one passphrase per line and end with an empty line.
Possible passphrase:
Starting recovery.
Read 0.0 Go in 0.0 minutes
Found 0 possible wallets
Found 0 possible encrypted keys
Found 138 possible unencrypted keys
The wallet is encrypted and the passphrase is correct
|
|
|
|
|
I've been reading this thread for a few days but don't have contributed because there are already good advices
I just realized though that an youtuber I follow may help for this kind of recovery
I won't post here because I don't want the guy to be spammed with dozens of requests from people who just send mails to any people mentioned in a 'wallet help' thread (yes this happened before)
Anyway I sent it to private73123 and if future people sees this message and needs HARDWARE help, you can PM me
FWIW I don't know the guy at all, he just happens to have tons of video of him working at his shop so that's your job to search, trust and choose what you do with this guy
|
|
|
|
it would be useful to have:
- updated Pywallet that works "properly" with newer wallet.dat files and doesn't just suppress/ignore errors
- Python 3 compatibility would be a bonus, as Python 2 is now completely unsupported
These 2 are a must, plus these: - clean that crazy source code, there's no reason for it to be 5000 lines long and to be that ugly - change the --datadir and --wallet arguments - kill (for now) the web interface and remove the twisted dependency (that would help reducing the code by the way) - be more explicit about ecdsa being only optional When do you think this will be available to download and run?? Honestly I don't know, you can follow the thread and I've put some issues on Github to track what I'm doing/planning Right now I'm on the code cleaning + python 3 support The __db.00x files are only internal files for Berkeley DB so not helpful
But yeah you can try the db_dump command (db-utils in apt) on your wallet, it should output a bunch of (sensitive!) hexadecimal data without errors
I just tested with an old wallet of mine, maybe from something like 2013, and it worked as expected
If it works for you then try deleting (backup them if you want but they aren't needed) the __db.00x files
Does the existence of the DB files indicate that Jack Jack found a valid/ actual bitcoin wallet on my device?? Thank you, and welcome back! As Mek said, no It just means that the Berkeley DB library created a bsddb environment in this folder, which actually means nothing |
|
|
|
Ok done, --datadir is no more I added a message about the breaking change, I think it is enough $ python pywallet.py --datadir abc --dumpwallet --wallet wallet.dat
Breaking change
The --datadir option has been removed, now the full path of the wallet file must go to --wallet
If you're not sure what to do, concatenating the old --datadir content, then a directory separator, then the old --wallet should do the trick
If not, ask for help in the Pywallet thread: https://bitcointalk.org/index.php?topic=34028
I also improved the displayed info for private keys (still P2PKH for now) $ python pywallet.py --info --importhex --importprivkey 1
Hexadecimal private keys must be 64 or 66 characters long (specified one is 1 characters long)
Padding with zeroes, uncompressed
Compressed: False
Address (Bitcoin): 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm
Privkey (Bitcoin): 5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf
Hexprivkey: 0000000000000000000000000000000000000000000000000000000000000001
Hash160: 91b24bf9f5288532960ac687abb035127b1d28a5
Pubkey: 0479be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798483ada7726a3c4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8
Hexadecimal private keys must be 64 or 66 characters long (specified one is 1 characters long)
Padding with zeroes, compressed
Compressed: True
Address (Bitcoin): 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
Privkey (Bitcoin): KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn
Hexprivkey: 0000000000000000000000000000000000000000000000000000000000000001
For compressed keys, the hexadecimal private key sometimes contains an extra '01' at the end
Hash160: 751e76e8199196d454941c45d1b3a323f1433bd6
Pubkey: 0279be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798
|
|
|
|
|
Actually it'd be better to completely remove this datadir option that confuses many people and makes no sense
Working on it!
|
|
|
|
Yeah much clearer, I'll add that to the next version! Maybe you didn't understand how to use the arguments and I couldn't blame you --datadir=./w --wallet=wallet.dat This looks for the file ./w/wallet.dat, is it really there? If it is in the pywallet folder then that would be --datadir=. |
|
|
|
Yes indeed, try this instead try:
r = db.open(walletfile, "main", DB_BTREE, flags)
except DBError as e:
print(e)
r = True
|
|
|
|
|
Show Posts
