Topic: Coinye [KOI/COYE] You can't kill a gayfish. - page 289. (Read 715941 times)
sell 1.2m coye 1 btc or pm me with offers
Got 750k and I'm selling 250k COYE. PM me offers in LTC/BTC or post here!
Sold to Jharkness user, multiple smooth transcations. Should I hold 500k ?
any working nodes now? wallet stopped syncing
My conf file this work for me
addnode=37.187.93.104
addnode=23.253.71.20
addnode=94.242.254.73
addnode=24.20.187.178
addnode=37.59.31.34
addnode=37.59.54.28
addnode=62.212.72.31
addnode=198.245.63.111
addnode=199.241.191.148
addnode=72.46.130.53
addnode=23.253.71.20:41338
addnode=148.251.11.238:41338
addnode=162.220.61.78:41338
addnode=188.115.182.34:41338
addnode=50.152.213.185:41338
server=1
daemon=1
listen=1
maxconnections=900
5ShEtDXZZ2VHQxVbahfhgHp77FPc6PWsLm
And if that doesn't work try portforwarding in your router on port 41338 and your computer networkadres. Works for me and have now 78 connections.
selling 5 Million Coinyes for 3 BTC or 100 LTC
Well, apparently my 500k coinye was stolen from the bitember pool. Was just about to cash out when I saw a manual payout to some unknown address. Still not sure if I was hacked or if they were. Pretty depressed... was excited to finally make a small profit off a coin release.
Taking charity :/
5nLqndbnH8sb1fnGJuHv3k9ehpSKBTNZ85
(Anyone else have a similar problem on bitember?)
Taking charity :/
5nLqndbnH8sb1fnGJuHv3k9ehpSKBTNZ85
(Anyone else have a similar problem on bitember?)
1. are you on a windoz pc?
2. did you scan you PC for malware, virus?
any working nodes now? wallet stopped syncing
My conf file this work for me
addnode=37.187.93.104
addnode=23.253.71.20
addnode=94.242.254.73
addnode=24.20.187.178
addnode=37.59.31.34
addnode=37.59.54.28
addnode=62.212.72.31
addnode=198.245.63.111
addnode=199.241.191.148
addnode=72.46.130.53
addnode=23.253.71.20:41338
addnode=148.251.11.238:41338
addnode=162.220.61.78:41338
addnode=188.115.182.34:41338
addnode=50.152.213.185:41338
server=1
daemon=1
listen=1
maxconnections=900
5ShEtDXZZ2VHQxVbahfhgHp77FPc6PWsLm
PM me your offer for COYE to BTC/LTC!! 
any working nodes now? wallet stopped syncing
addnode=37.187.93.104
addnode=23.253.71.20
addnode=94.242.254.73
addnode=24.20.187.178
addnode=37.59.31.34
addnode=37.59.54.28
addnode=62.212.72.31
addnode=teamcoinye.com
addnode=198.245.63.111
addnode=72.46.130.53
addnode=108.168.55.170
addnode=94.242.254.73
addnode=199.241.191.148
addnode=37.187.93.104
addnode=23.253.71.20
addnode=94.242.254.73
addnode=24.20.187.178
addnode=37.59.31.34
addnode=37.59.54.28
addnode=62.212.72.31
Sooo... How much BTC or LTC for 1126 COYEs?
I have a mean machine that's doing 11 khps
I have a mean machine that's doing 11 khps
any working nodes now? wallet stopped syncing
Here's what I think happens with these popular, highly anticipated coins with lots of Mhash at multiple pools.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
I think you're right
I would agree, but we were finding absolutely no blocks in that time. The pool did find stale shares which were reported on the frontend, and in between the 1000% rounds there were brief 2-3 blocks around 30-300%
So, the front end was updating like it should, matching with the shares I was submitting and the shares of the pool. No blocks though...
I wonder if some of the smaller pools were constantly playing catchup with new blocks found by larger pools and by the time their participants completed all work on a block, that block was already stale. It would be like a constant live-lock. Again, another degenerate symptom of too fast block generation and insufficient blockchain syncing time.
Maybe? We will likely never know the real cause. I do run --no-submit-stale on some of my rigs, it's possible they just never got sent to the pool.
But at the time icyhash was one of the few pools up, I'd wager that it was one of the largest. I didn't take any screenshots or anything, and I wasn't paying close attention, but I think the pool hashrate got over 5gh/s for a time.
After the pool owners actions, I wouldn't mine for him again. I did manage to get coins from him, but that's because I know the wallet doesn't need to sync to get a payout address (tip for next time! Keep the wallet.dat)
We never went past 750MH/s. I was waiting for it to hit 1GH/s. Would you like the block log or anything you can use to try and figure out what happened?
I see, I do remember the total network being over 11gh/s so maybe that had something to do with it.
I'm not pro enough to do anything with any logs, but I imagine someone on this forum can. Might be a good thing to figure out since your dead set on more pools.
I wish it was 11 GH/s. I was jumping up and down when I saw 750 MH/s. Mining pools are a lot of fun, that's why I'm dead set. It's not really about making a profit... It's just a fun hobby
10 minute offer: 105137.98052827 COYE for 0.1 BTC
First private message or highest offer wins. But I have to go to bad soon, that's why it's a limited time offer.
First private message or highest offer wins. But I have to go to bad soon, that's why it's a limited time offer.
I waste lots of time and got few coins at bitember.com
please donate some coins ,thank you very much
5fRBP9FjtNzinCEoQDL1RTm9szzbM27xWn
please donate some coins ,thank you very much
5fRBP9FjtNzinCEoQDL1RTm9szzbM27xWn
Here's what I think happens with these popular, highly anticipated coins with lots of Mhash at multiple pools.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
I think you're right
I would agree, but we were finding absolutely no blocks in that time. The pool did find stale shares which were reported on the frontend, and in between the 1000% rounds there were brief 2-3 blocks around 30-300%
So, the front end was updating like it should, matching with the shares I was submitting and the shares of the pool. No blocks though...
I wonder if some of the smaller pools were constantly playing catchup with new blocks found by larger pools and by the time their participants completed all work on a block, that block was already stale. It would be like a constant live-lock. Again, another degenerate symptom of too fast block generation and insufficient blockchain syncing time.
Maybe? We will likely never know the real cause. I do run --no-submit-stale on some of my rigs, it's possible they just never got sent to the pool.
But at the time icyhash was one of the few pools up, I'd wager that it was one of the largest. I didn't take any screenshots or anything, and I wasn't paying close attention, but I think the pool hashrate got over 5gh/s for a time.
After the pool owners actions, I wouldn't mine for him again. I did manage to get coins from him, but that's because I know the wallet doesn't need to sync to get a payout address (tip for next time! Keep the wallet.dat)
We never went past 750MH/s. I was waiting for it to hit 1GH/s. Would you like the block log or anything you can use to try and figure out what happened?
I see, I do remember the total network being over 11gh/s so maybe that had something to do with it.
I'm not pro enough to do anything with any logs, but I imagine someone on this forum can. Might be a good thing to figure out since your dead set on more pools.
They did some front end maintenance earlier, but they've been rock solid since I started using them, and the devs are in the IRC.
<< REPOSTING >> to make sure everyone has seen this and gets their coins paid out in full
ICYHASH USERS
I am utterly disgusted by the communities reaction to the problems we faced last night. I am not a scammer, never was a scammer, and never will be a scammer. I spent countless hours yesterday into the wee hours of the night to ensure this pool was online and fully operational. To see such a reaction out of the effort I put forth is really upsetting. However, out of the 814 users on my server, only a small handful were acting like dicks. I can't hold the honest users accountable for a few people's stupid actions.
As far as the 1000% block or whatever... I have been building mining for months. I spent the last week learning how to set everything up as far as running pools goes. I'm not overly experienced with it like some of you are. I haven't the slightest clue why no blocks were found for an hour. I do know that the pool was having some problems that were ALL corrected later in the night. If that work was lost due to these problems, I apologize. There is nothing further I can say or explain. I assure you there was no siphoning, coin steeling, putting hashes somewhere else, etc.
What Happened... My server is a dedicated box with 24 physical cores and 128GB of ram.
1) Even with all that power, the MySQL instance (configured correct, I'm a DBA mind you) for php front-end totally killed the CPU. These errors were corrected by commenting out and reworking some of the php-mpos code.
2) Closer to the end of the night, a second issue arose where the stratum instance stopped accepting incoming connections. This issue was transparent to me at first because my miner was purring away. I didn't realize until I investigated the debug logs that most people's connections were being rejected. Once I adjusted the maximum open files limit on the server and restarted stratum, this too was resolved. The server worked fine for 10 hours after.
3) Some dumbfuck thought it would be funny this morning to DDOS the site. At this point, I had no choice but to power off the server and null route the IPs affected.
NUMBER THREE is the reason why you cannot withdraw your coins. It's not because I'm a scammer. IT'S BECAUSE ONE OF YOUR PEERS FOUND IT FUNNY TO KNOCK IT OFFLINE.
To claim your coins, please PM me with IN THE NEXT 24 HOURS
1) Your IP address used on registration
2) Your username
3) Your wallet address
If you fail to mention any of these, you will not receive your coins. I will not reply to your PM. Keep an eye on your wallet.
What's Next:
I will be rebuilding these servers from scratch with proper DDOS protection and open more pools. This was one huge learning experience.
AGAIN, I ASK YOU... PLEASE STOP THROWING AROUND THE SCAM RUMORS. I'm probably one of the nicest system admins you will ever meet regardless of what some of you will think.
ICYHASH USERS
I am utterly disgusted by the communities reaction to the problems we faced last night. I am not a scammer, never was a scammer, and never will be a scammer. I spent countless hours yesterday into the wee hours of the night to ensure this pool was online and fully operational. To see such a reaction out of the effort I put forth is really upsetting. However, out of the 814 users on my server, only a small handful were acting like dicks. I can't hold the honest users accountable for a few people's stupid actions.
As far as the 1000% block or whatever... I have been building mining for months. I spent the last week learning how to set everything up as far as running pools goes. I'm not overly experienced with it like some of you are. I haven't the slightest clue why no blocks were found for an hour. I do know that the pool was having some problems that were ALL corrected later in the night. If that work was lost due to these problems, I apologize. There is nothing further I can say or explain. I assure you there was no siphoning, coin steeling, putting hashes somewhere else, etc.
What Happened... My server is a dedicated box with 24 physical cores and 128GB of ram.
1) Even with all that power, the MySQL instance (configured correct, I'm a DBA mind you) for php front-end totally killed the CPU. These errors were corrected by commenting out and reworking some of the php-mpos code.
2) Closer to the end of the night, a second issue arose where the stratum instance stopped accepting incoming connections. This issue was transparent to me at first because my miner was purring away. I didn't realize until I investigated the debug logs that most people's connections were being rejected. Once I adjusted the maximum open files limit on the server and restarted stratum, this too was resolved. The server worked fine for 10 hours after.
3) Some dumbfuck thought it would be funny this morning to DDOS the site. At this point, I had no choice but to power off the server and null route the IPs affected.
NUMBER THREE is the reason why you cannot withdraw your coins. It's not because I'm a scammer. IT'S BECAUSE ONE OF YOUR PEERS FOUND IT FUNNY TO KNOCK IT OFFLINE.
To claim your coins, please PM me with IN THE NEXT 24 HOURS
1) Your IP address used on registration
2) Your username
3) Your wallet address
If you fail to mention any of these, you will not receive your coins. I will not reply to your PM. Keep an eye on your wallet.
What's Next:
I will be rebuilding these servers from scratch with proper DDOS protection and open more pools. This was one huge learning experience.
AGAIN, I ASK YOU... PLEASE STOP THROWING AROUND THE SCAM RUMORS. I'm probably one of the nicest system admins you will ever meet regardless of what some of you will think.
He just sent me my coins. He's legit!
Same +1 for legit.
Sorry about the troubles you had spork
<< REPOSTING >> to make sure everyone has seen this and gets their coins paid out in full
ICYHASH USERS
I am utterly disgusted by the communities reaction to the problems we faced last night. I am not a scammer, never was a scammer, and never will be a scammer. I spent countless hours yesterday into the wee hours of the night to ensure this pool was online and fully operational. To see such a reaction out of the effort I put forth is really upsetting. However, out of the 814 users on my server, only a small handful were acting like dicks. I can't hold the honest users accountable for a few people's stupid actions.
As far as the 1000% block or whatever... I have been building mining for months. I spent the last week learning how to set everything up as far as running pools goes. I'm not overly experienced with it like some of you are. I haven't the slightest clue why no blocks were found for an hour. I do know that the pool was having some problems that were ALL corrected later in the night. If that work was lost due to these problems, I apologize. There is nothing further I can say or explain. I assure you there was no siphoning, coin steeling, putting hashes somewhere else, etc.
What Happened... My server is a dedicated box with 24 physical cores and 128GB of ram.
1) Even with all that power, the MySQL instance (configured correct, I'm a DBA mind you) for php front-end totally killed the CPU. These errors were corrected by commenting out and reworking some of the php-mpos code.
2) Closer to the end of the night, a second issue arose where the stratum instance stopped accepting incoming connections. This issue was transparent to me at first because my miner was purring away. I didn't realize until I investigated the debug logs that most people's connections were being rejected. Once I adjusted the maximum open files limit on the server and restarted stratum, this too was resolved. The server worked fine for 10 hours after.
3) Some dumbfuck thought it would be funny this morning to DDOS the site. At this point, I had no choice but to power off the server and null route the IPs affected.
NUMBER THREE is the reason why you cannot withdraw your coins. It's not because I'm a scammer. IT'S BECAUSE ONE OF YOUR PEERS FOUND IT FUNNY TO KNOCK IT OFFLINE.
To claim your coins, please PM me with IN THE NEXT 24 HOURS
1) Your IP address used on registration
2) Your username
3) Your wallet address
If you fail to mention any of these, you will not receive your coins. I will not reply to your PM. Keep an eye on your wallet.
What's Next:
I will be rebuilding these servers from scratch with proper DDOS protection and open more pools. This was one huge learning experience.
AGAIN, I ASK YOU... PLEASE STOP THROWING AROUND THE SCAM RUMORS. I'm probably one of the nicest system admins you will ever meet regardless of what some of you will think.
ICYHASH USERS
I am utterly disgusted by the communities reaction to the problems we faced last night. I am not a scammer, never was a scammer, and never will be a scammer. I spent countless hours yesterday into the wee hours of the night to ensure this pool was online and fully operational. To see such a reaction out of the effort I put forth is really upsetting. However, out of the 814 users on my server, only a small handful were acting like dicks. I can't hold the honest users accountable for a few people's stupid actions.
As far as the 1000% block or whatever... I have been building mining for months. I spent the last week learning how to set everything up as far as running pools goes. I'm not overly experienced with it like some of you are. I haven't the slightest clue why no blocks were found for an hour. I do know that the pool was having some problems that were ALL corrected later in the night. If that work was lost due to these problems, I apologize. There is nothing further I can say or explain. I assure you there was no siphoning, coin steeling, putting hashes somewhere else, etc.
What Happened... My server is a dedicated box with 24 physical cores and 128GB of ram.
1) Even with all that power, the MySQL instance (configured correct, I'm a DBA mind you) for php front-end totally killed the CPU. These errors were corrected by commenting out and reworking some of the php-mpos code.
2) Closer to the end of the night, a second issue arose where the stratum instance stopped accepting incoming connections. This issue was transparent to me at first because my miner was purring away. I didn't realize until I investigated the debug logs that most people's connections were being rejected. Once I adjusted the maximum open files limit on the server and restarted stratum, this too was resolved. The server worked fine for 10 hours after.
3) Some dumbfuck thought it would be funny this morning to DDOS the site. At this point, I had no choice but to power off the server and null route the IPs affected.
NUMBER THREE is the reason why you cannot withdraw your coins. It's not because I'm a scammer. IT'S BECAUSE ONE OF YOUR PEERS FOUND IT FUNNY TO KNOCK IT OFFLINE.
To claim your coins, please PM me with IN THE NEXT 24 HOURS
1) Your IP address used on registration
2) Your username
3) Your wallet address
If you fail to mention any of these, you will not receive your coins. I will not reply to your PM. Keep an eye on your wallet.
What's Next:
I will be rebuilding these servers from scratch with proper DDOS protection and open more pools. This was one huge learning experience.
AGAIN, I ASK YOU... PLEASE STOP THROWING AROUND THE SCAM RUMORS. I'm probably one of the nicest system admins you will ever meet regardless of what some of you will think.
He just sent me my coins. He's legit!
Got 750k and I'm selling 250k COYE. PM me offers in LTC/BTC or post here!
I sent you pm
Here's what I think happens with these popular, highly anticipated coins with lots of Mhash at multiple pools.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
Each of the large pools start mining based off of the current block chain. Because the difficulty is so low, block generations are occurring nearly instantly. Meanwhile, the network, users and pools are ddosing each other trying to get connections and updates. Competing block chains don't have enough time to propagate globally before N more blocks are found locally in a pool. So, each local pool has a block chain that could potentially stay longer than the updates that it is seeing from elsewhere. Other smaller pools and users are getting updates from these competing pools and either sticking with the closest/longest or switching back and forth.
As the difficulty goes up and speed of block generation finally goes down, you eventually get a more globally consistent block chain. However, potentially the vast majority of users find that they didn't get on the longest eventual chain and suddenly their coins disappear.
I would say that the solution probably lies in either much better pool communication (even under ddos type conditions) and/or raising the starting difficulty and slowing block generation to a liveable level quickly. If you don't have a globally consistent block chain then these coin launches are going to keep looking bad and anger a lot of participants.
Would love to hear other's thoughts.
I think you're right
I would agree, but we were finding absolutely no blocks in that time. The pool did find stale shares which were reported on the frontend, and in between the 1000% rounds there were brief 2-3 blocks around 30-300%
So, the front end was updating like it should, matching with the shares I was submitting and the shares of the pool. No blocks though...
I wonder if some of the smaller pools were constantly playing catchup with new blocks found by larger pools and by the time their participants completed all work on a block, that block was already stale. It would be like a constant live-lock. Again, another degenerate symptom of too fast block generation and insufficient blockchain syncing time.
Maybe? We will likely never know the real cause. I do run --no-submit-stale on some of my rigs, it's possible they just never got sent to the pool.
But at the time icyhash was one of the few pools up, I'd wager that it was one of the largest. I didn't take any screenshots or anything, and I wasn't paying close attention, but I think the pool hashrate got over 5gh/s for a time.
After the pool owners actions, I wouldn't mine for him again. I did manage to get coins from him, but that's because I know the wallet doesn't need to sync to get a payout address (tip for next time! Keep the wallet.dat)
We never went past 750MH/s. I was waiting for it to hit 1GH/s. Would you like the block log or anything you can use to try and figure out what happened?
Ok my mining issue seems to be related to thread concurrency in combination with the amount of RAM installed... i have multiple pc's, one died, this one only has 1 GB memory
Jump to: