You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current code reads config.txt on genesis, constructs a genesis address book, then constructs a genesis roster from the AB, and finally constructs the GenesisNetworkInfo from the genesis roster.
What should happen is that the roster is not created until just before handing the roster over to the platform. The GenesisNetworkInfo should be constructed using the genesis AddressBook.
In the node.proto in translating from AddressBook, the order of gossip endpoints should be internal ip address at index 0 and external ip address at index 1.
Acceptance Criteria
Rosters are not created until we're ready to give it to the platform.
When constructing a roster, the order of gossip endpoints is reversed. external at index 0 and internal at index 1.
Notes
The text was updated successfully, but these errors were encountered:
Background
The current code reads config.txt on genesis, constructs a genesis address book, then constructs a genesis roster from the AB, and finally constructs the GenesisNetworkInfo from the genesis roster.
hedera-services/hedera-node/hedera-app/src/main/java/com/hedera/node/app/Hedera.java
Lines 607 to 613 in acbc5b6
What should happen is that the roster is not created until just before handing the roster over to the platform. The
GenesisNetworkInfo
should be constructed using the genesis AddressBook.In the
node.proto
in translating fromAddressBook
, the order of gossip endpoints should be internal ip address at index 0 and external ip address at index 1.Acceptance Criteria
Rosters are not created until we're ready to give it to the platform.
When constructing a roster, the order of gossip endpoints is reversed. external at index 0 and internal at index 1.
Notes
The text was updated successfully, but these errors were encountered: