{"resolved":true,"match_type":"uuid","source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","requested_by":"printed_page","book":{"source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","id":"24410bf1-91f1-4e6b-9613-e64f0132d341","uuid":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","normalized_title":"thestackonsoftwareandsovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","isbns":["9780262029575"],"parsed":true,"ai_readable":true,"document_type":"book","page_count":517,"navigation_url":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341","title_url":"https://workshop.closeclaw.top/ai/title/The%20Stack%20On%20Software%20and%20Sovereignty","fixed_page_url_template":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","path_api_url_template":"https://workshop.closeclaw.top/api/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","read_url":"https://workshop.closeclaw.top/api/ai/read/24410bf1-91f1-4e6b-9613-e64f0132d341","page_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/page","search_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/search"},"page":{"printed_page":209,"pdf_page":225,"physical_index":225,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"82055133f2b5c3cf6300c9244acc96d116d36e6e5cd88d47ceff45e78cdf3589"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"$1 0 ^ { 1 3 }$ addresses, and so on. However, it must be said that the full IPv6 address space can enumerate many orders of magnitude fewer items than the possible number of books in Jorge Luis Borges ’ s “ Library of Babel. ” <sup>34</sup> How ubiquitous is the ubiquitous computation? If you were to try to assign an individual address to $1 0 ^ { 2 8 }$ things over the course of your life, you would have to work down to the level of individual molecules, numbering things at a scale below natural perception, doling out addresses for individual letters in books, hairs on heads, blood cells, specks of dust. <sup>35</sup> I was interested in experimenting with that fine granularity, trying to get a picture of it in my mind so that it might be more easily understandable. How small could one “ write ” an IPv6 address? I would need the most fine-tipped writing tools invented to find out. In collaboration with the Nano3 lab at Calit2, we wrote a single IPv6 address (3ffe:1900:4545:3:200:f8ff :fe21:67cf) with an electron lithography beam into a silicon wafer and photographed it with the scanning electron microscope (see the image in the online companion to this chapter). The address in our picture is 10 micrometers in width, about the size of a red blood cell. The lines of each digit are about 50 nanometers in thickness.\n\nBut nano-objectivity is only part of the story. Recall that deep addressability would allow for the identification not only of things with mass but also of relations between things. Once again, each letter in the sentence you are reading right now could have an address, but your act of reading of each one of them, those immaterial relations between two things, it and you, could be addressed as well, and from this graph and set traces proliferate and become techniques of a new geography. One can address both a discrete thing and the abstract reverberating envelope of relations around it that could extend toward infinity. Put differently, deep addressability includes not only discrete entities but also multiple levels of abstraction, as well as the traces of those entities and in turn the abstractions we hold for those — not just addressable nouns but addressable verbs, events, and allegories. While it ’ s unlikely that I could exhaust $1 0 ^ { 2 8 }$ addresses for familiar physical things over the course of my life span, I could easily exhaust that many relations of relations of relations of relations. I could spend all my addresses in an instant of we were to extend relationality all the way down into the abyss. The exhaustion of any full allocation of deep address exists therefore somewhere between never and instantaneously, and the measure of that vast middle ground is essential to the design brief of the Address layer of The Stack. <sup>36</sup> Whereas the traditional Internet of Things situates a network of physical objects, the full Address layer would include all these but also concepts, events, procedures, and memes, addressable at a common level through a generic protocol. <sup>37</sup> While there are real barriers to a global IPv6 implementation, some technological, others economic, and others political, we should assume that for The Stack, some platform for deep address will in time enumerate things and events at a similar or even more granular scale, giving way to disorienting associations between micro- and macrocosmos, linking, delinking, and blurring across natural scales. Besides IPv6, Bitcoin allows for $2 ^ { 2 5 6 }$ possible private keys and $2 ^ { 1 6 0 }$ possible private addresses. Perhaps its hash architecture can be made to not only to map virtual quanta of “ value ” but actual things as well at the scale required by a global economy, or a parallel economy. (Is the “ coin ” the “ address ” and the value in the mesh of addressees? If so then the cost of addressing of anything and everything may be prohibitive without the introduction of some new incentive for settling the blockchain consensus.) All that is solid doesn ’ t melt so much as it becomes fuzzy and spastic. In this, Address layer technologies of universal addressability point not only to assemblages that exist but to the media with which to compose those to come. <sup>38</sup>\n\nAddress Layer\n\n209","previous_page":208,"next_page":210}