/r/hocnet

Photograph via snooOG

Hocnet is a concept for a competitively decentralized internet, solving the scaling problems of mesh networks through competitive interchangeable centralization that is not a threat to the decentralized nature of the network. Hocnet is designed so that everyone pays for what they use and anyone willing to provide a service to the network will make a profit.

This project has merged with /r/altheamesh

Hocnet is a concept for a competitively decentralized internet, solving the scaling problems of mesh networks through competitive interchangeable centralization that is not a threat to the decentralized nature of the network. Hocnet is designed so that everyone pays for what they use and anyone willing to provide a service to the network will make a profit.

In progress whitepaper

code


Community

IRC: #hocnet on Freenode

Matrix: #hocnet:matrix.org


Other Projects

/r/incentivizedmesh

/r/altheamesh

/r/hocnet

1,235 Subscribers

3

Building a net Generation ISP: Getting what you pay for

0 Comments
2019/07/13
12:58 UTC

1

Building a net generation ISP: Community Connections

0 Comments
2019/07/05
12:22 UTC

2

Building a net generation ISP: The CoDel revolution

0 Comments
2019/07/03
18:54 UTC

3

Cascadian MeshNet's off grid Althea tower • r/darknetplan

0 Comments
2018/04/07
17:45 UTC

1

First Althea alpha devices awaiting programming

1 Comment
2018/01/01
23:06 UTC

1

Development Update #39: Putting together a MVP firmware • r/altheamesh

0 Comments
2018/01/01
23:05 UTC

7

Hi, do you need help from (mostly) non-technical people yet?

3 Comments
2017/12/18
02:51 UTC

2

Development Update #38: Assigning ip addresses and firmware tuning • r/altheamesh

0 Comments
2017/12/10
22:21 UTC

1

Development Update #37: Firmware and Daemon building gets started in earnest, Net Neutrality • r/altheamesh

0 Comments
2017/11/27
00:02 UTC

2

Development Update #35: Mozfest and supporting the unsupportable • r/altheamesh

0 Comments
2017/10/30
16:39 UTC

2

Development Update #34: Rightmesh comparison, Mozfest prep, and full path RTT implementation • r/altheamesh

0 Comments
2017/10/14
20:09 UTC

2

Development Update #33: Writing up RFC's for Babel extensions • r/altheamesh

0 Comments
2017/10/01
18:15 UTC

4

Development Update #32: Moving to transmitting only verifiable metrics • r/altheamesh

0 Comments
2017/09/17
19:11 UTC

2

Development Update #31: Evolving the demo network into a real test network • r/altheamesh

0 Comments
2017/09/04
14:08 UTC

2

Development Update #30: A fun toy and some experiments • r/altheamesh

0 Comments
2017/08/19
22:29 UTC

5

Development Update #29: Diving into Rust, MozFest • r/altheamesh

0 Comments
2017/08/06
15:52 UTC

2

Development Update #28: Remote verification is a go • r/altheamesh

0 Comments
2017/07/30
13:27 UTC

6

Development Update #27: Price based routing V1 complete • r/altheamesh

0 Comments
2017/07/16
14:42 UTC

3

Development Update #26: Tunnels in Tunnels handling secure traffic • r/altheamesh

0 Comments
2017/06/25
12:10 UTC

2

Development Update #25: Subnets, routing and threat models • r/altheamesh

0 Comments
2017/06/04
13:54 UTC

2

Development Update #24: Moving names more unicast messaging progress

So after some discussion /u/rusticscentedmale and I have decided to standardize on Althea as our project name.

We considered a lot of names, Hocnet is technically incorrect (and it follows that if technically correct is the best kind of correct technically incorrect is the worst kind of incorrect) not to mention difficult to talk about (is it Hawknet or Hocnet) making SEO difficult. We also ran through lots of other names I really liked Obol (coins used to pay Charon to ferry you across the river styx) but that didn't work out either, even though we did encounter the worlds must overengineered bowl in the process of researching that one.

Regardless from here on our I'll probably post updates over there. Or maybe just crosspost.

Regardless onto the actual progress for the last week, last weekend I realized that the code i wrote was about ten times as complicated as it needed to be and I made another attempt this weekend with much simplified code, good news is that it worked pretty much right away, bad news is that it seems to have revealed some issues with our testing environment and the way routes are published. So the next hangup is improving that, somehow even though the nodes are assigned ipv4 addresses they are actually operating over ipv6 and the ipv4 addresses aren't routable, meaning while we can hear advertisements by virtue of the way route advertisement works trying to send packets runs into the fact that no such routing table entry in the local kernel table exists. This probably has to do with the way we simulate many routing tables on one machine.

My attempts to get my RPI's to cooperate and make a physical testing mesh have also failed, I'm not sure if it's a setup issue or a firmware issue. I'm going to have to ask around.

I'm getting much better at working with this code and I think we can start to rely on faster changes and quicker improvements. Hopefully this means a viable demo in the coming months and a workable system by EOY.

1 Comment
2017/05/28
22:03 UTC

3

Development Update #23: Pointers and packets

So in the process of getting a testing script up for my code I realized that most of what I previously wrote shouldn't be required and I was over-complicating the problem quite a bit.

I think I have a better structure now and it actually seems to be sending packets, but these packets cause babel to crash, probably because they are malformed or the loop I'm using to send them is doing bad things to pointers. More formal debugging will come later this weekend.

In the meantime /u/rusticscentedmale has been focusing on handling our sybil attack and node trust problem for our theory paper. It's looking pretty solid at this point but I'll leave it to him to talk about that.

0 Comments
2017/05/20
18:36 UTC

3

Development Update #22: Unicast messaging test

So last weekend before heading out for a conference this week I wrote up what I think should work as a multihop hello system [0]. Right now I'm looking into how to test it exactly and setting up a decent CI script for it. Once that's done we can move on to verification and expanding whatever CI we make to test convergence in the face of dishonest nodes.

Babel really is hugely easier to work with just because userspace is more familiar, even if it does bring a whole new set of problems based on the fact that we don't see every passing packet. We've found good solutions to get around those problems and frankly this is much easier to secure than Batman-adv which is well designed but not setup to handle being exposed to hostile attackers, as opposed to linux routing tables which are very secure and widely used.

[0] https://github.com/incentivized-mesh-infrastructure/babeld/tree/multihop-hello

1 Comment
2017/05/13
12:52 UTC

Back To Top