go-ethereum | 易学教程

go开发以太坊智能合约-geth

阅读更多关于 go开发以太坊智能合约-geth

go-ethereum客户端通常被称为geth，它是个命令行界面，执行在Go上实现的完整以太坊节点。通过安装和运行geth，可以参与到以太坊前台实时网络并进行以下操作：挖掘真的以太币在不同地址间转移资金创建合约，发送交易探索区块历史及很多其他链接：网站: http://ethereum.github.io/go-ethereum/ Github: https://github.com/ethereum/go-ethereum 维基百科: https://github.com/ethereum/go-ethereum/wiki/geth Gitter: https://gitter.im/ethereum/go-ethereum 如果你希望高效的学习以太坊DApp开发，可以访问汇智网提供的最热门在线互动教程：适合区块链新手的以太坊DApp实战入门教程区块链+IPFS+Node.js+MongoDB+Express去中心化以太坊电商应用开发实战其他更多内容也可以访问这个以太坊博客。来源： oschina 链接： https://my.oschina.net/u/3837977/blog/1805453

Running geth on kubernetes

阅读更多关于 Running geth on kubernetes

问题 I am running geth full node https://github.com/ethereum/go-ethereum/wiki/geth on Google Cloud platform on a VM instance. Currently, I have mounted a SSD and write the chain data to it. I want to now run it on multiple VM instances and use a load balancer for serving the requests made by Dapp. I can do this using a normal load balancer and create VMs and autoscale. However, I have the following questions: SSD seems to be a very important part of blockchain syncing speed. If I simply create VM

Running geth on kubernetes

阅读更多关于 Running geth on kubernetes

geth never stop syncing on rinkeby testnet

阅读更多关于 geth never stop syncing on rinkeby testnet

问题 when the currentBlock becomes close to the highestBlock, it stop growing, and the highestBlock begin to grow. A while later, the currentBlock begin growing again. I run geth with command geth --rinkeby --fast . the highestBlock on my geth is very close to the actual number on https://www.rinkeby.io/#faucet. > eth.syncing { currentBlock: 2401750, highestBlock: 2401826, knownStates: 14219701, pulledStates: 14205841, startingBlock: 2401554 } > eth.blockNumber 0 logs below, seems normal: INFO [06

Web3.js sendSignedTransaction gives “Error: Failed to check for transaction receipt”

阅读更多关于 Web3.js sendSignedTransaction gives “Error: Failed to check for transaction receipt”

问题 I am using web3js v1.0.0-beta.34 to send signed transactions to a geth node Geth/v1.8.13-unstable-2e0391ea/linux-amd64/go1.10.3 in a loop. Problem: In the initial iterations of the loop, Node.js prints the transaction hash to console. But when the loop has been running for more than a handful of seconds, we start to get the error: Error: Failed to check for transaction receipt: {} at Object._fireError (/Users/x/test/node_modules/web3-utils/src/index.js:56:17) at /Users/x/test/node_modules

How to authenticate and send contract method using web3.js 1.0

阅读更多关于 How to authenticate and send contract method using web3.js 1.0

I am confused about how I should be executing a contract's method using the web3 1.0 library. This code works (so long as I manually unlock the account first): var contract = new web3.eth.Contract(contractJson, contractAddress); contract.methods .transfer("0x0e0479bC23a96F6d701D003c5F004Bb0f28e773C", 1000) .send({ from: "0x2EBd0A4729129b45b23aAd4656b98026cf67650A" }) .on('confirmation', (confirmationNumber, receipt) => { io.emit('confirmation', confirmationNumber); }); I get this error (if I don't unlock manually first): Returned error: authentication needed: password or unlock The above code

How to authenticate and send contract method using web3.js 1.0

阅读更多关于 How to authenticate and send contract method using web3.js 1.0

问题 I am confused about how I should be executing a contract's method using the web3 1.0 library. This code works (so long as I manually unlock the account first): var contract = new web3.eth.Contract(contractJson, contractAddress); contract.methods .transfer("0x0e0479bC23a96F6d701D003c5F004Bb0f28e773C", 1000) .send({ from: "0x2EBd0A4729129b45b23aAd4656b98026cf67650A" }) .on('confirmation', (confirmationNumber, receipt) => { io.emit('confirmation', confirmationNumber); }); I get this error (if I