Yes, we have three up and running now, all listed in the ANN.  You can also add http://hashgoal.com/pool/PULS/ they are on the correct fork.

Scorpio -

There was no conspiracy to limit our node's connections to cause a fork in our own coin, there is absolutely no benefit for a coin dev team to intentionally cause a fork on our own coin.  We released the source code and windows wallet to the entire community at the same time.  If a fork happened at block 1, it is because the first pool to mine a block was not synced to our network when it started mining - that is also not a realistic course of action - what pool would intentionally decide to run off on its own chain at the launch of a coin?  The most likely scenario is that a fork happened at block 643 based on what we see on the block chain.  Not having the block0001.dat the fork was on makes it impossible for us to compare blockhashes to confirm/deny exactly when it happened.

We'll be posting a non-mandatory wallet update very soon.  Details in the updated ANN.  Thanks for your support!

pravin, this is in reference to a fork that took place shortly after launch last night.  Hashgoal is on the correct fork, coins mined there are valid on the blockchain.

First off, apologies for taking so long to address this morning's posts.  I spent a much needed day with my family who I'd neglected quite a bit while we prepared for this launch (unfortunately, the wife and kid aren't coders!).

Our nodes were not down at any point as far as we can tell.  Looking through the history of the thread, there were several people that had no problems connecting to them.  We'd set up a node in the US and one in Europe with DigitalOcean to try to have a stable network, it wasn't sufficient.  I can't say why you, ocminer, or poolmn could not connect to them - it was an unfortunate circumstance.

Looking through the BE it seems more like the fork happened at block 643.  That ~40 minute block and immediate drop in diff tells me that a lot of hash left our network preceding that block.



poolmn can you check some of your blockhashes against the block explorer to confirm this?

http://cryptobe.com/chain/Pulsar?hi=675&count=50

Once we get this sorted out we plan to migrate our nodes to vultr to further stabilize the network.  This fork business sucked, there's no two ways about it.  Regardless of the difficulties we've encountered thus far, we will see this project through as far as the community wants us to.  I'll be on for quite some time this evening working and will be available to address any questions or concerns from the community.  Thanks.

We are working on it.  It would be helpful to reach out to the pool operators yourselves as well.  Hopefully we can come to a resolution that is acceptable by everyone involved.

Block explorer up.  Keep on mining, the hash rate is relatively low and there are plenty of coins still available during POW phase.

POS kicks in at block 2,500.  Any coins mined prior to block 2,340 will be mature for staking when that block hits!  

Thanks lahlor!  Definitely appreciate more involvement and you taking the time to set up a pool for Pulsar.

...... That sucks.  I was in IRC trying to get things sorted out and was booted by another pool operator, then insulted when I came back man.  Again, I apologize for the way that worked out.  Hope it didn't cost you too much time, effort, money.

We don't know who received what until block 600 (or beyond for that matter).  Once we get a BE up an running it will be more clear.  We did not instamine it - heck we relaunched the coin because solominers crushed all the early blocks the first time around.  We will continue moving forward with development of Pulsar and growing this community.  We have high hopes for the future of this coin and what it has to offer.

Another pool is up!

https://pulsar.miningpool.cc

Adding to ANN

We were willing to go with your fork but you pulled down your pool with no discussion on the matter man.  How could anyone sync to that fork with nowhere to sync with?  We do appreciate you setting up and running the pool and are sorry it worked out that way, obviously wasn't our intention.



Thanks lahlor!  Will add to our ANN.

We posted in both sections.  The thinking was that more pool operators probably have alerts set up for the Announcement area than the Pool area

Pool operators, we launched Pulsar last night and are in need of additional pools in order to spread out the hashrate and promote a more even distribution of our coin.  We currently have only one pool that is pulling anywhere between 200TH and 1PH at any given time.  If you are interested, the source is available in our Pulsar Announcement Thread.  If you have any additional questions, etc feel free to ask.  Looking forward to seeing more people get involved in our community!

Pool operators, we launched Pulsar last night and are in need of additional pools in order to spread out the hashrate and promote a more even distribution of our coin.  We currently have only one pool that is pulling anywhere between 200TH and 1PH at any given time.  If you are interested, the source is available in our ANN page @ Pulsar Announcement Thread.  If you have any additional questions, etc feel free to ask.  Looking forward to seeing more people get involved in our community!

Good catch there Vixa, sorry about the mistake in my post, it has been corrected - we were up very late last night digging into this fork issue and addressing community concerns.  The issue with the fork has nothing to do with the code and had to do with a massive influx of blocks that our nodes could not keep up with very early in the POW phase. 

As to the code, we are confident it is a solid piece of work.  You are more than welcome to look and see if there are any problems with it - the source is posted  



trader, yes we have plans for this coin.  MNs are already in the code and will be active on 18 July.  We chose a later date to ensure that the 8,080 block goes to one user, and was not split with a MN.  Incidentally, 8,080 is the amount of PULSE required to run a MN.  We'll unveil a much more comprehensive picture of our vision for the future in a polished product in the coming days.

Right now our efforts are focused on building this community and getting more pools on board to ensure a more even and fair distribution of coin takes place   If any of you can get the word out to additional pools and bring them into the family, it would be much appreciated!

The fork issue has resolved itself it appears.  There is an active pool with over 150TH/s hashing on it at hashgoal.com/pool/PULS/ on the same chain as our nodes.  There is currently no way to sync with the fork that suprnova and pool.mn were on.

If you are still having issues syncing to our nodes, you can add hashgoal to your conf.  I tested this on another PC using only hashgoal as a node and the wallet sync'd to the proper chain.

We are currently on block 1071.  Block range 1501-1551 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.

We have no problem accepting that fork.  But the pools are down and there is no way to sync to it.

There is a pool currently up at http://hashgoal.com/pool/PULS/ that is on the same chain as our nodes.

We are not proposing a relaunch.  Whatever decision is made, prefork coins will be intact.

It will depend on which blocks you got rewards for.  If they were before the fork, you'll get them.  If they were after the fork, it depends on which chain you mined them on.