Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Intro to Zero-Trust Security
Recorded: April 24, 2025 Duration: 0:59:21Space Recording
Short Summary
In a recent discussion, the Geek team unveiled their new testnet and innovative NFT features, emphasizing user control and security in blockchain identity. They also addressed the implications of quantum computing on cryptography and the importance of zero trust security in the evolving crypto landscape.
Full Transcription
Hello.
Awesome.
Okay, just in case anybody is listening to this playback, I am here early.
This is Stephanie.
Yes, and I just wanted to log in to make sure this was working.
So I will see you back here in about 10 minutes. Thank you. Hey Karen, it's working.
Let's see.
Hi Portal, can you hear me?
Oh, we can do so much in our heads, but not with this technology. Hello. Oh, it's Geek Cats. Yay. Welcome, welcome. And Dr. Fart, you've been here before,
and I guess you can hear me. Thank you for giving me an emoji. This is Stephanie,
and I am hosting today. I might be the only speaker today unless
people would like to request to come on because I like speaking to people hey
let's see we should not forget that there is a new testnet launched for Geek.
We are on lithium.
Oh, let's see.
So that's the third element.
And we snuck another one in there.
So we've had the fourth test release that we're hosting on stackit.geek.io.
stackit.geek.io.
That's S-T-A-C-K-I-T dot G-E-E-Q dot I-O.
And you can log in right now while you're on your Twitter account and go there.
And it looks like Web 2, but it is actually Web 3.
There's a wallet in there.
There's an app to play around and make your NFTs.
And it involves our special geek stacked NFTs,
which means that you can add records to an original NFT.
So we're calling that a digital asset that you curate,
and it grows through time.
You start with one, and then if you decide you want to add another chapter of your book
or picture or, you know, the second page of Geek's technical specifications to the first one,
then you can watch that, get that asset out of your wallet,
and add another layer to it, and keep building your stack.
And then by the time you're ready to sell it,
you can transfer this curated collection as a single transaction.
And that's the best I can do with my commercial voice right now.
Hey Nir, how are you?
So good.
And Richard.
I don't know Richard.
I think I know that profile picture, though.
So hello.
This is Stephanie.
Hello, everybody.
I am...
John is taking the day off.
That's okay,
because we sometimes need to take it down a notch,
and I'm here.
I'm trying to be responsible to speak clearly and in simpler terms.
Not my natural instinct, but I'm getting better.
So since we're not waiting for anyone, why don't I invite people to request to speak, and I'm happy to have
you on stage with me, happy to have a question back and
forth, and I'm just going to plunge in because Robbie's not here either,
and Robbie would be so gracious and
would, okay, let me see, how do I answer this request?
Robbie would would um okay let me see how do i answer this request um robbie would wait okay
um i will i will try to get to you ner oh no why are people saying why are you why are you doing sad
faces don't do that.
Okay.
Can you still hear me?
Oh, no.
I'm going to log on to my other machine while I'm doing this.
And maybe I'll ask Kieran, who knows the other password. Lexafix, hi.
All right, cool. So, hello, everyone.
why don't we wait a little while to get to quantum um resistance because i think there
Why don't we wait a little while to get to quantum resistance?
were some people in geek chat who wanted to talk about quantum resistance i said i would answer
those questions let's wait maybe till three it's three o'clock my time wait for about a half an hour
and um if everybody would just take a deep breath while I log on and try to get
Neuron stage I'd really appreciate it I'll be back in a minute Thank you. I might not be able to do it.
I'm sorry.
I'm not a very good two-device person,
which means that I'm going to be talking by myself.
No fun.
So, okay.
Anyway, I've greeted you all here.
I really thank you for being here.
We have been talking about Geek ID for quite a while now, a few weeks,
and I appreciate the listeners because we've actually worked out quite
a few use cases for Geek ID I'm just to review very quickly geek is a no smart
contract platform we do that for a reason which is to take out the attack
surfaces of smart contracts nobody wants their wallet drained and we don't want to do that to you so we have smart contracts
oh gosh
I found it
Nir and Brave
awesome
we don't have contracts
so the benefit of that is
when
hello
do you want to say something now?
No, no, later I...
Okay, okay.
Hi, Brave.
You a speaker yet?
Okay, so...
No smart contracts.
No smart contracts is really important.
Number one, you are trusting a developer. And smart contracts are not a piece of code that definitely does the same thing every time, which is really bad for blockchain, in my opinion. I've gotten opinionated over the past few years.
Smart contracts were changed to have an upgradable function.
And since they're code, if you know how to do that,
and you know that someone has left a back door in that contract to upgrade it or change it,
then you really don't know what you're signing.
So that's one way to buy a product that you don't really understand, and I'm against that.
Another way that smart contracts
are definitely a safety hazard is that we saw in the the by bit hack and we talked
about this at the at the time it happened to people were doing best
practices hey hipto and rub it rub it and, I'm going to assume that's something.
So the Bybit hack was a $1.4 billion drain on the Bybit exchange,
and it happened because even though three different multi-sig signers were
in charge of signing and they did their best when the multi-sig appeared to them
they probably had to just sign a hash so they were careful to use the wallets i assume and the multi-sig was
the gnosis safe contract smart contract and they didn't know what they were signing right so
all three of them signed the wrong thing and that those funds were siphoned off by North Korea.
Hackers group who have gotten very good at this.
And so I think we've been doing a lot of thinking about why it's a good thing not to have smart contracts.
And it's become much easier to articulate that after these kinds of hacks
um sweet tack because if you're going to protect yourself if you're going to stay secure if people
are trying to scam you you have to know what's going on and that's sort of the basis from which we look at blockchain you have to know what's
going on you have to protect yourself by verifying hey sweet tack hello how are you i'm well how are
you um yeah do you want to say something about security in the context of smart contracts?
Is that why you popped up here?
What?
Okay.
Well, I'm going to come back to you if you want to say something later.
In the meantime, mute and then just come off mute if you have want to say something later in the meantime um mute and then just
come off mute if you have something to say okay okay okay thanks a lot
all right all right um okay so we're no smart contract platform. And we've been talking about Geek ID lately because you can mint an NFT by yourself.
You have full control over it because there's no smart contract.
So that means nobody can get in the way between what you want to mint and what comes out.
And so you can make an ID for yourself and only you know who you are.
And your ID, if you want, can put your name on it and then you reveal what your name is or it can put your, you know, your handle on it.
But you don't have to. You could just have a public key.
But you don't have to. You could just have a public key.
And you control that geek ID as an asset in your account.
So one of the things we want to talk about is that this is a very different approach from the blockchain Web3 world at large when they talk about identity because they don't do it in the nft
way that we do right if they're talking about um token gated activities because you own an nft
it might sound like they're talking about the same thing as our geek ID,
but it's not because if somebody else is giving you a token and you're joining a community because you have that token, that NFT in your wallet,
you never originated it.
And you probably don't know the smart contract code.
I mean, there are probably 1% who do, but it's a risk to you in your wallet.
And it's a risk to you if someone airdrops it, right?
Because you might click on something you don't want to do.
Yeah.
Yeah, and Stephanie, what do you mean when you say you didn't originate it?
What do you mean?
Because maybe for you it's clear,
but we don't understand.
Okay, thanks.
So, and I'm not a developer,
so if I need correcting,
just come on up,
you know, ask to be a speaker.
But my understanding is
that NFTs on other platforms are minted originated minted
through a bit of code right smart contract code so when i say you didn't originate it unless you
wrote that code yourself and you're keeping it for yourself hey alex you
don't necessarily know what that code has done where it's been and what's sitting in your wallet
people say that they're just going to use a widget in a platform. And so they're giving you a no-code option to mint NFTs yourself very easily.
But then you're trusting the platform.
And so if the platform, for some reason, I learned this from Lon, if a platform uses a code library that calls some other smart contract and there's
some kind of disruption along the way, you don't necessarily know that you have an NFT
that will just behave in your wallet.
Yeah, please. So the difference is with Geek, we create ourselves the NFT that will be our ID.
And with the other solution, with the token gated solution, is a token that other people
have minted that will serve
as a pass?
The first part
is exactly right.
With a Geek ID
or with any NFT on Geek,
you know what you mint
because you do it yourself
and you're just supplying
the data and the data is
going on the chain and you can read it back so there's no code that says okay
I'm going to take what you input and I'm going to change it a little bit this way
so that it makes a random trait or something like that right so we don't do that there's no code involved it's just
you upload your first artwork and it goes like that on chain
okay i understand okay great so if you haven't tried that, we have NFTs on both custodial app and a non-custodial app right now.
Is it in the Stack app?
is meant for web two people to see how easy it is to mint their own NFTs and
that nothing happens between you and your NFT so if you go to the block
Explorer after you mint an NFT and you scroll down hardly anybody does this
you scroll down to the on the transaction level. You will see what the message the node was sent.
And it says exactly the type that you put in the public key.
And that's about it.
So there's no code.
So there's no code.
What I like about the, because the past you have several IDs in your wallet or account
and every time you do an interaction with, for example, a merchant or an institution or anybody or another person, you can use a different idea that's only for that person.
What it makes me think about is like it's replicating the real world.
the real world. For example, when you are in the street, many people encounter
For example, when you are in the street,
many people and they talk to you and some of them, they see all of them, they see you,
but some of them you share certain information with them. Some know only your name, others know
your name and where you live, others know other kind of information about you.
So it's like we can, with those NFTs,
we can choose what we can share with other people or institution.
We have the control, like in the real life.
That's what made me think about, I don't know if it's correct.
It's correct. It's correct it's correct it's correct you're
doing you're you're exactly right near and i'm i'm glad you um you brought that up because i
think it is very versatile and you can mint these on demand because you control your mint account
on demand because you control your mint account right so you can you can yeah you have control
it's going to take a little transaction cost but that shouldn't prevent you and so another thing Another thing you can do is you can use it as kind of an IOU.
John talked about this a week or two ago.
And I was thinking way back when we were just starting,
I was listening to people who were excited about having disposable crypto credit card things.
So they could have a one-time use that drew from their crypt
account, and nobody had to know how they were paying
or who they were paying.
They just had to know that they had money to pay for it.
And so we can
you can kind of do the same thing here except we're splitting the the ID part
with the private key that controls a infinitely controls the crypto part of your wallet.
You can have them in two different wallets if you want to.
So you can say with your ID, I'm here to pay, and then somebody else actually could pay for the transaction.
Okay, it's like one ID but in two wallets no you can't have um you you can have separate wallets
let me think this through but you can't have the same id in two wallets
does that make sense yeah yeah because it's one NFT. It's like one NFT.
Exactly. Exactly. Yeah, so it'll be given a unique number. You can make it look exactly the same,
but anyone could do that, right? So you don't want to make it so that your ID is counterfeitable.
That's a word.
But anyone can check and see which Mint account it came from
and that it came from you.
And that's the difference.
So you want to pop in and say anything near or brave
no okay so actually that that leads me to I'm sort of rambling but that leads
me to a different use case I was looking at which is that there are smart smart tickets and the smart so-called smart ticketing um is takes place when people are
trying to sell nfts for event ticketing so let's assume that they're making a ticket for a Taylor Swift concert.
And they're all unique.
They're coming from the same smart contract for NFTs.
And it just cranks them out, right?
Here's seat one and row one.
Here's seat two and row one.
I should have done that better.
Seat three and row one.
And then there's, they all have different QR codes.
And Lon and I were thinking about this.
And the problem with QR codes is that they are absolutely counterfeitable.
You can just take a picture of a QR code and you can Photoshop that in onto something else or put it on a, as a image file, right, on the website.
And who's going to know?
It looks exactly like the same QR code.
Okay, well, does smart contract solve that? Well, you can go back to the smart contract
account and say, did you actually issue this NFT? And you can find out, okay, yes, they issued it.
But if the NFT smart contract is upgradable, and about a year ago people were talking about NFTs that would update with your status, like if you played a game and you reached another level, they would change the NFT automatically for you.
they would change the NFT automatically for you.
That's a problem if you're thinking about a one-time use,
like an event ticket,
because you think you're buying a ticket that is in row 1, seat 1,
because it looks like it has the same QR code.
Somebody could make a really great living off of selling these tickets that look like
the real thing from the same smart contract account that mints these concert tickets.
But then if there's an upgrade, they can change it to, oh, that was last night's ticket.
You can't get in, right?
Or I sold 50 of those and only the first one in the door gets to use it and everybody else gets rejected
so there are a lot of that's not even going into the proof uh the off-chain proof of smart
contracts but they're they're just a lot of things that have come up that have made us think oh okay
um we're really happy we didn't do smart contracts.
It was a little bullheaded of us to do that, but I think it's more understandable now.
Does anyone want to come up and talk?
Maybe there was a member of the community, they were interested by the topic.
Oh, the quantum.
Yeah, the quantum topic.
Okay, yes, right.
By the way, I haven't said hi to Lexafix.
Hi, and Alex, yay and gideon nice just nice
to see you nice to meet you okay so quantum quantum is a different way um that we have to and that no one can break your keys because if someone can break your key they can use your key
to unlock your wallet and take all your assets right so the point of all of this cryptography is that under current conditions, it would take.
I think John says until the heat death of the sun to break one of these keys if you keep it private.
So that's a good thing. But if quantum computers come along and they can do it in two days and then they can get access
to your account and then they can spend out of your account or move it to somewhere else that
would be a bad thing all right got it so what does that imply for us as a no smart contract
us is a no smart contract platform well since the every account is controlled by individuals who
know what their accounts are doing this is no code involved in them they just know where their assets
are then we leave it up to every individual to decide how much protection they want to put around their assets.
We're very much, you know, you decide users what you want to do.
We're going to build the protocol and leave as much choice to you as possible, knowing that we're not going to change the protocol on you. So we thought about
quantum. And in order to make a key that is more robust, stronger, will hold up longer,
will take longer to break, you have to actually make the key longer. So more digits, right?
People think in terms of bytes.
So a byte is eight bits, and that
helps determine how long the key is.
A certain length key will take some number of bytes.
A quantum-resistant key has to be longer.
So the computer has to work harder to break it.
So that'll be take more bytes.
And that's the tradeoff.
So the tradeoff is you can get more security with an encryption algorithm that generates a longer key.
algorithm that generates a longer key so that takes longer to break so
So that takes longer to break.
if everybody has longer keys on the same chain it's more space right and uh if you're doing all
kinds of things on the chain uh it may take more of other resources too.
What are the three resources?
Bandwidth, compute, and storage.
So being quantum resistant is a resource cost against the security.
Resource cost against the security.
A long time ago,
Hippto will remember this, Alex will remember this.
We were doing,
we were talking about micropayments.
And micropayments,
we're thinking, you know,
one cent of less than a cent for streaming media.
No one wants to sit around and wait and wait for the whole chain to get through.
If everybody is using quantum keys, it's not worth it.
Because what are you trying to safeguard?
You're trying to safeguard a half a cent with this big key?
It doesn't make any sense. So in our philosophy of saying,
you know best about how you want to use the chain,
what your assets are, what your spending habits are,
what level of safety you want to have,
we're going to give you choices.
So one chain could have regular keys and be easy to use.
And then we will probably release another chain, because we're multi-chain,
that has the encryption ready so that all the transactions on that chain
can be expected to be protected with these long keys, right?
And that way we set expectations for the users that if they're using an app on that chain,
it's more secure, for sure.
They know which store to go to, right?
Which app to use.
But it's also going to take longer but it's more secure so they can they
can figure that out so one of the things that we've talked about in the past is put your health
information on that chain be careful where you put your health information right but but if
somebody uncovers my video um viewing habits I do tell Netflix that, right?
I don't care.
That's one area, right?
If certain things get exposed
because quantum suddenly takes us by surprise,
that's okay.
One thing that we could talk about
that we have talked about behind the scenes,
and maybe this is like your little gift for today,
is we've talked about releasing one chain from mainnet
and then taking the time to make the treasury chain quantum
the treasury chain with quantum encryption
with quantum encryption.
so that you know that the geek coins on the native chains
on main nets will be protected with quantum encryption.
And we haven't fully decided, right?
sided, right? It would take a long time. People are always asking us when, when, um, and maybe
It would take a long time.
People are always asking us when, when.
we're not going to be that kind of chain. Maybe people are not going to keep a lot of geek in a
wallet. And so they'll keep their geek in hard wallets and it's not worth it to go through all
of that. We're certainly not going through all of that for the first chain. So we just want to get people to use it.
But it's an option.
And so why is it an option?
It's an option because since every transaction
is standardized and down to the number of bytes
bytes that you have to put your data on the chain so if you want you know a
that you have to put your data on the chain.
hundred pieces of metadata then we can launch a chain for your app where you
have a hundred slots for metadata, no problem.
But in order to do that, you need to tell us
how many bytes you want.
It's different if you want 100 yes or no or toggles.
That's a different byte count than if you want
to have an entire classroom of people
fill up their 100 metadata slots with a sentence.
OK, so what John has done is he has specced out each transaction.
Every coin transaction has to have their coin account the number of coins keep track
of the number of nfts the number of fungible tokens etc and that format is the same across
every chain but the byte number per transaction depends on the kinds of applications that are using it.
So the computer knows, oh, I need to keep reading bytes.
I need to keep reading bytes because this is a chain where everybody's writing an essay in their metadata.
So let me just stop there and see if that makes sense to people.
So some chains, they have more bytes, it means more security or it has nothing to do with?
Okay, great question because I was getting a little confused myself. So the byte allotment per transaction has to be defined so the computer knows when they receive a message, what do I expect to read?
It's not that they care about the sentence that you put in fact um but anyway but they need to know if oh this is only going to go on for 10 bytes right and then i'll get to the next part
um so all of that is to say this is why we count bytes um and this is one of the reasons why you don't use,
we're not using quantum resistant keys for everything
because the cost is the byte.
And the more bytes, the larger the block space,
the more storage and so forth.
So we can have chains that have that same format, right?
Key, key, key.
I mean, sorry um coin account coin balance
fungible token balances of various kinds um and that might be a short account
because everything is very well defined we don't have sentences in that kind of account
right so this might be one of the exchanges that um akil wants to build
and so we know that those block the computer knows and we know and users know that that's a small
byte a few number of bytes for per transaction And so there, maybe you do want a quantum key
because you have the room.
Does that make sense?
Yeah, I think it's the same thing you said.
I don't know when I heard it.
You explained is also the speed you adapt to the people needs.
Yeah.
The same thing. needs. Yeah.
The same thing?
Yeah. Yeah.
I might be repeating myself, but Nuri, you're so good at listening.
Maybe not everybody gets it.
Okay, so that's sort of the quantum answer is that because we're multiple chains
and because we know how each transaction should look in each chain,
how each transaction should look in each chain same format but with room to grow
if you have a application where you're putting you know gobs of stuff in the
metadata and other chains will have the same format but small transactions so
maybe more efficient blocks and maybe the value of those
transactions are worth keeping with a quantum resistant key we can accommodate
both of those things okay so really it's a trade-off that's very very simple at
geek and we've decided that we don't want to say that we're
oh we're you know everything is quantum resistant because
there are going to be a lot of times when you don't want it
and that i think is the is the question that someone brought up in chat on Telegram is, you know, why don't you say this? Well, you know, it's kind of not that interesting to me, to the team,
but maybe we should talk about it more.
And yeah, you can go tell people we're ready for quantum if you want.
quantum if you want um so uh i i do want to say that we're talking we're going to be talking a
lot more about zero trust security um geek cats here i don't know how to say your full name mature mood um is um it's uh akim shared akim akim akim yes now i know akim
i know i know i've seen i've seen this he's been a og for years um uh thank you yeah uh
Yeah.
Right.
So here's what I realized, and it's only been in the last year, that when John started out to work on security for blockchains, he started out by saying, I don't think these other consensus protocols are very secure and right about that, right? We've seen them fork and we've seen them get hacked and we've
seen them get in contentious governance decisions and it's just, you know, not what we want
to do. And then he set about and said,
well, I want to make something very precise
and I don't want to be dependent on other people
who are going to make trouble for me.
And so our definition of security, I think,
is when I do something on chain
and I have access to my own assets
no one can get in my way
no one can stop me
no one can take stuff from me
no one can scam me
so we went into blockchain
and said
where are the sources of potential danger of threat to me on
chain well one is from governance so we took that out of the chain there's no voting
um one is from over dependence on a trusted third party.
So we didn't want that, right? So we started taking out these different kinds of trust layers that might threaten our security and our independence and our agency to get to our own stuff and have it done efficiently.
And because of that, we took out smart contracts.
We took out any kind of voting in a consensus,
not just in community voting, but actually in the consensus itself.
And then we took out centralization, tendencies to centralize so that we don't have people
making private mem polls, for example, because that's not fair.
There are people who know about them and there are people who don't, and everybody should
have the same advantage on Geek.
And so why am I saying this?
I'm saying this because as we work to take out these points of failure
and these centralizing forces and the need to trust other people,
like, you know, everybody uses the same block explorer
and they just trust that it's saying the right thing.
At Geek, you can prove it for yourself.
You don't need to trust us to give you the block explorer.
You know, when we give you the APIs to figure out how to write one yourself, you're welcome to write it yourself, right?
the API is to figure out how to write one yourself.
You're welcome to write it yourself, right?
And so taking out layer after layer
and point of failure after point of failure
eventually got us to trust this blockchain
and verify, don't trust.
And we have the proof.
You have the proof.
The proof is in the hands of the user at the edge.
It's not the control of the chain is not centered inside the network.
Okay, so we got to trust this blockchain.
We got to verify, don't prove.
I mean, verify, don't trust.
And I'm walking around for a couple years now saying,
I know this solves a huge issue because I have trust issues,
and now I don't have to trust, and I know this is going to be a problem
because, you know, we started before fake news, but now there's fake news.
People aren't trusting things.
They need a way to find primary sources on the chain.
We do that.
And eventually I figure out that by getting
to trustless blockchain, we're acting in a zero trust world.
A zero trust has tremendous significance in cybersecurity.
And so Geek is a blockchain platform.
It's a protocol that implements zero trust in cybersecurity.
And I'm super stoked about that because it means that everybody who is worried about cybersecurity which should be everybody will need geek because we are the only
ones who have taken all the trust out of the protocol all the all the ways things
could go wrong and you still need cybersecurity.
You can't afford for Microsoft or Cloudflare or Oracle to have a bad day.
Are you going to go to blockchain?
You might.
You might think about that, right?
It's decentralized. Are you going to go to other blockchains?
Well, you'll quickly find out that other blockchains are kind of wonky.
They do what they do, and we talk about it.
But when you really need something safe, somebody.
And so that is what I'm excited about.
I'm excited about it in terms of identity.
I'm excited about keeping people's data safe.
Everyone here knows that we started out thinking about supply chain cases and then we said oh that applies to information supply chain cases
we've been going and going and sort of inventing
and we end up at zero trust
so that's my little
that's my little wrap for today.
Yeah.
Yeah, that was really interesting.
The last part of what you said about everybody who needs real security in the cyberspace,
they will need a gig.
It's very interesting.
They really will.
I'm just thrilled about this.
So I've been writing explainers and things at a more professional level
instead of writing huge walls of text and chat
to lay these solutions out.
But cybersecurity,
I've realized,
and everybody knows this, you guys know this,
because you already know that we're better than,
geek IDs are going to be more secure than two-factor authentication.
I know.
Thank you, Brave, for publishing that.
But cybersecurity has really always been about trying to monitor who gets in.
So you have to log in.
Maybe you have to log in twice. have to log in twice maybe you have to do a
capture also you know you used to be you had a employee id and then you had to log into your
work computer there are all kinds of ways to think about logging in and making that difficult
and making that difficult um which don't really don't really authenticate who you are
they just authenticate that someone with your employee id badge came and got through the door
and then logged into your work computer i watch all kinds of i love spy shows right so
it's helpful for me to imagine it ending up in a place where I'm constantly thinking about how can these safety systems be defeated?
Because I watch all kinds of things on TV.
But what do cybersecurity, what is troubling to them now?
It's all electronic.
And there are all these kinds of attacks. There are phishing attacks. There are vishing attacks, which is video. No, sorry. Vishing is voice. There's quishing attacks, which is the QR code where you snap a QR code on your phone.
You snap a QR code on your phone.
And John tells me that what that does is it opens up a little app on your phone.
So you're taking a little bit of code on your phone to understand what the QR code is.
And now there are malicious QR codes, so you have to be really careful.
That was a tangent.
Where was I?
Oh, right. that was that was a tangent where was uh oh right so there are these different ways to log into a system but then once you're in um you can do damage so once i've taken over somebody else's
identity on ebay let's say then then I can start bidding, right?
And if they have a credit card saved under their profile and a quick checkout, I can
do all kinds of damage.
And I'm sure we'll think about lots of other examples.
You'll hear us talking about these um
but once somebody is in the system it's an issue of detecting a bad actor
and then trying to stop them as quickly as possible so it's very reactive cyber security
has been about trying to figure out how to get the right people in through the door and keep the
wrong people out and we know that gets compromised all the time and then once they're in, it's about risk management, which is detect, identify, mitigate.
All right.
And Stephanie, what you mean by they cannot come in is what you also explained this week is the air gap thing.
Oh, the air gap. to prevent them from coming in.
Yeah, yeah, yeah. The air gap is awesome. It's beyond the Geek ID, but between the Geek ID
and Zero Trust Geek ID, which is Zero Trust authentication to get into the system,
to ask for something. The air gap is a way to, you can come in and ask for something the air gap is a way to you can come in and ask for something
but we're not going to let you into our data silo we're not going to let you into a firewall
so we will give you a piece of data to read a file to read just your file
that you asked for that we know you are authenticated and approved to read.
But we're going to put you in a safe room.
And you can decrypt it over there and read that one piece.
But you're air-gapped.
You can't get over.
It's like one of those submarine locks, right, where you go from the submarine and everything is safe,
and then you go into the lock, and then it fills up with water,
and you're in there, and then you can go to the outside.
So we're keeping the submarine part safe.
We're giving you the data in a place where we know you're the one who's looking at it,
and we're keeping the ocean water out of the submarine.
That's the air gap.
I probably should have used a space metaphor.
Yeah, I understand.
It's very cool.
It's a good comparison with the water, the ocean, the internet, and the submarine.
What we need to protect our information.
Thank you, Lexa Fix, and you're going to figure out how to make this.
And brave, you'll figure out how to make these better stories.
But it's really super, super cool because what the ID
what we're able to do as
geek as zero trust
having taken all the trust out
is we're able
to say instead
being reactive
in cyber
security like
oh I let you in.
Darn, I shouldn't have done it.
Let me go back and try to undo that 10 minutes later or, you know,
three hours later or five days later.
I really shouldn't have let that person in the system.
Now we can verify your credentials
in real time
every time you do something if we want to.
And that's proactive, because we can verify what's going on by looking at the credentials,
by looking at the chain, which is constantly updating and giving me the information I need
before you do anything, before you try to defraud me rather than after I've noticed you're
a really weird account and I should I should stick my fraud AI on you right and I love flipping models
on their heads that this kind of it really gets me going. I really love that, that there's a problem
and people have tried to solve it for so long.
And I know I'm never going to denigrate anybody
who's trying to do this.
I just believe in security with all my heart,
but they have not had blockchain that works for them.
They have not had this constant ledger update with the zero trust
where everything is pinpointed down to a private key, which is the best we can get in cryptographic
security. So I'm really, really excited and I wanted to share that. And these are huge markets we're talking about because fraud and cybersecurity problems are not going to go away.
And so I love that for us.
But also, you know, it stays true to our mission to keep people safe and don't let the bad guys touch you.
and don't let the bad guys touch you.
So if we can do that,
if we can do that even in a little place first
and then move out from there,
I'm totally, I'm a happy camper.
And I think we can do it
because I know we have already built these NFfts the attestations the digital air
gap all of that depends on what we've already built which is the protocol the attestations
the nfts it's that simple those basic building blocks which have taken us a really long time
those basic building blocks, which have taken us a really long time,
but have been fun.
And no one else has, right?
So hang in there.
Yeah, you could go in places.
And I will leave it at that and turn it over to Brave.
And Nur, if you want to sing us out that's my story
I have nothing to add
it was very interesting, we learned a lot
I love it when you're on stage
Brave, it's getting very late for you
I know, so I'll just say
thank you so much and Lexifix keep making those just say thank you so much. And Lexifix, keep making those videos.
Thank you for being a community mod.
Thank you for being a new community mod.
Alex and Hipto and Akeem, Rubil, Kira and Brave,
you guys have been around forever.
And Gideon, you are a new face.
So I am really happy to meet you.
And we'll see you next week.
Bye-bye.
Bye. Thank you.
