-
client_resource_id
cannot be reused anymore for failed transactions 3b4c1636 -
Removed deprecated depoly/dev config 3eae89e7
-
Move hash, ledger and state fields to be on root response object fbc8840c
Deprecations
- In a future version of ripple-rest
issuer
will be renamed tocounterparty
-
Add place and cancel order functionality d80d198 and 274f5236 and a384c5d5 and e6a8c74a and bbf386ec
-
Add orderbook functionality, get an orderbook for a currency pair 41905cb9
-
Allow a fixed fee to be set on a payment aaa9efae
-
Make response objects consistent for payment history 159e53cb
-
Support paging behavior for balances and trustlines 6980ab7 and d5a153e3
-
Add code to allow rippled in standalone mode and not having a recently closed ledger 3d45a81d
-
Support gzip compression8dc2365d
-
Set SendMax for difference source and destination issuers e7726090
-
Allow a
url_base
for status url's to be set from config 93ffb6c1 -
Add query parameter for only showing frozen balances a9b246bd
-
Add cors allow methods 18e52a06
-
Increase default account_tx limit a2ed905f
-
Use the
ripple-lib-transactionparser
to compute transaction balance changes 8b900bf0 -
Fix parameter discrepancy,
*_froze_line
->*_trustline_frozen
2701c0b and a8aeeec -
Fix: allow trust line to be set to 0 333bf320
-
Add tests to show use of interest-bearing currencies 9c5412f
-
Add configuration to allow self-signed certificates 3503049b
-
Update ripple-lib which fixes several stability problems and improving transaction submission reliability, see ripple-lib releases
-
Add
validated
query parameter to POST payment, account settings and trustlines. When set to true this will force the request to wait until the transaction has been validated. f2710f4b, 1ee9c9ff, f243fef9 -
Add
/v1/transaction-fee
endpoint to retrieve the current fee that connected servers are charging. 212c0bfb and afaa381b -
Support
last_ledger_sequence
in POST payments, sets the last ledger this payment can be included in. -
Add config entry to configure
max_transaction_fee
. This allows you to set the maximum fee you're willing to pay for any transaction. Documented changes
-
Memo field support (pull 154)
-
Add
destination_amount_submitted
andsource_amount_submitted
to Payment (0d3599b and 67134e3) -
New endpoint to generate an address/secret pair,
/wallet/new
-
Expose
router
andremote
asRippleRestPlugin
to use as a plugin for other modules -
Log all connected servers, add reconnect to servers on SIGHUP
-
Endpoints renamed and removed (6802423):
- new
/v1/accounts/new
->v1/wallet/new
- removed
/v1/tx/{:hash}
- removed
/v1/transaction/{:hash}
- use
/v1/transactions/{:hash}
to get a transaction by hash - removed
/v1/payments
- use
/v1/accounts/{address}/payments
to submit a payment
- new
-
New configuration, you will have to change your config file. Documented changes
-
Refactored response and error handling, improves consistency of response messages. The response and error message format has changed.
-
New database interface, support for sqlite in memory or persistent through config path in
config.json
-
Deprecated Postgres support. Support sqlite only
-
Add protection against POODLE (cb4f12c)
-
Fix: always set issuer on
destination_amount
for path results (1b0c731) -
Transitioned to Express4
-
Centralize connection checking, improves consistency of connected responses
-
Centralize logging using winston, timestamps on all logs
-
New test-suite
-
Tied api version to major package version and added package version to index page
/
or/v1
-
Update ripple-lib which fixes several stability problems and crashes
-
Code refactor and cleanup
-
Fix: improper SetFlag/ClearFlag collision error message (d26ec5e)
-
Fix:
tec
transaction errors represented as success, resulting in false positives (d14c51c) -
Fix: issue where forcible server connectivity check would cause permanent server disconnect
-
Fix: show index page while hitting root
/
-
Fix: issue with notification parsing
-
Fix: check and validate issuer upon payment
-
Fix: database reset on startup
-
Fix: Check tx.meta exists before accessing
-
Fix: Allow browser-based client to make POST to ripple-rest server
-
Fix: Occasional crash on getting payments for account
-
Fix: Check that tx.meta exists before accessing
-
Fix: Case where ripple-rest would crash when rippled could not be connected to
-
Change rconsole logging from stderr to stdout
-
Add timestamps to HTTP(S) request logging
-
Fix database reset on startup
07/29/2014
- Enable invoiceID
- Do not limit the amount of account transactions per ledger to 10, fixing the issue where no incoming transactions were ever notified.
07/16/2014
- Return 502 Bad Gateway middleware when remote is not connected to rippled.
- 502 Middleware fixes the crash-on-startup bug when clients try to connect before ripple rest is connected to rippled.
07/10/2014
- Code climate integration badge
- capistrano scripts for server deployment
- new version of ripple-lib
- Setting SendMax on payments
- Fix broken outgoing payments endpoint
##1.1.1 06/18/2014
- Add Istanbul code coverage tests
- Refactor out express app object
- Add a few integration tests using superagent
- Return 500 instead of 200 on invalid ripple address
06/11/2014
- Add exclude_failed option to getAccountTransactions (defaults to false)
- Add protocol, host, and port (when applicable) to URLs returned to client
- Coveralls for testing
Internal Changes
- Add JsDoc comments to transactions.js, payments.js, and notifications.js
- Centralize ripple-lib transaction submit and get functions in transactions.js
- Significantly simplify getAccountTransactions logic and parameters set by recursive call
- Test ripple-lib transaction functions
- Test transaction submission to ensure transaction is saved to the database every time its state is changed
- Test payment submission and retrieval
- Test notifications
- Move notification and payment formatter functions into notifications.js and payments.js, respectively
- Replace hard-coded server connection timeout value with exported variable in server-lib.js
- Callback with error and entry for function to query database for transaction in getTransactionHelper
- Prevent second HTTP response for error after transaction proposed event in submitTransaction function
- Validate account in getTransaction
- Attach client_resource_id in getTransaction so it is correctly returned to client
- Strange pathfinding error message when no paths are found because of a lack of liquidity
06/10/2014
- GET /v1/accounts/{:account}/payments/{:hash} not responding
06/04/2014
- Client resource id now properly returned
- XRP Pathfind bug
- Pathfinding error message
- missing invoide_id
- normalize account settings
- notification timestamp formatting
- Travis.yml for Continuous Integration
- License
- Tests for balances, trust lines
- Add debug mode