The Arduino board MKR1310 is the new revision of the MKR1300 board dedicated to LoRaWan. This board is a SAMD21 Arduino board with a Murata ABZ module based on a STM32 with an SX1276 transceiver. Basically a bit outdated and expensive modem now.
After using this board for some teaching project, it’s a good time to make a feedback about it as many things need to be improved on that board to get benefit of it.
Continue reading
Many different crypto project are running decentralized computing as it’s a good piece to complete the distributed storage or messaging I previously documented. The principle is to be able to deploy a workload on someone else computed to serve a reliable web service. This layer is a IaaS layer like we can find on Azure, Aws, GCP, Ovh… This layer is an important piece of a decentralized cloud in construction in the web3.
In this blog post, I’ll review some of the projects like Flux or Golem and explain how to be part and use the one that seems the more reliable. As there are many different solutions and it has been a bit long to test all and publish them in a single blog post, this will be split into different one. The first one is about Akash.
Continue reading
Many different crypto project are running decentralized computing as it’s a good piece to complete the distributed storage or messaging I previously documented. The principle is to be able to deploy a workload on someone else computed to serve a reliable web service. This layer is a IaaS layer like we can find on Azure, Aws, GCP, Ovh… This layer is an important piece of a decentralized cloud in construction in the web3.
In this blog post, I’ll review some of the projects and explain how to be part and use the one that seems the more reliable. As there are many different solutions and it has been a bit long to test all and publish them in a single blog post, this will be split into different one. The first one is about GOLEM.
Continue reading
Many different crypto projects are running decentralized computing as it’s a good piece to complete the distributed storage or messaging I previously documented. The principle is to be able to deploy a workload on someone else computed to serve a reliable web service. This layer is a IaaS or CaaS layer like we can find on Azure, Aws, GCP, Ovh… This layer is an important piece of a decentralized cloud in construction in the web3.
In this blog post, I’ll review some of the projects and explain how to be part and use the one that seems the more reliable. As there are many different solutions and it has been a bit long to test all and publish them in a single blog post, this will be split into different one. The first one is about FLUX.
Continue reading
There are some domains where web3 application are promising. I already explored storj solution to store data and as a user point of view, it has convinced me. Now, I’m exploring the capabilities proposed by Streamr Network. This project has started in 2017 and still improving its development roadmap. It proposed publish & subscribe solution for standard protocols like MQTT, HTTP, Websockets. By design the solution is scalable and reliable. It currently has more than 4000 online nodes. The project will also propose a marketplace where to purchase data by subscribing to flows.
This blog post will detail my experience with this project and will be updated all along my usage of it, as miner and also as user.
Continue reading
Some time ago, a twitter thread made the community react about the amount of $6600 of communications consumption on the Helium network. This thread was full of approximations in order to present negatively the growth of the Helium network. But it is also an opportunity to take stock of the development of the use of the network. We will see in this article who operates the Helium decentralized network, what are the current data volumes and what are the associated financial metrics.
In short, we cannot talk about Nova Labs’ revenue with respect to direct communication costs because these costs are associated with different third parties offering the packet routing service. We cannot rely on this cost to estimate an associated business volume because there are many indirect costs as I have already specified in my blog post analyzing the running costs of a Helium router/console. Finally, regarding a long period where gamers found a way to earn a few dollars on the back of Nova Labs, involving many ancillary costs, distorted the data for June. You will understand all this in the rest of the article.
Disclaimer: I’m the owner of the public helium console helium-iot.eu (oui 6) – no need to makes comment like “he have written this because he own … blablabla”
Continue reading
The HIP-51 (Helium Improvement Proposal #51) starts a new way for Helium network. When it has started about 2 years ago, Helium has been designed to propose a global LoRaWan network. But, has I explained at the beginning of this journey, it’s not just a network, its the uberization of the telecom industry. In other words, once you find a good way to transform an industry, there is no reason to just transform on of its services, better is to transform all.
Telecom are not single network, they have IoT networks with LoRaWAN, NB-IoT, LTE-M, they have some WiFi services and 4G/5G services. The HIP-51 is basically a way to go that multi-service direction to compete with telecom industry.
I’ll detail in this post the way this is working (as much as I understood it, reading the HIP-51 currently under vote), and try to explain what will be the impact on the network and tokens.
Continue reading
The Helium router (aka console) is the LoRaWan network server. In a previous post I described how to setup a Helium router / console. In this post I will give you some details of what you can see in the grafana monitoring dashboard and this will help you to understand better how the network works to process the LoRaWan packets. We are going to detail what is an offer, a packet and the different monitoring information we can get from the router.
Continue reading