Finally, thank you to the amazing @TenderlyApp team for co-hosting this workshop with us, you rock! 💪✨
It was a pleasure to work together and we look forward to our next event! https://t.co/ET7OyTbcrC
最后，感谢了不起的@TenderlyApp 团队与我们共同举办了这个研讨会，你太棒了！ 💪✨
很高兴一起工作，我们期待着我们的下一个活动！ https://t.co/ET7OyTbcrC
🏆 3rd prize went to @MarkuSchick (@IncrementHQ) and @jasoonsmythe (@float_shipping) 👏 https://t.co/dCxFFyd42n
🏆 三等奖授予@MarkuSchick (@IncrementHQ) 和@jasoonsmythe (@float_shipping) 👏 https://t.co/dCxFFyd42n
🏆 2nd prize went to Oren Yomtov (@orenyomtov), Blockchain Researcher at @FireblocksHQ 👏 https://t.co/FLQrnr5y0b
🏆 二等奖授予 @FireblocksHQ 的区块链研究员 Oren Yomtov (@orenyomtov) 👏 https://t.co/FLQrnr5y0b
🏆 1st prize went to @rubilmax, @MerlinEgalite and @MathisGD_ from @MorphoLabs 👏 https://t.co/jt0GmQCaAj
🏆 一等奖来自@MorphoLabs 的@rubilmax、@MerlinEgalite 和@MathisGD_ 👏 https://t.co/jt0GmQCaAj
Thank you to everyone who participated in the Quantstamp x @TenderlyApp War Room Workshop today in Berlin 🇩🇪 and huge congrats to the winners 🥳🥳🥳 https://t.co/2b6HFsFo78
感谢今天在柏林参加 Quantstamp x @TenderlyApp 作战室研讨会的所有人🇩🇪，并祝贺获奖者🥳🥳🥳 https://t.co/2b6HFsFo78
RT: It's a wrap on @Quantstamp and Tenderly War Room Workshop! Thank you all for participating, we had a blast and we hope to see you next time 💜 https://t.co/xfq89NmuhH
RT：这是对@Quantstamp 和 Tenderly War Room Workshop 的总结！感谢大家的参与，我们玩得很开心，我们希望下次再见💜 https://t.co/xfq89NmuhH
Proof-of-Stake is finally here!
What does this mean for Ethereum and what is next?
Learn about:
⛓ PoS vs PoW
🪙 ETH Issuance
🥩 Staking withdrawals
🚀 Future Upgrades and
💪 Ethereum's Final Form
https://quantstamp.com/blog/th...
权益证明终于来了！
这对以太坊意味着什么，下一步是什么？
学习关于：
⛓ PoS 与 PoW
🪙 ETH 发行
🥩 质押提款
🚀 未来的升级和
💪 以太坊的最终形态
https://quantstamp.com/blog/th.. .
RT: 🧵 With the Merge fast approaching, we would do well to reflect on a few of its consequences pertaining to (pseudo)randomness on-chain.
Read on to learn about them 👇 https://t.co/J2e3pfuj1l
RT：🧵 随着 Merge 的快速临近，我们最好反思一下它与链上（伪）随机性有关的一些后果。
继续阅读以了解它们👇 https://t.co/J2e3pfuj1l
Read the full post on how you can prevent replay attacks post Ethereum merge 👇
https://quantstamp.com/blog/pr...
阅读有关如何在以太坊合并后防止重放攻击的完整文章👇
https://quantstamp.com/blog/pr...
Why nonce divergence is a limited fix 🛠️
- If an attacker can execute transactions on the other chain and make the nonces of an account match
- If the account owner forgets to maintain nonce divergence and transacts on the other chain
Replay attacks become possible again ⚠️💥
为什么随机数分歧是一个有限的修复🛠️
- 如果攻击者可以在另一条链上执行交易并使账户的随机数匹配
- 如果账户所有者忘记维护随机数分歧并在另一条链上进行交易
重放攻击再次成为可能⚠️💥
Both rollups and bridges employ custodian smart contracts on the Ethereum network that will be duplicated on both the PoW and PoS chains. There may be implications for users as well.
汇总和桥接都在以太坊网络上使用托管智能合约，这些合约将在 PoW 和 PoS 链上复制。也可能对用户产生影响。
Implementations of these systems are complex, so there is no one rule that fits every situation.
Some bridges and rollups may not be impacted at all, so we recommend users go through each project’s official channel to ask about the post-merge situation.
这些系统的实现很复杂，因此没有适合所有情况的规则。
部分bridge和rollups可能完全不受影响，建议用户通过各个项目的官方渠道询问合并后的情况。
When in doubt, users can always protect assets on other chains and rollups by exiting back to the Ethereum mainnet prior to the merge, and following the two-wallet advice above 🛡️
如有疑问，用户始终可以通过在合并之前退出以太坊主网并遵循上面的两个钱包建议来保护其他链和汇总上的资产🛡️
Some people suggest that diverging nonces can sufficiently protect against merge-related replay attacks, but this is not true ⚠️
有人建议分散随机数可以充分防止与合并相关的重放攻击，但事实并非如此⚠️
The Ethereum protocol stipulates that transactions sent to a network by an account are sequentially numbered, with no gaps.
Each number in the sequence is called a “nonce” and is part of the transaction payload that needs to be signed.
以太坊协议规定，账户发送到网络的交易按顺序编号，没有间隔。
序列中的每个数字都称为“nonce”，是需要签名的交易有效负载的一部分。
The case for nonce divergence assumes that if one chain advances the account nonce, the other chain will be behind in the transaction sequence, and any attempt to replay transactions would fail because of this gap.
随机数分歧的情况假设如果一个链提前帐户随机数，另一条链将在交易序列中落后，并且任何重播交易的尝试都会因为这个差距而失败。
Chain ID has two purposes:
- Indicates the chain the transaction is meant for, so participants can tell whether a broadcasted message should be processed, or if it should be dropped and ignored
- Prevents so-called “replay attacks”
链 ID 有两个用途：
- 指示交易的链，因此参与者可以判断是否应该处理广播消息，或者是否应该丢弃和忽略它
- 防止所谓的“重放攻击”
During the merge, some miners may not update their nodes to Ethereum 2.0 clients and continue on Ethereum's PoW chain, also operating with chain ID 1.
在合并期间，一些矿工可能不会将他们的节点更新为以太坊 2.0 客户端并继续使用以太坊的 PoW 链，也使用链 ID 1 运行。
Until a new chain ID is chosen for the surviving PoW chain, transactions signed and submitted to the PoS and PoW chains will be identical and can be executed on both…aka a “replay attack” 💥
在为幸存的 PoW 链选择新的链 ID 之前，签署并提交到 PoS 和 PoW 链的交易将是相同的，并且可以在两者上执行……也就是“重放攻击”💥
To protect against unintended replays, the most efficient approach is to move all assets on both chains to new accounts dedicated to those chains.
为了防止意外重放，最有效的方法是将两条链上的所有资产转移到专用于这些链的新账户中。