►
From YouTube: Wallet Standards Work Group Meeting – April 20, 2023
Description
Today the NEAR Wallet Standards Work Group met to vote on: https://github.com/near/NEPs/pull/428
Meeting Summary:
[Coming Soon]
Chapters:
00:17 Agenda
00:42 Objective
03:50 Introductions
04:50 NEP-413 – Author Summary
08:32 NEP-413 – Benefits
10:31 NEP-413 – Concerns
12:46 NEP-413 – Voting
17:25 NEP-413 – Next Steps
20:02 Getting Involved
Learn about Developer Governance:
Website: https://neardevgov.org
Twitter: https://twitter.com/NEARDevGov
Telegram: https://t.me/NEARDevGov
NEP Process: https://github.com/near/NEPs/blob/mas...
Join the NEAR Wallet Builder Community Group:
Telegram: nearbuilders.com/tg-wallet
Join NEAR's community:
Website: https://near.org/
Reddit: https://www.reddit.com/r/nearprotocol/
Discord: https://near.chat/
Medium: https://medium.com/nearprotocol
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
Dev Docs: https://docs.near.org/
Create a wallet: https://wallet.near.org/create
Apps on NEAR: https://awesomenear.com/
Learn to Build On NEAR: https://www.near.university/
Grants & Funding: https://near.org/grants/
#Blockchain #FutureisNEAR #NEAR #nearprotocol
#nft #dao
A
A
A
Here's
our
agenda
first
we'll
discuss
the
objective
of
this
call
and
I'll
provide
some
more
context
about
our
developer
ecosystem.
Next,
we'll
introduce
all
the
participants
that
are
involved,
then
we'll
get
into
the
main
discussion
net
428,
and
you
can
find
the
link
for
that
in
the
video
description.
If
you
want
to
follow
it
more
closely
and
lastly,
we
will
open
it
up
to
QA
and
talk
about
next
steps
so
to
get
started.
Let's
talk
about
the
objective
of
today's
call.
A
We
are
here
to
publicly
vote
and
arrive
to
a
final
decision
on
NEP
428,
which
is
a
wallet
standards,
extension
proposal
that
was
submitted
by
a
Community
member,
and
we
are
also
here
to
celebrate
the
effort
and
time
that
everyone
invested
into
this
snap
as
it
did
go
through
a
vigorous
review
by
the
community
and
many
subject
matter.
Experts
who
all
care
about
making
our
ecosystem
better
before
we
jump
in
I
wanted
to
give
some
more
context
to
help
contextualize
our
call.
A
One
of
the
main
tools
that
we
use
is
the
near
Dev
Hub,
which
is
the
main
platform
for
new
developers
to
contribute
and
stay
informed,
and
anyone
is
welcome
to
share
their
ideas,
Solutions
and
get
technical
support
and
funding.
You
can
also
find
various
communities
of
people
interested
in
specific
topics
such
as
zero
knowledge
or
tooling,
and
it's
really
just
a
great
way
to
meet
with
others
to
share
ideas.
A
There
are
four
key
roles
in
the
net
process.
We
have
the
author
or
champion.
This
is
the
person
who
writes
the
proposal
and
presents
it
to
the
work
group,
the
moderator,
the
person
who
facilitates
the
process
and
helps
ensure
that
the
net
progresses
the
reviewer.
This
is
an
assigned
subject,
matter
expert
who
reviews
the
technical
feasibility
and,
lastly,
the
approver,
which
is
the
working
group
who
makes
the
final
decision
just
to
visualize
the
the
process.
A
There
are
three
stages:
draft
review
and
voting
and
two
outcomes
approved
and
rejected,
and
all
the
roles
mentioned
before
help
move
the
net
through
these
stages
and
towards
the
outcome
most
of
the
activity
happens,
asynchronously
on
the
net
itself
within
GitHub,
but
when
we
do
get
to
the
voting
stage,
the
work
group
has
an
open
public
discussion
to
arrive
at
the
best
decision
in
a
transparent
way,
which
is
exactly
what
we're
doing
here
today.
We've
been
executing
this
process
and
are
looking
at
a
proposal.
A
That's
in
this
final
stage,
so
before
we
jump
into
the
actual
nap
I
wanted
to
highlight
the
participants
that
were
involved
in
this
snap.
So
first,
starting
with
the
author,
which
is
Amir.
Thank
you
so
much
for
submitting
the
snap
next
to
moderator,
so
myself
and
Vlad
have
been
playing
the
the
moderator
role
on
the
snap
and
we've
had
two
technical,
reviewers,
Joe
and
Andy.
And,
lastly,
the
working
group.
A
The
wallet
standards
members
which
include
sterile,
Osman
and
Cameron,
so
please
feel
free
to
introduce
yourselves
in
the
chat
or
when
you
speak,
and
with
that
I'd
love
to
move
to
the
actual
net
discussion
428
and
invite
Daryl
who's
going
to
present.
On
behalf
of
the
author,
who
wasn't
able
to
make
it
to
the
call
a
little
bit
about
the
net
and
why
it's
important.
So
there
will
please
take
it
away.
B
C
B
B
So
the
user,
when
they
actually
sign
into
a
deact,
will
be
authorizing
that
that
d-app
can
sign
transactions
against
more
than
one
contract,
and
this
is
part
of
the
near
blockchain
core,
the
ability
to
create
limited
access
Keys,
which
can
only
be
used
to
interact
with
contracts,
specific
contracts
in
specific
ways.
It's
kind
of
a
special
thing
about
mirror.
B
Not
all
blockchains
have
the
ability
to
have
multiple
keys
on
an
account
and,
as
a
result,
this
is
something
that
will
really
make
it
more
flexible
for
d-app
developers
who
are
taking
advantage
of
this
this
type
of
functionality.
The
benefit
of
using
these
types
of
keys
is
that
the
D
app
can
submit
transactions
without
interrupting
your
user
by
prompting
them
the
wallet
to
sign
each
transaction.
That
can
be
done,
that's
possible,
because
these
types
of
keys
can
only
do
specific
things
by
definition.
B
So
you
approve
these
keys
to
be
created
when
you
first
sign
into
the
D
app,
knowing
that
from
then
on,
those
keys
will
be
limited
in
their
scope
and
what
they
can,
what
they
can
actually
do.
If
nobody
can
take
your
funds
with
a
limited
access
key,
so
we
can
do
anything
anything
that
can
compromise
your
account
within
the
access
keys.
So
this
will
allow
the
apps
that
have
multiple
contracts
to
to
easily
facilitate
or
log
into
all
of
those
contracts.
Some
DFS
right
now
are
all
this
themselves.
B
They
actually
have
various
hacks
that
you
can
do
to
try
and
pull
this
off,
but
none
of
them
are
very
seamless.
They
are
they're
all
very
confusing
to
the
user.
The
user
wants
a
nice
easy
to
understand,
sign
in
prompt,
and
it
should
be
formatted
in
a
way
that
makes
sense
for
what
they're
doing
all
of
the
workarounds,
for
this
involve
prompting
the
user
to
sign
transactions
that
may
be
confusing
for
them,
because
it's
not
a
sign
in
transaction.
It's
not
a
sign
in
action.
B
A
Awesome
thanks
so
much
Daryl
for
that
summary
and
yeah,
as
I
mentioned
before,
there
was
a
lot
of
discussion
asynchronously
on
GitHub,
and
we
had
heard
a
lot
of
different
comments,
and
so
there
were
benefits
that
were
raised
and
concerns.
So
we'd
like
to
just
kind
of
summarize
anything
that
Daryl
hasn't
already
mentioned,
and
I'd
love
to
invite
Cameron
to
highlight
some
of
the
benefits
in
more
detail.
Yep.
C
Thanks
Rory
and
thank
you
Daryl,
hey
everybody.
My
name
is
Cameron
Dennis
CEO
of
benue
collective.
We
help
skill
near
in
the
United
States
I
joined
the
ecosystem
about
two
and
a
half
years
ago,
almost
three
now
because
of
the
year's
flexible
account
model
and
this
ability
to
give
access
keys
to
certain
contracts
and
I
think
that
this
is
just
a
prerequisite
to
mass
adoption
to
help
abstract
I
mean
to
be
totally
Frank,
blockchain's,
really
bad
user
experience
away
from
end
users-
and
this
is
a
pretty
huge-
you
know-
upgrade
to
the
ecosystem.
C
So
in
a
nutshell,
this
will
make
it
easier,
as
general
already
explained,
for
users
to
interact
with
many
different
contracts,
but
the
that's
on
the
user
side.
But
on
the
developer
side
it
does
eliminate
the
need
for
a
lot
of
developers
to
initiate
multiple
transactions
and
create
and
check
their
output,
which
is
really
helpful.
So
you
know,
overall,
this
is
a
pretty
straightforward.
Update
and
yeah
I
mean
I'm
super
supportive
of
it.
C
This
obviously,
is
something
that
also
sort
of
is
an
addition
to
a
previous
standard
that
was
already
passed
so
yeah.
This
is
a
very
just
key
for
the
ecosystem.
It's
just
almost
no,
no
issues
with
it
in
my
eyes,
and
hopefully,
oh
and
also
just
to
emphasize.
This
is
also
be
really
helpful
for
the
continuing
development
of
Boss,
widgets
and
components
where
everyone's
going
to
be
sort
of
interacting,
with
like
many
different
contracts
with
this
blockchain
operating
system.
C
For
those
who
not
know
Ilya
has
some
great
threads
on
it
on
Twitter.
Definitely
now
it's
not
the
time
for
me
to
explain
this,
but
this
is
going
to
be
very
helpful
for
users
and
developers
with
this.
You
know
further
rollout
of
the
boss,
so
yeah
in
a
nutshell,
makes
developer
and
user
experience
much
more
straightforward.
D
So
there
was
a
couple
of
concerns,
so
the
first
one
was
that,
like
we
don't
want
to
like
have
gaps,
break
current
ups
that
are
using
the
sign
in
method
to
create
a
single
access
key
and
that
was
resolved,
so
we're
adding
an
additional
method,
as
opposed
to
like
modifying
the
current
method,
to
support
both
operation
modes.
So
that's
the
problem
is
the
first
concern.
D
The
second
concern
was
that
we
wanted
to
scope
it
to
one
account
for
sign
in
multi,
and
the
thing
is
with
this
one:
is
that
like
there
was
so
there
was
two
things
with
that.
The
first
one
was
that
there
was
some
ux
concerns
about,
like
multiple
accounts
being
signed
in
to
multiple
contracts
and
showing
those
like
success
and
failure,
modes
and
stuff
like
that.
D
But
then
they're
all
brought
up
that.
That's
not
actually
a
concern,
because
the
standard
Dependable
token
standard
actually
requires
that
you
add
a
deposit
which
weren't
a
transaction
with
a
deposit.
Wouldn't
you
can't
sign
a
transaction
with
a
deposit
with
a
limited
access
key,
so
you'd
require
a
full
access
key
which
would
require
redirect
to
the
injected
wallet
or
browser
wall
or
whatever,
and
so
that
invalidates
that
concern
so
concern.
One
and
three
are
resolved.
A
This
time
is
that
we
actually
summarize
the
voting
indications
from
the
GitHub
discussion
just
to
make
it
easier
to
sort
of
synthesize
everything
in
one
place
so
based
on
the
the
indications
from
from
the
discussion,
it
looks
like
we
well,
we
need
two-third
majority
to
move
forward
with
the
snap
and
it
looks
like
we
had
complete
approval
just
from
the
discussion,
but
I
guess
I
do
want
to
provide
the
opportunity
now
in
case
there
are
any
other
concerns
or
comments
that
anyone
would
like
to
raise.
Please
feel
free
to
do
so.
B
Just
point
out
that
there
was
a
condition
on
my
approval
there
that
I
do
believe
that
we
should
change
the
signature
to
require
login
for
a
single
account
rather
than
multiple
accounts,
and,
as
Osman
mentioned,
the
the
drawback
of
multiple
accounts.
Is
it's
not
an
atomic
operation
anymore
to
sign
in
with
multiple
accounts
and
also
most
wallets?
Don't
really
have
a
concept
of
one
UI
for
multiple
accounts
being
active.
At
the
same
time,
most
wallets,
you
have
an
active
account
and
you're
signing
transactions.
B
You're
doing
it,
for
that
account
so
being
able
to
approve
for
multiple
accounts,
could
add
a
big
barrier
to
entry
for
wallets
to
actually
implement
this,
because
a
lot
of
wallets
would
actually
have
to
implement
like
some
kind
of
dynamic
account.
Switching
kind
of
thing
flow
in
the
UI
might
not
make
a
lot
of
sense
if
they're
just
running
around
a
single
account,
but
I
just
wanted
to
to
mention
that
that
was
the
thing
that
I
had
brought
up
in.
B
D
I
can
agree
with
that
I
just
like
sign.
The
sign
in
method
also
takes
in
multiple
accounts
so
like
if
we,
if
we
do
go
forward
with
that,
I
think
we
should
update
the
sign
and
Method
to
take
a
single
account
as
well,
which
is
actually
the
currently
implemented
version
of
that
in
near
PHS
as
well.
Selector
86.
B
B
B
A
D
A
D
D
So
we
need
to
add
a
supporting
key
store
for
that
or
for
adopts
to
be
able
to
keep
track
of
the
keys
they
currently
have.
And
then
so
the
wallet
selector
interface
should
add
to
its
interface
like
a
new
method.
Saying
asking
well,
let's
implement
this
as
well
and
and
yeah
the
last
one
is
just
the
top
wallet
teams
to
implement
it.
A
C
A
A
hundred
percent
yeah
Joe
and
Andy-
and
this
is
actually
a
very
good
segue
into
my
next
slide
over
here,
which
is
a
huge
shout
out
to
everyone
involved.
You
know
it
really
we're
we're
trying
to
really
decentralize
how
we
make
decisions,
but
still
there
needs
to
be
some
kind
of
coordination
happening
and
I
think
we
are
all
participating
and
and
leveraging
each
other's
strength
and
context
to
benefit
the
ecosystem.
So,
yes
huge.
Thank
you.
Thank
you
to
the
author
Amir
for
for
writing.
A
First,
you
can
submit
an
idea
using
the
dev
Hub
or
find
other
communities
to
to
to
collaborate
with,
and
if
you
have
a
specific
idea,
that's
technical
that
you
want
to
get
into
the
ecosystem
or
you're
seeking
funding.
You
can
submit
a
net
after
posting,
your
initial
idea
on
the
dev
hub,
and
you
can
also
view
all
of
the
naps
in
their
various
statuses
on
GitHub
and
join
those
discussions.
A
There's
also
a
community
group
that
you
can
join
for
the
near
wallet,
Builder
group
and
that's
a
great
place
to
connect
with
others,
and
you
can
learn
more
about
the
developer
ecosystem
and
the
near
devgov
website
and
our
social
channels,
and
we
look
forward
to
seeing
you
all
on
the
next
calls.
Thank
you
so
much
and
have
a
great
rest
of
your
day.