Bigbang Core launches HUAWEI CLOUD, IoT device on-chain manual service

China, Xianggang, Guiqing – 05-25-2020 ( — The rapid development of computer technology and the Internet has brought about the era of electronic payment systems and globalized big data, and the efficiency of human data processing has taken a new leap forward. People’s responsiveness to needs, ability to plan for community events and businesses, and even the efficiency of human connection, have been elevated to a new level.

Obstacles to the development of today’s society are attributable to “mutual distrust” at the source. Blockchain has features such as non-tampering, decentralization, anonymity, and traceability, allowing for a stronger relationship of trust between the various subjects of society. These features are combined with various industry applications, ecological scenarios to produce real value.

BigBang core is a block system built on P2P network. Similar to the current popular P2P digital currency system, it maintains a transparent ledger in a decentralized manner to achieve independent security management and efficient flow of users’ digital assets. The BigBang system is designed for the needs of IoT (Internet of Things) data services. It uses block technology to provide a decentralized security management platform for IoT data services, to achieve high concurrent and low latency performance requirements for IoT systems.

On this basis, has launched an IoT device on-chain manual service on Huawei Cloud. It is an enterprise-grade blockchain service based on blockchain technology and years of accumulation in core technologies such as distributed parallel computing, data management and secure encryption.

LWS stands for light wallet service and is a bridge between the BigBang common blockchain backbone network and the terminal data collection sensor devices. Through it, BigBang Core Wallet’s block and transaction data are updated and cached in a timely manner in LWS’s own high-speed in-memory database and local databases.

Based on this data, it calculates the latest UTXO set of public key addresses corresponding to the keys held by different end devices, and publishes (publish) these messages to Amazon’s cloud facility via a mqtt connection to AWS’s IoT Core, which is forwarded by its message broker to the corresponding end device that subscribed (subscribe) to them. Correspondingly, the end device packages these UTXO lists associated with itself into the transaction after obtaining the data captured by the monitoring.

Through the latter’s message broker to the LWS that subscribes to these devices to send transaction topics, the LWS will verify these transactions. If the verification is successful, it will forward this part of the transaction to the BigBang Core wallet through the Socket API. After the latter receives it, it will pass The P2P network interface broadcasts these transactions to BigBang’s entire network, the block-producing nodes collect these transactions, and finally complete the operation of their packaged blocks on the chain.

The BigBang client program, which is part of the IoT Device Firmware, utilizes a device CPU and secure computing co-processors to handle BigBang transaction-related computations including transaction build and resolve, HASH, ED25519 signature and validation, and more. The device private key is stored in a secure area of the processing chip and cannot be read directly. The protocol process between the LWS and BigBang clients synchronizes and updates the client UTXO list in real time. The LWS responds to BigBang clients sending transaction requests and broadcasts transactions across the network through connected network nodes.

The complete interaction flow between the IoT endpoint sending a transaction and the LWS is as follows:

Service Req/Reply: The BigBang client initiates a service request, passing information such as protocol version, wallet address, and required branch; the LWS returns the data used to construct the APIKey and a list of supported branches, provided the service is available; the APIKey is used for subsequent message signing.

Sync Req/Reply: The BigBang client initiates a synchronization request and passes the current record UTXO list HASH; LWS compares the UTXO list HASH and pushes the corresponding UTXO list if the client is judged to have lost step.

Update UTXO: When Block/Tx status updates (new block generation, transaction broadcast), the network node notifies the LWS via the Socket API, and the LWS pushes the UTXO status changes to the BigBang client after filtering.

SendTx Req/Reply: The BigBang client constructs and signs transactions based on the synchronized UTXO list, and broadcasts them to the entire network via LWS; LWS returns to the execution state.

LWS addresses the high concurrency and scalability of devices using AWS-provided long-connected, two-way message pub/sub message proxies that decouple from data interactions on the device side of a huge number of connections.

There’s no doubt that the increasing use of IoT devices today as technology civilizes raises concerns about transaction and data security, and the emergence of blockchain solves the critical trust issue. Blockchain and IoT are destined to be diversified as a result of the collision of blockchain and IoT. BigBang Core is an open, easy-to-use, flexible and efficient general purpose base service based on blockchain technology applied to IoT that will respond to the access and ownership of data from connected devices as open as possible; finding a direction that can be authenticated and take the characteristics of blockchain to the extreme by deep integration with IoT!

Media Contacts:

Company Name: BigBang Core
Full Name: Vicky Shu
Email Address: Send Email

For the original news story, please visit