If you want, you can get a lot of informations on
https://blog.blocksafe.network/Here below, just take a look about informations of the projectWhat is Blocksafe Alliance building?
We are building a platform to offer custom blockchain solutions that can both assign data to the blockchain and scale IoT networks on chain. Businesses will be able to utilize our platform to select custom features for their own private or public subtokens. These systems will be capable of privately delivering large data sets that are stored on, and distributed by, our blockchain through our subtokens and Masternode network design. Businesses and innovators will get their own subtoken equipped with individually selected features for their needs. Through integration with existing and specially designed networks, these individual subtokens on our network will be able to support IoT solutions and even large data in a highly scalable way.
What is the network made of?
While we cannot share every aspect of our network’s security, or how we internally deliver on the functionality of our network, we are happy to share where our inspiration comes from. Each of the projects that we are grafting together solves problems with scalable IoT blockchain solutions. We solve some issues with our own innovations, but an understanding of the following will suffice for most people who want to know what our network is;
Red5 is a media-streaming server written in java. Red5 supports streaming video (FLV, F4V, MP4, 3GP), streaming audio (MP3, F4A, M4A, AAC), recording client streams (FLV and AVC+AAC in FLV container), shared objects, live steaming video and audio (FLV, VP6, MP3, AAC), remoting (AMF), and RTMP, RTMPT, RTMPS, and RTMPE protocols. Red5 is meant to be easily integrated and is broadly used to provide the features of its network as a cost-efficient and scalable solution.
Qtum is an enterprise-focused project meant to offer cross-compatibility between Bitcoin and Ethereum Virtual Machine. Qtum is an open-source blockchain project that uses Bitcoin’s core code, incorporates POS, and puts the EVM on top of it. Qtum’s Account Abstraction Layer exists as a layer between Bitcoin Scripting Language and the Ethereum Virtual Machine. Qtum takes Ethereum’s Account Model and makes it compatible with Qtum’s version of BTC’s Unspent Transaction Output. This gives any project that uses Qtum to build an enterprise-ready blockchain the ability to choose the features they wish to use from projects built for either Bitcoin or Ethereum Virtual Machine.
Quorum is an enterprise-focused version of Ethereum. Quorum is a permissioned ledger where preselected delegates are given voting rights for specific consensus. This method allows for private and public transaction categories. It is also highly scalable and allows Quorum to perform hundreds of confirmations per second.
TrigX is comprised of each of these projects. Some features from each are foundational; they will be present in everything that we create on our network. The content-delivery features of Red5, the integration with the EVM of Qtum, and the methods of consensus voting from Quorum are foundational to our network. While Red5 is entirely foundational, some features and possible integrations offered by both Qtum and Quorum will not be necessary for many Blocksafe projects. There are also many features that overlap. Our task is to choose the features that are provided in a superior way, offer both where there are advantages for each, and to provide custom features or integrations where needed depending on the use case. We will also be integrating technology kits which will simplify building prototypes of new products on our network, similar to the IOT platform Particle. Data routing, encrypting of data, decrypting of data, etc. are all handled by separate parts of the network, making the overall design highly decentralized and secure. The only thing that ties the information together is the user’s private key.
How will it all work?
With all these features combined along with our proprietary work focused on security, we will have a very robust set of tools to offer on our network. Our subtoken service will offer security, flexibility, scalability, and a built-in system of exchange for other subtoken tokens as well as TrigX. The graphic below shows our initial subtokens and illustrates how the information for different use cases might travel differently across the Blocksafe Alliance network.
If you’ve been following the project, you’ll notice some changes to our Masternode layer. As, we’ve said, we are taking advantage of many of the core features of the content delivery network provided by Red5. One of the many reasons that we love Red5 as a CDN solution on the blockchain is that it is already compatible with a decentralized design. Red5 uses decentralized servers to deliver content on their network referred to as Origin Servers and Edge Servers. In light of this, and out of respect, Blocksafe Alliance would like to announce a few adjustments to the design of our Masternode layer. These will be the Masternode tiers upon launch: Origin Masternodes, System Masternodes, Chain Masternodes, Storage Masternodes, and Edge Masternodes.
Origin Masternodes, which are named after Origin Servers on the Red5 platform, serve two main functions. First, they are the load balancers for the data and hash routing on the entire Master Node layer. They also tag and track tokens. They ensure POB (Proof of Balance) is maintained concerning the transmission and storage of data across all four Master Node tiers. Origin Master Nodes also provide protection against the possibility of a majority hash power attack (51% attack) by always routing traffic to the edge layer where possible. This ensures the decentralization of hash power at all times.
System Masternodes’ role will remain the same. System Master Nodes will perform consensus on the network to securely transmit data. When data is transmitted across our network, System Master Nodes ensure that three points of consensus are reached before beginning the process again on the next node. Whether the data is being verified and transmitted on a System Masternode or Edge Master Node, it is still the duty of the System Master Node to ensure that the data remains encrypted (POE), stored where it should be (POS), and that it is distributed to, and only to, the proper channels. This layer will also control system processes such as virtual private network, system only/ logging data etc.
Chain Masternodes will perform consensus on binary and string data provided by sensors on the network.
Storage Masternodes , a new addition to the Master Node layer, will assist in the transmission and on-chain storage of larger data when it is needed. The routing of this data will still be controlled by the POB feature of the Origin layer.
We’ve also decided to add Edge Masternodes. These will interact with the Origin Masternode layer to control the networking and data flow between the Masternode layers. This is a preferred method over using the Origin Masternode for the majority of traffic as it protects against a 51% attack through ensured decentralization.
The most expensive Masternode, the Origin Masternode, will still require that 1500 trig be locked up for the duration of the license term and reward 375 ammo per month in exchange for the services provided. For the additional classes of Masternodes, we would now prefer to determine the cost and payout specifics closer to our main net launch. We know that the remaining four layers will be cheaper in both cost and reward.
*All Masternodes will be required to meet minimum requirements for maximum reward. Minimum requirements will be determined during the testnet period.
