Api calls for #339: needed api calls (mostly network) for supporting bts_tools #462
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bytemaster
added a commit
that referenced
this pull request
Nov 25, 2015
Api calls for #339: needed api calls (mostly network) for supporting bts_tools
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the following api calls:
get_advanced_node_parameters,set_advanced_node_parameters,get_potiential_peersaboutCode for
aboutwas ported from bitshares 0.9.x, with the difference that:BLOCKCHAIN_NAMEandBLOCKCHAIN_DESCRIPTIONin graphene, so they are not includedThis pull request doesn't include the
blockchain_get_witness_slot_recordsor thenetwork_set_allowed_peerscalls, I need to investigate more if they are required, and if so, will open a new issue for it at a later stage.