[ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin

[SaltySpitoon]

I would highly advise against downloading the new client for this moment. Justin, I'm glad you are helping, but I think it would be a good idea if before releasing the client, you allow Blindfolded to check it over. If nothing else, to just double check to make sure there aren't any mistakes and that your solution will truely help the situation in the more than immediate future.

[1715357423]

1715357423

[1715357423]

1715357423

[1715357423]

1715357423

[1715357423]

1715357423

[1715357423]

1715357423

[justin7674]

Alright I will go ahead and get the next block mined and tell you if it readjusts!
Russ should approve it in a few hours.
I do have prior experience in working on coins. So, I am sure this will help in the future as long as immediately. However, we need atleast 1 more person on the network to help me do the test.

[justin7674]

I don't believe Magnet was correct he just removed his post. We will see what he says.

[MaGNeT]

Alright I will go ahead and get the next block mined and tell you if it readjusts!
Russ should approve it in a few hours.
I do have prior experience in working on coins. So, I am sure this will help in the future as long as immediately. However, we need atleast 1 more person on the network to help me do the test.

Well, the new upload is still the old file.
Did a MD5 compare, both files give same hash.

Sometimes Quality needs to come before Speed.

Edit, think it was my browser cache? Did an CTRL+5 and now I got a file with another MD5 hash.
So I think this time he got it right  

I don't believe Magnet was correct he just removed his post. We will see what he says.

Problem was on my side, don't understand what happened but second time I downloaded it, it was different.

Old client hash: 69084E87510442FCD13C92B7ABB9243D
New client hash: A33C67AF3780E585A97043079A3E33B5

[CartmanSPC]

I would highly advise against downloading the new client for this moment. Justin, I'm glad you are helping, but I think it would be a good idea if before releasing the client, you allow Blindfolded to check it over. If nothing else, to just double check to make sure there aren't any mistakes and that your solution will truely help the situation in the more than immediate future.

Thanks for this statement!

+1

[CartmanSPC]

Here are the changes made in the code. If the difficulty adjustment is changed I think we can do something better than this but am not volunteering  

justin7674, consider paying more attention to the comments detail. There are two spots where you did not update the comments with the correct values.

Original

Code:

static const int64 nTargetTimespan = 1 * 24 * 60 * 60; // CraftCoin: 1 days

justin7674

Code:

static const int64 nTargetTimespan = 3 * 60 * 60; // CraftCoin: 3 hrs

Original

Code:

static const int64 nReTargetHistoryFact = 4; // look at 4 times the retarget
                                             // interval into the block history

justin7674 (need to fix the comments to say "look at 6 times the retarget")

Code:

static const int64 nReTargetHistoryFact = 6; // look at 4 times the retarget
                                             // interval into the block history

Original

Code:

        // Maximum 400% adjustment...
        bnResult *= 4;
        // ... in best-case exactly 4-times-normal target time

justin7674 (need to change "400%" comment to "200%")

Code:

        // Maximum 400% adjustment...
        bnResult *= 2;
        // ... in best-case exactly 2-times-normal target time

[justin7674]

Sorry, I will have that corrected tonight.

[coinerd]

I would highly advise against downloading the new client for this moment. Justin, I'm glad you are helping, but I think it would be a good idea if before releasing the client, you allow Blindfolded to check it over. If nothing else, to just double check to make sure there aren't any mistakes and that your solution will truely help the situation in the more than immediate future.

+1 for that.

As soon as I can pull this from the official craftcoin repository I'll be happy to move forward with it.

[Bonz]

wait does all this mean i should point my miners back @crc.scryptmining again?

[justin7674]

It would be best if you point your miner at : http://198.50.233.9:8830/static/

[MaGNeT]

The diff doesn't seem to be changing. What's holding it?

[TierNolan]

The diff doesn't seem to be changing. What's holding it?

The update changes the diff calculations.  It updates faster than before.  However, there is still a need to actually find the next few blocks at (relatively) high diff.

There still hasn't been an official confirm, just that the change will be looked at.

[Bonz]

It would be best if you point your miner at : http://198.50.233.9:8830/static/

naw i'd rather stick with scryptmining i can't stand p2pools

[justin7674]

The diff doesn't seem to be changing. What's holding it?

The update changes the diff calculations.  It updates faster than before.  However, there is still a need to actually find the next few blocks at (relatively) high diff.

There still hasn't been an official confirm, just that the change will be looked at.

+1 should be about 10 more blocks and it readjusts. After this it will readjust every 36 blocks. We repaired the max mint every day because the previous wasn't matching the amount of blocks generated every day.

[Bonz]

so what your saying is it's time to put my 2 mhash to it?  how long do you think 10 blocks would take at 16mhash (network speed once i join)

The diff doesn't seem to be changing. What's holding it?

The update changes the diff calculations.  It updates faster than before.  However, there is still a need to actually find the next few blocks at (relatively) high diff.

There still hasn't been an official confirm, just that the change will be looked at.

+1 should be about 10 more blocks and it readjusts. After this it will readjust every 36 blocks. We repaired the max mint every day because the previous wasn't matching the amount of blocks generated every day.

[PoolMinor]

Until these 2 sites get updated with the "new" wallet I will not be doing any downloading of the files.

https://github.com/craftcoin/craftcoin

http://craftcoin.net/download.html

[SaltySpitoon]

Speaking as a CRC user, the thing that concerns me most here, is not Justin's ability or intentions, its that if for whatever reason Blindfolded disapproves of the change, and the forked chain has already gone ahead and made any significant amount of traction, it will be a massive pain trying to fix the fix. It will be node hell, upon the return to the original, the client will be looking for the best height and difficulty, and will not know to ban the existing nodes created by the fork, causing all sorts of syncing errors and issues.

[nearmiss]

http://crc.scryptmining.com will update whenever official github is updated.


Watching this thread.

[Bonz]

Me 2... Intently!!! i have placed my backup rig on your pool in case i miss the time you update! when you do i will also place my larger rig on crc.scryptmining

http://crc.scryptmining.com will update whenever official github is updated.


Watching this thread.

[efx]

Someone hardforked craftcoin and went back 50 blocks to reset difficulty.
I had to delete my blockchain for this to take effect.

addnode=199.180.115.100

+

To be honest. Blindfolded fucked the network. He literally ditched it. I am the developer for the java plugin and he has just up and left. HE IS GONE THIS COIN IS DEAD AND DOESNT DESERVE ITS SLOT ON CRYPTSY

I am removing the java plugin and making it compatible for bottlecaps. Everyone move on from this thread.

+

There is no risk in testing the client from another computer. But, your loss. There is a pool that has reviewed the code and is agreeing to post a new pool to set the chain in place and unfreeze it. Nobody's transactions or money will be lost!

It's pretty (very) obvious that you do not really know what's going on. Essentially anyone on this forum could have implemented your 'fix', it's a temporary measure at best and needlessly introduces potential risks. Releasing the client and attempting to gain hashrate without approval is definitely on the edge of malicious.



"Your loss." Hm right, because those who do not decide to join your little fork would be left with devalued coins. Nice.

Forgive me if I do not find your references very impressive, especially after your baseless little outburst.


Anyways, as SaltySpitoon already mentioned,  nodes with a seemingly better height are going to be seen by the client and they will not be rejected immediately. The lack of node consensus is  not going to help anything, as such an insignificant edit means this will not be the last crc fork and the needless division of non-malicious network hashrate is entirely counter-productive. 

I say that you should all wait for a *real* fix, not a simple reduction in adjustment period.  Empirical evidence has already shown such a simplistic change is not a long-term solution to the problem of highly variable hashrate and introduces new potential risks.

Anyways, I hopefully didn't need to point any of the above out and you are all aware of what highly irregular coin generation can do to small economies.