Version 2.2.3 just released.
Now --register has a --wait key (defaults to 5000) and by default waits the specified number of milliseconds for the network consensus.

Uniclient timing sample: https://gist.github.com/sergeych/d7ececcf84d64577a523adfc66ce6744

Version 3.4.14 released.

• --split-off high-level command to perform split-join operation on compatible smart contracts/tokens.
• --revision-of option to use together with --import, when the contract imported from XML/JSON/YAML should become a new revision of the existing contract.
• --add-referenced option to use together with --pack-with, when a referenced contract should being packed together.
• Various fixes to scenarios when the file with the contract could be overwritten without being backed up.

You can always find the latest Uniclient documentation at https://kb.universablockchain.com/uniclient_user_manual/4.

Version 3.4.17 released.

• --split-off command now supports specifying --name to define the desired file name for the new contract file. If multiple --names are specified, they may be used for splitting the chops of the contract; omitted names will be autogenerated.
• --split-off and --register commands return exit code 0 for success and non-zero (actually, the number of errors) for any possible failure (from missing files to Universa failure replies).

If you experience slow Uniclient operations, especially on Linux environments – this may be caused by your Java setup being misconfigured to use a slower entropy pool for cryptography operations.

To solve this, you may need to do the following actions on your system:

1. Find the java.security file of your Java setup. On webupd8-based installations, you can find it in /etc/java-8-oracle/security/java.security. Normally, it is available in $JAVA_HOME/jre/lib/security/java.security.

2. Change the line:

securerandom.source=file:/dev/random

to read:

securerandom.source=file:/dev/urandom

3. Save your change and exit the text editor.

This information is available in the Uniclient user manual as well.

Version 3.4.18 released.

• --name option renamed to --output for clarity;
• the exit codes are properly generated for all the options depending on whether the execution was successful or not;
• the output files extensions are no longer added, removed or changed for the generated files, unless input and output formats differ and no output name was explicitly specified;
• --resync command removed (as it has been possible only with the node permissions).

Version 3.4.19 released.

• better Windows support;
• on macOS, it should not required JDK anymore (JRE should be sufficient).

Version 3.5.1 released.

• --node option (fixed and documented) to choose the specific node you want to connect to;
• --no-cache option fixed and documented;
• --probe-file command added, when you want to get the network state for a contract you already have in the file form.
• --resync command readded; for low-level system administration only.

Version 3.6.1 released.

• --sign command, to just add a signature to the contract (e.g. when multiple signatures are required for registration to succeed).

Version 3.6.3 released (05.07.2018)

• --import and --export now treat the addresses (KeyAddress fields) as Base58 (and even import from Safe58), so the exported contract should have this field matching what you normally see in the GUI.
• New features: --create-parcel and --register-parcel, to prepare the whole paying parcel on an offline computer, and then to be able to transport it to online computer which doesn’t need to keep any private keys. Such parcels are normally stored in the files with .uniparcel extension.
• --unpack fixed to don’t unnecessarily check the unpacked contract for validity.

Version 3.6.5 released (07.07.2018)

Significant network-level optimization of resource consumption: signing the main contract of the transaction now assumes signing every sibling. This decreases the amount of quanta/U uses by transactions where many siblings should be signed similarly (e.g., token splits to multiple recipients).

Using a SimpleRole with multiple keys instead of one (never explicitly specified before but still possible) now uses ALLOF logic rather than ANYOF.

Also:

• --unpack command now supports parcels.
• --register command saves the parcel that has been used for registration.

Version 3.7.2 released (10.07.2018)

Major new feature: UUTN wallets. Now you can store some (default) private key and some (default) U smart contracts in a single convenient place, so the private key is used by default for signing, and the U smart contract is used for network fees. Moreover, you can even store the UTN smart contract there, and it will auto-top-up the U balance when it gets low.

• --wallet option to choose a non-default wallet.
• --put-into-wallet command to put some private key, U contract or UTN contract into the wallet.
• --u-rate command to get the current U price in UTNs (or actually, how many Us are given for a single UTN).
• --u-for-utn command to reserve the required amount of U for UTN; pass --amount option to specify how many U you want to reserve.

Version 3.7.6 released (15.08.2018)

• When using the --revision-of option for --import command, you don’t need to specify the parent, origin or revision in the imported template; Uniclient will generate them for you.
• The processed references are exported as a string.

Version 3.8.1 released (11.10.2018)

• Contract serialization fixes to increase forward compatibility. Warning: contracts generated with 3.8.1+ version may be unreadable with clients/API <3.8.1! Earlier contracts will stay compatible with 3.8.1+.

Version 3.8.3 released (30.10.2018)

• The functionality of --create and --set commands was enhanced.
• New --start-http-server, --exec-js and --create-contract-with-js commands to provide the Client-side JavaScript functionality.

Version 3.8.4 released (01.11.2018)

• --password option to support the encrypted keys. When required, the passwords may be requested interactively.

Version 3.9.2 released (26.03.2019)

• Hotfix of the the network connection code for more redundant network bootstrap.

Version 3.9.6 released (02.04.2019)

• The network topology is now taken from the redistributable (on the first run), and maintained between sessions (in ~/.universa/topology/mainnet.json).
• The host to connect is taken on random from the network topology (either initial or last known).

Version 3.9.9 released (21.04.2019)

• Network connection improvements: DNS system independency; consensus-based (handles the case if several nodes are maliciously substituted).