Skip to content

Latest commit

 

History

History
471 lines (365 loc) · 30.9 KB

HISTORY.md

File metadata and controls

471 lines (365 loc) · 30.9 KB

ripple-lib Release History

0.18.2 (2018-02-13)

The SHA-256 checksums for the browser version of this release can be found below.

% shasum -a 256 *
f08ab61137255be3639e9d210ded2a182b6e0388f257a70d9b372ce7e7e518a6  ripple-0.18.2-debug.js
0604835b8421391167b4314ce93a76b5994780a08bd7edf36d91eb5e8f2643a2  ripple-0.18.2-min.js
fda56ab5c8256e04355e20064877ef4053f26c87f37cfcf861340f22bf89ee40  ripple-0.18.2.js

0.18.1 (2018-01-27)

Note: The package published to npm for this version did not include updated browser builds. If you are using a CDN that pulls from npm, please use 0.18.2 or later.

The SHA-256 checksums for the browser version of this release can be found below.

% shasum -a 256 *
6871855a2af1dc591ef557d442c11e8c60e01c5932054e13e8cbb84a182f45e0  ripple-0.18.1-debug.js
331f0baff46af44933a8fa31f128132945ff82a147acfff0a7315adb446e3de0  ripple-0.18.1-min.js
26324bb0725d2d484fe3b6086335d49734f45dc647b07c60746e0d8619f1ed3e  ripple-0.18.1.js

0.18.0 (2018-01-25)

0.17.9 (2017-11-14)

The SHA-256 checksums for the browser version of this release can be found below.

% shasum -a 256 *
b52f251eedac2509d72093eab1e8dba0d0f4a9fe6a28ec1cc90853cfb0fd7110  ripple-0.17.9-debug.js
d577a2bbdbdf7535c5365a1c52a2a31989d1b966e30abcba65c87133a536b9dc  ripple-0.17.9-min.js
ff4c3002842fac72ec2ebbd081e9594b0de6050d4d051a8fd6c06adb9a351488  ripple-0.17.9.js

The SHA-1 checksums for the browser version of this release can be found below.

% shasum *
e1995afc34aef6accd269cfccc55a45619618a41  ripple-0.17.9-debug.js
e6ad9a9c111ab696f5637bfa372d80999e5ae362  ripple-0.17.9-min.js
4866494ec5f9095cc34bea142f1e2b8ac5f7fbf8  ripple-0.17.9.js

0.17.8 (2017-11-06)

0.17.7 (2017-05-08)

  • Replace AJV with jsonschema

0.16.5 (2016-01-21)

0.16.4

0.16.2

  • Bump ripple-binary-codec dependency version to 0.1.1 to fix issue with computeLedgerHash for transactions with DeliverMin

0.16.1

0.16.0

BREAKING CHANGES

OTHER CHANGES

0.15.2

0.15.1

0.15.0

BREAKING CHANGES

OTHER CHANGES

0.14.0

BREAKING CHANGES

OTHER CHANGES

0.13.2

0.13.1

0.13.0

BREAKING CHANGES

OTHER CHANGES

0.12.9

0.12.7 and 0.12.8

0.12.6

0.12.15

0.12.4

0.12.3

0.12.2

0.12.1

BREAKING CHANGES

OTHER CHANGES

0.12.0

BREAKING CHANGES

OTHER CHANGES

0.11.0

0.10.0

  • Transaction changes
  • Important tef* and tel* and errors will no longer be presented as final. Rather than considering these errors final, ripple-lib will wait until the LastLedgerSequence specified in the transaction is exceeded. This makes failures more definitive, and ensures that no transaction will resubmit indefinitely.
  • A new, final tej-class error is introduced to account for transactions that are locally determined to have expired: tejMaxLedger.
  • Allow per transaction fees to be set, transaction.setFixedFee()
  • Improve memo support
    • Add MemoFormat property for memo
    • Enforce MemoFormat and MemoType to be valid ASCII
    • Support text and json MemoFormat
  • Update sjcl library
    • Improved entropy by taking advantage of platform crypto
    • Use jscl's k256 curve instead of altering the c256 curve with k256 configuration
    • Deprecated: The c256 curve is linked to the k256 curve to provide backwards compatibility, this link will be removed in the future
  • Fix empty queue check on reconnect

0.9.4

0.9.3

0.9.2

BREAKING CHANGES

OTHER CHANGES

Example on how to use paging with account_offers:

// A valid `ledger_index` or `ledger_hash` is required to provide a reliable result.
// Results can change between ledger closes, so the provided ledger will be used as base.
var options = {
    account: < rippleAccount >,
    limit: < Number between 10 and 400 >,
    ledger: < valid ledger_index or ledger_hash >
}

// The `marker` comes back in an account request if there are more results than are returned
// in the current response. The amount of results per response are determined by the `limit`.
if (marker) {
    options.marker = < marker >;
}

var request = remote.requestAccountOffers(options);

Full working example

0.9.1

  • Switch account requests to use ledgerSelect rather than ledgerChoose (278df90)
  • Deprecated setting ident and account_index on account requests (278df90)
  • Change initial account transaction sequence to 1 (a3c1d06)
  • Fix: instance transaction without remote (d3b6b81)
  • Fix: account root request ledger argument (bc1f9f8)
  • Fix: rsign.js local signing and example (d3b6b81 and f1004c6)

0.9.0

BREAKING CHANGES

OTHER CHANGES

  • Add routes to the vault client for KYC attestations (ed2da574)
  • Currency: add show_interest flag to show or hide interest in Currency.to_human() and Currency.to_json() Example use in tests
  • Configurable maxAttempts for transaction submission (d107092)
  • Binformat: added missing TransactionResult options (6abed8d)
  • Shrinkwrap packages for dependency locking (2dcd5f9)
  • Fix: Amount.to_human() precision bugs (4be209e and 7708c64)
  • Fix: change handling of requestLedger options (57b7030)

0.8.2

  • Currency: Allow mixed letters and numbers in currencies
  • Deprecate account_tx map/reduce/filterg
  • Fix: correct requestLedger arguments
  • Fix: missing subscription on error events for some server methods
  • Fix: orderbook reset on reconnect
  • Fix: ripple-lib crashing. Add potential missing error handlers

0.8.1

  • Wallet: Add Wallet class that generates wallets
  • Make npm test runnable in Windows.
  • Fix several stability issues, see merged PR's for details
  • Fix bug in Amount.to_human_full()
  • Fix undefined fee states when connecting to a rippled that is syncing

0.8.0

  • Orderbook: Added tracking of offer funds for determining when offers are not funded
  • Orderbook: Added tests
  • Orderbook: Update owner funds
  • Transactions: If transaction errs with tefALREADY, wait until all possible submissions err with the same before emitting error. Fixes a client "Transaction malformed" bug.
  • Transactions: Track submissions, don't bother submitting to unconnected servers
  • Request: request.request() now accepts an array of servers as first argument. Servers can be represented with URL, or the server object itself.
  • Request: request.broadcast() now returns the number of servers request was sent to
  • Server: Acquire host information from server without additional request
  • Amount: Add a constant for the maximum canonical value that can be expressed as a Ripple value
  • Amount: Make Constants static fields on the class, instead of a separate export

0.7.39

  • Improvements to multi-server support. Fixed an issue where a server's score was not reset and connections would keep dropping after being connected for a significant amount of time.
  • Improvements in order book support. Added support for currency pairs with interest bearing currencies. You can request an order book with hex, ISO code or full name for the currency.
  • Fix value parsing for amount/currency order pairs, e.g. Amount.from_human("XAU 12345.6789")
  • Improved Amount parsing from human readable string given a hex currency, e.g. Amount.from_human("10 015841551A748AD2C1F76FF6ECB0CCCD00000000")
  • Improvements to username normalization in the vault client
  • Add 2-factor authentication support for vault client
  • Removed vestiges of Grunt, switched to Gulp

0.7.37

  • Deprecations

    1. Removed humanistic amount detection in transaction.payment. Passing 1XRP as the payment amount no longer works.
    2. remote.setServer uses full server URL rather than hostname. Example: remote.setServer('wss://s.ripple.com:443')`
    3. Removed constructors for deprecated transaction types from transaction.js.
    4. Removed invoiceID option from transaction.payment. Instead, use the transaction.invoiceID method.
    5. Removed transaction.transactionManager getter.

  • 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 specify LastLedgerSequence. 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 return XRP - 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

0.7.35

  • LastLedgerSequence is set by default on outgoing transactions. This refers to the last valid ledger index (AKA sequence) for a transaction. By default, this index is set to the current index (at submission time) plus 8. In theory, this allows ripple-lib to deterministically fail a transaction whose submission request timed out, but whose associated server continues to emit ledger_closed events.
  • Transactions that err with telINSUF_FEE_P will be automatically resubmitted. This error indicates that the Fee supplied in the transaction submission request was inadequate. Ideally, the Fee is tracked by ripple-lib in real-time, and the resubmitted transaction will most likely succeed.
  • Added Transaction.iff(function(callback) { }). Callback expects first argument to be an Error or null, second argument is a boolean which indicates whether or not to proceed with the transaction submission. If an iff function is specified, it will be executed prior to every submission of the transaction (including resubmissions).
  • Transactions will now emit presubmit and postsubmit events. They will be emitted before and after a transaction is submitted, respectively.
  • Added Transaction.summary(). Returns a summary of a transaction in semi-human-readable form. JSON-stringifiable.
  • Remote.requestAccountTx() with binary: true will automatically parse transactions.
  • Added Remote.requestAccountTx filter, map, and reduce.
  remote.requestAccountTx({
    account: 'retc',
    ledger_index_min: -1,
    ledger_index_max: -1,
    limit: 100,
    binary: true,

    filter: function(transaction) {
      return transaction.tx.TransactionType === 'Payment';
    },

    map: function(transaction) {
      return Number(transaction.tx.Amount);
    },

    reduce: function(a, b) {
      return a + b;
    },

    pluck: 'transactions'
  }, console.log)
  • Added persistence hooks.
  • General performance improvements, especially for long-running processes.