Another pool is up!
https://pulsar.miningpool.cc
Adding to ANN
Topic: [ANN] Pulsar | Transcendent Concepts | Open Competition Distribution - page 4. (Read 5343 times)
July 07, 2015, 01:25:51 PM
July 07, 2015, 01:24:08 PM
Pool all fork. The front of the 600 who dug?
July 07, 2015, 01:23:43 PM
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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
sounds good dev, any special plans? Roadmap..
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! July 07, 2015, 12:40:40 PM
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-2000 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 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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
You are retarded and want to develop a coin
if you don't know the base-blok reward shedule.For sure you code that shitFor sure you are very goood coder
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
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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
sounds good dev, any special plans? Roadmap..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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
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! July 07, 2015, 12:18:17 PM
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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
sounds good dev, any special plans? Roadmap.. 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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
July 07, 2015, 12:15:13 PM
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-2000 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 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-2000 have 450 PULSE rewards, so there is still ample opportunity to get in with rewards comparable to the initial blocks.
You are retarded and want to develop a coin
if you don't know the base-blok reward shedule.For sure you coded that shitFor sure you are very goood coder
EDIT
I see you changed it to the right blok range. Bravo
July 07, 2015, 11:58:43 AM
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.
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.
July 07, 2015, 07:53:34 AM
sh*t now all of my coins are gone
July 07, 2015, 06:19:12 AM
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:
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...
Ya if we dont get on that fork all coins from pool miners there will be lost, even pre fork 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...
July 07, 2015, 06:11:43 AM
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.
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.
Pool.mn, please resync with us.
We can get this fork resolved, it happened at block 577.
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...
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.
July 07, 2015, 06:06:21 AM
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.
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.
Pool.mn, please resync with us.
We can get this fork resolved, it happened at block 577.
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...
July 07, 2015, 05:53:39 AM
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.
July 07, 2015, 05:50:06 AM
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?
July 07, 2015, 05:46:40 AM
The high difficulty of the pools would have really slowed the small fork so 577 is prob correct, could not have been much sooner
July 07, 2015, 05:44:35 AM
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.
We should press the fork of the pool. 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.
July 07, 2015, 05:41:11 AM
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.
Pool.mn, please resync with us.
We can get this fork resolved, it happened at block 577.
idk i was going by what dev said
July 07, 2015, 05:37:38 AM
up till 577 you should still have them right? dev said split was there.
It seems to me that split was more earlier.
July 07, 2015, 05:34:08 AM
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.
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.
On what block fork occured?
July 07, 2015, 05:33:11 AM
up till 577 you should still have them right? dev said split was there.
July 07, 2015, 05:32:54 AM
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.
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.
Jump to: