Topic: [∞ YH] solo.ckpool.org 2% fee solo mining 256 blocks solved! - page 202. (Read 102489 times)

Sigh....
Please ref https://bitcointalksearch.org/topic/m.24714338
It would be a very very pointless enterprise.... Your share rate would be so incredibly low most pools would treat it as a dropped or offline connection 

In the news today
https://www.hackster.io/news/you-can-now-mine-bitcoin-using-your-vintage-commodore-64-49057d732c47
I know a pool I can test this out on (not ck's)
 

Thanx dude!

The pool no longer has a server in Germany, only one in the U.S, however, o_solo_miner has a passthrough located in Germany


108ms is more than good, there is nothing to worry about.

Why is there no Germany: mine to de.ckpool.org:3333 on this new page?
And i did a ping test to both germany and us pool and both gives me 108 ms, is that good?

I quoted you both because you two have the same concern, don't worry about the timestamp at all, NO, you won't lose a block because your clock is half a minute late/early, you can even mine blocks with a timestamp in that past.

If block 100 is mined at 2:00 AM and you manage to solve block 101 with a timestamp of 1:50 AM, it will still be accepted, there are basically two rules for the timestamp of a block, it can't be more than 2 hours into the future based on your node network adjusted time, and it can't be lower than the median time of the last 11 blocks.

As for the online explorers, some might be showing the timestamp on which they received the block based on their own clock, some will show the timestamp that is in the block itself, clocks are never 100% synced so all this variation is completely normal.

That's true. On the other hand, the timestamps correlate with the data from https://live.blockcypher.com/btc/
I cannot tell which source is more to be trusted to be accurate.

In regards to the deviating timestamps I think there would only be an issue if these were the consequence of the propagation of new blocks to/from the network being too slow, potentially giving another found block precedence.

The timestamp that is used for the mining process is anyway provided by the client and added to the mined block header. If I understood the stratum protocol spec correctly, any timestamp within about a minute is considered valid from the Bitcoin network's perspective.

I just noticed that there are slight deviations (about half a minute) from the timestamps my cgminer reports from the ones on Blockchain Explorers like "BTC.com".
My time settings should be fine, just counterchecked them with "time.is" and the difference is just a few milliseconds.
Anything I have to worry about? Just wanted to make sure everything runs fine. Would be sad if a found Block is rejected by the network because of a bad time stamp 

Thats wrong, bitcoincore does support solo mining.
After the changes in the gbt protocol, cgminer and ckpool could not decode the gbt right, because of the changes made in bitcoincore.
Using bitcoincore 0.18.1 does still work with the last version of cgminer for solo mining. So until no greater change in bitcoincore is made,
you are fine using that for solo mining.
The changes are documented in bitcoincore and could be implemented into cgminer or ckpool for beeing up to date.

who asked about caino pool? not like it matters with two miners but is it really necessary?  knowing the history?
theres plenty of topic if one wanted to mine that way 

Why do you even worry about the nonce thing altogether? each mining instance will get a different template from the pool, and then the miner itself will adjust the extranonce2 as it pleases, and then you have the timestamp which adds up to the making of the Merkel root which creates a whole new world of possibilities, it's good that you want to learn about these things just for the sake of knowledge, but these "problems" are from the past and they have been solved for good, just pick the pool you like and mine on.

I had the same/similar thoughts on this topic recently and came to a concept that works for me (props to -ck for "the rock with the toothpick" image)

Think of solo mining as drilling holes into a huge rock from either side, desperately searching for a single fragment of gold inside. The one who finds it first, may keep it.

The drill is your miner instance. The more hash power you have, the bigger and faster rotating is the drill. There are MANY MANY drills, that are drilling this poor rock all at the same time.

Now you can drill holes sequentially with a bigger drill (by combining your hashing power into a single miner instance). Or have multiple holes drilled in different locations on the rock at the same time, but with a smaller drill (by splitting the hash rate on seperate miner instances).

Each mining instance gets the location info on where to drill with the nonce and extranonce1 value from the solo pool (or bitcoind) and drills there for gold until the self-generated (and continuously incremented) extranonce2 value is exhausted. Which then means, your miner did not find the gold in this location. Then the miner requests a new location and starts drilling there again. The number of locations is near to infinite, so a chance of a collision is near to none. Exactly this drilling job is repeated all over again and again until the gold is found by someone.

The most tricky (and hardest to understand) aspect here is that, while the very same location might be your drill's sweet spot, other drills cannot find anything there. So reusing the same location is not a bad thing in general. (This is due to the fact that each miner creates a different unique input for the hashing.)

A bigger and faster drill will increase your chance to find the gold earlier since you can drill many more holes than others in the same time, but even the small drill next to yours may be the lucky one instead. It's all pure luck in the end, with a known probability though, which may lead to you finding the block in the next instance or never.

All the experts out there, please correct me if I am wrong ofc  

Mining on this pool IS solo mining (KanoPool has that as well as an option). Solo mining just means that you all get all of the rewards and Tx fees minus 2% (-ck's fee) or minus 0.5% (Kano's fee) IF you find a block.

If you mean solo mining to your own personal node - thass another story. AFAIK the more recent versions of Bitcoin Core (the node software) no longer supports that so the pool operators do some addition coding for it to work.

Apologies, quick question and excuse my ignorance. I am looking into solo mining so I was wondering if you what you've suggested is also good for solo mining in order to avoid duplicated nonce guesses?

This is very helpful and much appreciated, will do my homework now.

You are pretty much on-target with your results. The vast majority of shares a miner returns are far below required diff.
At the risk of offending others here, here are some Help links from the pool I mine at:
Worker difficulty
Mining details
There is other good info in the Help section there. The mining process is the same for all pools.

That's good to know. Can you explain a bit about how the pool distributes the work and how difficulty is calculated? For example if the current difficulty to solve a block is 21.8 trillion and the highest difficulty I've achieved is 500million, what does this tell me? Aprreciate your response

No. Assuming they are setup correctly all pools send unique work to all miners connected to them.

hi, thanks so much for the prompt response. If I do it your way I am running the risk of duplicating nonces while trying to solve the block right?

Any particular reason why? Just point them both at the pool using the same payout address or miner name and let the pool itself handle things...