Xrpl-py

Latest version: v3.0.0

Safety actively analyzes 685525 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 5

3.0.0

BREAKING CHANGE
- Use rippled API v2 as default in requests

Added
- Support for the DeliverMax field in Payment transactions
- Support for the `feature` RPC

Fixed
- Allow empty strings for the purpose of removing fields in DIDSet transaction

Removed
- Remove deprecated `full`, `accounts`, and `type` parameters from ledger request model

2.6.0

Added
- Support for the Price Oracles amendment (XLS-47).
- Add `nfts_by_issuer` clio-only API definition
- Included `ctid` field in the `tx` request.
- `from_xrpl` method accepts input dictionary keys exclusively in the proper XRPL format.

Fixed
- Added support for `XChainModifyBridge` flag maps (fixing an issue with `NFTokenCreateOffer` flag names)
- Fixed `XChainModifyBridge` validation to allow just clearing of `MinAccountCreateAmount`
- Added support for IDE auto-completion of model constructors
- Currency codes with special characters not being allowed by IssuedCurrency objects.
- Construction of Wallet throws an "Invalid Seed" error, if the secret is not decode-able.
- Rectify the incorrect usage of a transaction flag name: Update `TF_NO_DIRECT_RIPPLE` to `TF_NO_RIPPLE_DIRECT`
- Add the missing `AMMDeposit` Flag `TF_TWO_ASSET_IF_EMPTY`

Removed:
- Remove Hooks faucet since it's now on the Xahau testnet.

2.5.0

Added
- Support for the DID amendment (XLS-40).
- Support for `server_definitions` RPC

Fixed
- Exported `get_nftoken_id` and `parse_nftoken_id` at the `xrpl.utils` level
- Fixed issue in `get_nftoken_id` where error is opaque when there are no `NFTokenPage`s

Changed
- Removed sidechain-net1 Devnet faucet support as it has been decommissioned. Users should instead use the bridge between Devnet and sidechain-net2 for testing.
- Removed amm-devnet faucet support as is will soon be decommissioned

2.4.0

Added
- Added new syntax for `SetFee` pseudo transaction sent after the [XRPFees](https://xrpl.org/known-amendments.html#xrpfees) amendment. (Backwards compatible)
- Support for [XLS-38d (XChainBridge)](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-38d-XChainBridge)

Fixed
- Update request models related to AMM
- Better error handling for when a `Wallet` is passed into an account or destination field
- Fixed AMMBid fields (BidMin, BidMax) with correct type IssuedCurrencyAmount

2.3

- `book_changes`: Returns a `validated` field in its response, which was missing in prior versions.

The following additions are non-breaking (because they are purely additive).

- `server_definitions`: A new RPC that generates a `definitions.json`-like output that can be used in XRPL libraries.
- In `Payment` transactions, `DeliverMax` has been added. This is a replacement for the `Amount` field, which should not be used. Typically, the `delivered_amount` (in transaction metadata) should be used. To ease the transition, `DeliverMax` is present regardless of API version, since adding a field is non-breaking.
- API version 2 has been moved from beta to supported, meaning that it is generally available (regardless of the `beta_rpc_api` setting).

2.3.0

Added
- Add AMM support [XLS-30](https://github.com/XRPLF/XRPL-Standards/discussions/78)

Page 1 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.