Skip to content

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

@ObiajuluM

Description

@ObiajuluM

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions