正在发生的交易/垃圾交易洪泛攻击

中本聪SN-3633
其他参与者原话creighto原帖 ↗

或许在最近实现的年龄优先级规则之外,还应加一条无手续费交易的最小年龄规则。换句话说,或许能定一条生成规则:免费交易务必埋深 3 个区块之后才能再次免费转账。这样真实用户在必要时仍可立即花掉新资金,同时仍能按需重新调配资金,而无需额外成本。我认为这会显著抑制目前正在进行的垃圾交易攻击。

Perhaps in addition to the age priority rule recently implimented, there should be a minimum age rule without a transaction fee. Said another way, perhaps a generation rule that says that a free transaction must be 3 blocks deep before it can be transfered again for free. This will still allow real users to immediately spend new funds if they have to, while still permitting real users to reshuffle funds to suit their needs without an overhead cost. I think that this would significantly inhibit the type of spamming attack that is currently underway.

中本聪回应

我正在做的就是类似的事。优先级就是你描述的这个概念更正式化的版本。

I'm doing something like that. Priority is a more formalised version of the concept you're describing.

其他参与者原话FreeMoney原帖 ↗

按现状,3.15 有不少免费交易空间,这些空间优先给 [年龄]*[金额]/[大小] 最高的交易,对吧?划出一部分免费交易空间要求 [年龄]*[金额]/[大小] > C 是否合理?

As it stands now 3.15 has a lot of free transaction space and that space is given first to transactions with the highest [age]*[value]/[size] correct? Would it be reasonable to make some arbitrary portion of the free space require [age]*[value]/[size] > C ?

也许可以这样设定 C:一笔标准的 1 BTC 交易能进入下一个区块的主要免费交易区域,而 .1 BTC 的交易要等约 10 个区块才能进入。再让允许 [年龄]*[金额]/[大小] < C 的区域每次放行十来笔交易。

Maybe set C so that a standard 1BTC transaction can get into the main free area on the next block. And a .1 can get in after waiting about 10 blocks. And make the area which allows [age]*[value]/[size] < C to let in about a dozen transactions or so.

中本聪回应

是的,就像这样。不要求优先级的区域是 3K,每区块约十来笔交易。

Yes, like this. And the no-priority-requirement area is 3K, about a dozen transactions per block.

我刚上传了 SVN r185,对免费交易设置了最低优先级要求。交易洪水由反复转手的币构成,因此它们反复依赖自己的 0 确认交易。0 确认交易优先级为 0,这类免费交易就只能逐笔等待,每次等一笔交易先进入区块。

I just uploaded SVN rev 185 which has a minimal priority requirement for free transactions. Transaction floods are made up of coins that are re-spent over and over, so they depend on their own 0 conf transactions repeatedly. 0 conf transactions have 0 priority, so free transactions like that will have to wait for one transaction to get into a block at a time.

0.3.15 版只有在别无选择时,才会创建依赖 0 确认交易的新交易,因此普通用户通常不会遇到这个问题。

Version 0.3.15 doesn't write transactions using 0 conf dependencies unless that's all it has left, so normal users shouldn't usually have a problem with this.

我认为这是在把默认手续费设为 0.01 之外的一个好折中。要求通过免费交易周转比特币时,频率不能过高,并不算过分。你用免费交易,就是在接受施舍,而同一批币能多频繁地享受这种施舍,总得有个上限。

I think this is a good compromise short of making the default fee 0.01. It's not so much to ask that free transactions can only be used to turn coins over so often. If you're using free transactions, you're taking charity and there has to be some limit on how often you can use it with the same coins.

我们一直说免费交易可能会处理得慢一些。加上 -paytxfee=0.01 能帮你确保交易快速通过。

We've always said free transactions may be processed more slowly. You can help ensure your transactions go through quickly by adding -paytxfee=0.01.

上下文
译文校对、修订与纠错

当前版本尚未建立逐条校对状态记录。来源核验、历史审校与当前译文校对是不同事项。

查看历史审校与代表修订 →

译文内容版本:ce1b90178d93。用于比对文本,不代表校对等级或更新时间。

准备纠错说明

请填写对应原文、现译文、建议译法和理由。复制后通过你联系本站作者的渠道提交;此处不会自动发送。

来源
英文原标题

Transaction / spam flood attack currently under way

Bitcointalk · 原始链接 ↗ 记录编号 SN-3633

阅读字号

选择适合你的字号,之后阅读会继续使用。