So that is pretty much the scope of ETC.
It is a much more tractable problem.
"So what is the scaling plan for ETC?"
L2. State Channels already work on ETH2 (Fate Channels + Connext already in production).
Fate Channels don't need CREATE2 so will work today on ETC as well.
Connext will work on ETC when we get Constantinople opcodes at Agharta in Jan 2020:
The plan for scaling L1 on ETC is not to scale L1.
Or at least to only do that in a sustainable "Moore's law" style manner.
Only to the degree which the current tech stack can support.
Security always comes first for ETC.
"Better Bitcoin", not "World Computer"
Hope that gives everyone some more insight into the thinking.
@/all Core dev meeting in 10 min.
Zoom Link: https://zoom.us/j/121989443
Regarding the discussion in the meeting on tooling support for EIP-1707 code prefix vs 44-VERTXN account versioning extension. Thanks to MrChico for spotting this -- the concern on 44-VERTXN's ecosystem tooling support can be wholly addressed just by making the
version field optional with default value
This I believe, from all information I have in hand, means that 44-VERTXN is nearly superior in all aspects compared with EIP-1707 code prefix.
I know one use case for versioning that I recently thought about
The biggest use case for versioning is definitely to avoid the next situation similar to EIP-1884. EIP-2348 discussed today does not do anything about that at all. However, fortunately, we have this covered. ethereum/EIPs#2341
If versioning is inherited from parent contract to the child, then it would be quite easy to deploy generic factories that would be used to take advantage of the old rules, with the cheaper opcodes, no?
@AlexeyAkhunov I don't think the goal here is to "prevent people from using older versions", but rather to "encourage people to use newer versions". Older versions are fine and people can continue to create new contracts of it as long as there are no current known EVM vulnerabilities (otherwise, we need emergency hard fork and backward compatibility has to be broken anyway). In the mean time, to encourage using new account versions, we can do changes such as systematically decrease opcode gas cost, so that older account versions are slightly more expensive to use, and contracts are better off migrating to the forward-compatible EVM version when it is possible.
Back to your questions -- the direct answer is a quantitative "yes", but I do think the above should have addressed the concerns behind the question.
@ajsutton Okay let me rephrase it -- older versions are fine and people can continue to create new contracts of it as long as there are no
current known EVM vulnerabilities. The thing is, whenever there's a vulnerability, we'd want to patch it both in the legacy EVM and the forward-compatible EVM. Because it's patched in legacy EVM, contracts under old rules cannot exploit it either.
This is why I also emphasis that account versioning is not for emergency hard forks. Those are situations where backward compatibility has to be broken.
avoid the next situation similar to EIP-1884
account versioning is not for emergency hard forks. Those are situations where backward compatibility has to be broken.
Well, as I see it, if we don't 1884 now, we will eventually have to do it in an emergency instead. So I still don't see how that reasoning applies to 1884. I guess you mean that next time, we can ship it "softly" even earlier, and let people migrate, and only much later actually change/remove it "breakingly", and then not bothering the "active ecosystem". If so, I finally understood your reasoning :)
@holiman Yeah. That's one way the forward-compatible EVM can work, and I do think that's a viable method. But just want to provide you an idea that will have even less backward incompatibility impact, and does what 1884 tries to accomplish.
Imagine, in an alternative universe, we decide to apply 1884 after 1702/39-UNGAS/40-UNUSED. The current 1884 specs, we increase certain opcode's gas cost, but note that this is functionally equivalent to decrease other opcode's gas cost. We apply 1884 as follows:
0), we do nothing.
1), we apply 1884 by decreasing other opcode's gas cost.
After this is done, we make sure to inform miners to configure their client to set the block gas limit according to the forward-compatible EVM gas cost config. Note that this is something that has to be done when we re-calibrate gas cost anyway, no matter whether account versioning is in place. When hard fork happens:
Nothing is perfect. This method certainly involves a slight increase in implementation complexity, and sometimes, gas cost analysis might be too complex to adopt this method, and we may be just better off using what you said above. But I just want to note that this is a possibility, and it indeed works for "simple" cases like EIP-1884.
I also want to note that once things move forward to the forward-compatible EVM, we can expect less and less of this when we do gas cost changes. After all, the forward-compatible EVM is forward-compatible in gas cost changes.
Dfor forward-compatible EVM, and we make the gas cost provided to be
g0 / D, and the gas cost calculated to be
g * D, where
gis the actual gas cost, and
g0is the gas limit.