Justin Kilpatrick |

Althea Development Update #45: Thinking about governance

Now that we’ve had stuff in the field for a few weeks we’re rolling back our focus on shipping new users and instead focusing on polishing our next major revision and including fixes to pitfalls we see affecting our currently live users.

We’ve had some downtime in Clatskanie trying to use a cheap n600 as the gateway infrastructure, I was curious how it would react under prolonged load. The answer is not well, it’s being swapped with an Edgerouter.

Sadly it doesn’t look like the n600’s are going to have a very long shelf life. After extensive debugging I have found their performance issues are due to slow context switching on their single core cpu’s. They simply can’t finish decrypting WireGuard packets fast enough.

We’ve also found some really bizarre WireGuard issues with our Australia test deployment. The backhaul tunnel to the exit server goes on and off every couple of seconds. I think it’s related to packet reordering on the backhaul network if I had to guess. More detailed investigation is in work.

The Claskine deployment will be working on getting their off grid tower deployed and linked into the mesh on Wednesday, I hope to get some cool pictures from that to share with you.

The (in)famous Clatskanie gateway and some other equipment

Way back when we talked about how promising on chain governance was.

You may have seen the drafts floating around the Matrix channels, but it’s essentially a pluggable governance architecture where people can create an administrative system for their local mesh group that raises a fund pool for common works and deals with administrating the local mesh. Exactly what the voting rules and such are is up to the users.

There’s also a global level designed to maintain quality control and direct some funds to the company. Essentially a TCR where you pay to register your deployment for use by our off the shelf devices. It’s a good way to decentralize some of the more closed parts of having a real Althea product on shelves.

It’s a legitimately difficult task to both plan to generate revenue and ensure that the product is still fair and ‘free’ as in freedom to user. It’s a hard balance and I’m sure some people will be upset no matter how we do it. But I’m happy with the one we’re striking.

You’ll see a nice summary and a official spec to comment on once we stop editing half of it every week. Or you can find the in-progress version in our Riot dev channel.


Subscribe to our newsletter!

Related Posts

Althea Development Update #70: Dueling scripts

Put on your night time sunglasses because I have a tale from our cyberpunk future, or present as it may be. How a poorly coded smart contract disrupted an ISP in rural Oregon.

Read More arrow_forward

Althea Development Update #51: Easier debugging in the field

Here’s our Alpha 5 release

Read More arrow_forward