Topic: [ANN] [EMD] - Emerald Crypto - PoW - Scrypt - low Difficulty - CPU mining - page 52. (Read 96834 times)

I have 250 sitting available right now. I realized I had the old wallet. Do I have to resync the whole block chain

You can try this:

listen=1
daemon=1
server=1
rpcuser=x
rpcpassword=x
rpcallowip=127.0.0.1
port=12127
rpcport=12128
maxconnections=20
addnode=188.134.72.213
addnode=107.170.99.188
addnode=92.238.186.27
addnode=62.44.226.18
addnode=82.169.240.36
addnode=108.8.4.42
addnode=71.9.214.72
addnode=70.180.113.106
addnode=90.64.117.129
addnode=24.102.94.25
addnode=92.59.89.58

But with the network hashrate running at over 1Gh/s, solo mining will be difficult unless you have some extreme hashing power at your disposal.

Announcement should come in 12 to 14 hours from now. It's 5am here now and I'm up working on the intro video along with some other things... Sleep is for the weak... 

I can't get solo mining to work and I didn't receive any of the coins from the blocks when I was mining in a pool to my wallet either.  My conf is below.

testnet=0
listen=1
daemon=1
maxconnections=100
server=1
rpcuser=
rpcpassword=
rpcallowip=10.1.1.*
rpcallowip=192.168.1.*
rpcport=12128
rpcconnect=127.0.0.1
rpcthreads=8
addnode=188.134.72.213
addnode=107.170.99.188
addnode=92.238.186.27
addnode=62.44.226.18
addnode=82.169.240.36
addnode=108.8.4.42
addnode=71.9.214.72
addnode=70.180.113.106
addnode=90.64.117.129
addnode=24.102.94.25
addnode=92.59.89.58

Hi Guys,
when is the BIG PROJECT Z ANNOUNCEMENT?

NP you are welcome

Yeah cheers it was just strange so thanks for confirming they at least have a chance to be on the chain

Hi LongAndShort,
regarding your post below. Coin E was on the right explorer as i mined directly to my EMD wallet there.
currently they have an issue as from about 5 hours ago i stopped getting any coins to my wallet.
i have no clue why. need to open a support ticket.

Thanks for the great support. it is much appreciated.
Regarding Cryptsy - i have also opened a support ticket to update regarding the EMD wallets. I suggest that everyone that is mining or waiting for their coin in Cryptsy will open a support ticket to push them.

Regarding the coin base - i really hope they sort it out as i have been mining there for a few days as well.

If anyone here (pool ops/pool dev) that is interested in opening an additional pool let me know.
i need to know what are the specs.

thanks

I do not have an account at Coins-E, so I have not personally verified it. They responded to me when I first released the update 3 weeks ago and one of the pool ops posted on here a couple of days ago that they were updated; so I assumed that they had it done. It is possible they have lost sync or are having other issues. I will check it out.

Cryptsy, on the other hand, has had the info for the same amount of time plus a support ticket that is now ~17 days old (with numerous updated replies from me) and still have not gotten it done. BitJohn had told me in chat a few days before the fork that it would be done and then they began having multiple issues with their wallet server. Somehow EMD got shuffled to the bottom of the stack. I, personally, have 35K or so EMD that I would like to be in my wallet, rather than on their exchange.

Just before the fork, I put in a request that they stop deposits and withdrawals until they were updated to avoid mixing old chain coins with currency from the new (official) chain. There were some undocumented pools out there that were, and some still are, on the wrong chain. I've managed to locate a few, but there are still several old clients running in the wild that need to be tracked down.

If anyone is aware of a multipool or other unlisted pool that was mining EMD before the fork, let me know or send them a message with a link to this thread or the emeraldcrypto.org website so they can get updated.

The best thing we can do about Cryptsy is to keep asking in their chat when the updated wallet is going to be online. Linking back to the thread, occasionally, probably wouldn't hurt either. If they see there is a demand (and they should have already noticed the uptick in volume and price the past few days), it should make it a priority for them to get the wallet updated and back online.


Coin-base had very little hash at the fork block and somehow ended up on a chain all their own. I messaged them when I noticed it, but it took them a couple of days before they finally re-synced and joined the right chain. They have had the "back-end issues" notification on their pool since that time.

It may take a few days for them to get through the database and get things cleaned up before they start showing blocks on the front end and making payouts again. They've been with Emerald for a long time, so I'm sure your shares are safe and you (and me, too) will be paid out soon. I'll reach out to them and try to get an ETA on when things will be back to normal.

yeah they need to -f their maintenance crons all of the in fact

Emerald_Crypto you are right - me was stupid
forgot to put the conf file in the roaming folder

BTW - are you in touch with the pool owner "http://coin-base.info/emerald/index.php"
No coins are seen there.


thanks for the support

Coins-e is most definitely not on the new fork maybe i'm wrong! Might want to have a chat with them and get them on the right one if they arn't because this isn't showing up in my wallet or on the chain
when i check this THIS explorer.

And for testing sake i have tried the faucet and tried sending coin to coins-e from my wallet and it has showed up on the chain but not at coins-e.


I have sent the necessary support ticket to them requesting they check out this thread properly and the block explorer to confirm they are in-fact using the right chain

First. Make sure you have the latest version (8.3.1) from the OP.

If on the current version, here is a list of nodes that you can add to your config file:

addnode=188.134.72.213
addnode=107.170.99.188
addnode=92.238.186.27
addnode=62.44.226.18
addnode=82.169.240.36
addnode=108.8.4.42
addnode=71.9.214.72
addnode=70.180.113.106
addnode=90.64.117.129
addnode=24.102.94.25
addnode=92.59.89.58

Or there is a sample Emerald.conf file in the OP with the same nodes listed that you can add to your appdata/roaming/Emerald folder (in Windows).

anyone else is suffering from re-syncing the wallet.
i get 0 connections.

Looking forward to the announcement glad i got in when ppl didnt know a couple weeks ago lol i will hold my few thousand EMD

Lots of hashes being spread around the EMD universe today. Net hash currently 1.1 Gh/s... Lot's of new miners out there getting their Emerald!

Speaking of the EMD universe... expansion plans (aka Project Z) announcement tomorrow. Will post here and on Twitter when ready.

Yeah, I've been fooling with it all damned day.. I'm setting up iptables rules to drop the bad nodes.. So far I've seen a digitalcoin and a worldcoin node connected, as well as some others that didn't have any identifying info. I played with the source a little bit and changed it to accept connections from 60001 minimum, but I don't think that had the desired effect since other interfering nodes are showing differently formatted version info. I'm going on fumes as well man, don't feel bad

Anyway, I've just left it alone to try and resync for several hours, using these as my added nodes (threw in the multipool's address as well).
connect=188.134.72.213
connect=107.170.99.188
connect=92.238.186.27
connect=62.44.226.18
connect=70.180.113.106
I thought using "connect" would limit it to only using those nodes to sync, without fetching their connected nodes and connecting with them as well, but I have 20 connections, but now seems to actually be syncing (slowly). Earlier, it'd sync a while, then stop, then load some more and stop, the multipool didn't seem to be suffering though I haven't mined blocks yet to confirm, it has been in sync with the block explorer the entire time. I was kind of suspecting maybe some DDoS mischief going on, but if it is I don't think it's hitting my server directly or my iptables would have been fishy. So IDK.

Ok, before I went on much further I decided to have a better look since I've kinda left it alone the last couple hours.... getpeerinfo is now showing me ONLY 0.8.3.1 clients now, which is strange because I've mixed and matched addnodes, -noirc, connect, etc. for hours and hours and always ended up seeing connected peers that very obviously weren't EMD. I'm nearly brain dead right now so I may just be imagining things, but I'm thinking that some sort of shenanigans may have been afoot, possibly some sort of DDoS or clusterfuck naughty node attack against our blockchain, or just a horrible accident with misbehaving nodes going completely awry. Feel free to tell me I'm wrong, or stupid, or both. I'd definitely recommend for a future version a complete protocol overhaul, paying careful attention to all the bits that'll keep our blockchain from mingling with any others. Some dns seed nodes would definitely be helpful as well as phasing out the old IRC peering stuff (didn't even bother poking my head into the IRC stuff to see if anything was amiss).

I just find it very strange that earlier, no matter what settings I was using, I still ended up with all sorts of crazy nodes connected but all of a sudden I only have current version nodes connected. I deleted the entire blockchain several times and kept getting all kinds of crazy stuff in the log, though I didn't have the presence of mind to snip some of it, I'll definitely hold on to the newest log in case it'll be of any use later on.

So far on the multipool, we're running about 1MH on EMD, got 2 confirmed blocks and no orphans, so that's a good sign. I'll be keeping an eye on it and will have the MPOS pool back up and running as soon as humanly possible, but it's syncing very slowly so not sure if I can stay awake long enough, lol.

Let me know if there's anything I can do to help out, and it shall be done! 

Anyone having issues with naughty nodes, use this to drop all packets to/from bad nodes (make sure you replace the IP in both the input and output rules):

hopefully that will help with the orphans:
Confirmed 32
Orphaned 21

There are still several of the old clients running in the wild. We are trying to contact anyone who maybe working with an old client to get them shut down or updated to the latest version. EMD is 15 months old, so there are a lot of old clients out there on sites who are blissfully unaware that there have been any changes.

And many more changes are coming... for the better!  

I'm constantly checking my peers so that I can update the addnode list in the OP with good peers... Matter of fact, getting ready to do that right now. If anyone notices any nodes that are updated and not in the OP, post them or send a PM and I will get them added.

To pick out good nodes - In the wallet console type: getpeerinfo  Then, in the peer list, look for peers with: "addr": "xxx.xxx.xx.x:12128", "version" : "6002", "subver" : "8.2.1" or "subver" : "8.3.1"

We are working on banning older versions of the client in the next update. I tried in 8.3.1, but could never get the wallet to find any peers. I was running on fumes at the time... Since I have somewhat recovered and regained a bit of my energy (and sanity); after giving the code a fresh look, we should get things ironed out in the next client update.