Yes, p2pool users can immediately make use of the patch like this.

There are things in the works to make things easier, like the payment protocol and BIP32.
As I said, it would have been nice if these matured before we phased out address reuse, but it seems we don't have that kind of convenience.

Reserved (for pool position list/summary, etc).

Pool	Patch/Position
BTCGuild	Waiting until threat materialises more.
Eligius	unique_spk_mempool

Addresses have always been considered single-time-use since Satoshi released the whitepaper.
While the community has tolerated reuse for things like donation addresses due to lack of convenient alternatives, it looks like the time is here early that this needs to stop.
I had hoped to defer anything in this area until wide deployment of the payment protocol (which should make such things unnecessary), but our hands¹ are perhaps² being forced³ to act sooner⁴.

I am hereby announcing the first release of a the first patch for miners to filter address reuse:
unique_spk_mempool for bitcoind 0.8.5
For now, since this is still somewhat common, this just deprioritises it to one reuse per block.
If I have time, I plan to write patches to be more and less aggressive that miners can choose between (or maybe others will beat me to it!).

If you want to support this move, encourage your favourite mining pool to adopt this or a similar policy change, or use a decentralised pool that lets you apply it yourself.

In collaboration with wizkid057, the Eligius mining pool (15% of total network hashing) is now the first to deploy this change on an experimental basis.

Armory 0.89.99.14-testing supports Bitcoin-Qt-compatible message signing, so Armory users can use My Eligius and similar functionality

chainminer isn't compatible with standard getwork either, so BFGMiner's proxy won't work with it.
(it always rolls ntime, even when this functionality is not enabled)

v1 M-boards can be fried if the software doesn't compensate.
I don't make any effort to compensate in BFGMiner.
Nobody has tested it, but I cannot recommend this combination.
Do so at your own risk...

Side note: I've never had problems with chainminer on Eligius... (via stratum proxy of course) O.o

Because everyone else knew it was obvious, and didn't need to be pointed out?

I'm sure there's a thread you can argue this in, but that's not the topic here.
Frankly, that coloured coins have this problem is obvious, so arguing over who "predicted" it first is a complete waste of time.
I expect Ron will probably delete your trolling (and my responses to it) when he gets back, so save your time and make a new thread.

This thread isn't about who predicted it first, it's about scalability.

If 100% of bitcoin users migrated to Mastercoin and used it the same way, would it produce more load on the blockchain, less, or the same?
If more, why?

It is, hence the solo mining section of README.

They should be, considering mining.eligius.st is just a CNAME for getwork.mining.eligius.st, which is a supported hostname...

Well, it's not quite that simple either.
If miners are behaving responsibly, they will have spam filters in place to avoid mining flood/DDoS transactions such as those going to BetCoin Dice.
There are two ways to filter transactions:
The most obvious way is to reject them from the memorypool. This has the benefit of not using up resources upfront. It also means you will accept any conflicting (eg, double-spending) transaction, no matter how much later it appears. For the miner and Bitcoin network, this is all positive. For BetCoin Dice, it means they are very vulnerable.
The other way, would be to accept it to your memorypool, but blacklist it from mining or relaying. This consumes the miner's resources, and if they don't have a sufficiently large memorypool, could cause them to mine fewer legitimate transactions. But it protects the spammers like BetCoin Dice because the double-spend is once again rejected.
When I ran Eligius, I experimented with both solutions at different times, and decided the former (which is better for Bitcoin and the pool, but bad for the flooder) is likely the more reasonable solution.

But to conclude, if miners are acting in the interests of Bitcoin, it will rationally be rather easy for anyone to double-spend DDoS transactions.

Please use http://luke.dashjr.org/tmp/code/webisect/webisect.php for regressions.

I forgot to update the OpenWrt README... For 3.6, you'll need to change "testing" to "latest"

We now have 3 stages: stable, testing, and latest.

Stable (currently 3.0.x) is "no outstanding regressions from previous release, and probably any bugs found will also affect previous versions too".
Testing (currently 3.5.x) is "only applying bugfixes to make this the next stable"
Latest (currently 3.6.x) is "new code in the works; lolmaybeithascrashing"

That said, 3.5.2 should have had the bigpic fixes too... :/

Did you opkg update?

Yes.

If you compile it...

The endian issues with the BigPictureMining driver should be fixed in 3.5.2+ - do you still have problems on OpenWrt?

NEW VERSION 3.6.0, NOVEMBER 12 2013

3.6 is only pulling in updates from cgminer 3.8.1, notably including the Klondike driver, which I hope to rewrite eventually. Please note that scrypt support is now officially unmaintained since Con has decided to remove it from cgminer. Any interested parties who want to see scrypt remain supported should step up to maintain it sooner rather than later, or I may just remove it at some point. Hashfast and TechnoB⃦it drivers are still planned, but not in this release yet (cgminer's Hashfast driver is not usable for BFGMiner).

Human readable changelog:

• klondike: New driver, just imported from cgminer mostly as-is for now.
• opencl: Support will remain, but it is not compiled by default. Use --enable-opencl to build it.

Full changelog:

• RPC: Bump to 2.2 for Works in POOLS
• Bugfix: klondike: Don't try to free off the stack
• configure: Update klondike checks for libusb
• klondike: Autodetect by VID/PID/Manufacturer, rather than too-short "K16" Product search
• Remove accidentally added ASIC-README
• klondike: Remove noop identify function
• klondike: Replace deprecated statline with temperature and ManageTUI stuff
• --shares should be scaled to diff1 not absolute number of shares
• More README updates.
• Minor README updates.
• sha2 allow external access to some macros and the K array
• klondike: Fixed a math issue when reporting fan speed on the status line.
• Add a get and queue helper work function.
• Reset the work_restart bool after the scanwork loop in case the driver flushes work synchronously.
• Get rid of the stage thread since all work can be asynchronously added now via hash_push anyway.
• Fix for opt_worktime on big endian machines.
• Do get_work in fill_queue without holding other locks.
• Make hash_pop signal the work scheduler each time it waits on the conditional that it should look for more work.
• Remove discarded work from quota used.
• Display works completed in summary and API data.
• Store how many work items are worked on per pool.
• Add the ability to add uint8 and uint16 entities to api data.
• klondike - initialise stat_lock
• klondike - better to unlock locks than to lock them twice
• Remove roundl check and define
• 'llround' is more suitable here than 'roundl'
• klondike - change options to clock and temptarget only
• klondike - fix another uninit dev warning
• klondike - downgrade 'late update' but add an idle detect - and correct error levels
• klondike - fix isc uninit warning
• klondike - drop the device for hotplug if it's unresponsive
• klondike - single 'shutdown' and ensure it happens
• klondike remove SCNu8 - unsupported on windows
• klondike - fix uninitialised dev bug
• Don't attempt to disable curses or print a summary during an app restart to prevent deadlocks.
• klondike - error condition handling
• Modify Makefile to only include opencl related code when configured in.
• Convert opencl to need to be explicitly enabled during build with --enable-opencl
• Implement a cglock_destroy function.
• Implement a rwlock_destroy function.
• Implement a mutex_destroy function.
• Simplify queued hashtable by storing unqueued work separately in a single pointer.
• Add cgminer compatibility macro for ms_tdiff
• klondike rewrite work control
• allow __work_complete() access
• miner.h allow devices to tv_stamp work
• klondike - can only calculate the nonce difference on or after the 2nd nonce
• klondike - correct/reverse min/max stats
• klondike: Remove unnecessary devlock
• klondike - use a link list queue rather than a circular buffer - and add timing stats
• Klondike - increase circular read buffer size
• Klondike - extra zero value and range checking in temp conversion
• klondike - display MHz also
• klondike correct cvtKlnToC() temperature calculation
• klondike - correct 1st reply debug based on define
• klondike - debug dump structured replies
• klondike - avoid division by zero if maxcount is unexpectedly zero
• klondike store and report errorcount and noise
• klondike - fix chipstats api stats buffer overrun with 16 chips
• klondike add new nonecount only once
• klondike - report mh/s based on nonces found + put old estimate into API stats
• klondike use a memcpy
• klondike fix bracket tabs indenting
• klondike: Update code to current git
• Klondike update code to current git
• Add Klondike to README
• Add Klondike to README.ASIC
• Klondike to main directory
• Klondike consistent code spacing
• Klondike update driver code to current git
• klondike: update firmware for 16 chips, add dist files
• klondike: beta final 0.3.0 release
• klondike: updated firmware, IOC method
• klondike: prevent nonces when not state W
• klondike: added driver config option support
• klondike: fixes for 300 MHz, fix K1 parts list
• klondike: update driver, docs
• klondike: update firmware & utils
• klondike: updated cgminer driver for 3.3.1
• klondike: update firmware and driver, create new cgminer fork
• update klondike driver
• klondike: add cgminer driver file as-is

Full changelog (3.5.2):

• README.scrypt: Update to reflect current status of code (unmaintained); remove Con's litecoin donation address (leaving his bitcoin one) since it is unknown if he still accepts donations with litecoin
• Bugfix: minerloop_async: Check the correct _mt_disable_called flag
• bitforce: Allow ZCX response to override Manufacturer string
• Bugfix: RPC: Restore null termination on responses
• Bugfix: configure: We need DLOPEN_FLAGS for lowlevel hid too
• Add additional debug information to help track work through BFGMiner
• README: Update hidapi dependency for HashBuster
• Bugfix: bigpic: Convert device serial and nonces to host endian
• Bugfix: modminer: Ensure devices that fail probe are closed properly
• Bugfix: bitforce: Ensure devices that fail probe are closed properly
• Bugfix: littlefury: Ensure devices that fail probe are closed properly
• Bugfix: bigpic: Ensure devices that fail probe are closed properly
• nanofury: Attempt to be more resilient to problems

Mac/Windows driver: http://www.ftdichip.com/Drivers/VCP.htm
Then, download BFGMiner from the first post and go through the README file.