Evan Conrad

“Meanwhile, the location of that storage matters. So if you're able to move that data from one cluster to another quickly, then maybe you might be able to spread across multiple different clusters and you can be interrupted over here and then pop back up over there.”

Expects: A workload may be able to move across clusters and resume on a different cluster after preemption if data can be transferred quickly between clusters. · no date given · not yet resolved

“product that can use lots of different types of capacity, um then you might really like S_F_ compute, because you will be able to use lots of different types of capacity and you'll make more money. Um you can take the uh the spread.”

Expects: A product capable of using many types of compute capacity might benefit from SF Compute by using varied capacity and earning money from the price spread. · no date given · not yet resolved

“Uh we will have some announcements um in a week or two um that we expect to come on.”

Expects: SF Compute expects to make some announcements within one or two weeks of the conversation. · 20 Oct 2026 – 3 Nov 2026 · not yet resolved

“Um so I think standardising the contracts in general is still pretty far away. Um”

Expects: Standardization of compute-capacity contracts remains a considerable distance away. · no date given · not yet resolved

“Like this is a thing that we're thinking about but haven't done basically. Um the early G_B_ two hundreds broke, the early H_ one hundreds broke, um and so if you were buying H_ one hundreds or you're buying G_B_ two hundreds, you might really want the ones that were deployed after a certain time because you're not getting the first G_D_ ones off the rack. And so if you're a super sophisticated customer, you may be willing to pay more um because”

Expects: Sophisticated customers may pay more for later-deployed units than for first-off-the-rack units, in light of failures in early H100 and GB200 deployments. · no date given · not yet resolved

“Yeah, so um a bunch of people are basically looking at this and thinking um if I think prices are going to go up, I might be willing to pay more than what I previously thought in the future um because I might think okay, I can buy a five right now. But if I can't buy any more, then maybe I will be willing to buy even more in the future just to lock it in if it's gonna come online later. So we see the other side as well. Um”

Expects: Buyers who expect compute prices to rise may pay more for future-dated compute to secure supply when they cannot purchase enough compute in the present. · no date given · not yet resolved

“build too much financialization before you've the industry has had time to build out the the physical settlement then I think what you have is you have a market that's very easy to manipulate and a market that has a lot of basis risk where the price you may be hedging against actually has nothing to do with the price that the market you can actually buy the capacity for.”

Expects: If compute-market financialization expands too far before physical settlement is established, the market will be easy to manipulate and will have substantial basis risk. · no date given · not yet resolved

“After we will take over and we will uh do the superconducting portions of that and ensure the things go right, we own the S_L_A_ and then if it turns out that that was a bad idea, that you need out of that cluster, we can immediately sell that cluster to somebody else, so it doesn't hit your balance sheet.”

Expects: SF Compute says that if a customer needs to exit a cluster, it can immediately sell the cluster to another buyer, preventing the cluster from affecting the customer's balance sheet. · no date given · not yet resolved