Bitcoin Forum

Its dead.  Poolmn intentionally forked and raped all the early blocks.  Steer clear of this pool. 

ok lets try this again =)

https://pool.mn/psr is ready !

my pool is already prepared, waiting on the source to launch.

www.suchpool.pw/pulse

(i might be slow because I am beyond busy at work, sorry!)

edit; nodes won't sync. no go.

mining.neosstore.com will have it back up when the src is released :)

DEV can launch a coin!

Source and windows wallet in ANN.  Let's do this right this time!!!!

I'm ready:

https://37.59.18.108

DNS not working currently, hence the direct IP

OK, we're up: https://pool.mn/psr

up but not synced yet.. waiting on nodes to connect but they aren't...

nodes are on the ann and where is your link?

Sorry wallet was not syncing for me at first, but the pool is now up

No sync in windows wallet even with nodes added

    "connections" : 0,

DOA! Have it all Suprnova :)

Busy at work, no time to loose on this.

How not found any block!

Anything i try windows wallet won't sync. So nice try for an even relaunch but it didn't worked out

http://mining.neosstore.com is alive

Did you addnodes listed in the ANN to your pulsar.conf?  That may help.

The blocks are flying like crazy lol

"version" : "v2.0.0.0-g32a928e",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : 500.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 587,
"timeoffset" : 0,
"moneysupply" : 290700.00000000,
"connections" : 4,
"proxy" : "",
"ip" : "",
"difficulty" : {
"proof-of-work" : 1316.00329085,
"proof-of-stake" : 0.00390625
},
"testnet" : false,
"keypoololdest" : 1436258561,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""


EDIT: First launch was a fail and i think the second one was the same a fail , so 900 blocks mined in a few minutes

Of course i did

Synced fine for me but only got a couple blocks  :'(

My cronjobs are struggling.. Should be fine soon.

Nevermind mining.neosstore.com is dead cause wallet aint syncing

Nodes are rejecting connections. Moreover, they are hosted at digital ocean.. It seems that many times in the past some coins have had sync/fork issues with nodes hosted there. I thought devs understood by now it was shite..

Surprisingly ocminer had no trouble syncing, everyone else did  ??? ::)

12:02:22

getmininginfo


12:02:22

{
"Blocks" : 514,
"Current Block Size" : 1000,
"Current Block Tx" : 0,
"Difficulty" : {
"Proof of Work" : 43497.52134415,
"Proof of Stake" : 0.00390625,
"Search Interval" : 1
},
"Block Value" : 35000000000,
"Net MH/s" : 6026465.53645758,
"Net Stake Weight" : 0.00000000,
"Errors" : "",
"Pooled Tx" : 0,
"Stake Weight" : {
"Minimum" : 0,
"Maximum" : 0,
"Combined" : 0
},
"Stake Interest" : 9000000,
"Testnet" : false
}

Pools are at block 934 now. Forked?

No problems here either, just use the nodes from the OP, we were up before 'nova

I had problems too syncing, but in fact I just used your pool as seednode  ;D

The nodes was closing my connection on win wallet

send version message: version 60015, blocks=0, us=xxxxxxxx:43208, them=188.166.121.151:43208, peer=188.166.121.151:43208
ThreadDNSAddressSeed exited
socket closed
disconnecting node 188.166.121.151:43208
trying connection 188.166.121.151:43208 lastseen=371182.9hrs
connected 188.166.121.151:43208
send version message: version 60015, blocks=0, us=xxxxxxxx:43208, them=188.166.121.151:43208, peer=188.166.121.151:43208
socket closed
disconnecting node 188.166.121.151:43208
trying connection 45.55.164.108:43208 lastseen=86.9hrs
connected 45.55.164.108:43208
send version message: version 60015, blocks=0, us=xxxxxxxx:43208, them=45.55.164.108:43208, peer=45.55.164.108:43208
socket closed


So this is just another fail launch like the first one

2 launches,2 fail. Good.

sell 50K=0.3BTC.to pm

nice instamine here:

https://pool.mn/psr/index.php?page=statistics&action=blocks

i'm out

My daemon was never synced, so technically you didn't sync for me. I didn't get the chance to get a single working connection. Dunno why exactly since I can trace/ping both seednodes, but they end up in socket error and won't connect.

I just used suprnova as addnode I got connections immediately:

That's good ole xinbin.... he does that when shadowrunner is not around

Alright guys i got it to sync mining.neosstore.com

I have 10 connections, but I have not suprnova in my addnodes and I'm on different fork with suprnova,
but blocks are getting confirmations in my wallet. So what fork is right?

So pool.mn was getting connection to the nodes posted on the ANN but the rest of us dont , hmmm thats strange , even ocminer used pool.mn as a node hmmm..

I had connections at launch, before pool.mn started, but we are on different forks.

OCminer, we need you to pause your daemon, delete your blockchain data, and sync to the nodes again.  You've run off on a fork with all that hash.

@Dev: This wouldn't happen if you'd have your nodes right.


OK i've stopped the pool and closed it - please switch to the other pools guys ! have fun with this coin

Thanks and sorry for wasting your (and my) time !

Which is the correct fork ? Are we mining on the correct fork ?

It seems that you were at wrong fork at launch and suprnova added you as node too.

Yes. I have successfully extracted coins into my wallet

So just for the record there were a few lucky persons who managed to get synced and others were mining on a fork because nodes refused connections. Right? It seems that relaunch is even worse than original launch...

Suprnova was at the same fork, but he closed pool, because dev said that he was on a wrong fork.
Dev, what fork is right?

that means you're on the same fork as we, but that does not mean the dev accepts this as the correct fork. we where on the same fork as suprnova all the time

I don't think Suprnova has a fork.

Correct fork:

{
    "version" : "v2.0.0.0-g32a928e",
    "protocolversion" : 60015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 565,
    "timeoffset" : 0,
    "moneysupply" : 283000.00000000,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : {
        "proof-of-work" : 85015.57354659,
        "proof-of-stake" : 0.00390625
    },
    "testnet" : false,
    "keypoololdest" : 1436256093,
    "keypoolsize" : 101,
    "paytxfee" : 0.00100000,
    "mininput" : 0.00000000,

https://pool.mn  skam pool !!!!!!

I'm in your pool.

Ok then we are on wrong fork too.

Closing the pool now.

So i was on wrong fork. to, and those nodes arent working ;\

Suprnova, can you please temporarily pause your daemon, delete your blockchain data, and sync to the nodes again they are still at 577 block


Pool.mn, please resync with us.

We can get this fork resolved, it happened at block 577.

I can't sync to those nodes

12:45:22

getpeerinfo


12:45:22

[
{
"addr" : "144.76.238.2:43208",
"services" : "00000001",
"lastsend" : 1436262240,
"lastrecv" : 1436262203,
"conntime" : 1436262061,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : false,
"startingheight" : 1067,
"banscore" : 0
},
{
"addr" : "116.26.20.66:61518",
"services" : "00000001",
"lastsend" : 1436262066,
"lastrecv" : 1436262241,
"conntime" : 1436262065,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 1067,
"banscore" : 0
},
{
"addr" : "173.23.75.89:56368",
"services" : "00000001",
"lastsend" : 1436262310,
"lastrecv" : 1436262208,
"conntime" : 1436262066,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "45.55.164.108:54884",
"services" : "00000001",
"lastsend" : 1436262073,
"lastrecv" : 1436262076,
"conntime" : 1436262072,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "52.25.69.193:43208",
"services" : "00000001",
"lastsend" : 1436262308,
"lastrecv" : 1436262239,
"conntime" : 1436262079,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : false,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "184.75.214.131:45606",
"services" : "00000001",
"lastsend" : 1436262308,
"lastrecv" : 1436262199,
"conntime" : 1436262107,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "174.117.18.129:53578",
"services" : "00000001",
"lastsend" : 1436262312,
"lastrecv" : 1436262109,
"conntime" : 1436262108,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "188.166.121.151:45756",
"services" : "00000001",
"lastsend" : 1436262113,
"lastrecv" : 1436262316,
"conntime" : 1436262113,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "37.59.18.108:45003",
"services" : "00000001",
"lastsend" : 1436262197,
"lastrecv" : 1436262309,
"conntime" : 1436262190,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 1064,
"banscore" : 0
},
{
"addr" : "188.64.171.182:29542",
"services" : "00000001",
"lastsend" : 1436262252,
"lastrecv" : 1436262252,
"conntime" : 1436262251,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "173.23.75.89:60070",
"services" : "00000001",
"lastsend" : 1436262308,
"lastrecv" : 1436262307,
"conntime" : 1436262306,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : true,
"startingheight" : 587,
"banscore" : 0
}
]

it is not so easy as you think as all the blocks since 577 > 10xx are/were already mined and credited on the pool. So if I reset the blockchain, I'd have to rework the whole transactions database to get that stuff sorted out.

IMHO its too much work, you'd be better off with a "new" pool here.

And BTW: I tried connecting from a separate server to your nodes, they STILL do NOT work...

What you dont understand man , we cant get connected to your nodes


connected 45.55.164.108:43208
send version message: version 60015, blocks=0, us=0.0.0.0:0, them=45.55.164.108:43208, peer=45.55.164.108:43208
socket closed
disconnecting node 45.55.164.108:43208
trying connection 188.166.121.151:43208 lastseen=371184.0hrs
connected 188.166.121.151:43208
send version message: version 60015, blocks=0, us=xxxxxxx:43208, them=188.166.121.151:43208, peer=188.166.121.151:43208
socket closed

Okay finally mining.neosstore.com shall work now!

Me neither wallet was open for an hour now and still no connection to the nodes in op

We restarted the nodes.  Please try connecting to again.  We have 18 connections currently.

{
    "protocolversion" : 60015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 596,
    "timeoffset" : 0,
    "moneysupply" : 0,
    "connections" : 15
    "difficulty" : {
        "proof-of-work" : 110289.70674336,
        "proof-of-stake" : 0.00390625
    },
    "testnet" : false,
    "keypoololdest" : 1436256093,
    "keypoolsize" : 101,
    "paytxfee" : 0.00100000,
    "mininput" : 0.00000000,
    "errors" : ""
}

block 1 ?

soo all pools were on same fork, were tossing that out and going with the solo miners fork at ~600. How is this different from last time....

Rename the coin and call it IDC - Idiot Dev Coin

The problems is right now there are some peers on the wrong fork so is hard to get on the right one when you try to re-sync , i have managed to get connection to one of your nodes and i'm on the right fork right now



{
"version" : "v2.0.0.0-g32a928e",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0000.00000000,
"stake" : 0.00000000,
"blocks" : 611,
"timeoffset" : 0,
"moneysupply" : 299100.00000000,
"connections" : 2,
"proxy" : "",
"ip" : "",
"difficulty" : {
"proof-of-work" : 154307.03195104,
"proof-of-stake" : 0.00390625
},
"testnet" : false,
"keypoololdest" : 1436258561,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}




[
{
"addr" : "173.23.75.89:43208",
"services" : "00000001",
"lastsend" : 1436263103,
"lastrecv" : 1436263103,
"conntime" : 1436262403,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : false,
"startingheight" : 587,
"banscore" : 0
},
{
"addr" : "188.166.121.151:43208",
"services" : "00000001",
"lastsend" : 1436263103,
"lastrecv" : 1436263103,
"conntime" : 1436262533,
"version" : 60015,
"subver" : "/Pulsar:4.0.0/",
"inbound" : false,
"startingheight" : 587,
"banscore" : 0
}
]

whats the point

Start at block 1 simple

GG for the fail. removed from pool

So it seriously need another Re-Re-launch from this Re-launch.........

wallet sync now ok , at hashgoal.com . test pool is up at     stratum+tcp://hashgoal.com:3349

The nodes are currently at block 642 and the two largest pools are past block 1,000.  It is best that the community decide which fork to follow.  We will support the decision either way.  

If you want to sync to our nodes, please do so - there is currently 30TH mining on that chain.  If you want to sync to the pools or even run your own node for the alternate fork, that is fine.  We will support whatever fork the hash is going to.

There was way more hash in pools, thats the fork I vote for. I think it was at 8-900 TH when we stoped

I was at right fork at launch. What with my coins?

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.

up till 577 you should still have them right? dev said split was there.

On what block fork occured?

It seems to me that split was more earlier.

idk i was going by what dev said

We should press the fork of the pool.

The high difficulty of the pools would have really slowed the small fork so 577 is prob correct, could not have been much sooner

If it forked at 577 I don't see a big problem, because now is only 642, but if it was
at 1 block why I have to loose all my coins although I was on the right fork from the launch?

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

maybe you really should accept supernova chain, a lot of ppl were mining and without pools i don't see how this coin will succeed.. as ocminer already explained:

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.

Ya if we dont get on that fork all coins from pool miners there will be lost, even pre fork  :-\

sh*t now all of my coins are gone

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/ (http://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.

Block range 1501-2000 have 450 PULSE rewards ???

You are retarded and want to develop a coin :) if you don't know the base-blok reward shedule.For sure you coded that shit
For sure you are very goood coder  ;D
EDIT
I see you changed it to the right blok range. Bravo

sounds good dev, any special plans? Roadmap..

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!

thanks for explaining, good luck. i will mine some

Pool all fork. The front of the 600 who dug?

Another pool is up!

https://pulsar.miningpool.cc

Adding to ANN

everything mined up to block 577 i think was on right chain, after block 577 chain splitted.. so u guys only loosed mined coins after block 577.. correct me if i am wrong.

We need DEV to explain. Where did the 600 of the most front go? Or was he himself? If it is a solo apparent imbalance

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.

It is extremely confusing right now because everyone is on different forks.

Hello all,

we are proud to be now a member of the Pulsar Community and created a second pool.

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

Block explorer and richlist set up at http://cryptobe.com/chain/Pulsar.

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!  

Ya this is wrong, ALL coins mined on pools are lost inc pre-fork unless pools can fix. Suprnova already said he isnt  :(

Maybe dev can convince them to fix?

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.

What can i do? Since the fork block, everything is lost and if the coins before the fork where also mined on a separate chain they are of course lost too, i am the last one who wouldn't help but all the dev did was "your fork is wrong, my fork is right" that's about it..  So unless he doesnt accept the pools chain as "the" chain, there is nothing i, or the other pools from the launch can Do

can't u and other pool operator just resync into new chain and coins mined up to block 577 are anyway accepted? split happened after block 577 so not all is lost right?

I will try again but earlier there was no connect possible

thanks oc, idk why we didnt use the pools fork anyway...dev asked community, and everyone said go with pool's and yet he didnt  :-\

going with the fork that had mined like 10 blocks @30TH vs the pools that had mined 500 more blocks at 900TH is beyond me and dont help the coin or community at all..

hey thanks for the pool but whats going on with payments?  ??? didn't receive any for past 2 hours... and you didn't respond to pm.. (okay i got response, waiting...)

We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.

Payouts disabled, you will not receive any coins to your offline wallet for the time being

I've resynched to the new chain:

src/Pulsard getinfo
{
    "version" : "v2.0.0.0-g32a928e",
    "protocolversion" : 60015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 1413,
    "timeoffset" : 0,
    "moneysupply" : 538600.00000000,
    "connections" : 6,
    "proxy" : "",
    "difficulty" : {
        "proof-of-work" : 458609.17120864,
        "proof-of-stake" : 0.00390625
    },
    "testnet" : false,
    "keypoololdest" : 1436258768,
    "keypoolsize" : 101,
    "paytxfee" : 0.00100000,
    "mininput" : 0.00000000,
    "errors" : ""
}


And as expected, EVERY coin is gone since it was a totally different fork from the start.

Since the Dev's nodes where down, the node I connected, pool.mn's node, was the "masternode" and everything was mined upon this chain.. Then at some time the Dev's node came back online and instead of connecting to pool.mn, suprnova or the other pools, he started mining from block zero and the folks which connected there then mined everything new.. So there was no fork at Block 5xx ..

It was like two separate launches next to each other..

I still don't really get why not simply the pool's chain has been used as the dev was waiting for pools and there where three pools on the same chain with lots of hash on it...

Nodes worked for me from the first block and weren't down at anytime and I started mining earlier then pool.mn, so
it looks that for some reason pool.mn started mining from block zero on his own chain. Maybe dev's nodes didn't work
for some regions. I often have wallets with zero connections with new coins when pools are already up.

I was synced entire time with the nodes in post no problem. pool.mn was on its own chain shortly after launch.

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.

https://i.imgur.com/Ub5kqKp.png

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

http://cryptobe.com/chain/Pulsar?hi=675&count=50 (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.

oc is correct it was fork from the start

i dont understand what you all are taking about.. Hashgoal pool is connected to node from last 15 hours and user mining well. what problem you all are facing?

look at here.. http://hashgoal.com/pool/PULS/

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.

ok great, its almost near the initial POS stage... thanks..

  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!).

Why have day off on the launch if you were preparing before launch  ?   And who is WE ? you mention a team ?  no-one codes ?

Its becoming quiet clear now.

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

WTB 10k pulsar will pay 0.065 BTC send PM

instead rent rig  and mine at http://hashgoal.com/pool/PULS/

you can still mine it till POW end...

Hey man do not try to fool us , like ocminer said there was 2 forks right from the beginning , about the nodes , maybe you just limited connection at start so you can mine yourself some coins , here is the address that mined almost 500 blocks http://cryptobe.com/address/PLx9W4VHj94tqKKmmLS4b9sfw95mopNe78  , and you keep telling us that the fork was at block 675 , first you said that was at 577 now is at 675 , if there was a fork at that block where is ocminer coins ???

no I want your coins  ;D

WTB 10k pulsar will pay .075 BTC send PM

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.

any more nodes?

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.

Dont try to hide that you mined like crazy 500 blocks on your "good fork" , why did you choose your fork and not the pools fork ??? there was a big hash on the pools fork but no you have chosen your own fork because you did not wanted to lose your 500 blocks mined .

P.S: Please explain why your nodes was closing our connection , just 2 guys got connected to your nodes but the rest was getting this on debug log

send version message: version 60015, blocks=0, us=xxxxxxxx:43208, them=188.166.121.151:43208, peer=188.166.121.151:43208
ThreadDNSAddressSeed exited
socket closed
disconnecting node 188.166.121.151:43208
trying connection 188.166.121.151:43208 lastseen=371182.9hrs
connected 188.166.121.151:43208
send version message: version 60015, blocks=0, us=xxxxxxxx:43208, them=188.166.121.151:43208, peer=188.166.121.151:43208
socket closed
trying connection 45.55.249.167:43208 lastseen=74.0hrs
connect() failed after select(): Connection refused

P.S : There was not fkc fork at block 643 , when i resynced my wallet to your fork i lost all my coins same for ocminer.

We should use the fork of the pool to be the most fair. Please update your wallet. Using a fork in the pool

It was or not a conspiracy probably you were the only one able to mine the first few hundred blocks and the responsible for this is only you. If nodes were working well this couldn't happen. If you relaunched the coin once you could do it second time seeing that things even got worse, make a 1 day delay and take the time to test everything. Sorry but your open competition distribution failed  and this will affect the future of the coin for sure

Stop lying around about that fork at block, 500, 600 or 550, these are our hashes (probably same like Suprnova):


src/Pulsard getblockhash 10
0000000000192e348dc20459e1f5d78ba6d6ed495ad99d6d8ed38c994d4df1da
src/Pulsard getblockhash 100
000000000002f1b8715b448388cb2614c5c8474c63fe1235915413ecf974e2ad
src/Pulsard getblockhash 200
000000000035733a9fab3f06353fb48de3fbd5f9039f927fc554d11911405493
src/Pulsard getblockhash 300
000000000003b57710479df6a18d8afbedb237a07df78df71d30fb3e2473a277
src/Pulsard getblockhash 400
000000000003be70366891d1d375fe2abbbfe8880c05e1bc975b593a5fbf59e5
src/Pulsard getblockhash 500
00000000002af59ad69aaa9ef06987fe4838b7f4231e9c507d29dccb3770f649
src/Pulsard getblockhash 600
00000000000396a8cb50ea3706316d7453bf2f62d1b833ae2fcc025a72d2498f
src/Pulsard getblockhash 700
0000000000038735cbd79b87a35308d1f168f559de503083d3b202866199cbd0
src/Pulsard getblockhash 800
000000000001084b8c1c622e0a9020c2125a6c8d271fd7ef087f93adc8901c18
src/Pulsard getblockhash 900
00000000000012ba1a4e18c9270b07d340e5d738addac72b7e0d6198d228cc7a
src/Pulsard getblockhash 1000
00000000000002171dac10098152b26e2a5d38d4ff32ecf97fb9ccff3b8a36b3


They are completely different from a new synched wallet.

I can sell you some if dev will use fork from pools ;D

Well dev was open to use pools fork until it became clear that fork did not happen at block 643 so using pools fork dev would loose all his mined coins.
BTW most pools resynced their wallet to devs fork so unless they saved the previous forks blockchain i don't think there is much hope that it can be taken back. I may be wrong though

With the new wallet everything is working fine. You can put your miners back to our pool.
Sorry for all circumstances!!

You could try compiling Linux in a sandbox.

What error you get? Maybe we can help you if you post it here.

thanks for fixing, back to mining. guys u missing easy blocks, may be worth it after all..

@dev can u please check if PoS needs fixing? still didn't get any PoS block..

@bct community

After reading all the post from dev i must say he has been very transparent and helpful from the beginning. Heck he even relaunched the Coin because some solo miners mined all the big rewards. Now before you all start crying and yelling about first 600 blocks instamine (about 300000 coins), you must be aware that after dev made a decision to continue with that chain also mining proceeded and that at very low diff because lack of interest. Continued mining generated far more coins than those first 600 blocks so don't say you didn't had a chance to get a nice chunk of PULS like i did. And at the time of this post pow still proceeding and diff still low and still good chance to get some easy blocks. I hope dev didn't get discouraged and will continue with this project. He has proven to be open to community suggestions and is very transparent, so instead trolling the dev get into mining before PoS starts, still time to catch some.

just my two bits.

Well just think about this, why is this better when dev alone mined all the high reward blocks compared to that when a few solo miners mined them, at least it was in more peoples hands now the dev alone owns about 30% of total POW supply. Would you mine a coin if it is launched with 30% premine? I don't think so...probably you would consider it as a joke. Now that's my two bits ;)

Yes the usual fud about dev getting every block. Since you know no one ever solo mines. I know what your doing man your a senior member so i know you arent that dumb. Its just trolling. Solo miners who synced with nodes from the post were on the right chain the entire time you know.

I know u guys wanna protect your investment but you know this coin is dead. There was 900 TH on pools fork and climbing. Ya he asked community what fork to go with, all said pool but than he decided to go with the 30 TH solo mining fork....obviously because he had more coins on that fork. Bad move losing most support and hash, which in turn lost most of the value of the coin.

Honestly whats 300,000(~1/3 supply) worth when it was mined at less than 30TH SHA256 in 15 min? And with almost all community packed up and gone, its been low hash for the rest of the time too. This coin had good chance but now looks like it wont even make an exchange.

Why you want compile for windows. There is an mega download with the windows executeable. Nothing to compile :)

Well, Oseturacoin or Singular had a weird start too, that one did fine on Bittrex.

I request the developers that if they had mined most of the coins than to make this coin success you have to put some coins in bounties.
First the coin needs a website (Cryptopia exchange asks for coin website for entering into voting list).

Good luck..

its just near POW end, last 146 block are remain .....

just copy and paste all the files in zip into any folder and run pulsar-qt.exe .

POS doesnt work by the way.

Hey DEV wake up!!
POS never happened.
We are still waiting for this:
https://i.imgur.com/cAZC8yi.gif

Hey dev's please fix the  POS.
And if you don't know how to fix it then tell someone who can do that for you(Obviously,.. by giving them the coins you mined from first 500 blocks)..... ??? >:(

Dev is obvious dropping the ball here by not posting. But you're an idiot for still parroting the moronic fud that solo miners do not exist. I got 12 blocks myself solo out of the first 50 before hash went up. I was not the only soloer.

may be you'r an idiot... but Its not about the first 500 blocks , but the point is that POS is not working...

Your the one who mentioned it chief. But your right this coin is deader than disco. Dev ran.