/r/incentivizedmesh

Photograph via snooOG

In incentivized mesh networks participants work together to route data to it's destination and are paid by other participants to do so.

Concept

Mesh networks have the potential to provide cheaper and more robust internet both in developed and developing countries by having the devices that use the network form the network themselves. Yet they are not in widespread use anywhere in the world.

Mesh networking tends to be difficult to setup, nontrivial to maintain, and most importantly only maintainable through charity. The goal of incentivized mesh networks is to turn that reality on it's head, by making it profitable, secure, and easy to participate building a competitive network for the users by the users.


Ongoing Incentivized Mesh Projects

Althea:

A series of GO scripts designed to allow the user to create a series of paid networking bridges. An independent and payment unaware mesh is then run on top. Currently prototyping, see /r/altheamesh

Hocnet:

A series of modifications to Batman-V designed to create a secure payment aware mesh. Currently somewhere in between conceptualization and prototyping, see /r/hocnet

Scrooge:

An attempt to create a multi function billing daemon. Essentially a universal interface for paid meshes that may work dramatically differently under the hood.


Community

IRC: #incentivized-mesh on Freenode

Matrix: #incentivized-mesh:matrix.org

/r/incentivizedmesh

102 Subscribers

2

Development Update #22: Unicast messaging test • r/hocnet

0 Comments
2017/05/13
12:53 UTC

1

Development Update #20: Switching to Babel • r/hocnet

0 Comments
2017/04/17
22:35 UTC

1

Development Update #19: Countdown to proof of concept • r/hocnet

0 Comments
2017/04/09
11:22 UTC

2

Verifiable metrics and/or non-mesh routing solutions

We've been having trouble finding routing metrics that are verifiable. Verifiable means that there is a way to correlate the metric as propagated by the routing protocol with the metric as measured across an end to end route. For instance, the Batman V protocol uses an algorithm called Minstrel to get throughput estimates. This may be hard to run end-to-end over a route because it is an algorithm that is designed for use from one radio to another.

I still think that it should be possible to have a verifiable packet success metric that can be used in Batman or a protocol like it. But this difficulty got me thinking about not using mesh protocols.

It should be possible to having routing provided by a service or services. I send them my metrics and some money, and they send me good routes. If I don't like their routes, I switch.

The service can then use a variety of protocols, best practice, and manual techniques to keep from having their routes corrupted by cheaters. If I don't like the job they're doing, I can get routes from someone else.

The payment layer would work the same as it does with a secure routing protocol, requiring no changes.

We're still probably going to continue on trying to secure mesh protocols, but this is a direction that could always be possible and maybe good for a quick MVP.

3 Comments
2017/04/06
04:44 UTC

1

Development Update #18: The problems with metrics • r/hocnet

0 Comments
2017/04/02
11:22 UTC

1

Development Update #17: Finally in userland • r/hocnet

0 Comments
2017/03/18
17:11 UTC

1

Development Update #16: Netlink callback functions in progress • r/hocnet

0 Comments
2017/02/28
23:14 UTC

1

Development Update #15: Working Netlink definitions • r/hocnet

0 Comments
2017/02/21
21:00 UTC

1

Development Update #14: Kernel level ipc is no fun • /r/hocnet

0 Comments
2017/02/13
00:34 UTC

2

Development Update #13: Netlink and Scrooge integration research • /r/hocnet

0 Comments
2017/02/05
23:19 UTC

1

Development Update #12: OGM signing and signature verification • /r/hocnet

0 Comments
2017/01/29
22:55 UTC

1

Development Update #11: Real development begins • /r/hocnet

0 Comments
2017/01/22
21:08 UTC

2

Hello World

So /u/rusticscentedmale and I have made this subreddit as a neutral space to talk about what we're calling incentivized mesh protocols, or any mesh network where people are paid to participate.

You can look at the sidebar for our respective projects and some channels to collaborate in. Our hope is that by getting together and working together we can avoid duplicating work and help each other solve problems, even if its just with rubber duck protocol design.


To that end we announce the Scrooge project, which has the goal of providing a mesh agnostic way to handle payments and other incentive related protocol components.

There isn't entirely a clear vision on what that means yet, but this is born out of Rustic and I noticing that our plans for payment where more similar in their requirements and restrictions than they where different, with the real differences fairly easy to put behind a layer of abstraction, hopefully letting us save some work and maybe even keep a single familiar interface for users of both of our protocols in the future.

6 Comments
2017/01/15
23:10 UTC

3

Development Update #10: And suddenly there was community • /r/hocnet

0 Comments
2017/01/15
23:04 UTC

Back To Top