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
If we pass 0x06 as a MsgProposeVersion and the remote node is running 1.26.0 or higher, we will get back a MsgAcceptVersion with 0x06 in the payload.
The difference between 0x05 and 0x06 is that the TxSubmissionProtocol has its starting agency flipped around the same as all the other protocols. In 0x05, the remote server started with agency so we had to spin up TxSubmissionProtocol right away to listen for messages from the server. In 0x06, when doing regular syncing with the node, we can not connect TxSubmissionProtocol at all since the server will be waiting on us forever to send something.
When doing a sync, we should update to support 0x06 and just omit adding TxSubmissionProtocol if the server responds with 0x06.
The text was updated successfully, but these errors were encountered:
If we pass 0x06 as a MsgProposeVersion and the remote node is running 1.26.0 or higher, we will get back a MsgAcceptVersion with 0x06 in the payload.
The difference between 0x05 and 0x06 is that the TxSubmissionProtocol has its starting agency flipped around the same as all the other protocols. In 0x05, the remote server started with agency so we had to spin up TxSubmissionProtocol right away to listen for messages from the server. In 0x06, when doing regular syncing with the node, we can not connect TxSubmissionProtocol at all since the server will be waiting on us forever to send something.
When doing a sync, we should update to support 0x06 and just omit adding TxSubmissionProtocol if the server responds with 0x06.
The text was updated successfully, but these errors were encountered: