FibreOS... So sexy. I think I know what I'm replacing BAMT with on my "screw around with stuff" rig. That requires me actually getting out of my chair though, so when I get around to it... lol Anyways, the pool at http://towedunder.fedaykin.us:100 is back up and running, will be working on stability and recovery stuff today, as well as our own message board. You guys let me know if you need a hand with anything! |
|
|
|
|
Well, give it up to murphy's law....
I crashed the server. As soon as my partner sees, he'll get it back up. Monitoring and auto recover stuff was on the list for tomorrow.
Better call it a night now, going to be another long day tomorrow! >.<;
|
|
|
|
The dev contacted me, I'll be adding Fibre to my multipool at http://towedunder.fedaykin.us:100 this evening! Fee will be 1% and will be rewarding .5% to the most faithful miner! Morning That's excellent news, I look forward to a Fibre multipool, Thanks for your support, anything you need just pm me. Krushang Thanks guys! Mining should be ready to rock and roll.. Starting tomorrow the pool site is going to start getting a makeover, going to add a trollbox and news ticker, and a forum. |
|
|
|
The dev contacted me, I'll be adding Fibre to my multipool at http://towedunder.fedaykin.us:100 this evening! Fee will be 1% and will be rewarding .5% to the most faithful miner! Thank you for supporting this coin! Almost makes me wish I was a miner, but I have no flashlight hat  Not a problem  Sorry for the delay, about to bring Fibre online on the multipool. This is the first Nist5 algo coin I've tinkered with, so hopefully I've got the diff settings set up right. If anyone has any input, please message me! |
|
|
|
The dev contacted me, I'll be adding Fibre to my multipool at http://towedunder.fedaykin.us:100 this evening! Fee will be 1% and will be rewarding .5% to the most faithful miner! |
|
|
|
You guys missed a pool! Available to mine at http://towedunder.fedaykin.us:100Please see the getting started page for more information. Starting tomorrow we'll be doing a promo, selecting 2 miners for a bonus at the end of the promo period! |
|
|
|
|
My partner and I are having issues with private keys not issuing the expected addresses, we generate a public/private keypair to collect pool fees, mining rewards, etc., mined to a certain address for a while but the address won't match up with the private key, importing the same WIF private key into different wallets gives different addresses..
This is a serious problem and my friend is missing a lot of coins, possibly a wallet bug but not 100% sure yet.
|
|
|
|
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. 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): sudo iptables -A OUTPUT -d 104.131.142.198 -j DROP
sudo iptables -A INPUT -d 104.131.142.198 -j DROP
sudo apt-get install iptables-persistent
/etc/init.d/iptables-persistent save |
|
|
|
Here the various conf files, someone can spot any issue?  limecoinx.conf (daemon .conf) rpcallowip=*rpcthreads=10 rpcuser=user rpcpassword=pass rpcport=3950 port=3949 server=1 daemon=1 listen=1 Don't ever do this! RPC username and password can easily be sniffed, especially if you're running off digitalocean or something like that, and with rpcallowip=* it enables any computer on the planet to connect and rob you blind! rpcallowip=127.0.0.1 if the pool software and wallet are on the same server. If you need to be able to connect via RPC from home, also add rpcallowip=your.home.ip.here You can have more than one allowed IP, just don't ever wildcard it! Old thread, I know, but a very important detail. |
|
|
|
I think I've figured out why we're having so many damn orphan blocks, and people's credits getting reversed......
"addr" : "104.131.142.198:7999",
"services" : "00000003",
"lastsend" : 1409971329,
"lastrecv" : 1409971329,
"conntime" : 1409953566,
"version" : 2000000,
"subver" : "/DGC:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 957573,
"banscore" : 0
That's a Digitalcoin node, but apparently emerald thinks its all good.. I'm guessing it's the "peermagic" or PCHstart bits are matching on both coins, allowing them to connect with each other. I'll have a look later on.
Meanwhile, gonna rework a couple things and see if things smooth out!
Many of these old litecoin clones have matching bits. I've noticed many coins that the nodes of other coins show up in their peers lists. One of the things I'm working on for the next major wallet update is to ban other peers from showing up. Probably can't knock them all out, but should be able to block the majority of bad peers including older versions of EMD. I tried to do it in 8.3, but it wouldn't sync properly... I needed to get the new checkpoints out to help get/keep people on the proper chain, so I decided to wait. I will work on it some more and get it included in the next update. Meanwhile things are still moving in the right direction, overall. There have been a couple of hiccups; but most have been ironed out. Some of the multipools have begun the switchover, so mining may be about to get tougher. There is a nice amount of hash on the network now; so that may keep some of them at bay, unless the difficulty drops low. But with the price where it is, it makes it much more profitable to mine at higher difficulties. I'm starting to ramble... Talk soon... I'm so tired I can't even think anymore... Anyway, the multipool's wallet seems ok, but the MPOS pool's wallet keeps mining many orphans in a row.. Tried knocking out all the addnodes and just using the ones supplied in the OP, even just using "connect" with them, keeps happening. I'm doing a complete resync now in hopes that it works itself out. The multi's wallet is running with the supplied addnodes as well as a bunch of addnodes I picked up somewhere, seems to be on the right block and everything looks alright. Don't know if I can stay awake long enough for the wallet to finish sync and put the pool back in operation, lol. If all else fails, try out the multipool at http://multipool.fedaykin.us:100, remember to use the lowest port number for vardiff. |
|
|
|
|
I think I've figured out why we're having so many damn orphan blocks, and people's credits getting reversed......
"addr" : "104.131.142.198:7999",
"services" : "00000003",
"lastsend" : 1409971329,
"lastrecv" : 1409971329,
"conntime" : 1409953566,
"version" : 2000000,
"subver" : "/DGC:2.0.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 957573,
"banscore" : 0
That's a Digitalcoin node, but apparently emerald thinks its all good.. I'm guessing it's the "peermagic" or PCHstart bits are matching on both coins, allowing them to connect with each other. I'll have a look later on.
Meanwhile, gonna rework a couple things and see if things smooth out!
|
|
|
|
Shade has been added to my multipool at http://multipool.fedaykin.us:100 or http://towedunder.fedaykin.us:100 (multipool.fedaykin.us URL may not be propagated yet)!! The site is still under development but is ready to rock and roll for mining! Please use your coin address or visit the mining key page to get yourself a universal mining key (handy if you're mining the switching ports). Please take notice of the port configuration, the LOWEST port number for every coin will be the vardiff port, all others are fixed diff. Vardiff port for Shade is 4021! Happy mining! Thanks for hosting a pool edric! Have added you to the main post. Thank you man! I'm also going to see about cranking you guys out a Mac wallet! Hopefully get it done tonight! |
|
|
|
Ready to rock at http://multipool.fedaykin.us:100 or http://towedunder.fedaykin.us (waiting on DNS to propagate, multipool.fedaykin.us may not resolve to correct host yet). Vardiff port for Dogecoindark is 4011. Please remember that in the port list for every coin, the LOWEST port number will always be vardiff, while the others are fixed diff. Please use your Dogecoindark address to mine with or generate yourself a universal mining key! Happy mining! |
|
|
|
Shade has been added to my multipool at http://multipool.fedaykin.us:100 or http://towedunder.fedaykin.us:100 (multipool.fedaykin.us URL may not be propagated yet)!! The site is still under development but is ready to rock and roll for mining! Please use your coin address or visit the mining key page to get yourself a universal mining key (handy if you're mining the switching ports). Please take notice of the port configuration, the LOWEST port number for every coin will be the vardiff port, all others are fixed diff. Vardiff port for Shade is 4021! Happy mining! |
|
|
|
Give me a bit guys, working on getting a pool up!! It's gonna be on my NOMP Multipool, but moving stuff to a different server real quick. The URL will be http://towedunder.fedaykin.us:100, you'll need to either mine using your wallet address, or visit http://towedunder.fedaykin.us:100/mining_key and generate a key, use the public key to mine with, keep the private key secret! Each coin is able to be individually mined, with several stratum ports available for those who have grouchy miners. The lowest port number for each listed coin will be the vardiff port, all the rest are fixed-difficulty. Once I merge some of my changes, it'll be more self-explanatory and user friendly. |
|
|
|
|
Hey guys, just thought I'd drop a line because I'm sure you're all wondering just what the hell I'm doing! Ciocgun messaged me a couple of times as well, just to let me know ya'll are still here! The pool isn't doing well at all, I was going to transfer all the coins to a fresh wallet file to see if it was all the transactions clogging it up, but found I couldn't transfer more than a million or two coins at a time, so ditched that.
Anyways, I've tried a few different things, hoping for an easy fix but to no avail. I thought it may have been related to the maximum block size (in KB) but even after upping that and adjusting a few things and endlessly recompiling and testing, same crap. The pool isn't doing very well at all, since the wallet cannot payout if your balance is higher than a couple million, but the wallet just stops running a few times a day. Good news, though. I'm a good 2/3 of the way through porting it all to the newest Dogecoin codebase (with latest protocol). I apologize for it taking so long but the pool business hasn't been so lucrative lately so I've been taking whatever side jobs I can as well as working part time here in town, though I do have some pretty big stuff coming up around the corner, I'm hurting for money now. There's been some pool issues that ended up costing me my savings in order to keep things running, plus these damn high summer power bills. So, right now I'm going to swallow my pride and hold up the "will code for food" sign! Seriously, though, If anyone feels like making a small donation, your old pal Edric would gladly accept. . .
But, Birdcoin is going to be next out the door, I'm pretty sure the new codebase is going to fix our problems, I'm just kicking myself for not doing that in the first place and trying to fix the old pile of crap code instead. And I promise as soon as things are running again, the pool will be just as it was before, alive and kicking, as well as paying! Noticed that Bird is still trading on a couple exchanges, with actual buy support, so that's promising.
You guys stay tuned afterwards, because I'll be launching some more pools in the near future, both my own and with a partner as well, with our own autoexchange system, as well as cooking up other types of services, some that should prove to be unique and interesting. Also, I'll be doing some comprehensive video tutorials on cryptocoin related programming, pool setup and administration, troubleshooting, both MPOS and NOMP, as well as working on my own custom pool management software for NOMP and MPOS for busy or inexperienced pool admins. Most of it done in the spirit of open source, and will be free, of course, but definitely appreciate donations!
Anyway, you guys are a patient bunch, and sorry I'm taking so long. I swear I'm not just sitting on my butt doing nothing, but trying to keep my head above water and stay alive. Also have reunited with my wife and trying to make things work.. Wives cost money too >.<;
I swore I wasn't coming back without binaries, darn it.. Next time...
|
|
|
|
Payout issues at http://carbon.fedaykin.us have been fixed. There were some payouts that didn't get processed properly so I sent those manually. Due to this, the transaction ledger on the site will not show a TXID. Anyone who was affected please check your wallets, let me know if you have issues. If needed I'll go back and pull up the TXID's for the manual transactions I appreciate everyone's patience and thanks for mining Fedaykin's Carbon Pool! |
|
|
|
|
Show Posts
