Translating new version white paper of Aeternity to Chinese

I. Title - must be clear and concise

Translating new version white paper of Aeternity to Chinese

II. Summary - a concise description of the campaign. Limit this to 2 paragraphs max, no longer than 300 words.

Introducing technology which Aeternity based on and new development plan of Aeternity to Chinese blockchain community through translating new version white paper of Aeternity to Chinese.

III. Goals - clear objectives must be set, noting the target demographics and the call to action/conversions.
Introducing technology which Aeternity based on and new development plan of Aeternity to Chinese blockchain community through translating new version white paper of Aeternity to Chinese. Till now some parts of the new version of white paper which gathered by Liuyang have been translated. And we have been told that the version we wanted to translate is not the final one. We will check the final version and change the changed part.

First paragraph of the new version Aeternity white paper gathered by Liuyang in English and Chinese is here.

The Aeternity blockchain

White paper

The Aeternity team (Converted to pdf by [email protected] at 2019-11-30)

Abstract

The Aeternity blockchain aims to be a development platform for advanced blockchain applications that can be used by millions of users. This is realised by giving easy developer access to commonly used blockchain features, such as spend transactions, oracle query and response transactions and a possibility to register names on the blockchain via name transactions. These features are widely used with other blockchains and are simply and cheaply accessible in the Aeternity blockchain. In addition, the Aeternity blockchain has it own contract language, called Sophia which let application developers build applications as advanced as they can imagine. Of course, the contracts work seamlessly with the native transactions for spend, oracles, names and future extensions of the transaction types. Learning from mistakes in other blockchain languages, Sophia and the Sophia Virtual Machine are designed with security in mind. Many programmer errors that can be exploited in other languages, cannot be made in the functional language Sophia or its dedicated, super fast, virtual machine.

Aeternity区块链白皮书

摘要

Aeternity区块链定位于成为可承载数百万用户的先进区块链应用程序的开发平台。这通过方便开发者获取广泛使用的区块链功能来实现,例如转账交易(spend transactions), 预言机和响应交易(response transactions)以及通过命名(name)交易实现在链上注册命名(name)的可行性。这些特征在其它区块链中被广泛使用,它们在Aeternity中很容易获取并且成本很低。另外,Aeternity拥有自己的合约语言—Sophia,Sophia允许应用程序开发人员构建他们能想象到的任何高级应用程序。当然,合约和预言机、命名的本地交易、以及交易类型将来的扩展间可以无缝连接。Sophia吸取了其它区块链语言的错误经验,Sophia和 Sophia 虚拟机根据安全性设计。许多在其它语言中会被利用的程序错误,不能利用在在函数式语言Sophia以及专注超快的Sophia虚拟机中。

IV. Roles - team members involved in the project as well as their backgrounds and expertise, as well as any reviewers from the Board or the AE team who need to check output before release, if any.

Redcan (named Crazy Kai in Chinese Aeternity community) major in Ecology. Redcan read thousands of English papers and published papers in English journals, thus he gets experience in English translation to Chinese. Redcan gets a dream which is to change the world and he believes Aeternity can change the world.

Liushao major in computer science, interested in blockchain, bulit a website named aechina.io to spread news and technology of Aeternity in Chinese Aeternity community.

Dashu from the Chinese community, a big fan of Aeternity and an early investor of Aeternity. He did a lot English-Chinese translation work for his company, thus he gets experience in English translation to Chinese.

Super Lan graduated from an internal college in Sichuan, major in electrical automation.Super Lan has been paying attention to blockchain since 2015. In the early stage, he mainly focused on BTC, he was lucky to find Eternity in February 2018, and I have been fascinated since then.He firmly believe that Aeternity will change the world. Therefore, he has been carrying out community activities in the Chinese community, translating official technical documents and some real-time news to provide the latest and most detailed team information to people like him who addicted to Aeternity.

Johnny is a big fan of Aeternity blockchain. He did English-Chinese translation for his company , he gets experience in English translation to Chinese.

Liuyang the owner of aeknow.org, he will be the technical advisor for this campaign.

V. Minimum Viable Products - list of final output

New version of Aeternity white paper in Chinese.

VI. Timeline - how long will this campaign run, including preparations.

One month away from the new version white paper coming.

VII. Milestones - divide the timeline into achievable milestones. The budget may have to be released in increments as milestones are reached.

The time listed is according to the time new version white paper finished.

In first two weeks, we will finish translation. In third week, we will proofread the document. In fouth week, we will submit the document to ae team and Chines Aeternity community.

VIII. Budget - a clear breakdown of costs as well as the total cost

700 AE in total. Previous, I submitted to translate it for free, it is OK for me, however the other members of the team need to be rewarded and encouraged.

IX. Assessment/KPIs - state the desired end result and how they will be monitored and measured. Clear KPIs are essential in the approval process of a CBC.

The submitted document will be checked by ae team and Chinese Aeternity members. Anyone reeds it can give suggestions, then we will change it accordingly.

2 Likes

Yes, Aeternity is an amazing project and it has started to grow. Recently, I heard that the community will translate the new white paper into Chinese. I am very interested. My doctoral friend and I may be able to provide some free help. I am Da Shu from the Chinese community. Thank you!

2 Likes

Fantastic, let us do it

1 Like

A good start is half the battle, and the mechanism determines efficiency. I think the team would be happy to have everyone so actively involved. .

Hi and welcome. We are in the process of finalizing the white-paper. So if you wait a few days the target will be stable at least :slight_smile:

2 Likes

Thanks, please contact me as soon as you guys finish it.

1 Like

Hi @Redcan can you please re-format your proposal based on the template here: Campaign Proposal Template

You may update your proposal when the new whitepaper is finished. Then we can proceed to evaluation. Thank you.

OK, I will do it latter. When will thw new whitepaper be finished?

1 Like

The proposal have been renewed @theScientress

Thank you @Redcan I will ask the devs and let you know as soon as I have an ETA on the whitepaper. But we can have this for evaluation next week. I’ll contact you early next week for details on that call.

Ok, thak you. If you get anything to tell me, please contact me as soon as possible.

Can you also add some sample links of your translations from English to Chinese? Thank you.

Most part of Base aepp was translated by us for free, the traslation detail is listed as following.

{
“cancel”: “取消”,
“close”: “关闭”,
“confirm”: “确认”,
“next”: “下一步”,
“ok”: “OK”,
“deny”: “拒绝”,
“allow”: “允许”,
“copied”: “复制”,
“scan-qr-code”: “扫描二维码”,
“guide-desktop”: “目前Base æpp只能在只在一个浏览器选项卡中打开的情况下运行. 请关闭所有运行的标签.”,
“minutes”: “{n} 分钟 | {n} 分 | {n} 分钟”,
“hours”: “{n} 小时 | {n} 时 | {n} 小时”,
“days”: “{n} 天 | {n} 天 | {n} 天”,

“add-to-home-screen”: {
“note”: “请添加这个app到主屏幕.”,
“button”: “添加”,
“skip”: “没有添加…”
},

“header”: {
“title”: “Base web”,
“connect-account”: “连接一个账户”,
“connect-account-with”: “与Base æpp 或 Ledger”
},

“sidebar”: {
“connect-account”: “连接一个账户以开始”,
“connected-account”: “| 连接的账户 | 连接的账户”,
“base-app”: “Base æpp”,
“ledger”: “Ledger”
},

“not-found”: {
“note”: “你寻找的页面没有找到.”,
“to-home”: “返回主页”
},

“update-available”: {
“title”: “发现新版本。”,
“restart”: “请重新启动Base æpp.”
},

“store-load-error”: {
“note”: “Base app 未能加载.”,
“reset”: “重置所有数据”
},

“account-switcher”: {
“create-account”: “新子账户”,
“create-account-desktop”: “创建新帐户”,
“create-vault”: “使用AirGap创建一个”
},

“validation”: {
“confirmed”: “密码不匹配,请重试”,
“decimal”: “必须为数字,支持 {0} 位小数”,
“excluded”: “该字段必须是有效值。”,
“min”: “必须至少为 {0} 个字符”,
“required”: “这是必填栏”,
“address”: “无效AE地址”,
“max_value”: “必须小于或等于 {0}”,
“min_value”: “必须大于或等于 {0}”,
“min_value_exclusive”: “必须大于 {0}”,
“mnemonic”: “无效助记词”,
“url_http”: “该字段不是有效的HTTP(S) URL”,
“air_gap_response_url”: “这不是有效的同步代码。”,
“aens_name”: “必须以.chain结尾”,
“aens_name_unregistered”: “这个名称已被注册”,
“account”: “无效的AE地址或AENS名称”
},

“intro”: {
“guide”: “Base æpp
æternity 区块链
掌控在您手中”,
“login”: “登录”,
“recover”: “助记词恢复”,
“create-account”: “创建一个新账号”,
“onboarding”: “查看使用说明。”
},

“onboarding”: {
“skip”: “跳过”,
“start”: “开始”,

"welcome": {
  "guide": "<primary>Base aepp</primary><br>æternity从这里开始<note />",
  "note": "发送 & 接收AE,探索 æpps并管理您的账户。"
},

"send": {
  "guide": "<primary>发送 &amp; 接收AE</primary>轻而易举<note />",
  "note": "转账到联系人和子帐户。通过分享您的地址进行接收。"
},

"aepps": {
  "guide": "探索æternity",
  "note": "让æternity区块链为您的日常生活增添活力。"
},

"subaccounts": {
  "guide": "<primary>创建子账号</primary>在毫秒之间<note />",
  "note": "创建专用账户,用于支付、存储和提供æpps燃料。"
}

},

“recover”: {
“title”: “恢复账号”,
“guide”: “输入您此前所备份的 助记词。”,
“mnemonic”: “助记词恢复”,
“button”: “恢复账号”
},

“login”: {
“guide”: “你好! 登录使用密码登录æternity”,
“try-again-or”: “请重试”,
“button”: “登录”
},

“app”: {
“title”: “Browse”,

"list": {
  "featured-guide": "<primary>精选</primary>",
  "browse-guide": "浏览",
  "bookmarked-guide": "书签",
  "guide": "æpps <primary>浏览器</primary> (beta)",
  "note": "将运行在æternity区块链上的æpps添加到这里"
},

"url-form-placeholder": "输入链接",

"browser": {
  "refresh": "更新",

  "confirm-account-access": {
    "guide": "<app /><br />请求路径到<br /><account />",

    "address": {
      "name": "地址",
      "explanation": "这个æpp要求访问您的公共地址。"
    },

    "transactions": {
      "name": "转账记录",
      "explanation": "涉及一个拍卖。æpp将准备交易,需要您确认交易。"
    }
  }
},

"settings": {
  "title": "帐户访问权限",
  "count": "没有,有帐户访问权限| {n} 有帐户访问权限",

  "list": {
    "note": "管理哪些可以访问您的(子)帐户",
    "subtitle": "| 可访问 {n} 账户 | 可访问 {n} 账户(子)"
  }
}

},

“transfer”: {
“title”: “钱包”,
“guide”: “发送和接收 Æ”,
“amount”: “量”,
“fee”: “Fee”,

"tooltips": {
  "identicon": {
    "header": "相同",
    "content": "确认哪个帐户是活动的.帐户和子帐户具有唯一的标识符."
  },
  "browser": {
    "header": "浏览",
    "content": "浏览器探索æternity区块链."
  },
  "account-switcher": {
    "header": "切换账户",
    "content": "点击切换帐户或创建子帐户."
  },
  "redeem-balance": {
    "header": "扫码充值",
    "content": "点击此处从二维码(或纸质钱包)导入余额。"
  }
},

"send": {
  "title": "发送",
  "subtitle": "转账资金",
  "guide": "<primary>发送</primary> AE 给<br /><senderAddress />",
  "note": "将收件人地址粘贴到下面.或发送到子账户、联系人或扫描二维码.",
  "transfer": "转账",

  "to": {
    "guide": "<primary>新转账</primary><br>从",
    "recipient": "账户",
    "address": "ak_ …",
    "paste": "粘贴",
    "scan": "扫描",
    "scan-address": "扫描 AE 账户",
    "subaccount": "或发送给子账户",
    "confirm-sending-to-same-account": "发送和收款是同一个帐户,您确定要发送到同一帐户吗?"
  },

  "amount": {
    "guide": "<primary>新转账</primary><br />从 <senderAddress /><br />到 <recipientAddress />",
    "balance": "余额",
    "max": "Max",
    "fee": "最小转账手续费"
  },

  "resolved": {
    "title": "转账完成",
    "note": "广播成功!",
    "subtitle": "你已发送 {amount}",
    "to-history": "查看记录",
    "to-explorer": "查看浏览器",
    "copy": "复制tx hash"
  }
},

"receive": {
  "title": "接收",
  "subtitle": "分享你的地址",
  "guide": "<primary>分享你的地址</primary>给发送者",
  "guide-desktop": "<primary>接收</primary> tokens",
  "note": "让别人扫描你的二维码或分享你的地址",
  "copy": "复制地址",
  "copy-subtitle": "保存到剪贴板",
  "share": "分享地址",
  "share-subtitle": "给其他人",
  "connect-account": "请先连接帐户"
},

"transaction": {
  "title": "转账记录",
  "subtitle": "展示转账历史",
  "pending": "正在发送",

  "list": {
    "all": "所有",
    "incoming": "收入",
    "outgoing": "支出",
    "error": "转账期间发生错误。",
    "loaded": "已加载所有转账。",
    "no-transactions": "没有与此账户关联的转账记录。",
    "pending-transactions": "正在转账",
    "today": "今天"
  },

  "details": {
    "title": "转账详情",
    "received": "您已收到",
    "sent": "您已发送",
    "account": "账户地址",
    "from": "从",
    "to": "到",
    "name-owner": "新名称的所有者",
    "date": "日期",
    "status": "状态",
    "owner": "所有者",
    "hash": "交易 Hash",
    "type": "交易类型",
    "to-explorer": "浏览器查询",
    "confirmations": "{n} 个确认",
    "fee": "转账手续费",
    "total": "总计"
  },

  "type": {
    "SpendTx": "Spend",
    "ContractCreateTx": "创建合同",
    "ContractCallTx": "签订合同",
    "NamePreclaimTx": "预申请 Name",
    "NameClaimTx": "认领 Name",
    "NameUpdateTx": "更新 Name",
    "NameTransferTx": "转移 Name",
    "NameRevokeTx": "撤销 Name",
    "OracleRegisterTx": "注册 Oracle",
    "OracleExtendTx": "延期 Oracle",
    "OraclePostQueryTx": "查询 Oracle",
    "OracleRespondTx": "回应 Oracle",
    "ChannelCloseSoloTx": "单方关闭通道",
    "ChannelSlashTx": "进入通道",
    "ChannelSettleTx": "结束通道",
    "ChannelSnapshotSoloTx": "单方快照通道"
  }
},

"migrated-balance": {
  "title": "迁移中的数量",
  "subtitle": "未显示为上述余额",
  "note": "正在迁移中。他们将在下一次硬分叉后可使用。",
  "to-migrations": "查看迁移"
},

"redeem-balance": {
  "title": "兑换代币",
  "subtitle": "扫描二维码充值",
  "guide": "从扫描的钱包中兑换<primary>全部代币</primary>",
  "no-funds": "此网络上没有可兑换的代币。请确保您已连接到正确的网络,并且余额尚未兑换。",
  "wrong-qr-code": "扫描的二维码错误,请扫描需兑换钱包的二维码",
  "scan": "扫描钱包二维码"
}

},

“hd-wallet”: {
“account-name”: “账户”
},

“air-gap”: {
“account-name”: “AirGap 账户”,
“scan-signed-transaction”: “扫描签署交易”,
“link-vault”: “连接 Vault”,

"setup": {
  "title": "AirGap 设置",
  "method-guide": "<primary>AirGap Vault实现高强度的安全性</primary><br />我们建议使用断网设备.",

  "another-device": {
    "title": "最大(建议)",
    "subtitle": "在另一个设备上安装AirGap",

    "install": {
      "guide": "<primary>在另一部手机上安装AirGap</primary><br />在应用商店搜索AirGap或扫描二维码.",
      "link": "连接"
    },

    "guide": {
      "steps": [
        "<primary>在第二个设备上打开AirGap</primary><br />在打开AirGap前请断开网络连接.",
        "<primary>创建密钥</primary><br />断开网络链接对密钥来说意味着安全性最高.",
        "<primary>以正确的顺序写下它</primary><br />恢复时你需要用到.",
        "<primary>添加一个æternity 钱包</primary><br />点击钱包, 添加钱包并选择æternity.",
        "<primary>连接æternity钱包</primary><br />连接你的Vault到æternity地址."
      ]
    }
  },

  "same-device": {
    "title": "普通",
    "subtitle": "在这个设备上安装AirGap",

    "install": {
      "guide": "<primary>在智能手机上安装或打开AirGap</primary><br />打开AirGap Vault,打开想要同步的账户, 点击右上角的三个点, 并选择复制同步码.",
      "button": "安装 AirGap Vault"
    },

    "sync": {
      "guide": "<primary>Vault正在同步</primary><br />请粘贴同步码.",
      "sync-code": "AirGap 同步码",
      "button": "同步"
    }
  },

  "completed": {
    "guide": "<primary>Vault 同步完成</primary><br />在你的账户下查找你的AirGap Vault.",
    "finish": "完成"
  }
},

"modal": {
  "sign": {
    "guide": "<primary>扫描 AirGap Vault app</primary>签署交易",
    "done": "完成"
  }
}

},

“ledger”: {
“account-name”: “Ledger 账户”,
“mobile-not-supported”: “暂时不支持使用 Ledger 在移动设备上签名。”,

"not-supported": {
  "guide": "请切换到 Google\u00A0Chrome",
  "note": "暂时只有Chrome支持与Ledger的交流."
},

"connect-guide": {
  "title": "如何连接 <primary>Ledger</primary>",
  "steps": [
    "通过USB连接 Ledger 并解锁",
    "在你的Ledger上打开æternity app",
    "点击下方的按钮创建第一个账户"
  ]
},

"modal": {
  "address-confirm": {
    "create-guide": "创建 Ledger 地址",
    "confirm-guide": "确认 Ledger 地址",
    "address": "Ledger 地址",
    "create-note": "在你的Ledger上创建一个新的账户, 先确认你的地址",
    "confirm-note": "开始进程, 在Ledger上确认你的地址"
  },

  "address-not-confirmed": {
    "title": "地址没有确认",
    "note": "地址确认前 Ledger 不能使用. 恶意软件会使地址错配.请联系技术支持来解决这个问题."
  },

  "account-not-found": {
    "title": "没有发现账户",
    "note": "所连接的 Ledger 不包含指定的帐户. 你依然可以使用它,但你必须创建一个新的账户."
  },

  "request": "向 Ledger 发送请求",

  "request-retry": {
    "title": "请求失败",
    "note": "Ledger 未连接或请求未被确认.",
    "try": "再试一次"
  },

  "transaction-fee": {
    "title": "设定交易费",
    "fee": "交易费",
    "micro-ae": "Micro AE",
    "note": "更高的交易费会带来更快的交易确认."
  },

  "sign-transaction": "在Ledger上签署交易"
}

},

“name”: {
“title”: “Names”,
“expiration”: “结束于”,

"list": {
  "ending-soonest-note": "拍卖即将结束",
  "character-length-note": "按字节长度拍卖",
  "max-bid-note": "竞价拍卖",
  "personal-note": "为您的账户申请一个Names!",
  "personal-explanation": "点击“+”按钮来申请并与您的帐号关联.",
  "no-auctions": "没有符合这些标准的拍卖。",
  "registered": "注册名称"
},

"details": {
  "title": "Names详细信息",
  "name": "Names",
  "owner": "所有者",
  "created-at-height": "创建高度",
  "expires-at-height": "到期高度",
  "to-point": "设置 Names 指向",
  "to-transfer": "转移 Names",
  "to-transactions": "查看交易",
  "current-bid": "当前出价",
  "previous-bids": "往期出价",
  "auction-not-found": "没找到你要找的..."
},

"point": {
  "guide": "设置所属Names的指向 <account />",
  "subaccount": "或指向子账户",
  "confirm-pointing-to-same-account": "您指向的帐户和当前名称指向的帐户是同一个帐户,您确定要完成此交易吗?",

  "notification":{
    "succeed": "{name} 已成功指向",
    "failed": "未知原因,{name} 未指向"
  }
},

"transfer": {
  "guide": "转移 Names 的所有权 <account />",
  "subaccount": "或转入子账户",
  "confirm-transfering-to-same-account": "您要转移到的帐户和当前 Names 的帐户是同一个帐户,您确定要完成此交易吗?",

  "notification":{
    "succeed": "{name} 成功转移",
    "failed": "未知原因,{name} 未转移"
  }
},

"bid": {
  "guide": "竞价 <primary><name /></primary>",
  "highest-bid": "当前最高出价",
  "remaining-time": "剩余时间"
},

"new": {
  "guide": "为 <inlineAccount /><primary>申请一个新名称</primary> ",
  "unknown-error": "未知错误",
  "name": "名称",
  "name-placeholder": "Name.chain",
  "register": "注册",

  "notification":{
    "claim-sent": "{name} 已成功发送",
    "registered": "{name} 已成功注册",
    "unknown-error": "未知原因,{name} 未注册"
  }
}

},

“modal”: {
“confirm-sign”: {
“guide”: "签署原始交易
by ",
“data”: “数据签署”
},

"confirm-transaction-sign": {
  "guide-spend": "<primary>完成转账</primary><br />从 <senderAddress /><br />到 <recipientAddress />",
  "guide": "<primary>{title}</primary><br />by <senderAddress />",
  "payload": "Payload",
  "recipient-account": "收件人账户",
  "contract-compiled-code": "合约编译代码",
  "call-data": "调用数据",
  "contract-address": "合约地址",
  "commitment": "提交",
  "name-salt": "命名",
  "name-id": "名字ID",
  "name-fee": "Name fee",
  "pointer": "指向 #{n}",
  "pointer-key": "指向 #{n} key",
  "pointer-id": "指向 #{n} ID",
  "contract-create": "创建新合约",
  "contract-call": "调用合约",
  "name-pre-claim": "预备取名",
  "name-claim": "确定取名",
  "name-update": "更新名称",
  "name-transfer": "转移名",
  "confirm-message": "似乎余额不足,确定要继续吗?",

  "details-fee-input": {
    "title": "交易费用",
    "value": "{value} MICRO AE"
  }
},

"tooltips-modal": {
  "initial-header": "学习如何使用 Base æpp",
  "highlighted-region": "醒目区域",
  "initial-content": "点击任何 {0} 来了解它的功能。"
}

},

“components”: {
“address-panel”: {
“title-default”: “地址”
}
},

“network”: {
“connection-status”: {
“offline”: “您已离线,请检查您的网络连接。”,
“no-sdk”: “我们无法连接到您选择的节点。”,
“connecting”: “正在连接网络中…”,
“connected-to-testnet”: “您已连接到测试网。”
},

"settings": {
  "title": "连接网络",
  "subtitle": "网络ID {id}",

  "list": {
    "copy-link": "复制链接",
    "remove": "移除"
  },

  "new": {
    "title": "连接其他节点",
    "guide": "连接<primary>其他节点</primary>",
    "node-name": "节点名称",
    "node-url": "节点链接",
    "connect": "连接"
  }
}

},

“remote-connection”: {
“connect-notification”: “您已成功连接{0}”,
“revoke-notification”: “连接被成功撤销 {0}”,

"settings": {
  "title": "远程连接",
  "count": "没有设备连接| {n}设备已连接| {n}多设备已连接",

  "list": {
    "connected": "已连接",
    "disconnected": "未连接 {date}",
    "revoke": "撤消"
  },

  "new": {
    "title": "远程连接",
    "wrong-qr-code": "扫描的二维码错误。 请务必扫描Base æpp生成的二维码",
    "camera-not-allowed": "请允许 Base æpp 钱包访问您的相机。",
    "prompt-name": "命名此设备",
    "default-name": "重命名"
  }
},

"connect-guide": {
  "title": "如何连接 <primary>Base æpp</primary>",
  "steps": [
    "在你的手机上打开Base æpp: base.aepps.com",
    "创建一个账户,或登录",
    "去设置 <icon-settings />",
    "点击远程连接 <icon-device /> 并点击 ‘+’",
    "用Base æpp扫描下面的二维码"
  ]
},

"modal": {
  "cancel-sign": {
    "guide": "在Base æpp上 <primary>签署交易</primary>",
    "note": "打开你的Base æpp,检查交易细节并签署",
    "cancel": "取消交易"
  }
}

},

“security-courses”: {
“modal”: {
“guide”: “恭喜!您创建了一个帐户”,
“note”: “请花2分钟时间了解安全的重要性”,
“to-security-course-1”: “开始安全教程1”,
“skip”: “我稍后再做”
},

"settings": {
  "title": "AE 安全教程",
  "subtitle": "免责声明",

  "list": {
    "subtitle": "安全教程 {n}",
    "to-base-app": "前往Base aepp",
    "note": "在“设置”中随时可以重新访问教程"
  },

  "details": {
    "subtitle": "安全课程 {n} of {count}",
    "to-next": "前往教程{n}",
    "to-list": "教程概述",

    "intro": {
      "title": "介绍&免责声明"
    },

    "bank": {
      "title": "你是银行"
    },

    "privacy": {
      "title": "你的隐私"
    },

    "layers": {
      "title": "安全层",
      "setup": "下载使用 AirGap",
      "buy": "买一个 Ledger 钱包"
    }
  }
}

},

“settings”: {
“title”: “设置”,
“language”: “语言”,
“account”: “账户”,
“logout”: “登出”,
“logout-subtitle”: “下次再见!”,
“version”: “版本号”,

"mnemonic": {
  "title": "备份助记词",
  "subtitle": "保护您的资金",
  "guide": "<secondary>检查每个单词</secondary> 拼写 <primary>永远不要</primary> 截屏或者拍照保留。",
  "to-show": "显示助记词",

  "show": {
    "guide": "<primary>请妥善保管助记词</primary><keyEmoji /><primary>并注意安全!</primary><br />写下这12个单词并保存<alternative>在安全的地方</alternative>. 将来你需要它们来<secondary>恢复</secondary> 你的账号.",
    "alert": "这也太快了!请确保已在纸上记录助记词 ... 并保存在安全的地方."
  },

  "confirm": {
    "guide": "<primary>确认</primary><crossedFingersEmoji /></primary>你的助记词</primary><br />敲击以下单词来组成你的助记词, <secondary>注意</secondary>保持正确的先后顺序!",
    "mnemonic": "你的助记词",
    "error": "顺序不正确,请重试",
    "placeholder": "第一 第二 第三 ····"
  },

  "confirmed": {
    "guide": "是否<primary>从设备中删除</primary> 助记词? 这将会提供 <alternative>额外的安全</alternative>… 但不可以撤销.",
    "delete": "删除助记词",
    "keep": "保管助记词"
  },

  "deleted": {
    "guide": "助记词已删除. <secondary>请在删除之前查看备份.</secondary>",
    "back": "返回"
  },

  "notification": {
    "title": "请备份你的助记词!",
    "subtitle": "确保你的资金安全以防损失.",
    "to-security-course": "安全教程",
    "to-mnemonic": "立即备份"
  }
},

"password": {
  "title": "钱包认证",
  "subtitle": "设置和管理密码",
  "change": "更改",
  "change-subtitle": "更新你的密码",
  "choose": "选择",
  "choose-subtitle": "",
  "remove": "移除密码",
  "wrong-password": "错误密码,请重试",

  "set": {
    "change-guide": "更改你的密码",
    "choose-guide": "选择一个密码并进行确认。",
    "password": "密码",
    "password-new": "新密码",
    "password-new-confirm": "确认你的新密码"
  },

  "modal": {
    "guide": "输入密码以继续",
    "continue": "继续"
  }
},

"currency": {
  "title": "显示货币单位",
  "subtitle": "选择要显示的货币单位",
  "use-as-main": "交易的货币单位"
},

"account-remove": {
  "title": "同步钱包",
  "disconnect": "未连接"
},

"reset": {
  "button": "重置",
  "title": "重置密钥",
  "subtitle": "重置后,需要恢复助记词",
  "confirm": "如果你没有备份帐号, 你将不能再次登录. 你确定吗?",
  "title-desktop": "重置所有数据",
  "subtitle-desktop": "",
  "confirm-desktop": "你将会取消与Base æpp的连接并清除所有已保存的状态. 你确定吗?"
}

}
}

1 Like

The Movie about Generliazed account and State channel, which one submitted by Mark was translated by me, for this work I got 600 ae as reward form AE team, translation detail is listed as following.
1

00:00:02,000 --> 00:00:04,933

各位看视屏的朋友,大家好!

All right hello everyone whoever is watching this

2

00:00:05,067 --> 00:00:06,533

Ae社区你们好!

hello aeternity community

3

00:00:07,000 --> 00:00:07,400

By aechina

4

00:00:07,400 --> 00:00:15,433

我们邀请了两位令人惊奇的开发者Hans Svensson博士和 Dimitar Ivanov

We’re here with two of our amazing developers dr. Hans Svensson and Dimitar Ivanov

5

00:00:16,533 --> 00:00:25,600

我们将会简要讨论我们刚刚拥有的Fortuna 分叉版本引入的内容。

And we would like to talk very briefly about what was introduced by the successful Fortuna Fork We just had

6

00:00:26,533 --> 00:00:34,100

我们仅谈论一个主要的类比特征,我们将主要关注于两个发面。

waht are the main analogical features and for his and would like to focus primarily on two of the of those

7

00:00:34,500 --> 00:00:39,667

一个方面是Hans正在进行开发的广义账户

One is generalized the acounts on which Hands is working

8

00:00:40,234 --> 00:00:51,866

另一方面,我认为状态通道是相当令人兴奋的并很可能是工业上更好的一个。

and I think state channels which is aeternities of chain solution which is quite

exciting and most probably one of the better ones in the in the industry

9

00:00:51,933 --> 00:00:57,467

因此我想从Hans Svensson博士开始,

so I would like to start with with dr. Hans Svenson

10

00:00:57,500 --> 00:01:05,933

Hans Svensson博士是目前为止我所知的ae广义账户方面的主要人物

who is the primary figure as far as I can as far as I know in relation to

the general generalized the account implemented in aeternity

11

00:01:06,267 --> 00:01:13,000

ae广义账户是 Fortuna 分叉后引入的主要特征。

which is actually the primary feature that is being introduced by the the fortuna fork

12

00:01:13,134 --> 00:01:17,900

因此Hans就广义账户你有什么要与我们分享的?

so hands what can you tell us about generalife accounts

13

00:01:19,034 --> 00:01:28,067

是的,首先我必须说我实现了所有的设计,思考,它如何工作则由Msasha完成

yeah well first I have to say I’ve made the implementation all of the design

and thinking out how it should work is done by Msacha.

14

00:01:28,533 --> 00:01:31,300

当然是这后面的主要架构。

Of course main architecture behind this

15

00:01:31,800 --> 00:01:38,766

广义账户是一个非常棒的特征,在用户体验方面

but generalized accounts is a really nice feature mainly on the UX side

16

00:01:39,000 --> 00:01:42,900

它将会使人们的生活更加简单

It will make the life easier of people

17

00:01:43,300 --> 00:01:53,633

特别是你想要另一种方式签名aeternity交易时。

and especially when you want to have another way to sign your your aeternity transactions

18

00:01:54,000 --> 00:01:59,134

首先我们需要解释我们今天要做什么。

and and first we have to explain what we do today

19

00:02:00,000 --> 00:02:03,567

如果你有一个交易想要发送到aeternity上

And if you have a transaction you want to post to the Aeternity change day

20

00:02:03,633 --> 00:02:10,733

你需要做的是你必须创建一个账户, 这需要花费一些代币。

what you need to do is you have to create an account that is spending some tokens to an account

21

00:02:11,067 --> 00:02:15,533

你必须掌握那个账户的私钥,否则它就不是你的账户了。

you have to have the private key of that account otherwise it’s not your account

22

00:02:15,766 --> 00:02:26,633

为了事实上做一些事情,你必须拥有这个账户,你必须花费代币,然后签名交易

And in order to actually do something you have to have this account and you have to spend tokens

and then to sign the transaction

23

00:02:27,000 --> 00:02:37,200

你将会使用内置的加密原语,aeternity使用的EdDSA签名方案

you will use the built-in crypto primitives that that aeternity uses it’s an EdDSA signature scheme

24

00:02:37,500 --> 00:02:46,866

我们使用了一种曲线,我们称之为25519曲线密码学签名

we are using something which we call the curve two five five one nine curve cryptography signature

25

00:02:47,000 --> 00:02:54,334

这是一种标准的加密方案但并不是最广为人知的

which is standardized but not perhaps the most well known

26

00:02:54,500 --> 00:03:00,034

如果我们说比特币、以太坊它们使用的是另一种加密解决方案。

if we say Bitcoin etherium they use another another crypto solution

27

00:03:00,500 --> 00:03:07,500

为了发送交易你就需要这个方案

and then in order to to post you transact you need to sign using this this scheme

28

00:03:08,167 --> 00:03:14,334

这并不是一个问题,因为我们有工具来实现这一方案,我们对所有东西都有

HTTP API

normally that’s not a problem there are tools for this then we have HTTP API for everything

29

00:03:15,000 --> 00:03:32,766

但如果你想实现其它东西或来自另一个世界,想要拥有一种不同的加密方案

来签名交易在,当然,当前情况下是不可能的。

but if you want to have something or well if you come from another world where you have want to have and I

want to have a different cryptography scheme for signing your transactions that is currently not possible of course

30

00:03:33,000 --> 00:03:45,034

因为我们决定了加密方案,我们不能在节点上完全建立它们

Because well we decided on one solution and we can’t we can’t really

build all of them into into there into the nodes

31

00:03:45,034 --> 00:03:59,966

替代方案是将签名检查放入合约,这样你就可以将所有你喜欢的加密原语写入合约了

and so the idea is then instead to move the signature checking into into contracts

such that you can write up whatever crypto primitives you’d like in a contract

32

00:04:00,433 --> 00:04:11,900

当然理论上你可以这么做,我指的是solidity,但是需要另一个账户来发起合约。

and and of course you can you can do this also say on a theory I mean solidity

but then you would have to have yet another account in order to call that contract

33

00:04:12,500 --> 00:04:28,633

因此我们用广义账户做的事情是我们用合约直接连接账户,

并用合约替代账户的签名检查

so what we’re doing with generalized accounts is that we are basically attaching a contract

directly to an account and in effect replacing the signature check for that account by contract

34

00:04:29,500 --> 00:04:43,000

它基本就是用合约来签名交易

so you can yeah basically what it is that of signing your your transaction with the we have

35

00:04:43,167 --> 00:04:51,000

并代替你为合约提供加密数据或数据

yeah yeah and instead you provide crypto data or data for this contract

36

00:04:51,000 --> 00:04:56,833

这个合约可以确定你是否成功签名了交易

so that this contract can decide whether you have successfully signed your the transaction or not.

37

00:04:57,500 --> 00:05:13,500

好的,因此这提高了钱包的灵活性。换言之,

你可以在很短的时间内拥有多个拥有不同的密码签名方案的账户。

okay so this this improves the flexibility of wallets it is can in once like very short sentence

you can have a accounts which use these different cryptographic signing schemes

38

00:05:13,500 --> 00:05:19,000

是的 它不止是两种加密签名方案,你可以拥有一整套其它内置限制条件。

yes and it’s not all about two cryptographic signing schemes you can have all sorts of other built-in limitations

39

00:05:19,400 --> 00:05:28,667

我知道有些钱包正在拓展限制,比如你可以直接部署附加在钱包上的合约。

I know wallets which have spending limits for example and that you can also of course

then implement directly in this this contract that is attached to them.

40

00:05:28,766 --> 00:05:33,200

好的,好的,这同样提高了账户的灵活性。

okay okay so also prove the flexibility of accounts

41

00:05:33,500 --> 00:05:49,567

是的,我们还有另一个应用程序,我们也有硬件来做这个,

硬件有一个内置算法,但这个算法不适合aeternity

yes and then then we also have another application there are there were there’s Hardware around for

for doing and that hardware has one algorithm built-in and that might not be the one we use it in aeternity

42

00:05:49,800 --> 00:06:01,833

因此为了在aeternity上使用这个硬件,你可以在合约中实现这个加密方案,

并与账户相连,

so in order to be able to use this Hardware together with aeternity then you can

implement that crypto scheme in a contract and attach it to come into an account

43

00:06:01,900 --> 00:06:07,833

突然间,你就可以用硬件为aeternity进行交易签名了。

and you can all of a sudden be able to use your hardware device

for for signing transactions directly for for aeternity

44

00:06:08,000 --> 00:06:09,300

这确实非常有意思

this is actually very interesting

45

00:06:09,300 --> 00:06:12,933

我有一个疑问因为我确实不知道这个问题的答案

you know I have a question because I actually don’t know the answer to this one

46

00:06:12,933 --> 00:06:24,533

我担心支持aeternity账户的广义账户被更多的硬件管理,

更贴切的说是更多类型的硬件钱包

so I kind of fear that generalised accounts enable the aeternity accounts to be managed

by more hardware devices let’s say more types of hardware wallets

47

00:06:24,533 --> 00:06:40,367

但这种情况与其它区块链的情况不同,这些区块链可以用其它不同的硬件进行管理,

例如比特币和以太坊的硬件钱包。

but isn’t the kind of a case with for example other block chains which are I mean also managed they

are available on other different kinds of hardware wallets for example Bitcoin and etherium ones

48

00:06:40,400 --> 00:06:49,900

如果有一个硬件钱包支持比特币和以太坊,它们使用一种加密签名

if there is a hardware wallet this hardware wallet will support them

and if they use one like one cryptographic signature

49

00:06:50,000 --> 00:07:03,700

硬件钱包该如何支持比特币和以太坊,或改怎么样处理,差异是什么

how is this possible like does the hardware wallet kind of is custom-built so

to say to support them or what is what is the like what is the difference

50

00:07:03,700 --> 00:07:09,766

为什么以太坊和比特币需要广义账户不需要被硬件钱包支持。

why why don’t for example etherium and Bitcoin need generalised

accounts to be supported by hardware wallets

51

00:07:10,034 --> 00:07:21,467

硬件钱包只是一个签名装置,因此需要数据,需要钥匙来签名

well the hard wallet is not much more than a signing device

so it takes data and it will take a key and it will sign it

52

00:07:21,500 --> 00:07:29,533

这准确来说它并没有使用任何东西

and that signature is what exactly what’s what they are all

using well nothing yet nothing experts really really needed

53

00:07:30,966 --> 00:07:35,200

问题是如果你想在aeternity分叉前使用它

so the problem would be if you want to use that on aeternity before the hard fork

54

00:07:35,234 --> 00:07:42,933

在你必须拥有一个普通aeternity账户之前你可以通过广义账户来实现

now you can do it with generalized accounts before you would have had to have a normal aeternity account

55

00:07:42,933 --> 00:07:45,234

你不能为此创造签名,关键是硬件实现的加密算法

and you can’t create signatures for that

56

00:07:47,800 --> 00:07:56,267

关键是硬件实现的加密算法

it’s all about which algorithm to the crypto that the hardware in question actually implements.

57

00:07:56,400 --> 00:08:02,833

因此,现在支持aeternity硬件设备变得更容易了,容易很多

okay so now it would be much easier to support aeternity hardware device much much more easier

58

00:08:03,167 --> 00:08:15,700

将来将其他加密算法加入aeternity同样会变得简单

因为我们不需要把它加入核心算法

yes and and also if there are other cryptography things which pops up it’s also will be easy

for aeternity to add them in the future because then we don’t need to add it to the core algorithms

59

00:08:15,800 --> 00:08:29,100

我们只需将它加入Sofia语言和运行在AE上的虚拟机中。

we just need to add it to the to the language and to the to the Language

you feel this right to Sofia and to to the virtual machine running

60

00:08:29,500 --> 00:08:40,966

好的,很好,牛逼,非常感谢您的分享,我已经和一些伙计讨论过广义账户

okay great great thank you for thank you for this actually kind of

because I’m have talked about generalized accounts with a few people already

61

00:08:41,367 --> 00:08:57,134

这确实非常有用,是的,我认为讨论和问问题

对于任何人理解广义账户的优势最好的方式。

but this was actually a very useful very useful explanation and yeah I think talking and asking the question

is the best way forward for anyone understand what these one of the advantages of generalized accounts is

62

00:08:57,167 --> 00:09:04,567

接下来让我们离开一会,我们将注意力转移到状态通道上,我对状态通道超级兴奋。

but let’s move for for just a little bit to state channels which I’m super excited about

63

00:09:04,900 --> 00:09:18,633

我认为状态通道是重大突破,我很期待aeternity上第一个实现

状态通道的aepp,因为我能想到很多。

and I I think there are like major breakthrough and I’m looking forward to the first apps

that actually implements the channels on aeternity because I can think of a number of those

64

00:09:18,833 --> 00:09:35,334

但我将会把话题交给Demeter来帮助我们了解利用状态通道做了什么

以及在下一个阶段Fotuna的到来上我们应该期待什么

but yes I will give the word to Dimitar to kind of help us yeah inform us what has been

done with the channels and what should we expect in the next Fortuna The Fortuna release.

65

00:09:35,467 --> 00:09:47,700

我说的释放的意思是3.XX版本的释放,下一次硬分叉该版本将会到来,

预计会发生在九月。

so when I said turn releases I mean the three the three points xx releases which are

coming up up to the next scheduled hold forth which will happen in September

66

00:09:47,733 --> 00:09:48,933

Dimitar请开始你的表演。

so the Dimitar yes

67

00:09:48,933 --> 00:09:57,433

好的,状态通道会是相当复杂的话题,内容相当广泛

okay so channels can also quite complex topic and they’re really wide in there

68

00:09:59,500 --> 00:10:01,234

不。。。

No…

69

00:10:05,000 --> 00:10:06,800

你回来了

now you’re back

70

00:10:16,000 --> 00:10:19,000

是的,现在可以运行了

yes now it’s working

71

00:10:19,500 --> 00:10:24,567

外面的风暴很可能影响了我的连接。

there’s a storm outside so this could probably interact with my connection

72

00:10:24,633 --> 00:10:28,034

好的,让我们开始

okay let’s do it

73

00:10:32,000 --> 00:10:41,567

真不好意思。我不想说太多。

so sorry so channels I don’t want to go really they can go, yes, because it’s going to be pretty long go

74

00:10:41,933 --> 00:10:49,766

在同道中有状态机可以为用户处理所有繁杂的工作。

but in channel we have this state machine that actually handles all the heavy lifting for the user.

75

00:10:50,100 --> 00:11:01,367

无论何时Alice在链下提供一个智能合约或智能合约代码,状态机会检测它是否有效

so whenever Alice offers smart contract or a code of a smart contract off chain

the state machine says if it is a valid one or not

76

00:11:01,733 --> 00:11:09,633

工作量巨大,但仍然在开发之中

and it does a ton of work but it’s still in a work-in-progress state

77

00:11:10,367 --> 00:11:18,533

需要更多的API,这意味着需要更稳定的途径来创建链下共识,等等。

so it needs more apis. it means it needs more stable approach for building consensus off chain and etc.

78

00:11:19,100 --> 00:11:27,533

这是正是我们为Fotuna做的事情,我们为合约的创建或唤醒添加了大量的API

so this is exactly what we’ve done for Fortuna we’ve added a ton of new API is

for creating contracts or calling them and etc

79

00:11:27,766 --> 00:11:35,900

我们努力工作以为合约的运行提供更为稳定的环境。

we’ve worked intensively into providing more stable environment for running those contracts

80

00:11:36,000 --> 00:11:49,000

关于通道有趣的事情是无论Alice何时提供一个合约代码,

我们假设是在链上利用预言机,他们需要对链有相同的看法。

the funny things about channels is that whenever Alice offers a contract code let’s say

they use an Oracle on chain and they both should share the same view of the chain

81

00:11:49,267 --> 00:11:59,766

如果Alice的机器领先Bob的几个区块,Bob就会

拒绝她有效的合约调用,链下合约调用

so if Alice machine is a few blocks ahead from Bob’s for example Bob

is going to reject her valid contract call off chain contract call

82

00:11:59,866 --> 00:12:18,533

这并不是正确的做法,我们已经在无需Alice提供调用的原数据的

情况下改进了这一现象。比如在链下更新时Alice的态度。

and this is not the way to go and we’ve improved this without Alice to provide some metadata about

her call like how she sees the the blockchain at the point of making the off-chain update

83

00:12:18,600 --> 00:12:25,400

如果Bob在网络上看到了同样的信息,那么他们继续交易是安全的

so if Bob sees the network the same way it would be safe for them to continue

84

00:12:25,500 --> 00:12:37,600

但是如果Bob没有分叉或其他东西或他所看的区块提前或落后于他人

或者是其他任何令人不高兴的事情,Bob依然可以拒绝。

but if Bob isn’t on fork or something or seeing just network few blocks ahead or behind

or whatever Bob might not be happy with that and Bob can still reject

85

00:12:37,933 --> 00:12:54,766

当我们正式引入虚拟状态通道时这将会非常便利

因为共识对双方、所有参与方都很重要

this would be really handy when we actually start introducing virtual channels because

consensus there will be really important for for both parties for all parties actually

86

00:12:54,900 --> 00:13:00,267

不仅仅是双方而是对虚拟状态通道里的所有参与方都非常重要。

not just for the two but for all the included parties in the virtual channel

87

00:13:00,633 --> 00:13:02,567

是的,我们了解这一点。

yes of course we understand it

88

00:13:02,633 --> 00:13:12,966

在你完成工作之后,现在状态通道主要由开发者使用

this is your work is now like after state channel they’re out there they can

be used by primary by developers at this point

89

00:13:13,000 --> 00:13:25,733

你正在做管理类的工作以使状态通道更用户加友好,非常友好。

you are now kind of do some some housekeeping which would allow there used to be to

become much more user-friendly basically took to make magical friendly

90

00:13:25,866 --> 00:13:35,200

状态通道不会被日常的使用者使用,

它们将会被开发者用来提供服务。

still a point there state channels are not going to be used by the everyday user

there will be they will be used by developers to provide services

91

00:13:35,633 --> 00:13:36,433

是的

yes

92

00:13:36,733 --> 00:13:44,000

我更希望你有一个使用状态通道的aepp,使用者可能不会真正理解

I’m more of like you have an app that uses the channels the user won’t actually maybe understand

93

00:13:44,034 --> 00:13:47,067

使用者不会真正理解这些,这是理想状态。

he won’t know the user won’t know that’s the that’s the ideal

94

00:13:47,367 --> 00:13:49,500

这是最佳情况。

this is the best-case scenario is

95

00:13:49,800 --> 00:13:55,034

如果用户必须知道状态通道怎么工作,我们用户量就会很少

if the user has to know how channels work we have really small proof users

96

00:13:55,567 --> 00:14:00,633

是的,我们确实尝试使状态通道简单易用。

yes exact it’s also we’re trying to make it easy to use their channels

97

00:14:00,633 --> 00:14:11,900

使用户不知道他们正在使用状态通道,而使开发者确实

知道什么正在发生,因此没有未曾设想到的边界情况

as to make it possible for the user actually not knowing that they’re using state channels and

for the developer to actually know what’s happening and so that there are no edge cases

98

00:14:12,000 --> 00:14:17,900

这些状态通道并不按他们所想象的那样工作

that have not been envisioned and these state channels don’t actually work as they’re supposed to be exactly

99

00:14:18,000 --> 00:14:29,067

是的 这就是我们即将引入链下争端解决方案的原因。

Exactly and that’s why we are about to introduce really complex handling off chain disputes

100

00:14:29,267 --> 00:14:36,567

就像Alice尝试在链上作弊,节点会提醒Bob的时候Bob是如何知道这件事的呢

like Alice tries to cheat on chain so how Bob is going to know when the node is going to inform Bob for that

101

00:14:36,766 --> 00:14:42,200

节点会给Bob提供下一步他所能做的事情的选项来保护他自己

and it’s going to provide him with options what he can do next to protect himself

102

00:14:42,500 --> 00:14:54,733

因此我们付出了很大的努力来为关闭漏洞提供更多的支持,这将使边界事件被掌控

so we’re working heavily in that direction into providing more support for closing called loopholes

that are left all the edge cases to be handled

103

00:14:54,833 --> 00:14:57,633

因此用户可以安全地构建aepps

so users can safely build apps

104

00:14:57,866 --> 00:15:05,467

基本上开发者可以标记已经可以稳定使用的状态通道。

basically developers that can do taps that consume the already stable state channels

105

00:15:05,733 --> 00:15:10,533

卧槽,很好。我有一个问题,因为你提到了节点

yes great and I just have one question because you mentioned the node

106

00:15:10,633 --> 00:15:27,200

有没有一个计划或我们该如何解决这个问题,

用户在没有运行节点的情况下使用状态通道

Is there is there a plan or how we can address this I will call like issue but a requirement for

each user the has a that is wants to use their channels to use them without actually running a node

107

00:15:27,334 --> 00:15:33,367

依赖于别人获得信息,我猜测你将会被出卖。

I guess this will be sold by relying on somebody else is not for the for the information

108

00:15:35,100 --> 00:15:39,966

目前 最好的方案是获得自己的节点

at the current point the best case scenario for you is to earn your own nodes

109

00:15:39,966 --> 00:15:48,467

长期来看 我们将会热于看到客户不依赖于任何节点

in the long run we would love to see completely not less clients that do not depend on any node

110

00:15:48,567 --> 00:15:57,433

他们只是依靠不同的节点来达成链当前状态的共识。

they just bring different nodes build their consensus about what the chain looks like at this moment

111

00:15:57,533 --> 00:16:10,633

大量的节点会出现不同的结果 可能在链下,可定是链下,但有可能是链上,

也以上链上查询

Thinking a lot of nodes for that getting different results building maybe off chain

definitely off chain but maybe on chain as well for certain on chain lookups

112

00:16:10,966 --> 00:16:19,866

因此这会变得很复杂,目前我们将所有复杂性都内置到了节点中

so this is going to be really complex and so far we’ve put all that complexity inside the node yes

and we keep it there

113

00:16:20,000 --> 00:16:29,533

但这极度依赖于使用可信赖的节点 因此用户最好使用自己的节点

but this heavily depends on using a trusted trusted node so users better use their own nodes

114

00:16:29,533 --> 00:16:42,334

好的,买一个二手电脑像Power个人电脑然后运行aeternity的节点

okay well actually buying a secondhand computer like a Power PC

and then running an aeternity to node there

115

00:16:42,500 --> 00:16:55,900

并允许对闪电网络持相同观点的任何人拥有一个任何人都可以使用的轻节点,

命名它为flat down或其它任何名字

and allowing anyone who is the same idea with the Lightning Network to have a node lightly node

that anyone can use maybe name it flat down or whatever

116

00:16:55,933 --> 00:17:06,966

然后任何人都能连接这个节点,并知道我为他们证明了这个信息,

但是当然更好或最好是使用自己的节点

and then anyone can connect this one and know that I’m providing this information

for them but of course it’s always always better or always best to use your own notes

117

00:17:07,134 --> 00:17:10,500

是的,谢谢你俩的分享。

and yes thank you both for this

118

00:17:10,500 --> 00:17:23,933

即将到来的Fortuna版本还会带来另一个非常有意思的更新,

它与fate虚拟机有关,但是我们没有人能讨论它

Actually there is one more very interesting like like update that is coming with Fortuna

but it’s related to the fate virtual machining

but we don’t have a person here to talk about this

119

00:17:24,167 --> 00:17:30,433

因此我只是想提醒一下,并且如果你们并不是你们,但社区却学到了更多。

so I just wanted to mention and if if you guys are not you too but the community was learning more

120

00:17:30,467 --> 00:17:35,966

Eric为开发者大会写了一篇非常好的文章

we have a very nice article by Eric for the we are developers conference

121

00:17:36,034 --> 00:17:44,567

我们同样在论坛有一些关于快速交易引擎的信息,

当然在博客上也有,我对此也非常期待

and we also have some information that in in the forum and also in the

in the blog about Fate and I’m also looking for that very much

122

00:17:44,633 --> 00:17:50,067

再一次感谢你们的分享没有像代码那么简短

so thank you again for this not as short code as I mentioned that

123

00:17:50,267 --> 00:17:54,234

我们面前的两位是信息量非常大的家伙

but we bring very informative guys

124

00:17:57,200 --> 00:18:00,966

好的,非常感谢你们陪我开车,再见。

yeah all right thank you very much and see you around bye bye see ya bye

125

00:18:01,134 --> 00:18:03,034

再见,下次再一起开车。

See you.

1 Like

This video and the translation of Baese aepp did come from our small team.

https://www.weibo.com/tv/v/IcYsjv58v?fid=1034:4430921466598229

1 Like

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

This campaign has been approved. No need for the call. Just FYI the devs are still making some refinements on the white paper. If all goes smoothly, the final version will be out early January. So there might still be minor changes to the white paper by then. Thanks and talk to you soon!