Happy new year everyone! Since my last blog post I've managed to implement the alternate network design I proposed. Phone client design proposed in update #79, now implemented and functionalThe major hudles where
2019 has been a key year for Althea. We implemented our billing software and grew our network in Oregon. From there, we launched a training and onboarding program which brought in new network
Android devices as IPv6 mesh network participantsRecently we've been working on a phone client for Althea. Our first design was to have every phone as a Babel node, advertising it's own routes and
It would be great for people to be able to buy a connection directly via their phone. You can’t really compete on price with something people already own.
We are excited to share the latest Althea news! Over the last few months, many of our prospective deployments are getting close to launch, and networks in Tacoma, Washington, and Abuja, Nigeria have
Althea, a system that lets routers pay each other for bandwidth, is launching its first network in Africa in early November 2019. An initial pilot network will start with about 15 participants. A
Since our last update I’ve encountered a couple of bugs where the problem had been hiding in plain sight. In one case for weeks and another for a year or more. Discovering root causes long term subtle bugs is both satisfying and important to create a better product.
The difference between Althea and most networks is that Althea is decentralized and so different members of the public can perform different roles.
Now we're exploring that we can do with multihomed users and connections
Researching market potential is an important part of starting an Althea network. While adding more links to an existing Althea network is relatively easy, setting up that network is similar to starting a
We apply latency control judiciously throughout at every Althea node in the network, with the ultimate goal of fairly allocating bandwidth at any given bottleneck.
A few weeks ago, we started a governance proposal on altheazone4 to vote on the next hard fork. This time, it will be scripted. Read my summary about it here. The proposal passed
what we’ve done in this release is design a fully automated a bridge, the user merely has to deposit ETH and the router takes care of the rest. The money will be exchanged for DAI, then transferred across the cross-blockchain bridge to become Xdai.
On Tuesday, the Althea validators finished a hard fork from altheatest3 to altheatest4.
A minute later when the gateway tried to validate that same payment again it chose the same failed node at random. It wouldn't get a third chance.
We launched the altheatest3 test blockchain. We'll be having a series of collaborative challenges for the validators.
For this development cycle I've focused on building a more advanced and easier to run series of integration tests. As Althea matures the complexity of the average bug to track down, identify and
Up to now, we've been running our networks on the Ethereum blockchain. The reality is that Ethereum simply isn't suitable for our use case. Ethereum's great for manual, medium or high value, sophisticated transactions...
What is a validator and what do I need?We're currently in the process of spinning up the Althea blockchain. We are using Cosmos, a proof of stake blockchain framework. This post is
Networks are made out of more than antennas and ethernet cables. They are homes and business - neighbors - connected to one another. These neighbors can also become relays, forwarding bandwidth to nearby