WEBVTT

00:00:01.935 --> 00:00:04.455
You will have some peaks at times and

00:00:04.455 --> 00:00:06.255
there'll be some strain on the grid where

00:00:06.255 --> 00:00:08.995
you'll get up to a maximum utility for

00:00:08.995 --> 00:00:11.295
a very, very small portion of the year.

00:00:11.635 --> 00:00:13.655
And so I think from our standpoint, that's

00:00:13.655 --> 00:00:15.475
where you do have to participate and you

00:00:15.475 --> 00:00:18.435
should be participating in potentially curtailment in these

00:00:18.435 --> 00:00:20.975
pieces. And that's why at DarkHorse, we believe

00:00:20.975 --> 00:00:24.055
in a world where there's a distributed computing

00:00:24.055 --> 00:00:24.935
use case, right?

00:00:24.955 --> 00:00:27.455
And so there's multiple states or multiple cities

00:00:27.455 --> 00:00:28.715
or multiple options.

00:00:28.995 --> 00:00:30.975
So you're not creating a specific grid strain

00:00:30.975 --> 00:00:33.035
in one area, but you've got different options

00:00:33.035 --> 00:00:34.455
where you can kind of run your compute

00:00:34.455 --> 00:00:36.135
and be a bit more flexible from a

00:00:36.135 --> 00:00:36.775
load standpoint.