Skip to content
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

feat(taiko-client): propose blocks with revert protection #18590

Open
wants to merge 1 commit into
base: feature/batch-revert-protection
Choose a base branch
from

Conversation

YoGhurt111
Copy link
Contributor

No description provided.

@@ -190,7 +190,7 @@ func (b *BlobTransactionBuilder) BuildOntake(
}
txListArray := make([][]byte, len(encodedParamsArray))
if b.proverSetAddress != rpc.ZeroAddress {
data, err = encoding.ProverSetABI.Pack("proposeBlocksV2", encodedParamsArray, txListArray)
data, err = encoding.ProverSetABI.Pack("proposeBlocksV2Conditionally", encodedParamsArray, txListArray)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we make this feature as a new flag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is feature is benefit for all users. Without this feature, user would propose empty blocks and verify blocks with much gas and get no reward. If all users apply this feature, it will cost little gas and revert tx even thought without the support of revert protection from endpoint.

Copy link
Member

@davidtaikocha davidtaikocha Dec 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Emm but then it will be a force upgrade of proverSet for all community proposers when we release a new version of client? I think if we still keep proposeBlocksV2 in proverSet, we should still support that path in client?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, will change it as an optional flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants