tried it on ubuntu, not functional, unless i missed something.  |
|
|
|
|
If a group with twice the has power uses an updated client then forces a fork, it may work, i know how to do it, i've already done it for two coins so far (results in two days). The main advantage to reviving this coin is that it is traded on the big exchanges already, i could change the retarget algo and push the update, but are people interested? and what is this "reward" you speak of?
|
|
|
|
I think you meant 12LTC per k lol. I started to jump all over that transaction  hahaha, yes, sorry and thank you. |
|
|
|
|
whats the current difficulty?
|
|
|
|
|
that's great, when can we expect a release?
|
|
|
|
|
ok, i'm done changing, am "test" compiling now, who would like to tell me how to compile for windows, or would the source code suffice?
|
|
|
|
so should i do it or not?  |
|
|
|
/usr/bin/ld: cannot find -lboost_system-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_filesystem-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_program_options-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_thread-mgw46-mt-sd-1_53
collect2: error: ld returned 1 exit status
make: *** [americancoin-qt] Error 1
what to do now?
Never mind-installing boost won't help you. What WILL help is fixing the americancoin-qt.pro. Check it out, I'm compiling on unix and clearly there isn't a c:/xxxx/xxxx BOOST_LIB_SUFFIX=-mgw46-mt-sd-1_53 BOOST_INCLUDE_PATH=C:\deps\boost_1_53_0 BOOST_LIB_PATH=C:\deps\boost_1_53_0\stage\lib BDB_INCLUDE_PATH=c:/deps/db-4.8.30.NC/build_unix BDB_LIB_PATH=c:/deps/db-4.8.30.NC/build_unix OPENSSL_INCLUDE_PATH=c:/deps/openssl-1.0.1e/include OPENSSL_LIB_PATH=c:/deps/openssl-1.0.1e to get this working, just delete the above lines from americancoin-qt.prohehe thanks, so if i hit a few blocks, one has your name on it. |
|
|
|
|
/usr/bin/ld: cannot find -lboost_system-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_filesystem-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_program_options-mgw46-mt-sd-1_53
/usr/bin/ld: cannot find -lboost_thread-mgw46-mt-sd-1_53
collect2: error: ld returned 1 exit status
make: *** [americancoin-qt] Error 1
what to do now?
|
|
|
|
-1 Reasoning is the same as Kyune stated above: I see no reason to change the constant, that just devalues any blocks mined so far (which have all had value of 1)...just change the divisor under the difficulty so the reward ramps up quicker as more people mine the coin.
Everyone that has mined Elacoin so far (and that includes me) have understood the reward parameters to be a certain set of established numbers with a certain slope as block count rises, that you're proposing to change. Effectively, you're proposing to wipe the vast majority of the value (if any) held by anyone who mined prior to your fork. the math has been done and we have devised a way that increases reward and does not devalue the current holders, it actually increases value. |
|
|
|
 its looking good i need more votes and help to get this thing going when i release the updated client
|
|
|
|
I saw your post in the original thread. I think increasing the retarget frequency is probably a good idea. But if you are going to change the original subsidy formula int64 nSubsidy = ((1 + (diff / 24)) * COIN) / (1 + (nHeight / 194400));
I see no reason to change the constant, that just devalues any blocks mined so far (which have all had value of 1)...just change the divisor under the difficulty so the reward ramps up quicker as more people mine the coin. Something like: int64 nSubsidy = ((1 + (diff / 2)) * COIN) / (1 + (nHeight / 194400));
ok, i'll run a simulation on it and see the results. so |
|
|
|
if i get 10 votes up i will do this, the overall net hash rate is 3.5mh/s and if we don't do this quick, this coin will die. Votes please
Last Active: 25-05-2013, 09:41:53 https://bitcointalk.org/index.php?action=profile;u=81730I think that rules can not changed without developer,..., Similar thing (fast retarget) could happen with Chncoin, and other coins under "miners attack", but, Anyone knows if miners, exchanges,... will use the forked client? What about blockchain?, if not. uhh, if the dev disappears the community can continue, we dont need him. as for being attacked, this coin has only 2.5 mh/s left, jus pointing one rig at it, i can force a fork. what we need to do is encourage people to download the updated client then start mining, the chain is the same, only updated parameters. your balances are saved if you back up your wallet.dat anyone with coding skills can change it, it's just up to the community to choose who's changes the will follow. |
|
|
|
Make it 11, I'm just not mining right now cause I'm busy compiling(or trying to)
1. I vote that we wait and do some thinking first, then have a put-together update instead of something just thrown together quicklike. I don't want to yeah or nay anything without some reasoned discussion.
2. I'm not really for or against any of your proposed changes right now, except that it's going to cause a fork(it is, right?) and I don't want to see an update that only has a linux client and no windows client. I can compile a headless elacoind.exe at the moment but I'm having trouble getting it to compile with the QT frontend too.
3. again, I'm not for or against any of those changes really, but at the same time I don't really see any point in changing them except to fill some psychological need to see big numbers. the faster block time really isn't that big of a change but... is it necessary? is a 2.5 min block time that bad?
mat5x is working on it... so, just wait and let's have something that we can feel more sure about. join the #elacoin chat on freenode if you want(probably not anyone on right now...)
that's the thing, if the hasrate goes below a certain number, the chain will literary die out, i've tried keeping the convo going but it seems only mat5x is responding. yes it is a psychological thing, but it works.. if you will take the windows side, that would be great, i run all my machines on various versions of linux, i barely remember how to work windows. things is, the community is 4 guys who are mining this on the pool, and by day's end, there may be noone there. Action is required fast and strong to bring the chain back to life and get miners working. As you know there are new altcoins everyday, and if this coin falls into that sesspool, it will never get out. |
|
|
|
|
+1 if you want these changes
1) block reward up to 50
2) retarget every hour
-1 if you disagree, please state your reasons so we can improve.
|
|
|
|
|
since noone is trying to, i'll change it. I am increasing block reward to
int64 nSubsidy = ((25 + (diff / 24)) * COIN) / (1 + (nHeight / 194400)); // 25 ELC per block
from
int64 nSubsidy = ((1 + (diff / 24)) * COIN) / (1 + (nHeight / 194400));
and retarget to
static const int64 nTargetTimespan = 1 * 1 * 60 * 60; // Elacoin: 1 hour
static const int64 nTargetSpacing = 2 * 60; // Elacoin: 2 minutes
static const int64 nInterval = nTargetTimespan / nTargetSpacing;
from
static const int64 nTargetTimespan = 3 * 24 * 60 * 60; // Elacoin: 3 days
static const int64 nTargetSpacing = 2 * 60; // Elacoin: 2.5 minutes
static const int64 nInterval = nTargetTimespan / nTargetSpacing;
any ideas of anything else i should change? Any objections?
i've been studying the code and i think i've got the idea
if i get 10 votes up i will do this, the overall net hash rate is 3.5mh/s and if we don't do this quick, this coin will die. Votes please
edit, ten votes coz i can only see 4 people mining @ the pool.
|
|
|
|
|
There's a 5LTC extra for block 22166 already, people are adding to the bounties.
|
|
|
|
|
Show Posts
