-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Note that fee_ref
will be removed if XRPFees is enabled
#2183
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor suggestion for clarity
content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Elliot Lee <[email protected]>
content/references/http-websocket-apis/public-api-methods/subscription-methods/subscribe.md
Outdated
Show resolved
Hide resolved
Minor suggestion to avoid ambiguity. |
…cription-methods/subscribe.md Co-authored-by: Amarantha Kulkarni <[email protected]>
@ximinez - I accepted the suggestion as it made sense to me - but please do let me know if you disagree |
I agree with the suggestion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
XRPLF/rippled#4247 removed the
fee_ref
field from the Ledger subscription stream ifXRPFees
is enabled. This is becauseXRPFees
removes the concept of fee levels from rippled, and that's whatfee_ref
returned, so it doesn't make any sense to include anymore.