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

removes LegacyContactInfo::is_valid_tvu_address #29570

Merged
merged 1 commit into from
Jan 8, 2023

Conversation

behzadnouri
Copy link
Contributor

Problem

Since #20480, turbine includes all epoch staked nodes in tree construction and no longer relies on obtaining their contact-info from gossip; and so distinguishing between is_valid_address and is_valid_tvu_address is no longer necessary and the latter can be removed.

Summary of Changes

removed LegacyContactInfo::is_valid_tvu_address.

Since
solana-labs#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.
@behzadnouri behzadnouri merged commit 677b6d6 into solana-labs:master Jan 8, 2023
@behzadnouri behzadnouri deleted the rm-is-valid-tvu-addr branch January 8, 2023 22:53
gnapoli23 pushed a commit to gnapoli23/solana that referenced this pull request Jan 10, 2023
Since
solana-labs#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.
gnapoli23 pushed a commit to gnapoli23/solana that referenced this pull request Jan 10, 2023
Since
solana-labs#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.
gnapoli23 pushed a commit to gnapoli23/solana that referenced this pull request Jan 10, 2023
Since
solana-labs#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.
gnapoli23 pushed a commit to gnapoli23/solana that referenced this pull request Jan 10, 2023
Since
solana-labs#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.
mergify bot pushed a commit that referenced this pull request Jan 25, 2023
Since
#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.

(cherry picked from commit 677b6d6)
behzadnouri added a commit that referenced this pull request Jan 25, 2023
…9904)

removes LegacyContactInfo::is_valid_tvu_address (#29570)

Since
#20480
turbine includes all epoch staked nodes in tree construction and no
longer relies on obtaining their contact-info from gossip; and so
distinguishing between is_valid_address and is_valid_tvu_address is no
longer necessary and the latter can be removed.

(cherry picked from commit 677b6d6)

Co-authored-by: behzad nouri <[email protected]>
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.

1 participant