SBHACK19 is the largest Blockchain hackathon event in Switzerland, organised by Trustsquare, which calls itself the “largest blockchain hub in the world.”

The goal of this hackathon was to explore use cases that solve real-world challenges.

For the Vertical (category) “Supply Chain”, the Elastos Team was made up of members: Peter Strauss and Artur Zsuravely of Hyperconnect, Adem Bilican of Elastos Unity, Mehmet A. Dogan from the CR Community, Nicola Zimmermann–the CR Community Manager and Co-Founder of Elastos Orchard.

The instructions for the hackathon were:

Build sector-specific solution offerings which helps your Vertical’s partners [the Supply Chain Vertical partners were GS1, Accenture, Panalpina and Cargolux iirc] in their journey towards digital transformation. Participants can compete in the following areas:
The Supply Chain’s challenges are shown below:

The Elastos Team, “Elastonians”, took first place in their division:


Gandhi has provided CR Press with a few of his thoughts from the event:

  • Most people, both coaches and competitors, were very interested in learning more about Elastos, especially in regards to Elastos’ scaling solution using the Main Chain–Sidechain structure with each sidechain used for a specific purpose.  This was well highlighted by the ID chain. While most teams in our Vertical were programming smart contracts, we were able to create a solution without using any smart contracts thanks to DIDs and the available APIs.
  • When mentioning Ethereum and NEO sidechains, the reaction was always very positive.  Most developers don’t want to learn a new smart contract system and are happy with what Ethereum is already offering.
  • Aside from the sidechains, Elastos Carrier helps solve the scalability problems.  This was highlighted in our project by using Carrier for p2p communication between smart containers, IoT devices/sensors, and a mobile application.  Instead of logging every event on the blockchain, we only logged the state of the container and products when they change from one party to another. We also allowed permission-based live tracking using Elastos Carrier and the HyperConnect framework.
  • The key word “serverless” was well received by most.  Those involved in supply chain are very aware of the limits of blockchain technology and they acknowledged that the combination of DID and Carrier could solve a lot of their problems.
  • Elastos Runtime wasn’t mentioned much because it is still in development.  It’s better to focus on what is already in production: Carrier, Main Chain, and ID sidechain.
  • Elastos’ consensus mechanism was met with overwhelming positivity, even if the topic didn’t come up too often.  DPoS added to a PoW layer leads to a higher finality of blocks without sacrificing decentralization and security.  It is important to mention that sidechains can choose their own consensus mechanisms (AuxPoW or DPoS), or potentially a custom mechanism in the future can be made if there is enough demand for it.
  • Decentralized storage was not talked much about, oddly enough, and it was seen more as a gimmick than a necessity for dapps.  There needs to be more education about distributed storage and its importance to dapps. To achieve this, Rong’s definition of a dapp should be refined into a new standard (Howey test for dapps?).  Then, Elastos will be the only ecosystem providing all the tools to build true dapps, which can’t be shut down by anybody.
  • There is a high demand for real solutions in the real world for every industry.  Blockchain solves a lot of them and Elastos has cutting-edge tech compared to other platforms used in the competition.
  • Business leaders as well as politicians are willing to use open source and public blockchains.
  • Developers immediately understand Elastos’ architecture, especially when you show them how it works instead of just explaining it.
  • English documentation is still severely lacking and without Song’s help, it would have taken a lot more time to go through the code to find what we were looking for and therefore, not finish in time.  At this stage, running dapp competitions therefore doesn’t make sense unless the goal is to create the documentation prior or through the competition.
  • Peter Strauss is really good at creating documentation; a large part of the english Carrier documentation was written by him.
  • Most teams were either startups or teams from existing businesses.  Few were teams like ours. Nevertheless, the community spirit was great and everyone helped each other wherever they could.
  • It was a lot of fun.
  • Developers don’t seem to need to sleep.  Artur was on site the whole 42 hours and slept only for 45 minutes.  The rest of the time was spent coding.
  • Organizing a hackathon is a huge undertaking and the resources needed to hold one should not be underestimated.  It is best for CR to collaborate with organizations like Trustsquare and sponsor a Vertical or special award rather than running it entirely alone.  To do this, there needs to be enough coaches to support the teams trying the Elastos infrastructure.
  • Attending a hackathon is a great way to grow your network and meet all kinds of people.

Read a press release on the hackathon here.

Visit SBHack19’s websites here:
Search for #sbhack19 on twitter.



Please enter your comment!
Please enter your name here