[UPDATE] added logging information

looks good while doing payouts
```
2014-02-16 17:51:09 - INFO --> Starting Payout...
2014-02-16 17:51:09 - INFO --> Auto Payout Sum: 107.55535194 - Wallet Balance: 35779.26412985 with 4750.003 unconfirmed
2014-02-16 17:51:09 - INFO -->   found 1 queued auto payouts
2014-02-16 17:51:09 - INFO -->     | UserID     | Username                  | Balance              | Address                                  | Threshold            |
2014-02-16 17:51:09 - INFO -->     | 5          | shorty                    | 107.55535194         | MMRFkUnQSMDBQSMBG3QBBaEg4ixSa7ksDm       | 100                  |
2014-02-16 17:51:11 - INFO -->   payout succeeded with RPC TXID: 722fbd25bd02e08516cb49577c0a69f8aa51be6a6867047cb553b29085c238d3
```
[UPDATE] changed logging
Update payouts.php
[UPDATE] add coinname to qrode
[UPDATE] make it uppercase
Merge pull request #1774 from iAmShorty/qrcode-coin

[UPDATE] add coinname to qrcode
[ADDED] Payout Queue Limiter

* [ADDED] LIMIT to getMPQueue and getAPQueue
* [ADDED] Default config payout queue size of 1000 for MP and 1000 for AP
* [UPDATED] Payouts cronjob to use this new default limits

This may help some coins that have tx count issues when doing sendmany.
Other coins can play with the values to find their sweet spot. Run the
payout multiple times in a row to force more transactions of the same
amount.

Fixes #1773 and thanks to @jrwr for the idea!
[CHANGE] 500 default limit
added block validation and account validation scripts
applied seraphers proposed fixes & suggestions
fixed newlines
removed a debug line
[ADDED] TX-DB-ID for payout validation
[FIX] Wrong method call in tickerupdate
Merge pull request #1782 from MPOS/payout-tx-limit

[ADDED] Payout Queue Limiter
Merge pull request #1770 from iAmShorty/realbalance-wrapper

[FIX] return balance from main account
[FIX] Wallet Balance Fix
Merge pull request #1790 from iAmShorty/wallet-balance

[FIX] Wallet Balance Fix
[CHANGED] Parse X-FORWARDED-FOR when supplied

Instead of trusting REMOTE_ADDR we should parse X-FORWARDED-FOR if
supplied. This will properly use the user IP in a multi-LB setup.

Needs testing
[ADDED] Use getCurrentIP on IP check