Bytes.io — Beta release Further to the we published earlier this month, here is a full debrief of our progress developing , with two small demos and some prediction of what is to come next. teaser Bytes Since the , we have split our team in two. One half specialises on the building of an based . This is a Linux + JavaScript stack ( ). The other half of the team is working exclusively on our . Alpha release IOTA IoT Internet access trading stack JS is great for IoT too beautiful mobile app Intro: What is Bytes? offers a platform for . means we are not substituting ourselves to regular , and means the trade is not intermediated. Bytes last mile, distributed, Internet access trading Last mile ISPs distributed in processing or enforcing the transaction, the transaction is processed via the blockchain and the users match based on vicinity (30 meters radius). This is completely P2P (Peer to Peer). No third party is involved not even ourselves: Having a platform for last mile, distributed, Internet access trading enables to: by enabling locals to sell their excess Internet access to travellers (we will make sure this is compliant) — when was the last time you used up your 100GB monthly limit? Do away with roaming . Indeed, connecting billions of machines to the Internet is nearly impossible for today’s centralised offerings. A distributed, programmable payment stack is needed. (or “Things” in the IoT parlance) Enable machines to transact with one another IoT Stack We have built a solution that enables IoT devices to sell Internet access one to another in a distributed way. We used Raspberry Pis (RPis) to simulate an IoT cluster. Goals The two requirements for our IoT stacks were that: The solution , and runs on Linux The solution has a . pure P2P architecture It is for at least two reasons. developed on a Linux platform First, , and as far as network applications are concerned, Linux is the favoured Operating System . Embedded devices mostly use Linux distributions Implementation We used Linux’ network utilities, , and . Electron enables to build desktop applications with JavaScript. IOTA.js Electron Using Electron means we do not need a webserver to host the dashboard, which enables us to maintain a fully distributed architecture. There is no server to cause delays, so everything gets done a bit faster. You can see how this works in below. 2 RPis, each with its own IOTA seed, controlled via an Electron dashboard interact: one sells Internet access to the other. the demo video Mobile Application Here are the main improvement over our last iteration: A completely , leading to a (remark how the Blockchain is abstracted away), redesigned UI seamless UX the user is now able (viz. ) to top up / withdraw in cryptos mIOTA the user is now able to (on community request): there are now two parameters: , . Say Alice sells Internet to Bob. The transaction will now only take place if the of Alice is no more than the of Bob. set the price / minute max buying price min selling price min selling price max buying price As well as some graceful error handling (in particular for those nasty thread & network related bugs). Click if you prefer long, slow and detailed videos. here Conclusion There was a between the version and this iteration… the pace at which we develop is about to accelerate even more! huge jump alpha by users. In parallel, we will look for stack…. Last: We are hiring! Our main goal is going to be the adoption of the mobile app partnership linked to use cases for our IoT

IOTA

Stacks

YouTube

Too Long; Didn't Read

Discover Saakuru: Web3 Mass-Adoption with 0-FEES

Bytes.io — Beta release

Too Long; Didn't Read

Company Mentioned

Coins Mentioned

Bytes Team

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Bytes.io — Beta release

Too Long; Didn't Read

Company Mentioned

Coins Mentioned

Bytes Team

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES