-
Notifications
You must be signed in to change notification settings - Fork 282
(depreciated) Improvment for the first phase of zktrie #100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* Let blockResult limit settable * fix bug * Update cmd/geth/usage.go Co-authored-by: HAOYUatHZ <37070449+HAOYUatHZ@users.noreply.github.com> Co-authored-by: HAOYUatHZ <37070449+HAOYUatHZ@users.noreply.github.com>
I suggest you open another PR (squash all commits into 1) against zkrollup branch. And prefix "depreciated" to title of this one. Dont close this one. So we can have a look at diff for both base branches |
Ok, one moment
|
core/blockchain.go
Outdated
@@ -1188,8 +1188,15 @@ func (bc *BlockChain) writeKnownBlock(block *types.Block) error { | |||
return nil | |||
} | |||
|
|||
// EvmTxTraces groups trace data from each executation of tx and left | |||
// some field to be finished from blockResult | |||
type EvmTxTraces struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving EvmTxTraces
to core/types/l2trace.go
might be more concentrated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
get it, may us just move to #101 for more reviewing?
* Upgrade trace code to decrease GC pressure. * Fix golangci bug * Add goproxy * update docker file * trigger ci * trigger ci * Upgrade code * Upgrade code * trigger ci Co-authored-by: HAOYUatHZ <37070449+HAOYUatHZ@users.noreply.github.com>
* refactor miner * format
This work has finished the first part of a better PR for zktrie: inducing zktrie as an alternative storage layer and providing a more effective, unitify logging scheme for the L2 trace.
There is some breaking change for the trace output comparing to current zktrie work branch:
I think these changes has no affection on the trace handling of roller because no module would refer the proof part except for the mpt-circuit