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

[PIE-2016] Updated PoAMetricService with method to check node's address. #133

Closed
wants to merge 1 commit into from

Conversation

mark-terry
Copy link
Contributor

PR description

Added a method to the PoAMetricService that allows plugins to check whether a given address matches the node's address.

Fixed Issue(s)

PIE-2016

@mark-terry mark-terry force-pushed the PIE-2016 branch 4 times, most recently from b903458 to cf7a7e1 Compare October 24, 2019 14:18
@@ -41,4 +47,11 @@ public PoAMetricServiceImpl(final BlockInterface blockInterface, final Blockchai
public Address getProposerOfBlock(final BlockHeader header) {
return this.blockInterface.getProposerOfBlock(header);
}

@Override
public boolean isThisNodesAddress(final Address address) {
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'm not huge on this function name. Suggestions?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah we shouldn't add this method to the public API. It should be a method that gets the current address which can then be compared. That could be getLocalNodeAddress somewhere more generic than this, but I actually like the idea of designing the API to handle the node address and the address used as a validator to potentially be different in the future. So maybe getLocalSignerAddress?

Signed-off-by: Mark Terry <mark.terry@consensys.net>
@mark-terry mark-terry closed this Nov 5, 2019
@mark-terry mark-terry deleted the PIE-2016 branch November 5, 2019 23:02
siladu pushed a commit to siladu/besu that referenced this pull request Oct 28, 2024
Engine API: refine message ordering section
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.

2 participants