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

There's no such thing. It's just as much work dealing with diff 1 and cpu miners as it is diff 1 quadrillion and quantum computers.

Another situation is that when the computing power of the pool can no longer keep up with the future difficulty, it cannot efficiently and continuously produce the blocks with luck. From the mine pool manager to the miners, maybe someone knows what it is like problem or result

of course it is

Is it even possible to Solo mine direct to a full node any more?

I agree bitcoind on a full node handles collecting transactions and forming the base work block in form of the GBT (GetBlockTemplate) data which is pulled by the pool, But I was under the impression that the pool software had to construct the block header using GBT to be worked on by the miners in the pool, and on CKpool specifically this is a unique block header for each different payout address (miner) because it is included in the header, this facilitates CK's unique function of not receiving the block reward and allowing it to be paid directly to the miner wallet by the network and only gets paid his 2% directly. 

Thats my understanding...
I was hoping to get a better feel for what is actually sent back and forth between the pool software and the miners... there is little online that actually describes the protocol and the data structures,  acknowledgements  - how does the pool know the miner needs more data ? does it do a pull request or something? If a miner finds a block how does it tell the pool?
You know just some mild curiosity about just what the hell is going on in there ... beyond "Yup it works, look away before it sees you and stops working" 🤨
Thanks

I saw this article

https://beincrypto.com/solo-bitcoin-miner/

In my comment with miner I did mean = person using an ASIC miner and trying his luck to hit a block

In case of a hardware miner that consists of several chips, I guess the load is distributed to each single ASIC chip. But this is just an assumption, I am not sure. Certainly you will get more accurate results soon from other users.

Hi,

Sorry jumping in on your thread, but you sparked a point of interest for me.

You say "all miners work on their own block", is a miner considered a single ASIC or group of ASICs?

In the case of say an Antminer S17, where each board has something like 114 ASICs per hash board (so 342 ASICs in total), is a single block job divided up in parallel to those 342 ASICs or is it a unique block assigned for each individual ASIC in the miner?

I guess I'm asking, what is the division of labour where a miner has lots of ASICs and what decides the distribution of that work?

Thanks

G.

In practice, miners & mining pools aren't actually building blocks & they never touch the mempool nor build/verify any transaction besides the coinbase - bitcoind handles all that. Handling Fees, signatures, etc is the job of bitcoind. By the time the pool process received the getblocktemplate() response - the block is already built & verified - besides the coinbase.

What pools do is keep track of miner stats, handle their networking & if a share reaches the target - tell bitcoind about it, which is done via the stratum protocol, which bitcoind has 0 idea about & is much more resource intensive than block verification/construction.

yes, that's correct. Sorry for misunderstanding. We're talking about solo pool What I said is valid for a solo miner on its own bitcoin full node.

"he miner fetches the transactions from the pool and thus fills the work pool locally on the miner.",..?

I thought the pool created the current block header  using transactions from the MemPool, not the miner... I thought the miner only spun through the hashing for the current unique black header/nonce/extra nonce range given to them by the pool ?

@Gholly: all miners work on their own block, they have unique tasks. Even if a block has been solved and confirmed on the network, individual miners continue to work on the constantly updating tasks. The miner fetches the transactions from the pool and thus fills the work pool locally on the miner. The complete nonce range is completely run through in fractions of a second at the ASIC speeds available today. That is why the extra nonces exist, so that the miner can be supplied with work without gaps.

-CK
Thank You for the answer,
I understand it makes no real difference, Just had the thought and wondered if everything started from the beginning every time(new block)... it was just a thought.

1 correct
2 nonce happens so quickly the entire range is always done by hardware. Extranonce is set by pool and also incremented by hardware, reset with every work update
3 all the churn handled by miner

None of this makes any difference to probability.

philipma1957,
Was that intended as a response to my question for CK?

I understand pools and ASICs and have been mining for years solo and on pools .... I was asking detailed questions about this specific pool software and how it treats the Nonce/ExtraNonce and related variable fields in the header, per user, from block to block and what it sends to the miner itself.
I was hoping for a little input from the master himself seeing that he wrote the pool software and the base software that runs in most of the miners today.

Thanks away

 

your miner is spinning a code created wheel of fortune.

you are making an effort to spin higher than 50trillion and change faster than all miners pointed to all pools for the BTC block chain.

Ck pool acts like a sorting device for a spin higher than 50 trillion plus

if you do it submits it and you get a block.

CK if you will, I have a few questions about how the pool works.

-As I understand on CKpool each miner is mining their own version of the current block. Because the Coin base transaction is preloaded with each miners wallet address and the pool wallet with its %fee it has to be differant. The rest of the transactions are the same in all the other miners blocks ... this makes the block we work on uniquely different from everybody else's work block ... correct?

Does the pool restart the nonce/extra-nonce/version bits/miner signature variables to zero every time the network/(pool?) moves on to the next block to solve every 10 minutes? or does the basic nonce variables continue basically where they let off from the last block?

-How much of this nonce related churn is handled by the pool and what is actually handed to the miner (asic) to do? I believe most ASICs still use your CGminer as at least the basis of their internal software. I have combed through bitcoin documents  online and reviewed some of the your pool source code (beyond me at this point, its been 40 years since i programmed much in C),but so much of the interaction between the pool and the miner isn't well described online or I just can't understand it... I was hoping for someone of great knowledge such as yourself to enlighten me a bit.

If you can give me a very basic pool to miner flow narrative/explanation, I would very much appreciate it.
Thank you

At least few seniors who can continue to submit 1.944.392.199.944 shares in the same account have achieved it,
 and they are still working hard at 12 digits
 

How long was that miner mining for that just found the block of Bitcoin?

Yes we hope that also and just for the info.

For our last block in the Blockparty Run we start 38 runs and submitted 486.455.389.518.928 shares to get a block by a diff from 43.551.722.213.591.
And we had a best share with high from 100.571.298.452.432

so the actual unknown block finder is very lucky with only 1.944.392.199.944 submitted shares and a best share from 166.457.402.539.689

Fingers crosst for our running longtime runs and the upcoming block partys

Best regards,
Willi