Topic: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink - page 166. (Read 297728 times)
March 26, 2014, 07:47:12 AM
Looks good! 8 is my lucky number. Cool
March 26, 2014, 06:47:23 AM
Hi,
I'm running the site http://www.crypto-coins-table.com.
I have listed your coin already. To provide the full information
for all users you can update the information here:
http://www.crypto-coins-table.com/index.php?var_action=update_coin&coin_id=888
regards
March 26, 2014, 02:46:44 AM
I'm offering a 1 888 block finder bonus right now. It's not much, I know, but I want to be able to give -something- back to the community! Come mine with us!
March 26, 2014, 01:51:21 AM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
see, I knew you would get it
let's Octo the shit out of this, f*** the DDoSersEdit: please update the message on the pool's board, let everybody know they can use both ports for now
Haha, I wish I knew a way to fight back. These DDoS'ing idiots, I don't know if they do it just for the hell of it, or if they're profiting in some fashion. I wouldn't go as far as making accusations, but who knows, could be a scheme by a somewhat morally challenged pool op to bring in more traffic!
Who wants to sign up for my botnet, and kick back? j/k
I'm still learning some of the ins and outs of running pools, and unfortunately DDoS type situations can be by far the most confusing and frustrating. For a little while there I had no idea what was going on. And to think I nearly turned off logging for my stratum server!
yeah there's always a reason or motive for someone to pull DDOS. who knows why but it seems to happen to any good coins taking off.
The kind of talent and resources needed to pull that off could be put to much better use, I would imagine.
On another note, if people who are mining with other pools wouldn't mind taking a second, I would like to know what percentage of rejected (stale) shares they're getting at other pools, in particular pool-wide stale percentages. My pool is at 0.36% rejected shares on average, tomorrow I'm going to play with a few tweaks to see if we can make that number smaller. This is but one of the things that I think about lying in bed, trying to go to sleep. I think I'm just a bit obsessive, I can barely stand to look at my own PC, the case is smashed and deformed, the heatsink stoved in on one side, thanks to my ex.
March 26, 2014, 12:27:47 AM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
see, I knew you would get it
let's Octo the shit out of this, f*** the DDoSersEdit: please update the message on the pool's board, let everybody know they can use both ports for now
Haha, I wish I knew a way to fight back. These DDoS'ing idiots, I don't know if they do it just for the hell of it, or if they're profiting in some fashion. I wouldn't go as far as making accusations, but who knows, could be a scheme by a somewhat morally challenged pool op to bring in more traffic!
Who wants to sign up for my botnet, and kick back? j/k
I'm still learning some of the ins and outs of running pools, and unfortunately DDoS type situations can be by far the most confusing and frustrating. For a little while there I had no idea what was going on. And to think I nearly turned off logging for my stratum server!
yeah there's always a reason or motive for someone to pull DDOS. who knows why but it seems to happen to any good coins taking off.
March 26, 2014, 12:26:21 AM
March 25, 2014, 11:44:45 PM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
see, I knew you would get it
let's Octo the shit out of this, f*** the DDoSersEdit: please update the message on the pool's board, let everybody know they can use both ports for now
Haha, I wish I knew a way to fight back. These DDoS'ing idiots, I don't know if they do it just for the hell of it, or if they're profiting in some fashion. I wouldn't go as far as making accusations, but who knows, could be a scheme by a somewhat morally challenged pool op to bring in more traffic!
Who wants to sign up for my botnet, and kick back? j/k
I'm still learning some of the ins and outs of running pools, and unfortunately DDoS type situations can be by far the most confusing and frustrating. For a little while there I had no idea what was going on. And to think I nearly turned off logging for my stratum server!
March 25, 2014, 10:50:19 PM
^^^
great price!
great price!
March 25, 2014, 08:54:55 PM
March 25, 2014, 08:29:30 PM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Great Work!
March 25, 2014, 07:57:59 PM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
see, I knew you would get it
let's Octo the shit out of this, f*** the DDoSersEdit: please update the message on the pool's board, let everybody know they can use both ports for now
March 25, 2014, 07:51:41 PM
@edric, kickin' it up a notch!
March 25, 2014, 07:50:42 PM
I've messed with some stuff in my iptables, now port 3333 will redirect to 3334 and in case of further attacks on 3333 I can just comment it out, restart service, and bam.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
Edit: and yay, people are reconnecting. I knew it, lots of unattended miners trying to connect.
March 25, 2014, 06:58:42 PM
March 25, 2014, 06:54:51 PM
I am debating switching back to port 3333, but not sure if the attack is still ongoing, and I don't want to find out the hard way. I'm just a little upset for those that haven't reconnected yet, they may be afk or at work or otherwise unable to see that we've changed the port and I can imagine their unattended miners trying in vain to connect.. Really irks me.
Can't you make a PAT rule in the firewall and redirect to 3334 (I'm assuming the protocols can work with NAT/PAT, don't know)?
That way, it it brings problems, you just have to shit the rule down, not reset everything ...
P.S - check PM, please
March 25, 2014, 05:43:19 PM
I am debating switching back to port 3333, but not sure if the attack is still ongoing, and I don't want to find out the hard way. I'm just a little upset for those that haven't reconnected yet, they may be afk or at work or otherwise unable to see that we've changed the port and I can imagine their unattended miners trying in vain to connect.. Really irks me.
Can't you make a PAT rule in the firewall and redirect to 3334 (I'm assuming the protocols can work with NAT/PAT, don't know)?
That way, it it brings problems, you just have to shit the rule down, not reset everything ...
P.S - check PM, please
March 25, 2014, 05:39:51 PM
Everything seems to be running smooth now as I believe all attacks have faded out. Unfortunately, I have been out of pocket all day and just received a voice mail from one of our guys to let me know that several OctoCoin pools were being attacked. I'm on my way to the office right now to see what we can do on our end but I believe things are under control at this point. It appears the primary issue was the nodes getting hit with an attack. We have small miners at most of the pools and the only pool that never dropped out was sfo.fusionhash.com:3338 - our miner at edric's pool and our miner pointed at sfo8.fusionhash.com:3338 (the primary FusionHash stratum server) both lost connection. We also run a private pool in our office and even that was throwing errors and dropping most shares.
Things seem to have calmed down but we will keep an eye on it. We have some fresh nodes on standby that we will post if another attack hits. Very strange timing - like edric said, it was probably just some kids screwing around. I did receive an email from FusionHash confirming that no coins were lost in the attack(s) and their database server was not affected. I want to thank edric for all of his effort - this guy continues to go the extra mile. Obviously FusionHash has been great as well but I have asked FusionHash to post status updates here from now on instead of just emailing us to help keep everybody informed. If edric hadn't been around, many people here would have been in the dark on the entire situation. Also, this is another great example of why you should always have a number of backup pools in place on your miners (personally, I usually round my backup list out with solo-mining.)
We have had a general OctoCoin news update planned for tomorrow and everything remains on schedule.
Things seem to have calmed down but we will keep an eye on it. We have some fresh nodes on standby that we will post if another attack hits. Very strange timing - like edric said, it was probably just some kids screwing around. I did receive an email from FusionHash confirming that no coins were lost in the attack(s) and their database server was not affected. I want to thank edric for all of his effort - this guy continues to go the extra mile. Obviously FusionHash has been great as well but I have asked FusionHash to post status updates here from now on instead of just emailing us to help keep everybody informed. If edric hadn't been around, many people here would have been in the dark on the entire situation. Also, this is another great example of why you should always have a number of backup pools in place on your miners (personally, I usually round my backup list out with solo-mining.)
We have had a general OctoCoin news update planned for tomorrow and everything remains on schedule.
Thanks for the update, good sir!
I am debating switching back to port 3333, but not sure if the attack is still ongoing, and I don't want to find out the hard way. I'm just a little upset for those that haven't reconnected yet, they may be afk or at work or otherwise unable to see that we've changed the port and I can imagine their unattended miners trying in vain to connect.. Really irks me.
March 25, 2014, 05:28:31 PM
Everything seems to be running smooth now as I believe all attacks have faded out. Unfortunately, I have been out of pocket all day and just received a voice mail from one of our guys to let me know that several OctoCoin pools were being attacked. I'm on my way to the office right now to see what we can do on our end but I believe things are under control at this point. It appears the primary issue was the nodes getting hit with an attack. We have small miners at most of the pools and the only pool that never dropped out was sfo.fusionhash.com:3338 - our miner at edric's pool and our miner pointed at sfo8.fusionhash.com:3338 (the primary FusionHash stratum server) both lost connection. We also run a private pool in our office and even that was throwing errors and dropping most shares.
Things seem to have calmed down but we will keep an eye on it. We have some fresh nodes on standby that we will post if another attack hits. Very strange timing - like edric said, it was probably just some kids screwing around. I did receive an email from FusionHash confirming that no coins were lost in the attack(s) and their database server was not affected. I want to thank edric for all of his effort - this guy continues to go the extra mile. Obviously FusionHash has been great as well but I have asked FusionHash to post status updates here from now on instead of just emailing us to help keep everybody informed. If edric hadn't been around, many people here would have been in the dark on the entire situation. Also, this is another great example of why you should always have a number of backup pools in place on your miners (personally, I usually round my backup list out with solo-mining.)
We have had a general OctoCoin news update planned for tomorrow and everything remains on schedule.
Things seem to have calmed down but we will keep an eye on it. We have some fresh nodes on standby that we will post if another attack hits. Very strange timing - like edric said, it was probably just some kids screwing around. I did receive an email from FusionHash confirming that no coins were lost in the attack(s) and their database server was not affected. I want to thank edric for all of his effort - this guy continues to go the extra mile. Obviously FusionHash has been great as well but I have asked FusionHash to post status updates here from now on instead of just emailing us to help keep everybody informed. If edric hadn't been around, many people here would have been in the dark on the entire situation. Also, this is another great example of why you should always have a number of backup pools in place on your miners (personally, I usually round my backup list out with solo-mining.)
We have had a general OctoCoin news update planned for tomorrow and everything remains on schedule.
I knew it!!!!!!
Bravooooo
Good joob
The faith died last!!!
Viva 888
March 25, 2014, 04:25:27 PM
Just a small reminder that the P2Pool is still up, and running (only has ~1.3 MH/s right now). Feel free to jump on.
(see the P2Pool node scanner in the OP)
(see the P2Pool node scanner in the OP)
March 25, 2014, 04:22:44 PM
Man something is really strange with this coin, look at the net hashrate.
First this DDos Shit and now a hashrate we havn't seen for days...
First this DDos Shit and now a hashrate we havn't seen for days...
I believe the net hash rate is partially due to a ton of completed shares hitting rapidly after the brief outage (some valid and surely some stale) - it will likely level out. That being said, mining profitability is so low on most of the other scrypt coins right now that a lot of the mine-to-dump people and multipools are now starting to hit OctoCoin as it offers the best ROI (depending on difficulty, of course). Obviously this isn't great for the current value, but these miners/multipools should drop off as the difficulty rises and everything levels out - like any coin, it's just part of the equation. We're still in the early stages of OctoCoin and we're in a bear market - if you can afford to mine, buy, and hold there will likely never be a better time to do so. Getting listed at CoinMarketCap was likely a factor in this increased exposure.
Jump to: