Coinye [KOI/COYE] You can't kill a gayfish.

[janos666]

coye.pool.pm, are you kidding me? I mined in this pool from the very beginning until it crashed (when the diff was minimal) and I earned less COYE/min than I earned later with a different pool when the diff was at least 16.
Of course, I didn't see what happened because the web interface was offline the whole time. And yes, I can't see if we had a lot of ophans, because that feature is still offline.
But it's strange, to say at least. I think the pool lost a lot of coins during the crash.

[1714468372]

1714468372

[1714468372]

1714468372

[1714468372]

1714468372

[1714468372]

1714468372

[1714468372]

1714468372

[1714468372]

1714468372

[BC-Trader]

coye.pool.pm, are you kidding me? I mined in this pool from the very beginning until it crashed (when the diff was minimal) and I earned less COYE/min than I earned later with a different pool when the diff was at least 16.
Of course, I didn't see what happened because the web interface was offline the whole time. And yes, I can't see if we had a lot of ophans, because that feature is still offline.
But it's strange, to say at least. I think the pool lost a lot of coins during the crash.

coins are never "lost" they just fail to find their way to miners.....often right into a pool operators pocket 

[rednalexa]

Went in to late on this one...

[BC-Trader]

For those having trouble syncing wallet....

I got it to work by adding all these nodes...

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

[zespmiao]

WTS 100k Coye/0.025 btc..

[1024KB]

For those having trouble syncing wallet....

I got it to work by adding all these nodes...

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

also just delete the peers.dat file in your app data folder where your conf file goes. restart the client and you are good to go.

[bmgbmg]

iFacts,

Send my 250K COYE!!!

Just a heads up to everyone, get him to send first until he can confirm this.  He may be scamming everyone 1 LTC at a time.

[AB3Ham]

I think I may have found the source of the problem that's causing a lot of people to have connection issues. I was unable to get my wallet to connect and sync with the network. I opened up TCPview and noticed that the wallet client was trying to open new connections by sending SYNs to nodes, but it wasn't hearing anything back.

The wallet client is set to listen on port 41338. I added a port forward rule in my router to forward port 41338 to my computer and wallah, immediately got 55 connections to the network and synced up. I'm not quite sure why outgoing connections aren't working when behind a router NAT/firewall.

So, for those of you having connection issues, try port forwarding 41338 to the host running the wallet client.

5TvofXcn2GyjmuhJ5xb9wTbxv3V1RHNzfx

[Kennar]

For those having trouble syncing wallet....

I got it to work by adding all these nodes...

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

Awesome. That worked. Thanks! What's your COYE address?

[1024KB]

I think I may have found the source of the problem that's causing a lot of people to have connection issues. I was unable to get my wallet to connect and sync with the network. I opened up TCPview and noticed that the wallet client was trying to open new connections by sending SYNs to nodes, but it wasn't hearing anything back.

The wallet client is set to listen on port 41338. I added a port forward rule in my router to forward port 41338 to my computer and wallah, immediately got 55 connections to the network and synced up. I'm not quite sure why outgoing connections aren't working when behind a router NAT/firewall.

So, for those of you having connection issues, try port forwarding 41338 to the host running the wallet client.

5TvofXcn2GyjmuhJ5xb9wTbxv3V1RHNzfx

or just delete your peers file and your good to go

[AB3Ham]

I think I may have found the source of the problem that's causing a lot of people to have connection issues. I was unable to get my wallet to connect and sync with the network. I opened up TCPview and noticed that the wallet client was trying to open new connections by sending SYNs to nodes, but it wasn't hearing anything back.

The wallet client is set to listen on port 41338. I added a port forward rule in my router to forward port 41338 to my computer and wallah, immediately got 55 connections to the network and synced up. I'm not quite sure why outgoing connections aren't working when behind a router NAT/firewall.

So, for those of you having connection issues, try port forwarding 41338 to the host running the wallet client.

5TvofXcn2GyjmuhJ5xb9wTbxv3V1RHNzfx

or just delete your peers file and your good to go

Believe me, I tried that many times.

[thefatman82]

Does this look like something's wrong?

Round Shares 
Est. Shares 2048 (done: 8814.01%)
Pool Valid 180511
Your Valid 26
Pool Invalid 1936
Your Invalid 0
 
COYE Estimates
Block 96.02359967
Fees 0
Donation 0
Payout 96.02359967
 
Network Info
Difficulty 1
Est Next Difficulty 2.0E-8 (Change in 171 Blocks)
Est. Avg. Time per Block 1193046 hours 28 minutes 16 seconds
Current Block 0

[st4nl3y]

is http://coinyecoin.icyhash.com/ down? did one already ? got some coins there

[rp4prez2008]

250,000 Coinye for sale. Pm offers

[Chris001]

78,000 COINYE for .035 BTC

[mangodream]

1,3 million COYE for sell. Paypal accepted.

[geokilla]

I regret not mining Coinye...

[xtrapool]

http://coye.xtrapool.com/index.php

0% Fee Smiley

Join us now.

[1024KB]

I think I may have found the source of the problem that's causing a lot of people to have connection issues. I was unable to get my wallet to connect and sync with the network. I opened up TCPview and noticed that the wallet client was trying to open new connections by sending SYNs to nodes, but it wasn't hearing anything back.

The wallet client is set to listen on port 41338. I added a port forward rule in my router to forward port 41338 to my computer and wallah, immediately got 55 connections to the network and synced up. I'm not quite sure why outgoing connections aren't working when behind a router NAT/firewall.

So, for those of you having connection issues, try port forwarding 41338 to the host running the wallet client.

5TvofXcn2GyjmuhJ5xb9wTbxv3V1RHNzfx

or just delete your peers file and your good to go

Believe me, I tried that many times.

did you add dedicatedpools seed ?? . I just added that, took out the rest of the peers, deleted peers file and restarted client. Good to go for me.

for the rest just do this

add this to your conf file, delete all else if your pool mining, delete peers.dat  and restart client

rpcuser=youruser
rpcpassword=yourpass
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=72.46.130.53
server=1
daemon=1

5nafP8kKsAbzF6JnnDaCpgpcxn6z4wBGK6 <--- my coinye addy if this helped

[goto2013]

250k for sale

btc / ltc / paypal !!!