回复：我在测试网络上做的一些测试及我的发现。
原始发布页
打开来源页面查看 1 个交叉存档
引用自：ByteCoin 于 2010 年 11 月 13 日 下午 11:55:11
当然，如果网络没有遭受洪泛，而且你并不特别担心当前交易被拖延，那么或许值得优先使用你的 0 确认交易，这样你就可以“保留”优先级更高的币，等网络确实遭受洪泛时再用。
你应该至少使用一些优先级，以防下一区块出现前发生洪泛。
只要所有依赖交易都至少有 1 个确认，如果交易一开始没有足够的优先级，其依赖交易就会随着时间增加优先级，直到它达到要求。
引用
当然，像我上面的帖子所述，通过加入 1000 BTC 左右刚刚周转过的币来提高优先级，仍然行得通！
或者说，要管理你在一笔交易上花掉多少优先级。软件必须知道你未来的计划，才能判断是现在花掉优先级，还是留到以后使用。不过我认为我们不需要深入到那种细节。普通用户和洪泛者之间的差异已经足够大了。
优先级不必包办一切。一旦你知道发生了洪泛，就可以添加 -paytxfee=0.01。希望借助优先级，你在此之前的交易最坏也只是较慢，而不会卡住。
英文原文
展开英文原文
Quote from: ByteCoin on November 13, 2010, 11:55:11 PM
Of course, if the network is not being flooded and you're not overly concerned about the current transaction getting held up then it's probably worth preferring to use your 0 conf transactions so that you can "save" the higher priority coins for when the network is being flooded.
You should use at least some priority in case a flood comes along before the next block.
As long as all dependencies have at least 1 conf, if the transaction doesn't have enough priority at first, the dependencies will age until it does.
Quote
Gaming the system by including 1000 or so recently turned over BTC to bump the priority as described in my post above still works of course!
Or managing how much priority you spend on a transaction. The software would have to know your future plans to know whether to spend your priority now or save it for later. I don't think we'll need to get into that much detail though. There's a wide enough difference between normal users and flooders.
Priority doesn't have to do everything. Once you know there's a flood, you can add -paytxfee=0.01. Hopefully with priority, your transactions before that should be at worst slow, not stuck.