[ANN] BigBang Core Re-energize the IoT

[BigBangCore]

Consensus Mechanism

As mentioned above, the consensus mechanism adopted by BigBang Core system is EDPoS+CPoW, which is dominated by EDPoS to determine the node that gets the right of block next time or indicate that the next block is generated by the consensus of workload proof.
When the EDPoS mechanism is not established effectively, such as in the initial stage, CPoW becomes the only consensus mechanism.
The consensus mechanism is described in detail next week.

[1714026800]

1714026800

[1714026800]

1714026800

[1714026800]

1714026800

[1714026800]

1714026800

[1714026800]

1714026800

[BigBangCore]

EDPoS Node Negotiation Process
The number of Token votes held by the EDPoS node is used as the
weight of the block, and the fixed block node series is generated by
random number calculation. After the establishment of EDPoS
mechanism, random Numbers are generated through negotiation
between EDPoS nodes. The negotiation process takes place once a
minute, and fair random calculations are made through weighted
verifiable key sharing (VSS) and Byzantine fault tolerance.
Each round of consultation includes the following procedures: 1. Node
registration; 2. Encrypted sharding data distribution;3. Secret Footage
released; 4. Data reconstruction and random beacon calculation.
Before each round of negotiation, each EDPoS super node needs to use
ECC algorithm to generate a set of private keys: {a0,a1...,at-1}, and the
corresponding public key: {A0, A1..., At-1}, satisfies Ai = aiG, (i = 0,1...,t -
1). t is the threshold value of reconstructed data, and the maximum value
of t is 50 according to the effective EDPoS super node.

[BigBangCore]

1. Node Registration

EDPoS super node will broadcast the registration information on the chain before the round of negotiation for the 16 blocks of the standard
block, including the encrypted polynomial coefficient {A0,A1..., At-1}, A0 as the public key for node negotiation.

[BigBangCore]

Light Wallet Service and LWS-Client

The light wallet service, abbreviated as LWS. It is a bridge between the blockchain of the BigBang Core network and the data acquisition sensor
of IoT device. BigBang Core Wallet's block and transaction data are updated and cached on time in LWS's own high-speed memory database and local database via LWS.

It calculates the latest UTXO collection of public key addresses for which different IoT devices hold keys based on this bunch of data. And sends
(publish) the data to Amazon's cloud facility via a MQTT connection provided by AWS IoT Core. Broker forwards to the IoT device where the
corresponding subscription (subscribe) has this information. Accordingly, the IoT device will package the collected data into the transaction based on these list of UTXO related to itself and publish it to Amazon IoT Core via MQTT.
Then, the Message Broker of the Amazon service is pushed to LWS, which subscribes to the sending transaction topic sending these devices, and LWS verifies these transactions and, if the result of verification is successful, the LWS forwards this transaction to the BigBang Core Wallet via the Socket API. After received the transaction, the core program broadcasts the transaction to the BigBang Core network by the P2P network interface, and the node that generate block will collect these transactions, which are eventually completed the process of packaging these transactions into blocks and permanently stored on the blockchain.

The LWS client program, as part of the IoT device Firmware, it uses the CPU and secure computing coprocessor of the IoT device to process BigBang Core transaction-related calculations including transaction construction/deconstruction, HASH, ED25519 signature/check, etc. The device private key is stored in a secure area of the chip and cannot be read directly.