Topic: ... - page 2. (Read 63883 times)
Watch out for the http://dice.emoticoin.org/
I sent my 6500000 coins there more than 12 hours ago and they still arent there. Im guessing it is a scam.
I sent my 6500000 coins there more than 12 hours ago and they still arent there. Im guessing it is a scam.
Linux source: https://github.com/emoticoins/emoticoin - git clone https://github.com/emoticoins/emoticoin.git
Windows binary: https://mega.co.nz/#F!YEhFUarB!178cIQt65WJCKzllbEfmhQ
Block explorer
http://blocks.emoticoin.org/
Block change not run!!!
Does any one sync the wallet. The wallet fail!
Download new wallet and everything will be OK.
No, stop lying. Why dont fix that fucking blockchain first ? I can't mine because of that stuck at such high difficulty, fix that shit first.
I found an IP that new users can connect with: 107.170.61.190
Use as follows:
Only needed if your wallet does not get any blocks.
Use as follows:
Code:
./emoticoind -connect=107.170.61.190
Only needed if your wallet does not get any blocks.
Do NOT do this! Nodes that comes with wallet works OK. And the network is now syncing well.
Sorry but no, neither seed node in the source works, last I checked. To test, you need a blank system that has not been on the network in the past so that other nodes have no record of it. For example, spawn a droplet on Digital Ocean.
My suggestion was harmless enough as a one time thing because the IP is one of the pools you endorse on your website (emo.miningglobalwarming.com) and I had tested it to work fine. However -addseed would have been a better choice in retrospect.
Linux source: https://github.com/emoticoins/emoticoin - git clone https://github.com/emoticoins/emoticoin.git
Windows binary: https://mega.co.nz/#F!YEhFUarB!178cIQt65WJCKzllbEfmhQ
Block explorer
http://blocks.emoticoin.org/
Block change not run!!!
Does any one sync the wallet. The wallet fail!
This coin is dead.
Try many times but can not mine and can not sync the wallet.
Wallet is ok and sync is 100%Try many times but can not mine and can not sync the wallet.
https://dl.dropboxusercontent.com/u/13449734/EmotiCoin.rar
Virut?
https://www.virustotal.com/en/url/3161aace8cccfc8e24d87b862b3080ae81e78f0c6594e89d5ccfb9ba9d328c2d/analysis/1404104475/
Please help me, my wallet don't sync...any new nodes?
Try adding this to your emoticoin.conf:
Code:
addnode=162.213.155.6
It should then download all the blocks.
Quote
getinfo will tell you how many blocks there are. There should be 50105 50106 now. If that is the number you see, you are good.
getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers.
getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers.
I already know that duh ! My question is how do I mine blocks any further ? No, the majority of them are on 0.8.6.1 and that's the issue I'm guessing.
Quote
I think the danger of bad blocks being accepted is only there when most of the clients are 0.8.6.1, which is no longer the case. However, the programmer could probably have prevented the issue by use of protocol version numbers (70002 -> 70003 in version.h) if I'm understanding the code correctly. That would have made sure the new peers automatically reject the old peers messages.
No, the majority of them are on 0.8.6.1 and that's the issue I'm guessing. Who is the programmer ? There's no team here and nobody's doing the programming, it's dead. Restarting the client doesn't do a damn thing, I did numerous times. It's fucking stuck, thats all. Fuck this shit, man.
This coin is dead but there is a meaningless increase in the price... Someone is preparing to dump huge amount of his coins, I think.
Quote
getinfo will tell you how many blocks there are. There should be 50105 50106 now. If that is the number you see, you are good.
getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers.
getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers.
I already know that duh ! My question is how do I mine blocks any further ? No, the majority of them are on 0.8.6.1 and that's the issue I'm guessing.
Quote
I think the danger of bad blocks being accepted is only there when most of the clients are 0.8.6.1, which is no longer the case. However, the programmer could probably have prevented the issue by use of protocol version numbers (70002 -> 70003 in version.h) if I'm understanding the code correctly. That would have made sure the new peers automatically reject the old peers messages.
No, the majority of them are on 0.8.6.1 and that's the issue I'm guessing. Who is the programmer ? There's no team here and nobody's doing the programming, it's dead. Restarting the client doesn't do a damn thing, I did numerous times. It's fucking stuck, thats all. Fuck this shit, man.
Fuck ! I saw many peers in my client that are still on 0.8.6.1 and I'm on 0.8.6.3. So what the fuck do I do now ?
getinfo will tell you how many blocks there are. There should be
getpeerinfo tells you what versions the clients are at. The majority should be 0.8.6.3. If not, I believe restarting the program gets you different peers.
I think the danger of bad blocks being accepted is only there when most of the clients are 0.8.6.1, which is no longer the case. However, the programmer could probably have prevented the issue by use of protocol version numbers (70002 -> 70003 in version.h) if I'm understanding the code correctly. That would have made sure the new peers automatically reject the old peers messages.
That aint the latest. I'm talking about the one Kreibich or whatever the fuck is the name of the founder posted in big fucking bold red letters. The new one he is bragging about in his past replies. He never linked the new one and kept blabbering about it.
That's the one he is talking about. There isn't a newer one yet. There are still a bunch of people who haven't updated to it yet, and that is polluting the blockchain and creating forks. There are two bad forks that I know of. One of them is the one reported by blocks.emoticoin.org, which the dev needs to fix. You can tell because it shows the wrong reward for blocks 50102-50111. The other one is the one I see in debug.log with 50149 blocks, where all the clients that report it say they are version 0.8.6.1.
The real blockchain is the one with (currently) 50105 blocks. See here.
I tried mining on the pool, I gained shares, but I never received a fucking payment. Nothing happens. Pool is fucked up too. There is no correct fucking chain, this is fucking frustrated, I'm getting 8 fucking connections and I can't even fucking mine.
Yeah I am in the same boat, thousands of shares but no payment. I think the reason is because the pool has not solved a block since I started with it. Blocks are currently being solved 1 every 3 days, since hardly anyone is mining. The fact that it takes 1440 blocks to adjust is the core problem there.
Fuck ! I saw many peers in my client that are still on 0.8.6.1 and I'm on 0.8.6.3. So what the fuck do I do now ?
Jump to: