-
Notifications
You must be signed in to change notification settings - Fork 60
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
[Bug] Types Confusion in Source and Docs #738
Comments
Also request_block_header(s) Brandt see JIRA |
The wallet protocol documentation (here: https://docs.chia.net/wallet-protocol/) documents (or, at least, mentions) the message request_block_header and respond_block_header. Those messages are deprecated and replaced by request_block_headers (plural) and respond_block_headers.
|
Moving this to the Docs repo for better tracking |
Hey @buggybuck , we are working on cleaning up the wallet protocol docs in this pr: Do take note though that the docs site is accurate regarding the messages you have listed in this ticket. The confusion arises from the part of the chia codebase that is being reviewed. The file protocol_message_types is using outdated messages and wrapping them to integrate the new messages. The source code that contains the most up to date information on wallet_protocol messages is the wallet_protocol file (https://github.com/Chia-Network/chia-blockchain/blob/main/chia/protocols/wallet_protocol.py) also linked at the top of the docs page for the wallet protocol. I have reached out to the dev team to see if we can update the protocol_message_types file to align with the currently used messages but it might be some time to clear out the tech debt leading to that difference (this is the pr for that change: Chia-Network/chia-blockchain#19132). As a side note, some of the wallet protocol messages are no longer using the python codebase (ex. As we migrate everything from python to rust you will see more messages make that switch and we will make sure to add that rust repo to the docs site for reference. This was a lot of info, do you have any followup questions or concerns? (note I will update here once the pr is in place and the docs site is updated) |
Hi BrandtH22! Thank you for your explanation and the pointers! Much appreciated! |
Hi there! Here is another mismatching pair: request_ses_hashes (76) / respond_ses_hashes (77) Kind regards |
What happened?
Hey there!
I'm a little confused by how some of the types have different names in the source code [1] and in the documentation [2].
You find 'register_interest_in_puzzle_hash' (enum: 70) in the source but not in the docs. Instead you find 'register_for_ph_updates' in the docs which in turn has no enum in the source.
'register_interest_in_coin' (enum: 72) <-> 'register_for_coin_updates'. Same situation.
'respond_to_ph_update' (enum: 71) <-> 'respond_to_ph_updates'. It's plural in the docs.
'respond_to_coin_update' (enum: 73) <-> 'respond_to_coin_updates'.
Is there a system to the madness? :D
[1] chia-blockchain/chia/protocols/protocol_message_types.py
[2] docs.chia.net
Version
main
What platform are you using?
Linux
What ui mode are you using?
GUI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: