Skip to content

Bulk pull ascending flag#3867

Merged
clemahieu merged 4 commits intonanocurrency:developfrom
clemahieu:bulk_pull_ascending_flag
Jul 20, 2022
Merged

Bulk pull ascending flag#3867
clemahieu merged 4 commits intonanocurrency:developfrom
clemahieu:bulk_pull_ascending_flag

Conversation

@clemahieu
Copy link
Copy Markdown
Contributor

No description provided.

…g requests the server to operate on account chains in ascending order toward higher block hight, rather than descending order toward the initial block.
@clemahieu clemahieu added the protocol change Change to protocol requiring new version label Jul 18, 2022
@clemahieu clemahieu added this to the V24.0 milestone Jul 18, 2022
@clemahieu clemahieu merged commit a8681a4 into nanocurrency:develop Jul 20, 2022
dsiganos pushed a commit to dsiganos/nano-node that referenced this pull request Oct 19, 2022
* Add a new flag to the bulk_pull messaged called 'ascending'. This flag requests the server to operate on account chains in ascending order toward higher block hight, rather than descending order toward the initial block.
* Increasing protocol version indicating support for the bulk_pull ascending flag.
* Adding separate convenience function section and commenting node::process function.
# Conflicts:
#	nano/core_test/message.cpp
dsiganos pushed a commit to dsiganos/nano-node that referenced this pull request Nov 14, 2022
* Add a new flag to the bulk_pull messaged called 'ascending'. This flag requests the server to operate on account chains in ascending order toward higher block hight, rather than descending order toward the initial block.
* Increasing protocol version indicating support for the bulk_pull ascending flag.
* Adding separate convenience function section and commenting node::process function.
# Conflicts:
#	nano/core_test/message.cpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

protocol change Change to protocol requiring new version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants