|
Yes still mine it, it's good time now
|
|
|
|
why so many retards here? to educate people of pos?? what a joke? why steal the name of an existing and successful coin? there are so many pos coins there, need to steal a name to "educate"? why not choose another name? clearly the dev is jealous of the success of ifc and wanted to steal something out of it. a purely mentally challenged behavior and a shame to the dev.
+1 can't believe some devs so stupid +1, lmao |
|
|
|
|
This coin has been there for long time, should be listed in cryptsy!
|
|
|
|
IFC goes crazy  |
|
|
|
Agree, used "ignore" button, this way it's much easier to read the thread than going through these long and useless paragraphs. Very few jerks like this in the forum, but good suggestions to skip them  |
|
|
|
|
I mined ELP and I will continue mine it, I don't care what people say about premine. It sounds soooo stupid to me, if you hate so much about premine, go away, period. No one ever asked you to mine it.
Everyone understands that by any standard, this is just an average premined coin to the worst. There are many coins premined much more than this (like a recent one premined 7.5 mil), so there's no point to discuss over and over the premine for ELP, simply sound very stupid to me, someone is a jerk.
|
|
|
|
Hows the chain coming mono, or anyone else out there who has this ver?
I restarted the client, it seems sync'ing. Now seems stuck at block 9540. but my previous 1000 some coins are gone! I am pretty sure it is not the original chain, do you have the check points in the code? |
|
|
|
yes please publish it, my 1.2 (existing) client sync's at 8347 only...
http://rapidshare.com/files/1990813362/philosopherstone-qt.zip grab it and join the *maybe* the main chain the client stuck at block 3500, with a lot errors in the log: ERROR: mempool transaction missing input ERROR: mempool transaction missing input ERROR: mempool transaction missing input ERROR: mempool transaction missing input |
|
|
|
it's a sad thing to see the owner announce his own baby dead... maybe this guy owes another apology to the community?  |
|
|
|
maybe you are right, but recent pow/pos coins have a lot problems, not only this one.
This means nothing. I can jump from the rooftop, and then say that it's a problem of building design, but that would be a false. As a comparison, pow only coins have much less problems and mostly stable.
Just because the most copy&paste developers already made this errors in the past. They know what they allowed or disallowed to do with the PoW design. But it doesn't mean that the PoW design is matured enough or hybrid design isn't matured enough. lol, pow/pos are copy-paste too, tho john claimed changed something, I guess it's small things. |
|
|
|
Looks like there base code may not be as mature as Litecoin...
Elacoin and many another examples can prove that you are wrong. Shitty code could be done using any codebase. maybe you are right, but recent pow/pos coins have a lot problems, not only this one. As a comparison, pow only coins have much less problems and mostly stable. Maybe the dev of these coins all screwed on something... |
|
|
|
|
yes please publish it, my 1.2 (existing) client sync's at 8347 only...
|
|
|
|
The bug is ridiculously simple. if(GetAdjustedTime() > RWD_SWITCH_TIME)
nSubsidy /= 64; GetAdjustedTime() call MUST be replaced with nTime. After this you should re-download block chain and add the new checkpoint. It's the only way to continue operation correctly. P.S. I really have no idea why anyone would try to use GetAdjustedTime() here. 1.2 made it past 6084 but seems to go very very slow now 8332,..8333..8334 very slow I am using the existing 1.2 client, and it has been very slow now at block 8337, the block still advance but slowly. It seems that it's been sync'ing the pos blocks... Oh well, seems to me all the recent pow/pos coin have problems, HBN, CAP, STR, GRW, etc. Looks like there base code may not be as mature as Litecoin... |
|
|
|
The bug is ridiculously simple. if(GetAdjustedTime() > RWD_SWITCH_TIME)
nSubsidy /= 64; GetAdjustedTime() call MUST be replaced with nTime. After this you should re-download block chain and add the new checkpoint. It's the only way to continue operation correctly. P.S. I really have no idea why anyone would try to use GetAdjustedTime() here. hmm thanks Balthazar... with expert's word can someone please fix the issue and recompile the client? John does not have access to his build env and someone else please fix the problem and publish the client? Then we should be back on track... just above your post nice, sorry I missed it, will try now.. oh, do you have a windows client? |
|
|
|
The bug is ridiculously simple. if(GetAdjustedTime() > RWD_SWITCH_TIME)
nSubsidy /= 64; GetAdjustedTime() call MUST be replaced with nTime. After this you should re-download block chain and add the new checkpoint. It's the only way to continue operation correctly. P.S. I really have no idea why anyone would try to use GetAdjustedTime() here. hmm thanks Balthazar... with expert's word can someone please fix the issue and recompile the client? John does not have access to his build env and someone else please fix the problem and publish the client? Then we should be back on track... |
|
|
|
|
need a consensus, if the community will go back to 1.1 chain, we should probably do it, but it seems to me that 1.1 chain is not a good one, it is a forked one, not the original one.
|
|
|
|
|
dump all the 10 premined to a random non-exist address.
|
|
|
|
|
Which version you guys using? 1.1 or 1.2? I guess 1.2 is the one to use?
|
|
|
|
|
can't connect network, anyone can post some IPs for addnode? thanks.
|
|
|
|
|
Show Posts
