Skip to content

Releases: Adamant-im/adamant

v0.10.0

04 Jun 08:00
9cc6514
Compare
Choose a tag to compare
v0.10.0 Pre-release
Pre-release

Added

  • The includeDirectTransfers parameter for the /api/chats/get and /api/chatrooms endpoints in #91
  • New properties to the /api/node/status endpoint in #90:
    interface Response {
      loader: {
        loaded: boolean;
        now: number;
        syncing: boolean;
        consensus: number;
        blocks: number;
        blocksCount: number;
      }
      // ...
    }
  • timestampMs field for the transactions in #93
  • ?returnUnconfirmed=1 flag for transactions in #96
  • Socket connection between nodes in #99. Learn more at https://docs.adamant.im

Changed

  • count now is returned as a number in every response in #110

Fixed

  • The bug when transaction pool doesn't properly remove transactions in #108

Deprecated

  • GitHub Wiki. Use https://docs.adamant.im for documentation
  • The withoutDirectTransfers endpoint, use includeDirectTransfers instead

v0.9.0

28 Feb 17:49
a10b67d
Compare
Choose a tag to compare

Added

  • address parameter to /api/delegates/get endpoint, which previously only supported username and publicKey. Usage:

    /api/delegates/get?address=U1234567890

    See: API specification and PR #79

  • WebSocket now supports subscribing to multiple transaction types instead of just one. For message transactions, added assetChatTypes event to subscribe to Message Types. Learn more at the Documentation. PRs #84, #85

  • New properties to to the response of the /api/node/status endpoint by merging data from /api/loader/status and /api/loader/status/sync, reducing the number of requests needed to get full information of blockchain status:

    {
      // ...
      "loader": {
        "loaded": true,
        "now": 45345521,
        "syncing": false,
        "consensus": 100,
        "blocks": 0,
        "blocksCount": 0
      }
    }

    Refer to the API Specification for property meanings. PR #90

Fixed

  • Fixed unable to connect to peers whose version names include pre-release or build metadata (e.g., +alpha, -dev.0). Now supports SemVer-2.0. PR #88

  • Fixed peer removal after one-time connection errors. PR #89

  • Fixed config files validation #92

Optimized

  • /delegates/get endpoint to search for a single transaction

Other

v0.8.4-dev.0

12 Dec 19:56
aae1855
Compare
Choose a tag to compare
v0.8.4-dev.0 Pre-release
Pre-release

Added

  • Subscribing to transaction types (#84) and asset chat types in WebSocket (#85)

Other

  • Updated dependencies (#82 )
  • Added unit tests (#86)
  • Minor optimizations

v0.8.3

24 Nov 14:24
bca4f89
Compare
Choose a tag to compare
  • Updated default nodes
  • Removed config.json: do cp config.default.json config.json after set up

Note: save your config.json file before update: cp config.json config.json.backup

v0.8.2

05 Nov 21:06
02adde3
Compare
Choose a tag to compare
  • Added confirmations field for /api/chatrooms/U* endpoint (#72)

v0.8.1

13 Apr 04:47
95df4fc
Compare
Choose a tag to compare
  • Added the logs for database migration script

    Now the ADAMANT node will log the messages before and after executing migration script:

    [inf] 2023-12-22 04:00:25 | Found 5 pending migrations. Start executing, this may take a while…
    [inf] 2023-12-22 04:17:13 | Migrations have been successfully completed.
    
  • Changed the default Access-Control-Allow-Origin CORS header value

    The default value for the cors.origin property has been changed from reflecting the request origin (true) to *. See the documentation to learn more about CORS configuration for the ADAMANT node.

    {
      "cors": {
        "origin": "*" // default
      }
    }
  • Added the config.json file to .gitignore

    Now the user needs to create the config.json file himself or copy config.default.json to start the ADAMANT node.

    cp config.default.json config.json
    

v0.8.0

14 Jan 18:15
5214996
Compare
Choose a tag to compare
  • Added cors option in config.json (see #62)

  • You can now use either inId or isIn in /api/transactions and /api/chats/get endpoints.
    Example: /api/chats/get?InId=U6386412615727665758 and /api/chats/get?isIn=U6386412615727665758 are the same.

  • Users ID in /api/chats/get and /api/chatrooms endpoints became case insensitive.
    Example: /api/chatrooms/U6386412615727665758 and /api/chatrooms/u6386412615727665758 are the same.

  • Transactions and POST /api/accounts/delegates accept transaction in plain object and inside transaction property .
    Example:

    curl -X POST https://endless.adamant.im/api/transactions/process
       -H 'Content-Type: application/json'
       -d '{"type": 0, "amount": 100000000, ...}'  # or {"transaction": { "type": 0, "amount": 100000000, ... }}
  • Added confirmations property for /api/states/get endpoint

  • generatorPublicKey query optimization.

  • Fixed "permission denied for schema public" error

  • Other minor changes.

Breaking changes

  • /api/blocks endpoint doesn't return count any more

v0.7.0

15 Oct 05:02
e0408f3
Compare
Choose a tag to compare
  • Update dependencies
  • Move legacy code to /legacy dir
  • Remove legacy docs

v0.6.5

25 Sep 11:33
1c3bae2
Compare
Choose a tag to compare
  • Changed default broadcast settings
  • Update devDependencies
  • Fix tests
  • Update install bash script
  • Lint code
  • Add --genesis param
  • Add portWS 36665 for testnet

v0.6.0

17 Feb 09:04
fef0c69
Compare
Choose a tag to compare
  • Socket connections return recipientPublicKey
  • Transactions API, including KVS and Chats, return block_timestamp
  • Fix for migrations
  • Endpoint /states/get/ support for parameters SenderIds and keyIds
  • Endpoint /states/get/ support for POST requests
  • Documentation update