The options I listed in my first post are still the only options. If you don't want to filter out SD transactions then the default "do nothing" option means that transactions will become very expensive, and small quantities of Bitcoin won't be spendable at all.
Not really.
Just expensive enough so SD is not viable. Say, 0.03 or so. For a moderate quantity it's not expensive. For micropayments, BTC is never going to scale to global scale as to accommodate micropayments. It's simple math really...
I don't think BTC is ready for fees so high. That's going to shut out a lot of commerce, not just SD.
It's going to force the evolution that will need to happen sooner or later anyway.
Ripple or whatever other overlay system is required for micropayments. Free transactions in the blockchain are not going to last too long.
Exactly, and i just hope the devs are intelligent enough not to try to 'fix' that problem by making the blocksize much larger. At least not untill everyone really got 10x faster/bigger CPU/HD/Internet compared to today.
Everyone should be able to run a full node through slow broadband internet (or Tor).
I don't believe in full nodes anymore after the last chain split. It's clear that many people don't understand the responsibility involved with running a full node rather than an SPV or a FAN node. Full nodes need to be upgraded as soon as possible, or the network will break like it did yesterday.
Just like mining is no longer a business one can get in with their GPU or CPU, I feel that full nodes should be moved out of the hands of the ignorant consumer and even the average merchant.
I would prefer a Bitcoin client that offered the user 5 types of nodes:
Supernodes, that run two or more full nodes to ensure consistency. Should be upgraded ASAP, and uses the most resources but also provides the most security.
Full nodes, the current default for Bitcoin-QT. Should be upgraded ASAP. Uses a lot of resources for good security.
FAN nodes, which are no yet implemented AFAIK. Can be left at an older version. Uses a lot of resources for good security, but not as good as a full node.
SPV nodes, which download and verify only headers. Can be left at an older version. Light on resources for adequate security.
Server nodes, which use a server to communicate transactions. Can be left at an older version. Very light on resources for acceptable security.