Urbit Valuation Papers

# Place the cursor inside "graph" to get some refactoring options digraph { graph [label="\n4-Dimensional Design"] 3 [label="Model"] 2 [label="Relationship"] 1 [label="Federation"] 4 [label="Complexity"] 5 [label="ICANN"] 6 [label="Analogy"] 7 [label="Abstraction"] 8 [label="simulation"] 9 [label="emulation"] 10 [label="exhibition"] 11 [label="ubu"] 12 [label=""] BLAN 1->7 5->1 1->2 2->3 3->4 }

The advantage of Urbit is that it makes web 3 work. The disadvantage is that it tends to obscure what the web really means: like the museum, Urbit is an interpreter with no transient state.

A language oriented programming environment. Data, networking and identity happen on an axis with reading and writing in public as the motivating axis.

Here domain is identity. Names are administered by ICANN, then FedWiki project, and independent open-source projects along further branches through to the leaves.

are mutually independent.

"Referential transparency is honesty and stability. [..] It's only a small stretch to say that 'Urbit' is this set of principles, and that if anybody follows these principles strictly they will create a system that is isomorphic to the Urbit."

Though this whitepaper has been produced by a single individual, we write in the second person to facilitate the contexts for language's reuse.

We draw on sources recent and past to secure our findings.

unfinished