[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[dmwardjr]

sweeeeeeeet

another block

 

[Rudler]

Maybe it will work again in a normal way. (1-3 hours per block)

Need 7 more blocks for reinvesting in a Antminer C1, perfect for wintertime.
Anybody tried to connect the C1 to a underfloor heating? 0_o
 
Friend of mine is heating his appartment with two C1.

[dmwardjr]

Maybe it will work again in a normal way. (1-3 hours per block)

Need 7 more blocks for reinvesting in a Antminer C1, perfect for wintertime.
Anybody tried to connect the C1 to a underfloor heating? 0_o
 
Friend of mine is heating his appartment with two C1.

No, can't say that I have.

So, you like the C1?

Is it pretty stable?

[Rudler]

The C1 is just another toy to play with....

Till now, I dont have one. A friend of mine's got two,
he is delighted bout the "transportpotential of the heat".
And they are running stable, he said.

So my idea, take 10 of them, put waterpipes together and
lead it through the underfloor heating......

[dmwardjr]

The C1 is just another toy to play with....

Till now, I dont have one. A friend of mine's got two,
he is delighted bout the "transportpotential of the heat".
And they are running stable, he said.

So my idea, take 10 of them, put waterpipes together and
lead it through the underfloor heating......

Sounds like a plan!!!

 

Will be a first!

[Rudler]

....at last....a block with 0:26:18.....

[dmwardjr]

....at last....a block with 0:26:18.....

Wow!

I be damn if it isn't!

Sweeeeeeeet

[jterry211]

The C1 is just another toy to play with....

Till now, I dont have one. A friend of mine's got two,
he is delighted bout the "transportpotential of the heat".
And they are running stable, he said.

So my idea, take 10 of them, put waterpipes together and
lead it through the underfloor heating......

Just put them in the bathroom and hook them up to the hot water side of your sink and you will have instant hot water. 

JT

[Rudler]

In winter it is very good, if you have got cheap power, you can save lot gallons of oil or gas for heating.
Six S3 heating 240sqm at 25°....

But ontopic:

question @ slushsupport: Do you know, if there are some vendors mining in this pool?

[jackbox]

Do the C1's generate as much expelled heat as the S3+ units? When my aircon is not on the room my Antminer S3+ is in heats up to about 31 Celsius (I am in Bangkok). Would a C1 generate as much heat from the radiator/fan unit or does it run cooler/hotter overall?

[Rudler]

It felt a little bit cooler than my S3 in normal modus....

Still need 6 blocks to get one very cheap, maybe.....

Edit: Anyone here already own a C1?

[vipgelsi]

Love the idea about the hot water.

[jackbox]

It felt a little bit cooler than my S3 in normal modus....

Still need 6 blocks to get one very cheap, maybe.....

Edit: Anyone here already own a C1?

Do you have the free $50 off coupons they gave to almost everyone or do you need one sent to you? I have 6 that most likely won't get used.

I am tempted to get a C1 but not sure if my room could handle the additional heat and if my Thai wiring could handle another 1100 watt power supply.

[Rudler]

Love the idea about the hot water.

Trust me, it is too less power to heat flowing water, but if you
have got underfloor heating or low emission radiators in a heating
cycle and enough overclocked C1, you can make finish sauna......

I am new here, are there no threads about heating with miners?

[dmwardjr]

I HOPE this block that is still at 100 confirmations remaining is ours and not someone else's.

That's the only reason I can think that it still has 100 confirmations.

Please be our block!

EDIT:  The more I watch it, the more it looks like none of the blocks we found are continuing their confirmation count down.

[MrTeal]

I HOPE this block that is still at 100 confirmations remaining is ours and not someone else's.

That's the only reason I can think that it still has 100 confirmations.

Please be our block!

EDIT:  The more I watch it, the more it looks like none of the blocks we found are continuing their confirmation count down.

Each new block on the network counts as one confirmation. There hasn't been a new block found by anyone in the last 40 minutes, hence no more confirmations.

[dmwardjr]

I HOPE this block that is still at 100 confirmations remaining is ours and not someone else's.

That's the only reason I can think that it still has 100 confirmations.

Please be our block!

EDIT:  The more I watch it, the more it looks like none of the blocks we found are continuing their confirmation count down.

Each new block on the network counts as one confirmation. There hasn't been a new block found by anyone in the last 40 minutes, hence no more confirmations.

Have you NOT noticed the confirmation count down on the blocks found have yet to move since that block was found?

Also, sometimes there is argument between pools as to whom found a particular block first.  That's why I was wondering why that recent block found was still at 100.

After watching longer, NONE of the blocks found are counting down to being cofirmed.  I'm sure they are; it's just we are not seeing it on the beta.


EDIT:

There we go, they are counting down now.

[MrTeal]

I HOPE this block that is still at 100 confirmations remaining is ours and not someone else's.

That's the only reason I can think that it still has 100 confirmations.

Please be our block!

EDIT:  The more I watch it, the more it looks like none of the blocks we found are continuing their confirmation count down.

Each new block on the network counts as one confirmation. There hasn't been a new block found by anyone in the last 40 minutes, hence no more confirmations.

Have you NOT noticed the confirmation count down on the blocks found have yet to move since that block was found?

Also, sometimes there is argument between pools as to whom found a particular block first.  That's why I was wondering why that recent block found was still at 100.

After watching longer, NONE of the blocks found are counting down to being cofirmed.  I'm sure they are; it's just we are not seeing it on the beta.


EDIT:

There we go, they are counting down now.

No, they weren't counting down at all because they weren't supposed to be counting down. The confirmations listed by Slush is basically the number of blocks built on top of the block in question. IE, for block 331733, Slush will consider that confirmed and pay out for it after the network all together finds another 100 blocks. After 331733, no blocks were found for 40 minutes, and that's why it stayed as 100 confirmations required, and none of the other blocks were counting down either.

As a point, until a block has at least one built on top of it there's always the chance it can get orphaned, but it would actually be very unlikely for even the last block to be orphaned after a couple minutes or so. You get orphan races when two blocks are found within usually a couple seconds of each other, but after a minute everyone who's not running broken software would have been mining on our block, and not the preceeding one.

[dmwardjr]

I HOPE this block that is still at 100 confirmations remaining is ours and not someone else's.

That's the only reason I can think that it still has 100 confirmations.

Please be our block!

EDIT:  The more I watch it, the more it looks like none of the blocks we found are continuing their confirmation count down.

Each new block on the network counts as one confirmation. There hasn't been a new block found by anyone in the last 40 minutes, hence no more confirmations.

Have you NOT noticed the confirmation count down on the blocks found have yet to move since that block was found?

Also, sometimes there is argument between pools as to whom found a particular block first.  That's why I was wondering why that recent block found was still at 100.

After watching longer, NONE of the blocks found are counting down to being cofirmed.  I'm sure they are; it's just we are not seeing it on the beta.


EDIT:

There we go, they are counting down now.

No, they weren't counting down at all because they weren't supposed to be counting down. The confirmations listed by Slush is basically the number of blocks built on top of the block in question. IE, for block 331733, Slush will consider that confirmed and pay out for it after the network all together finds another 100 blocks. After 331733, no blocks were found for 40 minutes, and that's why it stayed as 100 confirmations required, and none of the other blocks were counting down either.

As a point, until a block has at least one built on top of it there's always the chance it can get orphaned, but it would actually be very unlikely for even the last block to be orphaned after a couple minutes or so. You get orphan races when two blocks are found within usually a couple seconds of each other, but after a minute everyone who's not running broken software would have been mining on our block, and not the preceeding one.

Thanks for taking the time to explain that to me, Mr Teal.  I know you didn't have to but I appreciate it.  Learn something all the time.

Thank you!   

[kano]

...
No, they weren't counting down at all because they weren't supposed to be counting down. The confirmations listed by Slush is basically the number of blocks built on top of the block in question. IE, for block 331733 (https://blockchain.info/block/00000000000000000d85f2d73089f2420d3f71d4a614139ace6bab56888adbc1?site=slush), Slush will consider that confirmed and pay out for it after the network all together finds another 100 blocks. After 331733, no blocks were found for 40 minutes, and that's why it stayed as 100 confirmations required, and none of the other blocks were counting down either.

As a point, until a block has at least one built on top of it there's always the chance it can get orphaned, but it would actually be very unlikely for even the last block to be orphaned after a couple minutes or so. You get orphan races when two blocks are found within usually a couple seconds of each other, but after a minute everyone who's not running broken software would have been mining on our block, and not the preceeding one.

Just a couple of points.

In the current bitcoin-qt it's 101 blocks
When I added that to the ckdb code I was surprised to see it is actually 101 not 100 (as I also thought it was 100)
But that's also due to the confusion that when a block is found it is considered 1 confirm, not 0 confirms.

Although an orphan race is usually obvious, if someone finds a block after most people on the network know about another block, they can keep mining off their own block and win if they are very lucky.
Of course they would have to not send out their late block, thus the network wouldn't know about it at all.
But if they are lucky enough to build on their own block before anyone find a block to build on the network block, and they send out both, they will actually win the previous orphan race and their 2 blocks will become the network blocks.

So yes, even I look at the 'known' blocks when my pool finds a block and am usually pretty sure after a few minutes, but it's still not certain.
Of course, if you are looking at blockchain and not in your bitcoind debug.log the losing block may be on the network and you just can't see it in blockchain.
That's rare but it can happen.

The normal thing that happens on an orphan race is that part of the network will be mining on one and another part of the network on the other.
It's then purely up to which part of the network finds the next block, that decides the orphan race (though it can in rare circumstances be longer than 1 block to decide it)
So it just depends on who has seen both blocks, to know that the orphan race is even happening - but normally everyone has seen both and chosen the one they saw first, to mine on.