Search content
Sort by
Showing 10 of 10 results by 9code7
Re: Will these bitcoind settings hamper my solo miner chances?
lol...I knew my odds were practically zero but it's nice to see the math which proves it. Those odds are lower than I thought. Still, I'm running a full node for several reasons, only one of which is solo mining. My "rig" is 3 block erupters, so the amount of electricity being used exclusively for mining is negligible. I've had the block erupters for years so I thought since I'm running a node I might as well put them to work.
Now if they do find a block I'll have more appreciation for such an extremely unlikely event
Now if they do find a block I'll have more appreciation for such an extremely unlikely event
I'm running the latest version of cgminer on Ubuntu 18.04.03.
The output of timedatectl is:
However, when I run cgminer, it shows the starting date as 1969-12-31.
Will this affect my mining (BTC solo mining)? If so, how can i correct this?
The output of timedatectl is:
Code:
Local time: Wed 2020-02-05 15:46:13 EST
Universal time: Wed 2020-02-05 20:46:13 UTC
RTC time: Wed 2020-02-05 20:46:13
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
Universal time: Wed 2020-02-05 20:46:13 UTC
RTC time: Wed 2020-02-05 20:46:13
Time zone: America/New_York (EST, -0500)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
However, when I run cgminer, it shows the starting date as 1969-12-31.
Will this affect my mining (BTC solo mining)? If so, how can i correct this?
I'm running bitcoind and solo mining. It's a lottery miner since my hash rate is very low. Still, do these settings lessen my already low chances of finding a block?
maxconnections=50
maxuploadtarget=150
I chose these settings because my bandwidth is somewhat limited but I still would like to run a full node for several reasons.
maxconnections=50
maxuploadtarget=150
I chose these settings because my bandwidth is somewhat limited but I still would like to run a full node for several reasons.
Re: Is it possible to use an ASIC miner to crack a wallet.dat lost password?
I guess the answer in general is here:
Why Bitcoin mining ASICs won't crack your password
In other words it should be some particular ASIC especially designed for passwords' bruteforce. Random old ASIC-miner unlikely would be suitable for this since it basically works according to another scheme.
Why Bitcoin mining ASICs won't crack your password
In other words it should be some particular ASIC especially designed for passwords' bruteforce. Random old ASIC-miner unlikely would be suitable for this since it basically works according to another scheme.
Thanks - that answers it perfectly and explains why a miner can't be used for password cracking. It wasn't the answer I was hoping for but at least I know I need to look in another direction
Re: Is it possible to use an ASIC miner to crack a wallet.dat lost password?
It's pretty common:
https://github.com/gurnec/btcrecover
https://hashcat.net/wiki/doku.php?id=example_hashes (search for "bitcoin")
It's not like anyone can just crack your bitcoin password. They at least need the wallet password hash, which I have, and unless it's a weak password, they need to have educated guesses as to what the password is (which I do).
Since there are ways to solve these hashes with CPUs and GPUs, there must be a way to use SHA-256 ASIC hardware to solve SHA-256 password hashes much faster than CPUs or GPUs. I just don't know how and am hoping someone here does and can point me in the right direction.
https://github.com/gurnec/btcrecover
https://hashcat.net/wiki/doku.php?id=example_hashes (search for "bitcoin")
It's not like anyone can just crack your bitcoin password. They at least need the wallet password hash, which I have, and unless it's a weak password, they need to have educated guesses as to what the password is (which I do).
Since there are ways to solve these hashes with CPUs and GPUs, there must be a way to use SHA-256 ASIC hardware to solve SHA-256 password hashes much faster than CPUs or GPUs. I just don't know how and am hoping someone here does and can point me in the right direction.
Is it possible to use an ASIC miner to crack a wallet.dat lost password?
I have a Dash wallet from years ago and I can't find the password to it. I was able to dump the hash (parts between periods have been substituted):
Is it possible to use an ASIC miner, like an old Jalepeno, to crack the hash? I'm using btcrecover and it won't work with my GPU, and hashcat wants a bitcoin hash to begin with $bitcoin$96, so I'm looking for other options. I figured since the password I'm trying to crack is SHA-256 based, maybe an ASIC miner could help?
Code:
$bitcoin$64$...64-hex-chars...$16$...16-hex-chars...$190170$2$00$2$00
Is it possible to use an ASIC miner, like an old Jalepeno, to crack the hash? I'm using btcrecover and it won't work with my GPU, and hashcat wants a bitcoin hash to begin with $bitcoin$96, so I'm looking for other options. I figured since the password I'm trying to crack is SHA-256 based, maybe an ASIC miner could help?
Re: BiblePay | 10% Charity | POBH CPU | Sanctuaries (Masternodes) | Orphans
Yall might like https://truebibletrivia.com, a free Bible trivia game.