版权声明：

以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，译者Lochaiching。转载必须保留以上声明。仅授权原文转载。

本文原文链接为https://forums.eosgo.io/discussion/747/article-xi-v0-3-0-draft-eos-io-constitution-developers-and-smart-contract-licenses，Thomas Cox在EOS GO社区中更新了宪法草案第十一条的内容，由本号“EOS技术爱好者”翻译。

---

Article XI - v0.3.0 Draft EOS.IO Constitution - Developers and Smart Contract Licenses

第十一条：0.3.0版本EOS.IO宪法草案——开发人员和智能合约许可证

license-2859796_640.png

Thomas Cox

Purpose

Defines when a Member is a Developer. Establishes obligation of a Developer to provide a License and one or more Ricardian Contracts, and to name an Arbitration Forum for their software.

目的

定义什么程度的成员才是开发人员。设定开发人员有义务提供许可证、李嘉图合约（一个或多个），并为他们的开发软件任命一个仲裁法庭。

Text of Article

Each Member who makes available a smart contract on this blockchain shall be a Developer. Each Developer shall offer their smart contracts via a license, and each smart contract shall be documented with a Ricardian Contract stating the intent of all parties and naming the Arbitration Forum that will resolve disputes arising from that contract.

本文内容

每一个在区块链上提供智能合约的成员都应该是开发人员。每一个开发人员都应通过许可证来提供他们的智能合约，每一份智能合约都应记录在一份说明各方的意图的李嘉图合约中，并指定解决该合约纠纷的仲裁法庭。

Discussion

It's not clear at the Constitutional level what happens, or what should happen, in cases where code is published but no License is provided, or when no Ricardian Contract is provided. The EOSIO Software doesn't require either at the code level. Arbitrators will be required to figure out how to handle such cases.

A Member who is considering running someone's software should be wary of software offered without a clear License and without any Ricardian Contract(s).

It's certainly possible for the License terms to be referenced by, or even contained entirely within, the Ricardian Contract(s). That might be a good practice.

讨论

在代码发布但没有提供许可证或李嘉图合约的情况下，从宪法层面上不清楚发生什么，或应该发生什么。EOSIO软件在代码级别方面也是一样。仲裁员则被要求找出如何处理这种情况。

要是正在考虑运行某软件，应该警惕没有明确许可证和没有任何李嘉图合约的软件。

许可条款当然有可能被李嘉图合约引用，甚至完全包含其中。这可能是个很好的实验。

References

None yet.

参考链接

还没有

(all opinions are my own)

（所有的观点都代表我自己）

---

本文内容不代表本号任何立场

本文图片来源于网络

本文原文链接为https://forums.eosgo.io/discussion/747/article-xi-v0-3-0-draft-eos-io-constitution-developers-and-smart-contract-licenses，作者Thomas Cox，译者Lochaiching。转载请参照本文文首说明。

相关文章：

李嘉图合约究竟讲了什么 https://steemit.com/eos/@eoshenzhen/6ipbwb

通过仲裁流程的例子看社区治理理念 https://steemit.com/eos/@eoshenzhen/eos-gov

包含BP选举的社区为什么需要治理这一环 https://steemit.com/eos/@eoshenzhen/eos-gov-bp

更多内容，加入我们的知识星球吧～

WechatIMG2975.jpeg