[resend, sorry gavin] I think these ideas all make a ton of sense, some have been floating around for a while in various forms but it's good to draw them together coherently.
> o Fill up the "free" space (if any) with the highest-priority > transactions, where priority is a function of transaction size, age of > inputs, number of bitcoins... and ratio of inputs to outputs (to > encourage combining inputs so more pruning is possible). Is more incentive needed? If you have tons of tiny outputs you already have incentives to merge them because otherwise your txns will become large and the fees needed to overcome the DoS limits and gain priority will rise. The code to do it is a bit irritating as you really want to de-frag wallets in the background when the user is not likely to need the outputs quickly, and I suspect over time transaction volumes will become diurnal so it'd be cheaper to do that at night time, but it's all possible. > But that won't work for newly started clients that haven't seen a lot > of transactions enter/exit the memory pool Peers could provide first-seen timestamps for transactions when announced or when downloaded with Jeffs proposed command, but the timestamps are not necessarily trustable. Not sure if that'd open up new attacks. > or SPV clients that can't lookup transaction inputs SPV clients can do it by getdata-ing on the relevant inputs, but it's very bandwidth intensive just to guesstimate fees. > Maybe each client developer runs a "fee policy server" That's reasonable. I don't believe this case is worth worrying about right now. For the common cases of a) Customer buys from merchant (runs full node) b) Trusted person sends money to trusting person (does not need confirms) it wouldn't matter after the changes to the block creation code. It's only really an issue when a user running an SPV client wishes to accept money from somebody they do not trust, and they want it to confirm quick-ish (within an hour), but can tolerate delays up to that. I think this is likely to be rare. Much more common is that you want to accept the payment immediately, which is an oft discussed but different problem. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
