Adamant Versions Save

ADAMANT Blockchain Node

v0.8.3

5 months ago
  • 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

6 months ago
  • Added confirmations field for /api/chatrooms/U* endpoint (#72)

v0.8.1

1 year ago
  • 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

1 year ago
  • 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

1 year ago
  • Update dependencies
  • Move legacy code to /legacy dir
  • Remove legacy docs

v0.6.5

2 years ago
  • 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

4 years ago
  • 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

v0.5.2

4 years ago

/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

5 years ago

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

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