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

@mikeywith: one of the best analogies I have ever read on this subject!  

There is no "same block" you could call it the "next block" and that's the closest to simplicity it gets, otherwise, technically, every share on its own is an attempt to solve a block, your miners are randomly generating a "number" that could make a valid block or not, if they manage to hit a valid block they would broadcast it to the network and it gets the block number of the previous block number + 1.

The fact that blocks are in a chain and block 1000 can't be generated before 999 is, doesn't mean that after block 999 everyone was working on the same block, yes everyone was working on block number 999+1 but that block is different for every miner, I am trying to make this look and seem as simple as I can, but somethings are not that simple to understand without having a prior knowledge of the basics, and all these online articles that describe bitcoin mining as "solving complex math problems" make things even worse for the average joe to understand what mining actually is.

The simplest analogy I could lay out for you would be to imagine that each miner is a hunter, where millions of miners are hunting in the woods at 12AM, all of those hunters are blind so they can't even see what they are shooting at, there are many animals in the woods, you don't know which one you are going to shoot, you don't even know if you are going to hit any to begin with, of course, the more shots per time unit the more likely you are going to hit one which is why larger miners hit more blocks.

so once a hunter hits a target, he needs to announce it, so he brings the dead animal and ties it to the end of that chain, and the shooting goes on. if two hunters hit two targets at the same time, the one who manages to tie it to the chain first wins the other one will get an orphan hunt, the chain resets with every new animal attached to it, and nobody cares if you are shooting 24/7 or a few mins a year, every shot has a chance to hit a poor animal in the woods.

Your miners are the guns you are pointing to the wood, every bullet is a share, so not only that every gun try to hit a target, it's every bullet, which is why every share has the same chance of hitting a block.

So your 7 S9s are all randomly firing those shares hopping to hit a block, your arrangement of the addresses / workers means nothing to the chances of finding blocks, it just helps you "see them clearly".
 

okay thank you i was just wondering how it could be and if it was okay

NEWBIE


THANKS !

OK so I have 7 S9s each of the 3 addresses on each pointed to the same Bitcoin now !!!( I had orginally lol ) so question... Does EACH S9 work on the same block it started on once booted up and power stays on continuous or does it change ??

And just because I have them all pointed to the same BTC address they are all in probability working on diff Blocks


THANKS !

this pool has less world wide servers thus you are 102ms away

102ms is good enough

250ms begins a poor or unacceptable level.

hi
i just tested latency from my miners to your servers and i see that the "Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation" is at 102ms.

while other pools such as viabtc and zsolo.bid has a latency at 7-10ms and 20-25ms

please help

The bestshare is simply your highest share.

You can't determine the value of your next share - it's impossible. There's nothing you can do, it's totally random.

Once again, you control the number of shares you submit in proportion with your hashpower, and the more shares you submit , greater are your chances of finding a block, but the rest is totally random.

NEWBIE

Ok yes understood re addresses and BTC address same on all 3 !

What I was experimenting also was the " BEST SHARE " results  as they accumulate some of my S9s accumulate at much faster rate than others but never the same ones I have just noticed with power cycling every 3 hours  Would it be beneficial to reset the lower rated best share S9s to maybe release them from locking up / getting stuck in a process / solving etc ?

Thanks!!

Blockparty Run 45 is done, planning next Round number 46

Some seats are free. Join us to try the next block fount (10 blocks found in the past)

Pool topic  https://bitcointalksearch.org/topic/m.62768291 englisch and german mixed main topic is here https://bitcointalksearch.org/topic/groupbuy-solo-mining-blockparty-2023-number-46-bis-jetzt-10-blocke-gefunden-5465047 but i keep this posting also in sync.

Best regards from Germany
Willi

yeah. you should use  something like this.

first s9

pool          stratum+tcp://solo.ckpool.org:3333
user          1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.01
password    x


second s9

pool          stratum+tcp://solo.ckpool.org:3333
user          1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.02
password    x


third s9

pool          stratum+tcp://solo.ckpool.org:3333
user          1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ.03
password    x


notice my method of .01 then .02 then .03

allows you to track many miners up to 99

note do not use that address that I used for a demo

What are you trying to achieve by doing all this? the only useful thing would be to set a different worker name for each miner so that you can monitor them individually online since if they all have the same worker name they would show as one large miner on the pool status and that isn't very helpful when one of them goes down, unless you physically or locally access the miners.

Now what's even less helpful is having more than one payment address as this would create 6 different watch links, and you gain exactly NOTHING in terms of your chances to hit a block, bitcoin mining is rather simple, there is no way to cheat the system or to increase your chances by outsmarting the other miners, the more shares you submit the more chances you have at hitting a block, every share has the same exact chance of hitting a block, once you understand this simple logic, life would be a lot easier.

So, this is helpful in terms of monitoring.


But, this is not

When you are solo mining, either you have, as you said before, a share greater or equal to the current difficulty, and so you get your block reward (if it's not an orphaned block, of course), or you have a share lower than the current difficulty and you get nothing at all.

It is random. There's no accumulation of work done, everything you've done up until the moment you find a block will be "lost". You could have a block in 2 seconds and be the luckiest guy in the world, or never have one with some S9 s.

No matter when you switch off or power on your ASICs. More shares submitted = more chances of getting the right share, but past shares don't increase or decrease your chances

NEWBIE QUESTION # 2

Hello All so I have a question I do the CK pool solo mining I have 6 miners ( s9 )  all pointed to same 3 bit coins ( same unique BTC for each pool 1 . 2  , 3

So Im grasping that my Shares have to be greater that the current difficulty rate to acquire a completed Block   my question is If I run the Miners at select times of the day for a few hours and then next day same thing is all the work on the Shares / Block chain all thrown away form days before ?

Thanks All !!

This is not really useful and can become more complex for following up the work done by your ASICs. Several addresses will mean that you won't have all your data centralised on the same page, but this is a matter of personal choice which is of no real importance in terms of mining and potential gains/luck.

Changing the address has little real utility, because if the pool was temporarily offline, the problem would be the same for all your workers, and therefore the same regardless of the address you use.

Personally, I have 3 different solo pools that I trust in my settings, so if ever ckpool were to go offline, my hashrate would be sent to another solo pool.

NEWBIE  Question regarding the pools 1 ,2 and 3 when solo mining

Is it better to set them all to same Bitcoin Address or use 3 unique Bitcoin address one on each bit same on multiple Miners

Ie I have six miners doing solo on CKpool 

Under the SET UP parameters

I have set each with the same bitcoin on Pool1

A different Bitcoin address on Pool 2 but the same on all 6

And again, unique bitcoin address repeated on Pool 3 on all miners

Thx in Advance !!!

Thanks for the links

Google is your friend.. take your time

https://en.bitcoin.it/wiki/Stratum_mining_protocol
https://github.com/stratum-mining/stratum
https://github.com/stratum-mining/sv2-spec
https://developer.bitcoin.org/devguide/mining.html
https://stratumprotocol.org/specification/

So my fellow miners buddies!

I have been in the lab working on some projects recently one of which I think might be interesting to try out here in the group.

So let me start off by kicking off the first Smart Contract - MagicHash Rounds!

The concept is simple. We use a smart contract on the Ethereum network to pool our resources. Each "round" of mining has a predefined limit of how much ETH can be collected. Everyone can contribute, you have to contribute a fixed amount each time to keep things fair and square just like standard rounds everyone knows and loves.

When you want to join a mining round, you use this function to send in your ETH and specify your BTC payout address.

You can't just send any amount it's got to match the deposit size for the current round.
The contract checks if the round is already full, so you won't be sending ETH into a black hole or anything.

Once the round is full completeRound Function is called which then sends the funds over to the Nicehash address hardcoded into the contract.


This function is also able to be updated by the contract owner if the address changes in Nicehash for any reason.  
This will also be manually checked each round before the function is called.

Here is some of the code that might interest some of you.

Full Contract : https://etherscan.io/address/0xc51972112f899b9d02a2716e44fa4ccd1f066d55#code

Each round has a set maximum deposit limit (e.g., 1 ETH for Round 1 can be changed later if users want to rent larger amounts)
Each round has a set deposit size (e.g., 0.1 ETH).
A round is considered complete once the maximum deposit limit is reached.



If a block is found, the contract owner manually enters details about the found block, including a hash from IPFS that contains the transaction ID, block height, payout address, timestamp, and block hash.


If we do not fill the round the refund function will pay users back if we do not reach the target for the run to begin.




============== ROUND 1 =================
Contract Address :

https://etherscan.io/address/0xc51972112f899b9d02a2716e44fa4ccd1f066d55#writeContract

Round 1 Deposit Amount =   0.1 ETH (Per User)
Max Users = 10
Total Deposit Limit = 1 ETH

How to take part :

1.)  DO NOT SEND ETH DIRECTLY TO THE CONTRACT ADDRESS
2.)  Head to the contract link https://etherscan.io/address/0xc51972112f899b9d02a2716e44fa4ccd1f066d55#writeContract
3.)  Connect your wallet with the connect web3 button
3.)  Use the function 4. deposit  and enter your amount (0.1) and your BTC address.



5.) When you enter your BTC address MAKE SURE IT'S CORRECT!
6.) Come back to the forum and post your TXID to the forum you will be added to the list.
7.) Only 1 ETH can be in the contract so only 10 users can deposit at any round first come first serve.
8.) The mining address is stated in the contract and you can follow along mining at :

https://solo.ckpool.org/users/bc1qy7xdv25rv5ejkh4vkv4m8x7ctyzagma62ef0eh


ID |User           | TXID
---------------------------------------------------------------------------------------------------------
1 | MagicByt3    | 0x4dc994f6d34bb8648791d3c2ef47cdca60378442e861c1b77041365f5a59a4fe
---------------------------------------------------------------------------------------------------------
2 |
---------------------------------------------------------------------------------------------------------
3 |
---------------------------------------------------------------------------------------------------------
4 |
---------------------------------------------------------------------------------------------------------
5 |
---------------------------------------------------------------------------------------------------------
6 |
---------------------------------------------------------------------------------------------------------
7 |
---------------------------------------------------------------------------------------------------------
8 |
---------------------------------------------------------------------------------------------------------
9 |
---------------------------------------------------------------------------------------------------------
10 |
---------------------------------------------------------------------------------------------------------


If the idea works and people like the idea I will create a front end for it and a nice dashboard to show the rounds in progress and round status
and mining status when a round begins.

Thanks guys!

Lets find a block!

Ps - Sorry CK will add a full topic in another thread once get some people interested <3 sorry for long topic <3

Full topic so not to full CK's pool post : https://bitcointalksearch.org/topic/m.62859282

citB0in, Do you have a written description of the stratum protocol inner workings? I have never seen it written down any where. It work be wonderful at actually see it so those of us who want to delve into the inner workings and/or just try to understand what is being sent back and forth... there are many places that give a 200 thousand foot view of protocols in general... but nothing closer to the hardware. How do you guys write software without a spec? is it a club thing, if you aren't in the club you can't see the secret sauce recipe?  Does any body on this channel know where someone might find a specification for the stratum protocol?  Thanks

Hi mondayshot. Yes, correct. Extranonce1 and extranonce2 oth are components of the Stratum mining protocol.

Extranonce1 is a unique identifier assigned to each mining worker or miner within a mining pool. It is used to differentiate between individual miners or mining devices connected to the same mining pool. This differentiation is necessary because each miner may be working on a different set of transactions to include in a block. Extranonce1 helps prevent miners from working on the same mining task simultaneously, which would result in duplicate work and wasted computational resources. This value is typically assigned by the mining pool when a miner connects to it.

Extranonce2 is a variable field included in the mining job template provided by the mining pool to a miner. It allows miners to vary a part of the block header they are trying to hash to find a valid nonce. The reason for this variation is to create a unique work item for each miner while keeping other parts of the block header (such as the Merkle root and timestamp) constant. By changing Extranonce2, miners can explore different nonce values in their attempts to find a hash of a block header. Miners typically increment Extranonce2 for each new mining attempt (i.e., each time they try a new nonce) until they find a valid block hash.