-
Notifications
You must be signed in to change notification settings - Fork 497
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
Improve data cost estimation when full tx hurts compression ratio #1058
Conversation
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.
Two possible typos.
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.
Looks good
@@ -20,6 +20,8 @@ type ArbGasInfo struct { | |||
|
|||
var storageArbGas = big.NewInt(int64(storage.StorageWriteCost)) | |||
|
|||
const AssumedSimpleTxSize = 140 |
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.
We may want to think about this later, but definitely not now
var randR = crypto.Keccak256Hash([]byte("R")).Big() | ||
var randS = crypto.Keccak256Hash([]byte("S")).Big() | ||
|
||
func makeFakeTxForMessage(message core.Message) *types.Transaction { |
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.
it may be worth noting that this fake tx is invalid (signature doesn't check out, intentionally large field values, even the wrong tx type sometimes, etc)
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.
Looks great!
No description provided.