Comments (13)
@chriseth We have transaction tracing for internal calls implemented in Parity. It allows to do exactly that - query for any changes for the account.
from pm.
@Souptacular I gave a wrong link about EIP211 discussion: the last point in 2.a. This should be under discussion. Currently, the link doesn't point to a discussion but to a test file. Sorry.
from pm.
Agreeing on gas costs for MODEXP, ECADD, ECMUL, ECPAIRING.
For MODEXP specifically, are we going to modify it to somehow incorporate bit length or not?
from pm.
Another item: I am starting to get cold feet about the REVERT opcode being able to return data. My main concern is that it will break any applications that depend on being able to micro-charge for getting data. I do realize that such applications are not extremely secure in any case because the fee can always be circumvented via merkle proof magic, but even still such strategies always have some cost, and so there is opportunity for applications to be able to charge at least enough to pay back any fixed costs they have for transaction fees. I'm concerned that (i) we are introducing an economic change which breaks things, and that (ii) the marginal benefits of knowing why an error happened may not be worth the costs.
from pm.
An alternative without the economic change is REVERTLOG
that almost aborts, but logs one event. So (benefit of REVERT) - (benefit of REVERTLOG) needs to outweigh the costs.
[EDIT: REVERTLOG
needs to consume all gas, lest information can be encoded in the gas consumption]
from pm.
Item: proposal about freezing EIPs to allow time for testing.
Currently, no test cases are ready and stable because there are no indications which EIPs have stopped changing.
I propose introducing the notion of "freezing an EIP for Metropolis". Once EIPs are frozen for Metropolis, any change in the EIP that changes test cases needs to go through the All Core Devs meeting with the unanimous vote (it's meant to be hard, but not impossible, to achieve).
As an effect, when a frozen EIP has a critical problem, but if any party says they have not enough time to test the fix, the EIP would be dropped from Metropolis.
The first question is if we shall try to have this distinction "frozen". (Implementation details should come afterward: e.g. how to keep track of the frozen states; which EIPs to freeze first; shall we set the minimum duration between freeze and activation.)
from pm.
Item: was there a decision about opcodes of RETURNDATASIZE and RETURNDATACOPY?
I heard somewhere that that last coredev meeting decided that The EIP has been updated.RETURNDATASIZE
and RETURNDATACOPY
shall move from 0xd
and 0xe
to some new opcodes, but I didn't attend it. I don't see the change in the EIP or in the last meeting's records (I found none). Was there a decision? If yes, what are the new opcodes?
from pm.
Regarding EIP 96: should the gas price of BLOCKHASH
already change from the beginning of the Metropolis, or from the block where the behavior of BLOCKHASH
changes? https://github.com/ethereum/EIPs/pull/210/files#r117211219
from pm.
If we have time (no high priority), I would like to get some feedback about adding functionality that allows dapps to be notified whenever a certain address was touched by a transaction (including internal calls). This information does not necessarily have to be part of the block, but could be an isolated index database.
from pm.
Regarding EIP 211 (RETURNDATACOPY): the behavior of reading out-of-bounds from the returndata buffer is under discussion. We can at least gather opinions.
from pm.
Regarding EIP98 (med state removal): this should start at (inclusive) METROPOLIS_FORK_BLKNUM instead of one block after that (as written in the EIP). Pointed out by @gumb0 ethereum/EIPs#98 (comment)
from pm.
Regarding EIP96 (BLOCKHASH contract): should the blockhash-maintainance call at the beginning of each block increment the nonce of SYSTEM_ACCOUNT
? https://github.com/ethereum/EIPs/pull/210/files#r117260179
from pm.
Notes are here: https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2016.md
Closing issue.
from pm.
Related Issues (20)
- pm
- Id HOT 2
- EIP-4844 Implementers' Call #16 HOT 5
- SSZ Transactions Breakout Room #2 HOT 2
- EOF Implementers Call #8 HOT 3
- Execution Layer Meeting 156 HOT 13
- Consensus-layer Call 103 HOT 5
- EIP-4844 Implementers' Call #17 HOT 1
- Never Broke Again YoungBoy HOT 2
- EOF Implementers Call #9 HOT 2
- Execution Layer Meeting 157 HOT 8
- Consensus-layer Call 104 HOT 3
- EIP-4844 Implementers' Call #18 HOT 2
- Shapella Community Call #2
- Tp Hostage of wallet not Bug .
- Execution Layer Meeting 158 HOT 6
- EIP-4844 Implementers' Call #19 HOT 3
- EOF Implementers Call #10 HOT 2
- Consensus-layer Call 105 HOT 5
- EOF Implementers Call #11 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pm.