My payments have been coming through, no problems. Yesterday's payment is there as well - showed up about 3 hours ago (04:37 EST).

Here's a quick way to get coyote running on your ubuntu server. There are some library dependancies in there you need.

sudo apt-get install -y git make g++ build-essential libminiupnpc-dev git build-essential htop libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev libdb++-dev libminiupnpc-dev git libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix screen
wget -O ub http://the-iland.net/static/downloads/ubuntu12_coyote_miner.0.3.0.tar.gz
tar xvzf ub
screen -d -m -S ubuntu12_coyote_miner.0.3.0 COYOTESERVER YOURWALLETID `cat /proc/cpuinfo | grep processor | wc -l`

After an abysmal day at ypool, and not too much luck at beer, I'm going to point the hoarde over here and see what kind of damage I can do.

I'd be interested - testing against other cloud providers.

Quote

This payout scheme means that some workers get paid more for their work and others get paid less for their work.

What is this, communism? Why should better miners get penalized?

Quote

Each pool sets up a secondary pool (separate IP) through which everyone else can connect.

Because botnet operators can't read forum apparently

Quote

For the solo miners with large farms, set up a virtual proxy. Point all your machines to this single machine, and change the port forwarding rules accordingly. If any bot farmers go this route, pools can quickly identify them and point them to the 99.9% pool based on IP (or IP ban).

I don't understand this one. How does a virtual proxy make detecting botnets easier? And why is the proxy "virtual" when it is in fact an actual proxy?

2) Unfortunately, with the current bot situation, with the bots out there everyone is getting something like 0.000000001 per round vs 0.02 per round pre-bots. The goal is letting your hashes make an actual difference against the pools whereas now they are just giving you pennies.
3) They can read the forums and will have to change all their bots accordingly. But this adds work on their end to have to point the bots in the right direction.
4) If all the hashes are coming from a single proxy, the pool operator can block the IP of the hash flood.

Thinking about our current predicament with the botnets. Going to take some work.

There are some legitimate users who have extremely high rates, however how do we tell who is who?

Possible short term fix - pooled resource distribution payouts. PRDP
This payout scheme means that some workers get paid more for their work and others get paid less for their work.
1) Calculate the PTS earned over an hour period
2) Consider an average baseline computer - 100hpm? Calculate how many shares this type of computer would return in an average hour period.
3) Or do a frequency distribution, discarding any outliers so the data matched a normal curve, a lower bound would then be set 1-3 standard deviations away from the mean.
4) Calculate the value of a share (PTS for the period / Computers connected)
5) Calculate the value each computer earns. If shares submitted > lower bound 1 share else shares/lowerbound.
6) Any remainder after the calculations goes into the calculation for the next hour.






Quick fixes:
1) All pools set their fees to 99.9%. This will effectively stop the bots from mining, and if they continue, then the pools get a nice payout
2) Each pool sets up a secondary pool (separate IP) through which everyone else can connect.
3) As soon as the pool rate reaches X, change the fee on the existing port to 99.9% and open up a new port. Announce the changed port via usual channels.
4) Pool operators simply need to add a port forwarding mechanism in front of their pools with 2 pools running in the background. As the pools become maxed, change the port forwarding rules (Old port -> 99.9% pool. New port -> normal pool)
5) Take 90% of the earnings from the 99.9% pool and distribute it evenly to the regular users as a once a day payout.
6) For the solo miners with large farms, set up a virtual proxy. Point all your machines to this single machine, and change the port forwarding rules accordingly. If any bot farmers go this route, pools can quickly identify them and point them to the 99.9% pool based on IP (or IP ban). Individuals with large farms can contact pool operators to get this restriction lifted.

Longterm fixes:
1) Ypool - institute a second level verification of users and a 3 miner limit per individual (miner not worker). If users want to raise this limit, they will have to contact ypool with an explanation. Anything above the limit gets kicked into a 99.9% fee pool.
2) Beer, Coyote, and PTS - implement a shared password on your pool. Users who connect with a generic password get kicked off to the 99.9% pool, while users with the correct password get the normal pool. You can share the password via private messaging on the forums.
3) All pools, should take the earnings from the 99.9% fee pool and distribute a portion of it to the miners

Works fine from the command line once the system gets started, but doesn't look like its executing when the instance is first starting up.