Pages:
Author

Topic: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin - page 20. (Read 92682 times)

full member
Activity: 213
Merit: 100
Mining history: BTC->LTC->FTC->CRC:2200kh/s
hey is anyone here a mod on the spendlitecoin server?  I would like the go ahead on some mods but i'm the only one EVER online... k well that's not true but i'm the only one on in the evenings it seems

i would like to use mini map and autofish
legendary
Activity: 2674
Merit: 3000
Terminated.
Have the recent problems been resolved?
legendary
Activity: 1232
Merit: 1094
This solution is closer to viable. Still a little bit problematic if the hashrate suddenly drops, but definitely better than our current situation.

If you are willing to accept some centralization in the solution, you could add a rule where the devs can reset the difficulty (including the no-mint timeout).  This could be a special signed block header or something similar.  It would have to be part of the chain, so it can be verified.

Have you updated the alert keys so you can issue alerts?
full member
Activity: 156
Merit: 100
The update won't even cause a fork.


I suggest your new rules should be

- reset the difficulty to 1 starting at block
- the next 144 blocks have no block reward (other than tx fees)
- updates the difficulty every block based on the last 144 blocks
- caps the difficulty change to 1% per block

The 144 zero payment blocks prevent a "pre-mine" situation. 

It gives the network a chance to find the current hashing power without it being a giveaway.

It also means that nobody can make the accusation that those who happened to be online when the fork went live got an advantage.

This solution is closer to viable. Still a little bit problematic if the hashrate suddenly drops, but definitely better than our current situation.
legendary
Activity: 1232
Merit: 1094
The update won't even cause a fork.

I think what you mean is that coins from pre-fork will work on both old and new chains.

The difficulty drop-off problem is a problem that has plagued all alt coins.

Bitcoin is a "price maker".  This means that when they drop the price they pay per hash, the market adjusts to their new price.

Some miners might switch to alt chains, but mostly they can absorb price shifts.

In addition, since they have such a large share of the hashing power, it is less likely that they get hit with a surge of hashing power.

Alt coins are "price takers".  This means that they can't control the price of hashing power.

If they drop their price by a large step, then they will get no hashing power.

Changing the difficulty every block, even if the window is large is better than changing it in one big step.

If you limited the change to 1% per block, then after 144 blocks, you get a 4.19X change, which is pretty close to the current limits.

I suggest your new rules should be

- reset the difficulty to 1 starting at block
- the next 144 blocks have no block reward (other than tx fees)
- updates the difficulty every block based on the last 144 blocks
- caps the difficulty change to 1% per block

The 144 zero payment blocks prevent a "pre-mine" situation. 

It gives the network a chance to find the current hashing power without it being a giveaway.

It also means that nobody can make the accusation that those who happened to be online when the fork went live got an advantage.
full member
Activity: 196
Merit: 100
The update won't even cause a fork.

I don't think that word means what you think it does.

This update is exactly the definition of a hard fork. A change to the protocol, which many (most) of the existing clients will reject, causing the creation of two incompatible block chains with the same name and other identifiers.

 Huh
full member
Activity: 136
Merit: 100
Actually the update did not affect the coin any. The update won't even cause a fork. @Russ this patch is perfect for your coin. It is an easy fix that will prevent flash mining by 3 hour block readjusts:36 blocks.
legendary
Activity: 1844
Merit: 1338
XXXVII Fnord is toast without bread
I realize it is not my place to discuss what other miners and pool owners are doing for or against this coin. I feel that it is imperative that we all are on the same page.
FYI there was discussion on an exchange where people were placing a high priority on this unapproved "fix", they were trying to get a new pool established with the new code. It is very likely that these 5 or so people have already done damage to this coin. I am sure I don't need to name names.
full member
Activity: 156
Merit: 100

It's not a "No" but it's definitely not a "Yes" - Lets just say I'm keeping our options open for a day or two.


Rapid adjustment can, on the one hand, simply allow any attackers or hopping pools to push the diff even higher before abandoning the coin again.  I wish I had better input to give but I'm stumped by this one - as long as it's coins vs miners it seems most other types of development and innovation are going to have to stop (or at least slow way down) until someone figures out a long term fix for this.


This is exactly my reservation with this type of fix.
full member
Activity: 196
Merit: 100

It's not a "No" but it's definitely not a "Yes" - Lets just say I'm keeping our options open for a day or two.


As one of the only alts to try and develop a unique infrastructure before announcing yourselves, I think there are plenty of people happy to give you the time you need.

Rapid adjustment can, on the one hand, simply allow any attackers or hopping pools to push the diff even higher before abandoning the coin again.  I wish I had better input to give but I'm stumped by this one - as long as it's coins vs miners it seems most other types of development and innovation are going to have to stop (or at least slow way down) until someone figures out a long term fix for this.

In the meantime a sudden attempt to hard-fork someone else's coin while the dev is still actually working with it is a pretty lame-ass maneuver.
full member
Activity: 156
Merit: 100
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

+

Quote from: justin7674
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.

+

Quote from: justin7674

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.

 


This is a good springboard for what I wanted to reply. One of the reasons I haven't been quick to apply this fix is because I am unsure of its effectiveness. Simply lowering the max re-target, and shortening the time span for re-target isn't a real fix IMO. A patch? possibly (possibly not)... The simple fact is that this doesn't fix the root of the problem. In fact it could compound it even more if the network gets 2-3 solid days of high hashrate (which is likely to happen).

It's not a "No" but it's definitely not a "Yes" - Lets just say I'm keeping our options open for a day or two.
legendary
Activity: 1232
Merit: 1094
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

Exactly, the update is being "reviewed", that isn't a reason to put it into usage.

If it is rejected, then all mining on the fork is wasted.
efx
sr. member
Activity: 378
Merit: 250
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

+

Quote from: justin7674
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.

+

Quote from: justin7674

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.

 
full member
Activity: 213
Merit: 100
Mining history: BTC->LTC->FTC->CRC:2200kh/s
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.
sr. member
Activity: 448
Merit: 250
http://crc.scryptmining.com will update whenever official github is updated.


Watching this thread.
legendary
Activity: 2590
Merit: 2156
Welcome to the SaltySpitoon, how Tough are ya?
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.
legendary
Activity: 1844
Merit: 1338
XXXVII Fnord is toast without bread
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
full member
Activity: 213
Merit: 100
Mining history: BTC->LTC->FTC->CRC:2200kh/s
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.
full member
Activity: 136
Merit: 100
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.
full member
Activity: 213
Merit: 100
Mining history: BTC->LTC->FTC->CRC:2200kh/s
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
Pages:
Jump to: