[2016-12-30 13:09:57.775] Possible block solve diff 778034450998.287476 !
[2016-12-30 13:09:57.973] BLOCK ACCEPTED!
[2016-12-30 13:09:57.973] Solved and confirmed block 445852 by 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6.11x135
[2016-12-30 13:09:57.974] User 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6:{"hashrate1m": "7.02P", "hashrate5m": "7.62P", "hashrate1hr": "6.95P", "hashrate1d": "7.15P", "hashrate7d": "6.74P"}
[2016-12-30 13:09:57.974] Worker 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6.11x135:{"hashrate1m": "9.9T", "hashrate5m": "10.2T", "hashrate1hr": "9.3T", "hashrate1d": "9.03T", "hashrate7d": "7.03T"}
|
|
|
|
|
So why start another thread when you have one describing your venture into renting for p2pool already?
|
|
|
|
Holy smokes -ck solo pool is on fire hitting blocks left, right and center  wow.... the one before this was 13.5TH miner! looks like the BTC Gods are giving the smaller guys a chance after the big hitter got 3 in the bag ...All miners are 13.5TH or smaller as there's no such thing as a unique device with more hashrate. Look harder; you're looking at the worker. His overall hashrate was 420TH. |
|
|
|
DE block [2016-12-29 20:09:10.629] Possible block solve diff 3372079137838.309082 !
[2016-12-29 20:09:11.008] BLOCK ACCEPTED!
[2016-12-29 20:09:11.009] Solved and confirmed block 445700 by 1NrV55iVXdsDwoQYLnZK7DQMbhEmFDZyeV.barraccooda.004
[2016-12-29 20:09:11.009] User 1NrV55iVXdsDwoQYLnZK7DQMbhEmFDZyeV:{"hashrate1m": "789T", "hashrate5m": "766T", "hashrate1hr": "760T", "hashrate1d": "760T", "hashrate7d": "747T"}
[2016-12-29 20:09:11.009] Worker 1NrV55iVXdsDwoQYLnZK7DQMbhEmFDZyeV.barraccooda.004:{"hashrate1m": "13.5T", "hashrate5m": "13.2T", "hashrate1hr": "13.5T", "hashrate1d": "13.8T", "hashrate7d": "13.6T"}
|
|
|
|
[2016-12-28 17:31:11.512] Possible block solve diff 474121934727.925415 !
[2016-12-28 17:31:11.678] BLOCK ACCEPTED!
[2016-12-28 17:31:11.678] Solved and confirmed block 445574 by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.131
[2016-12-28 17:31:11.678] User 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY:{"hashrate1m": "417T", "hashrate5m": "421T", "hashrate1hr": "424T", "hashrate1d": "422T", "hashrate7d": "213T"}
[2016-12-28 17:31:11.678] Worker 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.131:{"hashrate1m": "13.5T", "hashrate5m": "12.3T", "hashrate1hr": "11.8T", "hashrate1d": "11.9T", "hashrate7d": "11.8T"}
[2016-12-28 17:31:11.678] Block solved after 194364218579 shares at 61.2% diff
|
|
|
|
nah. i said all inclusive, im sure adam back and his playboy matt corallo will be there to supply those.. oops did i just out them
and yes i have noticed that at a few events even when only one is set to make a speech, the other is nearby with a weird eerie shadowing for emotional support body language, kinda not subtle.
im 50% thinking its the booze hookers and blowjob weekend you are choosing..
and 50% fear that core will blacklist your blocks out of spite if you opposed core. not due to any bad data, but just not going with them you'll lose income.
Considering I have nothing to do with bitcoin core devs, blockstream, blockchain, blocktrail and whoever else you want to try and lump me in with, am not employed by any bitcoin related entity, have never attended a single bitcoin related function, roundtable or whatever, and am a specialist anaesthesiologist by trade that hacks on bitcoin mining related software in his spare time, I'm not even sure why you're attacking me or what the purpose of your attack is apart from continuing your usual tirade of nonsense trolling. So at this point I'm quite content to disengage any further communication with you as others have already done since you are clearly a full time btctalk troll. |
|
|
|
however as a visible member of the community showing my support serves another purpose.
free weekend all inclusive at blockstream sponsored next roundtable? You forgot the hookers and blowjobs. |
|
|
|
That's correct I am supporting segwit and always planned to. On the other hand Kano and I differ on our opinion on this and he does not plan to signal support for it in kano.is unless segwit gets close to activating and ultimately that is his pool and I am technical support for ckpool which he runs. No there is no way to support BU on my pool. That would defeat the purpose of showing my support for segwit and contributing to its activation. Note also that bitminter is signalling segwit too. On the other hand my pool is a tiny entity and will not be the deciding factor in segwit activating it or not, however as a visible member of the community showing my support serves another purpose. |
|
|
|
Hi there miners!  I've created this initiative. If you are a proud miner, would you like to be in The Wall? I think it's going to be awesome TM when it's full! http://proudminers.hopto.orgPlease tell me what you think about it, or any suggestion you have! Have fun... and make profit!  Would you like to explain exactly what this is? Since it looks like yet another meaningless scam at this stage, you'd do well to give a more thorough explanation here and on the site of what your alleged service is and does, otherwise you risk being instabanned on this forum. |
|
|
|
And your first block signalling segwit support Indeed it is. Unfortunately segwit voting doesn't seem to go much higher than 30% so I guess it may take a while until we see segwit activated. Aye. At this stage watching percentage voting yes is pointless as it is purely going to depend on number of large pools supporting it rather than absolute percentage. If, and, as soon as, another pool supports segwit the percentage will jump up and stabilise with their hashrate percentage. So it's been static for almost a month since the same sizeable pools have been featuring in the yes vote. |
|
|
|
What is the benefit of bitcoin core? Bitcoin Core will signal support for and recognise SegWit enabled blocks, amongst other additions. Depending on your stance in the max block size issue, you might like to consider using one of the other many bitcoin clients such as https://www.bitcoinunlimited.info/ which supports bigger maximum block sizes as a solution to the full blocks we currently are experiencing. What client you run has zero effect on what becomes the new standard which is determined by a majority of miners only. You're free to use whatever client you want though, it's like publicly showing your support for a political party but not having the right to vote... |
|
|
|
[2016-12-27 23:51:14.337] Possible block solve diff 2114998493450.212402 !
[2016-12-27 23:51:14.480] BLOCK ACCEPTED!
[2016-12-27 23:51:14.481] Solved and confirmed block 445453 by 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6.4x175
[2016-12-27 23:51:14.481] User 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6:{"hashrate1m": "15P", "hashrate5m": "14.3P", "hashrate1hr": "14.1P", "hashrate1d": "14P", "hashrate7d": "6.37P"}
[2016-12-27 23:51:14.481] Worker 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6.4x175:{"hashrate1m": "12.1T", "hashrate5m": "12.8T", "hashrate1hr": "13T", "hashrate1d": "11.9T", "hashrate7d": "4.08T"}
[2016-12-27 23:51:14.481] Block solved after 642634075129 shares at 207.2% diff
|
|
|
|
There's that Christmas block!  And your first block signalling segwit support |
|
|
|
|
This question comes up frequently and it has been adequately answered so I'm locking this thread.
|
|
|
|
Latency matters, but not as much as you might think.
2 years experience mining on a Exede sat connection (typical 700 ms round-trip ping, rarely as low as 660, most of that the double-hop out through geosynch) only kicked my rejects up into the 1-2% range instead of the sub-1% range I've had since my move last summer an aquisition of my first *GOOD* internet connection in about 6 years.
There's a simple scientific explanation; there is no need to speculate. Blocks are found on average every 10 minutes or 600 seconds and your stale shares are anything delivered after the block change due to hardware change speed and network latency. If your latency is 1 second 1/600 of your shares will be late and stale from latency alone. |
|
|
|
...
I had enough of that segwit moron who threatened the pool (in PM) - that I still have no idea why the mods didn't ban him
...
I would have thought the mods enforced stricter standards with regards to threats. That is an epic fail. Mods don't have the power to ban, nor can they see PMs. Only admins can and there are so few of them that are active that they're swamped. |
|
|
|
Much better luck Still the big miner. [2016-12-26 05:43:44.333] Possible block solve diff 478514221441.068115 !
[2016-12-26 05:43:44.506] BLOCK ACCEPTED!
[2016-12-26 05:43:44.506] Solved and confirmed block 445184 by 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6
[2016-12-26 05:43:44.506] User 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6:{"hashrate1m": "14.4P", "hashrate5m": "13.8P", "hashrate1hr": "14.2P", "hashrate1d": "12.4P", "hashrate7d": "3.86P"}
[2016-12-26 05:43:44.506] Worker 1VaKMTUFNZtCUicT2XdPa8uKVwLDjEFt6:{"hashrate1m": "9.9P", "hashrate5m": "9.65P", "hashrate1hr": "9.7P", "hashrate1d": "8.18P", "hashrate7d": "2.92P"}
[2016-12-26 05:43:44.506] Block solved after 163826750806 shares at 52.8% diff
|
|
|
|
A full bitcoin node uses a MAXIMUM of 1 Megabyte every 10 minutes to download a block.
INSIGNIFICANT.
While I acknowledge that oversubscribed cable is a real problem of its own, the issue is not just download b/w being used by a bitcoind node, it is upload bandwidth. Once your upload is saturated, your download bogs down immensely due to delayed acknowledgement of packets. Using quality of service and restricting bitcoind outbound bandwidth can make a massive difference to a normal domestic internet connection. Most uploads are very limited even if they're very fast download. Not everyone is blessed with optic fibre broadband... The difference here with adsl2 is dramatic. |
|
|
|
|
If you're running a full bitcoin node, that could do it. Mining itself uses hardly any bandwidth by comparison though.
|
|
|
|
|
You asked on the official pool thread. No need to start another thread.
|
|
|
|
|
Show Posts
