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

[SaltySpitoon]

My question is, with the projected "Band aided" plan, would that effect the implementation of a long term fix? If the only thing the short term fix is going to do, is fix the coin for as long as possible, to buy time for a long term fix, I don't see any problem with that. But, if by implementing the short term fix, it will be more difficult for the long term fix, there is a problem.

Blindfolded, what is your plan for the short term fix?

[TierNolan]

What's the proposed "band-aid" then?

[Blindfolded]

My question is, with the projected "Band aided" plan, would that effect the implementation of a long term fix? If the only thing the short term fix is going to do, is fix the coin for as long as possible, to buy time for a long term fix, I don't see any problem with that. But, if by implementing the short term fix, it will be more difficult for the long term fix, there is a problem.

Blindfolded, what is your plan for the short term fix?

It would consist of a manual re-target, and tweaking the adjustments. Difficulty may spike again the following day for all I know, but I'm willing to do it if there is sufficient pressure to do so. As far as making it more difficult to fix long term, it will probably have no real impact.

[SaltySpitoon]

My question is, with the projected "Band aided" plan, would that effect the implementation of a long term fix? If the only thing the short term fix is going to do, is fix the coin for as long as possible, to buy time for a long term fix, I don't see any problem with that. But, if by implementing the short term fix, it will be more difficult for the long term fix, there is a problem.

Blindfolded, what is your plan for the short term fix?

It would consist of a manual re-target, and tweaking the adjustments. Difficulty may spike again the following day for all I know, but I'm willing to do it if there is sufficient pressure to do so. As far as making it more difficult to fix long term, it will probably have no real impact.

That being said, if there is no harm done to the longrun by the short term fix, I vote for the short term fix to be implemented.

If the difficulty spikes and we are stranded again, we are back in the current situation, but no further back. And that will take some pressure off you to come up with a kick ass long term solution   and allow CRC to be used in Minecraft servers again (since getting deposits in/out is an issue right now)

If anyone sees any issues that could arrise, please voice them. Last thing I want to do is break the leaky pipe with the duct tape.

[Bonz]

ooooooh baby +1 to a short term fix like said before even if it lasts for only one day it would still breath new live into the servers i think me and maybe blindfolded are the only people with much in the way of CRC on spendlightcoins server and it is hard to get ppl interested in it when they can't put any starting capital in it and there are no npc shops!

so i guess that 2 votes for do it

***EDIT***
Just noticed there was a Poll added vote. looks like it's 8-2 for band-aid sofar

My question is, with the projected "Band aided" plan, would that effect the implementation of a long term fix? If the only thing the short term fix is going to do, is fix the coin for as long as possible, to buy time for a long term fix, I don't see any problem with that. But, if by implementing the short term fix, it will be more difficult for the long term fix, there is a problem.

Blindfolded, what is your plan for the short term fix?

It would consist of a manual re-target, and tweaking the adjustments. Difficulty may spike again the following day for all I know, but I'm willing to do it if there is sufficient pressure to do so. As far as making it more difficult to fix long term, it will probably have no real impact.

That being said, if there is no harm done to the longrun by the short term fix, I vote for the short term fix to be implemented.

If the difficulty spikes and we are stranded again, we are back in the current situation, but no further back. And that will take some pressure off you to come up with a kick ass long term solution   and allow CRC to be used in Minecraft servers again (since getting deposits in/out is an issue right now)

If anyone sees any issues that could arrise, please voice them. Last thing I want to do is break the leaky pipe with the duct tape.

[Bonz]

I think we need to have a Pool operator or 2 Chime in on this as both the Diff Stick and the Band-aid REALLY affect them

[Blindfolded]

Band-aid it is then. I will prepare it and push it out. Expect it by the end of the weekend.

[MaGNeT]

Band-aid it is then. I will prepare it and push it out. Expect it by the end of the weekend.

Great! I'll throw a frew hashes at it to get it to the diff change, so update the topic when it's pushed out.
Also make sure it disconnects old clients, so we don't get the forks like Philosopherstone and Noirbits had when it got hardforked

[Blindfolded]

Also make sure it disconnects old clients, so we don't get the forks like Philosopherstone and Noirbits had when it got hardforked

Anybody know where to do this? I cannot seem to find it. 

[TierNolan]

Anybody know where to do this? I cannot seem to find it. 

Do you have the alert keys?

Inherently, the old clients can form a network on their own.  If you force them to be disconnected, you aren't preventing them doing that, just forcing the 2 networks apart.

Do you have control over all hard-coded seed nodes?

You could set them up so that they don't forward addresses for old clients.

[Blindfolded]

Git Updated: https://github.com/craftcoin

Windows Build: http://spendlitecoins.com/downloads/craftcoin_1.1.2.zip



Best Of Luck, And Enjoy.



NOTE: The link on the "downloads" page on the craftcoin.net website DOES NOT LINK TO THE CURRENT BUILD. You must use the above link to download the latest version.

[Carra23]

Git Updated: https://github.com/craftcoin

Windows Build: http://spendlitecoins.com/downloads/craftcoin_1.1.2.zip



Best Of Luck, And Enjoy.



NOTE: The link on the "downloads" page on the craftcoin.net website DOES NOT LINK TO THE CURRENT BUILD. You must use the above link to download the latest version.

What is the change in this? How is the difficulty problem being handled?

[Blindfolded]

Git Updated: https://github.com/craftcoin

Windows Build: http://spendlitecoins.com/downloads/craftcoin_1.1.2.zip



Best Of Luck, And Enjoy.



NOTE: The link on the "downloads" page on the craftcoin.net website DOES NOT LINK TO THE CURRENT BUILD. You must use the above link to download the latest version.

What is the change in this? How is the difficulty problem being handled?

This is nothing more than a band-aid fix.

Changes are as follows:
Difficulty will re-calculate every block
max adjustment will be 200%

This patch does absolutely nothing to correct the inherent problem, it will only (possibly) get the coin moving again until it gets slammed with hashrate.

[dreamwatcher]

CryptoCoin Explorer has been updated.

[Blindfolded]

CryptoCoin Explorer has been updated.

Thank-you

[Carra23]

Not syncing even with 4 connections.

Any good nodes?

[Blindfolded]

Not syncing even with 4 connections.

Any good nodes?

65.167.153.115


65.167.153.125

you can also add cryptocoinexplorer since it has confirmed as updated.

[TierNolan]

Git Updated: https://github.com/craftcoin

There doesn't seem to be switch-over code?

From the github link, the new parameters are:

nTargetTimespan: 1 hour
nTargetSpacing: 5 minutes

This suggests a 12 block re-target time, rather than 1 block?

You also use 6 re-targeting periods to work out the new difficulty, so averaged over 6 hours.

I renamed my craftcoin directory to backup and started the client.  It downloads the first 11 blocks and then stalls.

I assume what is happening is that the 12th block (first retarget) has the wrong difficulty, according to the new rules.

You need to have the old difficulty rules up to block 9331 and then switch to the new rules.

An easier option would be to just have a checkpoint at 9331 and skip verification of the difficulty updates until then.

[Carra23]

Git Updated: https://github.com/craftcoin

There doesn't seem to be switch-over code?

From the github link, the new parameters are:

nTargetTimespan: 1 hour
nTargetSpacing: 5 minutes

This suggests a 12 block re-target time, rather than 1 block?

You also use 6 re-targeting periods to work out the new difficulty, so averaged over 6 hours.

I renamed my craftcoin directory to backup and started the client.  It downloads the first 11 blocks and then stalls.

I assume what is happening is that the 12th block (first retarget) has the wrong difficulty.

You need to have the old difficulty rules up to block 9331 and then switch to the new rules.

Same problem here.

[Blindfolded]

Git Updated: https://github.com/craftcoin

There doesn't seem to be switch-over code?

From the github link, the new parameters are:

nTargetTimespan: 1 hour
nTargetSpacing: 5 minutes

This suggests a 12 block re-target time, rather than 1 block?

You also use 6 re-targeting periods to work out the new difficulty, so averaged over 6 hours.

I renamed my craftcoin directory to backup and started the client.  It downloads the first 11 blocks and then stalls.

I assume what is happening is that the 12th block (first retarget) has the wrong difficulty, according to the new rules.

You need to have the old difficulty rules up to block 9331 and then switch to the new rules.

An easier option would be to just have a checkpoint at 9331 and skip verification of the difficulty updates until then.

...indeed
totally my fault, i'm on it.