Need a definitive update

[Majormax]

As a further point to understand:

Each strength/weakness and variable of a coin takes on changing significance at different stages in its life.

Robustness, flexibility and technical resistance to attack are uppermost in the formative stages (first 6 months)

[MicroGuy]

The power is also in the hands of the community.

It we have to do the rewrite and make v2.0, we're going to need the vast majority of the community's support. And we're going to need an exchange program to allow a fair reissue of the new coin to current 1.0 coin holders. This is going to take a lot of trust and planning.

[bitshirehashaway]

I also very much like the GLD designation. It has nothing to do with the type of hash or the block reward, it's simply the name I like. This is how consumers look at things, not from the underlying technology. If that was the case, no one would use Windows. But they like that name and they will like this name.

The only problem with the name is that it matches the symbol of the SPDR Gold Trust ETF which is GLD. Which may get a bad rep when people find out that they hold less gold than they sell shares for. In case of a gold run lots of investors will be holding the bag. And that might sour many people on the name GLD.

http://www.spdrgoldshares.com

I'm not sure I understand what you are saying, but I am pretty sure, this should be ok.

[Majormax]

Dreamwatcher posted this on the 'other' forum [LINK REMOVED]

"Although this will help in the short run, I believe you must look into a more permanent solution down the road.

I would recommend you take the time these changes give you and look closely at implementing a PPC style difficulty algo.

The PPC style algo is pretty resilient to these types of difficulty swings and attacks.

If you need help, Sunny has helped others in the past. I have worked with him on issues surrounding PPC since it came online and he has always been helpful.

Just my 2cents that I would recommend to any coin developer who has long term plans for there coin. (Yes I  know, I should be taking my own advice and implement into JKC also..I just do not know where the time goes  )"

Might be worth a thought.

[MicroGuy]

Dreamwatcher posted this on the 'other' forum [LINK REMOVED]

"Although this will help in the short run, I believe you must look into a more permanent solution down the road.

I would recommend you take the time these changes give you and look closely at implementing a PPC style difficulty algo.

The PPC style algo is pretty resilient to these types of difficulty swings and attacks.

If you need help, Sunny has helped others in the past. I have worked with him on issues surrounding PPC since it came online and he has always been helpful.

Just my 2cents that I would recommend to any coin developer who has long term plans for there coin. (Yes I  know, I should be taking my own advice and implement into JKC also..I just do not know where the time goes  )"

Might be worth a thought.

I'm beginning to lean toward a complete rewrite also. But before we work out the details of this new Goldcoin 2.0, I think we need to devise a plan to fully protect those holding the current coin. Otherwise, the PR fallout might prove difficult to overcome.

[dreamwatcher]

Dreamwatcher posted this on the 'other' forum [LINK REMOVED]

"Although this will help in the short run, I believe you must look into a more permanent solution down the road.

I would recommend you take the time these changes give you and look closely at implementing a PPC style difficulty algo.

The PPC style algo is pretty resilient to these types of difficulty swings and attacks.

If you need help, Sunny has helped others in the past. I have worked with him on issues surrounding PPC since it came online and he has always been helpful.

Just my 2cents that I would recommend to any coin developer who has long term plans for there coin. (Yes I  know, I should be taking my own advice and implement into JKC also..I just do not know where the time goes  )"

Might be worth a thought.

I'm beginning to lean toward a complete rewrite also. But before we work out the details of this new Goldcoin 2.0, I think we need to devise a plan to fully protect those holding the current coin. Otherwise, the PR fallout might prove difficult to overcome.

There is very little you cannot do with a hard fork. You can change just about anything in the chain, client/daemon, while continuing the current block chain. Nobody loses anything, because the chain before the fork is still a part of the valid chain.
The main issue with a hard fork is mining as any coin-base transaction after the fork without the updated client/daemon would be on an orphan chain or unofficial chain. Any transactions on this chain would not be reflected in the main fork, so existing coins would not be lost.


What kind of changes do you think would be a problem in a hard fork?

[MicroGuy]

Dreamwatcher posted this on the 'other' forum [LINK REMOVED]

"Although this will help in the short run, I believe you must look into a more permanent solution down the road.

I would recommend you take the time these changes give you and look closely at implementing a PPC style difficulty algo.

The PPC style algo is pretty resilient to these types of difficulty swings and attacks.

If you need help, Sunny has helped others in the past. I have worked with him on issues surrounding PPC since it came online and he has always been helpful.

Just my 2cents that I would recommend to any coin developer who has long term plans for there coin. (Yes I  know, I should be taking my own advice and implement into JKC also..I just do not know where the time goes  )"

Might be worth a thought.

I'm beginning to lean toward a complete rewrite also. But before we work out the details of this new Goldcoin 2.0, I think we need to devise a plan to fully protect those holding the current coin. Otherwise, the PR fallout might prove difficult to overcome.

There is very little you cannot do with a hard fork. You can change just about anything in the chain, client/daemon, while continuing the current block chain. Nobody loses anything, because the chain before the fork is still a part of the valid chain.
The main issue with a hard fork is mining as any coin-base transaction after the fork without the updated client/daemon would be on an orphan chain or unofficial chain. Any transactions on this chain would not be reflected in the main fork, so existing coins would not be lost.


What kind of changes do you think would be a problem in a hard fork?

My concerns are with the lack of communication from the developer.

He does not appear to be mining the coin any longer or effectively communicating. Also, I was informed that we need to know if the litecoin base keys were used in his code. If they were, my understanding is that that could cause problems down the road even if we get past these forks.

Transparency and communication will be essential if we are to solve these critical issues.

[MicroGuy]

I have been in touch with a developer who will posting his ideas in this forum a little later tonight. He has indicated to me that he is in direct contact with the current developer "gldcoin" and has access to the source code.  My thinking was we should make this the official forum and use some type of voting system or elected committee to decide how to proceed when major decisions need to be made.

[hyoshi]

All, I am the dev of "Nibble" - my coin has been near the top of coinchoose.com on and off for the last few weeks.  I can do whatever you want really with this coin.  Some ideas I have are to change the fork to 20,950 - its currently set to fork at 21k.  you guys will have to spread the word of the update, get cryptsy to install it and all that.

I would change the block time to 1 minute, make the difficulty retarget something like 250 blocks, make the max difficulty adjustment around 110% (makes attacks or spikes less effective or impacting), and change the coin maturity to 50 confirms - the current 100 for a coin with so few miners is insane.  I would keep the block reward at 500 but have it 1/2 every x amount of blocks (way out in the future)

These are not things the dev did wrong - its just that no coin is ever intended to be mined with under 10 mH/s total.

I can make these changes immediately and have a build for you tonight - I have dealt with gldcoin (we swapped nodes to improve both networks) and he told me that he will let me take over his dev duties.  He said that he just has no time at the moment, he's swamped at work, swamped at home or something.

[MicroGuy]

All, I am the dev of "Nibble" - my coin has been near the top of coinchoose.com on and off for the last few weeks.  I can do whatever you want really with this coin.  Some ideas I have are to change the fork to 20,950 - its currently set to fork at 21k.  you guys will have to spread the word of the update, get cryptsy to install it and all that.

I would change the block time to 1 minute, make the difficulty retarget something like 250 blocks, make the max difficulty adjustment around 110% (makes attacks or spikes less effective or impacting), and change the coin maturity to 50 confirms - the current 100 for a coin with so few miners is insane.  I would keep the block reward at 500 but have it 1/2 every x amount of blocks (way out in the future)

These are not things the dev did wrong - its just that no coin is ever intended to be mined with under 10 mH/s total.

I can make these changes immediately and have a build for you tonight - I have dealt with gldcoin (we swapped nodes to improve both networks) and he told me that he will let me take over his dev duties.  He said that he just has no time at the moment, he's swamped at work, swamped at home or something.

Thank you Hyoshi!

I was just thinking about you (and Nibble) today and how perhaps you might be willing to help us.

It sounds like you have some great ideas and hopefully we can now begin making some headway with Goldcoin. My understanding is that we need to know if the litecoin base keys were used in the code and discuss what impact that might have moving forward. I guess you could examine the source code and let us all know.

Also, I am consulting with another miner/developer who might like to provide his input into code changes. Maybe I can get him to chime in tomorrow here in this thread. If we have two people that understand the code, and one becomes missing in action, then community won't be put in another awkward situation like we're in now.

I suggest we all discuss this over the next day or two and get ample input from the community. Then a little later in the week, if everyone agrees we can begin the updates.

[dreamwatcher]

The keys could be an issue, but it depends what "keys": we are talking about.

IF we are talking about the Block Header "Magic numbers" or the P2P "Magic numbers" (In reality they should be the same, but I have seen some variance with the coins lately) ,  those can be changed in a hard fork relatively pain free. In the programming of the explorers, I use those numbers, and on most of the new coins I can tell exactly which of the older coins the source was forked off. It seems most of the new developers today are unaware they need to change those.   

If we are talking about colbees' key for the broadcast message system , that could changed in a hard or soft fork. I cannot recall anybody ever using the system to date (I could be wrong), but it is such a little know about/used system that I do not think changing the key would require a hard fork.

Anyway, all this is just my ramblings, and I could be wrong 

[MicroGuy]

I'm excited! We're finally making some progress.

Right now I need to get some sleep. I've been working non-stop for a while and just need a little rest. See you guys tomorrow and I just know we're going to make this work.

You guys are the best! 

[hyoshi]

All, I am the dev of "Nibble" - my coin has been near the top of coinchoose.com on and off for the last few weeks.  I can do whatever you want really with this coin.  Some ideas I have are to change the fork to 20,950 - its currently set to fork at 21k.  you guys will have to spread the word of the update, get cryptsy to install it and all that.

I would change the block time to 1 minute, make the difficulty retarget something like 250 blocks, make the max difficulty adjustment around 110% (makes attacks or spikes less effective or impacting), and change the coin maturity to 50 confirms - the current 100 for a coin with so few miners is insane.  I would keep the block reward at 500 but have it 1/2 every x amount of blocks (way out in the future)

These are not things the dev did wrong - its just that no coin is ever intended to be mined with under 10 mH/s total.

I can make these changes immediately and have a build for you tonight - I have dealt with gldcoin (we swapped nodes to improve both networks) and he told me that he will let me take over his dev duties.  He said that he just has no time at the moment, he's swamped at work, swamped at home or something.

Thank you Hyoshi!

I was just thinking about you (and Nibble) today and how perhaps you might be willing to help us.

It sounds like you have some great ideas and hopefully we can now begin making some headway with Goldcoin. My understanding is that we need to know if the litecoin base keys were used in the code and discuss what impact that might have moving forward. I guess you could examine the source code and let us all know.

Also, I am consulting with another miner/developer who might like to provide his input into code changes. Maybe I can get him to chime in tomorrow here in this thread. If we have two people that understand the code, and one becomes missing in action, then community won't be put in another awkward situation like we're in now.

I suggest we all discuss this over the next day or two and get ample input from the community. Then a little later in the week, if everyone agrees we can begin the updates.

Here is your dilemma. There is a hard fork in place at 21K which is 89 more blocks - you likely don't have a week. 

You don't need to change the public key for any reason other than the broadcast system at this point, and the magic number prefix codes don't really need to be changed either.  Those things are not critical - but likely should be changed down the road.

There is nothing to say that after this fork takes place though you can't fork again in a few weeks with a faster block time, etc.

[MicroGuy]

All, I am the dev of "Nibble" - my coin has been near the top of coinchoose.com on and off for the last few weeks.  I can do whatever you want really with this coin.  Some ideas I have are to change the fork to 20,950 - its currently set to fork at 21k.  you guys will have to spread the word of the update, get cryptsy to install it and all that.

I would change the block time to 1 minute, make the difficulty retarget something like 250 blocks, make the max difficulty adjustment around 110% (makes attacks or spikes less effective or impacting), and change the coin maturity to 50 confirms - the current 100 for a coin with so few miners is insane.  I would keep the block reward at 500 but have it 1/2 every x amount of blocks (way out in the future)

These are not things the dev did wrong - its just that no coin is ever intended to be mined with under 10 mH/s total.

I can make these changes immediately and have a build for you tonight - I have dealt with gldcoin (we swapped nodes to improve both networks) and he told me that he will let me take over his dev duties.  He said that he just has no time at the moment, he's swamped at work, swamped at home or something.

Thank you Hyoshi!

I was just thinking about you (and Nibble) today and how perhaps you might be willing to help us.

It sounds like you have some great ideas and hopefully we can now begin making some headway with Goldcoin. My understanding is that we need to know if the litecoin base keys were used in the code and discuss what impact that might have moving forward. I guess you could examine the source code and let us all know.

Also, I am consulting with another miner/developer who might like to provide his input into code changes. Maybe I can get him to chime in tomorrow here in this thread. If we have two people that understand the code, and one becomes missing in action, then community won't be put in another awkward situation like we're in now.

I suggest we all discuss this over the next day or two and get ample input from the community. Then a little later in the week, if everyone agrees we can begin the updates.

Here is your dilemma. There is a hard fork in place at 21K which is 89 more blocks - you likely don't have a week. 

You don't need to change the public key for any reason other than the broadcast system at this point, and the magic number prefix codes don't really need to be changed either.  Those things are not critical - but likely should be changed down the road.

There is nothing to say that after this fork takes place though you can't fork again in a few weeks with a faster block time, etc.

Okay.

I think I understand. So then let's try to make a decision tomorrow. As an added security measure I have just changed the new registration option to "admin approval" to keep the forum from being spammed during the night.

...talk to you tomorrow. And thank you so very much.

[GoldMine]

I've moved these posts to your own thread. Let's try to stay on topic. Thank you.