Bitcoin Forum
December 03, 2016, 04:52:14 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 [294] 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 ... 426 »
  Print  
Author Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers  (Read 828331 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 03, 2014, 12:00:45 AM
 #5861

Sounds like Anotherhost has a really, really bad connection.  There's really nothing I can see from the logs.  Your miner is working, the connection is just flakey as hell, and it isn't coming from this end.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
1480740734
Hero Member
*
Offline Offline

Posts: 1480740734

View Profile Personal Message (Offline)

Ignore
1480740734
Reply with quote  #2

1480740734
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480740734
Hero Member
*
Offline Offline

Posts: 1480740734

View Profile Personal Message (Offline)

Ignore
1480740734
Reply with quote  #2

1480740734
Report to moderator
jarhed
Sr. Member
****
Offline Offline

Activity: 322



View Profile
February 03, 2014, 01:33:41 PM
 #5862

Hey eleuthria, I'm about to .gif all your webgame MMORPG styled characters.
Idea is to articulate trolled answers via animated gestures.

eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 03, 2014, 07:59:40 PM
 #5863

Hey eleuthria, I'm about to .gif all your webgame MMORPG styled characters.
Idea is to articulate trolled answers via animated gestures.



Did you save them all?  Last I checked, BitMonsters is unresolvable, took down that server a long time ago (for now).  Either way, would prefer to not have them turned into meme/troll gifs.  I do eventually plan to use those art assets for something.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
jarhed
Sr. Member
****
Offline Offline

Activity: 322



View Profile
February 03, 2014, 09:05:46 PM
 #5864

Hey eleuthria, I'm about to .gif all your webgame MMORPG styled characters.
Idea is to articulate trolled answers via animated gestures.



Did you save them all?  Last I checked, BitMonsters is unresolvable, took down that server a long time ago (for now).  Either way, would prefer to not have them turned into meme/troll gifs.  I do eventually plan to use those art assets for something.

Only the ones posted here earlier.

For whatever reason I woke this morning with an image of your avatar throwing up a rhetorical middle finger or just waving both hands in the air whenever BTCGuild owns the chain.

So far only your avatar was prep for animation.
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 12:22:52 AM
 #5865

I've noticed when the pool luck is low the website appears to report my hashrate as low too (after a run of bad luck - like now)
When I check my Ant it disagrees

Right now website says 165GH/s for my Ant worker
The Ant says 185 GH/s

Just wondering why

I've noticed it a few times over the last week, always when pool luck is extended bad run

EDIT : Then perfect timing pool mines a block

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 04, 2014, 12:25:07 AM
 #5866

I've noticed when the pool luck is low the website appears to report my hashrate as low too (after a run of bad luck - like now)
When I check my Ant it disagrees

Right now website says 165GH/s for my Ant worker
The Ant says 185 GH/s

Just wondering why

I've noticed it a few times over the last week, always when pool luck is extended bad run


Your ant miner includes rejected shares and hardware errors.  Additionally, the pool dashboard is an estimate based on accepted shares, while your local miner is actual hashing speed.  The average on your Dashboard will always be +/- 5 to 10% of your actual hash rate (even further off if you have HW errors and/or lots of invalids).  As for "always when the pool luck is extended bad run", this is called selective bias.  You see the same fluctuation regardless of pool luck, but you're trying to associate completely independent events.  tl;dr:  Your brain lies to you.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 12:34:27 AM
 #5867

Your ant miner includes rejected shares and hardware errors.  Additionally, the pool dashboard is an estimate based on accepted shares, while your local miner is actual hashing speed.  The average on your Dashboard will always be +/- 5 to 10% of your actual hash rate (even further off if you have HW errors and/or lots of invalids).  As for "always when the pool luck is extended bad run", this is called selective bias.  You see the same fluctuation regardless of pool luck, but you're trying to associate completely independent events.  tl;dr:  Your brain lies to you.

My rejected and HW are very small (591 & 46 resp)
Have 0 stale but over 40,000 discarded versus more than 210,000 accepted (always around 20%)

Is there something I can do to improve the discarded ? What are they ? Where can I read up on it ?

Guess I do investigate more when luck is low ...

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 04, 2014, 12:36:03 AM
 #5868

Your ant miner includes rejected shares and hardware errors.  Additionally, the pool dashboard is an estimate based on accepted shares, while your local miner is actual hashing speed.  The average on your Dashboard will always be +/- 5 to 10% of your actual hash rate (even further off if you have HW errors and/or lots of invalids).  As for "always when the pool luck is extended bad run", this is called selective bias.  You see the same fluctuation regardless of pool luck, but you're trying to associate completely independent events.  tl;dr:  Your brain lies to you.

My rejected and HW are very small (591 & 46 resp)
Have 0 stale but over 40,000 discarded versus more than 210,000 accepted (always around 20%)

Is there something I can do to improve the discarded ? What are they ? Where can I read up on it ?

Guess I do investigate more when luck is low ...


Discarded is a meaningless stat for Stratum & GBT.  Ignore it completley.

EDIT to explain what it is:  In getwork days, the pool provided you a single unit of work, you finished it, and asked for more.  Discarded was a figure of how much work you had asked for that you never got to use due to longpolls making it obsolete.  In GBT/Stratum, pools don't provide you with a unit of work, but they provide you with a template to make work locally.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 12:38:22 AM
 #5869

Ok thx  Smiley

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 01:07:01 AM
 #5870

EDIT to explain what it is:  In getwork days, the pool provided you a single unit of work, you finished it, and asked for more.  Discarded was a figure of how much work you had asked for that you never got to use due to longpolls making it obsolete.  In GBT/Stratum, pools don't provide you with a unit of work, but they provide you with a template to make work locally.

Is there a good plain english write up explaining pools and how they operate or is it all programmer-speak gobbledegook ?

My inclination was that a pool just divided the potential solution space amonst live workers and gave them alll something to do
Is that anywhere near correct ?

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
mdude77
Legendary
*
Offline Offline

Activity: 1358


View Profile
February 04, 2014, 01:12:02 AM
 #5871

EDIT to explain what it is:  In getwork days, the pool provided you a single unit of work, you finished it, and asked for more.  Discarded was a figure of how much work you had asked for that you never got to use due to longpolls making it obsolete.  In GBT/Stratum, pools don't provide you with a unit of work, but they provide you with a template to make work locally.

Is there a good plain english write up explaining pools and how they operate or is it all programmer-speak gobbledegook ?

My inclination was that a pool just divided the potential solution space amonst live workers and gave them alll something to do
Is that anywhere near correct ?

That's pretty close to it.  Then it divides the rewards up among the workers in some sort of proportional manner equal to the work provided.  Which proportional manner used is in the fine details.  Most are pretty fair.  Some are subject to abuse.  The one used here is one of the fair ones.

M

MMinerMonitor author, monitor/auto/schedule reboots/alerts/remote/MobileMiner for Ants and Spondoolies! Latest (5.2). MPoolMonitor author, monitor stats/workers for most pools, global BTC stats (current/nxt diff/USD val/hashrate/calc)! Latest (v4.2) 
Buyer beware of Bitmain hardware and services.
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 04, 2014, 01:32:14 AM
 #5872

EDIT to explain what it is:  In getwork days, the pool provided you a single unit of work, you finished it, and asked for more.  Discarded was a figure of how much work you had asked for that you never got to use due to longpolls making it obsolete.  In GBT/Stratum, pools don't provide you with a unit of work, but they provide you with a template to make work locally.

Is there a good plain english write up explaining pools and how they operate or is it all programmer-speak gobbledegook ?

My inclination was that a pool just divided the potential solution space amonst live workers and gave them alll something to do
Is that anywhere near correct ?


Each hash a miner does is using a different blob of data.  A single change in a single bit will produce a completely different hash, with no deterministic way to know how it will change.  To prevent miners from repeating work, pools take a template of work, and increment a pool-side counter for each miner's work.  This means the template each miner receives is slightly different, so that they will produce completely different hash results.  Miners then take this template and have three values they can change:

1) ExtraNonce - A piece of the coinbase (payment transaction) that allows for a miner to increment a counter.  Most pools use 4-bytes for this value, meaning ~4.2 billion possible increments.
2) Nonce - Another 4-byte counter, this is part of the block header.  It has ~4.2 billion possible values as well.  You can use up ~4.2 billion nonces (~4.2 Gigahashes), then increment the ExtraNonce by 1, which allows you to try all 4.2 billion Nonce values again.
3) nTime - This is a timestamp part of the block header.  It *can* be altered within certain limits.  Each change in this would be another 4.2b x 4.2b possible hash results.  Most miners do not increment nTime anymore because there is no reason to alter timestamps with how much work can be generated by default.


By changing a single bit on any of those 3, you get a completely different hash.  There is also the pool side counter for each miner so there is no overlap, and then each pool has different payout addresses so no pool has overlapping hashes either.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
Taugeran
Hero Member
*****
Offline Offline

Activity: 658


CCNA: There i fixed the internet.


View Profile
February 04, 2014, 01:55:01 AM
 #5873

EDIT to explain what it is:  In getwork days, the pool provided you a single unit of work, you finished it, and asked for more.  Discarded was a figure of how much work you had asked for that you never got to use due to longpolls making it obsolete.  In GBT/Stratum, pools don't provide you with a unit of work, but they provide you with a template to make work locally.

Is there a good plain english write up explaining pools and how they operate or is it all programmer-speak gobbledegook ?

My inclination was that a pool just divided the potential solution space amonst live workers and gave them alll something to do
Is that anywhere near correct ?


Each hash a miner does is using a different blob of data.  A single change in a single bit will produce a completely different hash, with no deterministic way to know how it will change.  To prevent miners from repeating work, pools take a template of work, and increment a pool-side counter for each miner's work.  This means the template each miner receives is slightly different, so that they will produce completely different hash results.  Miners then take this template and have three values they can change:

1) ExtraNonce - A piece of the coinbase (payment transaction) that allows for a miner to increment a counter.  Most pools use 4-bytes for this value, meaning ~4.2 billion possible increments.
2) Nonce - Another 4-byte counter, this is part of the block header.  It has ~4.2 billion possible values as well.  You can use up ~4.2 billion nonces (~4.2 Gigahashes), then increment the ExtraNonce by 1, which allows you to try all 4.2 billion Nonce values again.
3) nTime - This is a timestamp part of the block header.  It *can* be altered within certain limits.  Each change in this would be another 4.2b x 4.2b possible hash results.  Most miners do not increment nTime anymore because there is no reason to alter timestamps with how much work can be generated by default.


By changing a single bit on any of those 3, you get a completely different hash.  There is also the pool side counter for each miner so there is no overlap, and then each pool has different payout addresses so no pool has overlapping hashes either.


just to give an estimate. using Eluethria's numbers. BTCGuild and most pools send a new work item every 30 seconds.

supposing a miner did still roll ntime, to roll ntime from 0x00 to 0x01 in 29 seconds would require ~640 Phash/second or ~26 times the current total network hashrate.

the software increments in this order:

Code:


Psuedocode:
for(ntime = 0; ntime <= 2^32; ntime++)
{
    for( extranonce = 0; extranonce <= 2^32; extranonce++)
    {
        for( nonce = 0; nonce <= 2^32; nonce++)
        {
           GenerateBlockHeader(ntime, extranonce, nonce);
           Hash();
    
        }
    }
}


it runs through the nonce loop 2^32 times then steps out one, increments extranonce, then runs the nonce 2^32 more. this goes on 2^32 times then steps out to the ntime loop, increments ntime, then steps back in to the nonce loop.

repeat until either a new work is sent from pool, we find a block, or ntime is exhausted.

math:
(Extranonce * Nonce) / hashrate = ntime_increment

(2^32 * 2^32 ) / x = 29

this yields x = 6.3609×10^17

Bitfury HW & Habañero : 1.625Th/s
tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1
Come join Coinbase
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 01:59:37 AM
 #5874

Each hash a miner does is using a different blob of data.  A single change in a single bit will produce a completely different hash, with no deterministic way to know how it will change.  To prevent miners from repeating work, pools take a template of work, and increment a pool-side counter for each miner's work.  This means the template each miner receives is slightly different, so that they will produce completely different hash results.  Miners then take this template and have three values they can change:

1) ExtraNonce - A piece of the coinbase (payment transaction) that allows for a miner to increment a counter.  Most pools use 4-bytes for this value, meaning ~4.2 billion possible increments.
2) Nonce - Another 4-byte counter, this is part of the block header.  It has ~4.2 billion possible values as well.  You can use up ~4.2 billion nonces (~4.2 Gigahashes), then increment the ExtraNonce by 1, which allows you to try all 4.2 billion Nonce values again.
3) nTime - This is a timestamp part of the block header.  It *can* be altered within certain limits.  Each change in this would be another 4.2b x 4.2b possible hash results.  Most miners do not increment nTime anymore because there is no reason to alter timestamps with how much work can be generated by default.


By changing a single bit on any of those 3, you get a completely different hash.  There is also the pool side counter for each miner so there is no overlap, and then each pool has different payout addresses so no pool has overlapping hashes either.

Thanks Eleuthria - takes a bit of digesting
So a 2 TH/s miner running at the full 2 TH/s would require ~2,100 secs to try all 4.2 billion hashes (Extranonces) for a single nonce setting and a single nTime ?
.... unless of course it got a hash result lower than the target



Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 04, 2014, 02:03:12 AM
 #5875

Each hash a miner does is using a different blob of data.  A single change in a single bit will produce a completely different hash, with no deterministic way to know how it will change.  To prevent miners from repeating work, pools take a template of work, and increment a pool-side counter for each miner's work.  This means the template each miner receives is slightly different, so that they will produce completely different hash results.  Miners then take this template and have three values they can change:

1) ExtraNonce - A piece of the coinbase (payment transaction) that allows for a miner to increment a counter.  Most pools use 4-bytes for this value, meaning ~4.2 billion possible increments.
2) Nonce - Another 4-byte counter, this is part of the block header.  It has ~4.2 billion possible values as well.  You can use up ~4.2 billion nonces (~4.2 Gigahashes), then increment the ExtraNonce by 1, which allows you to try all 4.2 billion Nonce values again.
3) nTime - This is a timestamp part of the block header.  It *can* be altered within certain limits.  Each change in this would be another 4.2b x 4.2b possible hash results.  Most miners do not increment nTime anymore because there is no reason to alter timestamps with how much work can be generated by default.


By changing a single bit on any of those 3, you get a completely different hash.  There is also the pool side counter for each miner so there is no overlap, and then each pool has different payout addresses so no pool has overlapping hashes either.

Thanks Eleuthria - takes a bit of digesting
So a 2 TH/s miner running at the full 2 TH/s would require ~2,100 secs to try all 4.2 billion hashes (Extranonces) for a single nonce setting and a single nTime ?
.... unless of course it got a hash result lower than the target

2 TH/s is actually 2 *trillion* hashes per second.  Your miner adjusts the nonce first, then adjusted the extranonce once it runs out of numbers to try.  At 2 TH/s, this happens roughly 500 times per second.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 02:06:26 AM
 #5876

Each hash a miner does is using a different blob of data.  A single change in a single bit will produce a completely different hash, with no deterministic way to know how it will change.  To prevent miners from repeating work, pools take a template of work, and increment a pool-side counter for each miner's work.  This means the template each miner receives is slightly different, so that they will produce completely different hash results.  Miners then take this template and have three values they can change:

1) ExtraNonce - A piece of the coinbase (payment transaction) that allows for a miner to increment a counter.  Most pools use 4-bytes for this value, meaning ~4.2 billion possible increments.
2) Nonce - Another 4-byte counter, this is part of the block header.  It has ~4.2 billion possible values as well.  You can use up ~4.2 billion nonces (~4.2 Gigahashes), then increment the ExtraNonce by 1, which allows you to try all 4.2 billion Nonce values again.
3) nTime - This is a timestamp part of the block header.  It *can* be altered within certain limits.  Each change in this would be another 4.2b x 4.2b possible hash results.  Most miners do not increment nTime anymore because there is no reason to alter timestamps with how much work can be generated by default.


By changing a single bit on any of those 3, you get a completely different hash.  There is also the pool side counter for each miner so there is no overlap, and then each pool has different payout addresses so no pool has overlapping hashes either.

Thanks Eleuthria - takes a bit of digesting
So a 2 TH/s miner running at the full 2 TH/s would require ~2,100 secs to try all 4.2 billion hashes (Extranonces) for a single nonce setting and a single nTime ?
.... unless of course it got a hash result lower than the target

2 TH/s is actually 2 *trillion* hashes per second.  Your miner adjusts the nonce first, then adjusted the extranonce once it runs out of numbers to try.  At 2 TH/s, this happens roughly 500 times per second.

Of course, Oops

Thanks everyone

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 02:10:05 AM
 #5877

Final question on this - are we all hashing the same "package" of transactions or is that a fluid situation managed by the pool software ?  ... suppose it has to be fluid

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
Taugeran
Hero Member
*****
Offline Offline

Activity: 658


CCNA: There i fixed the internet.


View Profile
February 04, 2014, 02:10:23 AM
 #5878

 le sigh. why did i just get so codey when he asked for laymans terms?

sudo reboot

Bitfury HW & Habañero : 1.625Th/s
tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1
Come join Coinbase
NicholasB54
Jr. Member
*
Offline Offline

Activity: 51


View Profile
February 04, 2014, 02:12:13 AM
 #5879

le sigh. why did i just get so codey when he asked for laymans terms?

sudo reboot
Hey, I can do maths  Smiley

EDIT : & Thanks for the clarification ... was busy typing & thinking while you posted - did help and clarify thx

EDIT2 : Didn't see your code 1st time of looking ... but think I can follow it thx again

Hodling Optimist : 1 BTC could eventually be worth $34,000 should bitcoin grow to account for even 1% of the global money supply (http://www.coindesk.com/venture-capital-bullish-bitcoin-risks/)
eleuthria
Legendary
*
Offline Offline

Activity: 1750


BTC Guild Owner


View Profile WWW
February 04, 2014, 02:48:45 AM
 #5880

Final question on this - are we all hashing the same "package" of transactions or is that a fluid situation managed by the pool software ?  ... suppose it has to be fluid

All miners on the pool are working on the transactions that the pool has selected for inclusion in the next block.  Different pools will normally have a slight difference in the transactions in their blocks due to different size limits, and which transactions they have seen on the network (since it's all p2p, not all pools since all transactions at the same time).

BTC Guild sends you a new work template every 30 seconds, regardless of whether or not a new block is on the network.  This new template includes an updated list of transactions to include in the block, since the more time between blocks, the more likely new transactions with higher priority/higher fees have been sent on the network waiting for confirmation.

R.I.P. BTC Guild, 2011 - 2015.
BTC Guild Forum Thread
Pages: « 1 ... 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 [294] 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 ... 426 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!