Hot answers tagged

135

Ropsten PoW Supported by geth and parity Best reproduces the current production environment Chaindata size 15 GB - Apr 2018 Kovan PoA (Immune to spam attacks) Supported by parity only Chaindata size 13 GB - Apr 2018 Rinkeby PoA (Immune to spam attacks) Supported by geth only Chaindata size 6 GB - Apr 2018 Sokol PoA (Immune to spam attacks) Supported ...


40

Each network version gets a name (id). Here is an overview. Olympic (0) is also regularly referred to as Ethereum 0.9; it launched early 2015 and was the first public Testnet. Deprecated in mid 2015 and replaced by Morden. Frontier (1) the official 1.0 release was launched as public main network in the summer of 2015. Forked to Homestead in early 2016. ...


22

Update - 25th March 2017 Ropsten has been revived! We are pleased to announce that the Ropsten testnet has been revived! Thanks to a generous donation of GPU hashpower, the Ropsten chain has been cleared of the spam blocks that had accumulated in a recent attack. https://github.com/ethereum/ropsten/blob/master/revival.md Update - 18th March 2017 ...


20

There are other networks as well, as described in this SO answer, copied here with their network id numbers: 0: Olympic, Ethereum public pre-release testnet 1: Frontier, Homestead, Metropolis, the Ethereum public main network 1: Classic, the (un)forked public Ethereum Classic main network, chain ID 61 1: Expanse, an alternative Ethereum implementation, ...


13

For rinkeby, just type geth --rinkeby from command prompt and you're in


7

For Kovan: parity --chain kovan it won't be possible to connect to Rinkeby with parity, only with geth. Rinkeby with geth: geth --rinkeby


7

Frontier is the name of the launch and first release of the live Ethereum network. Frontier is the current Ethereum network. It is described more, as well as the names for upcoming releases, here. Morden is the testnet for Frontier. Any bugs found here, will most likely also happen on Frontier. Responsible developers would test their code on Morden ...


7

Frontier is the name of Etheneum's current release stage. It is for early adopters, experimenters. When it was released, there were no Graphical User Interface available, everything had to be done with the command line. Also, some technical issues were to be expected often. For some serious use, people were encouraged to wait for the next phase, Homestead. ...


5

Red indicates it's a testnet, that's perfectly fine. You don't need the kovan specification json anymore. with latest versions, just run parity --chain kovan --no-warp. And the --no-warp flag will fix your synchronization issues (known issue on kovan).


4

You have to use either the --chain or --networkid options, depending on your client. The Kovan network is only available when using the Parity client. From the Parity --help output: --chain CHAIN Specify the blockchain type. CHAIN may be either a JSON chain specification file or olympic, frontier, ...


4

Ropsten is to be considered dead, and parity launched a Proof of Authority testnet called Kovan. Read the proposal here: https://github.com/kovan-testnet/proposal To update your testnet from ropsten to kovan, you will have to upgrade to the latest parity beta release (1.5.4), however, there are no official instructions yet, how to run kovan. Parity 1.5.5 ...


4

If anyone else is getting the error: Error encountered, bailing. Network state unknown. Review successful transactions manually. Error: VM Exception while processing transaction: out of gas Delete the ./build directory and enable the solc optimizer in truffle.js: module.exports = { networks: { development: { host: "localhost", ...


3

Any call to methods from https://github.com/paritytech/parity/wiki/JSONRPC-eth-module should work for rpc. For example requesting the current block number curl --data '{"method":"eth_blockNumber","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545


3

Here's a link to information on faucets for the Kovan testnet. There are currently four ways listed on the above link to get Kovan testnet ETH: Icarus Faucet (SMS Verified, Automated) Request Via Gitter (Manually Verified) Use PoW via SmartPool


3

There's currently (still?) an attack on the Ropsten test network: Ropsten testnet is under kind of attack? What can we do? what do I have to save in order to not loose my test accounts ? (i guess the UTC--xxx files from testnet/geth/keystore.) Yes, back up your ~/.ethereum/testnet/keystore/ directory before doing anything else. (Obviously it's only ...


3

That´s right. Homestead is the current main network whereas morden is commonly called the 'testnet'. They are both similar beside their content and value. Testnet 'coins' are worthless. While users can create some private chains for development and internal testing, it is interesting to have a network similar to the mainnet where smart contracts and Dapps ...


3

If you've sent any transaction in last 48 hours or so, then it's because of the 51% attack on ropsten, which is not resolved yet. Follow the link below: https://www.reddit.com/r/ethereum/comments/5w3vqu/ropsten_spam/ & yeah, sometimes the ropsten network has gone down ( or restart, I don't know) earlier too. I faced a similar issue when I was ...


3

Both Kovan and Rinkeby have a gas limit of ~7 million, which is about 330 regular ETH transfers per block (21,000 gas each). Kovan has a ~4 second blocktime and Rinkeby has a ~15 second blocktime, so the tx/s for Kovan is ~80 and for Rinkeby is ~20. These are just based on the max gas/block. Since they are both PoA, they might impose their own artificial ...


2

Check this out ! Kovan to the rescue :) http://www.ibtimes.co.uk/parity-pushes-new-ethereum-testnet-kovan-after-spam-attacks-1609901


2

run parity with parity --chain kovan. and then in your endpoint provide http://localhost:8545 or http://127.0.0.1:8545 8545 is the RPC port


2

As far as I know Kovan is only accessible by running Parity. This repo contains all of the info and instructions on getting Kovan setup along with the config file: https://github.com/kovan-testnet/config As for integration with Truffle, if you're running parity locally you could use the standard localhost:8545, and the network id: 42 I would also recommend ...


2

I am using the latest parity version. In this version we don't need to specify a Kovan config file. Below listed is the way i am starting parity. In this case I am getting KOVAN with red background. The additional parameters i.e. "--jsonrpc-apis personal,eth,net,web3" are used to include these libraries. Whenever I perform any transaction or deploy any ...


2

Googling gave me This about Kovan Faucet There are currently a few different methods of receiving Kovan Ether: Icarus Faucet (SMS Verified, Automated) Request Via Gitter (Manually Verified) Use PoW via SmartPool Github Gist Faucet ( Automated ) Go to http://gist.github.com and then create a new entry with the text being your Kovan address, once you save ...


2

You can't transfer ETH from one network to another. You can get free ETH on most testnets though, here's a link to information on faucets for the Kovan testnet. There are currently four ways listed on the above link to get Kovan testnet ETH: Icarus Faucet (SMS Verified, Automated) Github Gist Faucet ( Automated ) Request Via Gitter (Manually ...


2

This is because your main fallback function is not payable , I think: function () payable { main.handlePayment.value(msg.value)(msg.sender); } Best way to debug this is to use truffle debug see this http://truffleframework.com/docs/getting_started/debugging or remix debug https://remix.readthedocs.io/en/latest/tutorial_mist.html


2

It is 18.7 GB, and it took about 6 hours to download with --no-warp


2

Yes, it is possible: Configure Metamask to connect to a node that synchronizes with your private network Configure Metamask to use correct chain ID for your private network when constructing transactions Configure Metamask to use correct network ID for your private network, probably the same as chain ID


2

You declared you function as async but never used the async/await pattern. I added the await at the correct position for you. Try this: export const loadExchange = async (web3, networkId, dispatch) => { try { const exchange = await web3.eth.Contract(Exchange.abi, Exchange.networks[networkId].address) dispatch(await exchangeLoaded(exchange)) ...


2

I ran into this recently, too. This same address kept draining my account balance and I thought they must have gained access to my server because I was sure I'd closed down the firewall. Problem for me was that I hadn't realized that I still had my firewall open on the RPC port, and the easy fix was to close that port :). This is just for anyone else who ...


1

I think what you're experiencing is the difference between an Ether and a Wei. Internally, Solidity doesn't support floating-point or even fixed-point decimal variables - only integers. Consequently, everything is stored using integer values. "Ether" the currency unit is divisible to 18 decimal places. The smallest possible (indivisible) unit is called a ...


Only top voted, non community-wiki answers of a minimum length are eligible