首页 > 小蚁(前Antshares) > 正文

NEO的下一步发展计划 | What's Next for NEO

NEO智能经济 2018-07-14 21:35

  去年,我们在NEO社区的支持下完成了NEO 2.x的开发,NEO 2.x主要为NEO智能经济提供核心架构机制。现在又到了向前看的时候了,该考虑下一步计划了。下一步要做什么呢?简而言之,就是NEO 3.0,NEO 3.0的开发工作从上个季度(2018年第二季度)就开始了,已持续至今。

  In the past year, together with the NEO community, we accomplished the development of NEO 2.x. NEO 2.x provided essential infrastructure mechanics of the NEO Smart Economy. Now, it's time to look ahead. What's next? The short answer is NEO 3.0, of which development started in the last quarter (Q2 2018).

  NEO 3.0到底是什么?又包含哪些关键功能?今天就由NEO创始人兼核心开发者张铮文与大家分享NEO 3.0的最新功能与改进之处。

  What is NEO 3.0? What are the key features of NEO 3.0? Today, NEO founder and core developer Erik Zhang shares with us the latest features and improvements of NEO 3.0.

  张铮文:

  NEO3.0是一个全新版本的NEO平台,专门服务于企业级大规模应用。NEO 3.0具有较高TPS与稳定性,并提供智能合约扩展API与优化的经济与定价模型。最重要的是,NEO 3.0将彻底整改NEO的核心模块设计。

  Erik Zhang:

  NEO 3.0 will be an entirely new version of the NEO platform, built for large scale enterprise use cases. It will provide higher TPS and stability, expanded APIs for smart contracts, optimized economic and pricing models, and much more. Most importantly, we will entirely redesign NEO's core modules.

  1. 多方位改进

  1. Various Improvements

  1.1 提升TPS

  1.1. Increasing TPS

  要想在NEO上大规模运行分布式应用,就得提升TPS。我们将通过以下方式提升NEO 3.0的TPS。

  Increasing the TPS is important if we want to run large-scale distributed applications on NEO. In NEO 3.0, we will increase the TPS in the following ways:

  重构代码与核心模块

  优化网络协议

  实现NeoContract的功能清单与权限系统

  进行动态分片准备

  离状态数据持久存储与区块数据持久存储

  Refactor the code and core modules

  Optimize the network protocol

  Implement the feature manifest and permission system for NeoContract

  Prepare for dynamic sharding

  Detach state persistence and block persistence

  1.2 漏洞修复

  1.2. Bug fixes

  在NEO 3.0中,我们将修复某些已知漏洞,并大幅提升系统的稳定性。

  In NEO 3.0, we will fix some known bugs and significantly improve system stability.

  2. 协议

  2. Protocol

  2.1 调整经济模型

  2.1. Adjusting the economic model

  过去,NEO使用的是双币经济模型,该模型显然是成功的,但仍然存在以下问题,如NEO不可被分割使用,且GAS在支付系统费用时也不可被分割使用。这些问题阻碍了NEO和GAS代币效用的发挥。为了解决这个问题,需要对这一经济模型进行调整。下面是一些可能的调整方案:

  We designed a dual-token economic model for NEO, which has proven to be a very successful model. However, there were also problems: NEO was indivisible, and GAS could not be divided when paying for system fees (sys_fee). These issues were roadblocks for the utility of NEO and GAS tokens. To solve this problem, some adjustments to the economic model need to be applied. Some of the possible adjustments are:

  每年小幅提升GAS的供给量

  奖励共识节点

  使NEO可分割使用

  用GAS支付系统费用时允许精确到小数位

  A small increase in the supply of gas every year

  Reward consensus nodes

  Make NEO divisible

  Allow gas to use the decimal part when being used for system fees

  (以上仅为建议,该议题目前仍在讨论中,详见 https://github.com/neo-project/neo/issues/285)

  (This is suggestion only. This issue is being discussed at: https://github.com/neo-project/neo/issues/285)

  2.2 调整系统定价模型

  2.2. Adjusting the system pricing model

  对于开发者来说,昂贵的系统费用是其主要担忧。我们将对NEO 3.0的定价模型进行调整,这样可以大幅削减智能合约的运行与部署费用。

  For developers, expensive system fees have become a primary concern. In NEO 3.0 we will make adjustments to the pricing model so that the cost of running and deploying smart contracts will be significantly cheaper.

  3. 智能合约

  3. Smart Contract

  3.1 跨平台智能合约

  3.1. Cross-platform smart contracts

  如果智能合约能与NEO 3.0兼容,应该就能跨区块链平台执行。为了达到这一目标,我们不仅需要NeoVM的支持,也需要统一的智能合约API。此外,还需要一个专门的API进行平台检测。

  Smart contracts should be able to be executed on different blockchain platforms, if they're made compatible with NEO 3.0. To achieve this, we need not only NeoVM support, but also unified smart contract APIs. In addition, we also provide an API for platform detection.

  System.Runtime.Platform

  System.Runtime.Platform

  便于智能合约在运行时检测当前的平台。

  This allows the smart contract to detect the current platform at runtime.

  3.2 功能清单与权限系统

  3.2. Feature manifest and permission system

  部署智能合约时,必须清楚地阐述它可以调用的功能和权限。智能合约在运行时可访问的功能与权限仅限于其所展示的功能与权限清单中所列的内容,且不得执行任何清单之外的行为。

  When a smart contract is deployed, it must explicitly declare the features and permissions it will use. When it is running, it will be limited by its declared list of features and permissions, and cannot make any behavior beyond the scope of the list.

  3.3 原生合约

  3.3. Native contracts

  原生合约指不能在虚拟机上运行的智能合约。但原生合约可直接嵌入区块链代码,且仍可向其他合约展示其脚本,供其他合约调用。

  Native contracts are smart contracts that are not run in a virtual machine. Instead, it's built directly into the blockchain code. Native contracts can still expose their script hashes to other contracts, so that other contracts can invoke them.

  原生合约的一个用途是把NEO、GAS(和所有全局资产)变成NEP-5标准的资产。

  Native contracts can allow for the interaction with NEO and GAS (and all global assets) as NEP-5 tokens. This introduces a unified approach for sending and receiving assets in smart contracts.

  3.4 回调API

  3.4. Callback APIs

  为智能合约创建回调函数或系统调用指令,并允许其他合约通过回调函数执行任务,可与迭代器兼容。

  Create callback functions for smart contracts or SYSCALL, and allow other contracts to perform tasks through callback functions, which can work with iterators.

  3.5 其他新的API

  3.5. Other new APIs

  我们还将给NEO 3.0添加一些新的API,如下所示:

  We will add some new APIs to NEO 3.0. Some APIs that may be added:

阅读更多

上一篇:简报 | NEO创始人达鸿飞出席亚布力青年论坛创新年会

下一篇:NEO去中心化时代的开启 | NEO Entered the Era of Decentralization

您可能喜欢:

关于我们联系我们作者投稿
Copyright © 2013 比特巴手机版
币圈人都爱上的网站,新闻行情教程人物测评资讯大全