May I know how do you check the status for using Mars Lander

Thanks

Hahaha. Lucky should be my name.

I really want to thank everyone on the forum for their support and guidance.
Particularly thank you to the following:

-CK <-- Your pool has changed my world and wallet balance forever.
Kano <-- Your software and guidance was invaluable.
SideHack <-- You evil genius your hardware although small was extremely effective.
Willi9974 <-- I used the funds won from one of your block parties to buy the hardware
419Mining.com <-- Seller of the Compac F's  
AsicPuppy.com  <-- Seller of the Compac F's


I chose to share it was me for a few reasons:

1. Why shouldn't I share my success with others? I'd love to see you all hit.
2. Share the fact that you can still get lucky on the ever growing Bitcoin Blockchain even as a small or in my case micro solo miner. I am hopeful that this brings more small miners into scene.
3. Draw attention to smaller pools. It's a shame there are a few "big" pools out there that dominate most of the mining.
4. Yes I hit on a USB Miner Stick. I had 9 GekkoScience Compac F's (all overclocked) running cgminer on a HP Omen machine (That was also mining ETH at the time) hence the name "The Omen"
5. The 86TH that was seen on my account was mostly rented hashpower from Nicehash that had stopped prior to me finding the block. To be clear no rented hashpower was used to mine this block.
6. My entire USB Mining Farm consists of about 8.2TH - 9.3TH. The Omen had about 3.65TH of that at the time of finding the block.
7. I wanted to share the images of my setup and cgminer to show indisputable proof of what had transpired. (I too would be ultra skeptical if someone told me they hit like this on a USB stick miner).


Now because I hit big should I give up now? Nah... I am still mining with ALL my USB Stick miners as you can see here: https://solo.ckpool.org/users/3EoqjNmeaaVvVDCPbVXxQQRH6UFpDUqpPg


Again thank you all.
 

Cgminer does have provisions for temp monitoring, fan control, shut down, etc. but -- there needs to be a temp monitor of some sort to feed that info into cgminer and none of the Compacs have that. You could always look for RasPi projects that deal with temp control, mount a temp sensor to the heatsink and use it to simply switch off power to the sticks.

Why create a new thread?
You should go post here: https://bitcointalk.org/index.php?topic=5355470.260

You can change your BTC address, so you have new fresh one of statistics...

The bestshare stat shows exactly that. It resets everytime a block is found on the pool. The bestever stat is the bestshare you ever found and isn't reset.

Bestshare resets only when the pool finds a block.

The last block was in April 2020. It should be that value, or higher until the next block when it resets to zero.

Need some help.
Running 2 of the NewPac miners on a Raspberry Pi 4 2gb ram model with a 32GB micro sd boot card. The Pi did a reboot and now I can't run the command to start mining, which would be (replaced my username with X's for privacy), it spits out ! What do I do and how do I fix it?
Before the Pi rebooted, the miner said that there was no USB devices attached.
 I am more than willing to reinstall rasbian and the cgminer if needed. Please let me know!

I'm gonna agree with gt_addict, looks like you've got a flag set to report every gosh darn thing. Usually it just reports accepted shares, which when everything's working right you might see a few every minute. The A number up near the top is the number of accepted shares, and it's a big number so you're definitely mining and cooperating with the pool.

What's your command line? You can strip the credentials for safety, we just want to see what else is in there to help find the root of this.

I'm gonna agree with gt_addict, looks like you've got a flag set to report every gosh darn thing. Usually it just reports accepted shares, which when everything's working right you might see a few every minute. The A number up near the top is the number of accepted shares, and it's a big number so you're definitely mining and cooperating with the pool.

What's your command line? You can strip the credentials for safety, we just want to see what else is in there to help find the root of this.

Have you got the “-verbose” output set? (I think thats the option).

Solo Chance

Calculate the chance of hitting a bitcoin block when solo mining!

Hi,

This is a great site. Simple yet effective! I appreciate the effort you've put into it!

Where do you pull your network hashrate data from to calculate the probability with solo mining?

Regards
Stav'

2020deception: You did not buy it from GekkoScience. You bought it from a reseller. If you check the order details there should be further info on the actual seller, including some kind of contact info.

Stavroski: Connect to the pool and let it mine for a while - an hour at least. Typically the starting share threshold is high because pools expect a higher hashrate so it may take a while before any shares register, but after a few the pool should adjust the threshold. You may also look into the --suggest-diff command.

2020deception: You did not buy it from GekkoScience. You bought it from a reseller. If you check the order details there should be further info on the actual seller, including some kind of contact info.

Stavroski: Connect to the pool and let it mine for a while - an hour at least. Typically the starting share threshold is high because pools expect a higher hashrate so it may take a while before any shares register, but after a few the pool should adjust the threshold. You may also look into the --suggest-diff command.

2020deception: You did not buy it from GekkoScience. You bought it from a reseller. If you check the order details there should be further info on the actual seller, including some kind of contact info.

Stavroski: Connect to the pool and let it mine for a while - an hour at least. Typically the starting share threshold is high because pools expect a higher hashrate so it may take a while before any shares register, but after a few the pool should adjust the threshold. You may also look into the --suggest-diff command.