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

Implement feerecipient API for keymanager #3198

Closed
wants to merge 3 commits into from

Conversation

ethDreamer
Copy link
Member

@ethDreamer ethDreamer requested a review from michaelsproul May 20, 2022 19:30
});
})
}

Copy link
Member Author

@ethDreamer ethDreamer May 20, 2022

Choose a reason for hiding this comment

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

I had to break up collect_preparation_data() into different functions

The logic for retrieving the fee recipient for a given public key was pulled out into get_preparation_data() for use in the API call. Because this function is called in a loop inside collect_preparation_data(), I made it accept a FeeRecipientFile object instead of reading from disk so that doesn't need to happen for each iteration of the loop. This required me to create read_fee_recipient_file().

Also @michaelsproul I had to resolve a merge conflict when I rebased this with your changes to collect_preparation_data().. I beleive I did it correctly but may want to look closely at this part.

@ethDreamer ethDreamer changed the title Fee recipient api Implement feerecipient API for keymanager May 20, 2022
@paulhauner
Copy link
Member

Would you mind throwing a work-in-progress or ready-for-review flag on this 🙏

@ethDreamer
Copy link
Member Author

i'm going to re-open this from another branch that's been refactored

@ethDreamer ethDreamer closed this May 24, 2022
@ethDreamer ethDreamer deleted the fee_recipient_api branch December 19, 2022 21:27
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