Universa Web Client (test) Release Notes

v2.3.2 (8.03.2018)

Hotfixes for transaction type detection when the transactions are sent out from contract list, for repeated token sending out, and for token sends through the chat.

v2.3.1 (7.03.2018)

Hotfix for the slow contract update from the Crypto Cloud in case of laggy networks.

v2.3.0 (7.03.2018)

Now, during the transaction registration, you can choose whether you want to register it in MainNet or in TestNet. The balance of your MainNet or TestNet transactions will be decremented accordingly (depending on the transaction complexity and therefore cost).

v2.2.2 (6.03.2018)

Temporarily disabled the browser notifications which could cause the nasty notification loop.

v2.2.1 (6.03.2018)

Various hotfixes during Access Package purchase.

v2.2.0 (6.03.2018)

Access Package purchase page improvements:

  • The QR code is displayed for the payment address;
  • Return address validation and checksum calculation;
  • The list of products is refreshed more aggressively (to support price and availability changes).

v2.1.3 (5.03.2018)

Cleaning up terminology and explanations of fee structure.

v2.1.2 (5.03.2018)

The default product (Access Package) to purchase is now preselected. Minor text corrections.

v2.1.1 (5.03.2018)

Hotfix for notary contract file download.

v2.1.0, codename “LaunchSequence” (5.03.2018)

Major step towards the fully functioning MainNet: you can now purchase the transactions for the Universa MainNet.

This involves two major features:

  1. A store page is launched where you can purchase the Access Packages, and pay for them in UTNP tokens (at the moment). Each Access Package include Universa (and Crypto Cloud) access for 1 year, a (generous) amount of test transactions, and some amount of regular transactions.
  2. The purchased transactions above are consumed by Universa during its operation (contract registrations). For debugging/integration purposes, you may use test transactions, which are way cheaper (though may have storage/duration limitations and should not be relied upon for any important operations). The fee for these transactions is now displayed in the user interface.

v2.0.4 (01.03.2018)

Hotfix for account form validation.

v2.0.3 (28.02.2018)

Hotfixes for account page presentation.

v2.0.2 (28.02.2018)

Hotfix for old (deprecated) contract format decoding.

v2.0.1 (27.02.2018)

Hotfix for SHA2 and SHA3 cryptography algorithms (JS implementation) stability improvements.

v2.0.0, codename “ThreeTimesBetter” (27.02.2018)

Major backwards-incompatible change (one that required the Testnet data wipe on 27.02.2018). Before this, the hashId (that is used to uniquely identify all the contracts) was created as a (80 bytes long) result of SHA-512 (SHA-2 family algorithm) calculation. Now it is a (96 bytes long) record and is calculated as a concatenation of results from three different families of hash functions (requiring three different collision attacks to succeed simultaneously). The components of the new hashId are:

  • SHA-512/256, the strongest to the length extension attack variant of SHA-2 family algorithms; part of FIPS PUB 180-2 US Federal standard since August 2002;
  • SHA3-256, an algorithm of totally different algorithm family, SHA-3; part of FIPS PUB 202 US Federal standard since August 2015;
  • “Streebog”, a hash function defined by GOST R 34.11-2012 (ГОСТ Р 34.11-2012); Russian standard since January 2013; also covered by RFC 6986.

v1.5.0 (26.02.2018)

Added the warning message about the upcoming Testnet data wipe during “ThreeTimesBetter” release.

v1.4.2 (22.01.2018)

Hotfix for “Send” button availability in the wallet interface for non-logged-in users.

v1.4.1 (17.01.2018)

Hotfix for visual glitch in accepting the contact requests.

v1.4.0, codename “Exchange” (16.01.2018)

New features:

  • Exchanging the contracts is now available through the peer-to-peer chat, using the interactive dialog. You can add either some amount of the splittable contracts (tokens) to the exchange transaction; or you can add any non-splittable contracts to give them away.

v1.3.3 (9.01.2018)

Hotfix for HTML escaping in chat messages.

v1.3.2 (28.12.2017)

Hotfix for the chat being stuck on loading.

v1.3.1 (15.12.2017)


  • Fixed the issue with sending the tokens when balance is zero.
  • Visual improvement of sidebar when multiple chats are available.
  • The contract templates are now scrolled horizontally.

v1.3.0, codename “Notifier” (12.12.2017)

New features:

  • When any new message is received, an audial notification is provided and a browser notification is displayed. The browser notifications are combined and aggregated, to prevent flooding the screen with them.

v1.2.2 (30.11.2017)

Hotfix for issue with wallets currency merging displaying.

v1.2.1 (26.11.2017)

Hotfix for documentation accessibility.

v1.2.0, codename “Notary” (26.11.2017)

New features:

  • New “Notary contract” contract template, making it possible to register the binary contents of some files, and to validate them later.
  • Audial notifications to any changes of contract state according to the Universa network.

Some problems fixed, related to the future-proof of contract storage in the crypto cloud.

Various bugfixes.

v1.1.1 (16.11.2017)

Some bugs were fixed, related to the compatibility of contract operations between uniclient CLI and Web Client.

v1.1.0, codename “Optimal Primes” (13.11.2017)

New features:

  • Created and edited contracts can now be stored in the crypto cloud (available only under your private key).
  • The result of various network operations, especially contract registrations/validations/errors, is now displayed through the in-site notifications.

Some issues and bugs (such as problems with sending the tokens/tickets which would require to join several contracts) fixed.

v1.0.1, codename “911 Emergency” (9.11.2017)

New features:

  • Uploading the contract from the file will verify it in Universa network automatically.
  • Clicking the contract status causes a refresh/recheck in Universa network.
  • If there is something new in wallets, they get a red mark/badge.
  • When opening a chat window, the entry field is focused by default.
  • If a contract is corrupt somehow, the previous “last approved” state can still be recovered and reverted to.

Some issues and bugs (such as during the attempts to send tokens) fixed.

v1.0.0, codename “Seven-Eleven” (7.11.2017)

First public beta release of Universa Testnet and Universa Web Client.

Testnet is now publicly open for everyone to test the contract functionality of Universa. You can use Universa Web Client to create, edit and store contracts, to communicate with other Universa users using Messenger and send the contracts, all that with maximum security.

Release highlights:

  • Create a new private key pair to login or signatures (and make sure to back it up locally for future reuse).
  • Log in, edit your account (for Messenger), the account options are stored in the crypto cloud.
  • Alternatively, create a password to be used for “Nick+Password” login, similarly to regular Messengers.
  • Create the Universa contracts, using either the predefined templates (for tokens, and for shares / votes / tickets), or using the full-featured editor.
  • In about 30 seconds of editing and writing 0 lines of programming code, you can launch your own token or cryptocurrency. 1 cent is 0.01 of a dollar; your cryptocurrency may contain units as precise as 0.000000001 of your currency).
  • You may also create the contracts that cannot be split lower that 1 whole unit (good for company shares, election votes or gig tickets).
  • Browse the Wallets, which contain all the joinable/splittable contracts in a more convenient form.
  • Find your friends by the nick they’ve made public, and start chatting with them in the Messenger.
  • “Pay out” or give out a part of the joinable/splittable contracts (like tokens or tickets), transferring them to the Messenger.
  • Download and upload the contract files locally, for backup and future safety (please note: unless they have been transferred over the Messenger, the contracts are not stored in the crypto cloud at the moment! If you don’t want to lose them, do download them locally).