Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chinese translation for address.md and blockchain.md #209

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Chinese translation for address.md and blockchain.md #209

wants to merge 1 commit into from

Conversation

0x0042
Copy link

@0x0042 0x0042 commented Jul 5, 2018

I have translated them into Chinese, you may proofread them and then merge them to the master branch, thanks.

address_ch.md Outdated

## 账户地址

与比特币和以太坊类似,Nebulas 也采用了椭圆曲线算法作为 Nebulas 账户的加密算法。Nebulas 账户的地址是通过**公钥**计算出来的,而公钥则通过用户**密码短语**进行加密的**私钥**计算而来。此外,我们也有校验设计,旨在防止用户因为输入几个错误字符而将 _Nas_ 意外发送给错误的用户账户。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“�椭圆曲线算法” 前面有个异常字符

address_ch.md Outdated

## 智能合约地址

计算合约地址和计算账户地址略有不同,合约发送方的密码短语不是必需的,地址和随机数(nonce)才是必需。有关更多信息,请查看 [smart contract](https://github.com/nebulasio/wiki/blob/master/tutorials/%5BEnglish%5D%20Nebulas%20101%20-%2003%20Smart%20Contracts%20JavaScript.md) 和 [rpc.sendTransaction](https://github.com/nebulasio/wiki/blob/master/rpc.md#sendtransaction)。计算公式如下:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

随机数(nonce) 这里翻译成随机数不妥,直接使用nonce吧。

address_ch.md Outdated
length: 35 chars
```

**0x57** 是账户地址的一个单字节“类型码”,**0x19** 则是一个单字节固定“填充”。
Copy link
Contributor

@yupnano yupnano Jul 5, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议改成:
0x57 一个单字节“类型码”,表示账户地址;0x19 则是一个固定的单字节“填充”。

address_ch.md Outdated
length: 35 chars
```

**0x58** 是账户地址的一个单字节“类型码”,**0x19** 则是一个单字节固定“填充”。
Copy link
Contributor

@yupnano yupnano Jul 5, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

建议改成:
0x58 一个单字节“类型码”,表示智能合约地址;0x19 则是一个固定的单字节“填充”。

blockchain_ch.md Outdated
| blockHeader | transactions | dependency |
+---------------+----------------+--------------+
blockHeader: 头部信息
transactions: 交易数组
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“交易数组”改成“交易序列”比较合适

blockchain_ch.md Outdated
stateRoot: 根哈希账户状态
txsRoot: 根哈希交易状态
eventsRoot: 根哈希事件状态
consensusRoot: 共识状态,包含提案和超级节点
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stateRoot: 账户状态的根哈希
txsRoot: 交易状态的根哈希
eventsRoot: 事件状态的根哈希
consensusRoot: 共识状态,包含提议者和当前dynasty的验证者

blockchain_ch.md Outdated
hash: 交易哈希
from: 发送者的钱包地址
to: 接收者的钱包地址
value: 转移数量
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

转账数值(不应该翻译成转移)

blockchain_ch.md Outdated
timestamp: 1970年1月1日以来经过的纳秒数
alg: 签名算法的类型
sign: 区块哈希的签名
data: 交易数据,包含了交易类型(二元转移/部署智能合约/调用智能合约)和 payload
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sign: 交易哈希的签名(原英文文档有误)
data: 交易数据,包含了交易类型(普通转账/部署智能合约/调用智能合约)和 payload

blockchain_ch.md Outdated

首先,我们需要**交易池**来缓存来自网络的交易。然后,我们等待本地**共识**组件创建一个新的区块,例如 DPoS。

无论新区块来自哪里,我们都使用相同的步骤来处理,如下所示:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“�新区块” 有乱码
后面还有10处乱码,请仔细检查一下。

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

@0x0042
Copy link
Author

0x0042 commented Jul 6, 2018

@yupnano 合并了一下commits,乱码问题也全部改好了,估计是我的vscode有点设置问题导致乱码了

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants