Scam or legit? ioeX

c1s0r Jun 27th, 2018 48 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.     Decentralized Peer-to-Peer network blockchain ecosystem that allows manufacturers to save money on IoT device upgrades. In turn, users/owners of these IoT devices have the option of participating in the support of the entire P2P network and get ioeX coins as a reward. Users can even mine Bitcoins and ! simultaneously. Strong team, good idea, nothing questionable found.
  3. Our verdict: Not a scam, Approved!
  5. # Overview
  6. ## Concept
  7. Decentralized Peer-to-Peer network blockchain ecosystem
  9. Architecture based on distributed networks — combining the Internet, IoT, and blockchain solutions.
  11. ## Actual Product
  12. At this stage, they are offering the infrastructure itself and a platform for updating IoT devices based on this infrastructure.
  13. # Site
  14. Standard for these types of projects one-pager site without accepting any data input - thus cutting down on security issues.
  16. # Social Media
  18. Telegram_en: 5521 members
  19. Telegram_cn: 6462 members
  20. Facebook: 10166 likes
  21. Twitter: 7539 followers, 44 tweets
  22. Medium: 15 posts
  24. Social activity and follower numbers are actually very impressive for such a young project (1 1/5 month old).
  26. # Team
  27. The project's founder, Aryan Hung, gathered around himself an experienced group of experts. The core of the team worked at Foxconn at some point. No team member seems out of place - their collective experience 8-15 years.
  29. Note that the more experienced team members worked at Kortide, which morphed into Elastos Foundation — one of the main strategic partners of this project. All in all, looks like the team's professional capabilities are enough to deliver on their promises.
  31. # Consultants
  32. Almost all of the project's consultants are from their strategic partners and vendors. The exception is Colin Cheng — Founder of FintechCPA, which is a rather well-known organization in Japan. The most noteworthy consultants here are Rong Chen, the founder of Elastos Foundation, and Simon Szeto, Director of SBI E2-Capital HK.
  34. We see no reason to doubt the competency of these consultants.
  36. Interesting that ioeX is financed by an investment from SBI E2-Capital. And it's also one of the first projects financed by an investment from EOS VC.
  38. On the downside, their website doesn't list team members' or consultants' social profiles (even though all of them have social media profiles).
  40. Another annoying thing is that not all of the team member names on the English version of the site are quite the same as their names on LinkedIn — this is common for Asian projects, but should still be corrected.  
  42. # Whitepaper
  44. ## Project Summary
  45. Number of IoT devices is growing rapidly. Upgrades via OTA servers are too costly for manufacturers (both server and traffic cost).
  47. ioeX offers a "Decentralized Peer-to-Peer Network" solution. Such a network allows to maintain and relay content with minimal expenses.
  49. For starters, they're offering a solution for online updates. Eventually, will add new features.
  51. ## 1. Motivation and outlook
  52. Of course, the IoT device market is growing in terms of both the number and variety of devices sold.
  54. Each such device needs periodic updates (for adding new functions, fixing errors, maintaining a high level of defense from hackers, etc.). Both the software and the firmware needs updating.
  56. When an update comes out, all the devices start updating automatically. This overloads the servers much like a DDoS attack would. There have been plenty of cases of servers shutting down because of big updates. Which adds repair costs. Adding multiple servers to handle the update volume also raises costs.
  58. Beyond server maintenance costs, traffic costs are also significant, as noted in an example provided by ioeX:
  60. With 5 million active devices and a 50Mb update, using network traffic cost of US$0.1/GB (Amazon Web Services), this one update costs around US$25,000. Frequent and bigger updates are thus very costly for a manufacturer.
  62. Even beyond updates, all IoT devices have to store and relay a lot of information to the network.
  64. When a user wants to contact an IoT device via the Internet, there are often direct access issues (multi-level routing, firewalls, NAT). Which forces manufacturers to launch and service relay launchers. Again, this is an additional cost.
  66. All of the above problems is what ioeX is offering to solve.
  68. ## 2. The ioeX solution
  69. ioeX is offering their Decentralized Peer-to-Peer Network to fix the above problems. (referred to as "Carrier" in this section).
  71. The network itself is built on Elastos (which merits a whole other review).
  73. What's this Carrier? It's this perfected Peer-to-Peer network. It uses nodes s peers. And communication is Friend-to-Friend.
  75. The network can contain two types of nodes:
  76. - Bootstrap Node (Connects all peer nodes to form a network and assist peer nodes to relay data)
  77. - Peer Node (Saves and transports files for self and keeps files for remote delivery for other nodes)
  79. Initially, the network will not have trusted (Friend-to-Friend) relationships between nodes. Which allows them to avoid hacker attacks via direct network address.
  81. Since Carrier is a communication framework and does not have any application features or attributes - it doesn't store any information about users (like what and where is sent by a node). Instead, the node itself stores all the info.
  83. Nodes can freely exchange information only if they implemented a trusted relationship.
  85. App developers can flexibly control all aspects of the Carrier.
  87. Any data passed through the network can be encrypted. It can be translated using UDP packet-like mode (active by default) or TCP-like streaming mode - depending on an app's need.
  89. To transfer large files, developers must provide support to the Socket through own application (if they want interrupted downloads to be supported).
  91. All user APIs are asynchronous — which allows to initiate many operations without blocking or waiting for any operations to complete. The process can retrieve the result of an operation later or when it receives a notification of its completion.
  93. If a node cannot connect directly to another node, it's assisted by the Bootstrap Node, which acts as a Relay node. Carrier will choose the optimal route to transfer a file between nodes, including relay nodes (Bootstrap Nodes). Regular nodes don't store locally a list of all the Bootstrap nodes, just the nearest.
  95. UID acts as an indentifier in this network. The white paper indicates that if User B gets the same UID as User A, he will not be able to receive access to all the data of User A. To do that, B would have to establish a trusted relationship with A.
  97. The Carrier ID generated it first appears in the network is a public key corresponding to a key on the ECC Curve. All connections and transfer of data is encoded end-to-end between the nodes on each side.
  99. Carrier does not support offline messaging.
  101. Using the functions of Elastos, the team hopes to develop cross-network application.
  103. ioeX will contain a number of large-scale self-operated seed bootstrap nodes and seed peer nodes to provide peer-to-peer networking functions.
  105. IoT device upgrades will take place as follows:
  107. 1)  ioeX receives the update file from the manufacturer
  108. 2)  ioeX sends this file to seed peer nodes
  109. 3)  All Friend relationship nodes get updated by seed peer nodes
  110. 4)  Every update file will have its own address in the network.
  111. 5)  The manufacturer initiates the process of updating its devices.
  112. 6)  Randomly selected devices download the updates from a random address (until all devices that need the update are updated).
  113. 7)  The device is updated.
  115. This uses IPFS and so the update file is stored - in pieces and encrypted - on multiple seed peer nodes, which is safe.
  117. ## 3. How ioeX creates a Peer-to-Peer Networking ecosystem chain
  119. **Market Entry Method**
  121. - Equipment manufacturers can build-in support for P2P software during production.
  122. - Solution providers can provide manufacturers with solutions that embed P2P network capabilities
  123. - Chipset manufacturers can provide software and hardware integrated production solutions that come with P2P network capabilities
  124. - Collaborate with software companies from other authorized chipset manufacturers to license software with P2P network functions
  126. The target audience are the manufacturers of IoT devices. The White Paper indicates that ioeX is in negotiations with the leading manufacturers of various hardware (including Realtek and Mediatek). Later, they plan to work with Cisco, Fujitsu and Huawei.
  128. The team hopes that large e-commerce systems will want to integrate P2P networks incentivized by crypto. Which will add more Bootstrap Nodes to the system.
  130. And distributing apps to cell phones will allow any phone to become a Peer node — adding more Peer Nodes to the system.
  132. ## 4. ioeX token
  133. The platform will use blockchain technology. In this blockchain, they will record, for example, the amount and time of bandwidth. Node reward size will be based on this data.
  135. Token uses:
  137. - Pay with ioeX to get the network service
  138. - Reward miners of blockchain ledger
  139. - Reward bootstrap nodes to share the bandwidth
  140. - Reward peer nodes to share the storage capacity
  141. - ioeX eco-system can interact with Elastos / ELA
  142. - As a new payment tool in many industries
  144. Nodes will get ioeX tokens for providing network traffic and storage. This encourages device manufacturers to join the ecosystem (and incentivizes consumers to buy those devices because such devices can earn crypto)
  146. Through strategic cooperation with Elastos to share Bitcoin computing, the Bitcoin miner can generate additional rewards by simultaneously mining ioeX without extra costs in the mining process.
  148. To support the mining credit line, ioeX issue will increase by 3% every year. To keep the price of ioeX steady, the company will use 25% of its profits to periodically repurchase ioeX tokens.
  150. **"GAS" token issued on ioeX**
  152. To protect users from falling prices of ioeX and to pay for services within the platform, they will use GAS.
  154. GAS is fixed at US$1.
  156. The sources of GAS tokens are:
  158. - Exchange from user's ioeX wallet with ioeX coin.
  159. - Others may transfer GAS from their ioeX wallet to user's wallet.
  160. - Exchange ELA (Elastos coin) for GAS from the ioeX wallet.
  161. - Become a bootstrap node or peer node of a P2P network and obtain the award quota by providing P2P network services.
  163. Reward amount will be announced after the ICO.
  165. Using GAS, users can pay for:
  167. - Private cloud drive storage
  168. - P2P instant online communication tools
  169. - Remote screen control
  170. - Smart home device control
  171. - etc...
  173. **Token Economy**
  175. ioeX token holders can exchange them into GAS.
  177. ioeX token allocation:
  179. - 55% private sale and crowdfunding
  180. - 17% are used by the ioeX Foundation for the future development of ioeX coins
  181. - 10% will be held by team members in sealed state for 30 months and gradually released every six months.
  182. - 5% will be held by angel investors in sealed state for 30 months and gradually released every six months
  183. - 5% will be held by strategic investors to be sold to chipset vendors and solution providers and other strategic partners
  184. - 3% will be held by consultants
  185. - 3% will be initial mining reward
  186. - 2% will be used for promotional incentives as marketing expenses for project promotions.
  188. Funding use post-ICO:
  190. - 40% Future P2P network development
  191. - 30% Marketing, exchange listing
  192. - 15% Alliance building in strategic manufacturers investments
  193. - 15% Reserve fund for future development use
  195. ## 5. ioeX Roadmap
  196. **2018 Jul**
  197. - Release of basic service SW of ioeX P2P network
  198. - Messages and files can be sent by single-peer-to-single-peer and
  199. - single-peer-to-multi-peer.
  201. **2018 Aug**
  202. - Import ioeX P2P network function into IoT box and its remote Zigbee
  203. control APP.
  205. **2018 Sep**
  206. - Import ioeX P2P network function into AI Smart Speaker and its
  207. remote control APP.
  209. **2018 Oct**
  210. - Android/iOS/Linux/Windows version of ioeX P2P network function are
  211. ready.
  212. - Form the personal VPN through ioeX P2P network, creating a private
  213. and secure connection.
  215. **2018 Nov**
  216. - P2P network function incorporates blockchain ledger function to
  217. enable ioeX cryptocurrency reward mechanism.
  218. - Cryptocurrency wallet of ioeX, Alpha version.
  220. **2018 Dec**
  221. - Cryptocurrency wallet of ioeX, Beta version.
  222. - Beta version of OTA upgrade through ioeX P2P network function; more
  223. than 200,000 peer nodes and over 500 bootstrap nodes distributed
  224. throughout Asia, Europe, Americas, and Australia.
  225. ioeX P2P network will begin the project to incorporate IPFS function.
  227. **2019 Jan**
  228. - OTA upgrade through ioeX P2P network function officially released 1st
  229. version.
  230. - All devices can be rewarded.
  232. At the start of 2019, they will plan additional milestones.
  234. # Whitepaper conclusion
  235. Everything is logical and to the point. No big questions for the project. Plenty of illustrations for easy practical understanding how everything will work.
  237. On the downside, there's a lot of repetition in the text — same things explained over and over. Makes the White Paper a bit long and confusing. Some points are hard to fully comprehend. The Taiwan and Chinese versions leave the last two pages completely empty — strange and not professional.
  239. # Questions for the project
  240. Q: "For sealing terms please refer to Appendix 1" Where is this Appendix? Didn't find it in the White Paper.
  242. A:
  244. Q: Will the new updates work a la uTorrent? If not, why? It would speed up upgrading all of the devices without overloading the network.
  246. A:
  248. # Conclusion
  249. Strong team. Their significant experience will play a role, and the project will be useful. The idea itself is quite real. All aspects of making it work are described well in the White Paper (even though confusing at times).
  251. No big problems or questions for the project. Although such a team and infrastructure could do a lot more than mere "IoT updates." So waiting for new ideas and their implementation in 2019.
  253. # Verdict
  254. Not a scam, Approved!
  256. _**Disclaimer:** The above audit is not in any way financial advice or a solicitation to buy - it's merely our collective opinion that we are kind enough to share with you. Don't make us regret that._
  258. **The report is prepared in partnership with**
  260. **Our links:**
  262. -
  263. -
  264. -
  265. -
  266. -
  267. -
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand