Bull shit words about how you worked for free and did know what you were getting into. Blah blah blah
This is simple, stop supporting scam coins. What makes this coin a scam? I am glad you asked; what does this coin offer to the community that 100 other coins JUST like it do not? If a coin is great, it will not require a pre-mine. If it offers great services, i.e. new services that other clones do not, then it will have no problem being supported. People will come out of the woodwork to assist for FREE! Get off your high horse. If your Coin can't be changed directly for fiat like Doge or Bitcoin can then your coin is technically a scam. Hell all crypto amounts to Ponzi scheming and online gambling. Get over yourself. This coin offers nostalgia. Think of crypto like stamp collecting. Do you really need 10,000 different stamps? Someone does. Agreed. It's all about the cult following and popularity, "features" don't matter squat anymore. In time, that may come back into play - but for now, it's about which coin is the "cool kid on the block." |
|
|
|
AIR.pitythepool.com is back onlineSorry again for the problems, everyone. Hopefully the DDOS pricks will stay off it for awhile 
|
|
|
|
|
So WTF happened with the block reward halving? Er, quartering? Is the next "halving" going to take us down to 32k coins?
|
|
|
|
We are essentially catching up by 5-7 network days, depending on that day's block times, every actual 24 hours. Which means we are only adding about 1/8 of what we are eating up
Even with such a shitty situation, we are still far ahead of many older, more established, higher market cap coins on coinwarz, and I'm not referring to merge mined. Those don't count
It's actually a little worse than that, look at the ABE explorer and check out blocks since the diff adjustment on 3/4: March 5 the network mined a total of 6 blocks, and averaged 282 minutes per block March 6 the network mined a total of 5 blocks, and averaged 264 minutes per block March 7 (today) the network has mined a total of 6 blocks so far, averaging 155 minutes per block We could give this a few more days I suppose, and see if it works out averaging to the ~80 minutes per block it should be given the hashrate and current diff, but so far it looks pretty grim. The above post was right about PityThePool - despite only having about 1/3 of the network hashrate, it has found 18 out of the past 20 blocks. Not sure what would cause that - maybe PityThePool is just really kickass |
|
|
|
Sorry for the issues lately ith AIR.pitythepool.com
The AIR pool has been under intense DDOS attacks for over a week now, 6-12 hours per day. They have been targeting the AIR pool specifically. Yesterday it was finally large enough I had to have the firewall reject all requests to that host to conserve server resources.
I will bring the pool back online later today. Everyone's coins are safe and cron jobs are still running, so if you had auto-payouts enabled you should have already received your coins.
Sorry again for the all the trouble.
Thanks for the update. To your credit, I've mined on a few of your pools and they've always seemed solid. I appreciate the kind words. We have several DDOS mitigation techniques in place but unfortunately it's pretty much impossible to protect yourself 100%, depending on the type and size of the attack. 6-12 hours a day for a week is a good chunk of time for someone to point their bots at a site. Someone really, really wanted that pool to go down. |
|
|
|
|
Sorry for the issues lately ith AIR.pitythepool.com
The AIR pool has been under intense DDOS attacks for over a week now, 6-12 hours per day. They have been targeting the AIR pool specifically. Yesterday it was finally large enough I had to have the firewall reject all requests to that host to conserve server resources.
I will bring the pool back online later today. Everyone's coins are safe and cron jobs are still running, so if you had auto-payouts enabled you should have already received your coins.
Sorry again for the all the trouble.
|
|
|
|
We are 15k blocks ahead of schedule. This has nothing to do with wanting to hold what we already have. None of us have sold a single Benjamin, and in fact have used most of what we mined for giveaways on Reddit, Twitter, Cryptocointalk, and several other sites
Read what Igotspots quoted above. It explains our decision and gives reasons why a fork would make the situation worse. 10 minute block times are better for security, this is a known issue, as well as the KGW holes recently found, further strengthen our decision not to fork
Coins should not be created to serve the miners, but the consumers who will use them in the end. Benjamins will be one of the most secure blockchains once it has the hashpower to back up the numbers. Security and not losing coins or leaving them vulnerable to attack so vendors, exchanges, or traders don't lose payments is more important to us than making a few coin hopping miners happy. I'm sorry, but that's the truth. The ones that have stuck around mining since the beginning will enjoy having rarer-than-planned coins, but that was definitely not our intention
Sorry to be blunt but you are delusional. Appealing to miners is ABSOLUTELY REQUIRED. Without miners transactions cannot be confirmed. No sending coins, no receiving coins, no mining coins. I'm not saying BEN needs KGW. I'm not saying BEN has to decrease the block time (although, it would be my preference if it did). But the diff adjustment issue has to be addressed. Mark my words, the next diff adjustment will never, ever, ever arrive, BEN will never, ever, ever see anything close to 10-minute block times again if you do not fork this coin. I can't make it any more clear. If we make difficulty adjust faster, it will go up every block. Every block will get harder than the previous, increasing the time even further than if it jumps every 2000 blocks. The long time in between will let the network catch up. If difficulty is changed more frequently, it will go up more than if we don't fork it before it goes down You did the math before, so I know you understand how far ahead we are. Surely you realize what I mean? I do understand what you mean, but I don't think you understand what I mean Simply changing the diff adjustment to every 1 blocks will not fix the problem. The diff algorithm itself also needs to be changed, and adjusted to take into consideration the current block height. Current diff algo looks at the current block height, versus the expected block height and adjusts the difficulty up or down based on how close we are to the expected block#. This algo is no good, BEN will never, ever correct itself using this algorithm (well, maybe eventually, but it will take YEARS). A new diff adjustment algorithm must be implemented, maybe one that does not look at the expected block height, but looks at the length of time it took to complete the previous X number of blocks and adjusts the diff accordingly (pretty sure this would work, but I'm just shooting from the hip here). Additionally, the diff adjustment period must also be reduced - otherwise, BEN will simply end up with the same problem again in a couple weeks. Max time at current hashrate will be 4 months to be where it should be, sped up with more miners that hop on. This problem will never happen once it catches up, because the network will not allow it to get that far ahead. It only happened because ASIC power wasn't accounted for in the initial difficulty This, once corrected, will NEVER happen again. It's impossible to get 5 times ahead of the network other than with a massive launch Maybe 4.5 months from now only if you shutdown the network and mined ZERO blocks between now and July. Current block height is 24212, given the coin's 10-minute block times that block height should not have been reached until around July 20. But BEN is going to mine blocks between now and then (slowly, yes, but it will happen). This will continue to push the date out further. Current nethash is 1.3TH - what are you going to do when the coin gets "back to normal," 60TH worth of miners hop in and mine the next 2016 blocks in 3 hours? The diff will spike enormously again, because the blockheight is ahead of schedule, miners will hop off, and BEN will be right back where it is now. Regardless of the above, the next diff adjustment is not going to hit in July anyway. It will be way, way further out than that. Block times are going to continue to increase, unless you've got several TH of personal mining power you're willing to throw at BEN for the next 4 months. Each day, the # of days until the next diff adjustment is going to increase. There's a good chance BEN may never reach it. Fork the coin. It has to happen. |
|
|
|
We are 15k blocks ahead of schedule. This has nothing to do with wanting to hold what we already have. None of us have sold a single Benjamin, and in fact have used most of what we mined for giveaways on Reddit, Twitter, Cryptocointalk, and several other sites
Read what Igotspots quoted above. It explains our decision and gives reasons why a fork would make the situation worse. 10 minute block times are better for security, this is a known issue, as well as the KGW holes recently found, further strengthen our decision not to fork
Coins should not be created to serve the miners, but the consumers who will use them in the end. Benjamins will be one of the most secure blockchains once it has the hashpower to back up the numbers. Security and not losing coins or leaving them vulnerable to attack so vendors, exchanges, or traders don't lose payments is more important to us than making a few coin hopping miners happy. I'm sorry, but that's the truth. The ones that have stuck around mining since the beginning will enjoy having rarer-than-planned coins, but that was definitely not our intention
Sorry to be blunt but you are delusional. Appealing to miners is ABSOLUTELY REQUIRED. Without miners transactions cannot be confirmed. No sending coins, no receiving coins, no mining coins. I'm not saying BEN needs KGW. I'm not saying BEN has to decrease the block time (although, it would be my preference if it did). But the diff adjustment issue has to be addressed. Mark my words, the next diff adjustment will never, ever, ever arrive, BEN will never, ever, ever see anything close to 10-minute block times again if you do not fork this coin. I can't make it any more clear. If we make difficulty adjust faster, it will go up every block. Every block will get harder than the previous, increasing the time even further than if it jumps every 2000 blocks. The long time in between will let the network catch up. If difficulty is changed more frequently, it will go up more than if we don't fork it before it goes down You did the math before, so I know you understand how far ahead we are. Surely you realize what I mean? I do understand what you mean, but I don't think you understand what I mean Simply changing the diff adjustment to every 1 blocks will not fix the problem. The diff algorithm itself also needs to be changed, and adjusted to take into consideration the current block height. Current diff algo looks at the current block height, versus the expected block height and adjusts the difficulty up or down based on how close we are to the expected block#. This algo is no good, BEN will never, ever correct itself using this algorithm (well, maybe eventually, but it will take YEARS). A new diff adjustment algorithm must be implemented, maybe one that does not look at the expected block height, but looks at the length of time it took to complete the previous X number of blocks and adjusts the diff accordingly (pretty sure this would work, but I'm just shooting from the hip here). Additionally, the diff adjustment period must also be reduced - otherwise, BEN will simply end up with the same problem again in a couple weeks. |
|
|
|
We are 15k blocks ahead of schedule. This has nothing to do with wanting to hold what we already have. None of us have sold a single Benjamin, and in fact have used most of what we mined for giveaways on Reddit, Twitter, Cryptocointalk, and several other sites
Read what Igotspots quoted above. It explains our decision and gives reasons why a fork would make the situation worse. 10 minute block times are better for security, this is a known issue, as well as the KGW holes recently found, further strengthen our decision not to fork
Coins should not be created to serve the miners, but the consumers who will use them in the end. Benjamins will be one of the most secure blockchains once it has the hashpower to back up the numbers. Security and not losing coins or leaving them vulnerable to attack so vendors, exchanges, or traders don't lose payments is more important to us than making a few coin hopping miners happy. I'm sorry, but that's the truth. The ones that have stuck around mining since the beginning will enjoy having rarer-than-planned coins, but that was definitely not our intention
Sorry to be blunt but you are delusional. Appealing to miners is ABSOLUTELY REQUIRED. Without miners transactions cannot be confirmed. No sending coins, no receiving coins, no mining coins. I'm not saying BEN needs KGW. I'm not saying BEN has to decrease the block time (although, it would be my preference if it did). But the diff adjustment issue has to be addressed. Mark my words, the next diff adjustment will never, ever, ever arrive, BEN will never, ever, ever see anything close to 10-minute block times again if you do not fork this coin. |
|
|
|
I don't think you guys understand. Even if they fork it now to change block time or diff adjust it will only get worse The network thinks it is several weeks ahead of schedule If you want to speed it up then more miners need to be on the network. Thats it really. Ben summed it up pretty well a few pages back. Since I don't feel like typing it all I'll just quote it The general consensus last night was to let it be. This will keep the block time of all 4 coins on Paysha at 10 minutes
What does this mean for Benjamins?
It's going to suck mining for a little while. The difficulty keeps increasing, because we should only be on block 4500ish right now, not 20,000. We got way ahead early because so many ASIC miners jumped on before the first few adjustments. Benjamins will become extremely hard to mine for the next month, or even longer, depending on hash rate. Paysha will support BEN even if the transactions are slow for the first few months due to the problem. Both teams feel as if 10 minute blocks are better in the long run for network and transaction security, regardless of the short term damage. Changing the difficulty now would alter the lifespan of the coin to a degree that would ruin it. It would be mined out too fast. I know it seems like it's broken, but it's the exact opposite. Benjamins network is spiking difficulty to fix itself, rather than allow more Benjamins to be mined ahead of schedule
Thanks for your continued support of Benjamins
I assume the next few pages will be extremely negative, and it's deserved, so let's have it
OK, so add more miners to the network. Easier said than done. For miners to join up, there has to be something attractive about the coin. Profitability is the most important, or at least potential profitability. I'll agree BEN has some potential with the Paysha launch but with the horribly, horribly slow block times and very low hashrate, it's sorta like putting chrome rims on a rusty 1971 Ford Pinto to make it look better. You can't polish a turd. Right now I could earn about 0.002 BTC per day (maybe less) with ~350GHash mining BEN. Why would I do that when I could make 20x as much mining BTC or any number of other altcoins. I dislike the 10-minute blocktime but if it's that important to keep it, I'll respect the decision to do that. However, the coin still needs forked to correct the diff rut BEN is in right now. Just when BEN's first payment provider is about to launch, the entire network is stuck paying the price for something that happened a month ago, when early miners jumped on and mined a ton of easy BEN's when the diff was low. The diff algo needs to be reset, adjusted to compensate for the current block height (not expected block height) to get BEN back on track with 10-minute block times at the current network hashrate. Future diff adjustments should happen WAAAAY sooner than every 2016 blocks, more like every block or 2 blocks, or BEN will simply get back into this situation in another 2 weeks. |
|
|
|
|
I have tried as well with no luck . . . just tried mining LGBT, diff is only 1024. Antminer GUI shows connected & alive, but I'm not getting anything.
Solo-mining on a private pool (I'm the only one on the pool) I find a block a minute at least
|
|
|
|
No pools are working. Coin is broken. I an the op for PityThePool above. Coin generates errors on most transactions > 100k, diff is not adjusting correctly causing tons of orphans and other issues. Diff (1024) is still low enough that you can solo mine, if you dare . . . |
|
|
|
It doesn't have to be Gravety well!!!! I looked at the code, just drop the 2 weeks retargeting!
Looked further into BEN's code. The cut and paste of BEN was... cut and paste. Unfortunately, it didn't account for the new high power ASIC miners out there. And the launch was poorly done, resulting in what we have now. If BEN would have been premined (at 0 rewards, for example) from 0.0000244 diff to a safe diff, like 1 or 2 - we wouldn't have this problem today. BEN had to go through 6 order of magnitude from the genesis block diff, to multi GH/s inputs in a short time. Classic error. The Bitcoin code was originally based on CPU mining (a few KH/s) - not GH/s ASICs like today!. Even with today's CPUs, from the genesis block, you can get the first 100 blocks with a single CPU in 5 mins! (One order of magnitude = 10x increase, therefore, 6 order of magnitude = 10^6) BEN has a very long diff adjustment, like Bitcoin - but doesn't have the network to support it. I will either die - or survive, but only if it changes its difficulty to match its 2014 customers. In summary, lots of early people got LOTS of BEN early, which would explain the reluctance to change anything at this point. But, if they don't do anything, their fast earned coins will be worthless very soon.. I've said my piece on this before and I agree with nerioseole above. This coin IS BROKEN and will *never* be successful unless the diff retarget, and probably block generation time are changed. Benjamins - you said yourself, you FUCKED UP and accidentally left testnet code in production which resulted in a 10-minute block time, rather than the 64-second block times advertised since the coin's launch. Your first step towards success was admitting the mistake, but your biggest mistake was deciding to leave it that way. I don't see how anyone can admit to a mistake that huge and then refuse to fix it. Worst of all, at the same time, try to convince everyone it's better this way? At current rates it is taking 75 minutes to find a block and BEN is now at least 100 days to next diff adjustment. Except it won't be 100 days. By tomorrow block times will be 85 minutes. The next day, 95. The network hashrate will continue to drop, block times will get longer. This trend is going to continue until the coin is forked. The next diff adjustment will never arrive. Not trying to be a hater - I have supported this coin, you know I have - but Benjamins is OVER until this coin is forked. |
|
|
|
PLENTY OF ROOM FOR MORE - PAYOUTS EVERY 4 MINUTES
Pity the Pool! HeisenbergHex (HEX) Pool- Solid servers, UPS/generator backups
- USA based
- Redundant internet
- 1.5% fee
- Dedicated equipment - we own the hardware, we own the data center
http://hex.pitythepool.com |
|
|
|
I've been busy and haven't checked in a couple days so I wasn't sure. I won't worry about it for now but I should probably lower my payout threshold so it doesn't take so long between payouts. Edit: The site is up now but the minimum payout is only able to be set to 100.  Send him a message. All the pool ops listed in the OP are extremely helpful I have lowered the min payout to 1 BEN - sorry it's an MPOS default I just forgot to change These DDOS attacks are getting really annoying. They were really only attacking one pool but since the web front-end for all my pools is the same server they pretty much all went down. I'm going to scale out a bit with the pools so one getting attacked doesn't take everything down. I own two entire Class C address blocks no reason why I can't setup each pool with its own IP |
|
|
|
WALLET READY - WE ARE MINING
Pity the Pool! HeisenbergHex (HEX) Pool- Solid servers, UPS/generator backups
- Redundant internet
- 1.5% fee
- Dedicated equipment - we own the hardware, we own the data center
http://hex.pitythepool.com |
|
|
|
WALLET READY - WE ARE MINING
Pity the Pool! HeisenbergHex (HEX) Pool- Solid servers, UPS/generator backups
- Redundant internet
- 1.5% fee
- Dedicated equipment - we own the hardware, we own the data center
http://hex.pitythepool.com |
|
|
|
I love all the spam for the pools and not one up and running  That's because there is no source or linux binaries available yet |
|
|
|
|
Source and/or linux binaries please!!
|
|
|
|
|
Show Posts
