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

Oracle Set Transaction: Inconsistent Behavior with Missing AssetPrice Field #794

Open
ObiajuluM opened this issue Jan 4, 2025 · 0 comments

Comments

@ObiajuluM
Copy link

The XRPL documentation states: "Token pairs in the transaction with a missing AssetPrice field delete corresponding token pairs in the object."

However, when creating an OracleSet transaction without the AssetPrice field, the following error occurs:

xrpl.models.exceptions.XRPLModelException: {'price_data_series': 'Field must have both AssetPrice and Scale if any are present'}

This behavior seems contradictory to the documented functionality. Could you please investigate and clarify the expected behavior for OracleSet transactions with missing AssetPrice fields?

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

No branches or pull requests

1 participant