v0.5.2

/api/transactions and /api/transactions/get now support returnAsset argument that will force it to return transaction asset in answer, this will help to move to less endpoints in future.

v0.5.1

This is mostly bug fix release. Now AIP-14 is accepted, and clients are working on implementing it, so it's behaviour was corrected, to be consistent with final AIP version.
All clients working with /api/chatrooms, should be updated, and use it only with 0.5.1 version or further.

Fixes:

• Fixed bugs with /api/chatrooms endpoint returning non consistent data
• /api/chatrooms endpoints now work according AIP-14 #32
• withPayments parameter was replaces with withoutDirectTransfer, that is opposite to it. Direct Transfers are returned by default.
• Signal messages now doesn't show in chatrooms
• Default limit for /api/chatrooms was decreased to 25 records from 100.

v0.5.0

• New /api/node endpoints
• New /api/chatrooms endpoint
• WebSocket server for light clients to subscribe for new transactions.
• Version/minVersion moved from config file.

v0.4.2

• Tests for Nodes — Fix the tests
• New API Tests
• New POST /api/transactions endpoint
• Updated sodium dependency to resolve problems with recent Node.js versions

v0.4.0

• Adding Fair Delegate System support starting from block with height 4359464
• Dependencies Update

Notice: next version that is scheduled for release in next week, won't accept any nodes less that 0.4.x

v0.3.2

• Fixing issue with transfering tokens in chat messages.

v0.3.1

• Adding nodeTimestamp field to API responses. This is not network breaking, so only nodes providing public api should be updated.

v0.3.0

• Adding support for Rich Content Messages (AIP 5)
• Adding support for Signal Messages (AIP 6)
• Fixing filters in state(KVS) transaction api

v0.2.1

• Updating moment-js dependancy. Old dependancy was marked as insecure, but it was used as dev-dependency for migration generation, so it wasn't a security issue.
• Updating README
• Fixing bug in state(KVS) transaction signing mechanism
• Making state(KVS) transaction signing mechanism compliant with AIP-3

v0.2.0

This release presents breaking api changes so minor version letter was incremented.
Key Value Storage (KVS or states) system was added, it is needed for implementing additional required features in client applications. Fees for KVS are same as for messages.
Endpoints were added to use this features.
New endpoints doesn't support node side encryption. So all signing should be done clientside. Example of usage is available at adamant-console package.

Changes

• Initial addition of Key Value Storage (KVS) system
• New API endpoints /states/, actions: store, get