Jackal Town Hall

Recorded: Dec. 3, 2025 Duration: 0:18:57
Space Recording

Short Summary

Jackal's recent challenges with verification status highlight a decline in user trust, while ongoing fundraising efforts and promising growth in partnerships signal a proactive approach to overcoming obstacles in the crypto space.

Full Transcription

Music Thank you. Music Thank you. Hey, can you guys hear me okay?
Oh, what up? I got you live.
Oh, right on, right on.
Can you hear me okay?
It seems like I've warped it somehow.
I was jumping around between desktop and non-desktop.
I gave up on the desktop experience.
You think it should work better on the desktop, more stable,
but that's just not how we operate.
At least getting the headphones here can you hear me better um differently but but the same yeah it's a different timbre if you will
I don't know why this spaces feature is still so janky.
How old is it?
It's been around for a little bit.
Remember that one?
Treehouse?
Who knows?
A different time.
Yeah, that is a throwback.
But now we have the Everything app.
And this is a part of the everything.
Man, so much fun doing UI stuff for Respawn.
It's been a lot of fun.
It's been a lot of,. It's been a lot of,
oh, does this look good?
Time to move this over three pixels.
I'm starting to kind of lose it, I think.
Marcion, are you able to hear me?
Am I back?
It kicked me out. Oh, did it Am I back? It kicked me out.
Oh, did it kick you out?
Kicked me out.
Yeah, I can hear you now, though.
I love it. can you guys hear me over here like this is
great i can hear you now okay can you guys hit me with a thumbs up down there if you
can hear me over here because this is craziness i can hear you thumbs up thumbs up in the chat
yeah so uh pretty much today if you guys are wondering why the jackal account has lost its
check mark and everyone has lost their check mark is uh we were trying to downgrade to business
basic instead of business premium because it's literally like a thousand dollars a month
and uh apparently uh they just kick you off completely if you do that.
So that's awesome.
So we're now reapplying for our check marks.
So you're saying we're unverified.
We're unverified.
Which could be bad today, guys.
That's crazy.
Is that irony?
So that is what that is right now.
So we're in a weird spot on the front of verification on Twitter,
but we shall be back.
We shall be back.
Kind of over the last few weeks, what's going on in Jack-o'-Land?
So we're continuing to do validation calls for Respawn.
We've been able to get into some awesome conversations most recently with a
bunch of cybersecurity consultants and it's looking like we're going to get some more
deployments and some more essentially pilots into building out what those conversion criteria look
like and then moving into conversion. So that is where we are with respawn and the current state of that
it's it is as everyone should remember it is enterprise sales cycles so it does take a little
bit for us to convert those but it seems like they're coming quicker than we initially expected
which is extremely exciting i'll kick it over to marston on what's going on on the development front on where we are on there for the front ends for the
verification being able to be viewed in the application itself and then um yeah we can
kind of kick it over to mr ian gibson afterwards beauty yeah so we got uh we've got a lot going on
admittedly it's another one of those weird development weeks
where visually it doesn't seem like there's a lot going on.
But behind the scenes, man, the amount of code
that's being written and rewritten
to improve the way that things are going.
So basically there was a big push
where we had a system set up to actually save
all the files from things like Google, Microsoft, Slack, all that good stuff. And the way that we
were saving files was an initial design to validate that it worked. And when we started
we started seeing it working and we started seeing it plug into the rest of the system.
seeing it working, and we started seeing it plug into the rest of the system effectively,
Effectively, there was so much duplicate code spread across all of these sources.
So we've done a big push to take all of that and consolidate it down.
And when we did that, we created this really, really flexible system that we can build on top of.
And what that means for Respa as a product is a more consistency,
less bugs, which is always good. But more importantly, the code is already written for
a good chunk of what new sources will need to do in the future. So when we go about adding new
sources to the platform, whether that be on prem stuff, or saving Azure buckets, for example.
That data is all going to be funneled through the exact same system
that we have spent a lot of time building out,
which is really exciting.
That means our velocity to create new integrations into Respawn
is just much higher, which is excellent.
And on top of that, all of the analytics that we've been working on are vastly improved, both because we just finished a huge
sprint on a bunch of analytic stuff, and because this file handler bakes in a bunch of analytic
stuff. So now, you know, nobody on the team can even forget to plug analytics into
the software that we're building out for these integrations, because it just comes built in.
So that's really, really awesome. We get really, really good analytics on where the data is coming
from, where the data is going, how fast the data is coming in, all that good stuff. So that's been
really exciting. For us, we get to watch a lot of cool charts go up and down.
But on top of that, as far as usability stuff,
we have been really honed in on reporting
and by proxy making the front end really good at reporting.
So essentially what that means is when you go to do a backup
and you first click that button to make that backup happen,
behind the scenes, we're scraping everything off
of whatever service you're using.
But then we are pushing it on to Jackup Protocol
for all of our file verification.
And our file verification is, of course,
the most important part when it comes to respawn.
So with that, having a full registry
of all of your file verifications
and seeing which storage providers they're on,
how well the storage providers are handling your data,
all that good stuff,
that is packaged into a report.
And we've spent some time essentially building an indexer for the protocol to watch proofs as they go up.
And because of that, what we're able to do is you basically give the system a Merkle hash from any file in the world that lives on Jackal. And it will give you a
historical list of every single time your file was proven and which storage provider proofed that
file. So that is really cool. That lets us do a lot of cool graphing stuff that wasn't possible
with the way that Cosmos was set up before. So now anytime a user wants to go
and look at any of their backups,
essentially, they're going to not just be given,
hey, they are proven.
Yes, that's good.
They're going to be given a list
of every time they've been proven.
So you can say like, hey, you know,
this day it was proven three times.
This day it was only proven two
because one of the storage providers died. But, you know, now day it was proven three times, this day it was only proven two because one of the storage providers died.
But, you know, now that we're back at three, we're good. So they can actually see that whole history, which is very cool.
And then we've also just been doing a lot of front end work, cleaning out front end bugs, cleaning out little design things here and there, trying to make it a more cohesive experience overall.
things here and there, trying to make it a more cohesive experience overall. And that is mostly
to support a really, really nice visualization of your verifications on your data. So yeah,
lots of good stuff. Lots of big things that you will never see, which those are kind of
both the most fun and the least fun parts of this so the best big things
the best big things yeah they're really important really good big things um but yeah you'll never
you don't see them in the ui so we forget about them exactly um outside of that we're just
continuing to push forward on uh resp respawn we're currently raising for
respawn doing all that good stuff so that we can make sure that we can
continue to build and do all that good stuff on the response front so we're
looking to raise capital for it we're also in the process we have some really
awesome validation points so far but we're always looking for more design
partners so if you or anyone that you know
runs a business that would be interested in knowing if they can recover from a cyber attack
or error and autonomously healing when they can't, please feel free to let us know because that is
where we are right now is just in deep validation, early pilots, and then getting to a full operational go-to-market.
And that's kind of where we are right now.
I'll kind of kick it over to Ian,
what's going on in the front-end side of things,
and then we can kind of move on from there.
Well, on the front-end side of things,
Marston and I have been working really hard
at revamping the dashboard
and also just revamping a lot of the UXs.
We worked really hard at making the app pragmatically work, creating your backup flows, actually taking those backups and putting them on chain.
But as you did all of these things or as you do them all in the app as of right now, the app doesn't really show you anything that's going on underneath the hood.
So we're trying to do a better job of just adding in progress bars.
We're revamping the alerts section.
We're taking all the analytics that Marston's indexer is scraping and giving you a good way to just present those to the users.
and giving you a good way to just present those to the users.
And this is different from reporting
because reporting is kind of more for a MSP's client.
So we don't want them to be like exactly the same.
Like if there's some alerts that pop up,
we want the MSP to be able to address those and clear those
without necessarily like forwarding them on to the client
if they're just, you know, not that big of an ordeal,
if it's an alert that the MSP is aware of.
So we're kind of approaching it with two different target audiences for each set of data.
The dashboard is going to be all the data for the MSP,
and the report is going to be for the MSP's client that can just be sent out to them
at whatever interval that they see fit.
So we're revamping all of that stuff and we're also
bringing the verification storytelling to the very top of the dashboard we've already implemented it
in the app itself as we kind of like move through your different restore points and you can see the
last time that they had an on-chain integrity check so you know that that backup is good to go
you can you can always see that last integrity check um but in theory there's these integrity checks that are going on
all the fucking time um i believe they go on once every 12 hours marston correct me if i'm wrong
once every 12 hours per provider so realistically we're looking at three per every 12 hours.
And per bundle of data.
So like a restore point could be made up of like a thousand bundles of data. So for one restore point, for one backup, we could have like 2,000 verification checks that are happening in one day.
And we're trying to come up with a cool way to show that.
Because it's not necessarily something that the user needs to act on.
It's not like a UI element that they really need to interact with to do their day-to-day job.
But we want that storytelling to be there.
So right now, we're going to have an animation of the chain.
Just a bunch of blocks scrolling by.
And as those verifications hit, we're going to let you see where they're at on the blockchain.
Look at those on a a third party Explorer and just kind of have almost like a Bloomberg
terminal of just like verifications like flying by just so because you don't really, you know,
if you buy a fire extinguisher, you don't really get to like squirt it off.
You don't really get to see it in action.
It's just kind of like a safety feature that sits underneath your kitchen sink um but we want to like show you what's going on all the time so you
can like truly like believe in the uh in the in the product itself and there's a lot of uh just
behind the scenes stuff that uh you know it's kind of hard to like tell that story if i buy a safety
deposit box and i'm at some bank i get to walk through the balls you know what i's kind of hard to like tell that story. If I buy a safety deposit box and I'm at some bank,
I get to walk through the vault.
You know what I mean?
I get to see the big thick ass door.
I get to know that my stuff is safe inside of my little tiny box with my
little tiny key here.
We need to do a little bit more of that, like storytelling,
even if it is, you know, just story.
That's all it is.
It's not going to be like a necessary part of the app.
You don't need to click through it, but we want it to be fun, you know?
But I think that's kind of our biggest, you know, biggest thing that we've been grinding on.
And I think it's in a really good spot.
Hopefully we can start to activate that and deploy it into the app soon.
Is there anything else we chat about?
If anyone has, you know, any interesting stat ideas they want to see on the dashboard,
I guess now's a good time to, you know, get some feelers for that.
That's kind of what we've been in debate about and trying to figure out,
what do people actually need to see
to do their MSP job?
And I've just been screenshotting
a bunch of different DRAS apps
and non-DRAS apps as well,
and getting a lot of dashboard inspiration.
And yeah. Right on um that's pretty much everything
that's it from us right now on our end um we're just kind of grinding away getting this to market
getting early pilots validating our thesis and then continuing from there so if anyone knows of
anyone that would be a good partner for us at this stage that owns a business and really just wants to know if they can
recover and autonomously heal
when they can't, feel free to let us know.
But in the meantime, we'll see you guys
in two weeks.
Take it easy.
Bye, everybody.
Be good. Bye, guys. Thank you.