Topic: Help Me Do A Hard Fork (Read 659 times)
Got some great advice so far. Any other suggestions?
That's sound advice. The previous developer left without explanation, so your guess is as good as mine.
He didnt run off with a big payday. The pre-mine was .2%, mostly for giveaways.
I don't see any other issue with the coin other than the developer taking off. Solid coin that just needs some tlc.
He didnt run off with a big payday. The pre-mine was .2%, mostly for giveaways.
I don't see any other issue with the coin other than the developer taking off. Solid coin that just needs some tlc.
The developer of StabilityShares has taken off without explanation.
To make this sustainable you are going to need a full-time developer that knows what they're doing.
Determining why the last developer left would be a good place to start.
I think there are a few people in the community that would be willing to help with marketing, and attract miners if we can regain control of the coin.
If you were an investor, what would be the best course of action for recouping your money in this coin? I think I know someone with the technical abilities, just need step by step directions to get this done.
If you were an investor, what would be the best course of action for recouping your money in this coin? I think I know someone with the technical abilities, just need step by step directions to get this done.
http://www.reddit.com/r/dogecoin/comments/1y5anw/yes_the_network_has_forked_please_calm_down/
http://www.reddit.com/r/Bitcoin/comments/1a51xx/now_that_its_over_the_blockchain_fork_explained/
coins have been forked by accident when one pool gets too much hash rate based on disagreements with one version of a wallet and another.
however, an intentional 51% attack based on pool size (i.e. without changing wallets)has not been done before AFAIK, but is it more than probable. user BitcoinExpress has done this intentionally on weaker coins by overwhelming the entire network hash rate.
simply forking the coin won't change the parameters of the coin. to do this, someone will have to mod the source code. forking the coin means you'll at least have control over the coin, but having centralised control of the blockchain may not attract new miners/investors.
http://www.reddit.com/r/Bitcoin/comments/1a51xx/now_that_its_over_the_blockchain_fork_explained/
coins have been forked by accident when one pool gets too much hash rate based on disagreements with one version of a wallet and another.
however, an intentional 51% attack based on pool size (i.e. without changing wallets)has not been done before AFAIK, but is it more than probable. user BitcoinExpress has done this intentionally on weaker coins by overwhelming the entire network hash rate.
simply forking the coin won't change the parameters of the coin. to do this, someone will have to mod the source code. forking the coin means you'll at least have control over the coin, but having centralised control of the blockchain may not attract new miners/investors.
Would that actually work in practice, or is that just a theory?
why do you all just start mining on one pool? it's scrypt with no additional flavourings, so the trajectory of stabilityshares should just follow the longest chain on the block.
The developer of StabilityShares has taken off without explanation. I believe the coin holds a lot potential with its unique reward system, limited supply, and minimal pre-mine (0.2% for giveaways).
I am looking for help with doing a hard fork, so the people that invested their hard-earned money can find a way to recoup some of it. The community can take control of the development and marketing to ensure its success.
It seems straightforward: create a "genesis block" and add it to the code. Then update the node IPs to use only machines that have the new fork. That's my working theory
I am looking for help with doing a hard fork, so the people that invested their hard-earned money can find a way to recoup some of it. The community can take control of the development and marketing to ensure its success.
It seems straightforward: create a "genesis block" and add it to the code. Then update the node IPs to use only machines that have the new fork. That's my working theory
Jump to: