[Official] So what happened to Elacoin?

[Milkshake]

static CBigNum bnProofOfWorkLimit(~uint256(0) >> 10000000); // Elacoin: starting difficulty

Wait... this doesn't make sense. There's only 256 bits. Shifting right by ten million bits would result in zero. So the value of the above is zero.

On the other hand I have no idea what that variable means so feel free to ignore me if I'm talking out of my ass.

Just doubling my chances of the OP seeing this in case it's a bug... sorry to repeat myself.

Well, the value of it is not zero as you can see by debug.log

[1713243688]

1713243688

[1713243688]

1713243688

[dentldir]

If it was not Hazard, then it was  dentldir. I haven't said his name because I believe he was innocent until now, but Hazard is still denying it and I think it may have being the other guy I gave the source to.

Nope.  Wasn't me.  I didn't even see that you sent me the final source until 5 minutes before it was supposed to launch.  I just now got it to compile after plowing through a rather verbose boost error that was actually the same pthread_t error I PMed you about on the public git source.  However, the Windows client crashes after running for about 5 minutes.  Not ready for launch.

That being said, the linux client gets connections and doesn't download blocks.

However, the Windows client reported almost 137MH/s on the first run when I did getmininginfo.

Currently:
{
"blocks" : 5287,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00167116,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2012400,
"pooledtx" : 0,
"testnet" : false
}

Whoever is mining this thing is still going strong.

[com911]

Such an alt-drama here.  

[JohnDorien]

If it was not Hazard, then it was  dentldir. I haven't said his name because I believe he was innocent until now, but Hazard is still denying it and I think it may have being the other guy I gave the source to.

Nope.  Wasn't me.  I didn't even see that you sent me the final source until 5 minutes before it was supposed to launch.  I just now got it to compile after plowing through a rather verbose boost error that was actually the same pthread_t error I PMed you about on the public git source.  However, the Windows client crashes after running for about 5 minutes.  Not ready for launch.

That being said, the linux client gets connections and doesn't download blocks.

However, the Windows client reported almost 137MH/s on the first run when I did getmininginfo.

Currently:
{
"blocks" : 5287,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00167116,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2012400,
"pooledtx" : 0,
"testnet" : false
}

Whoever is mining this thing is still going strong.

well let's hope milkshake changed the sentence for genesis hash after the first source distibution

[nerdcustoms]

well 3:40 AM here now.... should I sleep, take a dump, or get coffee?  or all of the above?

[coinerd]

If it was not Hazard, then it was  dentldir. I haven't said his name because I believe he was innocent until now, but Hazard is still denying it and I think it may have being the other guy I gave the source to.

Nope.  Wasn't me.  I didn't even see that you sent me the final source until 5 minutes before it was supposed to launch.  I just now got it to compile after plowing through a rather verbose boost error that was actually the same pthread_t error I PMed you about on the public git source.  However, the Windows client crashes after running for about 5 minutes.  Not ready for launch.

That being said, the linux client gets connections and doesn't download blocks.

However, the Windows client reported almost 137MH/s on the first run when I did getmininginfo.

Currently:
{
"blocks" : 5287,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00167116,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2012400,
"pooledtx" : 0,
"testnet" : false
}

Whoever is mining this thing is still going strong.

how many coinds has it generated in 5k blocks of 2 Mh?

[r3animation]

If it was not Hazard, then it was  dentldir. I haven't said his name because I believe he was innocent until now, but Hazard is still denying it and I think it may have being the other guy I gave the source to.

Nope.  Wasn't me.  I didn't even see that you sent me the final source until 5 minutes before it was supposed to launch.  I just now got it to compile after plowing through a rather verbose boost error that was actually the same pthread_t error I PMed you about on the public git source.  However, the Windows client crashes after running for about 5 minutes.  Not ready for launch.

That being said, the linux client gets connections and doesn't download blocks.

However, the Windows client reported almost 137MH/s on the first run when I did getmininginfo.

Currently:
{
"blocks" : 5287,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00167116,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2012400,
"pooledtx" : 0,
"testnet" : false
}

Whoever is mining this thing is still going strong.

So you're releasing the windows binaries?

[arjay45]

static CBigNum bnProofOfWorkLimit(~uint256(0) >> 10000000); // Elacoin: starting difficulty

Wait... this doesn't make sense. There's only 256 bits. Shifting right by ten million bits would result in zero. So the value of the above is zero.

On the other hand I have no idea what that variable means so feel free to ignore me if I'm talking out of my ass.

Just doubling my chances of the OP seeing this in case it's a bug... sorry to repeat myself.

Well, the value of it is not zero as you can see by debug.log

Well I guess in C++ you can override the >> operator so it doesn't mean "shift right N bits" any more. But if that is still what it means then I would think there's a bug. But I don't know the source code very well. I am way too sleepy to go source diving at this hour. I'm helping with the mining of the genesis block though just in case it will speed this process up.

[nerdcustoms]

Not sure how the genesis block works, but is it something we can point the pool at and get it knocked out fast?  I don't mind throwing hashing power at it.

[Boxman90]

Yeah I'd much like to know how to help getting the genesis block. 3MH/s ready to go here. 6Mh/s if someone uploads a windows client, I can't build that.

[tytanick]

is it normal that i get now (but elacoind is running for sure)

Code:

Every 2,0s: ./elacoind getinfo                          Tue May 14 09:47:42 2013

error: couldn't connect to server

and in debug:

Code:

nonce 000B1000: hash = 06356f8425dd36908d3e124b34ed1636a2214c6ac0a243aaf6926d1e727a5302 (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B2000: hash = 564f23a9d3630274319a1b32095a0f4f87e45961e4017c3beb95961c03df927b (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B3000: hash = 895a23ab37830e58062824e89eac245f003214cd6a850d5c45bed092152162fd (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B4000: hash = 9ae87a856be3e232f4975bad08661ee26c6cda43008b8a39e572bd9725efffd7 (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B5000: hash = 5f38ae94695dfe74865434142c5349b6bc9b5fc06bef02b1e2fa00b210a3c761 (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B6000: hash = e4f3ed5edd43857fb196fd0f759aeb8d8880d2a075db5f8718026e6d6ec17ff6 (target = 00000ffff0000000000000000000000000000000000000000000000000000000)
nonce 000B7000: hash = fa50248a9d2d0e52920f914d643a97fdc9f70db644bb6a7332725919770116c1 (target = 00000ffff0000000000000000000000000000000000000000000000000000000)

[tytanick]

Yeah I'd much like to know how to help getting the genesis block. 3MH/s ready to go here. 6Mh/s if someone uploads a windows client, I can't build that.

Also 5MH/s from me

[dentldir]

how many coinds has it generated in 5k blocks of 2 Mh?

I think it's one coin per block.

[JohnDorien]

Yeah I'd much like to know how to help getting the genesis block. 3MH/s ready to go here. 6Mh/s if someone uploads a windows client, I can't build that.

Also 5MH/s from me

here's the windows daemon: https://mega.co.nz/#!P0hxFLjI!NtvycGW2xAZPmoXrGywnDHRoBwUmH0igQzhNw0zhEvU

just let it run if it crashes --> good! genesis block @ debug.log

[tytanick]

Elacoin relaunched !!!!
https://bitcointalk.org/index.php?topic=204823.0

[WindMaster]

If it was not Hazard, then it was  dentldir. I haven't said his name because I believe he was innocent until now, but Hazard is still denying it and I think it may have being the other guy I gave the source to.

Nope.  Wasn't me.  I didn't even see that you sent me the final source until 5 minutes before it was supposed to launch.  I just now got it to compile after plowing through a rather verbose boost error that was actually the same pthread_t error I PMed you about on the public git source.  However, the Windows client crashes after running for about 5 minutes.  Not ready for launch.

That being said, the linux client gets connections and doesn't download blocks.

However, the Windows client reported almost 137MH/s on the first run when I did getmininginfo.

Currently:
{
"blocks" : 5287,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00167116,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 2012400,
"pooledtx" : 0,
"testnet" : false
}

Whoever is mining this thing is still going strong.

I've left the original leaked elacoind running and have been watching it and using it for mining testing.  The block count you're seeing above indicates it's the same block chain I'm watching.  When I first started it, blocks were ~600 or so, so it doesn't appear to be the same block chain Hazard reported.  I also have slightly short of 1/2 of the coins minted on that block chain at the moment.  Appears the mining hash rate info is being calculated incorrectly, I have about 6MH/sec pointed at it which has mint roughly half the coins, so there's probably about 12MH/sec still on that chain.

{
    "version" : 60300,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 2264.00000000,
    "blocks" : 5486,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.00167116,
    "testnet" : false,
    "keypoololdest" : 1368517353,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

[barwizi]

stuck at syncing 162 blocks

[dentldir]

So you're releasing the windows binaries?

I shared my experience with Milkshake in building the Windows binary since I noticed he was stuck and I've been playing around with other alts recently.  The binary I have right now crashes hard when running as a server.  Probably because I built against the latest Bitcoin dependencies and not the ones in the original makefile.

Maybe I'm willing to help with a final release, but not inside all this drama.  I've already been called out because I tried to help and was sent source.  So far, not a great environment to jump into.

Either way, it shouldn't happen in a hurry.  It was ready for alpha today and testing by a limited experienced group.  Its clear the difficulty was too low as well.  

[dentldir]

I've left the original leaked elacoind running and have been watching it and using it for mining testing.  The block count you're seeing above indicates it's the same block chain I'm watching.  When I first started it, blocks were ~600 or so, so it doesn't appear to be the same block chain Hazard reported.  I also have slightly short of 1/2 of the coins minted on that block chain at the moment.  Appears the mining hash rate info is being calculated incorrectly, I have about 6MH/sec pointed at it which has mint roughly half the coins, so there's probably about 12MH/sec still on that chain.

{
    "version" : 60300,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 2264.00000000,
    "blocks" : 5486,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.00167116,
    "testnet" : false,
    "keypoololdest" : 1368517353,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

I guess the new chain is up now.  Orphan city with around 2MH/s with 31 connections.

[theking]

need some more nodes