create account

AN ARCHITECTURAL PROTOCOL by raihanrahman

View this thread on: hive.blogpeakd.comecency.com
· @raihanrahman ·
AN ARCHITECTURAL PROTOCOL
For various open public blockchain, anyone can download the source code and coordinator a node of blockchain on any device without substantially restrictions on computational ability or hosting environment. Alas, this is normally not really the case for real-work organization applications in the e-commerce sector. For case, all offerings that accept credit rating playing cards or retail store cardholder info must become managed with a PCI compliant hosting specialist. This is normally for the coverage of financial info, and it is normally likewise expected by law in many countries. Consequently, many of the customer-facing e-commerce applications we have today cannot operate openly on a particular blockchain node. Related difficulties may as well arrive in the format of upload speed, computer space, computation electric power, etc.   

![ApolloX Protocol1.JPG](https://cdn.steemitimages.com/DQmc9kfAybpcJ3f2f4jAW9axgT3VP4hCqoipAjrdGHxTZyZ/ApolloX%20Protocol1.JPG)
In order to overcome this issue, we propose a [ApolloX Protocol](https://apollox.network/)for each and every ApolloX node to define and identify the formal requirements for each and every position.  For example, a node may possess one purpose for credit rating greeting card processor which needs a PCI compliant node, and another node provides the purpose of covering photos to cell clientele.

This node requirement will not break the decentralized nature of Dapps on ApolloX [ApolloX Protocol](https://apollox.network/) as there is no central point of control or central point of failure. Anyone can deploy and maintain nodes, as long as it suits the fundamental requirement set by the [ApolloX Protocol](https://www.facebook.com/apolloxnetwork/). Miners who bring significant sums of computing means for hosting large capacity nodes will receive considerably more ApolloX tokens as an incentive than studied to those with low ability nodes.  

[ApolloX Protocol](https://www.facebook.com/apolloxnetwork/) nodes consist of a collection of middleware frameworks. These middleware frameworks happen to be standardized, reusable hindrances for setting up e-commerce applications, many of these as record devices, world wide web servers, API gateways, etc.   

[ApolloX Protocol](https://t.me/apolloxgroup) nodes may be deployed using the standardised Docker containers which can go in any important cloud platform, like Yahoo Clouds, MS Orange or even a personal computer.  ApolloX will distribute the nodes across the globe, furnish redundancy and program velocity improvement. For model, the ApolloX Industry will under no circumstances move offline.

It is believed there will be several key open public blockchains co-existing and many more directory blockchains for particular establishments. As a final result, it’s important to believe about support for interlock chain connection on moment one. ApolloX is definitely built with Tendermint-BFT and may easily acquire integration with Cosmos and enable features like used exchange and bridging for different cryptocurrencies.

E-commerce applications usually generate large volumes of info found in the daily procedure. It would come to be a superb misuse of resources if all that info was required to become placed on a blockchain. Consequently, in our style, we shop appropriate non-core data off the company and into an allocated database, like  Cassandra or data storage that is decentralized space system many of these as IPFS. The requirements for choosing what types of info to be placed off-chain is determined by their size, whether they will be associated to the level of privacy data, and whether they will be wanted by intelligent deals in [ApolloX Protocol](https://t.me/apolloxgroup).    

Info placed on a blockchain is readable to every node of the blockchain, yet a lot of info found in an e-commerce request requires privateness safeguard, including the buyer’s name and address. ApolloX deals with the level of privacy info by encryption before storing them in accordance to the related parties’ consumer secrets. For model, by default, just the shopper and the retailer contain access to an order’s facts,  and our program will encrypt the purchase info with the buyer’s major and seller’s major. After encryption, no person can read the order’s data without documentation from the purchaser or seller.
![ApolloX Protocol3.JPG](https://cdn.steemitimages.com/DQmVYPLxF1bsA2S95i7Ai93t6P6sAziemdjHU5gn48VcBhY/ApolloX%20Protocol3.JPG)


ICO NAME | ![ApolloX Protocol.JPG](https://cdn.steemitimages.com/DQmcYW6eRSG7ioeBueJK13rc6yma7ncDQ22kRzBpx2m4M73/ApolloX%20Protocol.JPG)
------------ | -------------
Website | https://apollox.network/
Twitter | https://twitter.com/apolloX_network
Telegram | https://t.me/apolloxgroup
ANN | https://bitcointalk.org/index.php?topic=4650252
Author Bitcointalk ID | Jerrycryptofield
Bitcointalk profile link | https://bitcointalk.org/index.php?action=profile;u=1660015
ETH wallet address | 0xBc41d2eCe871178a375d3e636ff6dEd1fBaCA1C2
👍  ,
properties (23)
authorraihanrahman
permlinkan-architectural-protocol
categoryprotocol
json_metadata{"tags":["protocol","cryptocurrency","eth","blockchain","crypto"],"image":["https://cdn.steemitimages.com/DQmc9kfAybpcJ3f2f4jAW9axgT3VP4hCqoipAjrdGHxTZyZ/ApolloX%20Protocol1.JPG","https://cdn.steemitimages.com/DQmVYPLxF1bsA2S95i7Ai93t6P6sAziemdjHU5gn48VcBhY/ApolloX%20Protocol3.JPG","https://cdn.steemitimages.com/DQmcYW6eRSG7ioeBueJK13rc6yma7ncDQ22kRzBpx2m4M73/ApolloX%20Protocol.JPG"],"links":["https://apollox.network/","https://www.facebook.com/apolloxnetwork/","https://t.me/apolloxgroup","https://twitter.com/apolloX_network","https://bitcointalk.org/index.php?topic=4650252","https://bitcointalk.org/index.php?action=profile;u=1660015"],"app":"steemit/0.1","format":"markdown"}
created2018-09-08 11:36:36
last_update2018-09-08 11:36:36
depth0
children3
last_payout2018-09-15 11:36:36
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length5,013
author_reputation530,866,524,718
root_title"AN ARCHITECTURAL PROTOCOL"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id70,691,833
net_rshares6,123,874,113
author_curate_reward""
vote details (2)
@introduce.bot ·
 @raihanrahman, I gave you a vote!<br>If you follow me, I will also follow you in return!<br>Enjoy some !popcorn courtesy of @nextgencrypto!
properties (22)
authorintroduce.bot
permlinkintroduce-bot-re-raihanrahmanan-architectural-protocol
categoryprotocol
json_metadata""
created2018-09-08 11:36:42
last_update2018-09-08 11:36:42
depth1
children1
last_payout2018-09-15 11:36:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length140
author_reputation20,568,707,332,317
root_title"AN ARCHITECTURAL PROTOCOL"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id70,691,838
net_rshares0
@popcornexpress ·
![](https://cdn.steemitimages.com/DQmZUKwQtFShDVKPFRwZm4sDqiQwaVMgSn7TciApFNk9By2/7.gif)
properties (22)
authorpopcornexpress
permlinkre-introduce-bot-re-raihanrahmanan-architectural-protocol-20180908t113713
categoryprotocol
json_metadata""
created2018-09-08 11:37:09
last_update2018-09-08 11:37:09
depth2
children0
last_payout2018-09-15 11:37:09
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length89
author_reputation7,011,339,506,459
root_title"AN ARCHITECTURAL PROTOCOL"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id70,691,874
net_rshares0
@surikowstepanuk ·
Right thoughts you have @raihanrahman, and set them cool
properties (22)
authorsurikowstepanuk
permlinkre-raihanrahman-an-architectural-protocol-20180909t231523528z
categoryprotocol
json_metadata{"tags":["protocol"],"users":["raihanrahman"],"app":"steemit/0.1"}
created2018-09-09 23:15:24
last_update2018-09-09 23:15:24
depth1
children0
last_payout2018-09-16 23:15:24
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length56
author_reputation-480,092,939,488
root_title"AN ARCHITECTURAL PROTOCOL"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id70,828,924
net_rshares0