当前位置: 首页 > 软件库 > Web3 > 区块链 >

ethermint-archive

Ethereum on Tendermint using Cosmos-SDK!
授权协议 Apache-2.0 License
开发语言
所属分类 Web3、 区块链
软件类型 开源软件
地区 不详
投 递 者 上官和惬
操作系统 跨平台
开源组织
适用人群 未知
 软件概览

This repo is archived as of October 7, 2020 but made available for historical record.

Active development of Ethermint is located at github.com/cosmos/ethermint

Ethermint

**WARNING:** Ethermint is under VERY ACTIVE DEVELOPMENT and should be treated as pre-alpha software. This means it is not meant to be run in production, its APIs are subject to change without warning and should not be relied upon, and it should not be used to hold any value. We will remove this warning when we have a release that is stable, secure, and properly tested.

What is it?

ethermint will be an implementation of the EVM that runs on top of tendermint consensus, a Proof of Stake system. This project has as its primary goals:

  • Hard Spoon enablement: This is the ability to take a token from the Ethereum mainnet and "spoon" (shift) the balances over to another network. This feature is intended to make it easy for applications that require more transactions than the Ethereum main chain can provide to move their code over to a compatible chain with much more capacity.
  • Web3 Compatibility: In order enable applications to be moved over to an ethermint chain existing tooling (i.e. web3 compatible clients) need to be able to interact with ethermint.

Implementation

Completed

  • Have a working implementation that can parse and validate the existing ETH Chain and persist it in a Tendermint store
  • Implement Ethereum transactions in the CosmosSDK

Current Work

  • Implement web3 compatible API layer
  • Implement the EVM as a CosmosSDK module
  • Allow the Ethermint EVM to interact with other Cosmos SDK modules

Next Steps

  • Hard spoon enablement: The ability to export state from geth and import token balances into Ethermint
  • Ethermint is a functioning Cosmos SDK application and can be deployed as its own zone
  • Full web3 compatibility will enable existing Ethereum applications to use Ethermint

Building Ethermint

To build, execute the following commands:

# To build the binary and put the resulting binary in ./build
$ make tools deps build

# To build the project and install it in $GOBIN
$ make tools deps install

Tests

Integration tests are invoked via:

$ make test

To run CLI tests, execute:

$ make test-cli

Ethereum Mainnet Import

There is an included Ethereum mainnet exported blockchain file in importer/blockchainthat includes blocks up to height 97638. To execute and test a full import ofthese blocks using the EVM module, execute:

$ make test-import

You may also provide a custom blockchain export file to test importing more blocksvia the --blockchain flag. See TestImportBlocks for further documentation.

Community

The following chat channels and forums are a great spot to ask questions about Ethermint:

 相关资料
  • Ethermint 是一个可扩展的、高吞吐量的 Proof-of-Stake 区块链,与以太坊完全兼容并可相互操作。它是使用 Cosmos SDK 构建的,运行在 Tendermint Core 共识引擎之上。 警告:Ethermint 正处于非常活跃的开发阶段,应该被视为 pre-alpha 的软件。这意味着它不应该在生产中运行,它的API会在没有警告的情况下发生变化,不应该被依赖,它也不应该被

  • 问题内容: 这两个词之间有什么实质性区别吗?我了解JDK代表Java开发工具包,它是SDK(软件开发工具包)的子集。但是指定Java SDK时,其含义应与JDK相同。 问题答案: 从这个维基百科条目: JDK是广义上的软件开发工具包(SDK)的子集。在最近针对Java SE,EE和ME发行的说明中,Sun承认,按照其术语,JDK构成了SDK的子集,该SDK负责编写和运行Java程序。SDK的其余部

  • 问题内容: 我有一个在Eclipse中导入的Google App Engine项目。由于某些原因,当我转到Eclipse项目属性时,Google App Engine SDK似乎被保存为jar的位置(appengine- api-1.0-sdk-1.4.0.jar),而不是实际SDK的位置。如果我修改项目的设置以使用正确的SDK,则不会保存新设置。由于无法修改设置,因此无法再从Eclipse内部部

  • 问题内容: 我经历了题为“以编程方式将AWS区域设置为1”的问题,但它没有提供我需要的所有答案。 Q1:我得到一个。我究竟做错了什么?还是我错过了错别字。 } 问题2:如果要从中构建Lambda函数,需要进行哪些代码更改?我知道如何创建lambda函数及其所需的角色。只是需要知道我编写的代码是否需要更改。我应该如何实现LambdaFuctionHandler类,如下所示: 问题答案: 关于Q1,请

  • 问题内容: 我只想要一些确认。 我在Windows上开发 我正在尝试将Facebook集成到应用中,并且SDK文档说我需要“导出签名” 从这里:http : //developers.facebook.com/docs/guides/mobile/#android 因此它说运行此命令: 首先,我必须下载openssl:OpenSSL 现在,假设上面的命令应该转换为: 因此,您想要安装在最新的Jav

  • 问题内容: 我正在尝试使用AWS开发工具包访问存储桶及其所有对象,但是在运行代码时,出现错误,线程“ main”中出现异常 请提出建议,尽管我已经对存储桶采取了以下所有许可,但我缺少的地方以及为什么发生拒绝访问错误: 代码如下: 问题答案: 现在问题已解决。代码存在以下问题: 终点不正确,应该有一个正确的终点。 没有足够的权限授予该存储桶。在AWS开发工具包中使用存储桶之前,应获取完整权限列表。