assembly
assembly
Show Posts - Jelurida
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Ardor Client: Ardor 2.2.5

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Jelurida

Pages: [1] 2 3
1
Nxt Helpdesk / Re: Cannot connect to /nxt-proxy No openAPI peers found
« on: September 19, 2019, 08:34:27 pm »
Did you try the experimental 1.12.0e version? It has some networking improvements to mitigate this problem. Also, try leaving the wallet running for some time to allow it to find such openAPI peers.

2
Official Nxt Releases / NRS v1.12.0e
« on: August 29, 2019, 03:40:36 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


Release 1.12.0e

https://www.jelurida.com/

sha256 checksums:

923f12ed6ac471f4133c001cf2fcfa6015c7eff95d24763641ff81e36cca9663  nxt-client-1.12.0e.zip

c07eb19c95776f20845368143c8e78ca471afb347e7ca10976d8744f66cb539d  nxt-client-1.12.0e.sh

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


Change log:

This is an experimental release, enabling several new features on testnet
only at block height 2500000. All testnet nodes must upgrade to this release
before this block (expected Sept 1, 2019). This release can also be used on
mainnet but upgrade is optional.

New features:

Added Asset Dividends payment by asset or currency. This allows paying asset
dividends not only in NXT, but also in any asset or monetary system currency.

Added Asset Properties feature, to allow setting arbitrary name/value metadata
on assets. Any user can set a property on any asset, only the asset issuer or
the user who sets the property can delete it.

Added Asset Increase transaction, allowing asset issuers to increase the total
number of asset shares available.

The Asset Delete History has been renamed to Quantity Change History and now
shows both asset deletion and new shares issuance transactions.
The getAssetDeletes API has been deprecated and a new getAssetHistory API can
be used to retrieve asset deletions, increases, or both.

Asset Dividends by Holding, Asset Properties and Asset Increase are currently
testnet-only features and will be enabled on mainnet at the next planned
hardfork block, exact height to be announced later.

New APIs related to the above features:

getAssetHistory, increaseAssetShares, getAssetProperties, setAssetProperty,
deleteAssetProperty


Process management add-ons, APIs and UI:

When enabling add-ons using the nxt.addOns property, if a package name is not
specified, the nxt.addons package is assumed, therefore it is no longer needed
to specify the full package name for the default add-ons included in the
release.

Added StartForging and ForgingEncryptedConfig add-ons to facilitate management
of forging processes.

The StartForging add-on reads the passphrases stored in a plain text file, as
defined in the property nxt.startForgingFile, one passphrase per line, and
automatically starts forging with each of these accounts when the server is
started. Since passphrases are stored unencrypted, this add-on should only
be used on well secured servers, or with accounts of insignificant value, or
in test environments.

For a secure way of starting forging with multiple accounts on a remote server
the ForgingEncryptedConfig add-on can be used to store the passphrases of
forging accounts in an encrypted file. This add-on exports two APIs:
saveForgingEncrypted and startForgingEncrypted, used respectively to save the
list of forging passphrases in an encrypted file, and to start forging with
them by only submitting to the server the password necessary to decrypt this
file. Note that at runtime, the forging account passphrases will still be kept
in server memory, but when using these add-ons will never need to be stored on
disk, and will not need to be re-submitted to the server each time forging
needs to be started. These add-ons are useful when forging on a fully trusted
node, and having to restart forging remotely without a risk of exposing the
passphrases in transit.

Added StartFundingMonitors and FundingMonitorsEncryptedConfig add-ons to
facilitate management of funding monitor processes.

The StartFundingMonitors add-on will automatically start all funding monitors
configured in a JSON formatted file, as defined in the property
nxt.startFundingMonitorsFile. The JSON can be generated by manually starting
the funding monitors as desired, and using the GetFundingMonitor API to
retrieve the list of monitors in JSON format. The secretPhrase parameter needs
to be manually added to the JSON for each funding monitor.

The FundingMonitorsEncryptedConfig add-ons allow storing the JSON configuration
of funding monitors in an encrypted instead of plain text file, and starting
the funding monitors by submitting only the decryption password to the server.
It exports two APIs for this purpose, saveFundingMonitorsEncrypted and
startFundingMonitorsEncrypted.

The SaveEncrypted APIs require the admin passphrase when used on a remote node.
To prevent overwriting arbitrary files, they will only overwrite an existing
file located in the conf/processes directory and with a default for the add-on
filename; otherwise the file must not already exist.

An UI for the above ForgingEncryptedConfig and FundingMonitorsEncryptedConfig
add-ons has been added, accessible under the cogwheel/processes menu.

Accounts under account control are no longer allowed to start FundingMonitors.


Java programming API:

As an alternative to programming against the http API, the same API calls are
now accessible from java programs using the so called APICallers. Those are
available in the nxt.http.callers package, and code samples for how to use them
are provided under src/java/com/jelurida/ardor/client/api, demonstrating tasks
such as local signing, message encryption and decryption, waiting for a new
block, etc. When integrating the Nxt functionality in your java programs,
using APICallers is the recommended approach instead of accessing core Nxt
classes directly.


Light client networking improvements:

Bootstrap of API proxy - try to connect to known peers and if this fails,
connect to trusted nodes to get latest open API peers. The purpose is to
either have a node serving the proxy at start, or to know that the network
is down, and also to fix the problems caused by old initial peers.

Default bootstrap node is defined in nxt.properties:
nxt.proxyBootstrapNodes=nxt.jelurida.com;

The new bootstrapAPIProxy API can be used to refresh the latest open API peers
from the bootstrap node.


Performance and stability improvements and bugfixes.

Windows and Mac installations now use by default an embedded Open JDK 12
installation.

The H2 database now uses the newer MV_STORE format by default. Conversion to
this format however takes effect only when running compact.sh on an existing
database, or re-downloading the blockchain from scratch.

Updated Jetty to version 9.3.27, H2 to 1.4.199.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAl1n1wUACgkQDPnHRy2A
uLlgbQ/6A4CPdNiKSCNv+w1JpHVzv2AVKWl5JdBPojg2AryAWCIz4qx8vI+CsWP9
2FMSOLnSvCFeHFsxTb92qPotItwS2V6zEuBJhY9lpt1jt2W/vD3hGnCMPvkc7IG4
jOMxenVdXPi1wJdWWW7hneuc08IXcFITBvhRg+5nI7vdLzHItIDxK62Prk2PHEfz
h58b94+qnjIprKvUzpXkCXXJUJ5gdK0HVFCXYj0DiNHZFwj1+OpSxtcssEDabfd6
RlLsiMHOcMsYAeyNxZW8oSiiIYS/JUMu571IRHbNjxl05iSxxRZM2nguOggA+sEY
QUh7i7NxBSc8Y8z/4sHnDLoczRpRNJNH5sNf9Da2Ur4Rp6iHb7Uw85vki4/Z3UJp
aMP3t/8fH9894+HOKi7NO+z3ibbtLPXqwJODWQyV7l9eggrm/wqIZ5Z0XnLPSjWK
2TI1JWWxtBsQYd6yIZRq1vnakQVul90ppPpm8tj5AhLZxSoojNwx+bggfSWH89hN
INOy7M5QBcf/iUNoEv4jED8Pbrdsgvta6OrxwuoeRzZiZpz6uF/X93w+vNa5Yrf0
YJQtbwz9sFK1l/Rqr+raNkVeSRTYscuC9FlQxnZCJYEkYbnwW0qX4hhxw0lbm7+q
rWxJoafYCRj9RonRdeLHiIo/VIzZM7004zR/pjWR9GUoQjApubU=
=M+TE
-----END PGP SIGNATURE-----

3
Ardor Software Releases / Ardor v2.2.5
« on: June 16, 2019, 09:23:20 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.5

https://www.jelurida.com/

sha256 checksums:

1282b33b153e6727bf70103c707cf0d1f3f8171f92a4fb673c32b7208171e16a  ardor-client-2.2.5.zip

f9331fc3e2fd2f81e1a3cb03de47dc22310232a467b24a5207593b2901d267a3  ardor-client-2.2.5.sh

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


Change log:

This is a bugfix release, addressing an issue with the Standby Shuffler add-on.
The recipient public keys were incorrectly generated with an \r character
appended to the user-supplied secret phrases, resulting in actual recipient
accounts different from what was displayed in the UI.

For users of the Standby Shuffler add-on who already had their shuffling
recipient account affected by this issue, a simple RecoverFunds API has been
added. Use that API with the secretPhrase of the intended shuffling recipient
account to automatically transfer your shuffled coins to the correct recipient.

Fixed version update hash validation.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAl0GAo8ACgkQDPnHRy2A
uLkkVw//WFZhP1KIVnzA0nA0+yG1Cla3I1hM8YGUr1bKcflW5HQ8q/i2LlkIv9HW
rT/zNYhalEbq4LWJIW+k2Fj76KVvCtzpH0MLsZshsgm7MBWNgdo4/JTY5mOCv4St
7+zXtKAY/77Q7Bj5gohduFrfRzfraPla58J47KyDtrmnXbMmhEzIssA5Sly9E+ze
YbDgfutzFp2/zTcNKIUklIdlYW3GdC3tP6vgJfafEAQ0kiIBPayEFCuci2yhx/7O
/K6NvrFtiyh5BuUMtIIiSnXz4ZCINv0hthN0S2uLwaKZVEANdCUczomErumcuWCZ
Vpx4YSTLwTHD4byoD1tN7d6yi0wQjMThR/Zdq8MmMchqtTMsfErkn4m3BowT/knx
PGJ0jPvV1kJA7iPJhCQW/eqwhdmZTNsX1sXvuyRKgwpmjFnecGRsu1n1HvX+c3SK
jGlljwmAv9n2xzdLRke5JFMUdVnjq1NGcWLlKImqM4Enl5XTZwnulkd8X3jKh+l2
8jcV3SnWU7ctGhwD0U2e3V952nfClXacofn7p8C5Awn1ulUSPHMLbB+SE3eywunJ
l25ag92c3L8PfPshh6f3SjhG5ZhgOcCyVo2sQ5FnSnNuYvSlNqUiKY9hpARRZhFO
rOSIDlwBTGj9fnaA50G78oXq1XsW1Ps16cabAbJJYTiofvu98Kg=
=LDff
-----END PGP SIGNATURE-----

4
Ardor Software Releases / Ardor v2.2.4
« on: June 13, 2019, 11:19:10 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.4

https://www.jelurida.com/

sha256 checksums:

3e4fb5c730a980360807c73bf686ccb4515672d6d11e3492861966580b2689f1  ardor-client-2.2.4.zip

b37dc41e2e7ce927fdf2ee3da1e8ea803c308e1e4ff78f11dd14e413be8faa50  ardor-client-2.2.4.sh

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


Change log:

This release introduces the StandbyShuffler add-on, a new feature intended to
simplify the use of our flagship privacy feature, fully decentralized and
trustless Shuffling.

A StandbyShuffler, as opposed to a regular Shuffler, does not start a new
shuffling immediately, but runs in the background and waits for other users to
start a shuffling which matches the StandbyShuffler parameters - holding (coin,
asset or currency), minimum and maximum amounts, and number of participants.
When such a shuffling is created, the StandbyShuffler joins it automatically. A
StandbyShuffler is configured on start with a number of recipient public keys
to use as recipients in each shuffling it joins, and shuts down once all have
been used.

Running a StandbyShuffler requires a full node, not just a light client.
To enable the StandbyShuffler add-on, add nxt.addons.StandbyShuffling to the
list of enabled add-ons in the nxt.addOns property. This add-on registers three
new APIs:

StartStandbyShuffler - start a StandbyShuffler. The secretPhrase of the
shuffling account must be supplied. The holdingType and holding parameters
define the coin, asset or currency for which to listen for shufflings being
started. The optional minAmount, maxAmount and minParticipants parameters can
be used to limit which shufflings to join. The recipientPublicKeys parameter
holds one or more public keys, used one at a time as a recipient account public
key each time a shuffling is joined. This can be specified either as a multi-
value parameter, or a single text value holding multiple public keys separated
by newlines. The feeRateNQTPerFXT parameter specifies what rate to use when
calculating the child chain fees for each shuffling transaction submitted.
Since the market rate can change between when the StandbyShuffler is started
and an actual shuffling is joined, one should use a high enough rate to make
sure shuffling transactions of the StandbyShuffler account are always bundled.

GetStandbyShufflers - returns a list of all StandbyShufflers running on the
node, optionally filtered using holdingType, holding and account parameters.
If not running locally, a secretPhrase or admin password are required.

StopStandbyShuffler - stops the StandbyShuffler for a specified account and
holding or all StandbyShufflers running on the node if account is not
specified. If not running locally, a secretPhrase or admin password are
required.

An UI for starting, observing, or stopping StandbyShufflers has been added
under Shuffling / My StandbyShufflers.

To automate starting the configured StandbyShufflers when the node is
restarted, a set of StartStandbyShuffling, SaveStandbyShufflingEncrypted, and
StartStandbyShufflingEncrypted add-ons has been provided.

StartStandbyShuffling automatically starts one or more StandbyShufflers as
defined in a file set in the nxt.startStandbyShufflingFile property. The
format of this JSON file is the same as the JSON output of GetStandbyShufflers,
with secretPhrase field added for each StandbyShuffler, thus the simplest way
to generate it is first to setup StandbyShufflers as required and then save
and edit the GetStandbyShufflers response.

Alternatively, to avoid keeping the secretPhrase and recipient public keys in
a plain text file, the SaveStandbyShufflingEncrypted add-on can be used to save
the StandbyShufflers configuration JSON in an encrypted file, and the
StartStandbyShufflingEncrypted add-on to start them by submitting the
decryption password through the API.


Added ChangeNOW as an integrated exchange in the wallet, allowing exchange of
Ignis and Ardor to any coin supported by ChangeNOW.

Permanently disallowed outgoing transactions from the new @ArdorBurnAccount,
see announcement at https://www.jelurida.com/ardor-burn-account

Pause forging if there are not enough connected peers from which to download
the blockchain, as defined in nxt.numberOfForkConfirmations or
nxt.testnetNumberOfForkConfirmations, unless nxt.isOffline=true. This is to
avoid building a fork if the node is temporarily disconnected. To disable this
behavior, set nxt.pauseForgingOnNoConnection=false (default is true).

Do not allow accounts under account control to start a Funding Monitor.

The SaveBundlingEncrypted, SaveForgingEncrypted, SaveFundingMonitorEncrypted
APIs now require admin password when running on a remote node.

Added a list of full transaction hashes with chain ids to the response of the
getUnconfirmedTransactionIds API.

Added a new bundling filter, nxt.addons.TransactionTypeBundler, which bundles
only transactions of the transaction types specified in the filter parameter.
The parameter must be a comma separated list of <type>:<subtype> pairs with
the "type" and "subtype" of the whitelisted transaction types.

Improved propagation of bundler rates between peers and calculation of best
bundler rates. The CalculateFee, GetBundlerRates, and all CreateTransaction
APIs now take both minBundlerBalanceFXT and minBundlerFeeLimitFQT parameters,
with defaults based on the nxt.minBundlerBalanceFXT (default 1000 ARDR) and
nxt.minBundlerFeeLimitFXT (default 10 ARDR) properties.
Bundlers with effective balance lower than minBundlerBalanceFXT, or remaining
fee limit or available ARDR balance lower than minBundlerFeeLimitFQT, are
excluded from the best rates calculation.

Shamir secret sharing passphrases can now be used to sign transaction
vouchers.

Updated Jetty to version 9.4.18. This release fixes a Jetty bug which causes
a server hang after high load, therefore an update is highly recommended.

The Jelurida Public License has been updated to version 1.2, to clarify that
Ardor code is not portable to Nxt clones unless the JPL requirements for Ardor
are also satisfied (article 3.4.2 of the General Conditions), and to require
that airdrops, including the fact that they are done in order to satisfy the
JPL, are announced at least a month before the planned snapshot date (article
2.2 of the Special Conditions).


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAl0CKT4ACgkQDPnHRy2A
uLkxvA/9FVm31aOSntJbTweeYYDqtivycq/DHSRFEOt2tZCTccHOU+PTngv5Yb7v
aJ20WimSmCCiyiqlJsmA8/YzMi9L0oczzI7YJ/c2EHWBzk6kjcMzx3E0aRFXsRl6
Uwo+nl068zh27+r+lInF1tGTuXRWb9hN2iju/66gVEO0CGXoXacgsvTUOJ23jxDE
BXfTeQcL4DOzEmotZjZrDGtiyvRONKMVCFS7oVGJMGQS5zJxLIW16EruL/WF4c7S
hQtZt58aU7ebJ/6oNb6AIr1i4l5tNSZ2Ad+3SNXRDgiozdHWWTFTWS6i6a8+q5eK
NAnBwlmY+QfS7PBAlLatwGF58/KfTBlnH3w3IpvKF1mNm1v2NKp5LMnhzc60gtsH
hPJ9e0kMzuH395UfTR/QZF8nqSfRXaxcH0XOJMX3pyG8pNK+cJgURJCo0xVZx9Mv
ISJoxsaYVJDuK+KnzSVufutHUXdfiuNrQ30LNmq1tG5FR7eYOr3bf2P8v4SWG7QE
YZcQomkGtEO0EQnx/55QVr52830ER4SoKUjHgdHW4KhvtTEvJwqHlfi+vaGSFALP
qrnpUXPlfbAn37hUdZYiGcdPvUOkaqNSwez0hr2o7ZR8ZSaCsIqWooan/7UYrivj
3KnSR/ZwMgbOkM665Hk5H+gZS/G4dVf4d95aIxjNr8XASBuOaz0=
=UJpy
-----END PGP SIGNATURE-----

5
Ardor Software Releases / Ardor v2.2.3
« on: April 23, 2019, 12:36:33 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.3

https://www.jelurida.com/

sha256 checksums:

93ae873e406d405490baf6e26816509282e8c92a505798168a914ede1d2c704e  ardor-client-2.2.3.zip

f414a71a656bdc0e97ff71ad1b65b7bd182d8b80216bc285e4e59f9cf63e0371  ardor-client-2.2.3.sh

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


Change log:

This release adds multiple usability enhancements, optimizations and bug fixes.
For users of 2.2.1 or 2.2.2, upgrade is optional but highly recommended.

New feature: Shamir Secret Sharing

Shamir Secret Sharing support is now enabled for both client and server. It
allows splitting a passphrase into N pieces out of which only K are required to
restore the original secret. This technique is useful to protect the full
passphrase from key loggers on the client workstation and from eavesdropping
during transport to a remote node. Shamir Secret Sharing is also useful for the
creation of fragmented backups, by storing each piece in a different physical
place or with a different trusted party, with at least K of them required to
recover the full passphrase.

Secret share splitting and combining is supported both on the server side using
the node APIs, and client side in the wallet, so that secrets split on one side
can be combined on the other.

Client side

When printing a paper wallet, a new dialog enables setting the total number of
secret pieces to generate from a passphrase, and the number of secrets required
to re-combine a passphrase. These secrets are then printed into separate pages
of the paper wallet.

For all dialogs which accept entry of a passphrase the user can now check the
"Shared Secret" checkbox, then enter or scan the required number of secret
pieces to combine the original passphrase in memory.

Server side

Any API which accepts the "secretPhrase" parameter can now accept instead
multiple "sharedPiece" parameters which the node will combine into the original
passphrase in memory. A node can keep some of the secrets in its configuration
file while accepting other secrets using API parameters.
To configure this setup for account address X, split your passphrase into
several pieces then list some of the pieces in a semicolon separated list as the
value of the property nxt.secretPhrasePieces.X. When using the API, submit the
parameter sharedPieceAccount=X where X is the account address, and also submit
the remaining required pieces using multiple sharedPiece parameters. This
configuration enables to start forging, bundling, etc, on a remote node without
ever transmitting the full account passphrase to it over the internet.

New APIs for Shamir Secret Sharing:

Use the splitSecret API to split a passphrase into pieces.

Use the combineSecret API to combine secret pieces to the original passphrase.


Contracts

Due to enhancements to the underlying API caller infrastructure all lightweight
contracts have to be recompiled and redeployed in order for a contract runner
running this version to be able to execute them correctly.

Any other code using the API callers must also be recompiled.


Installation

The Windows and Mac installers now bundle a copy of OpenJDK 11 and Java FX sdk.
OpenJDK is installed into the jdk folder.
Java FX is installed into the javafx-sdk folder.
The jre folder which included the Java distribution in previous releases is no
longer created by the installation.
Users who created customized scripts relying on the jre folder should adjust
their scripts to the new structure.
For the linux installation package, the code is compiled with OpenJDK 8, and
can still be run under either Java 8, or Java 11 or 12. For Windows and Mac,
the installation package is compiled using Java 11.


UI improvements

When loading a transaction voucher it is now possible to attach an encrypted
message to yourself, and to recalculate the transaction fee. It is now also
possible to not immediately broadcast voucher transaction, for the purpose of
offline signing.

The coin exchange displays the inverse rate in the "Buy" dialog, and as a
tooltip when hoovering with the mouse over any price field.
Expected orders and order cancellations (unconfirmed or phased) are displayed
in the order book with a special icon to their left.
Left pane balances are updated with each new block.
The order of columns was changed so that the "Sum" column displays the coin to
buy, clicking the "Sum" column updates the amount to buy accordingly.
Red warning is displayed when typing an amount to buy which requires larger
balance than the available balance. Total field is limited to 8 decimals.

The dashboard transaction view was improved to reduce appearances of duplicate
transactions when the transaction moves from unconfirmed to confirmed status.

Support login by alias and recipient alias for any alias. If not an account
alias, map the alias to the alias owner account. Since any alias owned by an
account can now be used as an alias to the account, this release deprecates
the so-called "account" aliases, and we will remove support for them in the
next release.

Approximate leasing expiration date is displayed in the Account Leasing tab.

A new Account Properties tab has been added to the account info modal,
displaying all properties set on the account.


Networking and performance improvements.

As a result of our extensive load testing efforts, this release includes
several networking stability improvements and performance optimizations.


New add-ons to simplify automated and secure running of tasks on remote nodes:

A set of custom add-ons to automate forging, bundling, and funding monitors
has been include in this release.

The StartForging add-on reads the passphrases stored in a plain text file, as
defined in the property nxt.startForgingFile, one passphrase per line, and
automatically starts forging with each of these accounts when the server is
started. Since passphrases are stored unencrypted, this add-on should only
be used on well secured servers, or with accounts of insignificant value, or
in test environments.

For a secure way of starting forging with multiple accounts on a remote server,
the SaveForgingEncrypted add-on can be used to store the passphrases of forging
accounts in an encrypted file, and the StartForgingEncrypted add-on to start
forging with them by only submitting to the server the password necessary to
decrypt this file. Note that at runtime, the forging account passphrases will
still be kept in server memory, but when using these add-ons will never need to
be stored on disk, and will not need to be re-submitted to the server each time
forging needs to be started. These add-ons are useful when forging on a fully
trusted node, and having to restart forging remotely without a risk of exposing
the passphrases in transit.

The StartBundling add-on reads a list of Bundlers stored in a JSON formatted
file, as defined in the property nxt.startBundlingFile. The exact JSON can be
initially generated by manually starting the bundlers configured as desired,
including any custom bundling rules, and using the GetBundlers API to retrieve
the list of bundlers in JSON format. The only manual modification required is
to add a "secretPhrase" parameter to the JSON for each bundler, with the
corresponding account secret phrase. On server start, the StartBundling add-on
will automatically start all bundlers as configured.

Similarly to the above forging add-ons, the SaveBundlingEncrypted and
StartBundlingEncrypted add-ons can be used to store the JSON configuration of
bundlers in an encrypted instead of plain text file, and start the bundlers
on submitting the decryption password to the server.

Finally, for automating funding monitors, the StartFundingMonitors add-on will
automatically start all funding monitors configured in a JSON formatted file,
as defined in the property nxt.startFundingMonitorsFile. The JSON can be
generated by manually starting the funding monitors as desired, and using the
GetFundingMonitor API to retrieve the list of monitors in JSON format. Again,
the secretPhrase parameter needs to be manually added to the JSON for each
funding monitor.

The SaveFundingMonitorsEncrypted and StartFundingMonitorsEncrypted add-ons
allow storing the JSON configuration of funding monitors in an encrypted
instead of plain text file, and starting the funding monitors by submitting
only the decryption password to the server.


Other improvements:

The CalculateFee API now also returns the required child chain fee based on
the best bundling rate available, as feeNQT.

The JPLSnapshot add-on has been ported to Ardor. It can be used to generate
a JPL-compliant snapshot of Ignis child chain balances.

Starting a funding monitor or shuffler with feeRateNQTPerFXT=0 is now allowed.


Library updates:

Updated Jetty to version 9.4.17, Bouncy Castle to 1.61, and H2 database to
1.4.199. With the new H2 release, using MVStore mode is the default. However,
conversion of existing databases to MVStore format is not automatic. To
migrate to the new storage format, the easiest way is to use the compact.sh
or compact.bat script, which should take a few minutes, and will also improve
the database performance.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAly+8jAACgkQDPnHRy2A
uLnRiA//TXgWWzbkM6TC48faknX0JT93hfsbJs0DSndHpVz22CFnvDBBgrFONVHN
1pLQt8KIW8lWawGqkhMKWsWydzAYpgWqldzBRhkJd7mqO+JDE3gGUNOVr0bWQ47a
y4yFNI8kONLuNbHalyiszcKUg8Y6FJG2+XcQmJCDjap0YVifxwoL0z0Kh+Tr7JiX
7mYH5eTg19nXMc9e1Pu0HqFc1cA84nVhrgihtyTesMYNEmMDfM40+eakJxFmLYr8
vx+8se4qLUhaJJIOxHSdoTAq/DDcRcq2ri2nHfjJxPCHufe2rZB9BvZ0mBR22lYO
5YTPdSiEn8z1kWauw5yRLKiQKEQ8BjJ8cLpKTJPL/zDik4dCVxLiFTi26m5kBYF4
rvSXOVk3MzLe4gHW2yjyqsSv90FqEG5wgaSzGrN97YTRgUzKFzl4fDsqe9xPY1P2
ZE3KvUVSyftY9reVrj1jFcLEDd/NTC+ioRtgu51j9V2gxSNYp7Vm6WKFtZzmf3WS
klUGwbuAuBvB9lqsVMc1LZvJ3xBoriy8jkSS1FQZs1L6vORiF0iWIlowJ1B5gc0I
QCI//VqIxQGK659Qj/5ZIXn+9xqHn5UHWa1Ruhgpyo6tgDQmE+76Q0JKOlRLr2bX
JEWDc7niabKfcm3wHG/iut3SaYjNJqazfb13WAme19oL9wHKZO0=
=Io2V
-----END PGP SIGNATURE-----

6
Ardor Software Releases / Ardor v2.2.2
« on: January 15, 2019, 01:36:39 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.2

https://www.jelurida.com/

sha256 checksums:

4d5aa5ade0de7c4ae1ff2fc3ff75d5fdbffd6b5dc15a2673ef99db0caab12c54  ardor-client-2.2.2.zip

7be6df1d3b46e8000ae935a39969de385faac0cda1801d0fc9c6c3fad86ba88a  ardor-client-2.2.2.sh

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


Change log:

This is a bug fix and usability enhancements release.

Users still using version 2.2.0e or earlier must upgrade immediately as they are
already on a fork, and their nodes are blacklisted by this release.

Anyone who did not upgrade to 2.2.1 prior to block 543000 must manually delete
and re-download the blockchain from scratch, after upgrading.

Users using version 2.2.1 are not required to upgrade.


Contracts:

Added an includeContract parameter to the getContractReferences API to return
metadata about the actual contract being referenced.

The contract runner now removes the last block when started to make sure
trigger transactions in the last block are processed in case processing stopped
before processing the contracts for this block.

Contract unit tests now use simpler methods for verifying transactions submitted
by a contract.

The contract manager now waits until the transactions it submitted are included
in a new block before exiting.

Contracts with an inner interface and an inner class implementing it are now
supported.

The contract processRequest callback now supports initializing a randomness
source and accessing the last block.

Fail gracefully when a contract submits the messageToEncrypt parameter without a
passphrase. Contract devs should encrypt the message first then submit the
encrypted data.


UI Enhancements:

Contract selection widget and contract parameter specification template were
added to dialogs which specify a recipient field. This enhancement simplifies
the task of configuring a contract trigger transaction.

The Contracts page now provides simple runtime statistics about contract
execution when clicking on any of the invocation types in the Invocation column.

Each chain now has a chain description displayed in the wallet and when
switching between chains.

Login by account using an Ignis alias is now supported by deleting the ARDOR
prefix then typing '@' in front of an existing alias name which is mapped to an
account id.

"Fat Finger" warning for amount and fee is now defined and enforced per chain.
Reasonable default values were defined.
Use the account settings page to adjust these values for the current chain.

Dialogs now support more than one warning per form submit.
For example in case both the amount and the fee are too high, both warnings are
displayed one after the other.

The wallet no longer warns about assets and currencies with more than 6
decimals.

The Changelly menu items was moved from a top level menu to the settings menu to
provide more screen real estate for the mobile app.

Increase and delete shares links are displayed in the "My Assets" page only when
these actions are allowed.

Vouchers with unicode parenthesis are now parsed correctly.

The desktop wallet now displays a file chooser dialog before downloading a cloud
data item or message attachment to the local workstation.

The transaction and block info dialogs now display the raw transaction and block
json in a separate tab.

Coin exchange layout improvements.


Others:

Fixed an initialization issue that could cause some custom add-ons to deadlock
on start.

Fixed false positive unsigned bytes verification error when cancelling
ARDR buy order.

The getPeers and dumpPeers APIs now also allow filtering by version, optionally
including newer versions.

Added a checkpoint at block 545555.

Updated Jetty to version 9.4.14.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlw91oUACgkQDPnHRy2A
uLlaoA/+LAoazQlqUjnDqLQz6weVorZIS6Y7szwVa+g6A4uB4DsAEEZtAzzCAVog
PjcOpoVvtWoMs0XceesdLAuo9Lxs+5wspMPQ1rvmVDcCnWOO6dv8UZgx24CDpZdL
7rTUD6ca8BegKbvTT3OktMNpP3ENT6m4dAa+Zpw+dwMDO0yJOZAI6pCpWWxJZMyR
yqg4545jDNLmlirHBDu5ZmZhuDvSNIl7AyUrVP6OkpViwedtz3wRNhhyLKRl2v7w
XiKxV6eksruFsmdqRmJGH7BScS7eW4yJnO7YPCMhw4WBe4SuWC+6aKE+bK9yUaug
xgzZiegFp7PqtmoRi3+z9BCH6cu/2Y7w+6aUE2jUuCgHXg6BwvZNxhv9JT60i636
w//rq87YD0ya3yL81SToBEdS0wn+ePEopBF+hFWYZ9NEB13I1igK/EGEgjw3ClQJ
C2pZHTSiv14+wR0+ZXeVa3wxkRUcGKjqH2iRbtxMKvK4o7E5hpXRbGZwQE/uyPC2
fqunC3vLWpI7FQR5ejxcJRFTpZpfPOeTpR5mhoalirFBznrM3ZRpUleMrMzsCldL
if0360kZL/jQR5I+i/m697w7dYZsfhQ6WdmnnT3hPBYCKvJiRlC82BWJ7ozGz8sk
kGAhQ6HyCZGPefPaTctPBQlQaimAEWXmcBcjeTQq/WY5VAe6xHU=
=ysld
-----END PGP SIGNATURE-----

7
Ardor Software Releases / Ardor v2.2.1
« on: December 13, 2018, 03:44:44 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.1

https://www.jelurida.com/

sha256 checksums:

4e6a3075141847252724e13a49d3e8110694a49a08fc22dfd986b53a39f3770d  ardor-client-2.2.1.zip

a85546d0e51b58fb9de02f2d3ac0381111c8b739e2798b632825516c61167c2c  ardor-client-2.2.1.sh

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


Change log:

This release adds support for the new Max Crowdfund (formerly Dominium) child
chain, token name MPG, to be activated at block 543000 expected to be reached on
January 10, 2019.

At the same block, the new Lightweight Contracts and Asset Properties features
will also become enabled on mainnet.

Transactions with asset 6066975351926729052 (old CtC) will be disabled and open
orders cancelled.

Revealing a secret using the ApproveTransaction API will now approve all phased
by hash transactions which specified the hash of this secret regardless if they
are listed in the phasedTransaction parameter or not.

A new GetHashedSecretPhasedTransactions API will return a list of phased by hash
transactions with phasingHashedSecret and phasingHashedSecretAlgorithm as
specified.

This is a stable release and a mandatory upgrade for all nodes, with block
543000 (Jan 10) as final deadline.


Lightweight Contracts:

Contract validations now use Java annotations. The following annotations are
available:
@ValidateContractRunnerIsRecipient - checks that the contract runner account is
the recipient of the trigger transaction.
@ValidateContractRunnerIsSender - checks that the contract runner account is the
sender of the transaction.
@ValidateChain - checks that the chain of the trigger transaction is in the
accept array and is not in the reject array.
@ValidateTransactionType - checks that the type of the trigger transaction is
one of the types in the accept array and is not one of the types in the reject
array. A new TransactionTypeEnum class lists all available transaction types and
sub types.

See the HelloWorldForwarder sample contract for usage example of the validations

The contract runner getSupportedContracts API was enhanced to return more meta-
data about the running contracts including the supported invocation types,
contract invocation parameters, and contract validations.
This information can be used by clients to provide better user experience by
analyzing the contract capabilities and helping the user properly trigger the
contract.

Contracts can override the built-in duplicate checks for transactions submitted
by a contract by overriding the isDuplicate() method.
Oracle contracts should implement this method to make sure they do not submit
the same transaction more than once with different data.
See for example the IgnisArdorRates contract.

Added uploadContractRunnerConfiguration API to let contract runner node admin
upload the contract runner config after starting the node.
This way contract runner nodes no longer need to store the contract runner
account passphrase or other sensitive data on the node itself.
Instead, they can upload it after starting the node from the contracts page in
the wallet. The format of the uploaded configuration file is the same as the
existing contracts.json format.

To prevent a contract runner from locking user funds permanently in the contract
runner account in case the contract does not execute, contract transactions can
be submitted with phasing by hashed secret. The contract runner will submit its
own transactions using the same hashed secret and other phasing parameters.
The trigger transaction, and transactions submitted by the contract in response,
are either approved together or rejected together.
If a transaction is not approved when reaching its finish height, its funds are
released back to the sender.

To assist with generating secure secrets to hash, a new secret generator wizard
was added to the wallet approval modals dialog. Generated secrets are not saved
by the client.
A secret can be reproduced by the client in case it was lost, using the account
passphrase used when generating it.

The parameter injection introduced in version 2.2.0e was replaced with a more
robust solution based on an interface. In the new design, invocation, setup and
runner parameters are defined using an inner interface decorated with the
@ContractParametersProvider annotation.
For each contract parameter create a default method which defines its name,
data type and default value, decorated with a contract parameter annotation:
@ContractInvocationParameter - specified by a trigger transaction or voucher.
@ContractSetupParameter - specified by the contract reference.
@ContractRunnerParameter - specified by the contract runner configuration.
To load the contract parameters from inside your contract code use the following
statement:
Params params = context.getParams(Params.class);
Where Params is the inner interface decorated with @ContractParametersProvider
annotation.

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.


UI Enhancements:

A contracts page was added to the wallet to list the information provided by
the getSupportedContracts API. This page is available only when the wallet is
connected to a contract runner node.

Asset properties UI was implemented accessible from the "Asset Properties" link
on the asset exchange page. Users can use it to set, update, and delete asset
properties.

When entering recipient address in the client wallet use the @ prefix to point
to an existing Ignis alias which stores the account id. In previous versions the
alias was loaded from the current chain.

The contacts button to the right of the recipient field now lists all the
remembered accounts in addition to the defined contacts.


Updating to this release from 2.2.0e may cause a one time shutdown on first
start in order to fully apply the database changes.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlwSZ4UACgkQDPnHRy2A
uLlssRAAhFXNsIeGpwgoO0zInyfc+gpf9eWBBvB+S0ww+0Jh69k0zyaxKMPNI/9r
rjAVnCvawi10DnA6V6AVUL58XlWBAH+rGNz3FJi7JxYz7AXNToO1WOAHDI4db/vv
Rr8dfdoMljNMrkUrTHG609qV0O8ZnavThSHcsCbHXyjVUaHInnVqL1+2fxVVOWIQ
/FrzdZiLVvfMHHVkkhZfC0V5BJmlaPzQe7bU5zx+CYIGv4vCQKiJxup2LjowByyl
2p+7sibeYvQxh0hzVaNDYKeznFKiq8ZGZpm5m4WVyPlCyICH8dTs/0ZI7jEI6wAU
vEYSSudCcRmThbhAEPlYwch6hdfPJl18blKcl0yYf4sbGVu1nmrX8E98cP6NBlYU
525NApoJ8KyJjvVCZ0H2ZpGLPbtNGqAWZKFyDxDzIcW0YPmP+T/e869Tjiv5OUz1
JKAGMk9nnYOpaopcZIM2di/40R3zzBTl+cKOe0sbqkZG+Y8IaBbGeF/JP9JZo/Hc
Yd41nPBjGz+WZm2lqERRUc7xbuNJ2KLcdNVIDl4Uo8mkRw9qFhLdM+7alhGecx8Y
i4AGXbNyLvGLB80xx2LOVWIrlN1VAOlSmTJx1Z7BByMrnS1m6alP73WCc2tUjK2d
AsMTnYLIAIKrt7gJkHqsS3TiawGhTH2Y5g+5bVJX1ML9vfwiVuY=
=C1IY
-----END PGP SIGNATURE-----

8
Ardor Software Releases / Ardor v2.2.0e
« on: November 02, 2018, 10:19:42 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.2.0e

https://www.jelurida.com/

sha256 checksums:

6f29f16499366284d6351eff2cb3613b72e306c3bde9eb26df20bfcf4dec6fdd  ardor-client-2.2.0e.zip

f63b69c8482c480ff56e774ab2a95ff4f8a5465e2ca6eeea27aace3006a9d372  ardor-client-2.2.0e.sh

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 nxt.properties 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: https://ardordocs.jelurida.com/Lightweight_Contracts for more details and
examples.

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.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlvcGdgACgkQDPnHRy2A
uLkZthAAuHopHNKNkp1rCNTnqBarBcuhxyTcuxTv0582pT6RO8HksBao/KEElr79
fAKNJUfu17g71tjzOpEVSAHH4WFckyWMEQwOwcNta+8nBVfXPGTzKESZFmBAOBHu
YJiOMZLo6YhEuvwr2Rv2h3iWAucQLCrDL45ckNM8oULYWeEOgF6teP3RKOKA62Vz
m1r+QR1MDTeroJfMnGIaqa4KfHXndCWUk8YGw4KVyUoKJywGfNRtQI6AmasJp2k3
NagFP5iyTf7VnTLiqvMUeNMsp1fUHrRalPegFFcEAqd+7qiuWFe/FdJ5KeoYbjch
QmGa/VVYpRu1BG4rdD7+5SrGuuAu0ksTrm5OQOPUXJR3T1fMYkDUgHgHnMlSCtMz
qPhKa5OjjFHv5qHVHuMhQ25tk7MpDMHB6X5DE62vAswLWUjqDy/My+F9HzNvwg6h
uugQR+dbIptGtJhLI5cBiDPR+htcPGPOhClFz/wQ8qoezBmAk+N3mFX89QofqiSD
GP9JjWrUlWWzmNGWn9Ud45OfTY33CQYQBUnCXoFvIlwGMCl2LGjPTVvP1f0fW8yR
fGw22u5/VT+s43E9O53Mc32m58ow8sb4gWdQRdUEP1GNQOPkBbgw1hI/5cus56Vb
6wY7tV5qjGmjtZ0L1fzn13YH2x4unSy86afyqJ+r3B8T8DCU5+E=
=AmSO
-----END PGP SIGNATURE-----

9
Ardor General Discussion / Ardor Online Hackathon 2018
« on: October 22, 2018, 08:12:25 am »
Jelurida announces the Ardor Online Hackathon - a Lightweight Contracts Coding Competition: https://www.jelurida.com/ardor-hackathon-2018

10
Ardor General Discussion / Ardor Learning Hub
« on: October 22, 2018, 08:10:26 am »
The new Ardor documentation site we have been working on, the Ardor Learning Hub: https://ardordocs.jelurida.com/, is now ready!!!

11
Ardor Software Releases / Ardor v2.1.2
« on: October 07, 2018, 12:34:00 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.1.2

https://www.jelurida.com/

sha256 checksums:

02e5e70d862e89df8fc5b8c49705efdacd30c9df53bfbc01a2007afbbae9a2b6  ardor-client-2.1.2.zip

c8ab74406c7f105872eb4fa833058f52d344ff81fc7648145344ff0129247353  ardor-client-2.1.2.sh

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


Change log:

This is a critical bugfix release. IMMEDIATE update is mandatory for everyone.

Fixed validation of string fields length in transaction attachments.

This is a stable release and should be used for mainnet nodes too, however
lightweight contracts are still available only on testnet.

Changelly exchange integration is now available in the Ardor wallet:

https://nxtwiki.org/wiki/Changelly_Integration

Javadoc is now available for sample contracts and API callers


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlu59Z4ACgkQDPnHRy2A
uLlg6Q/+IkdLQgM5STdANYpeosB6ZLbopCyGKxSs11NOzDiAcUWHP2RyiZ+KOwHE
bLrn+Xw2ngRqG/HYpWPZUbZT3NUjimp6gjrYiJIRYobjz7WTbLrSzqR4kgIN2Our
wyo/SAQr7mCIwHRx0hIQbLu5aP37F+2mGCF1ziAgEmJX1DtIzBdmWK4fSzt6jHmv
IYHV4CrdKwwGwrimjPwZJlOl1jfAE2q4vrsXGpDnD1KkU31ZeWYU8rTsu3LV9tnW
MtttSD5o9cWipySQaZes1hXiMQH0/Lze7ElT08dXfRUVta/o8sQrbY6N4a6j1Ycw
WhBujn8bk0hYpDPEXtU86ChdE+qwaiAPLw71dCEQnOrJwwM0YaRxH/Gl8kJrDjPJ
0KRE97Cfzf2dOc6n4IcY87h98BGwc3+dtaV85LXc2uUkwGp8da5LJp5vGXP6PXCi
iIyelTe+3cyEM+FpcotHplFc3NY/jongx8MGc++KJn/q7dMc3DtuarPhoSmEXMEh
wzUlSsX7ySSrHlZlI5zEFxZrvXPRKRpV6uHErJ3j9duFqwLzskS77NEWA+KKAhmo
YJ9ldQ6eAU5CeDefTkHwpdGoy5axSXJd/eZZBiGHQZUcsuccUhaaRUkw2DYuXSG4
YIi+DmBuE3stvIOvLDIFQH0sqerRrTWEyR4ApPWFEfdmpbZ6t6c=
=FnBJ
-----END PGP SIGNATURE-----

12
Official Nxt Releases / NRS v1.11.15
« on: October 07, 2018, 10:44:15 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.15

https://www.jelurida.com/

sha256 checksums:

933f7a5ed02b6f4af2d50060e60acda746a2261f733b90f2ab969e951c735dfa  nxt-client-1.11.15.zip

b06700f02538350980a9a41186d0a37354d19f53da1077d003b1a385311473f0  nxt-client-1.11.15.sh

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


Change log:

This is a critical bugfix release. IMMEDIATE update is mandatory for everyone.

Fixed validation of string fields length in transaction attachments.

Fixed locale issue affecting Turkish users.

Allow setting the Content-Type header of the API responses to application/json
instead of text/plain using the nxt.apiFixResponseContentType property. Default
is still text/plain to preserve compatibility.

Updated libraries to Jetty 9.3.24, Bouncy Castle 1.60, IzPack installer 5.1.3.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlu52nsACgkQDPnHRy2A
uLlyShAAqb80A2fDWG3oF7nG/Z0l0XVhVVlPEvUIE0Uk4CLrZxZL5mepUibKSpsM
9Bh3tMK6h4MIZKQ+axhG6xfuCqixqg+cpLuvc2MTJWwy5zwnMTSsewcA0jKJYa/O
DHDg2AO4QjrpCQJRo+HU/ZZXUyo++iwPM6UnscevaLxvby8EdQD4uKxBeJ1kOgLF
6num8lTqSF3viCudFdKuDnRB++YrJNWmQjdECufsnmkEBHjmTZM/g9j73fkMlc4n
9574o5NBDCf7e9fXU3BZlcAhtO+6nuVPSuMWQe9TyzTuFpCtkHVqsP1crdISr3Wx
hMdU88k63ksGZXGfRYPMyhl/ylJp+d5ikVrGefNZJPpZzkN4SBBQq7rBiHn+ib9K
E3mbkkxTu50uOniqApJAZ6xf1QffCUR7pDlyOXFxi3/QvWFf0O0qkCr5EN6yAEvy
bLo0WWDJSgEhKmqP+4xjVE6EwWWVk7pK99jAXkGWQ6dKn7kdQfohJWYrxf3VIL4T
DaKU65yegR5JfePk7ii2qlbm8v5L1+oG+cbFnpOv2WLB1FTmdVmZEBc7bdcekdyz
tad0tHgKbstM38bsoHnIBqeVYsWqmPi3x0GK0frYQ+YKauSRwhWsrE2YpTlkTBhZ
EDCCFXy+uIe54f+ejbEcMjFyTn5QbWzNXcrCociZ/azSxNyKKUI=
=HhN+
-----END PGP SIGNATURE-----

13
Ardor Software Releases / Ardor v2.1.1e
« on: September 29, 2018, 08:49:34 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.1.1e

https://www.jelurida.com/

sha256 checksums:

ea0103ab8522b7c5603b3b67cc162ea68009565a1df0f5a96ee55b3b345e2327  ardor-client-2.1.1e.zip

9d4d506023d2c6d89eafcb6f07a24abac08570a94a48e3ce19d1fa343dc2a636  ardor-client-2.1.1e.sh

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


Change log:

This is an experimental release. It is a mandatory upgrade only for testnet
nodes, but can also be run on mainnet.

Contract Manager IntelliJ Plugin is now available to enable contract
deployment and management from inside the IntelliJ Java Development IDE.

The Contract Manager utility now supports contract verification which, given
a hash of existing contract deployed as cloud data and a Java source file,
compiles the source file and verifies that the resulting class file is
identical to the contract class file.

API callers are objects which enable simple integration of Java programs with
the Ardor APIs. Multiple code samples are provided under
./addons/src/java/com/jelurida/ardor/client/api to demonstrate tasks such as
local signing, fee calculation, message encryption and decryption, and waiting
for a new block.

Transaction voucher loading is now supported when logging in using remembered
passphrase.

Fixed coin exchange between parent and child chain.

Fixed decimal calculations for MS currency reserve and claim dialogs.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAluvKbkACgkQDPnHRy2A
uLkdow/8C7PbCryVMqNnSeLzn5fwbCrRCZuEWHO+Yl7EINv8FcJDPi8j2mWRfCuD
6SdftXZjsz9pGiM5dRQHeE4GawCAIAjnGeM7+HQMKv51I/cqF073ybPvUz5m8Q7h
s0qNBnvLGrUWIyK7/Q24D2F6Lu97kLE4iU/e0RSiWJYmFqiMYyiwLe/64G5ds1CJ
fd/b0p6qDK13IXEiTADa22+7734fV6mEeXgmaRpkjkeOsVE+rp2+i8au9inM02Yu
E8Ms141cTlx0qbg17gzaaV54ZXii6rUx5QjY6FQoRcFXGe/Qk6/6l5N8Yeg7IFuh
qAb0tdwKFXGUrMdI+p7IBCKw41YED5bGy0pxlW8tGb5YvS85cbIr0FBZIKlDFiM7
sZSZgsuTd++qn3p/0HQ8x64x8tDDZZNeVJPrmxDlFwxg/NvLCR3UKcPJwRPvR9bc
rOYi6AuWRubPLjTaO/qaja78USDkO5iAcVN96NWYd3PHUW7u+Ko9lk3VDO3reZkv
14+7p5RUonvL0ekwGyGj6ORZAO5dFOujC2eaiPGLGFrqiq5yllWOlHXLMlNwNG5x
28PtXroBdvEgFDJwxSN/cSgv4E7aLkDbNb2x+Nfz9ZorZ8emqM/fseosicK1TXoS
VxQvPTILnoc4BD1o6+6tp4qIjF5XUSfLyzcWCtMSL0NHzi2zCCk=
=FTKC
-----END PGP SIGNATURE-----

14
Ardor Software Releases / Re: Ardor v2.1.0e
« on: August 17, 2018, 10:28:02 am »
More information about Ardor Lightweight Contracts:
https://nxtwiki.org/wiki/Lightweight_Contracts

15
Ardor Software Releases / Ardor v2.1.0e
« on: August 17, 2018, 08:31:44 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.1.0e

https://www.jelurida.com/

sha256 checksums:

4c0724287b53c3fc63b54568c9a1965abc879f7a904267c7845f6fafa5b88b6e  ardor-client-2.1.0e.zip

2177bb23aa452f65129fc7a0baeeb13e6ce534340b23fc0f74eac5db353f5e8b  ardor-client-2.1.0e.sh

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


Change log:

This is an experimental release. It is a mandatory upgrade only for testnet
nodes, but can also be run on mainnet. On testnet, a hardfork to enable the
lightweight contracts feature has been scheduled at height 341500.

First release of lightweight contracts and transaction vouchers.
Refer to the nxt wiki for official documentation.

The bundling of transactions has been significantly enhanced to support more
flexible bundling filters and fee calculations rules. Multiple bundling filter
classes can be defined in the nxt.availableBundlingFilters property.

The following predefined bundling filters are available by default:

nxt.addons.PersonalBundler - bundles only the transactions of the bundler
account.

nxt.addons.AccountPropertyBundler - bundles only transactions sent by accounts
which have the "bundling" property set on them by the bundler account.

nxt.addons.AssetBundler - bundles only transactions involving the specified
asset.

nxt.addons.CurrencyBundler - bundles only transactions involving the specified
MS currency.

nxt.addons.PurchaseBundler - bundles only purchases of digital goods sold by the
specified account.

nxt.addons.QuotaBundler - bundles transactions until reaching a quota per sender
and transaction type.


The startBundler API has been modified to accept an optional "bundlingRulesJSON"
parameter, in which the list of bundling rules can be defined in JSON format.
Alternatively, a single bundling rule can be defined using a "feeCalculatorName"
and one or more "filter" parameters.

A new addBundlingRule API has been added to allow clients without JSON support
to run bundlers with more than one rule, by adding rules to an already started
bundler.

More than one filter is allowed per rule. The rule is executed only if all
filters allow the transaction.

The lists of available bundling filters and fee calculators can be retrieved
using the new getBundlingOptions API.

The Bundlers page has been enhanced to support the new bundling rules and
filters features in the client UI.

Account property with name "nrs_recipient_ui_options", set by the recipient on
itself is now used to configure the modal when sending funds to that account.
This can be used instead of the "#merchant:" account description and allows
control over the message encryption, such as disabling it for exchange accounts.
The value of the nrs_recipient_ui_options property is a JSON object with fields:
- - message_format: same as the format specifier in the #merchant account
description
- - encrypt_message: default value for the encrypt message box
- - encrypt_message_disabled: if true, the encrypt message box is disabled

Don't show permanent message option on ARDR chain since permanent messages are
disabled there. Fixed verification of prunable messages on ARDR.

IGNIS is now the default chain when loading the wallet for the first time.

Support compilation with Java 10 and language level 9.

Updated translation resources and removed old translations.

Added a checkpoint at height 221000.

Renamed the BITSWIFT child chain to BITS.

Updated Jetty to version 9.3.24 and Bouncy Castle to 1.60. Delete the old lib
folder if installing on top.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlt2fzkACgkQDPnHRy2A
uLk2yA/+JHm8CXYHzcoJmPCae9VaYrKbdKj86iTi53D5egxhB3njD6EJCm//pd8e
V0irNi3Vp+NCQJbdgT5UHsROwTAJM/G6CnZhMBPZ7I2jfmPa7shVYQW1gu/+4zLj
igBq9+wOJwvn91cD3f6hkCpg8Gy9o6RCbtEQDcgFKivG8QmCb08UhHC41+vxYlQv
rElyPURZiGA0VKEPNOHmNZsX8ALoDL5nTYPlxtCQuHNJvSJ/hg4rWqr28G+yN6+m
lZvP+Q8HWXNCNfrXrEHv81uuggeT6qyus7WEGY5zhha2e47ej83qVkUz2Fi6cnU7
/KUIpLqIs6Cmgcizm5thnIvZuwOOYThWSZMt1NX1a6+rO0DHDEpRD2tB5DhG6uny
6wexruGi/IpF/E8k9WQtpMeq6f/BCcIpcoCGZOF0o2tJjcnveFbrR4jsOAnzQhUA
NF+orc2JVckPbM2mQVo4xWCJAlOZgfhFKFWvwwYejFhCSMA6GM4EIMTfTI14UAtt
fEWYKtnFJkeqPmqHsoWsLsSsjypXg7dwTHDZ3+ZHtS1bLwb+xDV9ZnF4AgFHF1XC
91eOiHi4Ikma2xxAl+o5zNf4oK8zptQOM1nvWlqIuPZ7/G9tGhEdA1wdUGWmuVsQ
LVyTyNvCFkyAh8CfsYjccqgdm2EcTPodY2jrhol4Kde76DHUQX4=
=mjvC
-----END PGP SIGNATURE-----

18
Official Nxt Releases / NRS v1.11.14
« on: June 05, 2018, 11:03:17 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.14

https://www.jelurida.com/

sha256 checksums:

452f7320ea806c8e7cc6d87b85fff2085320043d0c2f5e80e799802e2b94abed  nxt-client-1.11.14.zip

47796863ef08855df87e58a2cf4094c38946f52231a1678c85c091a2f27b93d5  nxt-client-1.11.14.sh

The exe and dmg packages must have a digital signature by "Stichting NXT".


Change log:

Updated the translation resource files.

Updated default peers, added checkpoint at height 1865000.


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

iQIzBAEBCgAdFiEEvs/qm2srO/+g27NEDPnHRy2AuLkFAlsWZKQACgkQDPnHRy2A
uLk9vg/9FenaH3Usd1sNQ6UtkBPfLkNqKbZ7+tvMmeirxSAGbANlIMUrkUSrZhil
WOAWXRIiL5EGd9JkOhueG4+lzxhG+e7g8kFVBTiRe6YskegyGr4/7ty0x/DBOgVw
AJncXqzv/YOIzPkV6xOzOaM6Kz4jhZgDHQ2JE/y3zH5/i7MuEF8B9AqegpQmoafn
5aikGe2P6XhIzLV5X2mm0KV6uNL2ilqv0uONjr61+nMwM3zcE7snwxd9lLg6/U/m
0vas87zR9p5fgDC2TcOaVKeDyFzaxHO2zznZPGvjXKqUEr0SH6bsFLSCkTN6Qhx7
q093vgkhvQ7j3rbs602bizTTT628WgpXRlQR2eExueIsk8fcf0cwZ2trOoHIJdbT
Qhh/2fMhhoSJMnJmgKe89mYtpP/GPo6avtFpTIw+9nYCupcaygnxxxCWbbNojom8
MOUqjGftlrA+cK7ZoeaznWyZCxLZV7l57bebUjkVQQxr2j9GojUC0BVgUyanuXNu
bTOyV2AH2UBrWRLnLGOEhNaGFkKowUwuzEtuamfYYSZkWQ/3qKP3ZsoBqP8J+rBE
7DmbrQnr5fcBQ+AwKFUz5xy6tAU2ODGJNqvwkZCZ2ZNi9C0IjTmbvrj2Alo+aBAa
q10fhLs2dS797kXeo1I1YWiTcLWgBQ6AAH0L0WXWtbz1ksuNgjY=
=f2Ce
-----END PGP SIGNATURE-----

19
Ardor Software Releases / Ardor v2.0.14
« on: February 14, 2018, 10:38:58 am »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 2.0.14

https://www.jelurida.com/

sha256 checksums:

23ec29b0995970c7ce183dd024acc04b87481c24ca34ba7d5412a30bed437dc1  ardor-client-2.0.14.zip

0ea055afb5f6225babd701fbe0499bcbb7bf5ededb31c17088d64458d1fdf91e  ardor-client-2.0.14.sh

The exe and dmg packages must have a digital signature by "Stichting NXT".


Change log:

Multiple client UI bugfixes and enhancements:

Correct coin order cancellation fee calculations when the exchange coin is ARDR
and correct fee coin label in the buy and cancel modals.

Format amount and fee according to chain decimals in transactions tables.

Fixed server calculated exchange rate to display according to locale numeric
formatting.

Added the buy orders side to the coin exchange, improved layout of the coin
exchange page.

Fixed update of account balances per chain.

Fixed alias offer to any account. Fixed decryption of DGS goods.

Added Ardorgate EULA and privacy policy checkboxes and links.

Improved the "not enough funds" error message.

Fixed sending of transactions when running as light client.

Added UI for blacklisting bundlers.

Do not process or propagate bundler rates when running as light client.

Do not load genesis block json when running as light client, for faster initial
startup.


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

iQIcBAEBCgAGBQJahAqBAAoJEAz5x0ctgLi5SXkQALuYfemfVMwSB0m/NjKYjDHm
v7uJfenI9toGnIZlG33rHxvF4aSBE/LvrP242UiACCkK0eD8oHSQv6xMCbTHXgff
AaTiU9d2aaU1M+2Z1ay4R3n8kW28p3BLJiGkSKgOA2NRGs1624eUBGz7NBPsjrXT
/lvAoZMr9Q9XeCyT0OGeoC41VkIpNp5RKk1xi81FD0dfnKH1J6UxqOgIfJRfOKy6
lbrYPrmZMbuoX9Ia5wjvi1MSjz2fuOMOA7ixjUV/6XrHWcJzrtcrp04nNkRo/JCR
GnVIgmKPUJJ3vOjCzkyVfXX02BL+mFMXHYvUSVRyptf8cmm2OVPa10yZ55KvbFyn
6SUx0c1kyU3hy2tCm5w6ND56LEROpzPqyBqwx4CLfqY/PupugkVpJBYQu5/LK3FT
ToNYGE/5I/kdKd/GKL9E9zNJ7Ke4hF11sn69W4tvzHj4ShsgOi0YzcSNkY6qrp8j
8SsKz2kMx6rrHlGIl0sIJHwGows2r/20VyUqpWbdUiH1waxgKaqP1CT1I6fv04/l
5N60StN9xu7ZOUVtKKXsbl/VysfEQWQX29id34Kv6wFIS8QtVK8Fx9j5Zz/EYQ9x
XNwWnkxkygW+Suzi1+bvu1UtqM9ahK9bF8AGgIIpGmjNT41Q4HEUXP9HstLD3l5d
PZlbVQaofj48hWtEb3J9
=2Cne
-----END PGP SIGNATURE-----

20
Official Nxt Releases / NRS v1.11.13
« on: February 12, 2018, 07:14:04 pm »
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.13

https://www.jelurida.com/

sha256 checksums:

c828d8a4bc011378183c1e5c97a065c103f1773b768859836b77e3169809b7e8  nxt-client-1.11.13.zip

cad848a9fd2ba878a506389cdea134f3152f804fdea67be21bad7a0bda4d1305  nxt-client-1.11.13.sh

The exe and dmg packages must have a digital signature by "Stichting NXT".


Change log:

Desktop wallet performance optimizations to reduce excessive load.

Do not allow login using passphrase to a non-existing account to prevent users
from losing their funds due to a typo. Use the "choose your own passphrase"
link under "create new account" if you really need to login to a non-existing
account using passphrase.

Client UI enhancements and bugfixes.


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

iQIcBAEBCgAGBQJagaLlAAoJEAz5x0ctgLi50ysQAJhJ38Jq7fzeOFS7dsjLlFBJ
PaZmo/Bz9GkmWjMzjualbw66YbcVZ3RuFFGeiikASyMHBNrJlr0D5SLF/9eUA3WS
nCEpCYWpMFSfnaHB2QGooZOoWTEZJXNSFvthSE74li7/KxahEGPuT2aePvVT9nx0
BgHUWhGyZtw3mR+Rrvt/TgHl11hghaz/tRILYXJ+KUjT8S5ue/UtNW0l3Ap83bVF
zTbO9LOd6s+8Q1qJpjcx0z1l1XPSn3UVW5BW6Wtp0d5MLhkjX/Kq6jaYKU1sVRHp
SnT13e9+SWwYk3Zt2vto1l5BwuGYCv2uETBidoF9RsuTOWSKFdo2Zry/pCwHxQ6n
0JGUrC2ggjrUCfVXRfDh5YXe/eL0ApU+2m/BxMcuB1UaLwy4nqoXWegoz1y+VjxQ
BuC1Od0m+C4dsyW8HJbKoQspUS83UWJJge1Hm4BR/f6riXI7NqnIZUsbtoA0srSt
8OsjgNtQyPNlxuRxP+oTLHHCQ6DN/MFuPFGahzqpi2eapl6spzMfwxKOPvjVKkd5
SmO7OEtcJWgFLVhHr6L5OrKHw9D0Ckmn4kyyO04ESqU3ihw7t7TUG3TvYk+pZ742
1I8BvTFIX7DaHf330mre/TUjx6KHVf1NcTRBzNhZKaTBuaI2khSrF/xO2Ur8yqpB
hXHsvp0wLatAhhXaBHFp
=l0Hh
-----END PGP SIGNATURE-----

Pages: [1] 2 3
elective-stereophonic
elective-stereophonic
assembly
assembly