Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 436. (Read 1210783 times)

While I agree that the aws miners are currently problematic for this note, primarily because of the difficulty adjustment algorithm, a GPU miner is not the correct solution to that problem. If you think having an onslaught of GPU miners seeking the smallest increase in their daily profitability is going to be even remotely beneficial for the value of the currency and the investors, you're sadly mistaken.

I think a modification to your difficulty algo should be your objective. I'd avoid GPU mineability at all costs.

Thanks. We will use some of that.

Found a tool about bbr:
http://whatmine.com/coin/601/-

By the way, The title of this thread can be modified:

[ANN][BBR] Boolberry | Frist ever Anonymous/Cryptonote/Alias | No IPO/Premine | 2 EXCHANGES

It will be better.
Thanks.

I suggest Dark Gravity Well 3.

I think this coin need Explorers.~~~~~~~~~~~~~~~

I think we need to implement Kimoto's Gravity Well to regulate difficulty. It will change the difficulty more quickly.

At the risk of providing facts:  I was perhaps 1/4th of that increase - with apologies.  It was EC2, no GPU.

I suspect I know what happened:  I looked at the diff, calculated that it was profitable on EC2 to mine at a particular rate, and launched quite a few hundred c3.8xlarge instances.  My goal was to let the diff creep back up to where it should be based on the hashrate, and top out at the end of where it was profitable on EC2, and then kill the instances.

... what I forgot is that this wasn't a vacuum.  The hash rate increased *way* faster than I thought it would, and my guess is that about 10 other people all had the same idea at about the same time when the profitability calculation looked positive.  One or two of them probably launched up to 1000 instances.

The combination of all that resulted in a huge diff spike (which I think might be interacting with a mis-tuned parameter in the difficulty retargeting).  When I got up this morning, I saw the diff, said words I won't utter in a public forum, and immediately killed all of my instances.  Looking at the hash rate graph, I think other people still had instances starting up or running, because it kept increasing even after I killed about 600mh/s.  And then it tanked when all of the cloud miners suddenly realized they were bleeding away money.

I'm not going to do that again.

Look above, crypto_zoidberg showed there is overwhelming evidence it is ec2 (and someone said 60% of their peers were amazon). The sooner the public GPU miner, the better. That would make net hashrate much more stable, and if someone has a private GPU miner, level the playing field.

And considering people are saying this coin is no longer currently profitable to mine with EC2 instances, and afterwards the hashrate triples or something to that effect this morning, I would have to conclude someone found a way to write up a GPU miner.

To all who is wondering where did the evil came from: if it is a super-GPU or it amazon: take a look to BBR graphs: http://boolberry.com/state.html



You could see there just a lot of new connections, and a lot of peers appeared in greylist. And this is only peers seen by one machine(monitoring node).

So it seems that it was just huge amazon evil.

>And how much do they pay each time they do that?
Unfortunately not everyone have to pay for servers

Thing is, a GPU miner would likely be extremely profitable to keep running, even at a high difficulty. However, you'll notice that, upon crossing the point where each coin mined on EC2 would cost more than it would sell for at the exchange, the hash rate drops off extremely quickly.

And how much do they pay each time they do that?
You only have to buy graphics cards once.

Why? There are people who can launch thousands of instances on Amazon for a hour....

I bet you it's a GPU miner.

When does diff retarget?

Whoever this is: STOP THAT!

Cloud people left when difficulty went to 214G

No block in 3 hour ?

While I believe a GPU miner for wild keccak is possible, it is an extremely different hashing algorithm than what the other CryptoNote coins currently use.

The speed is equal to a high powered CPU, so Its not really all that much of a benefit. Also, we are waiting to see if it is even cost effective based on power consumption. This will give the cryptonote guys something to work on if they do indeed want to remove the fact that its possible which would just be a fork away.