[ANN] Announcing Galaxycoin - GLX, the new PoW/PoS coin, no premine!

[iGotSpots]

If you restart it, the coin is dead

[HuuHachu]

If you restart it, the coin is dead

possible ... but could also just be a saying from someone owning some blocks already ^^

For the retarget, a weighted average would probably be better than the current one ...

Also for the pre-launch test, the oscillation should have been visible anyway ... Values would not have been that high, but relative amplitude must have been identical.

[iGotSpots]

If you restart it, the coin is dead

possible ... but could also just be a saying from someone owning some blocks already ^^

For the retarget, a weighted average would probably be better than the current one ...

Also for the pre-launch test, the oscillation should have been visible anyway ... Values would not have been that high, but relative amplitude must have been identical.

I have gotten like 2 total so far. I'm just saying, from all the last coins that restarted, you may as well just not start it again and let it die

[HuuHachu]

If you restart it, the coin is dead

possible ... but could also just be a saying from someone owning some blocks already ^^

For the retarget, a weighted average would probably be better than the current one ...

Also for the pre-launch test, the oscillation should have been visible anyway ... Values would not have been that high, but relative amplitude must have been identical.

I have gotten like 2 total so far. I'm just saying, from all the last coins that restarted, you may as well just not start it again and let it die

well, in the current case, screwed re-target algorithm did not cause unreasonably high mining ... a hard-fork is possible and indeed recommended over a restart.
Unstable block duration such as now is not a problem from a mining point of view (over a long period, the average is correct)... When people start making transactions, it will really become a problem for the confirmation time.

[arlington]

Sorry guys, this looks like a failed trial.

I think we have two options:

1. Hard-fork at say, block 800. I can revert back to PP-coin/Novacoin retarget algorithm (still each block).
2. Do nothing and let it die. In which case I'll lock this thread.

Let me know which you prefer.

[TheSpiral]

Sorry guys, this looks like a failed trial.

I think we have two options:

1. Hard-fork at say, block 800. I can revert back to PP-coin/Novacoin retarget algorithm (still each block).
2. Do nothing and let it die. In which case I'll lock this thread.

Let me know which you prefer.

1 Sounds find. The retarget every block seems okay in theory, just not the massive difficulty swing it's currently getting (i.e. double/half per block). Just leads to nothing being mined for a while.... then suddenly block block block block block, back to nothing...

 Fixable though. Go for it

[stevenlam]

Sorry guys, this looks like a failed trial.

I think we have two options:

1. Hard-fork at say, block 800. I can revert back to PP-coin/Novacoin retarget algorithm (still each block).
2. Do nothing and let it die. In which case I'll lock this thread.

Let me know which you prefer.

I choose 1

[HuuHachu]

Yes, hard-fork is the way to go ...

Be careful to not put something that enable insta-mining ... if the diff variation is strongly limited from one block to the next and the hard-fork happens at a low diff, it will take a large number of blocks to stabilize to the correct value (causing insta-mining as we have seen with many alts)


At least the launch was fair in its own way ^^

(per-announce would have been better though)

[arlington]

OK, so hard-fork at block 750, I put back the ppcoin algorithm for diff adjusting:

   if(pindexLast->nHeight < 750)
   {
      int blockstogoback = nTargetInterval;

      const CBlockIndex* pindexFirst = pindexLast;
      for (int i = 0; pindexFirst && i < blockstogoback; i++)
         pindexFirst = pindexFirst->pprev;
      assert(pindexFirst);

      // Limit adjustment step, this should be enough since it is continuous adjustment, max twice or half
      int64 nActualTimespan = pindexLast->GetBlockTime() - pindexFirst->GetBlockTime();
      printf("  nActualTimespan = %"PRI64d"  before bounds\n", nActualTimespan);

      if (nActualTimespan < nTargetTimespan/2)
         nActualTimespan = nTargetTimespan/2;
      if (nActualTimespan > nTargetTimespan*2)
         nActualTimespan = nTargetTimespan*2;

      // Retarget
      bnNew.SetCompact(pindexLast->nBits);
      bnNew *= nActualTimespan;
      bnNew /= nTargetTimespan;

      /// debug print
      // printf("GetNextWorkRequired RETARGET\n");
      printf("nHeight = %d, nTargetTimespan = %"PRI64d", nActualTimespan = %"PRI64d"\n", pindexLast->nHeight, nTargetTimespan, nActualTimespan);
      // printf("Before: %08x  %s\n", pindexLast->nBits, CBigNum().SetCompact(pindexLast->nBits).getuint256().ToString().c_str());
      // printf("After:  %08x  %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString().c_str());
   }
   else   // ppcoin algo
   {
      const CBlockIndex* pindexPrev = GetLastBlockIndex(pindexLast, fProofOfStake);
      const CBlockIndex* pindexPrevPrev = GetLastBlockIndex(pindexPrev->pprev, fProofOfStake);
      int64 nActualSpacing = pindexPrev->GetBlockTime() - pindexPrevPrev->GetBlockTime();

      bnNew.SetCompact(pindexPrev->nBits);
      int64 nTargetSpacing0 = fProofOfStake? nTargetSpacing : min(nTargetSpacingWorkMax, (int64) nTargetSpacing * (1 + pindexLast->nHeight - pindexPrev->nHeight));
      int64 nInterval = nTargetTimespan / nTargetSpacing0;
      bnNew *= ((nInterval - 1) * nTargetSpacing0 + nActualSpacing + nActualSpacing);
      bnNew /= ((nInterval + 1) * nTargetSpacing0);
   }

the ppcoin algo is used in several others, like bottlecaps and cosmoscoin, so it should have no problem. Again sorry guys for the roller-coaster mining, it was not intended  

[arlington]

version 1.1 released. Download links updated in OP. After block 750, it will revert back to ppcoin's diff retarget algorithm (still adjust each block). Hopefully this will fix the diff oscillation issue.

This is a hard-fork, please update the client before block 750.


does not work

[liteuser]

version 1.1 released. Download links updated in OP. After block 750, it will revert back to ppcoin's diff retarget algorithm (still adjust each block). Hopefully this will fix the diff oscillation issue.

github?

Edit: thanks!

[arlington]

.

[arlington]

version 1.1 released. Download links updated in OP. After block 750, it will revert back to ppcoin's diff retarget algorithm (still adjust each block). Hopefully this will fix the diff oscillation issue.

github source has not been updated ...

updated

[TheSpiral]

Quick updates are very nice.
At block 742, we'll see how this goes past 750.
And... Client crash  at 750 :/

[liteuser]

linux client just core dumped. Cannot restart it ...

[arlington]

linux client just core dumped. Cannot restart it ...

looks like most people did not fork....

old client still work, at block 761 now.

Can always go with old client, sucks

Old client:
https://docs.google.com/file/d/0B-_cT_EUbb3oLWxqY1R3SlFnM1U/edit?usp=sharing

[arlington]

Oh well, anyway guys have fun for the roller coaster...

[MaGNeT]

This is as succesful as QuantumCoin 

[Vlad2Vlad]

reserve

Do you guys have galaxyCoin.com locked in?  Just curious cause I tried to go to the website and there isn't one. 

[Online24o0n]

Ok, ha ha, another joke coin, Why cant we start getting these posts deleted, just spam....   Nice logo, took me about .5 seconds to find that on google images.