Skip to content

eth2: catalyst RPC calls and command line options #22468

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

gballet
Copy link
Member

@gballet gballet commented Mar 9, 2021

Supersedes #22320

@gballet gballet force-pushed the cacatalyst-for-executable-beacon-chain-rebased branch 3 times, most recently from f409a01 to 7b9fe46 Compare March 10, 2021 15:19
gballet and others added 2 commits April 8, 2021 16:35
@gballet gballet force-pushed the cacatalyst-for-executable-beacon-chain-rebased branch 3 times, most recently from 2cd97ee to 27f37ed Compare April 8, 2021 15:55
}
}

block, err := api.eth.Engine().FinalizeAndAssemble(bc, header, api.env.state, transactions, nil /* uncles */, api.env.receipts)
Copy link
Member

Choose a reason for hiding this comment

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

QQ: the block reward is applied based on the ethash rules. So in the eth2, actually there is no block reward here right? The reward will be applied in the consensus layer(they have their own accounting model).

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, this is the long term view. Right after the merge, you won't be able to move the "eth2 eth" from the beacon chain into the eth1 "execution layer", so it still makes sense to offer a reward... more importantly, for the upcoming testnet: if you don't have a way to produce value, you won't be able to test anything.

@gballet gballet force-pushed the cacatalyst-for-executable-beacon-chain-rebased branch from 27f37ed to 523f1cb Compare April 9, 2021 07:57
@gballet gballet force-pushed the cacatalyst-for-executable-beacon-chain-rebased branch from 523f1cb to 9a35a22 Compare April 9, 2021 09:58
)

// JumpTable contains the EVM opcodes supported at a given fork.
type JumpTable [256]*operation

//nolint:deadcode
Copy link
Member Author

Choose a reason for hiding this comment

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

node to self: this is no longer needed

@gballet
Copy link
Member Author

gballet commented Apr 20, 2021

Closing to prevent confusion with #22641

@gballet gballet closed this Apr 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants