Ardor v2.2.0e singapore
Please login or register.

Login with username, password and session length
Advanced search  


Latest Stable Ardor Client: Ardor 2.3.3.

Author Topic: Ardor v2.2.0e  (Read 7595 times)


  • Board Moderator
  • Jr. Member
  • ****
  • Karma: +33/-1
  • Offline Offline
  • Posts: 62
    • View Profile
Ardor v2.2.0e
« on: November 02, 2018, 10:19:42 am »

Hash: SHA512

Release 2.2.0e

sha256 checksums:



The exe and dmg packages must have a digital signature by "Jelurida Swiss SA".

Change log:

This is an experimental release, and a MANDATORY upgrade for all testnet nodes.
It can also be used on mainnet.

Added Asset Properties feature, to be activated at block 455000 on testnet only.

Asset Properties allow attaching metadata to assets, in the form of name/value
pairs. The property name can be up to 32 characters, and property value up to
160 characters in length. Anyone can set a property on an asset. Only the asset
issuer, or the setter of the property, can delete a property. The setter of a
property can edit it by setting a new property with the same name.

New APIs: SetAssetProperty, DeleteAssetProperty, GetAssetProperties.

Implemented freezing of assets and currencies, to be used for tokens that are
scheduled to become child chains, or need to be deactivated for other reasons.

Freezing of arbitrary assets or currencies is not (and will not be) supported.
The freezing of a particular holding must first be enabled in a new release,
and is then triggered at a predefined height, optionally specified as asset
property for assets, or account property for currencies.

After the freeze height, no further transactions with the frozen holding are
possible (with the exception of setting or deleting asset properties). Freezing
is not reversible.

Implemented migration of a frozen asset or currency to a new child chain. The
migration of a particular holding must first be enabled in a new release, and
is then triggered at a predefined height, optionally specified as asset property
for assets, or account property for currencies.

Implemented loading of account balances for new child chains. The Dominium child
chain will be launched on testnet at or after block 455000, with testnet
balances allocated to developer accounts only.

Fixed loading transaction voucher which contains attached encrypted message.

Node log file name changed from nxt.log to ardor.{n}.log where {n} is the log
file number. The current log file is always named ardor.0.log. Up to 10 log
files are kept.

The windows startup script run.bat no longer relies on the windows registry
when looking up the Java version.

Lightweight Contracts:

The contract runner now executes contracts in their own sandbox which restricts
the contract permissions based on a standard Java policy file named ardor.policy
By default contracts allowed to connect to any address, and read, write and
delete files in the temp folder of the contract runner workstation. Direct
access to the local workstation, or the local blockchain not through the APIs
is blocked by default. The contract runner operator can grant additional
permissions per contract or for all contracts submitted by a specific account.
See examples in ardor.policy file.

Added support for deployment and verification of single source file contract
which compiles into multiple class files. The contract classes are automatically
packaged into a Jar file when deployed to the blockchain. Similarly verification
of the contract unpacks the Jar and compares individual class files.

Parameter injection is now supported using the ContractInvocationParameter,
ContractSetupParameter and ContractRunnerParameter annotations. This reduces
contract boiler plate code for reading parameters.

Contract class selector was added to the contract manager plugin. Users
upgrading from a previous release will need to redeploy the IntelliJ plugin
after installing this version. The plugin version should be 2.2.0.

Contract runner parameters can be specified in the file using
the addon.contractRunner. prefix. The contracts.json configuration file is now
only used when specifying secret contract runner parameters so can be ignored
in most configuration.

It is no longer required to define contracts which do not setup parameters in
the contract.uploader.json file.

See: for more details and

Due to interface changes introduced by this release, all existing contracts will
have to be redeployed on testnet and contract runners using a previous version
won't be able to run contracts deployed using the current version.

On testnet only, after block 455000 the average block time will be reduced to
10 seconds. This is to allow faster testing and development, and to test the
feasibility of reducing block time should the need arise on mainnet.




  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: Ardor v2.2.0e
« Reply #1 on: November 02, 2018, 10:38:26 am »

Mobile app link
SHA256 6ae06bd6cef0bce9b414b49b3e33d3316094cf5eb39a4813995c436135b22420
NXT Core Dev
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651


  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: Ardor v2.2.0e
« Reply #2 on: November 04, 2018, 07:57:12 am »

I think reduce block time is better,not sure down to 10 seconds though,I also wonder is it possible to prohibited block time less then 5 seconds and bigger than 30 seconds?


  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: Ardor v2.2.0e
« Reply #3 on: November 17, 2018, 01:13:49 pm »

I want to report a small bug.

Open account ARDOR-BLCK-V7R9-E3P9-32SWY on testnet,this account is Mandatory Approval by asset.

Click Account Details,then Account Control,then click Asset,you will see a errorCode 5 popup.