Newsletter 198 & 201: Add Chinese translation #777
Conversation
add Chinese to Bitcoin Optech
news-201-zh
| --- | ||
| title: 'Bitcoin Optech Newsletter #201' | ||
| permalink: /zh/newsletters/2022/05/25/ | ||
| name: 2022-05-25-newsletter |
There was a problem hiding this comment.
| name: 2022-05-25-newsletter | |
| name: 2022-05-25-newsletter-zh |
| title: 'Bitcoin Optech Newsletter #201' | ||
| permalink: /zh/newsletters/2022/05/25/ | ||
| name: 2022-05-25-newsletter | ||
| slug: 2022-05-25-newsletter |
There was a problem hiding this comment.
| slug: 2022-05-25-newsletter | |
| slug: 2022-05-25-newsletter-zh |
|
|
||
| MEV 问题是在以太坊（Ethereum）和相似的协议上显露出来的，在这些平台上，使用公开的链上交易协议将使矿工可以抢跑交易（frontrun trades）。举个例子，假设下面两笔交易都在等待进入下一个区块： | ||
|
|
||
| - Alice 卖出资产 *x* 给 Bob，价格为 1 ETH |
There was a problem hiding this comment.
| - Alice 卖出资产 *x* 给 Bob，价格为 1 ETH | |
| * Alice 卖出资产 *x* 给 Bob，价格为 1 ETH |
| MEV 问题是在以太坊（Ethereum）和相似的协议上显露出来的，在这些平台上，使用公开的链上交易协议将使矿工可以抢跑交易（frontrun trades）。举个例子，假设下面两笔交易都在等待进入下一个区块： | ||
|
|
||
| - Alice 卖出资产 *x* 给 Bob，价格为 1 ETH | ||
| - Bob 卖出 *x* 给 Carol，价格为 2 ETH（Bob 可从中赚取 1 ETH） |
There was a problem hiding this comment.
| - Bob 卖出 *x* 给 Carol，价格为 2 ETH（Bob 可从中赚取 1 ETH） | |
| * Bob 卖出 *x* 给 Carol，价格为 2 ETH（Bob 可从中赚取 1 ETH） |
|
|
||
| 如果这两笔交易是用公开的链上交易协议执行的，知晓了这两笔交易的某矿工可以把 Bob 踢出局。例如： | ||
|
|
||
| - Alice 卖出资产 *x* 给矿工 Mallory，价格为 1 ETH |
There was a problem hiding this comment.
| - Alice 卖出资产 *x* 给矿工 Mallory，价格为 1 ETH | |
| * Alice 卖出资产 *x* 给矿工 Mallory，价格为 1 ETH |
| 如果这两笔交易是用公开的链上交易协议执行的，知晓了这两笔交易的某矿工可以把 Bob 踢出局。例如： | ||
|
|
||
| - Alice 卖出资产 *x* 给矿工 Mallory，价格为 1 ETH | ||
| - Mallory 卖出 *x* 给 Carol，价格为 2 ETH（Mallory 可从中赚取 1 ETH；Bob 则颗粒无收） |
There was a problem hiding this comment.
| - Mallory 卖出 *x* 给 Carol，价格为 2 ETH（Mallory 可从中赚取 1 ETH；Bob 则颗粒无收） | |
| * Mallory 卖出 *x* 给 Carol，价格为 2 ETH（Mallory 可从中赚取 1 ETH；Bob 则颗粒无收） |
|
|
||
| Osuntokun建议 BIP86 的实现同时返回原始密钥（内部密钥）和调整后的密钥（输出密钥），以便调用函数可以使用适合其上下文的任何一个。 | ||
|
|
||
| - *与脚本路径支出的交互：* 与脚本路径支出一起使用的密钥有一个相关连的问题：为了使用脚本路径，支出者必须知道内部密钥。同样，这就需要实现者返回内部密钥，这样它就可以在其他需要它的代码中使用。 |
There was a problem hiding this comment.
@harding Our bullet-id-adder function strips out these characters and leaves a blank ID causing build issues. In the past we added some ASCII to get unique IDs and we could do that here if its not possible to keep the Chinese characters in the slugs. Thoughts?
There was a problem hiding this comment.
Edit: Okay, I did a bit of research. It seems that URLs generally only include ASCII characters. If we wanted to use UTF8 characters, they'd be expressed as %number to conform to ASCII. Maybe we can re-use the English section names for the anchor labels?
@dongcarl, do you have some insight on this?
There was a problem hiding this comment.
I found this relevant PR: #349 (comment)
There was a problem hiding this comment.
Hi @xekyo @bitschmidty ! I want to confirm are these 2 operations have equivalent results:
make productionlocally- PR review checks on GitHub
If so, I will try to fix the problem to make sure there is no error locally and then submit PR again.
Thanks!
Translation of Newsletter 198 & 201 into Chinese.
Primitive Lane community has translated Optech newsletter since Feb 2021.
This PR is just a beginning. The translated newsletter since #136 will be migrated to bitcoinops.github.io repo gradually. And we will continue to translate every week. 💪