[∞ YH] solo.ckpool.org 2% fee solo mining 281 blocks solved!

[citb0in]

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.

[1714268548]

1714268548

[1714268548]

1714268548

[1714268548]

1714268548

[1714268548]

1714268548

[1714268548]

1714268548

[1714268548]

1714268548

[stablepayouts4u]

"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 ?

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.

[Nexus9090]

@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.

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.

[citb0in]

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

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.

[jimbocuzzi]

I saw this article

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

[Gholly]

"the 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 ?

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.

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

[Gholly]

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

[citb0in]

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

of course it is

[g5120u]

"the 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 ?

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.

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

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

[-ck]

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

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.

[Sc0rPs]

Hello all,

 Been using ckpool off & on for a while now, usually have an S9 or something pointing at it. Yesterday decided to run 3PH just for a spin of the wheel... and when I checked miner status on one of the ASICs it read 2 Blocks Found. Man, had me going for a minute there .

 Not sure how or why it reported that, as I don't quite get the depth of these things... just know my best block has to be above the current network difficulty to even "qualify". Just thought it be a funny little story and good time to say hello.

[jinjabjo]

I've just started mining on this with 1.7 GigaHash... Is it even worth killing my gpu to try my luck?

[-ck]

I've just started mining on this with 1.7 GigaHash... Is it even worth killing my gpu to try my luck?

No. GPU mining became pointless with bitcoin over a decade ago.

[jinjabjo]

I just seen this on a youtube video and thought I would give it a go.

[mikeywith]

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

Possible, yes, is it a smart idea? certainly not.

When people refer to "own full node" they usually refer to the node running on their old PC connected to $50 router, which is pretty risky to use, you need a dedicated server with nearly 0% downtime, and you also need very low latency, overall, there is no room for error when it comes to mining, finding a block is pretty difficult and close to impossible with any home miner, adding more risks of losing that block because your PC decided to reboot for a windows update or the cat jumped over the power cord will make things even worse.

If you want to do that for fun and to experience things, go ahead, other than that it's a terrible idea.

[Gholly]

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

Possible, yes, is it a smart idea? certainly not.

When people refer to "own full node" they usually refer to the node running on their old PC connected to $50 router, which is pretty risky to use, you need a dedicated server with nearly 0% downtime, and you also need very low latency, overall, there is no room for error when it comes to mining, finding a block is pretty difficult and close to impossible with any home miner, adding more risks of losing that block because your PC decided to reboot for a windows update or the cat jumped over the power cord will make things even worse.

If you want to do that for fun and to experience things, go ahead, other than that it's a terrible idea.

Isn't EVERYONE here doing this for fun? I would bet the vast majority of the guys on here are lottery miners...<1 Petahash running in the basement.

My question again was simply Technical.....
Does Bitcoin Core / bitcoind support connecting to an ASIC miner without a need to run a copy of CKpool or some other pool software to provide stratum support?

That was my question, not economics.
Thanks

[-ck]

Does Bitcoin Core / bitcoind support connecting to an ASIC miner without a need to run a copy of CKpool or some other pool software to provide stratum support?

no

[Gholly]

Thank you

[citb0in]

Does Bitcoin Core / bitcoind support connecting to an ASIC miner without a need to run a copy of CKpool or some other pool software to provide stratum support?

no

@Gholly: you can run bitcoin cored and a particular CGminer version that allows you to mine against your own bitcoin cored without the need of other pools.

[Gholly]

that's interesting... is it the same CGminer CK wrote - do you have a link i would like top read about it .... i plan on staying here on CKpool but i like check everything out,