Thread by @BrianOBeirne1

1/ Hey man, thanks for watching my vids. I see this question a lot, so I’ve put together a more in-depth answer for anyone currently researching @Conste11ation $DAG. Feel free to share. Here's my view on how the @dodsbir & #USAF will utilize the #Hypergraph and $DAG

https://twitter.com/JeromeVdv1/status/1658163457533915156

2/ While the @dodsbir et al may currently be running a private instance of the #Hypergraph code base (Tessellation) to optimize data flows on their infrastructure (without deploying $DAG), this is extremely unlikely to persist in the long term for two reasons.

3/ First, the purpose of the #Hypergraph is to collect, validate and transmit data. It does this, inter alia, through edge computing & data locality. If the DOD were to ultimately run a separate private network, this would mean they would need to own the devices "at the edge".

4/ But this begs the question: where is the edge? i.e., how could they know in advance what devices they need to own? Remember, the purpose of networks is to communicate, and the purpose of communication is to inform the communicating parties...

5/ But if you already know – or believe you already know – the who, what, when, where and why associated with the communication, then you have hamstrung yourself with respect to any inputs and contexts that fall outside your preconceived idea of what is needed... see the problem?

6/ Recall that information (“entropy”) is by definition “surprise” (@ScandalOfMoney), which means the goal of a network is actually *to be in a position to be surprised*. But the only way you can be in such a position is if the network and its endpoints are open ("generative").

7/ This means it must be a public network. And this means the DOD – because they obviously want to maximize their ability to collect and transmit data - must ultimately want to be part of the public network, even if they haven’t realized that yet (which I doubt).

8/ Second, let’s say arguendo, despite the foregoing, the DOD decide to run their own private network. No matter how powerful their computing resources, they will never be as powerful as a network that can source computational resources from the public.

9/ This is textbook generative economics. the #Hypergraph is the most powerful communications network on earth because it harnesses the latent computational resources (memory, processing power, etc) of all connected devices and redistributes them via a free market mechanism.

10/ Remember $DAG is how this happens. You cannot divorce the market forces embodied by $DAG as a tradable asset, from the #Hypergraph’s utility as a communication network. They are intrinsically linked.

11/ Any attempt by the DOD to bypass this via centralized decision making is unlikely to work and certainly won't be optimal. And, again, it presupposes they know in advance what endpoints they will need, and this is simply self-defeating when it comes to gathering intelligence.

13/ Finally, while there’s more points I could make here (about graph-theoretic connectedness & how the Hypergraph is fundamentally monic and designed to protect against network partitions)...

14/ I’ll just emphasize that the DOD is competing against formidable adversaries in a theater of war, and seeking to deploy autonomous weapon systems which rely on split second response times. I highly doubt they would forego the advantages associated with the public network...

15/ especially when it’s an advantage their adversaries may seize in their absence. For this reason, I believe a lot of the work ongoing with the DOD is about guarding against this possibility. I imagine the DOD is building its initial reputation metrics...

16/ (being first movers will be extremely important in defining the PRO landscape in the long term). I expect they are also already working on something akin to a firewall to prevent adversaries from using the Hypergraph as a weapon of war against the United States.

17/ So to conclude, the DOD running a private network would potentially pose national security risk and would, in any event, be self-defeating from a data-gathering perspective. A merger of the DOD’s private instance with the public #Hypergraph is, for these reasons, inevitable.