assembly
assembly
Ardor v2.3.2
singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Ardor Client: Ardor 2.3.2. Mandatory upgrade before Sept 22, 2020!

Author Topic: Ardor v2.3.2  (Read 2457 times)

Jelurida

  • Board Moderator
  • Jr. Member
  • ****
  • Karma: +33/-1
  • Offline Offline
  • Posts: 62
    • View Profile
Ardor v2.3.2
« on: August 11, 2020, 01:43:38 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.3.2

https://www.jelurida.com/ardor/downloads

sha256 checksums:

6cbfa094a66ed57b68dcc77886b473ef92d6cdbbaff37a19d14328c542cfcfaa  ardor-client-2.3.2.zip

4c52b419c734cae11777e5fe6efefae6f650e525bcff578eb30f7501ee8e7ee3  ardor-client-2.3.2.sh

The exe package must have a digital signature by "Jelurida Swiss SA".


Change log:

This stable release is a mandatory update for mainnet. A hardfork to enable
new functionality and activate the GPS child chain is scheduled for block
1453000 expected on Sep 22, 2020.

At the hardfork height, the GPS asset (assetID: 3123987739214429747) will be
migrated to a child chain. Existing asset exchange orders for the GPS asset
will be cancelled, further transactions with it will be disabled, and a
snapshot of the asset balances as of that height will be used to automatically
distribute the tokens of the newly enabled GPS child chain.

The following new features, already available on testnet, will be activated on
mainnet after the hardfork:

Allow sending zero fee child chain transactions even from accounts not yet
registered on the blockchain.

Allow setting up account control with zero max fees.

The AEUR child chain will become permissioned, thus disabling further
transactions with AEUR after the hardfork.

Locally generated SSL keystore

To simplify the setup of SSL certificates and a Java keystore required to enable
https communication. The node auto-generates certificates and keystore in
case none were provided. The auto-generated keystore can be used to setup Https
communication quickly on a local node.
When the nxt.apiSSL property is set to true and the keystore location is not
specified or the nxt.keyStorePath property is pointing to a missing file, the
node will automatically generate a key pair, a local root certificate and an SSL
certificate signed by it, to form a valid certificate chain. The node will
create a keystore containing these artifacts according to the format and
password specified in nxt.keyStoreType and nxt.keyStorePassword correspondingly.
The local root certificate is saved using the same path as the keystore file
with a file suffix "-ca.crt". Import this certificate as a trusted CA into the
browser keystore to enable the browser to validate the auto-generated
certificate chain.

When using light client or while downloading the blockchain, the local node
forwards API calls to a random remote node and confirms each API response with
up to three additional remote nodes. This functionality which was previously
implemented by the wallet is now implemented by the node itself to make it
faster and more reliable.

A new API - getAPIProxyReports - provides information about the light client
remote API calls and their confirmations.

Improved retrieval of prunable transactions and bootstrapping of archival
nodes.

Lightweight contracts framework improvements

Two new callbacks were added to the contract interface init and shutdown. init
can be used by contract developers to perform static initialization tasks used
during the lifetime of the contract, while shutdown can be used to reclaim
resources used by the contract before shutting it down.
When starting a node the init callback is invoked on all contracts loaded by the
contract runner. Similarly, when shutting down the node the shutdown callback is
invoked. When uploading a new version of an existing contract, when loading the
new contract reference the contract runner will first shutdown the existing
version of the contract then initialize the new version.

It now possible to submit transactions from processRequest callback.
Transactions returned using context.createTransaction() are automatically
broadcast to the node by the contract runner.

Due to the introduction of new functionality, some existing contracts developed
using older versions of Ardor must be recompiled and redeployed to the
blockchain.
The existing version of such a contract may throw an exception when loaded or
when triggered. Therefore, contract runner node operators should use the node
log file to watch for exception messages and redeploy the contract if necessary.

New sample contracts

Trading bot (CoinExchangeTradingBot.java) is a contract which performs market
making on the coin exchange and asset exchange.
Contract runners can define the holdings (coin or asset) on which to submit buy
and sell orders and the percentage difference from a base exchange rate loaded
from coinmarketcap, which serves as a sample data source.
The bot can be configured to compete with other traders or issue orders
according to the base exchange rate to provide liquidity.

The account balance notifier (AccountBalanceNotifier.java) monitors the account
balances of configured holdings and raises an alert in case their holding
balance drops below some minimum limit. The notifier can be used to monitor an
account performing market making to alert the operator in case a holding balance
is exhausted.

The chain monitor contract (ChainMonitor.java) monitors specific aspects of the
blockchain operations. It submits an alert to one or more notification services
in case a problem with the blockchain operation is detected.

The whale alert contract (WhaleAlert.java) watches the blockchain for balance
changes larger than a pre-defined threshold defined per holding and alerts the
configured notification service when such transaction is included in a block.

Notification service contracts (SlackNotifier.java, TelegramNotifier.java) are
utility contracts used for posting messages from other contracts to Slack and
Telegram respectively.

Wallet pages which do not rely on any specific account such as the Blocks,Peers,
Generators,Node Configuration pages can be opened from the settings menu without
requiring the user to login first.

To prevent repetition. the administrator password setting was moved from the
account settings to the device settings dialog.
Users who defined the password in the account settings will have to manually
redefine it in the wallet device settings.

The wallet sidebar displays an approximate countdown for the next expected block
using information extracted from the generators list.

The Node JS module can now connect to a node using https with a self signed
certificate by setting disableSslCertificateVerification to true in config.json

Added a tax reporting add-on which produces a report in CSV format compatible
with the CoinTracking service.

Updated Jetty to version 9.4.31.


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAl8yg7IACgkQDPnHRy2A
uLlJ8w/9Fo4OKHogXoa6p6G2IEBgoyldnJ8zovI5oi4hUzo2BPn0oPBRN2GUrveK
PiSSDTuWOMdWHiN6tuwajPWqWLWArdzDJ6+MGpVNeXW89FxxS0gBtR8b+s5V4523
F1Nn6gxxRbVtagkNcweKaGMIbV4THDZleHG9S44Xlw02MX8CHIbj/c5JHJ2+OVRU
oKhKo1InIWXg6KvxpCnyQ0CLyXaqETzKOjkyd5pTjwNFDVvygYXbwUJrA0JwZlBG
kfKTwThMHCR9W71JAwJdBbWIqGVvsqws1haa8kkda2hfxM/Ev3Iw6kLh+M7EbHCU
T4QvEeSnD8xqcfDC08L70jlh9aAT1GrF0JkcYJImAvloWtjvkf0fOQqwXfGkRz8V
VfPoEojvANcotyaf2TaT7TIbWY5pVdrL5llGjMnFjmvW75YM3nyOeqGjG9SsTMaP
yax0AHqk4/Yne9XjFEja/OysPeThZRnQ6TkOtmzsU5yqKjGHqf6W9EXDOy4Iflrv
3Kko5XBwzrtXsQiEi/hr4yoLVYkRfLswVJyYPu2krlqAs0/u7wCYVm7g+l6D2RcG
5ekBerv7dswXc5chA6dEHNDtcPNI++6mKmpbyuvVcqxYQG2uNgw4WNMrgNpYJSsN
MQ6i0loEoMSgXmeGrLwW/rss/dHx6pggXMoO9vKRG4jHz5KPe34=
=PEYi
-----END PGP SIGNATURE-----
Logged
 

elective-stereophonic
elective-stereophonic
assembly
assembly