译文/Translated：
Block.one信奉开源的创新模型，它能让我们和其它EOSIO开发者社区的同仁能够携手推进行业和EOSIO™软件的潜力。
我们一直积极探索的一个领域是EOSIO钱包生态系统和密钥及密码管理的方向。利用区块链技术，钱包（作为密钥管理者）保证用户可以安全地使用区块链应用。我们想实现大规模推广基于区块链的软件，它们的存在就至关重要，所以它们也是我们研究的一个重点。
思考良久之后，我们决定要公布可以在现有的EOSIO钱包上使用的密钥管理。这就意味着，Block.one不是现在就要发布自己的钱包，正相反，我们想用这个机会发布我们作为开源软件做的一些工作，我们希望借此推动改进现有钱包生态系统的标准。未来我们会陆续发布一些repo来和Block.one以及创新的社区分享，而其中第一篇就是关于这项工作的介绍：EOSIO Labs™。
我们很高兴地宣布EOSIO Labs计划。当我们在EOSIO家庭创建新的工具、影响全球的开发者社区的时候，我们意识到我们有必要区分几个事情：我们正在开发的内部产品、我们打算发展的软件工具、我们未来要发表获得EOSIO社区成员反馈以了解他们带来的价值的其它研究项目。
EOSIO Lab发布：通用认证库
我们在此宣布，我们要打开认证库（UAL）源代码的GitHub存储库。EOSIO Lab计划的第一步是通过编写一个单一、通用的API从而让app开发者集成到一个认证器（钱包、应用程序浏览器、密钥管理器等）。此外，它还给开发者提供一个可选但统一的UI界面，这样用户就能获得他们在用的钱包或所在的网站 一致的外观和感受。
过去一年，EOSIO生态系统不断发展，我们也一直在研究怎么能让EOSIO支持的应用能够和钱包交互、这又会给开发者和用户体验带来怎样的影响。不管是软件还是硬件上来看，钱包的数量都有了爆炸式的增长，这就给了用户一个非常用价值的东西：创新和选择。
但随着钱包的数量增加，问题也随着而来。App开发者必须和所有这些钱包的API集成（或者放弃、选择不继承），而交易签名的增加和分化，最终用户面临着更多不确定，甚至是混乱，的局面。选择的钱包最终让他们郁闷、可能是碎片化的、规模化应用也遭到阻碍，这样的情况下，他们可能觉得他们想用的那个app完全不能用。
这项工作表明我们的方向和思考，现在它开放给整个社区检查和思考它在其它开发工作流程中的使用方法。我们希望能收到您的反馈，也会在未来继续探索和发表更多相关工作。
使用EOSIO Labs储存库
EOSIO Labs计划的目标是更快地把我们的创新和发现和所有的开发者分享，从而增加这些创新能给EOSIO社区带来的价值。EOSIO Labs下项目的开源库被认为是alpha版本，Block.one不保证将来一定会参与。它会不会继续贡献和参与取决于整个社区对这些项目的采用度。
EOSIO Labs存储库是实验性的。我们鼓励社区的开发者使用EOSIO Labs储存库（在MIT许可下发布）作为代码和概念的基础融入他们的应用。我们还鼓励社区成员贡献和进一步发展这些储存库。但因为这些储存库不是由Block.one支持产生的，我们可能不会回应如下需求：发布报告、提取请求、功能更新，等其它的要求，我们希望社区能够对此负责。但是，根据EOSIO Labs内的概念和代码库的使用情况，某些特定的代码库和概念可以从这里毕业，它们会逐渐升级，获得我们的支持，让它们能够走得更快。作为EOSIO Labs的毕业生，它们能够获得我们觉得必要的支持，正如我们给维护EOSIO开源库（Demux, EOSJS等）和其它的支持一样。
联系我们
如果您想给我们提供反馈或者和我们团队合作，共同为开发者改进EOSIO Labs储存库，您可以给我们的开发者关系调组发送邮件developers@block.one。
您还可以在EOSIO Developer Portal订阅我们的邮件列表，获取我们最新的消息。我们很高兴能够步段为EOSIO开发者改进软件的可用性，为区块链的大规模应用奠定基础。
EOSIO Labs的明亮未来
通过EOSIO Labs, Block.one将继续发布我们对密钥和密码管理的想法和研究。这是我们作为社区一份子想解决的诸多问题中的其中一个而已，我们欢迎并鼓励您对有兴趣的领域进行探索，并期待不断发展成世界上最有活力和创新的技术社区之一。
免责声明
Block.one作为EOSIO社区的一员，自愿做出自身贡献，并不对软件的总体性能及任何相关应用程序负责。对于此处所述版本以及相关GitHub版本或EOSIO软件，我们不作任何明示或暗示的陈述、保证、担保或承诺，包括且不限于提供担保，保证适销性或对某一特定目的和非侵权的适用性，并不承担相应的责任。在任何情况下，无论是合约操作、侵权行为或其他，亦无论是否与软件或文档相关，或由于软件使用导致，或在软件和文档上的其他交易导致的任何索赔、损害赔偿或其他债务，我们均不承担责任。任何测试结果或绩效数据具有指示性，无法反映所有情况下的绩效。任何对第三方或第三方产品、资源或服务的引用都不受Block.one的认可或推荐。对于您使用或信任这些资源的行为，我们概不负责，并且不承担任何责任和义务。第三方资源可能随时更新、变更或终止，因此此处的信息可能已过期或不准确。
原文/Original：
At Block.one, we believe in an open innovation model that allows us and others in the EOSIO developer community to collaboratively push the boundaries of what is possible within the industry and EOSIO™ software.
One area we have been actively exploring is the EOSIO wallet ecosystem and the direction of key and password management. In blockchain, wallets (as key managers) serve a critical role in the way users interact securely with blockchain applications. They are a pivotal component in the path towards mass adoption of blockchain-based software and have been a focus of much of our research.
After much consideration, we have decided to release our work related to key management in a way that can be used by existing EOSIO wallets. That means Block.one itself will not be releasing a proprietary wallet at this time. Instead, we are taking this opportunity to release our work as Open Source Software, and by doing so hope to encourage ongoing improvements of the standards in the wallet ecosystem. We will be releasing this work as the first in a series of repos in a form we’re really excited to share for both Block.one and community innovation: EOSIO Labs™.
We are pleased to announce the EOSIO Labs initiative. As we create new tools in the EOSIO family that impact the global community of developers, we have come to recognize the need for a clear distinction between in-house products we are committed to developing, software tools we are committed to growing, and research projects we would like to publish for feedback from others in the EOSIO community to help understand the value they can provide.
EOSIO Labs Release: Universal Authenticator Library
With this announcement, we are open sourcing the Universal Authenticator Library (UAL) GitHub repository. This first step in the EOSIO Labs initiative demonstrates an alternative approach for app developers integrating with an Authenticator (wallets, app explorers, key managers, etc.) by coding to a single, universal API. Furthermore, it offers developers an optional, but opinionated, UI layer so that users get a consistent look and feel independent of the wallet they are using or the site they are on.
As we’ve seen the EOSIO ecosystem evolve over the past year, we’ve been studying how EOSIO-enabled applications interface with wallets, and how that impacts both the developer and user experiences. There has been an explosion in the number of wallets — hardware and software — and this has given users something very valuable: innovation and choice.
But with an ever-increasing number of wallets comes overhead. App developers must integrate with all of those proprietary wallet APIs (or give up and choose not to), and end users face increased uncertainty — even confusion — as transaction signing experiences multiply and diverge. Users may even find that the app they want to use doesn’t work at all with their wallet of choice leading to frustration, fragmentation, and barriers to streamlined adoption.
This work illustrates our direction and thoughts, now available for the wider community to review and consider adopting in their development workflow. We welcome your feedback and will continue to explore and publish more related work in the future.
Working with EOSIO Labs Repositories
The intent of the EOSIO Labs initiative is to more rapidly share our innovations and discoveries with all developers and by doing so increase the value these innovations can deliver to the EOSIO community at large. Open source repositories for projects published under EOSIO Labs are to be considered alpha, released with no firm expectation of future involvement by Block.one. Block.one’s continued contributions and involvement will depend on wider community adoption of such projects.
EOSIO Labs repositories are experimental. Developers in the community are encouraged to use EOSIO Labs repositories (released under MIT license) as the basis for code and concepts to incorporate into their applications. Community members are also welcome to contribute and further develop these repositories. Since these repositories are not supported by Block.one, we may not provide responses to issue reports, pull requests, updates to functionality, or other requests from the community, and we encourage the community to take responsibility for these. However, depending on the adoption of concepts and codebases from within the EOSIO Labs umbrella, select repositories and concepts can graduate over time to supported status to enable such projects to move ahead rapidly. As projects graduate from EOSIO Labs, they will enjoy the support we feel is needed, as afforded to actively maintained EOSIO open source libraries such as Demux, EOSJS and others.
Stay Connected
If you are interested in providing feedback and working more closely with our team to improve the EOSIO Labs repositories for developers, you can send our developer relations team an email at developers@block.one.
You can also keep up to date with future updates by subscribing to our mailing list on the EOSIO Developer Portal. We are excited to be continually improving the usability of the software for EOSIO developers as we continue laying a foundation for the mass adoption of blockchain technology.
The Future is Open for EOSIO Labs
Going forward through EOSIO Labs, Block.one will continue releasing our thoughts and research on the direction of key and password management. This is just the first of many areas of research we hope to tackle as part of the community. We welcome and encourage your feedback on areas of interest to explore, and look forward to continually growing one of the most vibrant and innovative technology communities in the world.
Disclaimer: Block.one makes its contribution on a voluntary basis as a member of the EOSIO community and is not responsible for ensuring the overall performance of the software or any related applications. We make no representation, warranty, guarantee or undertaking in respect of the releases described here, the related GitHub release, the EOSIO software or any related documentation, whether expressed or implied, including but not limited to the warranties or merchantability, fitness for a particular purpose and noninfringement. In no event shall we be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or documentation or the use or other dealings in the software or documentation. Any test results or performance figures are indicative and will not reflect performance under all conditions. Any reference to any third party or third-party product, resource or service is not an endorsement or recommendation by Block.one. We are not responsible, and disclaim any and all responsibility and liability, for your use of or reliance on any of these resources. Third-party resources may be updated, changed or terminated at any time, so the information here may be out of date or inaccurate.
原文链接/Original URL:
