Closed timbeiko closed 5 years ago
Here's the Istanbul tracker for Geth: https://github.com/ethereum/go-ethereum/issues/19919
Here is the one for Pantheon: https://pegasys1.atlassian.net/browse/PAN-2756
Here's the one for aleth https://github.com/ethereum/aleth/issues/5716
I'd like to bring up hardfork naming as an agenda point. It seems that the fork after Istanbul is already being planned during these calls and I think it would make sense naming that fork and avoiding referring to them as "istanbul part 1 and part 2" (or "phase 1 and phase 2").
Here on Ethereum Magicians I proposed to go with Devcon city names.
Having thought about this today, I think this is a reasonable suggestion: 1) It is unlikely that anytime soon we run out of names. 2) It removes the risk of bike shedding names for many forks to come.
Expanding on 1):
The above of course assumes that Devcons continue to take place every year. In the unlikely case that Devcons won't be organized in the future, there would be still plenty of time (as shown above) to agree on a new naming scheme.
(Perhaps a bit prematurely, but I did create meta file named Berlin back in May: EIP-2070)
Tracking for Trinity: https://github.com/ethereum/py-evm/milestone/11
Small typo, the title of the Youtube Livestream incorrectly indicates the meeting as happening on the 2nd of August.
Short update on 1962:
Tracking issue for Parity: https://github.com/paritytech/parity-ethereum/issues/10770
Unfortunately 2200 UTC is too late for me to join.
@Daft-Wullie thanks for the catch -- updated!
@sorpaas and @karalabe and @chfast (well, everyone really) -- the reject below 2300
could be changed into reject below 1600
, since 700
will be spent on CALL
(if re-entrancy is what we fear). Do we want to use that, or leave that particular optimization aside?
@holiman I have considered the option of lowering the required gas for SSTORE from 2300 to 1600 (i.e. stipend - call cost). I'm not sure this gives us a lot because the particular number is less important than the fact we introduce a weird behavior. But on theoretical level it depends on the interpretation what "calls with stipend only are safe" mean.
In case of 1600, it should be defined as stipend_gas - call_gas
so we don't have to update the spec in case we'd lake to change the call_gas
in future.
Personally, I don't have strong preferences. 2300 is slightly simpler and safer, 1600 is more user friendly because chance of this exception to happen in practice is lower.
I'm fine with keeping 2300
, if nothing else than because most people have focused on the re-entrancy aspect, and I'm not sure we've fully vetted potential security problems arising from breaking "the callee cannot change its state". So if we're doing EIP-2200 now, I agree with 2300
Some numbers relating to SLOAD
and LOG
topics
750
for a log with 1 topic. 800
for SLOAD means 1550
(plus some gas per byte in log data)
1125
for log with 2 topics, with one SLOAD
becomes 1925
(plus some gas per byte in log data)
2300
for log with 3 topics and one SLOAD
Closed in favor of https://github.com/ethereum/pm/issues/121
Ethereum Core Devs Meeting 68 Agenda
Agenda
a) Geth
b) Parity Ethereum
c) Aleth/eth
d) Trinity/PyEVM
e) EthereumJS
f) EthereumJ/Harmony
g) Pantheon
h) Turbo Geth
i) Nimbus
j) web3j
k) Mana/Exthereum
l) Mantis
m) Nethermind