Universa Web Client Release Notes
- v3.5.x releases
- v3.4.x releases
- v3.3.x releases
- v3.2.x releases
- v3.1.x releases
- v3.0.x releases
- v2.14.x releases
- v2.13.14 (25.10.2018)
- v2.13.13 (16.10.2018)
- v2.13.12 (13.10.2018)
- v2.13.11 (06.10.2018)
- v2.13.10 (06.10.2018)
- v2.13.9 (20.08.2018)
- v2.13.8 (20.08.2018)
- v2.13.7 (14.08.2018)
- v2.13.6 (02.08.2018)
- v2.13.5 (27.07.2018)
- v2.13.4 (26.07.2018)
- v2.13.3 (24.07.2018)
- v2.13.2 (20.07.2018)
- v2.13.1 (12.07.2018)
- v2.13.0 (11.07.2018)
- v2.12.x releases
- v2.11.x releases
- v2.10.x releases
- v2.9.x releases
- v2.8.x releases
- v2.7.x releases
- v2.6.x releases
- v2.5.x releases
- v2.4.x releases
- v2.3.x releases
- v2.2.x releases
- v2.1.x releases
- v2.0.x releases
- v1.5.x releases
- v1.4.x releases
- v1.3.x releases
- v1.2.x releases
- v1.1.x releases
- v1.0.x releases
- v3.x releases
Universa Web Client Release Notes
3.x beta client is available at beta.universa.io.
2.x client is available at access.universa.io/contracts.
For more information on Web Client, see Web Client.
During the beta testing of 3.x client, it coexists with 2.x simultaneously.
- Fixed the problem when a contract could be considered “undefined” or not saved in the crypto cloud in some rare cases when performing token swap operation while having the connectivity issues.
- UTN-U reserve procedure separated for more clarity.
- Fixed the problem with UTN-U orders which could be wrongly considered canceled in some cases.
- New feature: ability to download the local-storage data for support requests.
- Fixed the occasional issues for some early-made tokens (like SGT).
- Major speedup (and general revamp) for the contract status checks procedure.
- Fixes for transaction pack cloud saving during the split-join operation.
- Fixed the problem during the public key import.
- Fixed a rare split-join bug, causing an occasional situation when split-join needs to be run twice or more to be completed successfully.
- Performance improvements on the Wallets page.
- Added the ability to reload UTN-U order for the cases when UTN tokens seem missing.
Features and improvements:
- The network requests are now balanced over the nodes.
- As UTNPs can now be swapped to UTNs, reserving U for UTNP tokens directly is now disabled.
- Added the common error handler.
- Wallet transactions list is now enhanced and contains the from/to data.
- The whole wallet transactions list and swap orders list can now be downloaded.
- It is now possible to “restore” the order, recreating the order-contract.
- The list of keys now contains the marker for the primary (associated with the current Crypto Cloud connection) private key.
- For declined contracts, extra information is displayed on mouse hover.
- For declined contracts, the network registration is disabled.
- On contract uploading, a success message is now displayed.
- After deleting a contract file, it is automatically downloaded (to prevent occasional loss of data).
- Only resolved order can now be archived.
- Minor mistype fixes.
- The primary private key (used for the Crypto Cloud connection) cannot be deleted anymore.
- Fixes for declined token contracts.
- Safely handle the “canceled” state during the attempt of U reservation for UTN (adding the UTN contracts to the storage).
- Added the U balance validation before attempting to register contracts in the network.
- The list of latest orders/transactions (inside the user profile section) has been updated to contain the order code, and the capability to download the whole order transaction pack.
Optimizations and internal improvements:
- Updated the split-join algorithm to split tokens in batches.
- Refactored and cleaned up the procedure of tokens sending over the chat.
- The notifications enhanced with the capabilities of data updating and being closed by API only.
- In the token send approval processing, the message loop pausing is fixed.
- Added the extra protection to prevent any attempts of contract double usage (which will still fail anyway).
- In the U-for-UTN reservation procedure, fixed the validation of maximum available U.
- Fixed the transaction pack registration cost calculation.
- Selector UI fixes and validation.
- Fixed the validation of tokens amount to be sent (to be no more than the wallet balance).
- Fixed the constantly checking of the declined contracts.
- Fixed the “contract not exists” error.
- The web client now regularly rechecks whether it has been updated, and suggests reloading when a new version is available.
- In the UTN-UTNP swap and U-for-UTN reservation procedure, added the confirmation dialog.
- Added the orders archiving feature.
- In the profile, the list of transactions (swap orders) is now sorted.
- Added the new type of notifications to indicate the loading process.
- Added the token processing notification on splitjoin operation.
- Added the checks/validations whether creating or sending of the tokens should be allowed.
- The token sending process now allows a textual description to be added.
- For the token receiving through the chat, the wallet link is now displayed.
- Clicking the sidebar contract now scrolls to the according chat message and highlights it.
- During the network registration process, the preloader is now displayed.
- Prevent page reloading on important operations (such as, the network registration).
- During the authorization, the cloud syncing is now explicitly indicated.
- Fix for the public key downloading format.
- More convenient and usable name for the key files when downloading them.
- Added the explicit method for proper public key unpacking.
- Fixed the invalid scenario with the contract draft being considered modified by the client.
- The transaction pack is being automatically downloaded when deleting the contract+order pair for swap orders.
- UI fixes in mobile version.
- Hotfix for U contract structure reader when reading U contracts with obsolete structure.
- Fixed the contracts duplicating in some obscure scenarios.
- Safer contract registration process.
- Hotfix for the error with the UTN-U reserving dialog.
- Reserving U for UTNs is now enabled, with proper UI.
- Many fixes:
- Fix for the duplicated order contracts problem.
- Long key names UI fix.
- Fix UTN-U order cloud import name.
- UI/UX improvements:
- Dedicated icon for UTN token contracts.
- Added the ability to download the order transaction pack from the list.
- In the UI of (swap) orders, it is now possible to the order contract together with the associated order.
- Added the notification of successful contract remove.
- Don’t hide the revoked U contracts from the list.
- Sorting the wallet transactions and contracts.
- Improvements for internal engine:
- Added the cache for getAmount and getDefinition.
- Keep orders on associated contract deletion
- Prevent the swap order creation if such one exists already.
- Added Sentry error logging.
- The failed swap orders are now rechecked after the client bootup.
- It is now displayed whenever the swap order status is being rechecked.
- In the list of contracts, and on the Wallets page, the key name is now displayed for the key used to sign the contract.
- Fixed the bug with missing short name for some token contracts.
- In the Wallets for, all the wallets for smart contracts in all state (not only Approved one) are now displayed.
- In the list of transactions for this, you can now download the contract.
- Proper Crypto Cloud naming in the codebase.
- Fixed the “Key exists” issue when signing in using the private key.
- UI hints when U or UTN amounts are insufficient to execute UTN-UTNP swap.
- UI improvements on uploading the existing contracts or keys from file.
- UI fix in uploading the file to have allow selecting the previously selected file.
- During the contract deletion, the cache object is being reset.
- After the cloud save on adding the contract or keypair, the object is now updated.
- Updated UTN-UTNP order status checker.
- Display the error on incorrect key file upload.
- Web workers enabled for more reactive interface during resource-heavy operations (such as: private key generation, chat messages loading, etc).
- Separating the Crypto Cloud module in the APIs.
- Fixed the bug with importing the web2.x-generated contracts.
- “Reserve U” form cleanups (including actualizing the exchanges list).
- Crypto Cloud access is now batched, to prevent too large/heavy downloads getting stuck for some users.
- In the key list interface, the user can now selectively download either the public key or the private key.
- UTN↔︎UTNP swap enabled for public testing.
- Minor fixes for capsule serialization/deserialization.
- Critical hotfix of data caching.
- The resource-consuming operations in the API are now cached.
- Key generation form fixes.
- The client version is now explicitly displayed. Wallet-grouping contract interface improved.
- First public release of 3.x series, rewritten from scratch to provide more responsive and reactive interface.
- Fixed the tokens joining when the tokens were owned by different private keys.
- Fixed the key address calculation in some scenarios when the CRC32 part had the leading zeroes.
- Minor change for the U reserving dialog texts.
- Updated the capsule detection logic for the capsule to show in local contract explorer.
- Fixed the RoleList address list determination helper.
- Fixed the key packing procedure during adding a new contract.
- Fixed sending the heavy notary contracts over the chat.
- In the key list, there is now an explicit marker for the primary account key.
- In the mobile interface of the key list, added the key download button to the keys.
- Hotfix for UTN calculation when reserving the minimal U pack.
- Fixed the U contract filtering.
- Balance fixes.
- Actualized the list of UTNP exchanges.
- Fixed the rare bug of float serialization to octet array.
- UTNP-related text corrections.
- Fixed the issue with account loading (forward compatibility) in case if the contracts from the future version of web client are found.
- Fixed the issue with sending the contracts to the long addresses.
- The draft UTN contracts are not considered or used anymore for automatic U reservations;
- DECLINED-state contracts can now be downloaded as single-contract-only.
- U/UTN reservation rate display fixed at “Reserve more” page.
- Backward compatibility issue fixed for notary contracts;
- The contract explorer now displays the nesting level in data sections properly.
- Key selection widget displaying fixed.
- Fixed the page jumps when removing the contracts or rechecking the states.
- Modal confirmations added for removing the keys and contracts.
- Contract states can now be refreshed with the “Refresh” button.
- U reservation text corrected.
- When transferring a contract using the short/long address, a suggestion is displayed to download the contract and pass it to the receiver using any non-CryptoCloud way, when the chat contact cannot be determined from the address.
- Fixed the contact detection (and contract sending over the chat) when attempting to transfer a contract using the short/long address.
- Fixed the negative balance displayed when U package is over.
- Fixed the “U reservation for UTN” order occasional duplication and ordering.
- Fixed the occasional U contract duplication.
- The keys of other parties are not implicitly added to the key list automatically anymore.
- Fixes for key loading/merging from the cloud.
- Fixes for owner address display inside explorer.
- U auto-reserve is disabled by default.
- UTN tokens can now be used to reserve U.
- U reserve can now be auto-topped-up if you have sufficient amount of UTN tokens.
For more details, see Web Client: U Balance KB page.
- Fixed the issue with logging out.
- Less debugging info.
- Fixed the UI problems wih key selection in token receiving dialog, that could occur on some browsers.
- Fixed the issues when the local time significantly differs from the network time.
Fixed the Safari-specific problems on tokens receiving.
- When the user is uploading the
.unikeyfile and does not provide the key name, it is taken from the file name.
- The recovery procedure is added at the “Universa is loading” splash screen in case if it is stuck loading.
- In the contract information, the origin ID is now properly displayed for origin contracts.
- Removed the temporary warning about the Universa Pack purchase suspension.
- The repeated displaying of the same contracts that could occur when the contract are requested multiple times, is now deduplicated.
The overall contract information (available when you click on the specific contract header) now displays who is the owner of the contract. For all the contracts controlled by any of the keys available to you, it should be displayed as “OWNER (You)”.
Added the temporary warning about the Universa Pack purchase suspension during the UTN retrieval.
- A complete Universa pack purchase can be reclaimed just by its order ID.
- U balance calculation fixes.
- Text cleanups.
- Text tweaks for the form of token claim;
- No “Decline” button if cancel_url is undefined (as in the UTN case);
- Token claim form displaying logic is improved to prevent its possible disappearing.
Cancel order button is now optional.
Fixed the heading when the order status switches to “ready”.
Text and styling fixes.
When a contract from external issuer is received, the transaction pack (containing the contract) is being automatically downloaded.
Supports the integration with external token/contract issuers.
Now when you download the contract from the Web Client, you receive a transaction pack (
.unicon file) where the contract you’ve selected is set as the primary one (assuming the contract is in APPROVED state). The transaction will still contain all the other contracts (so the whole pack is valid).
The cancelled U purchase orders are double-checked on the client startup, to give out the purchases which were wrongly cancelled.
Fixes for token conversion orders display.
All contracts can now be edited in the full contract editor. Do it at your peril!
Fix for the full contract editor: no more force-scrolling when the contract is refreshed.
Fix for a sporadic bug with mintable token sending out. Favicon added.
Hotfix for mintable token validation.
Mintable token contract template added, with such extra features like the interface to issue more tokens for a mintable token. For mintable contracts, its unique per-token information (to distinguish the token from other similarly-named ones) is in its “Issued by” field; so this field is displayed in the wallets for these tokens, instead of “Origin ID” field (as for non-mintable tokens). Various GUI fixes and textual tweaks.
Maintenance completed, “Maintenance and heavy load” warning removed.
Fix for the primary sibling detection for the token split procedure. “Maintenance and heavy load” warning added.
The default api_level for the contract operations is now 3. More fixes for hypertoken functionality description and wording.
Some fixes for hypertoken functionality description and wording. Fix for the signature information displaying.
Contract details displaying added:
- A contract can be displayed externally, on the universaexplorer.com site.
- Also, it can be displayed locally, when the user clicks its title.
Many visual and formatting fixes.
Logging out of client/chat now cleans up all the data.
- Fix for new roles addition in the full contract editor;
- Fix for API calls of hypertoken purchase functionality.
Contract title format corrected.
Hotfix for sending the updated profile to every chat contact (when you change your profile details).
Added the feature of sending the contract in the chat, altering the contract owner in process.
The hypertoken purchase form enabled back, after some token rewording.
Hotfix for new contact add to the chat.
As a preparation for hypertoken renaming/rewording, the hypertoken purchase form temporarily switched off.
Hotfix for uBTC hypertoken purchase.
Hotfix for hypertoken purchase form.
Hotfix for the aggregation of tokens into the wallets.
Hypertoken purchase (for BTC and ETH at the moment) is available for a public beta test; other features are approaching.
The split-join contracts (tokens and alike) now display not just the currency symbol/name, but also some unique binary identifier. This prevents confusing between multiple currencies (probably, even issued by different issuers) which are named similarly. For non-mintable contracts/tokens, the hashId of the origin contract is displayed; for mintable, the tuple of issuer address and the short name (which are normally used to split/join such mintable contracts).
Contracts are now being imported and exported using the Transaction Pack binary structure (previously they were serialized as Capsules). The Capsule import is still supported, too.
v2.6.0, codename “Mainnet” (12.04.2018)
Mainnet has been launched and announced.
Signature internals tweaked.
Some U-related interface cleanups.
On the “U” purchase dialog, it is displayed now if the promo code is invalid.
In the “U” purchase dialog, the return/refund address field is now optional in case if the promo code is used.
Internal message structure updates for transaction serialization.
Besides the public key, the user can be identified by the address (or multiple addresses). The addresses are available in the key list; also, the interface of the contract templates is updated to support the addresses as well.
create_at handling in some obscure scenarios.
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.
Hotfix for the slow contract update from the Crypto Cloud in case of laggy networks.
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).
Temporarily disabled the browser notifications which could cause the nasty notification loop.
Various hotfixes during Access Package purchase.
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).
Cleaning up terminology and explanations of fee structure.
The default product (Access Package) to purchase is now preselected. Minor text corrections.
Hotfix for notary contract file download.
v2.1.0, codename “LaunchSequence” (05.03.2018)
Major step towards the fully functioning MainNet: you can now purchase the transactions for the Universa MainNet.
This involves two major features:
- 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.
- 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.
Hotfix for account form validation.
Hotfixes for account page presentation.
Hotfix for old (deprecated) contract format decoding.
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.
Added the warning message about the upcoming Testnet data wipe during “ThreeTimesBetter” release.
Hotfix for “Send” button availability in the wallet interface for non-logged-in users.
Hotfix for visual glitch in accepting the contact requests.
v1.4.0, codename “Exchange” (16.01.2018)
- 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.
Hotfix for HTML escaping in chat messages.
Hotfix for the chat being stuck on loading.
- 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)
- 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.
Hotfix for issue with wallets currency merging displaying.
Hotfix for documentation accessibility.
v1.2.0, codename “Notary” (26.11.2017)
- 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.
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)
- 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” (09.11.2017)
- 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” (07.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.
- 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).