BNB Chain 提出 BEP-675 提案，旨在提升区块构建效率
BNB Chain’s BEP-675 Proposal Targets Faster Block Building
BNB Chain has introduced BEP-675, a draft proposal aimed at improving network throughput by reducing block re-execution in the validator process.
BNB Chain 引入了 BEP-675，这是一份旨在通过减少验证器过程中的区块重执行来提高网络吞吐量的草案提案。
The proposal introduces blind signing for validator blocks, allowing builders to submit executed blocks directly. According to the proposal, the change can reduce validator execution time on the critical path from 125 milliseconds to 15 milliseconds, with testnet environments showing a potential doubling of throughput.
该提案引入了验证器区块的盲签名，允许构建者直接提交已执行的区块。根据该提案，这一变化可以将关键路径上的验证器执行时间从 125 毫秒减少到 15 毫秒，测试网环境显示吞吐量可能翻倍。
That sounds technical, but the goal is simple: make block production more efficient without relying only on higher gas limits or shorter block times.
这听起来很技术性，但目标很简单：在不只依赖更高 gas 上限或更短区块时间的情况下，提高区块生产效率。
The key caveat is that BEP-675 is not live on BNB Chain mainnet. It remains in Draft status under the Pasteur network hard fork timeline.
关键注意事项是，BEP-675 尚未在 BNB Chain 主网上线。它仍处于 Pasteur 网络硬分叉时间线下的草案状态。
For more details, visit the official Github platform.
更多详情，请访问官方 Github 平台。
TL;DR
TL;DR
- BEP-675 aims to reduce block re-execution in BNB Chain’s validator process.
- The proposal could improve throughput in testnet environments.
- It is still in Draft status and should not be described as live mainnet functionality.
- BEP-675 旨在减少 BNB Chain 验证器过程中的区块重执行。
- 该提案可能在测试网环境中提高吞吐量。
- 它仍处于草案状态，不应被描述为已上线的主网功能。
Why Block Re-Execution Matters
为什么区块重执行很重要
In blockchain systems, small inefficiencies can become big bottlenecks.
在区块链系统中，小的低效可能成为大的瓶颈。
If builders and validators are repeating some of the same execution work before a block is finalized, the network is spending time on duplicated effort. BEP-675 targets that issue by changing how executed blocks are submitted and verified.
如果构建者和验证者在区块最终确定之前重复执行一些相同的工作，网络就在重复工作上花费时间。BEP-675 通过改变已执行区块的提交和验证方式来解决这个问题。
The proposal’s core idea is to remove unnecessary execution from the critical path.
该提案的核心思想是从关键路径中移除不必要的执行。
That could allow blocks to move faster through the production process, improving throughput without pushing every other parameter harder.
这可能使区块在生产过程中更快地移动，在不加大其他参数压力的情况下提高吞吐量。
For users, the benefit would be less visible than a new app or token launch, but it could matter for network performance.
对于用户来说，好处可能不如新应用或代币发布那么明显，但它可能对网络性能很重要。
Not Every Scaling Upgrade Needs Bigger Blocks
并非所有扩容升级都需要更大的区块
Scaling debates often center on gas limits and block times.
扩容争论通常集中在 gas 上限和区块时间上。
Raise the gas limit, and more transactions can fit into a block. Shorten block times, and blocks arrive more often. Both can increase throughput, but they can also create new pressure on validators, nodes, propagation, and network stability.
提高 gas 上限，区块中可以容纳更多交易。缩短区块时间，区块更频繁地到达。两者都可以提高吞吐量，但也可能给验证器、节点、传播和网络稳定性带来新的压力。
BEP-675 takes a different angle.
BEP-675 采取了不同的角度。
It targets the workflow around block construction and validation. If the same amount of work can be processed more efficiently, the network may gain capacity without simply forcing larger or faster blocks.
它针对的是区块构建和验证的工作流程。如果相同的工作量可以被更高效地处理，网络可能在不强制更大或更快区块的情况下获得容量。
That is the cleaner kind of scaling when it works.
当它起作用时，这是一种更干净的扩容方式。
Draft Status Keeps Expectations In Check
草案状态让预期保持现实
The most important limitation is status.
最重要的限制是状态。
BEP-675 is a proposal. It is not something users should assume is active on mainnet today. It sits inside a hard fork timeline and still needs the usual implementation, testing, review, and activation path.
BEP-675 是一项提案。用户不应假设它今天已在主网上激活。它处于硬分叉时间线内，仍需经过常规的实施、测试、审查和激活流程。
Crypto markets often treat proposals as finished upgrades.
加密货币市场常常将提案视为已完成的升级。
That is risky. Drafts can change. Timelines can shift. Testnet performance may not translate perfectly to mainnet conditions.
这是有风险的。草案可能会更改。时间线可能会变动。测试网的表现可能无法完美转化为主网条件。
The right read is that BNB Chain is working on a meaningful throughput improvement, not that throughput has already doubled for live users.
正确的解读是，BNB Chain 正在致力于有意义的吞吐量改进，而不是说现有用户的吞吐量已经翻倍。
Why BNB Chain Needs Efficiency
为什么 BNB Chain 需要效率
BNB Chain has long competed on low-cost, high-throughput activity.
BNB Chain 长期以来一直以低成本、高吞吐量的活动竞争。
That attracts DeFi apps, trading venues, gaming projects, retail users, and high-frequency transaction patterns. But it also means the network needs to keep improving performance if demand rises.
这吸引了 DeFi 应用、交易平台、游戏项目、零售用户和高频交易模式。但这也意味着，如果需求上升，网络需要持续提升性能。
Efficiency upgrades help maintain that competitive position.
效率升级有助于维持这一竞争地位。
They can also reduce pressure during periods of heavy activity, especially when retail trading and on-chain speculation spike.
它们还可以在高活跃期减轻压力，尤其是在零售交易和链上投机激增时。
A block-building improvement may not be flashy, but it can support the kind of user experience BNB Chain is built around.
区块构建的改进可能并不引人注目，但它可以支持 BNB Chain 所构建的用户体验。
What To Watch Next
接下来关注什么
The next steps are implementation and activation.
接下来的步骤是实施和激活。
Developers, validators, and the broader ecosystem will need to evaluate whether BEP-675 performs as expected, whether it introduces new trade-offs, and when it can safely move beyond Draft status.
开发者、验证者和更广泛的生态系统将需要评估 BEP-675 是否按预期表现，是否引入了新的权衡，以及何时可以安全地超越草案状态。
If successful, the proposal could give BNB Chain more throughput headroom without relying entirely on blunt parameter changes.
如果成功，该提案可能为 BNB Chain 提供更多吞吐量空间，而不必完全依赖生硬的参数调整。
For now, BEP-675 is best understood as a technical scaling proposal with real potential, but not yet a live mainnet upgrade.
目前，BEP-675 最好被理解为一个具有实际潜力的技术扩展提案，但还不是一个活跃的主网升级。
That is still important.
这仍然很重要。
The networks that keep improving under the hood are the ones most likely to handle the next wave of demand.
那些在底层不断改进的网络最有可能应对下一波需求。
This article is based on BNB Chain’s BEP-675 proposal materials.
本文基于 BNB Chain 的 BEP-675 提案材料。
This article was written by the News Desk and edited by Samuel Rae.
本文由新闻编辑部撰写，并由 Samuel Rae 编辑。
This report is based on information released by Github. at Github
本报告基于 Github 上发布的信息。在 Github 上。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力