Good lord, will anybody be able to test the final code more than, say, two days before it's supposed to go live? Yet another reason marketers have no business setting these ridiculous deadlines in the first place. Doesn't anybody remember how people auto-scanned transactions when the Android RNG bug meant you could brute force coins into any address you wanted? I suppose the 2X people would say that somebody setting up a server that drains BTC addresses whenever a 2X transaction goes out is a feature.

In any event, on the off chance that the fork goes through and is actually used, I suppose this opens up an interesting question for Armory. Should Armory enforce the opt-in (if it gets added, which I suppose will happen at the last minute), and explicitly require users to opt out? My initial thought is that the stakes are too high to risk people getting burned, especially considering how...challenging it is to communicate instructions to some Armory users. But, I'm open to ideas.