[Music]
hey everybody um yeah my name is Greg uh
or Greg the Greek if you know me online
uh I'm one of the co-founders chains
saafe and as well as Sprinter we recent
Rebrand a few days ago from uh
Sigma um today I'm going to be talking
about end game the endgame wallet uh
this is coming from about a year over
well over one to two years wor of
Standards work that's something I do a
lot in my spare time um and it's
something that we focus a lot at
Sprinter is driving how we can look at
like multichain um and getting the ux
there right we don't have a wallet we
don't really do wallet infra we work in
solving as well as we've been doing
multi- Building Bridges since 2018 and
building Proto we're protocol
engineering a chains safe and I was one
myself for eth
2.0 um so I'm trying to remove as much
bias as possible I'm objectively looking
at the standards when we go through
here so where let's do a little I want
to do a little Memory Lane I want to
like you know bring it a little pain you
know when was I don't know if many of
you remember the world before EIP 1193
but this was when you download a new
fancy wallet and then all of a sudden no
app would ever be able to work with it
or communicate with it if if you're in
an app developer you had to manually
code in communicate with like metamask
or communicate with fancy new wallet
there was a time when you couldn't even
have multiple browser extensions and
that was pre multi- injector provider
there was also I mean this is still a
problem let's be honest we're still
getting we're getting close aggregate
balances that look nicer so your usdc is
better or how about Network switching or
even you know you go to a Dap immediate
wallet pop up we we've been iterating
and fixing a lot of the ux challenges we
see and we see that the improvements
that have been happening over the last
couple years these iterations have all
come
from erc's eips and capes and that's why
they're really important that we start
adopting them but frankly where are we
going right now we're actually like
right now the chain of obstruction space
has kind of us
um we are right now selling application
developers that we they need to deploy a
smart contract for their app to get the
best features in the guest users if you
hear that statement frankly for my
opinion you're going down a road where
you're going to have to do a very ugly
migration path with when six to 18
months and it's just the wrong way to be
dealing with smart contract wets unless
you as the app developer are willing to
deploy wallet infra and when I say
wallet infra I'm saying like a my crypto
website like a full Rage Quit mechanism
so they can migrate to something
different to someone better
you're just vendor locking them inside
your own system maybe inside the wider
system of the deployer who gave you that
because frankly are you well equipped
enough as an app developer to deploy
preferences for the user smart contract
wallet if they want to say exess because
we're going down an intense system are
you willing to express a preference for
them to
ensure that if they say I want one eth
always to exist on mainnet never take
away that one eth you know if I have two
it can go down to one are you ready to
deploy that type of preferences and
those type of feature sets to them CU if
you're not you should never be giving
them a smart contract wallet you're
setting them up for failure and you're
sending your users up for a awful ux
experience down the
road and frankly it just creates
fragmented balances and it doesn't get
us anywhere and the biggest problem we
still have today is that it do we have
any mobile app developers
here have you ever tried to communicate
with a smart contract wallet that was
deployed by another
team yeah it doesn't work it's
impossible we work with game developers
they can't connect to remote accounts
it's it's literally impossible and
that's because we've moved into a world
of pass Keys pass keys are domain
separated you if chains saafe issues you
a pass key only the chainsa doio domain
can ever access that same Pass key so
you need a way to talk to them and
that's where I'm going to be going with
this um a quick note and I'm going to be
very you know this might be a bit of a
lie but like I think we're getting there
within 1 to two years years we're
probably going to see 90% of
transactions will be solved there's no
doubt about that they it we are going
down that path and that's going to
happen um so with that in mind we have
to think there's this big debate of
smart wallet versus like dumb app and so
and so forth frankly if the app is going
multi-chain and you're interacting with
different contracts on different chains
you are smart you have to be smart you
have to know how to actually make and
Bridge those
connections otherwise the wallet's
always smart let's be real they need to
be the one to ensure that the user is
there because they need to be ping that
wall in for I was describing
earlier now let's do this endgame I'm
going to verbally abuse you with erc's
and that's totally fine there's going to
be there's other sessions today that
will help you learn about these erc's
more in deep I'm going to go over them
as quickly as I can as effectively as I
can and use web two examples so you can
understand why they're important these
eips and erc's and capes are ridden by
well over 20 plus people so when I say
there's like no bias in here I'm just
stitching the stuff together that we're
talking about in the wallet meetups at
every
conference okay here's your general
interaction right dap wallet very simple
we know we want to deploy 4337
everywhere that's a given it's the best
ux we can get because we can't get
native account
abstraction we know pass keys are the
easiest way to onboard a user because
seed phrases are too complicated private
keys are difficult and frankly the whole
experience that we've been doing before
is just because because we in this room
frankly are ahead of the curve it's not
going to work for most people pass keys
are a must and they live at the wallet
level the next way to actually broker
this system is to realize that your
dap's never going to actually have a
wallet like a smart account your dap's
going to use an embedded wallet why you
can blind sign in the background as long
as you have permission that means you
can actually maintain the same web 2
experience you thought you needed this
means that you don't need to go and make
a job posting that says hey I need a web
3 designer no no you just need a
designer you need a really good designer
that knows what they're doing and that's
it you can build Web Two experiences you
can get a per desk that looks like Robin
Hood there's no reason you can't do that
the embedded wall allows us to have that
control we need to know how to register
people now this is one that a lot of
people don't realize the capes chain
agnostic Improvement proposals Green
Field playing field for not just evm but
the whole spectrum of blockchain
standards Cape 275 basically says how
can we get to a one-click onboarding you
type I type in Greg theeg greek. it
looks up to see who deployed my smart
contract wallet for me and from there we
generate a slug for an HTTP request or
an iframe or whatever and this is where
the magic happens ERC 75 75 is the same
thing as ooth it's the idea that it
links you when you click sign in with
Google it links you out to Google right
we because I looked up in in the
registry who deployed this wallet I can
actually go in directly to that user so
I can use that pass key to get access to
that 4337 account and now I can use it
with the embedded wallet on my
app but permissions
7715 we stack a permission across the
wire protocol by stacking a permission
across the wire protocol what you end up
getting now is you can be expressive hey
my per desk wants to spend a th000 usdc
per hour and make it expire in 24 hours
what does that resemble a jbt token
something we're used to we're making the
app development cycle easier
here finally
7579 Ryan Stone team big shout out the
idea here your app wants to be a little
bit more expressive the smart account
isn't what you want it to be so you can
develop a plugin directly link it onto
the smart account that you don't really
know about finally 7811 if anybody keeps
up in standard here you probably haven't
kept up with this one it got announced
last week and there's going to be a lot
built up on top of it the simple gist I
want to know from the wallet what are
the assets I don't want to use an
indexer anymore I'm tired of having to
go and query you know an RPC node on a
for Loop over the assets I want to know
about just tell me what do you have
what's the balance of it it's single
chain we're going to take it
multi-chain there's a lot of other erc's
that go on this but the interesting
thing thing the one thing to keep in
mind 7 tri5 it's super ambitious very
ambitious we're not there yet we're
really close we need all these other
eips to get standardized on top but once
we do the one thing we get is we get
this communication channel that we've
never had to a remote account the same
way we do with oos so when a web 2 user
comes into the web 3 space it looks like
you know Google asking for an app asking
Google hey can I borrow your calendar
information
but in this way it's going to register
plugins it's going to ask for permission
on how to spend wallets from your funds
this way we're not depositing funds into
you know poly Market instead you're just
they're borrowing
them and I think I'm running out of time
there's a timeline here I'll skip to
when end I don't know I got quoted two
two years from now the other day I'm not
going to lie I think we can be a bit
more ambitious frankly we're not
protocol developers I was one previously
we don't need to go slow we can go fast
we can