Published in


Ambrosus: The launch of the 2nd Scalability solution — sidechains, Ambrosus Bridge updates, Front-End Team progress, Vlad Trifa (Chief Product Officer, Ambrosus) on EDCON 2019

Biweekly update 8th May — 22nd May

Over the period of the two weeks, Ambrosus wasn’t particularly active on the social side, however, the development progress seems to be essential. The team published a document with a complete overview for the notion of sidechains: A sidechannel (or a sidechain) is a separate blockchain network that runs in parallel with the main network. It can be mostly a private network, however, the sidechannel must be tied to the main network with some form of interoperability between them. Moreover, a new progress report appeared. It contains information about recent breakthroughs, horizon development and events planned: firstly, a number of very important fixes and enhancements have been made to the different masternodes within the Ambrosus Ecosystem; Secondly, The Ambrosus Front-End Team presented a fine-tuned and concise introduction to — the Ambrosus ‘Asset’ and ‘Event’ search/management interface; Thirdly, Ambrosus Bridge timestamps have been added to logs, and all issues discovered in the end-to-end testing (e2e) have been checked — and that’s not all! Social networks make us happy with the increasing number of subscribers, as well as developers with their frequent commits. The sky’s limit for Ambrosus, stay tuned!


GitHub metrics
Developer activity (from
  • Ambrosus launches the 2nd Scalability solution, in addition to Bundling — sidechains! Create your own tokens and NFT on top of $AMB-NET. This is the first step for Ambrosus to become the BoB — Blockchain of Blockchains! The paper they published gives a complete overview for the notion of sidechains, as well as what the PoC specifically entails: A sidechain is a separate blockchain network running in parallel to the main blockchain network. The Ambrosus PoC explains how through the Hermes Dashboard, enterprises and entrepreneurs alike have the possibility of creating tokens on the Ambrosus network for loyalty programs, custom assets, and much more.

A sidechannel (or a sidechain) is a separate blockchain network that runs in parallel with the main network. It can be mostly a private network, however, the sidechannel must be tied to the main network with some form of interoperability between them. The side network can be configured differently to the main network or it may be a different network altogether. This allows for greater flexibility when it comes to transaction fees. Users in the side network can pay fees in that network’s native currency. So the proposal is to create assets on the main network and to have the ability to convert them into the native sidechannel currency where transactions can be performed while paying fees using, essentially, the same custom asset. After performing all the necessary transactions in the side-channel, users can convert their assets back into mainnet assets.

For the Ambrosus Ecosystem, the development of a sidechain architecture is crucial for two reasons. First, with the help of sidechains, unique forms of customer engagement such as loyalty programs, tokenised assets, and product-specific coupons can be managed on the Ambrosus Network at scale. This opportunity vastly expands the types of solutions that can be built within the Ambrosus Ecosystem by Ambrosus Solutions Architects as well as Ambrosus blockchain entrepreneurs. Second, sidechains provide an effective means of managing high-speed transactions without compromising the main network. From Internet of Things Devices (IoT), to micropayments, this increases the value proposition of Ambrosus to enterprises wishing to manage and store potentially millions of data entries at a cost-effective and manageable rate.

Masternodes Development Update:

  1. A number of very important fixes and enhancements have been made to the different masternodes within the Ambrosus Ecosystem. With regards to Apollo Masternodes, problems related to high CPU usage specifically in the product environment have been fixed.
  2. A universal script for automated transfers of AMBs from Apollos to the Apollo Top-Up Account has been designed for more efficient movement of AMB among validator nodes.
  3. Concerning Atlas Masternodes, ‘Bundle Status Tracking’ (BST) has been implemented as a cleanup mechanism for Atlas Masternodes, to further streamline the process of efficient data storage.
  4. Hermes Masternodes have also been the subject of a number of positive enhancements: for starters, and most importantly, the Hermes Masternode Extended API has been released on GitHub! Such documentation provides additional querying capabilities which consists of both REST and GraphQL APIs. In relation to optimizing Hermes for enterprise usage, the signing of requests on the Hermes Load producer has been moved to the client side, indicating a sophisticated upgrade to the Hermes architecture. Along the same tangent, all scripts related to the Hermes Load producer deployment have been reviewed, with one minor security issue identified and resolved.
  5. Additionally, another tool has also been released on the Ambrosus GitHub, which allows any interested party to gather insights pertaining to each node’s status (i.e. Sync time and current block) on the network! More specifically, the Parity Exporter provides real-time insights into a number of important monitoring variables including gas fees, transaction queues, account balances, and gas limits (among other features) and is openly available for use by any interested party.

Front-End Developments:

  1. The Ambrosus Front-End Team presented a fine-tuned and concise introduction to — the Ambrosus ‘Asset’ and ‘Event’ search/management interface! Recently released on GitHub, this document explains how to utilize to visualize Assets and Events on the Ambrosus Network.

2. Front-End team has continued to work on UI fixes, Demo Application designs, and other front-end applications for different Ambrosus clients.

AMB-NET Tools and Fixes:

  1. A number of tools used on AMB-NET have been enhanced, while at the same time minor fixes and additions have been made to other components of the Ambrosus Ecosystem (challenge resolutions, distribution of rewards to bundles, and time stats of holding bundles have been added, while integration tests and alerts have been implemented.)
  2. Demo-Dashboard fixes have been completed, and a new and much-improved version of AmberEx has migrated to the Ambrosus Test Environment.
  3. A stress test has been run on the developer network to verify the activity of validators. Finally, all AMB-NET environments (Main, Dev, and Test) were checked while missing monitoring and alerts were documented for the production environment.

Dashboard Module Application:

  1. The public release of its Ambrosus Dashboard Module, accompanied by its Angular application documentation overview! Available on GitHub, this application and its accompanying documentation allows interested developers and entrepreneurs to download, and begin experimenting with their own dashboards for authenticating users connecting to AMB-NET, creating Assets and Events, and securing the transmission of data onto the network. A host of roles are available to dashboard users, illustrated in the photo below:

Ambrosus Bridge:

The Ambrosus Bridge has been undergoing significant developments, as it prepares to convert tokens from the first Atlas and Hermes Masternode operators into native AMB! Such developments include the following important milestones:

  1. all design/usability improvements have been implemented.
  2. metrics have been added to the bridge validator (i.e. number of discovered transactions as well as the number of warnings).
  3. scripts have been created for bridge contracts monitoring.
  4. the bridge has been checked in non-common use cases with no new issues discovered.
  5. test documentation of the bridge has continued, while necessary changes to the bridge test environment have been verified.

A number of measures have been done to both optimize the bridge in its current state, and to allow for community members to easily transfer tokens to and from the Ambrosus Network. More concretely, bridge optimization entails the following:

  1. timestamps have been added to logs, and all issues discovered in the end-to-end testing (e2e) have been checked;
  2. the e2e test has been refactored and improved for future testing.

Social encounters

  • Ambrosus business developer Rado Dragov is rocking it at Burberry HQ, presenting Ambrosus retail solutions to the management. $AMB-NET can be used to protect the quality and authenticity of luxury products!
  • EDCON 2019 — Vlad Trifa (Chief Product Officer, Ambrosus) giving a speech. Watch on YouTube.

Upcoming events:

  1. 15 May — Innovative Switzerland Program — Zug, Switzerland — Speaker: Angel
  2. 22 May — InNOWvate Supply Chain Event — Amersfoort, The Netherlands — Speaker: Rado, Kevin
  3. 3–5 June — Global Entrepreneurship Summit 2019 — The Hague, the Netherlands — Angel
  4. 6 June — Startup Grind Europe Conference — London, UK — Speaker: Angel
  5. 24–26 June — Crypto Valley Conference 2019 — Zug, Switzerland — Speaker: Angel
  6. 2–5 July — Tech Open Air — Berlin, Germany — Speaker: Angel


According to Q&A:

At some point between these first two dates, new documentation will be released relating to a unique and fully-functional IoT solution, as well as more detailed insights into the Ambrosus Edge Gateway itself.

The Ambrosus developer team will intensively test Atlases running on the newly updated AMB-NET. Therefore the next one to two weeks will be dedicated to testing the new DMP algorithm on TEST-NET. If that works as desired, a final test will take place on AMB-NET, after which Wave 0 Atlases will go live. If all goes according to plan, Atlases should begin onboarding by the middle of May.

By the end of June, a selection of core components of the Ambrosus Ecosystem involving IoT devices, Edge-Gateways, Hermes Masternodes and communication protocols, as well as the Ambrosus Network with accompanying Atlas and Hermes Masternodes will be fully-operational and functioning. Developers will be able to build robust applications utilizing all of the components of the Ambrosus Ecosystem, while entrepreneurs will possess all of the tools, required documentation, and information on collaborating with Ambrosus, in order to be successful in building and scaling real-world solutions.

Horizon Development

  1. Bundle synchronization will continue to be monitored, while performance issues relating to the MongoDB will be further analyzed. Beyond minor tweaks, the first Hermes and Atlas Nodes managed and operated by community members will be forthcoming.
  2. In the coming weeks, the DevOps team will be resolving any further discovered issues with validator optimizations. Particular applications will be deployed to the Dev-Environment, while an automated changelog generation for existing deployed components will be implemented.
  3. Future focus on the Ambrosus Bridge will be concentrated on completing test documentation, performing testing on the Ambrosus Explorer in relation to the Bridge, and also verifying the fixed UX design. While the bridge will constantly be updated, the developer team is pleased with its overall status and performance.


  • Photo from Telegram Community chat:


Token holders and the number of transactions dynamics (from
Source: coingecko.
Source: coingecko.

Social media metrics

Social media activity
Social media dynamics
Social media dynamics

The graph above shows the dynamics of changes in the number of Ambrosus Facebook likes, Reddit subscribers and Twitter followers. The information is taken from

This is not financial advice.

Subscribe to detailed companies’ updates by Paradigm!

Medium. Twitter. Telegram. Reddit.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store