Search content
Sort by
Showing 20 of 23 results by EdouardDuval
STRONGS
STRONGS [STRS] is a new cryptocurrency with a great future!
Also, an experienced marketer and trader will join our team after the launch of the project. Our cryptocurrency is based on kHeavyHash algorithm
Main Features
Name: STRONG$
Abbreviation: STR$
PoW algorithm: kHeavyHash
Maximum Coins: 180M
Premine: 100000 STR$ (To be used for rewards, adding to exchanges and promotions)
Block reward: 25 STR$ (50% to miners / 50% to masternodes)
Masternode Pledge: 7000 STR$
Average time to find a block: 50 seconds
Number of blocks to mature: 20
Calculation of difficulty: every 3 blocks
Mining will begin on May 8, 2025
For the first 100 blocks, the reward will be set at 1 STR$ to prevent instamining.
Wallet:
Windows: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Win64.zip
Linux: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Linux.tar.gz
Roadmap
May 8, 2025 - Start of mining
May 10, 2025 - Launch official pool with 1.5% commission and DDOS protection
May 10, 2025 - Launch of a website
June, 2025 - Exchanges (First Xeggex, Second NOKYC)
PUBLIC RELATIONS
Website: May 9, 2025
AWARDS.
Transfer: 200 STR$
Pools: 200 STR$ (For the first three pools).
STRONGS [STRS] is a new cryptocurrency with a great future!
Also, an experienced marketer and trader will join our team after the launch of the project. Our cryptocurrency is based on kHeavyHash algorithm
Main Features
Name: STRONG$
Abbreviation: STR$
PoW algorithm: kHeavyHash
Maximum Coins: 180M
Premine: 100000 STR$ (To be used for rewards, adding to exchanges and promotions)
Block reward: 25 STR$ (50% to miners / 50% to masternodes)
Masternode Pledge: 7000 STR$
Average time to find a block: 50 seconds
Number of blocks to mature: 20
Calculation of difficulty: every 3 blocks
Mining will begin on May 8, 2025
For the first 100 blocks, the reward will be set at 1 STR$ to prevent instamining.
Wallet:
Windows: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Win64.zip
Linux: https://github.com/STRONG-chain/STRONG/releases/download/1.0.1/STRONGS.-v.1.0.1-Release-Linux.tar.gz
Roadmap
May 8, 2025 - Start of mining
May 10, 2025 - Launch official pool with 1.5% commission and DDOS protection
May 10, 2025 - Launch of a website
June, 2025 - Exchanges (First Xeggex, Second NOKYC)
PUBLIC RELATIONS
Website: May 9, 2025
AWARDS.
Transfer: 200 STR$
Pools: 200 STR$ (For the first three pools).
Hi everyone, hope you doing well.
My question is, is there another software than hashcat for resolving this kind of hash?
$bitcoin$64$xxxxxx$16$0af493ab2796f208$99974$2$00$2$00
My question is, is there another software than hashcat for resolving this kind of hash?
$bitcoin$64$xxxxxx$16$0af493ab2796f208$99974$2$00$2$00
Is it your wallet or found/bought online?
End of extracted hash is like in some forged wallets offered for sale:
https://bitcointalk.org/index.php?topic=5242967.msg56287468#msg56287468
root@RémiM:~# python2.7 core_decrypter.py?dl=1.1
-snip-
root@RémiM:~# pip install base58
Requirement already satisfied: base58 in /usr/local/lib/python3.9/dist-packages (2.1.1)
can you help please? Thanks
everytime i try i get thiis
Pip is installing base58 to Python 3.9 while you're using Python 2.7 for core_decrypter.py.-snip-
root@RémiM:~# pip install base58
Requirement already satisfied: base58 in /usr/local/lib/python3.9/dist-packages (2.1.1)
can you help please? Thanks
everytime i try i get thiis
Try to specify the python version when using pip.
My wallet isn't this one.
I just take these hashes as example.
I find a lot of people who are stuck to this step.
Like the lostwallet project on github.
If you can really help i send you a message on telegram with my adresse.
I just take these hashes as example.
I find a lot of people who are stuck to this step.
Like the lostwallet project on github.
If you can really help i send you a message on telegram with my adresse.
How hard would it be for jackjack or someone to create a standalone tool to decrypt private keys, if the correct hex strings and passphrase were inputted? Not that I'm implying he should, as he seems to be a very busy person. But If you can search out the required info with a hex editor, it would be a very flexible tool for fragmented wallet files.
Probably not very difficult... because it didn't take me too long to bang this out: https://keybase.pub/hcp/python/core_decrypter.pyIt's pretty rough... but basically, if you can feed it an "encrypted master key" (or decrypted master key), "encrypted private key" and matching "public key"... it will prompt for wallet passphrase and then attempt to decrypt the master key... then use that to decrypt the private key before outputting the Address+WIF.
I've run some tests on some newly generated wallet.dat data... and the master key/priv key/pub key data from the code example in joric's post that I linked to earlier... and it seems to be working OK.
As per the comment at the top of the script, it borrows very heavily from the "Proof of Concept" code from joric's post.... full credit to them!
NOTES:
- Python 2.7x compatible only for now... if there is enough interest, I'll see if I can make it Python3 compatible.
- requires a couple of libraries that you'll likely already have installed if you've been using PyWallet etc (ie. pycrypto, ecdsa etc)... if Python moans at you about modules not being found then install them with pip
- (For now) The encrypted master key needs to be the full 66/67 bytes (132/134 hex chars) of the mkey record in the wallet.dat... This should be of the form:
"30" - 48 byte data record indicator
"48 bytes worth of encrypted master key"
"08" - 8 byte data record indicator
"8 bytes worth of salt"
"4 bytes worth of method" - should be 0 (ie. 00000000)
"4 bytes worth of iterations" - in Little Endian (ie. 1fb80000 ==> 0x0000b8f1 ==> 47345)
"00" - 1 byte end of record indicator (optional)
for example:
Code:
3008adc5605413b38a04979bf465d0cff826a25c2c8812e582241477052c6d45c11b27690ba3bf2c1da144600789c2baaa08d8659791be653e15000000001760030000
Quote
3008adc5605413b38a04979bf465d0cff826a25c2c8812e582241477052c6d45c11b27690ba3bf2c1 da144600789c2baaa08d8659791be653e15000000001760030000
This modified version of the walletinfo.py script (original here) will output the "full mkey" from a wallet.dat: https://keybase.pub/hcp/python/walletinfo.py
Usage:
Code:
python walletinfo.py wallet.dat
otherwise, you'll have to do some hexediting of the wallet.dat file to find the data you need... have fun with that
I am also considering modifying the script so you can supply the "parsed" master key data (ie. encrypted key, salt, iterations etc) individually... I guess it depends on what is the most likely format of the hex data extracted from the wallet.dat file.
On subsequent runs for private keys from the same wallet.dat (ie. encrypted with the same master key), you can just use the "decrypted master key" that is output instead of using the "encrypted" master key + walletpassphrase
Example:
Code:
C:\core_decrypter>C:\Python27\python.exe core_decrypter.py --enc_mkey 3008ADC5605413B38A04979BF465D0CFF826A25C2C8812E582241477052C6D45C11B27690BA3BF2C1DA144600789C2BAAA08D8659791BE653E150000000017600300 BF1356ABEEB7FD2C7CD6757BA4B459AF64D62A3855592B24F685F642D7143D7F6725230C8B8D9B65D42DA5634DDA9A73 020016BE1AFB579AB2EF6F57220E8946B0653FD5B883E09D70A7825F17C3B07F3D
Enter wallet passphrase:
Keys successfully decrypted:
decrypted mkey: 84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6
--------------------------------------------------------------
uncomp addr: 13y8obG15gqVBmuRzD7HnokyVqGhQJZBfC
uncomp WIF : 5JXMD129XHcfpWF8hrzKG7eW4zDwZtuQ82gkwfMLz9aQRTxvsrh
--------------------------------------------------------------
comp addr : 15V1kJedt9CJDsEYCofuvfWTyapqJPW4C9
comp WIF : KzLxBy64cgLSLg5P1MdybiLXJba7rC6H42SUxGGoDErSNtSKCJKP
--------------------------------------------------------------
C:\core_decrypter>
Enter wallet passphrase:
Keys successfully decrypted:
decrypted mkey: 84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6
--------------------------------------------------------------
uncomp addr: 13y8obG15gqVBmuRzD7HnokyVqGhQJZBfC
uncomp WIF : 5JXMD129XHcfpWF8hrzKG7eW4zDwZtuQ82gkwfMLz9aQRTxvsrh
--------------------------------------------------------------
comp addr : 15V1kJedt9CJDsEYCofuvfWTyapqJPW4C9
comp WIF : KzLxBy64cgLSLg5P1MdybiLXJba7rC6H42SUxGGoDErSNtSKCJKP
--------------------------------------------------------------
C:\core_decrypter>
On the next run, you can just use the "decrypted mkey" that was displayed:
Code:
84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6
... and remove the --enc_mkey flag from the commandline:
Code:
C:\core_decrypter>C:\Python27\python.exe core_decrypter.py 84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6 ba946bb7db1a98e628d1a93104369d7cbb7a4cba9c9705223a2c7891bdc888a8b1019c27d2c17b28728513a51ba54f1e 0200cc635c13471b913e22bbe568711c19fd7bcb7449a9f09885f9ca53aff3cc6e
Keys successfully decrypted:
decrypted mkey: 84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6
--------------------------------------------------------------
uncomp addr: 1K3p8CZCRZoKuXtzzawYs2LmKuN1uV2jvd
uncomp WIF : 5JsNBq7rwGPqp1jZLSgawvtusp3E47c2PjPex2QgK4Mhj4Bneuv
--------------------------------------------------------------
comp addr : 1CVQVAeTCPhNUCcVsmSqrZoXWQCksbmgmc
comp WIF : L1sJWoPHQWwpSWEqipMiqSt8PGcpck9b9L6zVsDWWhpNkErSrJwf
--------------------------------------------------------------
C:\core_decrypter>
NOTE that there is no "wallet passphrase" prompt! Keys successfully decrypted:
decrypted mkey: 84d1f2f2380eb3a089ea256b851553ebfbc95555eb11b28a9eaaa7eeb97db4d6
--------------------------------------------------------------
uncomp addr: 1K3p8CZCRZoKuXtzzawYs2LmKuN1uV2jvd
uncomp WIF : 5JsNBq7rwGPqp1jZLSgawvtusp3E47c2PjPex2QgK4Mhj4Bneuv
--------------------------------------------------------------
comp addr : 1CVQVAeTCPhNUCcVsmSqrZoXWQCksbmgmc
comp WIF : L1sJWoPHQWwpSWEqipMiqSt8PGcpck9b9L6zVsDWWhpNkErSrJwf
--------------------------------------------------------------
C:\core_decrypter>
If the walletpassphrase is not correct or the hex data is corrupt/incorrect, you will see a warning like this:
Code:
C:\core_decrypter>C:\Python27\python.exe core_decrypter.py --enc_mkey 3008ADC5605413B38A04979BF465D0CFF826A25C2C8812E582241477052C6D45C11B27690BA3BF2C1DA144600789C2BAAA08D8659791BE653E150000000017600300 BF1356ABEEB7FD2C7CD6757BA4B459AF64D62A3855592B24F685F642D7143D7F6725230C8B8D9B65D42DA5634DDA9A73 020016BE1AFB579AB2EF6F57220E8946B0653FD5B883E09D70A7825F17C3B07F3D
Enter wallet passphrase:
WARNING!!!
WARNING!!! - computed public keys DO NOT match, passphrase is probably incorrect or hex data is corrupt
WARNING!!!
C:\core_decrypter>
The script calculates the pubkey from the decrypted privkey, then compares to the user supplied "hex pub key". If both the calculated compressed and uncompressed pubkeys do not match the user provided pubkey, then either the wallet passphrase was incorrect (resulting in a bad master key decrypt) or the priv/pub key hex data could be corrupt/incorrect.Enter wallet passphrase:
WARNING!!!
WARNING!!! - computed public keys DO NOT match, passphrase is probably incorrect or hex data is corrupt
WARNING!!!
C:\core_decrypter>
Wallet passphrase for the examples above: password123
Partial Pywallet dump (with encrypted privkeys):
Code:
keys": [
{
"addr": "15V1kJedt9CJDsEYCofuvfWTyapqJPW4C9",
"compressed": true,
"encrypted_privkey": "bf1356abeeb7fd2c7cd6757ba4b459af64d62a3855592b24f685f642d7143d7f6725230c8b8d9b65d42da5634dda9a73",
"pubkey": "020016be1afb579ab2ef6f57220e8946b0653fd5b883e09d70a7825f17c3b07f3d",
"reserve": 1
},
{
"addr": "1CVQVAeTCPhNUCcVsmSqrZoXWQCksbmgmc",
"compressed": true,
"encrypted_privkey": "ba946bb7db1a98e628d1a93104369d7cbb7a4cba9c9705223a2c7891bdc888a8b1019c27d2c17b28728513a51ba54f1e",
"pubkey": "0200cc635c13471b913e22bbe568711c19fd7bcb7449a9f09885f9ca53aff3cc6e",
"reserve": 1
},
{
"addr": "1JSo3zCQ8xaj9oGgfts8DMATtQ5ptnwigk",
"compressed": true,
"encrypted_privkey": "65207b28be9d6b142837e192797cc782e3c8f868fddb2fb901895dd4115c6bc1367c0787544f48bc631ec7e8fa0ebb51",
"pubkey": "02020828662e18c691abd0ca216d655c576bbbac560a8852e7aafb42acb76ed9b9",
"reserve": 1
},
{
"addr": "15V1kJedt9CJDsEYCofuvfWTyapqJPW4C9",
"compressed": true,
"encrypted_privkey": "bf1356abeeb7fd2c7cd6757ba4b459af64d62a3855592b24f685f642d7143d7f6725230c8b8d9b65d42da5634dda9a73",
"pubkey": "020016be1afb579ab2ef6f57220e8946b0653fd5b883e09d70a7825f17c3b07f3d",
"reserve": 1
},
{
"addr": "1CVQVAeTCPhNUCcVsmSqrZoXWQCksbmgmc",
"compressed": true,
"encrypted_privkey": "ba946bb7db1a98e628d1a93104369d7cbb7a4cba9c9705223a2c7891bdc888a8b1019c27d2c17b28728513a51ba54f1e",
"pubkey": "0200cc635c13471b913e22bbe568711c19fd7bcb7449a9f09885f9ca53aff3cc6e",
"reserve": 1
},
{
"addr": "1JSo3zCQ8xaj9oGgfts8DMATtQ5ptnwigk",
"compressed": true,
"encrypted_privkey": "65207b28be9d6b142837e192797cc782e3c8f868fddb2fb901895dd4115c6bc1367c0787544f48bc631ec7e8fa0ebb51",
"pubkey": "02020828662e18c691abd0ca216d655c576bbbac560a8852e7aafb42acb76ed9b9",
"reserve": 1
},
Traceback (most recent call last):
File "core_decrypter.py?dl=1.1", line 14, in <module>
import base58
ImportError: No module named base58
root@RémiM:~# pip install base58
Requirement already satisfied: base58 in /usr/local/lib/python3.9/dist-packages (2.1.1)
can you help please? Thanks
everytime i try i get thiis
I already tried it with 10 million combinaison password and don't find anything.
maybee i'm doing it wrong.
Can you explain how you will do it if it was yours? Thanks in advance.
maybee i'm doing it wrong.
Can you explain how you will do it if it was yours? Thanks in advance.
I already tried it,but not a success.
I was thinking
since i got the hashes of the password, is there a way to recover it with others software?
Like is there a software made only for bitcoin hashes?
thanks for your time.
I was thinking
since i got the hashes of the password, is there a way to recover it with others software?
Like is there a software made only for bitcoin hashes?
thanks for your time.
Hi everyone, hope you doing well.
My question is, is there another software than hashcat for resolving this kind of hash?
$bitcoin$64$xxxxxx$16$0af493ab2796f208$99974$2$00$2$00
Thanks you for your help.
My question is, is there another software than hashcat for resolving this kind of hash?
$bitcoin$64$xxxxxx$16$0af493ab2796f208$99974$2$00$2$00
Thanks you for your help.
I ve totally deleted the software and download the blockchain again .... Wait to see if i was write with the password since it use a character that is not accepted by pywallet, which explain the erros I get.
Thanks for all this help
Thanks for all this help
I used all the pywallet i found.
Does that mean you get "Segmentation fault" error message for all pywallet you tried?
But i think I ve got the password to the wallet.dat.
But there is one last problem
I download bitcoin core.
And even though i try everything in my mind
it keeps abort because of some
Original message:
Error opening block database.
Do you want to rebuild the block database now?
I click rebuild.
and everytime it does :
Original message:
Error opening block database
How i solve this problem??? it start to be annoying to go about all this trouble...
But i need my btcs back;
But there is one last problem
I download bitcoin core.
And even though i try everything in my mind
it keeps abort because of some
Original message:
Error opening block database.
Do you want to rebuild the block database now?
I click rebuild.
and everytime it does :
Original message:
Error opening block database
How i solve this problem??? it start to be annoying to go about all this trouble...
But i need my btcs back;
Could you share debug.log file generated by Bitcoin Core so we can give more specific suggestion? If you don't know where to find it, check https://en.bitcoin.it/wiki/Data_directory.
2022-08-24T13:13:18Z Qt 5.15.2 (static), plugin=windows (static)
2022-08-24T13:13:18Z Static plugins:
2022-08-24T13:13:18Z QWindowsIntegrationPlugin, version 331520
2022-08-24T13:13:18Z QWindowsVistaStylePlugin, version 331520
2022-08-24T13:13:18Z Style: windowsvista / QWindowsVistaStyle
2022-08-24T13:13:18Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2022-08-24T13:13:18Z Screen: \\.\DISPLAY1 1366x768, pixel ratio=1.0
2022-08-24T13:13:20Z Assuming ancestors of block 000000000000000000052d314a259755ca65944e68df6b12a067ea8f1f5a7091 have valid signatures.
2022-08-24T13:13:20Z Setting nMinimumChainWork=00000000000000000000000000000000000000002927cdceccbd5209e81e80db
2022-08-24T13:13:20Z Prune configured to target 1907 MiB on disk for block and undo files.
2022-08-24T13:13:20Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2022-08-24T13:13:20Z Using RdRand as an additional entropy source
2022-08-24T13:13:20Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core ne s’est pas encore fermer en toute sécurité…"
2022-08-24T13:13:20Z Default data directory C:\Users\Joël\AppData\Roaming\Bitcoin
2022-08-24T13:13:20Z Using data directory C:\Users\Joël\AppData\Roaming\Bitcoin
2022-08-24T13:13:20Z Config file: C:\Users\Joël\AppData\Roaming\Bitcoin\bitcoin.conf (not found, skipping)
2022-08-24T13:13:20Z Setting file arg: wallet = ["Test"]
2022-08-24T13:13:20Z Using at most 125 automatic connections (2048 file descriptors available)
2022-08-24T13:13:20Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-08-24T13:13:20Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-08-24T13:13:20Z Script verification uses 7 additional threads
2022-08-24T13:13:20Z scheduler thread start
2022-08-24T13:13:20Z Using wallet directory C:\Users\Joël\AppData\Roaming\Bitcoin\wallets
2022-08-24T13:13:20Z init message: Vérification des porte-monnaie…
2022-08-24T13:13:20Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2022-08-24T13:13:20Z Using wallet C:\Users\Joël\AppData\Roaming\Bitcoin\wallets\Test\wallet.dat
2022-08-24T13:13:20Z BerkeleyEnvironment::Open: LogDir=C:\Users\Joël\AppData\Roaming\Bitcoin\wallets\Test\database ErrorFile=C:\Users\Joël\AppData\Roaming\Bitcoin\wallets\Test\db.log
2022-08-24T13:13:20Z Using /16 prefix for IP bucketing
2022-08-24T13:13:20Z init message: Chargement des adresses P2P…
2022-08-24T13:13:21Z Loaded 48675 addresses from peers.dat 298ms
2022-08-24T13:13:21Z init message: Chargement de la liste d’interdiction…
2022-08-24T13:13:21Z SetNetworkActive: true
2022-08-24T13:13:21Z Cache configuration:
2022-08-24T13:13:21Z * Using 2.0 MiB for block index database
2022-08-24T13:13:21Z * Using 8.0 MiB for chain state database
2022-08-24T13:13:21Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-08-24T13:13:21Z init message: Chargement de l’index des blocs…
2022-08-24T13:13:21Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2022-08-24T13:13:21Z Opening LevelDB in C:\Users\Joël\AppData\Roaming\Bitcoin\blocks\index
2022-08-24T13:13:21Z Fatal LevelDB error: Corruption: 1 missing files; e.g.: C:\Users\Joël\AppData\Roaming\Bitcoin\blocks\index/000497.ldb
2022-08-24T13:13:21Z You can use -debug=leveldb to get more complete diagnostic messages
2022-08-24T13:13:21Z Fatal LevelDB error: Corruption: 1 missing files; e.g.: C:\Users\Joël\AppData\Roaming\Bitcoin\blocks\index/000497.ldb
2022-08-24T13:13:21Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2022-08-24T13:13:24Z init message: Chargement de l’index des blocs…
2022-08-24T13:13:24Z should not be overwriting a chainstate
2022-08-24T13:13:24Z Error: Error opening block database
2022-08-24T13:13:25Z Shutdown: In progress...
2022-08-24T13:13:25Z scheduler thread exit
2022-08-24T13:13:26Z Shutdown: done
thanks you a lot man.
You help a lot.
I will give you a reward.
And the pywallet you give me works without segmentation fault
I used all the pywallet i found.
But i think I ve got the password to the wallet.dat.
But there is one last problem
I download bitcoin core.
And even though i try everything in my mind
it keeps abort because of some
Original message:
Error opening block database.
Do you want to rebuild the block database now?
I click rebuild.
and everytime it does :
Original message:
Error opening block database
How i solve this problem??? it start to be annoying to go about all this trouble...
But i need my btcs back;
But i think I ve got the password to the wallet.dat.
But there is one last problem
I download bitcoin core.
And even though i try everything in my mind
it keeps abort because of some
Original message:
Error opening block database.
Do you want to rebuild the block database now?
I click rebuild.
and everytime it does :
Original message:
Error opening block database
How i solve this problem??? it start to be annoying to go about all this trouble...
But i need my btcs back;
Re: Found my old Bitcoin wallet.dat. Already ran pywallet. What now?
-snip-
But everytime I get to add the password it says : segmentation fault.
How can i make it work?
From which version of pywallet was it?But everytime I get to add the password it says : segmentation fault.
How can i make it work?
Because in my tests, I haven't encountered a 'seg fault' error by using the master branch of: https://github.com/jackjack-jj/pywallet/tree/master
Tested in Python v2.7.17.
Do not download from the releases tag, it's the old version from 2011.
THANKS YOU A LOT MAN ! It helps.
Now i get the error
ERROR parsing wallet.dat, type b'mkey'
... i don't know what to do .
Re: Found my old Bitcoin wallet.dat. Already ran pywallet. What now?
-snip-
How can i figure out the private keys from these information please?
If you've provided the passphrase, the WIF private keys will be listed under the "keys" json array (usually above that master key array).How can i figure out the private keys from these information please?
It contains "addr", "compressed", "encrypted_privkey" down to "secret",
the one that you're looking for are the "sec" above secret, which is the WIF prvKey of the address above it.
But if you see this line:
Code:
The wallet is encrypted but no passphrase is used
Then there'll be no WIF keys listed there.Yep I understand it.
But everytime I get to add the password it says : segmentation fault.
How can i make it work?
Thanks you for your time.
Re: Found my old Bitcoin wallet.dat. Already ran pywallet. What now?
How can i figure out the private keys from these information please?
If you just use the script or command that the OP did then you both will receive the same result.
Do you know exactly the password of your wallet.dat? then use the command that I posted above or this below
Code:
pywallet.py --dumpwallet --datadir=. --passphrase=YourPassword
Or if you don't know the password then you need BTCrecover tool the guide can find here btcrecover Tutorial
I tried this . But everytime, on all my computer it says : Segmentation fault
I think I ve got the right password but I can make it work.
thanks for all the answers , very appreciate.
yep that is exactly what i do not understand
why this software do this bug?? oO
I'm so close to get my btcs back... and there is a new bug.
But nevermind,
I ask on github and open up a new issues hope someone can help.
And last question but maybee the more important
if there s a way to find a private keys from mkeys an c keys because i already tried crackBTCwallet
Thank you a lot.
why this software do this bug?? oO
I'm so close to get my btcs back... and there is a new bug.
But nevermind,
I ask on github and open up a new issues hope someone can help.
And last question but maybee the more important
if there s a way to find a private keys from mkeys an c keys
because i already tried crackBTCwalletThank you a lot.
Thanks for the documentation, i'll read it
@pawgo and i already tried this soft.
I have only the wallet.dat that is the passwords that are lost.
And i try somehting.
With pywallet.py i tried some passphrase but everytime i get this error
Segmentation fault
what that mean please?
@pawgo and i already tried this soft.
I have only the wallet.dat that is the passwords that are lost.
And i try somehting.
With pywallet.py i tried some passphrase but everytime i get this error
Segmentation fault
what that mean please?