I must say I'm a bit disappointed with Slush at the moment. On the other hand I really don't want to mine with any of the Chinese pools (no offense to those of you who are Chinese!)
There are plenty of non-Chinese pools... Tis true, but I think Slush is the biggest of them all at this point. Correct me if I'm wrong. Also I love Slush's stats and web front end! (also monitoring and notification features). Make up your mind, are you disappointed or not  Obviously not disappointed enough to stop mining here and help activate BIP91. |
|
|
|
I must say I'm a bit disappointed with Slush at the moment. On the other hand I really don't want to mine with any of the Chinese pools (no offense to those of you who are Chinese!)
There are plenty of non-Chinese pools... |
|
|
|
Could you pls explain a little more here since I understand this issue is about to better sync the activation UASF / SW2x ?
Wouldn't it be better the SW2x lock-in is to be delayed to minimize the time difference between those two activations ?
That's what the miners try ?
BIP91 has to lock in and start invalidating non-segwit blocks before BIP148's activation, otherwise BIP148 goes active while the miners continue to mine non-segwit signalled blocks. They aren't really compatible, even though they ultimately lead to segwit's activation. BIP91 being activated earlier is better than them conflicting come August 1. This is the main reason segwit2x rushed and chose to activate 2 weeks before BIP148. |
|
|
|
Congrats... Great to see that your pool got to be part of a possible pivotal moment in bitcoin history....  This activation period looks very close but I don't think it will succeed because f2pool is STILL holding out. No idea what he's thinking; he's done some bizarre flip flops in the past that have nothing to do with what he says, so I don't even know if he's holding out because of gmaxwell's issue on the btc1 git. There is still enough hashrate to activate it without him on one of the activation periods (they are 336 blocks long) but instead of it being a given it's going to be a close one based on random luck. |
|
|
|
Ok i dont feel that bad now, it was a rental, pretty damn good investment there
congrats 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS
Not sure that's a rental, he's been mining that hashrate for quite a while at a stable hashrate. Rentals fluctuate far more than that and usually don't run for that long. By the way, the pool's bestshare appears to be stuck at zero now. It won't affect blockfinding but I'm currently investigating... |
|
|
|
[2017-07-19 23:32:10.553] Possible block solve diff 1001470489893.795044 !
[2017-07-19 23:32:10.636] BLOCK ACCEPTED!
[2017-07-19 23:32:10.692] Solved and confirmed block 476641 by 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS.1x3x7
[2017-07-19 23:32:10.692] User 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS:{"hashrate1m": "724T", "hashrate5m": "700T", "hashrate1hr": "692T", "hashrate1d": "690T", "hashrate7d": "681T"}
[2017-07-19 23:32:10.692] Worker 12iSvuwsDwUCFKpXnUmtFJNGPmMm2Yt6cS.1x3x7:{"hashrate1m": "12.1T", "hashrate5m": "13.6T", "hashrate1hr": "13.7T", "hashrate1d": "13.7T", "hashrate7d": "13.5T"}
[2017-07-19 23:32:10.694] Block solved after 2018478812597 shares at 250.9% diff
And a BIP91 + BIP141 block to boot. Maybe just maybe we'll help activate it! |
|
|
|
Maybe I will toss some here. near as I can tell we have done 1,000,000,000 plus and 700,000,000 would be average luck so we are due  Every hash is welcome and appreciated  Just bear in mind someone else is mining here renting from NH so make sure you're not competing with him. |
|
|
|
Hello! My question is probably at the wrong place but I ask here because i read this whole post and understood that in this forum there are some people who really know a thing or two about mining. I know nothing about mining. But I really want to start mining because it seems like a pretty sweet opporunity and I need to find between 20,000$-40,000$ in the next 2-3 years for my education. The problem is that I have no clue where shall i start and how much money I will need to invest in hardware. I got a little off topic my question is: Can someone tell me where I could read some TRUTHFUL documentation on the whole deal, this should include the hardware i need the way i should set it up and how i should be mining to make the whole thing profitable. I hope my question is not too absurd and will get some feedback. Thanks!
Please start looking in the mining speculation subforum for your answers and not posting in this unrelated topic. |
|
|
|
Am I able to connect to this using a Rockminer T1? So far no luck.
So far no luck with any pool with the T1...
Read the website instructions please. If you have an asicminer tube/prisma, you can use a custom port 3335 (only accepts usernames without worker extensions) eg:
solo.ckpool.org:3335
|
|
|
|
What's this, an ad?
You're a mod, you didn't move it to the marketplace where it belongs? It wasn't even clear that this is an ad. |
|
|
|
|
The rockminers had a very broken stratum implementation which assumed certain fixed parameters in the stratum pool. Some pools provide a special port or proxy to allow them to work, such as my solo.ckpool.org . Otherwise you'll need to investigate using a proxy such as ckproxy specially set up to make them work to your pool of choice, and even then it will only work with certain pools.
|
|
|
|
|
Bullshit. This vulnerability was fixed years ago by all real pools and only applied to one form of pool software.
|
|
|
|
Lower difficulty puts more stress on fast ASIC miners since the miner has to process an excessive number of shares in a short period of time. If the miner would be working only on a few shares with higher difficulty the efficiency of the miner would be higher.
@ck I was under the impression that ASICs are always processing 1diff shares and all that diff setting means is "Don't send any result under this value to the server". Have I been wrong about that all of this time? Or are they just over-simplifying and calling "processing" the act of sending to the server?  It's partially true, but their reasoning is a lie. Today's ASICs actually filter out low diff shares themselves but the problem is their server since it collates the shares from multiple miners and passes them on. There is no such thing as a standalone asic itself that needs anything more than diff 10k since the S9 is the biggest miner around and really it works fine at lower diffs and only gets overloaded at diffs of under 1k. Presumably they're running into load issues on their servers. |
|
|
|
...When they were going to signal SegWit a while ago, Wang Chun said that SegWit would be a "disaster" then started signalling really soon after under the guise of following the public..
Yeah, what kind of dick reverses his position based on the belief that holding strong to such a position would create a fork in Bitcoin that's not good for Bitcoin?  A real big dick... but no wait, maybe it's a real small dick and this is their way of compensating by feeling like they have power? |
|
|
|
A few are holding out or have reverted while they get clarification on the latest problem with the fork as pointed out to them by gmaxwell here https://github.com/btc1/bitcoin/issues/85 . They're waiting to see how bad an issue it might be in the real world before deploying it (+/- again). Is this why f2pool and bitfury still holding? Yesterday Bitfury was signaling bip 91, today they changed to segwit. I'm tracking this through xbt.eu Bitfury have said they are now: https://twitter.com/BitfuryGeorge/status/887557125437829121Only f2pool is left of the big pools and there's already enough hashrate so they'll definitely do it knowing that. |
|
|
|
A few are holding out or have reverted while they get clarification on the latest problem with the fork as pointed out to them by gmaxwell here https://github.com/btc1/bitcoin/issues/85 . They're waiting to see how bad an issue it might be in the real world before deploying it (+/- again). |
|
|
|
signalling means changing a variable. this variable is the block version. to support BIP91 which SegWit2x implemented you change that variable to 0x20000010 and to support more than one BIP you add the bits to this number for example to support both SegWit2x (BIP91) and SegWit you change it to 0x20000012 (addition of bit 1 and bit 4 if i am not mistaken) SegWit alone is 0x20000002 for these stuff you don't need to run a specific client, you just edit a single line of code. you may also run btc1 client and change your useragent to something different to mask the fact that you are running that client, maybe to protect against getting DDoSed No. Changing just one bit is not enough to be safe with the BIP91 fork because part of running BIP91 means orphaning any blocks that aren't signalling segwit once support is over 80% @-ck what client you running? Bitnodes shows only 64 btc1 clients while BIP91 is almost 65% at xbt.eu. Almost no one is running Garzik's client just signaling BIP91 it seems.
I run a custom coin daemon but the extra code for BIP91 comes from here: https://github.com/segsignal/bitcoin |
|
|
|
|
Show Posts
