第99期：Bitcoin Core v30

关闭。

off.

隐私？

Privacy?

是的。

Yeah.

你可以

You can

如果我们更改这个，就能看到谁升级了。

see who upgraded if we change this.

也许类似的情况也适用于手续费率。

And maybe something similar applies to fee rates.

如果我们突然取消它，就能看出谁升级了。

If we suddenly drop it, then you can see who's upgraded.

所以我不确定那里正确的做法是什么。

So I'm not sure what the right path is there.

对。

Right.

好的。

Okay.

我们继续下一个议题吧。

Let's move on to the next point.

不错。

Cool.

实际上，我认为这里还有一个政策问题。

Actually, I think this is also there there's another policy issue.

有一个新的政策规则。

There's a new policy rule.

如果我说得不对请纠正我，但有一个新的政策规则，限制每笔交易或每输出的签名操作次数，SIGOps？

Just correct me if I'm saying anything wrong, but there's a new policy rule that restricts the number of signature operations, SIGOps, per transaction or no, per output?

对吧？

Right?

是的。

Yeah.

我们曾经在第93期节目中详细讨论过关于共识清理与恢复软件的提案，该提案旨在应对时间扭曲攻击。

So we did a whole episode 93 about the great consensus cleanup restoration software proposal, which deals with time warp attacks.

SoftWark提出的一种攻击方式是防止有人创建一笔交易，需要在树莓派上耗时一个半小时来——抱歉，是创建一个在树莓派上需要一个半小时才能生成的区块，对吧？

And one of the attacks that SoftWark proposed SoftWark is trying to deal with is preventing somebody from making a transaction that takes like an hour and a half on a Raspberry Pi to oh, sorry, to create a block that takes an hour and a half on a Raspberry Pi to Right.

嗯。

Mhmm.

而在现代计算机上可能需要几分钟。

And maybe several minutes on a on a modern computer.

因为如果一个恶意矿工生成了这样的区块，他们就能拖慢竞争对手的进度，从而获得领先优势。

Because if if a if a malicious miner produces such a block, they can stall their competition and maybe get a head start out of that.

而这一问题的解决方案正是依赖于这一特定规则。

But in and and the way that was fixed involves that particular rule.

所以这个每笔交易2500个SIGOps的限制，我认为是针对每笔交易的。

So this this 2,500 SIGOps limit per I think it's per transaction.

好的。

Okay.

所以简单说一下，它的意思是，如果我理解得没错，你可以创建一个交易或一个输出，但你不确定到底是哪一个？

So just say what it what it is, it means, basically, if I understand correctly, you can make a transaction or an output with what so you're not sure which of the two it is?

它到底是交易还是输出？

It's either a transaction or an output?

我觉得是每个交易限制，但你要统计的是输入和输出中的SIGOPs。

I I think it's it's per transaction, but what you're counting is you're counting SIGUPs in the inputs and in the outputs.

好的。

Okay.

所以一个交易中最多只能有2,500个签名，对吧？

So that can be a maximum of 2,500 signatures basically in a transaction then.

对吗？

Right?

这就是它的意思。

That's what that means.

我

I

是的

Yeah.

签名操作略有不同。

Signature operations is slightly different.

例如，多重签名的旧式多重签名或裸多重签名，正如我们所称的那样。

So for example, a multisig legacy multisig or bare multisig as as we called it.

我认为它算作20次左右。

I think it counts as 20 or something like that.

我对这里的细节有点模糊，但基本上，这是对签名操作数量的限制。

I I'm a little fuzzy on the details here, but basically, it's a limit in the number of signature operations.

任何合理的交易都不会超过这些限制。

No sane transaction would actually go over those limits.

比如，有

Like, there's

因为不是几百，而是几千。

Because no because it's thousands.

是的。

Yeah.

对。

Yeah.

没错。

Exactly.

你需要一种非常、非常疯狂的多重签名。

You'd need a very, very insane kind of multisick.

所以，唯一会发起这种交易的人，要么是试图攻击网络的人，要么是做实验的人。

So the only people who would be making such a transaction are people trying to DOS the network or people doing experiments.

我认为历史上确实有过一些实际违反这些限制的案例。

I think there were some historical examples of of of these actually violating them.

好的。

Okay.

所以现在，如果你发起一笔包含3000个SIG OPS的交易，那么

So right now right now, if you make a transaction with 3,000 SIG OPS, well,

仍然可以是3000个SIG OPS。

can still be 3,000 SIG OPS.

是的。

Yeah.

对。

Yeah.

它仍然可以被打包进一个区块中。

It can still be mined in a block.

它仍然是共识有效的。

It is still consensus valid.

对吗？

Correct?

是的。

Yeah.

这一点不会改变。

And that doesn't change.

对吧？

Right?

这是一个策略变更。

This is a policy change.

是的。

Yeah.

所以你现在不能再中继它了。

So it's like you can't relay it anymore.

对。

Right.

如果有人向你发送这样的交易，而你正在运行比特币核心30版，那么你将不会把它包含在你的内存池中，也不会中继给其他节点。

So if if someone sends a transaction like that to you and you're running Bitcoin Core 30, then you're gonna not include that in your mempool and not relay it to other nodes.

但如果它在区块中，那仍然没问题。

But if it's in a block, again, then that's still fine.

是的。

Yeah.

这个团队的存在是为了保护未来的矿工。

And this team is there to protect future miners.

它并不是真的为了保护网络，因为我不认为它们会那么糟糕。

It's not really there to protect the network because I don't think they're that that terrible.

但对于未来的矿工来说，当且仅当这成为软分叉时，它就成为了共识。

But a future miner, when when and if or if and when this becomes a soft fork, then it is consensus.

我们不希望矿工意外地挖出这个东西。

And we don't want a miner to accidentally mine this thing.

所以这是其中一个原因。

And so that's one of the reasons.

政策规则的目标之一就是防止意外挖出某些内容。

That's one of the goals of policy rules is to prevent accidentally mining something.

矿工那里有一个标准交易。

The miner does there's a standard transaction.

他们永远不会看到它。

They'll never see it.

他们永远不会挖出它。

They'll never mine it.

对。

Right.

所以这是为了预期可能在未来发生软分叉，提前让网络行为朝那个方向发展。

So it's kind of in anticipation of hopefully, potentially a future soft fork to already sort of Yeah.

你知道，推动网络行为朝那个方向发展，这样当软分叉发生时，它只是一个相对较小的改动，不会引起太多问题。

You know, push network behavior kind of in that direction so that when the soft fork happens, then it's a relatively small change that can't really cause too much problems essentially.

对吧？

Right?

是的。

Yeah.

没错。

Exactly.

你希望软分叉对用户和矿工来说都尽可能安全。

You want soft forks to be as safe as possible for users, but also for miners.

是的。

Yeah.

而且我认为这也关联到另一个观点。

And I think also so that ties in with, I guess, another point.

我们似乎又稍微回到了Oprethorn问题上。

We we do apparently keep getting back a little bit to the Oprethorn issue.

总体而言，我认为Bitcoin Core项目的目标是尽可能消除策略规则，使节点接受和中继的内容尽可能接近实际的共识规则。

As a general sort of direction, I think the goal of the Bitcoin Core project is to essentially, you know, as much as possible, just get rid of policy rules and make what nodes accept and relay as close as possible to the actual consensus rules.

对吗？

Is that correct?

有一种理念认为，策略和共识应当趋同。

There is a there is a philosophy that says that policy and consensus should converge.

是的。

Yeah.

没错。

Exactly.

我不知道这是否现实，但其中一个原因是，策略的一个目标是升级钩子。

I don't know if that's realistic, but and one of the reasons is that one of the goals of one of the one of the use cases for policy is upgrades, upgrade hooks.

嗯。

Mhmm.

升级钩子的意思是，比如SegWit版本二、三或四目前不是标准的，因此不会被中继。

Upgrade hooks means that, say, SegWit version two or three or four currently is not standard, so it will not be relayed.

但它在共识上是有效的。

But it is consensus valid.

只是如果你挖出它，它就没有意义。

It's just that if you if you mine it, it has no meaning.

所以这是一种我们不希望它们相同的情况，因为那样你就永远无法升级。

And so that's a case where we don't want them to be the same because you would never be able to upgrade.

当然。

Sure.

是的。

Yeah.

对，是的。

I yeah.

所以我理解你的理念，你不想设置那些有些人称之为教条的限制，比如交易大小限制或RBF机制。

So I get the I get the philosophy of like you you don't wanna have these pedantic limits as some people would call them, like the opportune size or RBF things.

嗯。

Mhmm.

但我认为，说共识和策略不能完全一致是不对的，因为那样的话，你将永远无法对比特币进行升级。

But it's not I don't think it's true that consensus and policy cannot be identical because you would never be able to upgrade Bitcoin anymore.

是的。

Yeah.

是的。

Yeah.

你仍然得为……留出空间

You still gotta leave the room for

一个币。

a coin.

或者你会根据情况说，你可能会让它变得完全不安全。

Or you'd make it depending on how you could also say, well, you'd make it completely unsafe.

所以你也可以这么说，那就直接允许SegWit版本三中继，别管它了。

So you could also say, well, let's just allow SegWit version three relay and not worry about it.

但那样的话，人们可能会不小心伤害自己，把钱转出去，因为你可能会得到一个B C 1 f地址，这可能是未来的某个SegWit版本。

But then people can shoot themselves in the foot and give away their money because you would get a B C 1 f address, which might be some future SegWit version.

我不知道字母f对应的是什么。

I don't know what the letter f maps to.

嗯。

Mhmm.

你会直接把钱发到那个地址，钱就消失了，甚至不会落到任何人手里。

And you would just send to it, that money would just disappear, and it wouldn't even go to anyone.

好的。

Okay.

为了给我们的听众一个大致的概念，因为现在的限制是2500。

What's just to give our listeners a sort of rough idea because so now the limit is 2,500.

正如你提到的，这个数字远远超过任何人实际使用时可能需要的量。

Like you mentioned, that is probably far beyond anything that anyone would ever use for any real reason, essentially.

嗯。

Mhmm.

这对一个节点实际上会产生什么影响？

What kind of impact does this actually have on a note?

假设这个限制被触及了。

Let let's say this limit is touched.

比如，有一笔交易确实包含了2500个SIG操作。

Like, there is a transaction that actually has 2,500 SIG ops.

我们说的是这笔交易会让你的节点卡顿一秒钟，还是连一秒钟都不到？

Are we talking about a transaction that's gonna stall your note with like a second or not even that?

或者大致的范围是怎样的？

Or what what's what's sort of ballpark

你有没有考虑过？

do haven't think about?

我看过具体的数据，但我觉得影响可以忽略不计。

Looked at the exact numbers, but my guess is it's negligible.

对于单笔交易来说，这非常安全。

Like, this is very safe for individual transactions.

其中一个原因是，还有一个策略限制，将交易大小限制在100,000千字节以内。

And one of the reasons is that the policy there's another policy limit which limits transactions to a 100,000 kilobytes.

嗯。

Mhmm.

而且

And

所以我认为，真正更危险的是这些高数量的SIGOps与超大交易的结合。

so my guess would be that the combination of these these high numbers of SIGOps and a very large transaction are what what really is more dangerous.

你必须记住，比特币中存在这种二次方现象。

You gotta keep in mind that we have this quadratic phenomena in Bitcoin.

所以二次哈希，这就是SegWit解决的问题，但传统交易仍然如此。如果简化来看，两个各一KB的交易，每个都有一次不良计算。

So quadratic hashing, that's what solve a SegWit, but legacy transactions still If you simplify it, two transactions of one kilobyte have like one bad each.

对吧？

Right?

加起来就是两次不良计算。

It adds up to two bad.

但如果你做一个两KB的交易，可能会变成四次不良计算。

But if you make a two kilobyte transaction, it might be four bad.

这是不良计算乘以不良计算。

It's it's bad times bad.

是的。

Yes.

所以，如果是一个大交易，其危害远大于多个小交易的二次叠加。

So if it's one big transaction, it's much worse than several small transactions quadratically.

因此，这可能就是为什么单个交易违反这个策略限制不会构成问题，但矿工却可能包含一个更大的交易。

And so that's probably why, like, in an individual transaction violating this policy limit is not gonna be a problem, but a miner could include a bigger one.

对。

Right.

但无论如何，总结一下，一个包含2500个SIG操作的交易，实际上根本不可能有真正的使用场景，但同时仍在安全范围之内。

But in any case, you know, to summarize this, you know, a transaction that has 2,500 SIG ops is both very impossible to be used for any real reason while at the same time also still well within sort of safety limits.

所以这就是为什么至少这个数字是大致这么选定的。

So that's why at least that's a ballpark that number was picked.

对吧？

Right?

是的。

Yeah.

而且总的来说，这种共识清理的想法是为了缓解最坏情况，同时不没收任何合法用途，也不会接近合法用途。

And and in general, you'll the idea of this consensus cleanup thing is to mitigate the worst case scenario without confiscating any legitimate use case or getting anywhere near legitimate use cases.

是的。

Yeah.

所以这里存在一种权衡。

So there is a trade off.

你可能无法完全解决，仍然会存在验证速度较慢的区块，但不会那么慢。

You might not be able to solve There might still be blocks that are slow to validate, but not as slow.

你不可能做到完美解决方案，因为那样可能会危及到某些非常隐蔽但仍可能真实存在的使用场景。

You can't make it you can't have a perfect solution because then you're gonna start risking that you confiscate somebody's very obscure, but still potentially real setup.

是的。

Yeah.

好的。

Okay.

我们继续下一个议题。

Let's move to the next point.

另一项改进是单父单子的孤儿区块处理，或者在这方面有所提升。

And other improvement is one parent, one child orphanage, or there's something improved in that sense.

你能提醒我具体是什么吗？

Can you remind me what it is?

是的。

Yeah.

我们在之前的节目中已经讨论过这一点，但简要回顾一下：单父单子交易和交易包对像闪电网络这样的工具特别有用。

We have covered this in previous episodes, but a quick recap is that one parent, one child transactions, packages are useful for especially tools like Lightning.

在闪电网络中，当两个人建立了一个通道时，他们需要就强制关闭交易或惩罚交易达成一致。

So in the Lightning Network, when two people have a channel, they need to agree on the on a forced closed transaction or a penalty transaction.

基本上，就是你可以单方面关闭通道的交易。

The basically, the transaction that you can unilaterally close the channel with.

所以，如果你和我有一个通道，而其中一方离线了，我们各自都有一笔交易，可以在不与对方沟通的情况下关闭通道。

So if if you and I have a channel and one of us is offline, we both have a transaction to close the transaction without talking to the other side.

是的。

Yeah.

但我们必须决定这笔交易中包含多少手续费，而我们无法预知未来手续费会是多少。

But we have to decide how much fees go into that transaction, and we don't know how much fees the future is gonna hold.

因此，这一直是闪电网络中的一个复杂问题。

So that's always been a bit of a complexity in Lightning.

解决这个问题的通用方案是锚点交易，即允许你稍后添加一个子交易。

And the general solution to that is anchors where you, like, allow yourself to add a transaction later, a child's transaction later.

嗯哼。

Mhmm.

当时有不同的机制来实现这一点，但很多都遭受了钉住攻击——你添加了一个交易，但别人又添加了另一个，导致你无法提高手续费，交易永远无法确认，结果就来不及了，人们就崩溃了。

And there were different mechanisms to do that, and a lot of them suffered from pinning attacks where, like, you would add a transaction, but somebody else would add another one, and and you wouldn't be able to bump it, and it would never get confirmed, and you'd be too late, and people cry.

但后来人们提出了‘瞬态尘埃’的概念，这可不是芬兰金属乐队，它允许你创建一个手续费为零、金额为零的输出交易。

But then we people came up with the concept of ephemeral dust, which is not the Finnish metal band, which basically lets you make a transaction with a zero fee, zero amount output.

然后子交易花费这个零手续费、零金额的输出，并在最后一刻支付所需的任何手续费。

And then the child spends that zero fee, zero transaction output and pays whatever fee is necessary and can decide that at the last moment.

是的。

Yeah.

而要做到这一点，当然你需要添加一些自己的币。

And and to do that, you, of course, have to add some of your own coins then.

基本上，你是在将这个零金额输出与你自己的一些真实比特币一起花费给自身，并在新交易中包含手续费。

Basically, what you're doing is you spend that zero amount output to yourself in combination with some real money Bitcoin sets that you're sending to yourself, and you include a fee in that new transaction.

因为这是一个新交易，你现在可以准确知道应该包含多少手续费，才能在合理时间内确认。

And if that you know, now now because this is a new transaction, you basically know exactly how much fees you're supposed to include for it to confirm within a reasonable time.

是的。

Yes.

而且你可以替换它，是的。

And you can replace it Yeah.

如果手续费立即上涨的话。

If fees go up immediately.

所以这是一个不错的解决方案。

So so that's a nice solution.

通常情况下，你不允许中继一个手续费为零、完全没有手续费的交易。

Normally, you're not allowed to relay a transaction that has a zero fee, zero that has no fees in general, of course.

这样的交易不会被中继。

That's not gonna relay.

嗯。

Mhmm.

拥有一个零金额的输出也不会被中继，因为我们有尘埃限制。

And having an output with a zero amount is also not going to relay because we have a dust limit there.

嗯。

Mhmm.

所以想法是，你可以将它们作为一个交易包中继，即一个子交易和一个父交易。

So the idea is that you can relay them as a package, a one child, one parent transaction.

因此，这是一种临时的尘埃，因为尘埃确实存在，但它被立即花费了，并且总是以一对的形式在同一区块中出现。

So it's ephemeral dust because the dust exists, but it's immediately spent, and it always goes as a pair in the same block.

所以区块本身不会产生任何尘埃。

So the block never creates any dust.

只有交易本身会。

Only the transaction does.

是的。

Yeah.

它就是那个零零交易，其输出在同一区块中被立即花费。

It's it's the the zero zero set transaction is immediately or output is immediately spent in the same block.

它只是立刻消失了。

It's just it's immediately gone.

对吧？

Right?

这就是重点。

That's the point.

是的。

Yeah.

那么BitCover 30有什么改进？

So what's the improvement in BitCover 30?

改进在于，这个底层机制依赖于一个叫做“孤儿池”的东西。

The improvement is that this this mechanism under the hood relied on something called the orphanage.

孤儿池是BitCover用来识别的一种方式：嘿。

And the orphanage is a way for BitCover to see, hey.

我刚收到一笔新交易，但我不知道它的父交易是什么。

I just got a new transaction, but I don't know what the parent is.

所以我先暂时保留它，然后向对等节点询问父交易。

So I'm just gonna keep it for a little bit and then ask the peer for the parent.

所以

And so

因此，孤儿池专门用于那些通过点对点网络到达你这里、但你无法在区块链上看到其来源的交易。

So the orphanage is specifically for transactions that do make it to you over the peer to peer network, but you don't see basically where it's coming from on the blockchain.

它它

It it

是的。

Yeah.

它并没有花费任何你知道的币。

It's not spending anything you know.

所以你会问：告诉我它的父交易是什么，然后父交易发送，对等节点就会把它发送给你。

So you ask you're like, tell me what the parent is, and the parent sends sends and the peer sends it to you.

对。

Right.

对。

Right.

这个机制自29版本以来就一直存在了。

That mechanism has, you know, has been around now for, I think, since version '29.

这个机制的问题在于，它非常容易受到攻击。

The problem with that mechanism is that it's very easy to attack.

你可以通过无限的子交易来淹没孤儿池，这些交易完全可以是垃圾交易，因为它们知道无法判断一个子交易是否真实。

So you can flop the orphanage basically with infinite child transactions just that can just be complete garbage transactions because they know there's no way to know that a child is a real transaction.

嗯。

Mhmm.

所以，如果你知道你想影响哪个节点，你只需向他们大量发送孤儿交易，这几乎是免费的。

So it's essentially free to you know, if you know what peer you want to influence, you just, you know, just flood them with with orphans, basically.

这是一个先进先出的系统。

And it's a first in first out system.

一旦孤儿池中有100个孤儿交易，你就可以全部替换掉它们，这样就再也没有孤儿交易了。

So once a 100 orphans are there, you just replace all 100 of them, and there's no orphans anymore.

因此，这个中继机制是无效的。

And so this relay mechanism doesn't work.

所以在闪电网络的场景中，如果你试图攻击你的交易对手，并且大致知道他们连接了哪些节点，

So I guess in the lightning scenario, if you if you are trying to attack your counterparty and you roughly know what peers they're connected to,

也许你可以

maybe you

向他们的孤儿交易池发起轰炸，使他们的对手无法发出惩罚交易。

can blast their orphanages out, and then your peer will not be able to get their penalty transaction out.

类似这样的情况。

Something like that.

这就是潜在的风险。

That would be the risk.

是的。

Yeah.

那问题出在哪里？

So what's the deal?

所以版本30大大增强了孤儿交易池的强度。

So version 30 makes the orphanage a lot stronger.

它基本上——我不太了解完整的机制，但简而言之，假设你有10个节点，如果其中一个节点不断向你发送大量孤立交易，你并不会直接全部丢弃它们。

It basically well, I don't understand the full mechanism, but it boils down to if if one one of your let's say you have 10 peers and one of your peers starts misbehaving by sending you tons and tons of orphans, you're not just going to flush them all.

只有当另一个节点也向你发送了相同的孤立交易时，你才会保留它。

You're only if if another peer also sends you that orphan, you're gonna hold onto it.

因此，这里有一个更好的账务系统，使得攻击孤立交易池变得更加困难。

So there's just a better accounting system that makes it more difficult to attack the orphanage.

比特币核心在保护孩子们。

Bitcoin Core is protecting the kids.

没错。

Exactly.

是的。

Yeah.

对。

Yeah.

保护孩子。

Protect the children.

好的。

Okay.

所以，孤儿池现在更健壮了。

So the orphanage is more robust now.

下一个点？

Next point?

是的。

Yes.

有一个比特币命令，但我认为这有点太技术宅了。

There's a Bitcoin command, but I think that was a bit too nerdy.

我不知道你是否在意这个。

I don't know if you cared about it.

哦，是的。

Oh, yeah.

不。

No.

不。

No.

不过你尽管说吧。

Go for it, though.

是的。

Yeah.

一个命令来统领所有。

One command to rule them all.

以前有Bitcoin D、Bitcoin QT、Bitcoin，也就是Bitcoin d和Bitcoin QT，基本上是这样。

So there used to be Bitcoin D, Bitcoin QT, Bitcoin well, Bitcoin d and Bitcoin QT, basically.

然后还有一些即将推出的更改，会加入Bitcoin node和Bitcoin GUI。

And then there's some other changes coming up that would add Bitcoin node and Bitcoin GUI.

而且，其他开发者也说，好吧。

And, you know, other developers are like, okay.

这变得越来越混乱了。

This is becoming a confused mess.

有人下载了比特币，看到有15个以比特币开头的命令。

Somebody downloads Bitcoin, and they see, like, 15 commands that start with Bitcoin.

现在该怎么办？

What to do now?

所以解决方案是增加一个名为比特币的命令。

And so the solution is to add another command, which is just called Bitcoin.

你调用这个命令，然后告诉它具体要调用哪个其他命令。

And and you call that command, and then it and you tell it what what what else to call.

它有一个文档说明。

So it has a it has a documentation.

你输入比特币 node。

You call Bitcoin space node.

它会启动比特币d。

It starts Bitcoin d.

一共有15种标准。

There are 15 standards.

这标准太多了。

That's too many standards.

我们需要一个统一所有标准的标准。

We need a standard to rule them all.

现在有16个标准了。

Now there are 16 standards.

是的。

Yeah.

没错。

Exactly.

所以

So

这是给那些用命令行的极客准备的，但正如你所说，命令行对我来说根本不存在。

this is for nerds that use the command line, which as as you said, is I command line doesn't exist for me.

如果它不在图形界面里，那我就当它不存在。

If it's not in the GUI, sure, so I'm not aware of its existence.

我不在乎这个，但这是给像你这样的人用的，不知为何他们更喜欢用命令行。

I don't care about it, but this is for those people like yourself that, for some reason, prefer to use that.

对吧？

Right?

是的。

Yes.

好的。

Okay.

嗯，这类用户可能只是少数。

Well, such user might be a minor.

当然。

Sure.

我的意思是，我相信有很多人使用它。

I mean, I'm I I I I'm sure there's a lot of people that use it.

只是

Just

嗯，这只是一个过渡到下一个话题的桥梁。

Well, that that was a bridge to the next topic.

哦，你真聪明。

Oh, so you're clever.

IPC挖矿接口。

IPC mining interface.

是的。

Yeah.

我不记得这是什么了。

I don't remember what this was.

告诉我。

Tell me.

是的。

Yeah.

所以告诉我，我们之前几期聊过Stratum v2。

So tell me what we're We talked about Stratum v two a couple episodes ago.

我们确实有，是的。

We had, yeah.

嗯，我们确实讨论过。

Well, we did.

我认为在多个集里都提到过。

I think in multiple episodes.

一直有个想法，就是去中心化挖矿。

There has been the idea of, well, decentralizing mining.

Stratum v2 就是一种实现方式。

Stratum v two is one way to do that.

它首先增加了加密功能，还允许单个矿工创建自己的模板，从而实现一定程度的分离，你知道的？

It adds encryption for one thing, and it also adds the ability to add to for individual miners to create their own plug templates to kinda separate you know?

而这正是

And that is

主要是作为一种去中心化矿池的方式。

mostly It's basically a way to decentralize mining pools.

对吧？

Right?

矿池，是的。

Pool Yes.

矿池中的矿工可以自行决定在区块中包含什么内容。

Miners on a pool can, for themselves, decide what they put in blocks.

是的。

Yeah.

这主要存在于比特币核心之外。

And this mostly exists outside of Bitcoin Core.

有一个名为Stratum参考实现（SRI）的项目。

There's a particle called the Stratum Reference Implementation, SRI.

嗯。

Mhmm.

他们开发了各种软件工具，比如运行你自己的矿池、在Stratum v1和Stratum v2之间转换、创建自己的区块模板等。

They make all sorts of software tools, like, to run your own pool, to convert between Stratum v one and Stratum v two, to make your own block templates, etcetera.

但他们确实需要 Bitcoin Core 来做一件事，那就是生成区块模板，以及在找到区块时提交解决方案。

But they do need Bitcoin Core for one thing, which is to make the block templates and also to send the the the solution if you if you find a block.

这一部分被称为模板提供者。

And this this part is called the template provider.

因此，在最初制定规范时，设想的是由 Bitcoin Core 作为 Bitcoin 的模板提供者，只是要

And so the original idea was for when the spec was written, was for Bitcoin Core to be the template provider for Bitcoin Just to

为了明确这一点，模板基本上就是指进入区块的所有内容。

to be very clear about this, templates basically just means everything that goes into a block.

是的。

Yeah.

除了区块的解决方案之外。

Except the solution for it.

是的。

Yeah.

除了那些无意义的东西。

Except the nonsense.

除了哈希。

Except the hash.

是的。

Yeah.

当然。

Sure.

还有支付相关的内容。

And and the payout stuff.

是的。

Yeah.

所以 Bitcoin Core 擅长生成模板，但问题是，为了让 Big Concord 做到这一点，它必须支持 Stratum v2 协议。

So Bitcoin Core is good at making templates, but the the problem was that in order for Big Concord to do this, it would have to speak the stratum v two protocol.

因此，它必须支持相同的加密标准和新的消息格式。

So it would have to support the same encryption standards and new messages.

因此，我和一些其他人实现了这个功能，但当时对添加这些额外的复杂性、增加这些加密方法、监听端口以及处理消息等，存在一些阻力。

And so this was implemented by me and a few others, and there was some resistance to adding basically, to adding all this extra complexity, adding these these extra cryptographic methods and listening to ports and processing messages, etcetera.

于是我们达成了一个妥协：让比特币核心通过我们称为IPC（进程间通信）的协议进行监听，它并不直接支持Stratum v2，但能够支持Stratum v2所需的那些消息，或者提供Stratum v2所需的信息。

So then a compromise was reached, which is that, well, we'll have Bitcoin Core listen on a protocol we call IPC, interprocess communication, and it's not directly supporting Stratum v two, but it does support the messages that Stratum v two needs, or it can give the information Stratum v two needs.

它可以提供区块模板。

So it can give a block template.

它可以推送区块模板等等。

It can push a block template, etcetera.

这就是比特币核心第30版所实现的内容。

And so that's what in the that's what in that's what's in version 30 of Bitcoin Core.

然后你可以使用一个独立的应用程序连接到比特币核心，将这些信息实际转换为Stratum v2的协议语言。

And then you can use a separate application to connect to Bitcoin Core and actually basically translate this to the actual Stratum v two language.

对。

Right.

让我复述一遍，看看我有没有理解对。

So let me repeat this back to you and see if I get it.

所以Stratum v2本质上是一个独立的项目。

So stratum v two is basically a different project.

这是一个专门用于挖矿的项目。

It's a mining specific project.

它为矿池提供了一种方式，使其能够去中心化部分运营，特别是单个哈希算力用户，也就是矿池的矿工。

It's like it says set a way for mining pools to decentralize part of their operations, namely individual hashers, you know, users of the pool miners.

他们可以决定哪些交易被打包进区块，但为此，他们需要使用比特币核心来获取网络上的交易信息等，并利用这些信息来构建区块。

They can decide what goes into a block, which transactions go into a block, but for that, they would actually use Bitcoin Core to, you know, hear what transactions are on the network, etcetera, and use this to construct essentially the block.

现在，有一种桥梁或方式可以连接到Stratum v2协议，从而使整个系统协同工作。

And then now there's kind of a a bridge, a way to connect with the stratum v two protocol in order to make it all work.

这个总结够准确吗？

Is that a good enough summary?

是的。

Yeah.

对，没错。

So yeah.

完全正确。

Exactly.

所以，在VaconCore和整个Stratum v2生态系统之间有一个桥梁，它使用了这个新的IPC系统。

So there's a bridge between VaconCore and the rest of the stratum v two ecosystem, and it uses this new IPC system.

对。

Right.

这个系统原本是为完全不同的目的设计的，即进程分离。

So was intended for something completely different, namely the separation of processes.

它的设计目的是将节点与钱包和图形界面分开，这样如果其中一个崩溃，其他部分也不会崩溃。

So it was designed to split the node from the wallet and from the GUI so that if one of them crashes, the other doesn't crash.

我们可能仍然会这么做，但目前我们基本上是重新利用了这个工具。

And it might we might still do that, but for now, we we basically repurposed this tool.

对。

Right.

目前我知道的唯一使用Stratum v2的矿池是Demandpool，但我觉得他们还处于初创阶段。

I don't so right now, they're the only mining pool that I'm aware of that uses Stratum v two is Demandpool, but they're kind of still in startup phase, I think.

还有Brains。

And Brains as well.

他们使用它吗？

Do they use it?

是的。

I Yes.

但我不认为他们自己做，我不认为他们提供自定义模板。

But I don't think they do their own they I don't think they offer template custom templates.

他们只是支持新的加密算法。

They just support the new cryptography.

但这已经是一个改进了，因为如果你是ASIC矿工，现在如果你连接到任何Stratum v1的矿池，你的路由器、互联网服务提供商或任何人都可以窃取你的算力。

But that's already an improvement because if you're ASIC if you're If you run your ASIC farm and you connect to any seven v one pool now, your router or your internet provider or anyone can just steal your hash rate.

是的。

Yeah.

是的。

Yeah.

是的。

Yeah.

这不太好。

That's no good.

短的。

Shors.

但确实如此。

But yeah.

好的。

Okay.

但Brains目前还不允许个体矿工构建自己的区块，至少还没有。

But Brains does not or at least not yet allow individual miners to construct their blocks.

我不这么认为。

I don't believe so.

Demandpool计划这么做，但我认为他们还没有真正推出这项功能。

And and Demandpool does plan to do that, but I don't think they've actually launched this yet.

所以这就有点像鸡生蛋还是蛋生鸡的问题

So there was a bit of a chicken

我恰好知道，他们快要真正上线了。

I happen to know that they're getting close to launching for real basically.

哦，这是个好消息。

Oh, that's good news.

在比特币核心这边，一直存在一个鸡生蛋还是蛋生鸡的问题，因为即使这个新的IPC接口本身也颇具争议，部分原因在于当时还没有人使用它。

Has been a bit of a chicken egg problem on the Bitcoin Core side because shipping this new even this new IPC interface was also controversial partially because nobody was using it yet.

所以有些人说，我们应该先在矿池中彻底测试它，确保万无一失后再发布。

And so there's some people that say, well, we should first thoroughly test it with the pools and etcetera to make sure it's right and then ship it.

而反对意见是，如果这个功能没有被整合进比特币核心，矿池是不会去测试的，因为让他们编译一个自定义的实验性版本实在太麻烦了。

Whereas the counter argument to that is, well, the pools are not gonna test it if it's not already shipped in Bitcoin Core because it's too much of a pain for them to compile some custom experimental version.

尤其是当他们还不确定这个功能最终会不会被部署时。

And especially if they're not sure that it's actually gonna be deployed.

对吧？

Right?

他们至少需要有一些信心。

They need to have at least some confidence.

是的

Yeah.

之前确实存在这个鸡生蛋、蛋生鸡的问题，但现在它已经进入发布版本了。

There was that chicken egg, but now it's in the release.

但还不是很最终版本，所以下一个版本中可能还会有一些破坏性变更。

But it's not completely final yet, so it might still make a few breaking changes in the next release.

好的。

Okay.

我本来就想说。

I was just gonna.

所以我本来想问，现在这个完全可以直接使用了吗？还是比特币核心这边还有工作要做？

So I was gonna ask, is this completely good to go now, or is there still work to be done on the Bitcoin Core side?

没有。

No.

还有很多工作要做。

There's still good.

我的意思是，它已经可以使用了，但我认为还能改进。

I mean, it should it it's usable, but I think it can be improved.

对。

Right.

当然。

Sure.

好的。

Okay.

在我们转到最后一个话题之前，对这个话题还有什么最后的想法吗？

Any last thoughts on this topic before we move to the last last one on Let's our move.

好的。

Okay.

我们列表上的最后一个问题是，你给我解释一下。

Last one on our list is you you explain this to me.

NAT的BMP和端口控制协议PCP。

NAT's BMP and port control protocol, PCP.

嗯。

Mhmm.

所以我们之前几期已经讲过这个了。

So we have covered this in earlier episodes.

外面的世界很孤独，尤其是如果你从住宅环境运行你的节点的话。

You're it's a lonely world out there, especially if you run your node from a from a residential place.

通常，你的路由器会阻止任何连接到你的请求。

Typically, your router will block any connections to you.

所以你的节点可以访问外部世界，但外部世界无法连接到你。

So your node can can reach the outside world, but the outside world cannot reach you.

而且有多种常用的方法来解决这个问题。

And there's various methods that's often used.

这是一种‘别给我们打电话，我们会给你打’的模式。

It's it's a don't call us, we'll call you kind of

是的。

Yes.

逻辑。

Logic.

而现在，在游戏和种子下载等领域，已经开发出了一些方法来改变这种情况，让你能够接收外部连接，因为这样做在性能上有好处，也有其他原因促使你这么做。

And now, you know, in the world of gaming and torrents, etcetera, there have already been methods developed to change that so that you can actually listen to people connecting to you because there's some performance reasons that you wanna do that and other reasons why you wanna do that.

比特币核心从很早以前就开始使用这种方法，比如2012年甚至更早。

And Bitcoin Core was using that from very early on, like 2012 or even earlier.

但当时使用的方法并不安全。

But the method it was using back then was unsafe.

它被称为UPnP，因此默认是关闭的。

It was called UPnP, and so it was kind of turned off by default.

它一直存在。

It's there.

它一直都在，但因为软件存在太多漏洞，所以默认是关闭的。

It's always been there, but it was, like, off because of too many vulnerabilities in the software.

而最近，我们有了一个全新的方法。

And as of recently, we have a brand new method.

所谓全新的方法，其实是一个大约十年历史的标准，叫做PCP（端口控制协议）。

By brand new, I mean, it's a ten year old standard probably, called PCP port control protocol.

Bitcoin Core 已经从零开始实现了这个协议。

It's been implemented from scratch in Bitcoin Core itself.

从第30版开始，它默认开启。

And as of version 30, it's on by default.

这意味着，如果你全新安装一个节点，并且你的路由器支持这个协议——它可能支持，也可能不支持，但我认为许多现代路由器都支持——那么你的节点就会处于监听状态，这意味着你可以建立更多连接，网络也会更加稳健。

So that means if you install your node freshly and if your router supports this protocol, which it may or may not, I think a lot of modern routers will support it, your note is listening, which means you can have a bit more connections and the network is gonna be more robust.

是的。

Yeah.

所以，通常情况下，当你启动一个节点时，你可以连接到其他节点，但其他节点却无法连接到你，这就导致比特币核心节点中出现了一个子集，或者你可以称之为子社区，这些节点为网络其他部分提供了更多的服务或连接。

So, basically, normally, if you start up a node, then you can connect to other nodes, but other nodes cannot connect to you, which means there is essentially a subsection or, you know, a a sub community, whatever you wanna call it, of Bitcoin Core nodes that are providing more services or more connection to the rest of the network than others.

是的。

Yeah.

这些节点的连接性会更好，而且对这些节点的需求也很高，因为数量有限，每个人都想连接到它们。

They're gonna be better connected, and also there's a demand on those nodes because there's only a limited number of them and everybody wants to connect to them.

是的。

Yeah.

所以这实际上是一个略微中心化的因素，因为最初每个人都依赖它。

So it's a slightly it's a slightly centralizing factor actually that everyone sort of initially

依赖。

relies on.

中心化是因为这类节点数量不少，但它们可能会过载。

Centralizing because there's plenty of them, but it could they could get overloaded.

比如，如果比例变得过于不对称，那些正在监听的少数节点就会完全不堪重负。

Like, if the ratio is too is too becomes too asymmetrical, then the few notes that are listening will get completely overwhelmed.

而且这一点我

And this I

我的意思是，我并没有说它是中心化的，但我会说这确实是一种中心化的倾向。

mean, I didn't I didn't say I didn't say centralized, but I would say that is a sort of centralizing aspect.

对吧？

Right?

如果所有节点在这一点上都大致平等，每个人互相帮助，而不是都依赖某个子集，那就更好了。

It's better if all notes are sort of equal in that sense and everyone helps each other rather than everyone relying on some subset.

这样确实更好，但我认为这里并没有集中的风险。

It's better, but I don't think there was a risk of centralization here.

是的。

Mhmm.

但我确实认为，这些资源有被过载的风险。

But I do I do think there's just a risk of of overloading these resources.

问题的一部分在于，我们希望远离比特币节点通常只连接到少数节点的做法——我不是在‘觉醒’这个词的语境下说的，而是指连接来自世界各地、不同国家、不同网络的节点，这样就更难被某个网络运营商欺骗。

And part of the problem is because we want to move away from so so we Bitcoin nodes, want to connect to a diverse set of peers, and not in the the in the woke sense of the word, but in the as many places in the world, like different countries, different networks, so that it's harder to trick you for one network operator to trick you.

我们几年前在播客里讨论过一个新项目，叫ASMAP，它试图绘制互联网地图，然后确保节点能真正连接到不同国家等地方。

And there's a new project we talked about years ago in a podcast called ASMAP, where we try to map the Internet and then try to connect it really to different countries, etcetera.

这个项目的一个副作用是，我们可能会开始连接到一些非常冷门、非常冷门的地方，许多节点会因为试图过度多样化而纷纷连接到这些地方。

And one of the side effects of that project is that we might start connecting to very obscure very obscure places, and a lot of nodes would start connecting to those very obscure places because they're trying to diversify a bit too much.

于是，比如你在南美洲某个偏僻地方运行了一个互联网服务商，里面只有一个比特币节点，结果成千上万的节点都会试图连接到你，因为你实在太独特、太稀有了。

And then those, like, you run-in some random place in South America, you have an Internet provider with just one Bitcoin node in it, and then, like, thousands of nodes try to connect to you because you are very unique and special.

因此，如果更多的节点在监听，那么在这个偏远的互联网提供商上，也会有更多节点在监听。

And so if more nodes are listening, then hopefully on that obscure Internet provider, there's also gonna be more nodes listening.

这样，流量就不会全部涌向那一个监听节点。

So not all the traffic just goes to that one listening node.

是的。

Yeah.

好的。

Okay.

那么，Bitmap Core 中到底有什么新内容？

So this is so what exactly is new in Bitmap Core?

这现在只是一个功能吗？

Like, this is now just a thing?

或者

Or

这个功能从上一个版本起就已经存在了，但现在默认启用了。

So this feature has been in there since the last version, but it's now on by default.

所以如果你升级了，而且没有手动开启或关闭它，它就会默认开启。

So if you upgrade and you didn't manually turn it on or manually turn it off, it will be on.

那么

Then

如果你关闭了它，它就不会再被自动开启。

If you turn it off, it's only it's not gonna be turned on.

那么它就可以被外部世界调用。

Then it can be called by the outside world.

如果你的路由器支持的话。

If your router supports it.

是的。

Yes.

好的。

Okay.

路由器通常支持这个功能吗？还是有什么前提条件？

Do routers generally support this, or what's the if there?

我不确定。

I'm not sure.

比如，我们会弄清楚的。

Like, we we'll find out.

比如，从统计数据中应该能明显看出，监听节点的数量会大幅增加。

Like, it should be pretty clear in the stats that the number of listening notes would go up dramatically.

因为没错。

Because Right.

因为目前，大多数监听节点都在Tor上，因为人们设置Tor节点的方式通常也包含监听功能。

Because at the moment, most of the listening notes are on Tor because the way people set up their Tor notes usually is such that they're also listening.

所以有些人会说，大多数比特币节点都在Tor上。

So that's why some people are saying, Oh, the majority of Bitcoin nodes is on Tor.

但这并不正确。

Well, that's not true.

大多数监听比特币节点确实在Tor上。

The majority of listening Bitcoin nodes is on Tor.

对。

Right.

但这种情况最终可能不再成立。

But that might no longer be true eventually.

对。

Right.

对。

Right.

PCP也是一种毒品。

PCP is also a type of drugs.

这不在我的专业范围内，但你来说说看。

That's not my expertise, but you tell me.

巧合？

Coincidence?

我觉得每一个三个字母的缩写大概都是。

I think every three letter acronym probably is.

所以

So

好的。

Okay.

我想我们已经把列表过完了，Chors。

I think we made it through the list, Chors.

是的。

We did.

那么，这种情况下，除非你还有什么要补充的？

Well, in that case, unless you have anything to add?

没有。

No.

人们在哪里可以找到这个？

Where can people find this?

人们在哪里可以找到 Bitcoin Core 30？

Where can people find Bitcoin Core 30?

Bitcoincore.org。

Bitcoincore.org.

好的。

Okay.

谢谢，乔治。

Thanks, George.

感谢收听Bitcoin

For listening to Bitcoin

X Play。

X Play.