Dear BURST community, dear team members,

thank you so much for making this possible! This means very much to me and I'm trying to contribute everything I can to this great project!
We have many marketing and promotion ideas ready which we want to start in the near future. They will definitive help BURST!
As Crowetic already said I will be fully responsible for all marketing activites.
I have already big plans for this but if have you would like to see something special, which I didn't think about, please write to me!
I'm always open for critics and improvements.

Thank you again!





@riskyfire ByteEMini was added. I'll improve the list tomorrow.

Hey dranster,

thanks for your kind words.
We have already developed a marketing strategy which includes Twitter PR, social media articles as well as many other amazing things.
Also the conference, I will attend, is a part of this plan.
But please don't expect that the price rises in the next hours because of this.
You should see the first results after weeks/months  

Agreed! Are they running on the same server? I know they share the same code but its still
odd that they're both stuck on the same block.

The two biggest pools should not be offline at the same time!

The pools all run on individual hosts - and are NAT'd out of the colo on individual addresses. The pools are not technically going down - they're just on different forks of the chain. We're trying to make this harder to happen - each pool has each other blacklisted, so block confirmations have to come from the network, not another pool. So ninja/burst-team believe they've one a block, others on the network agree with them, the other pools don't and we're forked. What would really help is spreading the hashing power over all the pools. With so much hash power on burst-team and Ninja, it's not hard for them to create forks.

I do not understand the mechanics of how a fork happens, however it seems wrong that it needs the hash power to be evenly spread to reduce the risk. It sounds to me that the overall system is in some way flawed if it's this easy to create a fork? Also we seem to be forked for a very long time, surely if we can see it there ought to be a way for the servers to detect it and correct quickly?

I also assume that during the fork the miners on the forked Server are being deprived of the opportunity to win blocks?


Thanks


Rich

I'm going back to Solo mining for a while. I think its best for the Network.

I suspect that it's happening when two different pools have two very similar (identical ?) deadlines, they publish the DL to their peers who confirm it, but if they have different peers, then both DL's can be accepted by different parts of the network.

When any of burst.ninja, pool.burst-team, .eu or biz get onto a forked chain, we pay out of our own blocks the miners winnings from the fake-forked blocks, so no miner ever loses income because of a fork.

H.

Rich,

As I said, burst.ninja and the rest of our pools payout even for rewards "earned" when we're on a fork. Because the rewards didn't equate to deposits into Ninja, it's short on funds for what it needs to do the payouts, and when it's short, it won't payout anything. I've messaged Crowetic to get some Burst deposited; as soon as he does so the pool will pay out.

H.

OK sort of understood, and thanks that you and Crowetic make up the shortfall from your own funds when a Pool forks.

What I do not understand in this case is that a fork to me implies that pools are running but solving different block streams? Whereas during the time of the fork ninja was stalled with no blocks being solved by miners?


Rich