Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now
6

Constantinople is non-contentious. It wont create 2 forked chains, it's just an upgrade to the mainnet. It was however delayed yesterday, and will likely be postponed around a month.


5

I tried this and worked (but I recommend to create a backup): => xxxxxx is the future block number you want to do hardfork your private ethereum chain. 1- Alter the .json file by adding "constantinopleBlock": xxxxxx, "petersburgBlock": xxxxxx. PetersburgBlock is the Constantinople fix due to a security hole of Constantinople. 2- Run the command: geth --...


3

Have a look here: https://medium.com/chainsecurity/constantinople-enables-new-reentrancy-attack-ace4088297d9 TLDR; Repricing SSTORE defeats the re-entrancy protection that the gas stipend is meant to provide. That would be a breaking change to some deployed contracts. Hope it helps.


2

If I'm not mistaken, the plan is to release Constantinople without adjusting the SSTORE pricing precisely because it would be possible to re-enter (with a budget of 2,300 gas) and accomplish some of the lower-cost repriced storage operations. That would be bad for some contracts already on the chain. .send and .transfer do indeed revert from running out ...


2

According to http://forkmon.ethdevops.io/, 7 blocks have been mined on the ConstantiNOple chain, while 2696 have been mined (at the time of writing) on the non-ConstantiNOple chain. That means ~14 ConstantiNOple eth have been mined while 8088 non-ConstantiNOple eth has been mined. It's highly unlikely that any support will come from this, seeing as the ...


2

You don't need to do anything about your ether - if you ran a parity or geth node, you need to be on a version that either didn't support the fork in the first place, or reverted the fork - other than that, your node will handle reorganization/syncing to the correct fork. More information, including specific version numbers, here: https://www.parity.io/...


2

Exactly the opposite, take your ether to your wallet. By your wallet, I mean a wallet that you are the only person who knows the private key. If you don't do this and leave your ether, say in an exchange, then it's up to that exchange to what happens your forked ethers.


2

There's nothing you need to change in your smart contract to comply with Constantinople. Newer versions of the solidity compiler will include the bitwise shifting EIP. You don't need to worry about EXTCODEHASH or CREATE2 since you will only benefit from those feature if you need them specifically. The other EIP, net gas metering, will happen passively.


2

The new changes for the Constantinople fork can be found here for every main client https://github.com/ethereum/pm/wiki/Constantinople-Progress-Tracker To summarize some of the main changes are: Reducing block rewards from 3 ETH to 2 ETH (Lowering inflation). Optimizing code (Refactoring code for the EVM), reducing storage costs for developers Delaying the ...


2

Casper is the proof-of-stake protocol. There are two being developed, one by Vitalik Buterin and another by Vlad Zamfir. Vitalik's is known as Casper FFG. Vlad's is known Casper CBC. They are NOT complementary AFAIK, but rather being developed in friendly competition based on differing philosophies. I suppose one of them will be selected or perhaps ideas ...


2

I got the issue resolved by upgrading geth to version 1.8.23


1

From here: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1013.md Included EIPs: EIP 145: Bitwise shifting instructions in EVM EIP 1014: Skinny CREATE2 EIP 1052: EXTCODEHASH Opcode EIP 1234: Delay difficulty bomb, adjust block reward EIP 1283: Net gas metering for SSTORE without dirty maps


1

As far as I know there has been no major talk about anyone sustaining the pre-Constantinople fork after the fork block. Also there has been no replay protection AFAIK from pre to post Constantinople


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