My main point is that it's impossible to reconcile your lofty claims about Gun with, frankly, the unreadable mess you have in your repo.
It doesn't matter if your ideas are great. You keep putting Gun forward as a kind of shiny, superior successor to Riak, Cassandra and CouchDB, which I'm afraid only makes you look foolish.
You seem to have done the branding before you did the code. First you need to demonstrate solid, mature code. Then you can try competing with the big boys.
A detailed critique of your code would take a lot of effort, but I've made some notes [1]. I find the code to be unreadable and full of bad code smell. With all the mutation and callbacks and events and what not going on, it's just too hard to tell how the code is intended to flow. I don't see a clean API, even an internal one, nor I see a clean structure. It needs a lot of cleanup [2].
When talking about code, it's rarely just aesthetic. My philosophy is that if one can't even manage the trivially superficial aspects of code (formatting, structuring files, naming variables, and so on), it's not worth talking about its inner workings.
Sorry if this comes across as terribly harsh, but I hope you can see I'm trying to be constructive.
---
[1] A few examples:
* Your code is littered with arbitrary console.log() statements that have no actual utility. They look the kind of temporary logging I insert whenever I need to trace a difficult behaviour.
* No code is documented, aside from childish comments like:
} // IT WORKS!!!!!!
* Lots of what looks like global state.
* Lots of anonymously named variables like r, u, n.
* Big chunks of commented-out code (e.g., in radix.js).
* Lots of what looks like test data. Are you telling me this is part of the project?
rad('user/marknadal', {'#': 'asdf'});
* Lots of mutation. E.g., in s3.js you get some kind of event and then you modify the inputs.
* Syntax formatting is inconsistent and shoddy.
* require() calls in the middle of code.
* You have a test folder, but it's barely got any actual tests. You do have at least one commented-out test in the middle of everything (list.js, line 25).
[2] You may want to look into replacing callbacks with promises, and restructure it using more classical ES6-based OO, as opposed to the prototype-based, lexically-scoped style you're using now.