It does bring something new to the table...constant crashing.
Mt Gox Coin?
Topic: [ANN] Elacoin | Released | Fair Elastic Scrypt Mining | No Premine - page 36. (Read 133938 times)
May 14, 2013, 05:21:54 AM
Mt Gox Coin?
May 14, 2013, 05:21:43 AM
Using these two nodes - hope they are right?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
The one starting with 199 is mine, the one starting with 96 belongs to arjay45. Between the two of them, you'll probably connect to one or the other between crashes of elacoind. Both of us are seeing elacoind crash (segfault) every few minutes.
Originally the value was high, however that has being fixed.
Ha ha - so I am covered
Up till 4k blocks; not much left.
May 14, 2013, 05:21:01 AM
Using these two nodes - hope they are right?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
The one starting with 199 is mine, the one starting with 96 belongs to arjay45. Between the two of them, you'll probably connect to one or the other between crashes of elacoind. Both of us are seeing elacoind crash (segfault) every few minutes.
Originally the value was high, however that has being fixed.
May 14, 2013, 05:20:14 AM
The node 96.126.118.229 is owned by me. I have it automatically restarting when it segfaults -- which it does every few minutes. But well, what can you do. If there's a fix in the morning I'll pull it in and recompile (about 8 hrs from now).
-addnode=96.126.118.229
I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.
-addnode=96.126.118.229
I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.
BTW - Which distribution are you running? Debian 6.0 here, segfaults definitely occurring. The comments in the code for CBigNum suggest that older versions of Ubuntu will seg fault if difficulty is set incorrectly. Apparently not restricted to Ubuntu. So while it's happening as the result of an external library (certain versions of OpenSSL), there's already comments in the code saying it runs the risk of segfaulting if set incorrectly.
Ubuntu 12.04 LTS Server. Other people are saying litecoind doesn't segfault for them (and hasn't in months) yet elacoind is segfaulting. So I don't think it's my libraries. But I'm sleepy. Hopefully OP finds the bug and fixes it.
May 14, 2013, 05:20:03 AM
I have 1 coin after 100 orphans!!!
May 14, 2013, 05:19:39 AM
Personnaly I have decided to not waste any more time/gpupower on this coin.
The lunch was terrible at best and if the community think the concept of this coin could be interesting, we should just fork it and relunch it the way it supposed to be done.
Have a good day every one.
The lunch was terrible at best and if the community think the concept of this coin could be interesting, we should just fork it and relunch it the way it supposed to be done.
Have a good day every one.
+1
"Fool me once, shame on you. Fool me twice, shame on me."
May 14, 2013, 05:19:09 AM
(5s):5725.3K (avg):5717.5Kh/s | A:0 R:7123
this is amazing, i have almost as much as the pool has but m empty handed. maybe i need to stop LTC and point the farm here
this is amazing, i have almost as much as the pool has but m empty handed. maybe i need to stop LTC and point the farm here
May 14, 2013, 05:18:48 AM
w00t.... I am a ELA onellionaire
May 14, 2013, 05:17:53 AM
Personnaly I have decided to not waste any more time/gpupower on this coin.
The lunch was terrible at best and if the community think the concept of this coin could be interesting, we should just fork it and relunch it the way it supposed to be done.
Have a good day every one.
The lunch was terrible at best and if the community think the concept of this coin could be interesting, we should just fork it and relunch it the way it supposed to be done.
Have a good day every one.
May 14, 2013, 05:17:46 AM
Using these two nodes - hope they are right?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
The one starting with 199 is mine, the one starting with 96 belongs to arjay45. Between the two of them, you'll probably connect to one or the other between crashes of elacoind. Both of us are seeing elacoind crash (segfault) every few minutes.
May 14, 2013, 05:17:44 AM
any pools ?
May 14, 2013, 05:17:31 AM
THANKS for the Guide + 10 its working
Where did you get the elacoind.exe?
May 14, 2013, 05:16:50 AM
And how do we know its synced ? i only get a blinking dot...
Blockchain is not so large yet, so wait a couple of minutes.
is there a command to see this ?
tail debug.log
just open debug log file and see when stop flooding heigh=xxx
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
IRC got join
IRC got join
Added 50.137.151.133:7688 from 92.243.23.21: 17 tried, 308 new
IRC got new address: 50.137.151.133:7688
connection timeout
trying connection 86.157.191.43:9223 lastseen=0.1hrs
connected 86.157.191.43:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=86.157.191.43:9223, peer=86.157.191.43:9223
trying connection 198.199.86.4 lastseen=0.0hrs
Added time data, samples 6, offset +2 (+0 minutes)
receive version message: version 60001, blocks=4992, us=82.168.107.39:53994, them=86.157.191.43:9223, peer=86.157.191.43:9223
IRC got join
received block ee79864ed6088eaef4c6
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
received block 93fc3aef72622cded90d
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
disconnecting node 86.157.191.43:9223
Disconnected 86.157.191.43:9223 for misbehavior (score=100)
IRC got join
connection timeout
trying connection 54.245.12.125:9223 lastseen=0.1hrs
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
connection timeout
trying connection 118.210.234.30:9223 lastseen=0.1hrs
connected 118.210.234.30:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=118.210.234.30:9223, peer=118.210.234.30:9223
trying connection 198.199.86.4 lastseen=0.0hrs
Can anyone do this please
May 14, 2013, 05:16:21 AM
THANKS for the Guide + 10 its working
May 14, 2013, 05:16:02 AM
And how do we know its synced ? i only get a blinking dot...
Blockchain is not so large yet, so wait a couple of minutes.
is there a command to see this ?
when the daemon is running, open another command prompt.
browse to the directory with elacoind that's already running, and type "elacoind help" .
This will give you the list of console commands including "getinfo".
you don't want to type "elacoind -help" as that will show you the help for executing the daemon, which you already did in another cmd prompt.
Thank you! Had mine running for a bit now and says 'blocks' = 0 with getinfo. Guessing I just need to let it sit a bit?
May 14, 2013, 05:15:52 AM
The node 96.126.118.229 is owned by me. I have it automatically restarting when it segfaults -- which it does every few minutes. But well, what can you do. If there's a fix in the morning I'll pull it in and recompile (about 8 hrs from now).
-addnode=96.126.118.229
I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.
-addnode=96.126.118.229
I have lots of bandwidth, and should have low latency to US/Canada. The server is in Dallas, TX.
BTW - Which distribution are you running? Debian 6.0 here, segfaults definitely occurring. The comments in the code for CBigNum suggest that older versions of Ubuntu will seg fault if difficulty is set incorrectly. Apparently not restricted to Ubuntu. So while it's happening as the result of an external library (certain versions of OpenSSL), there's already comments in the code saying it runs the risk of segfaulting if set incorrectly.
May 14, 2013, 05:15:06 AM
And how do we know its synced ? i only get a blinking dot...
Blockchain is not so large yet, so wait a couple of minutes.
is there a command to see this ?
tail debug.log
just open debug log file and see when stop flooding heigh=xxx
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
IRC got join
IRC got join
Added 50.137.151.133:7688 from 92.243.23.21: 17 tried, 308 new
IRC got new address: 50.137.151.133:7688
connection timeout
trying connection 86.157.191.43:9223 lastseen=0.1hrs
connected 86.157.191.43:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=86.157.191.43:9223, peer=86.157.191.43:9223
trying connection 198.199.86.4 lastseen=0.0hrs
Added time data, samples 6, offset +2 (+0 minutes)
receive version message: version 60001, blocks=4992, us=82.168.107.39:53994, them=86.157.191.43:9223, peer=86.157.191.43:9223
IRC got join
received block ee79864ed6088eaef4c6
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
received block 93fc3aef72622cded90d
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
disconnecting node 86.157.191.43:9223
Disconnected 86.157.191.43:9223 for misbehavior (score=100)
IRC got join
connection timeout
trying connection 54.245.12.125:9223 lastseen=0.1hrs
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
connection timeout
trying connection 118.210.234.30:9223 lastseen=0.1hrs
connected 118.210.234.30:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=118.210.234.30:9223, peer=118.210.234.30:9223
trying connection 198.199.86.4 lastseen=0.0hrs
May 14, 2013, 05:14:55 AM
May 14, 2013, 05:14:06 AM
Using these two nodes - hope they are right?
addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
~22 MB addnode=199.204.38.220
addnode=96.126.118.229
What is the size of the blockchain?
May 14, 2013, 05:14:06 AM
And how do we know its synced ? i only get a blinking dot...
Blockchain is not so large yet, so wait a couple of minutes.
is there a command to see this ?
tail debug.log
just open debug log file and see when stop flooding heigh=xxx
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
IRC got join
IRC got join
Added 50.137.151.133:7688 from 92.243.23.21: 17 tried, 308 new
IRC got new address: 50.137.151.133:7688
connection timeout
trying connection 86.157.191.43:9223 lastseen=0.1hrs
connected 86.157.191.43:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=86.157.191.43:9223, peer=86.157.191.43:9223
trying connection 198.199.86.4 lastseen=0.0hrs
Added time data, samples 6, offset +2 (+0 minutes)
receive version message: version 60001, blocks=4992, us=82.168.107.39:53994, them=86.157.191.43:9223, peer=86.157.191.43:9223
IRC got join
received block ee79864ed6088eaef4c6
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
received block 93fc3aef72622cded90d
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
disconnecting node 86.157.191.43:9223
Disconnected 86.157.191.43:9223 for misbehavior (score=100)
IRC got join
connection timeout
trying connection 54.245.12.125:9223 lastseen=0.1hrs
IRC got join
connection timeout
trying connection 198.199.86.4 lastseen=0.0hrs
connection timeout
trying connection 118.210.234.30:9223 lastseen=0.1hrs
connected 118.210.234.30:9223
send version message: version 60001, blocks=0, us=82.168.107.39:9223, them=118.210.234.30:9223, peer=118.210.234.30:9223
trying connection 198.199.86.4 lastseen=0.0hrs
Jump to: