Pages:
Author

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

hero member
Activity: 595
Merit: 506
Congrats to the miner!

Looks like it was 40 Petahash?

legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
Congratulation to 36AisvWi1UiwLTeTZxLzindAkorqeUc3tT for solving Block 858,978.

diff: 197522447695680 @ ~15-35P
Smiley
jr. member
Activity: 72
Merit: 3
Wow, congrats! Before 100% too

Bravo anon miner! Bravo CK & CK pool!

It's been a good year here for a handful of people.
newbie
Activity: 13
Merit: 0
Congratulations!
member
Activity: 259
Merit: 85
So many numbers and so little time
Well what do you know, looks like I spoke too soon Cheesy

Congratulations whoever found block 858978

member
Activity: 259
Merit: 85
So many numbers and so little time
Far too quiet around here...

About time we hit another block don't you think?



newbie
Activity: 1
Merit: 0
Hi all, new to mining. Sorry if this question is answered somewhere else but I saw conversations going back to 2014 and can't possibly read it all.
When solo mining with CK pool is there a way to verify which miner solved the block? What I'm trying to understand is if there is a way to verify if my miner finds a block. At this point (with limited understanding) I'm just point hash and CK pool and hoping they are trustworthy and will pay out if my miner gets lucky.

On a separate note is there a way to put a message in the found block? I see the last block (853742) from Solo CK pool and the coinbase tag and OP_RETURN data is full of gibberish. It would be cool if each solo miner could put their own notes in those fields (understandably this might mean more overhead for CK pool and if that's the reason why we can't that's totally fair).

Cheers!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
hero member
Activity: 504
Merit: 1065
Crypto Swap Exchange
Gotcha!

I see there's some lucky people on here that already hit a block. Any particular reason why ckpool doesn't display Block Height and Last Found on miningpoolstats.stream?

You can use this link to see the last blocks found:

https://mempool.ninja/mining/pool/solock
newbie
Activity: 6
Merit: 2

The pool gives every worker effectively unlimited unique work so they can't overlap.If you managed to write your own broken mining software that redid the same hashes somehow the pool would reject them. If the pool is reporting your hashrate correct there are no dupes.

Gotcha!

I see there's some lucky people on here that already hit a block. Any particular reason why ckpool doesn't display Block Height and Last Found on miningpoolstats.stream?

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hello ck
The pool is working as well as before, thank you.
And there is no problem Wink Kiss
I haven't changed a single thing on the pool in years, but sure.
newbie
Activity: 19
Merit: 0
Hello ck
The pool is working as well as before, thank you.
And there is no problem Wink Kiss
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Hi all!

Me and two buddies joined CK Pool this month with a total of 9 Avalon Nanos. At this moment we can just hope that eventually the total of 36 TH/s hits a block.
I have a question though related to the process of generating hashes with different units to a single wallet:
When I mine with verious units to a wallet, do the units know what hashes were already tested by requesting them at the pool or do the miners just test if the generated hash works?
Would the share be rejected if two units post the same hash to the pool? Do units know what hashes the other units have already sent?
From what I understand a hash is generated from a textblock of the previous hash, so there can be millions and billions of different hashes for the same text block.
I'm just asking in theory.

Thanks in advance and lucky mining to everyone. May Satoshi be with you!

The pool gives every worker effectively unlimited unique work so they can't overlap.If you managed to write your own broken mining software that redid the same hashes somehow the pool would reject them. If the pool is reporting your hashrate correct there are no dupes.
newbie
Activity: 6
Merit: 2
Hi all!

Me and two buddies joined CK Pool this month with a total of 9 Avalon Nanos. At this moment we can just hope that eventually the total of 36 TH/s hits a block.
I have a question though related to the process of generating hashes with different units to a single wallet:
When I mine with verious units to a wallet, do the units know what hashes were already tested by requesting them at the pool or do the miners just test if the generated hash works?
Would the share be rejected if two units post the same hash to the pool? Do units know what hashes the other units have already sent?
From what I understand a hash is generated from a textblock of the previous hash, so there can be millions and billions of different hashes for the same text block.
I'm just asking in theory.

Thanks in advance and lucky mining to everyone. May Satoshi be with you!
hero member
Activity: 504
Merit: 1065
Crypto Swap Exchange
Hi i am new here and with minining is right Statumuser:  btcwallet.Workername_1 ?
to give a name for difrent miners ?

Yes, you can use either "." or "_" to name your workers.

For example:
wallet.worker1
wallet_worker2

and how i can see if i solve a  block ?

Your bestshare needs to be > or = to the current network difficulty (though the block could still be orphan but unlikely)
+ most ASICs interfaces show "BlockFound=1" (or something similar) when you find one.
+ the coins in your wallet waiting for their 100 network confirmations and people congratulating your wallet address in this thread
newbie
Activity: 1
Merit: 0
Hi i am new here and with minining is right Statumuser:  btcwallet.Workername_1 ?
to give a name for difrent miners ?

and how i can see if i solve a  block ?
hero member
Activity: 1241
Merit: 623
OGRaccoon
I spotted the call for it to change set difficulty but it seems to keep doing 10k diff for some time after this.

Either it flips to the lower or it sometimes stays on 10k untill the next set diff message comes but that can sometimes be some period of time.

should we not Dequeued the work on this call?

Code:

₿ (291161) bm1366Module: RX Job ID: 38
₿ (291161) asic_result: Nonce difficulty 264.60 of 10000.
₿ (291691) bm1366Module: RX Job ID: 38
₿ (291691) asic_result: Nonce difficulty 54983.11 of 10000.
₿ (291691) stratum_api: tx: {"id": 12, "method": "mining.submit", "params": ["bc1***.***, "648516380013d80c", "0500000000000000", "66bb9e77", "0f860342", "0fe28000"]}
₿ (291811) stratum_task: rx: {"params":[858],"id":null,"method":"mining.set_difficulty"}
₿ (291811) stratum_task: Set stratum difficulty: 858
₿ (291811) stratum_task: rx: {"result":true,"error":null,"id":12}
₿ (291821) stratum_task: message result accepted
₿ (292671) bm1366Module: RX Job ID: 40

Should we not do create_jobs_task: New Work Dequeued here if the stratum message is to move to 852 diff?

₿ (292671) asic_result: Nonce difficulty 282.49 of 10000.
₿ (293201) bm1366Module: RX Job ID: 40
₿ (293201) asic_result: Nonce difficulty 481.34 of 10000.
₿ (293741) bm1366Module: RX Job ID: 40
₿ (293741) asic_result: Nonce difficulty 326.37 of 10000.

Code contines for some time at 10k diff before the switch down to the stratum set_difficulty.


member
Activity: 259
Merit: 85
So many numbers and so little time
CK can I ask why it takes so long for the diff change sometimes up to 10 min or more for Bitaxe boards?

Takes nearly 11 min from connecting before the pool adjusts the diff down from 10k to normally for bitaxe between 320-550 range is what I see the boards land is most of the time.


I've not used Bitaxe before, does it send the suggested diff back to the pool like CGMiner does?

With a Gekko Science compac F, if I set the suggested diff to say 600 in CGminer, within a few seconds of connecting to the pool the rate is adjusted to that what was requested.

Perhaps the Bitaxe firmware doesn't do this?



member
Activity: 76
Merit: 18
member
Activity: 456
Merit: 16
CK is legit and an OG in the space.
Just GTFOH if you're going to throw unfounded and inaccurate accusations.
Pages:
Jump to: