|
So far it seems to be in a nice home with loving parents.
|
|
|
|
Glad to help. Good luck, and hopefully you'll knock out a block and win some BTC  |
|
|
|
That's weird... I'm looking at it right now... my gear is all connected, and I see apederzoli is pushing a good-sized rental currently. Let me take a look at the logs for you... EDIT: OK, I see your rental connect... but it doesn't submit any shares, and eventually disconnects. 2016-05-05 19:38:47 [Pool] [bitcoin] (Thread 7) Authorized borachinua
...
2016-05-05 19:49:01 [Pool] [bitcoin] (Thread 7) Connected timed out for borachinua: last submitted a share was 614 seconds ago
Your last actual submitted share: 2016-05-05 18:48:55 [Pool] [bitcoin] (Thread 3) Share accepted at diff 1042/1330.40491620 by borachinua
EDIT2: I just checked the "Pool Verificator" on NH for both the EU and US stratum servers on ports 3333 and 3334. Everything came back as good. |
|
|
|
¡Viva la Batalla de Puebla! Good luck to everyone |
|
|
|
|
110TH? I know there have been blocks solved here with far less hash than that. I remember a guy hit with an S3. I don't remember the 300G hit that -ck mentioned, but for sure plenty of folks have hit with less than 110T.
|
|
|
|
I try to keep it entertaining . When I was posting today's promo I was originally going with "share greater than 5T"... but figured that would scare people... OMG!!! I have to get a 5T share??? So, 500G it is. |
|
|
|
You depend on someone else to feed your ASIC work and blocks
Yes, pools feed your miners work. I guess there's no simple way to filter blocks before they're sent to your ASIC - but the code level action of this is confusing to me.
What do you mean by "filter blocks"? You don't send blocks to your ASIC. In fact, your miners have no concept of a block whatsoever. I guess I just don't understand how the "block hit" process happens since I don't think a single ASIC can do a whole block calculation (can it?).
The "block hit" process happens if your miner provides a solution to the SHA256d hash which satisfies the network difficulty. There is no such thing as "whole block calculation". There is only SHA256d hashing. I guess ck gives you a direct connection to the stratum. So it's like you're running your own Btc node. But if so, how can ck siphon off his 0.5% upon success?
Because he's creating the block (just like on my pool, I create the block). As such, I can define what transactions are in the block, including the coinbase transaction (the one that defines how/where the 25 BTC block reward is distributed). On his pool, he defines the coinbase transaction as "99% of the reward + transaction fees goes to address XXXXX and 1% of the reward + transaction fees goes to address YYYY". So I know there's some aspect I'm not understanding here. (If I understood C I guess I could read the kano code.) For instance, who handles block difficulty if you're "directly connected to stratum" as ck says? I thought difficulty was the number of zeros at the beginning of the hash, and was set by Btc current difficulty. (see? noob.)
The network handles block difficulty. All difficulty means is, "the solution you provide must meet or beat this value in order to accept your block on the chain". |
|
|
|
|
Unfortunately, the fourth was not strong... but is that going to stop us? Hell no! It's Cinco De Mayo! Half-priced margaritas for everyone because the Mexicans, against overwhelming odds, defeated the French invaders.
So, let's celebrate here, too. 1BTC to everyone who solves a block today.
Now for the kicker...
If the block-solving share is 500G or greater, you get another 1BTC.
|
|
|
|
Time to kick it up a notch for the last hour of the promo... If you find a block, and the share that solves it is greater than 198,000,000,000, I will give you an additional 1.980 BTC on top of the 1.977 BTC for finding the block. May the fourth be with you |
|
|
|
Definitely cool pieces of history to have |
|
|
|
|
4 hours left... who is strong with the fourth?
|
|
|
|
|
Congrats on hitting 410235!
|
|
|
|
Definitely enjoying the Star Wars references in the replies  And, about 9PH currently hashing away on the pool... |
|
|
|
Good luck to you all! May the fourth be with you . |
|
|
|
|
Actually, it's sometime between 1/11 and 2/14.
Here's the math broken down:
(178,659,257,773 * 5) - (178,659,257,773 * .2252) = 853062224014.5204
853062224014.5204 represents how many shares from the previous blocks are included in the 5N. Start subtracting...
853062224014.5204 - 28,386,020,800 = 824676203214.5204
824676203214.5204 - 198,717,154,987 = 625959048227.5204
625959048227.5204 - 199,254,758,327 = 426704289900.5204
426704289900.5204 - 10,544,894,813 = 416159395087.5204
416159395087.5204 - 22,355,511,995 = 393803883092.5204
393803883092.5204 - 139,379,877,102 = 254424005990.5204
254424005990.5204 - 217,761,509,429 = 36662496561.5204
36662496561.5204 - 151,774,724,299 = -115112227737.4796
Ahhh... so sometime between block 392809 and 398354. Right around 75.8% of the way through that round. The round took about 34 days, so right around Feb 6.
|
|
|
|
|
There is no correlation at all.
|
|
|
|
Jonny, anyway to tell from the data on the pool site where we are on 5N? Kinda looking for the shift or shift graph page that Kano has. Easy to see where your 5N is. Since the hash rate has a high variance, hard to figure out if my first shares are still in 5N or dropped off. Don't need you to do any enhancements, just provide some guidance on what existing data can be used to get a rough idea of individual 5N standings.
Thanks,
You can kind of fake it. Take a look at the current round. You can see we're currently 16.75% done. That means we've got about 29925425677 shares this round. Subtract that from 5 times the current diff and you get 863370863186. Knowing that, you can kind of work your way backwards. Look at the "Statistics->Pool" section at the blocks found. Start subtracting the actual shares and you'll eventually get to 0 or below. The 5N window would therefore be somewhere after that previous block. Remember, that's just an estimate. Hopefully I'll get some time to write some code to give a better answer |
|
|
|
I've realized that the VarDiff is actually chasing the hash rate provided... NOT the pools problem -- to the best of my knowledge... (Although I have questioned the VarDiff in the past on this thread)... I had MAJOR rejected shares earlier -- and THOUGHT that I had solved that problem -- so now I have THIS problem... I'll give up -- and either, at some point, try and desegregate -- or, just give up... Right now, I don't have a whole lot of extra time on my hands... That may change in a week or two... BEST OF LUCK to EVERYONE on the SUPER COOL PROMO going on right now!!! And -- I shouldn't quote you -- as your "may the fourth be with you" is STILL echoing throughout the thread!!! I'm confused as to what your problem is. As Phil has suggested, and as I emailed you, do not put all of your miners into a single worker. Use multiple workers, or, use a proxy on your end and send a single stream to the pool. I also said I would gladly create and open up a fixed diff port for you if you provided me the hash rate so I could calculate a good diff for it. I'm also confused by what you mean regarding vardiff chasing the hash, and what your questions about vardiff are. You can also try to use port 3334. The diff starts at 65535. Since I have pushed well over 10PH rentals through that port with multiple connected bridges, there should be no problems at all. |
|
|
|
|
Show Posts
