[ANN] Pulsar | Transcendent Concepts | Open Competition Distribution

[tinybenis]

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

no I want your coins 

WTB 10k pulsar will pay .075 BTC send PM

[Pulsardev70]

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.

[UltrA1]

any more nodes?

[Pulsardev70]

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.

[scorpio18]

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.

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.

[jambo110]

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.

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.

[superman1314]

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 should use the fork of the pool to be the most fair. Please update your wallet. Using a fork in the pool

[badam]

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.

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

[poolmn]

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.

[totoy]

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

no I want your coins  

WTB 10k pulsar will pay .075 BTC send PM

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

[badam]

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 should use the fork of the pool to be the most fair. Please update your wallet. Using a fork in the pool

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

[lahlor]

Hello all,

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

Welcome to miningpool.cc
Change the Pool to mine different coins over the top left dropdown.Our pools mainpage www.miningpool.cc

Pulsar Pool // Algo: SHA256

stratum+tcp://pulsar.mininigpool.cc:9478

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

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

[samspaces]

How to compile  wallet on windows source is brore its not compile with mingw 

You could try compiling Linux in a sandbox.

[lahlor]

How to compile  wallet on windows source is brore its not compile with mingw 

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

[trader19]

Hello all,

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

Welcome to miningpool.cc
Change the Pool to mine different coins over the top left dropdown.Our pools mainpage www.miningpool.cc

Pulsar Pool // Algo: SHA256

stratum+tcp://pulsar.mininigpool.cc:9478

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

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

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

[trader19]

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

[trader19]

@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.

[badam]

@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

[Paycoinzzz]

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.

[SIX3P0]

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.