Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Jackal Town Hall
Recorded: Sept. 3, 2025 Duration: 0:26:58Space Recording
Full Transcription
Music Thank you. All right. Let's get started.
Mr. Marston, how you doing?
We got Jaden.
I'll speak down there.
Jaden, I think it'd be best for you to come up, too,
because I know there's a lot of stuff going on on the sales side right now, too.
But in the meantime, Mr. Marston, how are things?
How are you doing?
How's your last two weeks, Probably since we last chatted here.
Good, man. Just putting all the pieces together. It's, it's working,
but it's not without all these little tiny problems that keep popping up
that I got to,
you know,
put out a bunch of fires,
but otherwise it's,
it's good.
Yeah.
So tell me about like the pieces and like,
tell me about like all the things that kind of go into putting this all
together.
Like what is everyone kind of working on and like really really spell it out for me yeah so like probably the biggest thing is of course
like the front end right so the actual website that respawn runs on um it's pretty big. It's probably the biggest like app that we've ever worked on.
Um, there's just so many pages and like all those pages have to do the right thing all
the time and, uh, trying to manage all that state is a challenge, but it's good.
And I'm actually very pleasantly surprised at how good it's become with how little time has been spent on it compared to some other things like the vault.
But a lot of that was just kind of crypto specific stuff that we don't have to worry about quite as much because we're not interfacing with wallets the way that we were before, which is really good.
It makes our lives a lot easier.
But then other than the front end, I think I have a count here.
We have like 1, 2, 3, 4, 5, 6, 7, eight, nine, 10, 11, 12, 13, 14, 15 pieces that aren't the web app, which is a lot.
So for everything that we interact with, we have a piece of like Outlook for Microsoft is its own piece and Google Drive is its own piece and Gmail is its own piece.
So they're all their own little services so that we can run like an entire backup in parallel.
So if somebody goes to Google and says, I want to back up my entire Google system on to Respawn, we have all these different pieces that all run at the same time.
So we scrape as much stuff off Google all run at the same time.
So we scrape as much stuff off Google as it will let us have all at once.
And then we package all that up.
We hold on to it and then get it over to Jackal.
And the part that gets it to Jackal is its own piece as well. And that scales up and scales down so we can run like as many of those in parallel
as we need to load the protocol as quickly as possible.
So just getting those together alone was like a pain because Jackal is very
different than Google.
So trying to do all that communication between was a pretty big hurdle, but it's coming together
pretty nice. The kind of middle piece that holds it all together is doing a lot of work for us
right now. And that piece is just the biggest piece of code we've written probably since the storage providers and the protocol itself.
So lots of bugs in there that we'll probably have to deal with. And that's kind of where we're at
right now is like, as we put the pieces together, that little translation layer in between where
we're finding the front end doesn't like to play nice with it all the time, and it doesn't like to play nice with Google or Microsoft all the time.
But as we're just whittling those away, it's coming together more and more.
It feels legit.
The biggest thing was the actual, like, editor,
which now that we're at this point we're doing like tests on it this
week I want to get a video going of the note editor because it's feeling really
good now so you guys can kind of see more what I mean when I say that I know
there's pictures of it but actually feeling it is a little bit different
that's finally at a place where it like,
not only like works because we had it working before,
but it didn't do anything on the backend of things where like it wouldn't
schedule stuff for you.
Cause we hadn't hooked that up yet,
but now it works and it schedules stuff for you.
So if you make like a backup routine in the node editor, you actually do get those
backup routines added to your account and you can see them kind of on the on deck page,
ready to go. And then when their time is right, they will actually go through the process of
backing everything up for you, which is really, really fun.
Yeah, and I think it's important for me
to kind of frame the problem that we're
looking to solve here as well, because it's
kind of been a little bit since we've really talked about why
we're working on Respawn.
And I feel like there's a lot of confusion around that
in general and why it's good for the protocol
and why it's a good thing for us to spend our time on while we're on this earth.
So to frame the problem, like we were all well aware that like the modern world just runs on data,
like every company, hospital, school, government, business, small business, big business, whatever it might be.
might be. And there's kind of like this really big looming problem where about every year around
$10 trillion of costs is kind of forced upon these businesses. And of that $10 trillion of cybercrime
costs, about 70% of that is downtime. And when we kind of figured this out and we started looking in this,
we started to look at like, okay, why is downtime so prominent?
Like why hasn't there been a lot of innovation in this space?
And we've kind of come down to a few really specific things
that we think that we can make an impact on.
Number one, just everyone has backups,
but most of those backups are never tested
and restores fail about 60% of the time.
Reason being is like testing these things is really, really difficult.
But luckily for us, we know one thing that can verify something in real time, and that is actually building it on blockchain rails, which is pretty special.
And that's one of the superpowers of what we're building.
hours of what we're building. Another big thing is that like small businesses, if they do get hit
and they have downtime, they have critical data loss, about 60% of them also die within six months
of losing that data. So this is like a really, really, really big problem in general. And we
think that the fact that this specific problem space with the advent of AI powered attacks and
cyber attacks, just exponentially growing, you need vulnerabilities year over year growing. That is kind of idiocy that we built digital civilization on the assumption
that the backups will work without ever actually having backups that can work realistically.
They're not tested. Testing is expensive. Recovery drills is expensive. And day to day,
a lot of people just don't really
they just kind of hope for the best but at the end of the day um hoping isn't really a strategy
if like you this is the fail safe for everyone's entire business and no one's ever um suffered a
really heavy cyber attack with a lot of costs associated with it, or no one's really ever paid a ransom when their backups did work.
So kind of every time we see this in the news,
this is kind of a state of failed backup and recovery technology.
So with that, kind of like our plan right now,
just so everyone's aware,
is to build the first provable recovery backup system.
So every mailbox verified every single 12 hours,
kind of having proof instead of hope.
We want to expand it.
So this is kind of step two in our master plan here.
So we just want to expand it across the SaaS ecosystem.
So we're starting with Office 365, Gmail, Slack.
Now we're moving,
then we're going to be moving into like Salesforce,
GitHub, AWS,
kind of every platform in general that holds your business and the world's knowledge in general.
And then kind of moving into kind of our step three here is we just want to create a global recovery network.
So when you think hospitals, law firms, governments, enterprises, Respawn just kind of becomes a backbone that keeps all those critical systems online no matter what.
that keeps all those critical systems online no matter what.
And yeah, step four, long term,
we just kind of want every bite of human knowledge
to be continuously tested, verifiable and recoverable.
We just want data loss to feel as archaic
as dial-up internet, for example, right?
So that's kind of where we are,
and that's kind of where our head's at.
And that is my focus on really, really pushing the pedal to the metal to
get this product out if we're successful and i jaden will kind of go into our pipeline of companies
we have we're looking to hit the ground running and get as many companies um protected and using
the system as quickly as possible once we go live. For us, right now, our pipeline is looking like
$250,000 of pipeline. We obviously have to grow that and we have to find a scalable,
repeatable process in that. But yeah, we just really want to hit the ground running,
get everyone onboarded and really try to make a dent in that $10 trillion of cybercrime cost every year. And really the only metric for us
is seeing that number go down as much as possible.
It's really binary in our eyes.
So that's kind of where we are.
But Jaden, how's it over to you, dude?
What are you working on sales front?
I'll just kind of do a little brief overview
of the to-do list that I have
here. I've been designing our entire go-to-market outbound system. So I will just do like a brief
literally to-do list. And if you want me to elaborate on the content and the context of any
of the to-do list items, let me know. And I'm happy to do that. Some of the stuff that I've been working on over the past week, two weeks, is first of
all solidifying what Patrick just talked about, which is the problems that we are uniquely
able to solve.
So everything from just eliminating downtime in general to what we hear a lot of C-suite
executives at service-based companies talk about is the
fact that because there's no verification, it is a trade-off between investing more time
in running recovery drills and, and being less or more uncertain.
So whether you're going to be okay if, and when you get hit.
And what I mean by that is there's no way to verify.
So if I want to do a back channel verification by running tests, I can do that, but it costs a lot of time.
If I don't want to invest my team's time into running these fugazi verifications by doing recovery drills, if I don't want to do that, then I get my time back,
but I'm more uncertain that I'm going to be okay if and when we get exposed. So we've been building
those problem statements out. We've been building our sequence, which is how we're going to approach
companies. So it's a 16-step process. There's going to be 16 touches.
I'm going to be reaching out to every single company
and every single person at that company 16 individual times
through a mix of cold call, cold email, and LinkedIn.
We defined our target market.
We defined our personas.
So that's like specific job titles,
specific demographic information, what these
people care about. And then recently, as of a couple of minutes ago, Patrick and I have identified
a list of triggers. And triggers are, I'm reaching out because I saw X. The other to-do list items,
build email templates, build call scripts, which are almost completely done, and integrate the existing
customer relationship management software, which is HubSpot that we have. We're going to be
integrating the sequences that I've built out into HubSpot so that I can do some of that
automatically and don't have to do it manually. And the other and last thing on my immediate to-do
list is to integrate our lead generation software as well.
If you want me to elaborate on any of that, let me know. But that's just the to-do list there.
No, no, that sounds about right. Busy, busy boy. I'll speak on behalf of Ian right now. So Kony
Daddy can't be here because he is currently moving, he's moving from Cincinnati to Chicago but kind
of what we've been working on his end is inbound stuff so ads to funnels to landing pages to
hopefully fingers crossed qualified leads so that is kind of what he's working on right now is ad
creatives copy working on funnels, all that wonderful stuff.
And I'm definitely not also, he's been really instrumental in working on the front end as well
and designing the front end and getting all that stuff hooking.
So that's kind of what the last two weeks has been looking like for Jackalabs.
Outside of that, we've kind of been rambling here for about 17 to 20 minutes.
So I'd love if anyone has any questions, feel free to come up.
Other thing is an ask as always, if you guys have any companies that you think could benefit,
pretty much every company in the entire world should have backups.
And we think that we can provide them with a much better solution for what they currently have.
So if you can think of anyone, send them our way.
We'd be more than happy to have them as well.
But yeah, if anyone has any questions, feel free to come up.
While we're waiting for people to come up,
side note, something very exciting outside of Respawn.
Either today or tomorrow,
the file size limits are going to be pulled off the vault.
So you'll be able to upload whatever you want.
We've been testing today and there's a bunch of new stuff that you probably
won't even think about because it's all performance stuff,
but we've upgraded Jackal.js to use a faster hashing algorithm, which means the hashing part of uploading files
will be substantially quicker.
The actual upload process itself won't really change
just because of the file sizes going over the wire are the same.
But because we made it faster and removed the file size limit,
when you start uploading big files, that was when we really saw the hashing algorithm start slowing
us down. So we switched to a faster hashing algorithm. And if you are using the old hashing
algorithm in an app of some sort, that's okay.
That will stick around.
That'll be fine.
We've put a lot, maybe too much thought into this.
So there's no chain upgrades needed.
There's a storage provider upgrade that is in pre-release right now that manages this for us.
And a Jackal.js upgrade, which Jackal.js going forward will use the new hashing
algorithm but it won't affect any files that have already been updated or uploaded. Any old files
that use the old hashing algorithm are still valid still good you just won't be uploading
new files with that old hashing algorithm so should be a little bit of a better experience
for you if you're using the vault and we'll have some more details on twitter and stuff coming out soon
yeah no size limits that's what we need and honestly like a big piece of this is is um this
is something that i think that every crypto project should be doing in
general but um like using your own protocol building apps on your own protocol like the
iteration speed and the way that we can find things and to try to solve our own problems is
extremely extremely extremely helpful um so that's kind of where my head's at there i think it's
important to use the things that you build. Going into anything else, if anyone has any questions,
want to come up, want to chat, want to...
Oh, my goodness.
That was loud.
I'm driving a star.
I just ripped my laptop charger out of the wall with my chair.
Really nice of me.
But anyways, if anyone has any questions we got uh fisherman
you're up you're live
making it in there how are you doing oh not too shabby i had a question about what's after respawn or have you guys put any team effort
or thought into that where you would pivot your available man hours once you get respawn out and
going um i think that respawn like well this is the thing right like i'd like it to be the forever
project like the market is big enough and like public market comps um like these are
billion dollar um backup and disaster recovery products so i in a perfect world that would be
the killer app of the protocol in general which would drive as much data onto the protocol in
general as well so i think that would be the best use of our time um if the event that the market
just chews us up and spits us out,
we're going to have to iterate and build something new. But that's going to wear my
head's at. And I think that building ResPun is the best thing for the protocol because
there's no other way to get more data onto the protocol rather than pretty much protecting
a company's entire carbon copy of their current data. It's moving data in size.
It solves a problem uniquely.
Our value propositions are unique and actually solve a problem for these guys,
whether it's the verification, whether it's cutting costs on actually doing recovery tests.
There's margin for us to get cash flow positive as a company
and also drive as much value to the protocol in general.
So I think that this is the one in my mind,
but I think that almost all demand hours should be focused on that.
And in turn, when we use the protocol,
we find more bugs and we fix those bugs,
which then in turn makes the protocol better as well.
That's kind of where my head's at at least.
Yeah, that's pretty much kind of like where I think things are going.
If with the protocol itself um every time we do
something with respawn the protocol just gets added to basically um which is really great and
then I think the biggest thing for a respawn as far as like dev hours go is just kind of like maintenance. And then as far as like new things go, the protocol itself will grow with respawn as
we add features to respawn.
Like I know one of the big things we've been talking about as far as respawn is concerned
is, you know, we have the data.
We want to get the data back as quick as possible. So something that a lot of other
like backup and recovery software does is there's like this idea of a live mount.
And essentially, if you have something like an S3 bucket, and that is compromised,
and you want to get back up and running ASAP, then you can live mount. And what that means is you can point all your systems to
an S3 bucket that is hosted by the backup company. And then you can just get up and working and
reading data directly from that in your applications instead of needing to move everything over,
because they already have it. So things like that are kind of essential next steps for Respawn as
a product. And with that, you know, we want to make the data on Jackal more usable in the same
way that you would make an S3 bucket more usable and have those live mount capabilities. What I would love, love, love, love, love to do is get to a point where all of that
company's data is backed up in a way that mimics whatever storage medium they were
using originally.
And we load it onto the protocol and we can live mount directly from the protocol.
So those types of things where you might be able to just like pretend that the protocol
is something else while still having all of that privacy
and maintaining the integrity of your files.
Those features that we would be throwing at Respawn,
they don't just work for live mount,
like mimicking an S3 bucket or even mimicking a Google Drive.
Those are not just for backups,
but those would just be like
free features that once we put them into Respawn, we'd be building them into the protocol directly.
So then we put them in the protocol and the protocol gets them for free. So I think it's
going to be one of those situations, like Patrick said, where we just kind of are the users of the
protocol. And we just keep building in features that we need.
And then as the protocol scales, you know, we're seeing more apps come on like Seguia,
like Oculus. And as those scale, they're probably going to be doing the same thing where they want
certain features on the protocol. And we kind of, if all, you know, goes well and everybody's game
for it,
kind of work together on making the protocol underneath all of our apps stronger.
Because if we push changes to the protocol that are good,
Sigia gets benefit.
If Sigia pushes changes to the protocol,
good chance we get a benefit out of it too.
So as we scale, more teams ideally come online
as the protocol gets bigger, and that helps Respawn, and Respawn helps the protocol. So that's kind of where my head's at.
Good answer, guys. I just kind of wanted to take a temperature check and see what you guys were thinking on that.
I know we talk about what we're doing right now, but it's not often that we talk about really, really long-term vision, which is something we should do more, actually, because I know we have a lot on our minds, but until we get there, we won't really know what's viable and what's not.
like if it only takes one of these products to actually start to scale,
like what the protocol needs for the entire protocol to be cashflow positive,
it's literally just $2 million of net buy pressure.
So that is either if we want to take it down the direction where we're just
focusing on storage purchase, that's $2 million of storage purchase.
That's around 11 petabytes not that
crazy in general especially if we're taking carbon copies of companies or if uh oculus for example is
doing a lot of streaming or the mobile app with cigna just takes off it's just not out of the
realm of possibility at all
if anyone has any other questions feel free to come on up if not we're going to get back to work
get back to cooking we're in lock-in season september to december the best time of the year
arguably my favoriteably my favorite. Arguably my favorite.
But it does not seem like anyone's coming up.
If that is the case, I really appreciate it, guys.
Thanks for being here.
Thanks for being with us.
And we'll see you guys in two weeks.
Cool.
Yeah, thank you, guys.
Host
JACKAL
from
Jackal Protocol
