其他参与者原话ByteCoin原帖 ↗当然，如果网络没有被垃圾交易淹没、你也不太在意当前这笔交易被耽搁，那么优先使用你的 0 确认交易可能更划算，这样可以把较高优先级的币「省」下来，留到网络真的被淹没时用。
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.
只要所有依赖的交易都至少有 1 个确认，如果交易一开始优先级不够，前序交易的年龄会随着时间推移而增长，直到这笔交易的优先级足够高为止。
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.
其他参与者原话ByteCoin（续）原帖 ↗当然，像我上面说的那样往交易里塞入约 1,000 个刚周转过的 BTC 来抬高优先级，这种钻空子的手法依然有效！
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.
优先级不必包办一切。一旦确认有洪水攻击，你能加上 -paytxfee=0.01。希望有了优先级机制，你在此之前发出的交易最坏也只是慢，而不是卡死。
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.
当前版本尚未建立逐条校对状态记录。来源核验、历史审校与当前译文校对是不同事项。
译文内容版本：6226e8f1ef75。用于比对文本，不代表校对等级或更新时间。
请填写对应原文、现译文、建议译法和理由。复制后通过你联系本站作者的渠道提交；此处不会自动发送。
