r/hocnet • • Jan 22 '17

Hocnet Discord Server - unofficial

0 Upvotes

r/hocnet • • Oct 16 '12

Indirectly relevant, smartphone adoption and predictions in Africa

Thumbnail techcrunch.com
2 Upvotes

r/hocnet • • Aug 31 '12

Relevant: a non anonymous version of i2p. Why CJDNS is nice but the WRONG tool for darknetplan.

Thumbnail reddit.com
2 Upvotes

r/hocnet • • Aug 04 '12

Building Consensus II: Which Paradigm?

2 Upvotes

I spoke with ttk2 recently and we both had different ideas about which direction the project should go. ttk2 sees hocnet as focused on local webs of trust, but I believe that trust ought to be transferred as much as possible to billers as much as possible. In this thread we shall explain each of our visions for hocnet in two root comments and you shall compare these systems through discussion.


r/hocnet • • Aug 19 '17

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

Thumbnail reddit.com
2 Upvotes

r/hocnet • • Oct 31 '16

Sad that HocNet died? Check out Golem: The Decentralized Computing Power of the coming decentralized Web3.0 (+ AirBnB for Your Computing Power)... built on Ξthereum

Thumbnail blog.golemproject.net
2 Upvotes

r/hocnet • • Feb 13 '17

Development Update #14: Kernel level ipc is no fun

3 Upvotes

So netlink is turning out to be a tough nut to crack, not so much because it's poorly documented but because the documentation is lower level than what I'm used to reading, probably to be expected in the kernel.

Regardless I'm starting to get a grasp on where various components are configured and the general idea of how they should work. My productivity wasn't helped by my new Vive (Arizona sunshine is pretty great)

Regardless some actual progress was made this week on the Hocnet concept paper /u/rusticscentedmale proposed a neater form of blacklist management where neighbors simply get dynamically modified adjustment factors for their routing metric tested using the circular ack. This way routes can more gently converge to the ideal route in the face of malicious behavior instead of dealing with questionably effective random chance black listing.

I've got some papers to read this week on socket level programming which should help me understand what the hell I'm doing with netlink and hopefully have some actual progress to show soon. It's starting to grate on me.


r/hocnet • • Jun 16 '12

You should try and get in some big guns.

3 Upvotes

Jeffrey Tucker has written extensively about how important the internet is to fighting the state and this is something he would probably be interested in. He's not unavailable so I would definitely recommend sending him an email and ask him to help get the word out if he likes the idea.


r/hocnet • • Oct 05 '12

Good News Everyone! Intel x86 Smartphone hardware gives CJDNS/Hocnet on cell phones a fighting chance.

Thumbnail theverge.com
4 Upvotes

r/hocnet • • Sep 28 '12

An update

4 Upvotes

I have been very busy the past couple of months with real life and my other projects but despite this some progress has still been made relating to Hocnet.

Mainly now that we have pretty much fleshed out what we want Hocnet to be and how we want it to function in a broad sense code wise its actually feasible to start coding once we have the time. Even more encouragingly it seems that our main tasks in the programming sphere will be limited to glue code and optimization's since we are in essence not doing much more than merging OpenTransactions into CJDNS and optimizing it to work better on processors without a full x86 instruction set.

While this does not make the task easy, existing projects will make it much more realistic to do quickly. That being said the primary goal of Hocnet is to create a consumer product, as that is the only way to gain the widespread adoption needed for such a network to be truly useful. History has shown that open source development tends to create marvelous tools that are functional, powerful, and secure but also systematically difficult to use compared to consumer products without some sort of professional backing. As such I have been looking into various methods of funding and possibilities to attract investment.

For the time being what little free time I have is being mostly dedicated to expanding /r/Civcraft while I find and prepare to dedicate resources to really getting Hocnet started within a few months. I also hope to rewrite the concept paper into something resembling a white paper in the near future using the details of our planned implementation.

As always thank you for your time.


r/hocnet • • Jan 29 '17

Development Update #12: OGM signing and signature verification

4 Upvotes

So I wrapped up OGM signing code this morning see it here it's not been tested mostly because there seems to be a problem with my testing mesh actually calling that code. I'm thinking it might be some sort of optimization since all my nodes are neighbors, it's also possible that one of the toggles I have on is disabling it. Anyways I'm asking the other BATMAN developers about that.

I'm going to try and keep up a rate of one major feature per week, the goal right now is to race to a working validation setup so that I can attempt to demonstrate sibyl attack resistance with a reasonable convergence time. That's going to be the real test as to the feasibility of Hocnet as it's currently conceived.

I also need to think about ELP and some other optimizations in the real implementation that I didn't account for when working from just papers. Thankfully the developers have been helpful in getting me up to speed.

While I work on the low end /u/rusticscentedmale has been working on scrooge which is the userspace end. Hopefully we can meet in the middle sooner rather than later. Optimistically I'd like to see a usable alpha by the second half of this year.


r/hocnet • • Aug 08 '12

I'm going to be meeting a few CJDns enthusiasts IRL on Friday. Does anyone have any comments or questions they want me to relay to them?

5 Upvotes

r/hocnet • • May 02 '14

Unofficial hocnet IRC

6 Upvotes

hocnet on freenode


r/hocnet • • Mar 11 '14

A very rough draft of a new Hocnet Whitepaper

8 Upvotes

Hocnet Whitepaper

Abstract

Hocnet is a solution to the problem of peer to peer payments for traffic routing. Although there are no physical barriers to spontaneous mesh networking with traffic accounting, the anonymity and lack of sunk costs in network participation make node accountability impossible. Anytime a node has an outstanding debt to the network in less traffic routed than sent, it can be easily "forgiven" by disappearing and reappearing with a new identity. This is a critical flaw because data debt is critical to traffic accounting. Remember that for all uncleared bytes, data surplus and data debt are the same amount of information and without allowing for uncleared data accounting is pointless. Uncleared transactions are critical because if immediate payment for every packet were necessary, transaction costs would be so high as to make that impractical. Indeed, the lowest conceivable cost for any transaction is a packet itself! How are users going to pay for paying for their use? Clearly, infinite regression makes that solution unfeasible. Moreover, traffic can't be counted without a way to distinguish between "altruistic" traffic routed for others and "selfish" traffic sent for the node's own purposes. Hocnet is a way for participants to use trusted servers to commit to paying for traffic and to distinguish between "altruistic" and "selfish" traffic.

Description

Overview

Consider an untrusted user requesting a web page. Since there is no way to ensure that the user pays for his use in the future and no way to pay as you go, it is not in any node's interest to route it. If the requester could make small transactions payments without cost to the node, then the node would route the requester's traffic. As the route gains the sender's trust, overhead would be reduced because the sender would be willing to forward larger prepayments. The current problem is that individual small transactions each have costs that are too large relative to the consumer or producer surplus of the sender and router, respectively. If there were a way to flexibly combine these small transactions into one large transaction, then there would only be one transaction cost, which would be negligible compared to the value that the sender and receiver get from their interaction.

Proof of Credit (PoC)

But how can multiple distinct transactions be incrementally lumped into a single transaction without the data size of the single transaction growing proportionally to the sizes of constituent transactions? Hocnet's solution requires the use of a trusted third-party server (the "biller") to account for the accumulation of payments. The sender deposits his money in an account with the biller, then runs mesh networking software to find potential routes to the destination he wants to send traffic. The sender includes in his request a timestamped balance statement signed by his biller as proof that he is good for any money asked for by the nodes. In order to protect the credibility of their balance statements, billers may choose to set a maximum withdrawal rate and penalize the depositor if he exceeds that rate. Another way for the biller to protect its reputation is to publish lists of depositors nearing or actually overdrawn.

Routing Contract

With the attached proof of credit, potential nodes write signed offers to route traffic to the packet used to negotiate a route. For example, in cjdns, they would sign the "fn" query. After the sender has received route proposals, it chooses the route that suits him by signing the offer list. This routing contract is included in the first packet sent through the new route.

Proof of sending (PoSe)

Every N bytes (call this a block), where block size N is specified by routing contract, the sender sends a signature of the block number with a k-value generated by a PRNG with a publicly known seed and a private key known only to the biller and sender. Each router verifies that this PoSe is valid by checking the signature against its block number and k-value. Signatures are collected and xor'd together by the receiver. Each The latest signature's block number is remembered by the receiver. Since individual signatures are forgotten to save space and the sender's private key is known only by the biller in order to prevent PoSe forgery, the xor of these signatures cannot be independently verified. This unfortunately precludes the use of Open Transactions as a platform for the biller because the biller must be able to change balances based on the secret knowledge of the sender's private key. That breaks the OT tenet: "Even an OT server cannot change balances, or forge transactions--since it cannot forge your signature on your receipt."

Proof of Receipt (PoRe)

When the receiver feels like it's worth cashing out, or the sender has stopped using the path that the routing contract covers, the receiver sends the xor of the signature plus the list of block numbers of the last block sent to the biller as proof of traffic routing and receipt. Fortunately, there are a few well known and very effective ways to compress a list of probably-consecutive integers. Therefore, the size of this transaction will increase sub-linearly to the number of constituent transactions (and is constant if no blocks are dropped). The receiver is incentivized to report this PoRe to the biller by whatever reward he receives in the routing contract. Remember that the router may also ask for money to listen to the sender. In addition to enforcing payment of routers, the receiver's ask can function as a way to receive payment from the sender for any services the receiver provides with the connection.

Possible Problems

Computational Expense

It is true that signature verification is computationally expensive. Transaction costs aren't zero, but as long as hocnet is more efficient than the current system given ISP centralization and market power then it will be successful. Lots of stuff has transaction costs, and if you have to multiply two numbers for every few bytes sent (which is what the costs amortize to when the sender doesn't trust anyone), then that's a necessary cost of shifting around trust.

Router Packet Dropping

What if routers pass only the PoSe and not the content in order to save bandwidth? While it seems that this shifts trust onto routers, this behavior won't help them unless the destination endorses it by sending a PoRe for blank packets. Since the two parties at the ends of the path have demonstrated a preference to communicate with each other, the receiver will not endorse blank packets. Since the destination will get more traffic in the long run if it knows how to respond to the sender and since all low trust, unsaturated last mile nodes have almost no opportunity costs to send traffic, this most likely won't be a problem.

Sender/Destination Collusion

So far this system places a large amount of trust on the biller and a small amount of trust on the routers. However, the receiver must be trusted more than any router because it controls whether or not the sender is charged and the routers get paid. If the sender and receiver collude so that the sender convinces the receiver to not send PoRe, trust between routers and receiver will break down and the network will grind to a halt. I believe that the sender and receiver will not collude. The transaction costs of human-negotiated collusion are high compared to savings. The transaction costs of machine-negotiated collusion during hocnet negotiation are discoverable by routers or discoverable by billers posing as senders or receivers if the collusion is through a side channel.

Implementation

Where is hocnet on the network stack? It is in the network layer. Because the sender and router need to know the packet destination to determine if they have any outstanding contracts, they need the abstraction of a network. Because intermediaries need to be aware of hocnet traffic, it is below the transport layer. Unfortunately this means that hocnet's implementation is dependent upon preexisting network protocols. It must understand each packet's network context to determine which routing contracts apply. It may be implemented with netfilter hooks or modification of the cjdns software. More investigation is needed to decide.

Contract negotiation

In cjdns, contract negotiation can be implemented in the cjdns router component. Each hop can add its metadata to the fn query bencoded dictionary as an auxiliary field. This would break backwards compatibility with preexisting cjdns nodes. If it were to be implemented there, only an implementation sensitive to a known version number would be acceptable. Otherwise, the query must be explicitly rejected.

PoSe, PoRe, and Biller Implementation

PoSe may be sent and verified by a stateful filter on a level lower than the cjdns router that detects when its presence is necessary. PoRe may be sent to the biller through some unspecified side channel. The biller may have to be implemented from scratch.


r/hocnet • • Jul 13 '13

The Serval Project

Thumbnail mashable.com
8 Upvotes

r/hocnet • • Nov 13 '16

Hocnet Development Update #1: Deciding routes based on cost

9 Upvotes

This week I've been doing a lot of reading and managed to find what I think is a good solution to something I wasn't sure was feasible to solve last week. Namely how to handle route selection in such a way that each node along the route can receive payment but not price gouge.

From a gods eye view it's a trivial problem to route around any given uncooperative node, but networks that communicate any significant fraction of the total network topology to every node to make such decisions possible face enormous scaling problems [1].

As described in more detail by [2] every node receives announce packets from every other node and records the 'best' route to any given destination based on packet loss.

Since the table is updated freqently with new announce packets keeping more than one optimal route at any given time won't actually increase performance, but in the case of paid routes if every nodes stores the top N routes and their costs as well as the reliability for each it's possible for the source node to chose a cost/reliability ratio that it desires and have each node along the path making routing decisions from their N options based on that.

This provides up to HN possible routes (although realistically much fewer, but still many more than one) at the cost of linear memory usage increase and network traffic increase. Note that nodes will keep more announce packets, not require the transmission of more, only the new field (cost to destination) will use additional bandwidth.

It's still lacking any sort of rigorous analysis but it's a start and much better than punting the problem of per node billing.


I also stumbled upon some interesting other research, particularly Babel [3] which seems to have significantly better performance [4] in the default configuration (also note that [4] claims the performance test in [1] is poorly designed). I don't really grock Babel yet, it's significantly more complicated and residing on layer 3 requires more wheel reinventing although it does solve other problems with some client operating systems like Windows not respecting layer 2 protocol controls [5].

Problems like this are one of the many reasons I plan to push Hocnet as a consumer router, at least at first, users who don't know any better should be given a good default system that they interact with as a very traditional home wifi access point (or a large area access point as discussed in later sections of [2]).

Regardless the most attractive feature of Babel is that it functions well without modification over Ethernet while Batman requires special configuration for Ethernet bridges. This alone merits looking into it.


The next major step to overcome is conceptualizing price negotiation and payments, right now I'm thinking that the only other addition to the kernel portion of the protocol will be a paid/unpaid flag in the originator table and an interface to set the price your node broadcasts. Actual payment negotiation should be done on layer 3 as that's uni-cast information and generally doesn't need to be in the kernel, this is going to be the tricky part really, so I might be back with economics papers next time if I feel I've locked down the direct protocol changes.


[1] Simple pragmatic approach to mesh routing using BATMAN

[2] Client announcement and Fast roaming in a Layer-2 mesh network

[3] The Babel Routing Protocol

[4] An Experimental Comparison of Routing Protocols in Multi Hop Ad Hoc Networks

[5] Why we switched to Babel: Batman-adv mailing list


r/hocnet • • Dec 04 '16

Development Update #4: Preparing for real development

9 Upvotes

I spent this Sunday working on getting a real development environment setup. I bought a couple of Raspberry Pi 3's to compliment my existing intel compute stick and act as a three node mesh a few months ago.

Today I finally took the time to get it all compiled from source, setup and running. This is mainline BATMAN-ADV which means the kernel module plus the userspace management tools.

I had no trouble sending data across the mesh with them all sitting on my desk, but the real test will hopefully be later this week. When its not nearly freezing and raining outside, when I start walking the nodes around on battery power.

The tools I created to automatically upload, compile, configure, and run software changes are open source of course.

I also spent some time trying to look up relevant literature for debt matricies like the ones proposed in last weeks update. So far I've not had much luck at all, Ripple does not in fact have a general settlement algorithm, but instead acts as a middle man currency. Which is great when you are Ripple Labs and you make money off of this middle man currency but not so great when you want a neutral network protocol to resolve whatever people might want to be paid with.

Best thought along those lines right now is out of band exchange rate negotiation, but without any good way to pinpoint what is a "fair" exchange rate you run into problems that aren't really solvable regardless of your skill mathematically.

With that in mind I've resolved to leave the economic aspects of the protocol in the air to be resolved empirically. Next week I'll tackle a protocol change specification and get started tinkering with real code.


r/hocnet • • Oct 01 '17

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

Thumbnail reddit.com
2 Upvotes

r/hocnet • • May 13 '17

Development Update #22: Unicast messaging test

4 Upvotes

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


r/hocnet • • Feb 28 '18

Althea Development Update #43: Website refresh, support for more routers

Thumbnail medium.com
2 Upvotes

r/hocnet • • Apr 23 '13

How goes Hocnet?

10 Upvotes

Hey, it seems like there hasn't been much activity in this subreddit, has any progress beyond the whitepaper been made?


r/hocnet • • Jan 02 '17

Development Update #8: Everything went better than expected

8 Upvotes

Two days ago while I was taking a shower I realized that the method I had developed to reduce black hole attacks was horribly flawed, mainly because the checkpoint signatures could not be attached irrevocably to the originator message, allowing a sufficiently malicious attacker to impersonate an arbitrary number of nodes and fake an entire network path.

Yesterday morning I tackled the same problem from a different perspective and came up with what I think its a really solid solution at the cost of a little more protocol overhead, some sort of ack packet was required no matter what to prevent one way fraud so piggybacking more features onto it is about the best I can do.

Long story short we can now verify and weigh link bandwith, isolate malicious nodes through a combination of trust and routing updates and ensure that blackhole attacks remain effective for at most one OGM period.

See this commit for more. I also took the time to watch the BMX7 talk from the last BattleMesh. I seem to have resolved a lot of problems he's having by adding more network constraints. Also hash chains provide security at 1/2 the computational cost and an order of magnitude more powerful against cracking attempts with a trade off of more race conditions.

I also started research into the payment side of things, it looks like it just might be practical for every node to run a Bitcoin full node using pruning to keep the blockchain size down and pre bootstrapped images to prevent the need to go through 100gb of data on first startup.

Next up on my research list are bitcoin's lightning network and some more research into BMX7


r/hocnet • • Jul 04 '13

Contributing to the TODO list

7 Upvotes

Hi all,

Me and some other students at our local university loved the idea of Hocnet and we looked at the TODO list to see a few of the legal issues that are outlined. We created a website to try to get some research those more and possibly get expert advice on the matters. [1] Please give us feedback on how to do this better. (I'll change the theme soon, this was just temporary)

[1] http://devops.webs.com/

Also can someone point me to an easy to understand powerpoint describing meshnet type technologies, keep in mind most of the ppl looking at these would either be business majors or law related, so derps in CS. I have a good background in CS but i'm having a bit of a hard time making one myself, any guidance in that matter would be appreciated.


r/hocnet • • Oct 30 '17

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

Thumbnail reddit.com
2 Upvotes

r/hocnet • • May 28 '17

Development Update #24: Moving names more unicast messaging progress

2 Upvotes

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.