A new partnership paves way for blockchain to an airspace area

A special IoT blockchain framework offers secure solutions even in an unsecure environment
02 March 2018   322

Today, on March 2 in Geneva a leading Swiss cybersecurity and IoT solutions company WiSeKey has announced a strategic collaboration with a California-based blockchain airspace platform developer VIMANA Global. WiSeKey has a unique blockchain framework that offers all-in-box security measures with an API that is easy to implement and effectively manages the life-cycles of devices and their respective digital certificates.

The sector of Autonomous Aerial Vehicles is growing fast, and traditional air traffic control towers are not designed to handle thousands of flights within the urban area. The resources of WiSeKey with efficient control, secure environment, optimized information processing will potentially solve the scalability and security issues of VIMANA. Blockchain technology and its peer-to-peer nature allows it to operate with big data volumes.

Security and positive identification are the key elements in peer-to-peer exchanges that power the VIMANA Blockchain Airspace platform. The combined ecosystems give us the opportunity to potentially support exciting new features in the future.


Evgeni Borisov


With every node (AAV) in the network connected and communicating with each other constantly, the clients will be able to just enter their destination and relax.

By combining WISeKey's Secure Element (our tamper-resistant silicon chip) and its managed Public Key Infrastructure (PKI) systems with the VIMANA Blockchain Airspace platform, we are bringing a powerful solution that increases the level of safety for IoT transportation systems, while ensuring maximum security and trust on the system.


Carlos Moreira

Founder & CEO, WISeKey

The first pilot cities to host the project are Dubai, Abu-Dhabi, Tokyo, Singapore, and Mumbai. VIMANA will test its aerial commuter vehicles with vertical take-off and landing.

7 Accounts blocked by EOS BP without Going an Arbitration

EOS is facing another issue just days after its mainnet activation, as the newly elected block producers have frozen 7 EOS accounts on suspicion of being stolen
19 June 2018   48

The backlash began as the block producers did go over arbitration, an integral part of the EOS’s governance system. The critics are certainly questioning the credibility of the project. Jackson Palmer, the creator of Dogecoin and a well-known person in the blockchain industry, questioned the very governance process constructed by EOS and the role of EOS Core Arbitration Forum (ECAF).

The structure of EOS’s governance has been parted into 3 distinct groups - block producers, arbiters, and token holders. This separation resembles the executive, constituency, and judicial, of any governed system respectively. 

On 17 June 2018, the top 21 Block Producers unanimously agreed to protect property that may have been compromised through phishing attacks or other scams where member’s private keys were compromised. The EOS911 initiative was created by EOS42 as a way to prevent victims of private key theft from having their tokens lost once the 72-hour unstacking period ended following the EOS Mainnet Launch. Once that period ended, the thieves would be free to transfer the tokens wherever they’d like, rendering futile any recourse available to the community at this time.
EOS New York, in their recent post

So, in this case, the block producers did not go with the arbitration, rather they only conferred with them. Then the post added:

Foreseeing the process that would be required to act, EOS New York, on a call with BPs and BPCs, requested an expedited review of the merits of the case from ECAF (EOS Core Arbitration Forum) who was also on the call. The idea was that if ECAF found merit in the evidence provided, a formal ruling from ECAF would ask the BPs to “freeze” the accounts in question until such time that a thorough and formal review of the claims could be completed.
EOS New York, in their recent post

This is not the first problem EOS is facing amid its mainnet activation, as within 48 hours of that, the network suspended because of some bug. Though the error only led to a 5-hour network blackout, that is surely not something the team would have expected.