yeah I saw those photos. but here is the deal the `14 nm chips all over the world from BMT to Intel have had issues . Size matters the smaller you go the more voltage issues of leaking occur. look for the 14nm design to stick around 2x to 3x longrt then the 28 nm size. If BMT makes a new miner the s11 it may have an upgraded 14nm chip. It may use more of the same chip at lower volts. It will not be for sale until another company drops a new miner that is close in quality to the s9. the miner below is said to exsist https://bitcointalk.org/index.php?topic=1317180.msg16681727#msg1668172710 th at 1000 watts if this is sold at 899 - 999 usd it would be better then the s9. If this goes on sale in under 1 month and does not crash and burn. It would push BMT I did not even notice that thread was active again. Looking nice!
|
|
|
Now it is time to buy S9 batch 19,20 or to wait for new s10 or s11 because in s7 during this much batches the s9 was released so when to expect new miner ?
BMT has no reason to release another miner. They have absolutely zero competition on the 14/16 nm node. but in one exhibition it was shown that 14nm then 10 nm then 7 nm To what are you referring?
|
|
|
Now it is time to buy S9 batch 19,20 or to wait for new s10 or s11 because in s7 during this much batches the s9 was released so when to expect new miner ?
BMT has no reason to release another miner. They have absolutely zero competition on the 14/16 nm node.
|
|
|
I don't see how the R4 is at all profitable; I've done the math and at 10 cents a kilowatt this thing is really not profitable at all maybe just maybe a few bucks profit after over year of running 24 hours a day if prices stay where they are now.
Unfortunately, almost nothing is profitable at 10 cents a kW these days. Now if you do not pay for electricity, that is a different story, but those cases are rare.
|
|
|
I will say that I have always loved BitMinter. It was my first bitcoin pool. However, the pool luck has been really bad these last 6 months. It is my opinion that this bad luck has had a significant impact on the hashrate overall. I really want to see the pool succeed and grow, but as of a few weeks ago, I am only using BitMinter as my backup.
|
|
|
We have been on fire this last week! However, I am still trying to figure out why we historically get so few transaction fees. I look back at the blocks we solve and the blocks surrounding ours are almost always >900kB. The last block we solved, block 435656, was only 20kB. I am betting kano is going to jump in on this and say something like, "People do not configure their setup properly. That is the problem you will always run into with p2pool." In any case, I think we should attempt to improve this somehow. Any ideas? You're spot on with your reasoning. Knowing how to set things up properly plays a large role in the composition of the blocks you create. In a more typical pool model (like mine, kano's, etc) a single source provides the workload for all miners. You as the miner don't have to know anything other than how to configure your hardware to point to the pool. Details of block size, block composition, etc are all managed by the pool software and the pool operator. With p2pool, when you are running your own node, you must also learn how the blocks are created. Ideally, you should understand the code - how it creates blocks, how often it changes the block composition, etc. For example, what happens in the p2pool code when a block is found on the network? How does it invalidate the transactions on which miners are currently hashing? Does it produce an empty shell and push that to miners? Does it fully validate the new block? What are the optimal block size settings that will be most efficient for your p2pool node? What kinds of transactions should be in any blocks it creates? These are just some of the things a pool operator needs to know, regardless of whether or not that operator runs a typical pool like myself, or a p2pool node. The reality is some pool operators don't have the foggiest. This applies to both models - I'm not singling out p2pool here. In a nutshell, on a pool like mine or kano's, the burden of this knowledge is ours to bear. We tune our pools as best we can to produce full blocks with lots of transactions and fees. For example, kano ensures that all of his own pool's transactions are included in the work given to his miners. Why? Because it allows him to confirm the pool's miner payout transactions, which might otherwise not be picked up by other pools. Yes, I am aware of the technical aspects that go into setting up a proper node. I myself took the time to optimize my entire setup from hardware, through system tools, to the bitcoin node itself for maximum performance and payout. To rephrase my original question of "Any ideas?", how do we get everyone onto the same page? I find we still have a problem with getting everyone onto the same version of p2pool. Is this task a bridge too far?
|
|
|
We have been on fire this last week! However, I am still trying to figure out why we historically get so few transaction fees. I look back at the blocks we solve and the blocks surrounding ours are almost always >900kB. The last block we solved, block 435656, was only 20kB. I am betting kano is going to jump in on this and say something like, "People do not configure their setup properly. That is the problem you will always run into with p2pool." In any case, I think we should attempt to improve this somehow. Any ideas?
|
|
|
I am going to guess that the hashrate spike was one of the manufacturers testing their new stuff on p2pool for compatibility. The bummer is that all of my shares were orphaned during the spike.
That of course happens on p2pool when there is one miner with a high % of the pool ... For normal BTC that's called a 51% attack. For p2pool that's ... not uncommon. Thank you for pointing out the obvious.
|
|
|
I am going to guess that the hashrate spike was one of the manufacturers testing their new stuff on p2pool for compatibility. The bummer is that all of my shares were orphaned during the spike.
|
|
|
Hard to decipher if it's random, it's certainly not consistent. It has been a long time since I saw 6 PH/s on P2Pool, and we're back over 100 miners too 😍.
The share difficulty is over 2,000,000. Wild!
|
|
|
What is up with this random hashrate on p2pool? Rentals?
|
|
|
I am having issues with a low end ASIC that was shipping to me with virtually no packing. I was hoping that this thread wouldn't be limited to this particular ASIC (A gridseed Orb) but be a good way to tell in general if any ASIC might be faulty. I realize there will be differences. I am using my Windows machine to run several programs at once, one being cgminer for this device. I have a duplicate item sent by the same person with a lot of packing after I suggested he should because of the possibility of solder shock damage. I get the following errors: the cgminer occasionally quits on me, but more often I see the ASIC read back it's name and then options/specs all in one line across the screen, in the same basic rhythm as is I was getting Accepted lines....ocassionally seeing also the "stratum connection to pool 0 interrupted" message. The other one stays connected the whole time, to the same pool as the first one, and give much problem. What goes? He offered me to send me another as he has a few, but it occasionally stays connected.
I am wondering if your devices are getting enough power.
|
|
|
Antminer S3 doesn't have anything using USB.
I thought the LAN adapter was USB.
|
|
|
I've been working on a new node scanner for P2Pool.org and while I was writing the crawler I realized it would be trivial to add in the network edges for each node and visualize it, so I did. I'm really happy with the result so I thought I'd share it... This is just a snapshot in time (10:30 this morning) of the network, but I may update it hourly at some point in the future. I was quite pleased with our node count and connectivity! 111 active miners 91 nodes discovered (p2pool version 16+) 47 public nodes (blue) 44 private nodes (yellow) The visualization at http://p2pool.org/nodes/ is interactive, allows you to zoom for IP addresses, and click to highlight a nodes peers. I doubt it will work on mobile browsers... Here is a screen shot of the P2Pool network: See the interactive version: http://p2pool.org/nodes/Wow. That is cool. I found my node on the interactive version.
|
|
|
a cointelegraph news article pointed them with new very powerfull mining rigs..what do you guys think?
Personally, I think it looks like a scam. The stock photo on their website looks awfully similar to some of the other 4U units that were fakes. I could be wrong, but 60TH definitely looks questionable especially being on the 20nm node at 0.102J/GH. I could be wrong though.
|
|
|
@ Neuroticfish please post a btc addy so I can send you 75 us dollars in btc. WTF! for a final day of fun check here I placed 0.10 btc for a ckpool play westhash price hash workers current hashing S #1734235 0.9600 0.12 48 0.0709 http://solo.ckpool.org/workers/1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje{"hashrate1m": "106T", "hashrate5m": "65.7T", "hashrate1hr": "8.11T", "hashrate1d": "365G", "hashrate7d": "358G", "lastupdate": 1475928940, "shares": 3690582486, "bestshare": 234326039.29902551, "bestever": 2209707439} all that are on the list for the last diff game will get to split 10 btc I will keep the rest if it hits. It was fun brother! Thank you for your devoted efforts in creating a fun game for all of us to speculate.
|
|
|
Yep, mining farm test ... good to test the P2Pool, too. Well, at least we got a block out of it.
|
|
|
Just an update. Looks like it was a temperature issue. Closed the windows and now its been running almost three days without fault. Great suggestion in2tactics Glad to hear that it worked.
|
|
|
Spoke to soon. It's stopped again. Looks like I may be breaking this for spares and giving up on the mining aspect unless someone has a spare S7LN board as I'd prefer it to have the larger heatsinks.
Are you sure the temperature is not dropping too low? I found that even an unmodded S7-LN likes to drop boards if the temperature goes below 52C. I have my fan on manual in order to keep the temperature between 56C and 60C.
|
|
|
|