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

Migrate to new network message #244

Merged
merged 6 commits into from
Mar 11, 2021
Merged

Migrate to new network message #244

merged 6 commits into from
Mar 11, 2021

Conversation

bvbfan
Copy link
Contributor

@bvbfan bvbfan commented Feb 22, 2021

There is no need to hardfork message anymore, just use new one.

@bvbfan
Copy link
Contributor Author

bvbfan commented Feb 22, 2021

It seems not work, i will investigate.

Signed-off-by: Anthony Fieroni <[email protected]>
@bvbfan bvbfan force-pushed the fix/network_message branch from c1e8977 to 41d4678 Compare February 22, 2021 12:00
@bvbfan
Copy link
Contributor Author

bvbfan commented Feb 22, 2021

The transition cannot be done in one step, due to PushMessage uses the old (Bitcoin) start message, so for now we can run some nodes with this patch in another commit we can remove 41d4678#diff-00021eed586a482abdb09d6cdada1d90115abe988a91421851960e26658bed02R578

@monstrobishi monstrobishi merged commit 9bd1cc5 into master Mar 11, 2021
@monstrobishi monstrobishi deleted the fix/network_message branch March 11, 2021 08:10
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.

4 participants