Huge? LOL... I guess you don't remember 2014 too well  . 10% was considered a reprieve. On January 2, 2014 the network difficulty was 1,418,481,395. By the end of the year (on 12/30) it was 40,640,955,016. There were 29 difficulty adjustments that year, of which 19 were over 10%. |
|
|
|
|
If you're renting your hash, then somebody hit a block of an alt coin with your miner.
|
|
|
|
Wow... 40PH/s! I just checked out this pool for the first time in a long time (by long time - my last share ever submitted to Slush was 1 year, 8 months ago)... it's certainly changed look and feel. Somebody's been busy . |
|
|
|
|
Something else. Were you renting your gear? Pointing it to an alt coin? Because for that to have been a bitcoin block, best share would have had to have been at least 72,722,780,642
|
|
|
|
|
Entry looks good, thanks.
The reason I started the pool was precisely because of the newbie account scams that have popped up. Nexious hit me personally - I barely mined there, but was the one that found the block, which caused the whole con to be exposed. I thought I was helping out a small pool operator and some miners. I'm glad I did find that first block. At least it put an end to the scam and didn't cost anyone any more of their time and money. Hopefully with my pool, I can provide that help to the community by providing a legitimate alternative choice for miners to point their gear.
|
|
|
|
LOL... indeed you did |
|
|
|
Slick service! I especially like the random entropy dots that fill the screen . Mind if I ask what kind of hardware you've got executing the vanity addresses, or is it a trade secret? I have generated a number of my own addresses on my rMBP with GeForce 750M. For my needs it does the job well enough... I try to not make them too complicated. I wonder how one of those $10,000 Mac Pros would fare... hmmm... 12 cores and dual AMD D700s... |
|
|
|
|
Welcome. I'll echo some of the other comments made here about "free" power. There is no such thing. Just because power is included in your rent, don't think for a second the landlord won't notice if suddenly his power bill goes up significantly. Also, the S7 will consume pretty much an entire 15A circuit (assuming standard US residential wiring here). Not sure what kind of a place you and your girl are moving, but before you consider mining, you'll want to know and understand the power situation.
Keep in mind that what an S7 might earn today is not what it might earn next week or next month. The network difficulty changes every 2016 blocks. Unfortunately, we're on an upswing (last was over a 10% increase and we're headed that way again), which means that your hash is now earning 10% less than it was the previous 2016 blocks, and will likely earn 10% less yet again next time.
As for your cooling questions, there have indeed been some interesting experiments. Bitmain produced the Antminer C series that was water-cooled. A number of people have tried full immersion cooling using different specialty liquids.
|
|
|
|
This belongs in the alt coins forums...please move it |
|
|
|
After spending 2 days debugging getblocktemplate requests my conclusion is: Most mining software implements a subset of GBT to make it work for them and doesn't follow the standard strictly. Miners also introduce some other rules in agreement with pools that are not documented. If you are working on a pool you will have to manually test it against miners to be sure it works (good luck). I couldn't get cgminer to work with my pool proxy. The problem is that it differentiates between solo and pool mining (what I don't think is part of the getblocktemplate specification). After reading the source code I found this https://github.com/ckolivas/cgminer/blob/master/cgminer.c#L6512. So, cgminer will only treat you as a pool if you submit "coinbase/append" and "submit/coinbase" as mutables. This is not really explained anywhere and it took me some time to figure it out. I can understand the idea behind this choice, but it still looks a bit arbitrary to me. It will just reject you with a message that you are not a pool without clarification. I can see users breaking their head over this. To answer some of the questions myself after 2 days of researching: 1. Stratum is much better defined and smaller. It is also more popular between pools. This makes it easier to implement and find information about. It's straight forward, there is basically only one way to do it. You loose some flexibility, but at least you don't need to deal with the mess of BIP22 and BIP23. I will try to write a tutorial how to implement GBT correctly if I find time. 2. Because of cgminer behavior the proxy needs to do much more. Now it needs to understand "submit/coinbase" and keep track of the transactions submited to the miner. It makes it more complicated. But using a bitcoin node to get information from the network and not implementing your own is still a good idea. I didn't get to experiment with setting the difficulty. I hope I will soon have a proof of concept pool running on testnet to try more advanced stuff. P.S. What is wrong with you guys? Accusing me of scaming. Casually requesting me to send you 25btc. Promoting your own pools. From my perspective this doesn't look like a welcoming community. I never accused you of scamming - I was responding to the comments made by Phil. I think it's cool that you're trying to understand the processes behind the scenes and are experimenting with your own software. Personally, I'd recommend taking a look at some of the existing implementations (ckpool, NOMP, UNOMP, stratum-mining, eloipool, etc). See how those guys tackled the problems you're facing. Who knows, maybe you'll be inspired and write the next great thing . Also, I apologized previously, but let me do so again in case you missed it. I didn't mean to hijack your thread chatting about my pool. A lot of us were just scammed by some guy running a long con. He opened up a pool this past summer. Was active on the boards and responsive to queries and support on his pool. Right up until I found the pool's first block. Within minutes, the pool went down, the website went dark, email servers were taken down. The pool operator took the 25 BTC and ran. So, as a gesture of goodwill, I am providing a place for miners to point their hash. That's all. Both Phil and -ck have made the same offer - which I personally think is very generous of them. If you're a newbie account and want to open up a pool, they are willing to escrow the 25 BTC for the first block. That way, miners will know that they'll at least get paid for the first block. It's not a perfect solution - but at least it's something to try and prevent the scammers from continually taking advantage of folks. |
|
|
|
|
You're running a pool as root???
|
|
|
|
|
Sorry about that... the target is 12 shares per minute.
|
|
|
|
Pool: Jonny Bravo's Mining Emporium Website: http://www.bravo-mining.comProxy: No Generation address: 14KxdJ7DfAPsxCYkpcDTcKotjeProcfRPo Coinbase signature: /bravo-mining/ Payout method: PPLNS Fee: 0.5% Pay Tx Reward: Yes Vardiff: starts at 1042. Range from 8 to 4096. Local Work: stratum Pay Orphans: No Min Withdrawal: 0.001 Merge Mining: No |
|
|
|
Yeah, I've been around a while  . Been running my own p2pool node for almost 2 years. I just got fed up with all the scams and jackasses ripping people off, and wanted to do something about it. Since people seem to be scared of p2pool for some reason, I thought I'd offer up the choice of a "typical" mining pool. Edit: @OP - sorry for hijacking your thread. |
|
|
|
As A heads up we just had a guy open a pool and run off with the first block it hit.
So if you are going to open this pool to the public I will make this offer send me 25btc I will hold in escrow for no charge and I will add .25 btc to the first block payout.
Most of us are tired of the cons that have happened . If you don't want to use me as an escrow ask another trusted person. But frankly no one will want to be in your pool due to the recent theft.
I actually got so angry that I opened up my own pool. It's nothing fancy and I'm not offering crazy promotions or promises. Straight up BTC mining. Anybody who wants to can mine on it. So far, it's only me. Every now and then I'll rent some hash and throw it at it to see if I get lucky - after all, I found that block on the scammer's pool. bravo-mining.com |
|
|
|
|
I fully agree that the persons paying for the rental are going to take a pretty sizable financial loss. However, it is not a complete loss (they'd still make *something* if and when the pool found blocks). As the gear owner, I'm still getting paid regardless. It's only the miners on the pool that get shafted.
As you correctly point out, PPLNS mitigates things, since risk is transferred to the miners. Had I chosen a PPS pool, then it would be the pool operator that eats the losses.
|
|
|
|
I only used the word eventually because it wasn't instant. I didn't mean to imply some enormous stretch of time... in my head it was seconds . So, if I'm reading your latest reply correctly, you'll have potentially 4 types of blocks: 1) A block with only a single coinbase transaction sending the 25 BTC to your offline wallet 2) A block with only a single coinbase transaction sending the 25 BTC to your miners 3) A block with all kinds of transactions, but the coinbase sends the 25 BTC to your offline wallet 4) A block with all kinds of transactions and the coinbase sends the 25 BTC to your miners Any of the "offline wallet" blocks require you to, at some point in the future, do a manual payout run. Otherwise, the miners get the virgin coins from the block generation. Thanks again for taking the time to reply. |
|
|
|
It does, thanks. I was all kinds of confused about what you were actually sending if you didn't send the coinbase at least out to your miners. Now I know how you're managing it: you send out what is effectively a "template" block that contains only a single coinbase transaction directing the 25 BTC to your offline wallet. Eventually you send the actual coinbase transaction with all of your miners who expect to get paid by this block, along with the set of unconfirmed transactions you'll include in your block. I realize you're avoiding a bandwidth spike initially, but you're actually increasing your bandwidth needs overall, right? Initial spike uses less bandwidth because it's transmitting a pretty small chunk of data to your miners. Larger data transmission occurs shortly thereafter. However, if you transferred the "actual" work only, then you'd never deal with that first "template" work. Anyway... it is what it is. Thanks for the reply . |
|
|
|
keeping people from using someone else's solve hash)...
Nobody can use a hash belonging to someone else. Block withholding means that a Miner Withholds a block solve, but it can't be used for anyone else on nor on any other pool. There is nothing you can do to prevent a miner from checking a hash to see if it meets difficulty before submitting it and withholding it if it does meet difficulty. I still fail to understand why anyone would withhold a hash that has met difficulty, surely they have nothing to gain from doing this ? They have plenty to gain from it, and nothing to lose. Let's say I am a malicious user and have written software to withhold any block solving shares. Let's also assume I own 5PH/s of gear, which is only about 1% of the entire network. Not a tiny amount of hashing power by any stretch. I put my gear up for rent on any of the sites. People start renting my gear and pointing it to this pool, for example. They're hoping to hit a block. Well, because of my hack, they'll never hit that block. However, I will still get paid for the rental. Now let's say you don't like somebody's pool. We'll pick on kano's pool here (no offense at all to kano, it's just an example). You know that my gear has the block withholding exploit in it, so you rent my gear and point it right at kano's pool. Everybody on his pool is all kinds of excited that 5PH/s just showed up and is looking forward to the payouts. Uh-oh... no new blocks are found by my gear. However, blocks are still found by the existing hash on his pool. So... everyone there complains that the pool is unlucky. I don't really care because you rented my gear and I'm still getting paid. Heck, even you will get paid for any blocks the pool finds. Win for me, win for you, loss for everyone else on kano's pool. |
|
|
|
|
Show Posts
