Topic: [ANN] [BEN] Benjamins ◄ SHA-256 ►◄ BOUNTY AVAILABLE to make BEN merge mineable!! - page 31. (Read 94414 times)

Why is it 2000 blocks or EVERY block? is there no where in the middle?

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?

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.

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.

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

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

FREE pool at iSpace Mining Pools

http://ispace.co.uk

I would like this coin to do well. But I am confused what is going on i do not understand re targets and all the other technical stuff.

Will this coin bounce back or will it wither away and die. The way you explain it is by hashpower will sort it so how do WE / YOU Get the message out for more miners.

Admittedly I dont have much hash maybee 40 ish ghs. But iam getting 10% of what it was a week ago

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.

First of all I'm not Ben. Second I posted an exploit for Gravity well. I would say that's pretty relevant since that what I'm guessing you want to see

Block time is 10 mins I think

Anyway this is one reason I advised and still suggest not giving in to complaints. Some of us understand security

https://bitcointalksearch.org/topic/delete-504103

Welcome back....

A wise man once told me... "dont feed the trolls" so no matter how arrogant/instigating and pretentious your next comment is ill simply remember like you said "your compitition" so obviously are grasping at desperate straws and now have to resort to trolling. So be it, ill refrain from replying now i have you figured out, may BEN supporters feel honored you consider us competition, for we dont even know who you are, what you are about, or what coin you are marketing....

"We are all born ignorant, but one must work hard to remain stupid."
-Benjamin Franklin

Yea, once an hour on average

24211   nickbiker   07/03 01:58:15   23,719
24210   nickbiker   07/03 00:56:08   109,892
24209   nickbiker   06/03 20:09:18   66,989
24208   HenryFord   06/03 17:15:07   22,989
24207   HenryFord   06/03 16:12:34   125,696

That is only due to low hash rate. Although you are quite off

Est. Avg. Time per Round (Network)   1 hour 16 minutes 3 seconds

"In this world nothing can be said to be certain, except death and taxes." - Benjamin Franklin

....The problem with visa and mastercard is any 12yr old russian script kiddy can fire up sqlmap or similar tool and with no actualy skills in sql let alone hacking go out and scan all of africa and third world countrys for shitty configured webstores, then with the press of a button dump the data, loginto tor and sell it to carders....
I wouldnt blame visa as much as i would blame shitty third world web devs, pay penuts get monkeys.

Paysha will not be vunrabile to such exploits, even if the data was dumped the passwords (one would hope would be hashed) so "theif" has nothing....

Also in regards to mastercard and visa alot of the data for sale is from actaull employees and stoer owners they install skimmers on there own POS and harvest the data then sell. You will find 90% of card data comes from dodgy store owners and employee's the rest from third world countrys..... many a times swim has found a thirdworld webstore running mysql as root user and hosting 100+ pages from the same DB.... you would be suprised how many well known USA sites are hosted in a dodgy thirdworld shared hosting enviroment.


For instance...
If you use the SAME PASSWORD YOU USE HERE anywhere else then you are fucked, ie: if you use the same password from bitcointalk on paysha, say goodby to your funds, this isnt paysha's fault, its yours. Hacker hacks this site bitcointalk, dumps DB uses his "bitcoin mining" ASICS to crack your passowrd hash with salt then uses bot to try combo's on a list of 100+ bitcoin related sites, stores results and laughs all the way to the bank, but who is to blame? not paysha but you for using the same dodgy password for everythign you do online...... No asic could crack my 16 + char password, and its different for everysite.

Told you he would respond soon! Thanks for paying attention to the miners

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

Send him a message. All the pool ops listed in the OP are extremely helpful