Sounds like merged mining would be a good idea.
That way you can go ahead and mine litecoin or whatever but still also be applying that same hashing power to this coin.
Your supporters thus won't have to choose between mining for profit and mining to support this coin, they can mine whatever scrypt coin they like for profit but also merge in this coin to support this coin.
-MarkM-
Topic: [ANN] Elacoin | Released | Fair Elastic Scrypt Mining | No Premine - page 9. (Read 133887 times)
July 14, 2013, 09:14:08 PM
July 14, 2013, 09:03:30 PM
Dead coin?
June 22, 2013, 03:39:15 PM
I think we need to really sit down and work on this, the algo is still nbot matching up with current market trends.
June 22, 2013, 02:31:51 PM
More of the same, it seems:
Code:
06/16/13 22:06:27 REORGANIZE: Disconnect 168 blocks; aa0c7d4a4175c0a7e60f..d46843aec3fa51f1d936
06/16/13 22:06:27 REORGANIZE: Connect 169 blocks; aa0c7d4a4175c0a7e60f..753aef9f7df2242cc154
06/16/13 22:06:27 REORGANIZE: Connect 169 blocks; aa0c7d4a4175c0a7e60f..753aef9f7df2242cc154
( well if people dont mine, what can we do. at least THEY'RE mining, tho they're not processing transactions either :/privmsg'd you , like your feedback.
June 16, 2013, 06:11:37 PM
More of the same, it seems:
Code:
06/16/13 22:06:27 REORGANIZE: Disconnect 168 blocks; aa0c7d4a4175c0a7e60f..d46843aec3fa51f1d936
06/16/13 22:06:27 REORGANIZE: Connect 169 blocks; aa0c7d4a4175c0a7e60f..753aef9f7df2242cc154
06/16/13 22:06:27 REORGANIZE: Connect 169 blocks; aa0c7d4a4175c0a7e60f..753aef9f7df2242cc154
June 07, 2013, 02:50:22 AM
is their any windows version for this yet ?
Windows version at github:
https://github.com/elacoin/elacoin/tree/master/windows-binaries
and mac too!
June 06, 2013, 07:20:06 PM
is their any windows version for this yet ?
June 04, 2013, 02:30:20 PM
scryptmining pool reporting bug fixed, payouts coming.
elacoinpool should be soon./
elacoinpool should be soon./
June 04, 2013, 02:35:04 AM
i help run ZeroPool.
it is finding new blocks, but this Pool software which all 3 pools run, are reporting stats wrong. So do not fear. its a reporting bug, not a bug that will affectshares and payouts:
BitcoinMiner:
proof-of-work found
hash: 000000000f58129f05a2de1c1128eff79dbfb6624ca08ef06ed1615bef8aa1b9
target: 00000000cce90000000000000000000000000000000000000000000000000000
CBlock(hash=1e314295a5ebd3aa2578, PoW=000000000f58129f05a2, ver=1, hashPrevBlock=381151d6190187646a4e, hashMerkleRoot=9866b6f29a, nTime=1370326748, nBits=1d00cce9, nNonce=2013293824, vtx=1)
CTransaction(hash=9866b6f29a, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04db86ad510109062f503253482f)
CTxOut(nValue=0.90979200, scriptPubKey=022b9212cea3821d494cd934dde681)
vMerkleTree: 9866b6f29a
generated 0.909792
keypool keep 260
AddToWallet 9866b6f29a new
SetBestChain: new best=1e314295a5ebd3aa2578 height=18955 work=30760650524082 date=06/04/13 06:19:08
ProcessBlock: ACCEPTED
for eg.
someone comment on the pools' bug? (I didnt install the pool or set it up, i just helped update the client behind it properly.)
it is finding new blocks, but this Pool software which all 3 pools run, are reporting stats wrong. So do not fear. its a reporting bug, not a bug that will affectshares and payouts:
BitcoinMiner:
proof-of-work found
hash: 000000000f58129f05a2de1c1128eff79dbfb6624ca08ef06ed1615bef8aa1b9
target: 00000000cce90000000000000000000000000000000000000000000000000000
CBlock(hash=1e314295a5ebd3aa2578, PoW=000000000f58129f05a2, ver=1, hashPrevBlock=381151d6190187646a4e, hashMerkleRoot=9866b6f29a, nTime=1370326748, nBits=1d00cce9, nNonce=2013293824, vtx=1)
CTransaction(hash=9866b6f29a, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04db86ad510109062f503253482f)
CTxOut(nValue=0.90979200, scriptPubKey=022b9212cea3821d494cd934dde681)
vMerkleTree: 9866b6f29a
generated 0.909792
keypool keep 260
AddToWallet 9866b6f29a new
SetBestChain: new best=1e314295a5ebd3aa2578 height=18955 work=30760650524082 date=06/04/13 06:19:08
ProcessBlock: ACCEPTED
for eg.
someone comment on the pools' bug? (I didnt install the pool or set it up, i just helped update the client behind it properly.)
June 04, 2013, 01:10:49 AM
i really hate these people. June 03, 2013, 11:40:02 PM
I updated (elacoind kept crashing). But is there an issue?
[/quote]
Thanks for the update, now we might get some real hashpower to cement things in place properly to stop this kind of attack.
June 03, 2013, 11:37:37 PM
is there an issue? maybe. someone went and mined their own chain of 283, and beat our chain.
hows that possible? by them having more hash power. I dont think its any of the pools as I know individuals with as much power as the pools, and there's 2-3 of them out there who are acting (as far as Iknow...) on good faith. just like every other coin.
what can we do? continue mining. someone with a lot of hash power thinks the coin is worth something, so we got someone's attention. it's up to us if we want to maintain the value in the coins we already have or not.
the difficulty is slightly lower than it should be (.15 instead of .3) so current coins worth more than later coins too, so that's a (kinda, wierd) bonus for now til 18360 when regular reward takes over.
only more hashing power by fair-dealing miners will stop this, or else its worth nothing to anyone.
hows that possible? by them having more hash power. I dont think its any of the pools as I know individuals with as much power as the pools, and there's 2-3 of them out there who are acting (as far as Iknow...) on good faith. just like every other coin.
what can we do? continue mining. someone with a lot of hash power thinks the coin is worth something, so we got someone's attention. it's up to us if we want to maintain the value in the coins we already have or not.
the difficulty is slightly lower than it should be (.15 instead of .3) so current coins worth more than later coins too, so that's a (kinda, wierd) bonus for now til 18360 when regular reward takes over.
only more hashing power by fair-dealing miners will stop this, or else its worth nothing to anyone.
June 03, 2013, 11:24:10 PM
hard fork working well, we're at 1.95 minutes per block. cant get any better than that (target was 2 minutes.)
next diff will likely move us from .27 to .3 , leaving the block time as is! sweet. this is working properly.
high value coins coming out now til 18360 before regular scaling takes hold. set your miners on KILL!
I WISH COINCHOOSE WOULD UPDATE it's showing 16x LOWER than actual. get in before everyone finds out.
next diff will likely move us from .27 to .3 , leaving the block time as is! sweet. this is working properly.
high value coins coming out now til 18360 before regular scaling takes hold. set your miners on KILL!
I WISH COINCHOOSE WOULD UPDATE it's showing 16x LOWER than actual. get in before everyone finds out.
I updated (elacoind kept crashing). But is there an issue?
June 03, 2013, 11:18:17 PM
So....we just got screwed eh?
June 03, 2013, 10:54:52 PM
received block c4d5612cf8e54e4ffc36 from 96.53.211.181:9223
received block c5b12feb83fe0300f48b from 72.78.100.13:9223
REORGANIZE
REORGANIZE: Disconnect 282 blocks; 7f24078d4a4e023e2d6c..01fd900e3436f1df4b46
REORGANIZE: Connect 283 blocks; 7f24078d4a4e023e2d6c..9e4124071bcad1ed3a35
cant fight someone with a giant rig just by having a nice coin setup with a supportive community. that's worth nothing.
comments?
received block c5b12feb83fe0300f48b from 72.78.100.13:9223
REORGANIZE
REORGANIZE: Disconnect 282 blocks; 7f24078d4a4e023e2d6c..01fd900e3436f1df4b46
REORGANIZE: Connect 283 blocks; 7f24078d4a4e023e2d6c..9e4124071bcad1ed3a35
cant fight someone with a giant rig just by having a nice coin setup with a supportive community. that's worth nothing.
comments?
June 03, 2013, 10:11:59 PM
hard fork working well, we're at 1.95 minutes per block. cant get any better than that (target was 2 minutes.)
next diff will likely move us from .27 to .3 , leaving the block time as is! sweet. this is working properly.
high value coins coming out now til 18360 before regular scaling takes hold. set your miners on KILL!
I WISH COINCHOOSE WOULD UPDATE it's showing 16x LOWER than actual. get in before everyone finds out.
next diff will likely move us from .27 to .3 , leaving the block time as is! sweet. this is working properly.
high value coins coming out now til 18360 before regular scaling takes hold. set your miners on KILL!
I WISH COINCHOOSE WOULD UPDATE it's showing 16x LOWER than actual. get in before everyone finds out.
June 03, 2013, 01:39:47 PM
New pool up and ready to go for the hard fork. http://elc.scryptmining.com stratum-only, proportional payout per block. Check us out!
June 02, 2013, 07:23:57 PM
For clarification, most of the fixes I managed to find scouring through threads on bitcointalk. So, I think I pulled a fix by comparing tyrone70's .pro? and I can't remember where I got the fix for the net.cpp. I had other problems that were just me being stupid. I can't remember everything
Windows client Binary download(compiled w/ mat5x's 6/2/13 source):
https://docs.google.com/file/d/0B0p_1nvOYdjzVmx5Sk5FSHNwUW8/edit?usp=sharing
To Compile windows QT client(get sources from github?
:
If you want to compile for windows, you need to do 2 things:
1. In the elacoin-qt.pro file you need to add(no quotes) "__NO_SYSTEM_INCLUDES" to the DEFS(it's at the top). If you're compiling elacoind.exe do "-D__NO_SYSTEM_INCLUDES" instead, and do it in Makefile.mingw instead.
in net.cpp, you need to remove the "/miniupnpc/" from all the UPNP header includes. Not an ideal solution but it works.
I compiled with UPNP support. You don't have to, but I don't see why it would hurt to compile it with it. You'll get some noise from qmake either way.
Otherwise, follow the instructions for building the headless windows bitcoin QT client here:
NOTES:
1. You can ignore the leveldb stuff
2. make sure your directory slashes are unix style "/" in elacoin-qt.pro and makefile.mingw
https://bitcointalksearch.org/topic/building-headless-bitcoin-and-bitcoin-qt-on-windows-149479
I'll upload the client to google drive just as soon as I can get it compiled.
Windows client Binary download(compiled w/ mat5x's 6/2/13 source):
https://docs.google.com/file/d/0B0p_1nvOYdjzVmx5Sk5FSHNwUW8/edit?usp=sharing
To Compile windows QT client(get sources from github?
: If you want to compile for windows, you need to do 2 things:
1. In the elacoin-qt.pro file you need to add(no quotes) "__NO_SYSTEM_INCLUDES" to the DEFS(it's at the top). If you're compiling elacoind.exe do "-D__NO_SYSTEM_INCLUDES" instead, and do it in Makefile.mingw instead.
in net.cpp, you need to remove the "/miniupnpc/" from all the UPNP header includes. Not an ideal solution but it works.
I compiled with UPNP support. You don't have to, but I don't see why it would hurt to compile it with it. You'll get some noise from qmake either way.
Otherwise, follow the instructions for building the headless windows bitcoin QT client here:
NOTES:
1. You can ignore the leveldb stuff
2. make sure your directory slashes are unix style "/" in elacoin-qt.pro and makefile.mingw
https://bitcointalksearch.org/topic/building-headless-bitcoin-and-bitcoin-qt-on-windows-149479
June 02, 2013, 06:05:47 PM
godamnit. BTCtalk went down middle of my post and i lost it all. :/
diff of code changes to the 2 main functions in main.cpp:
http://pastebin.mozilla.org/2478635
sorry the comments are cut off in the diff.
github:
https://github.com/elacoin/elacoin/tree/master/src
comments also cut off there unless you download it, can view here the 3 files that were changed.
full code in there. only 2 functions changed in main.cpp (reward and diff retargetting). net.cpp has 1 debug line extra to see who sent you a block, and irc.cpp changes the irc channel so old and new clients dont collide as much. (actually the line is in main.cpp for the debug, not net.cpp, so its untouched except increasing max clients, a local mod for myself, removing it from git)
edit: net.cpp is now stock original.
Comments?
-mat5x
diff of code changes to the 2 main functions in main.cpp:
http://pastebin.mozilla.org/2478635
sorry the comments are cut off in the diff.
github:
https://github.com/elacoin/elacoin/tree/master/src
comments also cut off there unless you download it, can view here the 3 files that were changed.
full code in there. only 2 functions changed in main.cpp (reward and diff retargetting). net.cpp has 1 debug line extra to see who sent you a block, and irc.cpp changes the irc channel so old and new clients dont collide as much. (actually the line is in main.cpp for the debug, not net.cpp, so its untouched except increasing max clients, a local mod for myself, removing it from git)
edit: net.cpp is now stock original.
Comments?
-mat5x
June 02, 2013, 03:10:22 PM
the community is small enough, if the code is available, maybe you should release now and let people see the changes before they decide to join the band wagon
yep that's fair we're just testing things out now to make sure we're not totally breaking things.
will post this aft tho i dont know if everyone should adopt the code immediately til we decide it's good. not just good coin parameters, but good code syntax, no bugs
retarg is looking like @ block #17820, which is 8.25 * 2160 (ie exactly 1/4 into the 2160 block retarg cycle) and just a few dozen blocks ahead of us. (at 17790ish now)
for simplicity we've also decided to set the reward to 1.00 ELC as it is right now, until the network settles down with miners after the retarg, then after 1/4 * 2160 blocks (ie 540 blocks) the scaling of the 270 day cycle will apply (and block will be slightly less than value 1 ELC due to scaling of course, as we're 9% of the way to 194400 (270days) at #18360 (8.5 *2160))
the blockrate has been very slow, so trying to add code that allows scaling to give something closer to the proper block rate. however, if diff drops < 1, rewards are still given as if diff = 1 to give a minimum incentive to keep mining (as mentioned previously).
so summary:
block 0-17820: reward 1, retarg diff at 17820
block 17821-18360: reward 1
block 18361+: reward scaled by (block#+194400)/194400
glad to have you onboard!
Jump to: