-
Deprecations
- Removed humanistic amount detection in
transaction.payment
. Passing1XRP
as the payment amount no longer works. remote.setServer
uses full server URL rather than hostname. Example:remote.setServer('wss://s
.ripple.com:443')`- Removed constructors for deprecated transaction types from
transaction.js
. - Removed
invoiceID
option fromtransaction.payment
. Instead, use thetransaction.invoiceID
method. - Removed
transaction.transactionManager
getter.
- Removed humanistic amount detection in
-
Improved multi-server support. Servers are now ranked dynamically, and transactions are broadcasted to all connected servers.
-
Automatically ping connected servers. Client configuration now should contain
ping: <seconds>
to specify the ping interval. -
Added
transaction.lastLedger
to specifyLastLedgerSequence
. Setting it this way also ensures that the sequence is not bumped on subsequent requests. -
Added optional
remote.accountTx
binary parsing.{ binary: true, parseBinary: false }
-
Added full currency name support, e.g.
Currency.from_json('XRP').to_human({full_name:'Ripples'})
will returnXRP - Ripples
-
Improved interest bearing currency support, e.g.
Currency.from_human('USD - US Dollar (2.5%pa)')
-
Improve test coverage
-
Added blob vault client. The vault client facilitates interaction with ripple's namespace and blob vault or 3rd party blob vaults using ripple's blob vault software (https://github.com/ripple/ripple-blobvault). A list of the available functions can be found at docs/VAULTCLIENT.md