►
From YouTube: Developer Tooling Community Meeting (November '22)
Description
This week, Jane and David, the PM and EM for Developer Tools as they dive into NEAR Tools Updates, and what the team is cooking up in Pagoda Console!
Wallet Selector Multi-language Support:
👉 https://github.com/near/wallet-selector/blob/main/packages/core/docs/guides/multilanguage-support.md
Wallet Selector V7.2.0:
👉 https://github.com/near/wallet-selector/releases/tag/v7.2.0
NEP-413 - Proposal to Add verifyOwner method to Wallet Standard
👉 https://github.com/near/NEPs/pull/413
--
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
To
a
developer,
tooling,
community
meeting
excited
you
all
are
here
yeah.
If
you're
new
to
this
yeah,
we
are
going
to
do
an
update,
then
we're
going
to
do
an
AMA
at
any
time.
If
you
have
questions
for
us
feedback,
anything
like
that,
go
ahead
and
drop,
it
there's
a
little
q,
a
button
at
the
bottom
that
you
can
ask
us
questions
or
feel
free
also
to
post
in
the
chat
and
I
will
try
to
monitor
both
and
we
will
get
to
those
questions
as
they
come
up
with.
B
B
So
we
got
a
lot
going
on
this
call,
so
hopefully
we'll
get
through
all
of
it,
but
also
want
to
show
some
of
the
stuff
the
tools
team
is
building
for
Pagoda
console,
so
we're
literally
working
on
all
the
tools,
the
wallets
and
console
in
many
different
places
all
right.
So
let
me
try
to
share
my
screen.
Let's
see
if
that
works,.
A
B
You
can
see
it
all
right
perfect,
so
today's
agenda
is
we're
going
to
talk
about
the
Walla
selector
and
then
Dave
is
going
to
talk
about
the
JavaScript,
SDK
and
ABI,
and
then
we'll
switch
on
to
the
cool
things
that
we're
building
in
the
Pagoda
Council,
including
the
deploy
and
the
develop
pipeline,
so
without
further
Ado.
Let's
get
started
so
just
to
reiterate
on
the
tools
team
Vision
we're
here
to
deliver
intuitive,
productive
and
Reliable
Tools,
that's
needed
for
your
web
3
developments.
B
So
what
we're
building
is
one
of
the
JavaScript
stack
at
the
top
layer
is
a
Wallace
selector
which
allows
you
to
integrate
your
d-app
to
a
number
of
different
wallets.
Just
using
a
single
point
of
integration,
a
single
Library,
so
version
7.2
was
released
on
November
7th.
So
we
want
to
congrats
to
the
community,
wallets
well
done,
opto
and
Neath
that
have
been
added
to
the
wallet
selectors,
so
check
them
out
and
if
you
want
to
add
support
for
them
in
your
D
app.
B
So
what
are
we
building
in
upcoming?
So
first,
what's
definitely
going
to
come
out
in
the
next
release
is
a
dynamic
ordering
of
the
wallets
based
on
usage.
So,
as
you
can
see
today,
you
know
there's
a
lot
of
different
wallets
for
the
users
to
choose
from
when
they
pop
up
wallet
selector,
which
you
know
could
be.
You
know
a
lot
of
choices
now.
B
Let's
say
the
user
has
selected
a
specific
wallet,
my
near
wallet
or
you
know,
Ledger,
for
example,
the
next
time
they're
coming
back
to
the
D
app
and
open
up
wallet,
selector
we'd
like
to
show
them
the
ability,
like
that
specific
wallet
that
they
have
logged
in
last
time
at
the
top.
So
we're
introducing
this
ability
for
you
to
enable
an
optimize
wallet
order.
It's
just
really
just
a
simple
Boolean
that
you
can
use
when
you
set
up
wallet
selector.
B
B
Additionally,
what's
really
cool
is
we're
also
detecting
the
wallets
I
installed
in
a
specific
browser.
So,
like
let's
say
this
user
has
a
sender
like
already
in
their
browser
right,
then
they
we
know
their
understand
their
users,
so
actually
that
gets
also
bumped
to
the
top
based
on
what
the
user
is
choosing
like
what
they
have
installed.
So
it
just
makes
this
list
more
digestible
for
the
for
the
end
user.
You
don't
really
need
to
do
anything.
The
Logics
are
written.
B
A
B
A
See
I
see
cool
the
another
question
that
just
popped
up,
which
and
that's
kind
of
on
the
first
slide
that
you
were
talking
about
of
the
individuals
that
added
to
to
wallet
selector.
The
question
just
is
like
what
are
the
requirements:
business,
Tech,
Etc
from
Pagoda
to
be
included
in
this
wallet
selector?
Oh.
B
Yeah,
that's
a
great
question,
so
there
is
a
product
criteria
and
the
security
credit
criteria
there
in
the
contributing.md
on
the
wall
of
selector.
So
like
the
product
criteria,
is
we
basically
release
two
neps
when
describe
the
interface
for
inject
wallets
other
Footbridge
Wallace?
You
must
follow
that
specific
interface.
That
was
actually
a
voted
on
approved
in
the
previous
Wallace
standards
meeting.
So
you
need
to
like
basically
make
sure
that
your
wallet
follows
specific
interface
and
then
for
the
security
criteria.
There's
that's
published
by
our
security
team.
B
So
it
has
very
detailed
requirements
on
what
you
need
to
do
and
eventually
you
need
to
publish
a
like
a
self-declared
statement
of
your
security,
either
on
your
GitHub
repo
or
your
website.
And
then
you
contribute
the
pr
our
team
works
with
you.
It's
a
little
bit
like
a
couple
back
and
forth
and
then
your
PR
is
now
merged
into
Wallace
selector
and
you
become
one
of
the
wallets
supported
in
wallet
selector.
A
A
B
Will
not
recommend
a
wallet
for
you,
it's
a
wallet
that
you've
used
in
the
past.
So
the
first
time
you
see
the
screen.
It's
not
going
to
recommend
anything
to
you.
If
you're
logged
into
a
specific
wallet
on
that
D
apps
contacts,
it
remembers
or
you
log
into
the
next
time
when
you
come
over
here
at
the
app
it
bumps
out
to
the
top.
So
we
don't
do
recommendations,
cool.
A
B
Right,
okay,
so
what
else
is
next?
So
you
know
Wallace
electricity
is
a
really
strategic
library,
because
it's
sort
of
like
a
single
point,
integration
for
the
developers,
but
also
it's
sort
of
when
a
user
is
interacting
with
their
d-app
they're,
going
to
interact
with
this
interface.
First,
pretty
much
so
anir
in
Pagoda,
and
you
know
in
the
ecosystem.
We've
been
talking
a
lot
about
web
2
onboarding.
How
we
can
do
it
I
think.
That's!
You
know
also
mentioned
like
a
lot
of
folks.
B
Users
use
centralized
app
because
they
ease
of
use-
and
you
know
something
a
lot
of
times
in
web
3.
The
user
experiences
do
quite
clunky,
so
we've
been
doing
a
lot
of
thinking
on
that.
So
we
want
to
drive
adoptions
of
near
by
developers
and
make
it
super
easy
for
Di
developers
to
provide
user
with
a
great
interface.
So
now,
if
we
go
think
about
web
2
users,
they
are
not
really
familiar
with
accounts
that
the
keys
accounts.
B
Like
accounts
Keys
Etc,
it's
just
a
social
logging
and
it
works
it's
much
more
analog
to
what
they
have
in
the
web
to
URL.
So
on
the
protocol
side,
you
know,
there's
a
NEP,
that's
published
by
Ilya
about
meta
transactions,
which
is
with
the
end
ago,
of
making
it
really
simple
for
users
to
onboard
so
the
use
case.
There
is
like
a
user
who
can,
like
you
know,
participating
a
d
app
that
does
earn,
does
acts
to
earn.
B
They
will
be
creating
an
account
like
an
actual
account
Unchained
with
ability
to
perform
certain
actions
and
earn
near
and
slowly
that
account
has
enough
money
to
pay
for
gas.
But
in
the
beginning
you
would
have
an
account
that
just
get
you
started
right
now,
the
issue
there
is,
you
know
you
create
an
account.
You
have
no
near
you're
kind
of
being
a
chicken
AG
situation,
so
I
think
the
amount
of
transactions
lunch
which
should
either
be
like
end
of
Q4
early
year
and
our
social
logging.
B
It
makes
so
easy
for
web
2
users
to
be
able
to
use
an
existing
mental
model
to
log
into
the
app
and
just
start
using
the
DF
without
thinking
about
wearing
together,
first
near
to
get
started.
So
we
try
to
make
this
onboarding
first-time
user
experience
so
so
smooth.
So
what
does
that
mean
for
Wallace
electors?
So
Wallace
selector
needs
to
support
web
2
loggings
right.
So
this
is
a
early
design
of
what
we're
thinking
so
I
actually
want
to
show
the
demo
for
what
this
looks
like.
B
C
B
B
So
just
assume
these
wallets
don't
really
support
social
logging
at
this
point,
but
when
they
do
they'll
be
shown
on
this
list
and
when
you
choose
one,
we
essentially
like
to
sign
in
and
create
an
account
in
that
wallet,
and
we
take
you
to
the
stage
where
you
can
like
log
in
for
the
social
email,
for
example.
But
actually
you
know
we
hope
to
support
a
bunch
more
logging
options.
So
all
the
web,
2
social
log
is
that
you
can
imagine.
B
Is
the
need
for
Wallace
to
integrate
the
web
to
onboarding
into
their
wallet
code?
So
we've
done
a
lot
of
you
know,
design,
discussion,
Tech,
design
discussions
around
this
and
the
suggestion
from
our
Tech
lead
is
use
the
web
3
auth
SDK,
so
the
Wallace
would
really
own
the
entire
experience.
You
can
use
the
web3
SDK
using
their
hosted
solution
or
you
can
host
your
own
Solutions
and
effectively
just
be
able
to
use
like
an
oauth
2.0
to
allow
the
user
to
log
in
and
then
the
user
has.
It
has
the
experience.
B
That's
super
intuitive,
so
you
know
I
think
the
web
3
off
we're
going
to
actually
have
another
discussion
with
this
next
week
with
specific
wallet.
Builders
in
the
wallet
Builder
group
call,
but
you
can
check
out
the
docs.
So
if
you're
a
wallet
Builder
and
you
would
actually
like
to
participate
in
web
2
onboarding,
which
I
think
is
a
really
huge
opportunity
for
you
to
gain
users
as
you
know,
but
there
really
is
a
matter
of
transaction
I
highly,
encourage
you
to
look
into
web3,
auth
Integrations
and
build
a
proof
of
concept.
B
B
All
right,
awesome,
so
I
think
one
more
features
to
talk
about
for
the
oh
I
think
I
cover
most
of
the
slides.
So
you
know
if
you
you're
a
wallet.
Builder
now
is
the
opportunity
to
drive
adoption
to
your
wallet
and
the
tremendous
opportunity
that's
coming
up
in
addition
to,
while
the
transition
is,
you
know,
drawing
us
to
onboard
web
2
users
all
right.
So
the
next
thing
that
we're
releasing
on
Wallace
electric
is
localization.
B
So
while
a
selector
has
like
came
a
long
way
from
like
a
baby
Moto
with
just
a
two
wallets
to
a
number
of
different
wallets,
so
now
it's
time
to
get
into
localization.
We
have
Now
supported
Spanish
translation,
so
this
is
live.
It's
based
on
your
browser's
language,
so
Chinese
translation
will
be
coming
out
in
the
next
release,
we're
looking
to
add
localization
for
other
geographies
as
well.
So
if
you
do
can
write
a
foreign
language,
please
consider
submit
or
PR
to
us.
B
A
B
A
Cool
one
of
the
questions
about
the
login:
if
the
idea
is
to
make
blockchain
transparent
for
the
user,
why
not
simply
show
login
with
Google
log
in
with
Facebook
log
in
with
near
log,
in
with
near
takes
Google
Wallet
selector
any
web
2
platform
uses
a
default
wallet,
because
web2
users
will
not
know
which
wallet
to
select
even
the
less
wallet,
even
the
less.
What
is
a
wallet.
C
I
think
I
understand
this
man,
so
I
think
what
he's
asking
is,
why
not
have?
Basically
the
you
get
sort
of
analysis?
Paralysis,
because
you
have
so
many
options
now
Logan
with
near,
would
require
us
to
be
sort
of.
If
we're
doing
a
similar
way
to
like
web
3
off.
Does
it
would
require
us
to
be
sort
of
custodial
with
keys,
and
that
would
put
us
in
a
position
of
power
we'd
rather
not
have
so
the
webview
wallet
has
is
sort
of
a
somewhat
custodial
solution.
C
Would
undermine
the
sort
of
plurality
of
the
ecosystem
if
we
had
a
sort
of
official
near
way
of
looking
in,
because
what
we
want
is
developers
to
come
in
and
make
wallets
and
login
systems
and
all
this
kind
of
stuff
that
do
a
great
job
of
it.
And
you
know
million
flowers
and
people
do
a
much
better
job
than
I
said.
We
just
said
the
near
one:
people
are
just
gonna
use
our
wallet
and
they're
not
going
to
use
any
of
the
other
fabulous
wallets
in
the
ecosystem.
Would.
B
B
Yeah
for
sure,
we're
definitely
like
the
same
thing
goes
into
our
ethos
and
not
like
recommending
I
suppose
we
don't
want
to
play
favors
we're
just
here
to
show
you
different
walls
of
the
app
developer
decides
and
we
don't
want
to
like
say
this
is
the
right
way
to
log
into
a
specific
wallet.
So
that's
not
while
selectors
go
here,
cool
all
right
anything
else
and
if.
B
B
That
could
be
something
that
we
could
do
in
Wallace
lecture
to
like
help
the
Builder
to
like
trigger
a
specific
state
in
which
they
can
have
the
call
to
action
say
like
at
this
point
you
need
to
like
trade
veneer
or
you
need
to
buy
near
using
one
of
those
onboarding
ramps.
So
that's
something
that's
considered!
It's
like
probably
more
down
the
line
when
this
gets
adoption.
B
Okay,
let's
move
to
sorry
I'm
jumping
ahead,
so
let's
move
to
the
NEP
413.
So
this
is
something
that
we
actually
already
published
on.
The
GitHub
is
verify
owner.
I
have
been
mentioning
this
in
previous
calls,
and
now
we're
in
a
pretty
good
State
I
would
say
so
we
really
want
you
guys
to
comment
on
this
NEP
before
it
goes
through
this
formal,
nap
review
and
voting
process.
B
So,
specifically,
like
the
message
is
signed
off
chain.
It's
including
it
just
shows
it's
a
string.
It's
not
a
valid
transaction.
We
don't
want
you
to
accidentally
sign
a
transaction
and
publish
on
chain.
It's
always
signed
with
a
flow
access
key
and
it's
the
signature
should
be
really
easy
to
verify.
B
So
I
don't
have
too
much
of
ad,
because
this
is
going
to
be
discussed
really
thoroughly
at
the
wall
is
Standard
Group
an
EP
call
in
the
next
call.
That's
upcoming,
but
there's
a
lot
of
you
know
comments,
and
so,
if
you're
building
this
you
should,
if
you're
building
a
wallet
or
if
you
care
about
the
interface
to
a
wallet,
you
should
definitely
comment
on
this
on
GitHub
there's
something
else.
B
I
want
to
say
about
this
right,
and
so,
if
you're,
a
wallet
Builder
once
this
nap
goes
through
the
voting
process,
it
becomes
formalized
interface.
Then
it
is
asked
that
you
also
support
this
in
your
wallet.
So
you
can
have
a
verify
owner
method
and
by
the
way,
I
think
it's
already
implemented
in
the
Wallace
selector
I
had
the
NEP,
so
yeah
all
right,
so
now
I
just
hand
over
to
David.
So
he
can
talk
about
the
JavaScript
SDK
API.
C
Yeah,
so
we've
been
getting
a
lot
of
questions
about
the
API
specifically,
why
it's
not
sort
of
being
pushed
out
outside
of
the
console
context.
Right
now
and
from
our
perspective,
the
API-
you
know
sort
of
individual
API
libraries
are
not
the
most
useful
thing
in
the
world.
They're
only
really
useful
when
they're
sort
of
able
to
be
used
across
the
whole
near
ecosystem
and
we're
getting
pretty
close
to
stage
now
where
so,
for
example,
a
Ross
contract
contract,
don't
really
needs
API
into
the
mix
there.
C
C
We
also
have
that
same
API
generation
working
for
any
JavaScript
contract
that
uses
JS,
docs
or
anything
using
the
JS
SDK.
We
also
can
do
typesafe
contract
rules
from
typescript
and
that's
either
in
near
api.js
or
I
was
doing
working
on
getting
working
near
apigs,
and
we
have
it
currently
working
in
the
JS
SDK.
C
We'd
get
widespread
usage
and
then,
once
you
get
a
lot
of
apis
out,
there
it'd
be
very
easy
to
sort
of
peruse
the
kind
of
interfaces
that
any
smart
contract
from
here
is
using
without
necessarily
slowly
understanding
how
it
works
and
sort
of
call
it
in
a
way
that
is,
you
know,
provably,
correct,
so
yeah,
that's
that's!
What's
kind
of
happening
in
ABI
right
now,.
B
So
exciting
cannot
wait
till
we
have
Avis
for
all
the
contrast
in
the
air.
It
would
just
open
up
such
I.
Guess
I
want
to
say
smart
contract
Legos
all
right.
So
this
is
super
cool.
Let's
move
on
to
what
the
tools
team
is
going
to
build
for
Pagoda
consoles
is
you
know,
like
the
Pagoda
console
teams,
building
products
for
popular
console,
but
the
two
scenes
building
a
lot
for
that
as
well,
so
you
may
have
heard
of
specific
features.
That's
wrote
out,
Proto
console
or
will
be
wrote
out
so
now.
B
I
just
want
to
present
this
developer
workflow
important
console.
So
you
know
to
go
to
the
council.
When
you
come
to
the
page,
you'll
be
able
to
see
a
the
Pagoda
templates,
which
is
just
a
a
gallery
of
a
lot
of
different
projects
that
you
can
view.
So
the
projects
would
have
a
smart
contract
code,
either
written
in
JavaScript
or
rest
and
then
on
the
front
end
a
front-end
app
that
communicates
with
the
specific
smart
contract
and
so
from
there.
B
B
So
and
then
you
are
now
inside
the
Pagoda,
Council
and
I
will
show
the
demo
after
this
after
we
go
over
the
flow
and
once
you're
in
the
console,
you
can
see
that
this
the
test
in
that
contract
has
been
deployed
and
view
the
front-end
application,
and
here
in
the
deploy.
You
can
also
then
promote
the
DIA
from
a
staging
environment
to
the
production
environment
and
the
contract
deployed
from
test
to
mainnet.
So
this
is
a
work
pipeline
deploy
pipeline,
that
you
can
reuse,
as
you
add,
and
make
changes
to
your
smart
contract.
B
And
finally,
when
we
have
deployed
your
contract,
you
know
you
can
observe
this
contract
using
many
of
the
existing
features
in
console,
including
view.
The
contract
API
interact
with
this
contract
using
the
ABI
form
view
the
contracts
alerts
and
even
making
into
a
shareable
projects
so
and
also
in
this
workflow,
when
you
Fork
the
GitHub
repo
in
the
future,
we
give
you
the
opportunity
to
load
that
code
in
online
editors.
You
can
make
changes
to
this
code
so
of
all
the
work.
B
B
All
right
so
we're
going
to
Fork.
This
is
the
project
and
then,
at
this
moment,
in
the
deploy
flow,
you're
prompted
to
log
into
GitHub
and
authorize
yourself,
so
we
create
a
fork
of
the
existing
templates
and
I
can
create
a
fork
as
soon
as
the
fork
is
created
that
triggers
a
deploy
on
testnet.
So
now
you're
inside
the
deploy
tab
inside
Pagoda
console-
and
here
you
can
see
that
this
contract
is
now
deployed
onto
testnet.
I
will
present
you
the
time
of
the
last
commit
and
the
commit
hash.
B
They
can
also
open
up
this
front-end
D
app
and
View
and
interact
with
it.
Now,
if
you're
happy
with
this,
you
can
also
deploy
the
same
contract
and
the
app
to
the
main
nut.
So
when
you
click
deploy
to
mainnet,
we
actually
ask
you
to
log
into
the
wallet
selector
because,
as
you
know,
from
Mainland
deploys,
you
will
need
to
pay
for
the
contract,
deploy
and
we're
playing
with
a
few
features
in
the
future,
where
we
can
make
this
payment
nil.
So,
let's
just
say
now
you
log
into
wallet
and
you're
back.
B
We
deploy
the
contract
onto
the
mainnet,
and
now
you
can
see
that
this
contract
is
now
deployed
and
like
the
specific
in
the
hash,
so
you
can
also
interact
and
there's
other
things
you
can
do
here,
including,
oh
wow,
I'm.
Sorry,
all
right
so
view
ABI,
which
is
you
know,
view
the
details.
The
contract
setup
alerts
interact
using
API
form,
so
let's
say
you
want
to
interact
using
API
forms.
B
We
take
you
here
to
this
existing
feature
inside
Pagoda
console
you
can
interact
with
the
existing
contract
on
testnet
on
mainnet
and
yeah,
like
check
out
how
the
contract
can
work.
So
this
is
the
deploy
flow
which
we're
really
exciting
to
be
working
and
collaborating
with
the
console
team,
and
we
hope
is
something
that
you
guys
really
like.
B
B
That's
a
really
good
question,
so
these
smart
contracts
are
going
to
be
made
initially
by
Pagoda
and
therefore
those
contracts
will
be
audited.
So
yeah
we
don't
want
to
issue,
like
contrast,
are
not
audited
to
the
community
and
have
those
contracts
copy
like
100
times.
That
would
not
be
the
go.
So
these
are
the
contracts
from
which
you
can
build
and
add
functionalities
too.
C
This
is
this
is
a
really
cool
part
of
this
feature,
which
is
so
what
you'll
be
able
to
do.
If
there's
a
public
GitHub
repository
is
you'll,
be
able
to
say,
okay
I'm
calling
this
contract,
what
is
the
source
code
of
that
contract
and
that
really
sort
of
opens
up
a
whole
array
of
possibilities
for
the
console
team
we
can
do
stuff
like
if
you
get
a
stack
Trace
out.
Where
did
that
stack?
Trace
come
from
like
what's
the
code
rather
than
just
getting
some
sort
of
blob
of
nonsense.
C
You
know
exactly
the
hash,
you
know
exactly
the
location.
We
have
the
ability
to
sort
of
do
really
sort
of
Now.
Is
it
going
to
be
sort
of
perfect
verification?
You
know?
Is
it
a
decentralized
deterministic
bills?
Initially?
No,
but
you
know
that
Pagoda
is
so
many
baby
trust
who
sort
of
so
it's
we'll
have
a
degree
of
verification.
A
B
B
The
next
thing
where
the
two
is
team
is
going
to
work
on
is
on
the
develop
so
like
basically,
a
really
good
Segway
from
the
previous
question
question
two
questions
prior,
so
you
can
Fork
this
specific
template
and
you
can
add
additional
functionality
so,
like
let's
say
this
isn't
there's
existing
nft
contract
and
you
want
to
add,
like
a
burn
mechanism
to
it.
So
you
can
just
Fork
this
repo
and
it
will
open
up
the
code
inside
an
online
editor.
B
You
can
add
additional
like
a
method
to
your
smart
contract
and
essentially
from
there
you
can
build
your
contract
and
then
we
take
you
through
the
same
workflow
that
we
saw
earlier.
I
can
share
this
again
on
figma
in
one
second,
a
lot
of
figma
files,
all
right
so
in
the
deploy
flow
in
the
develop
flow.
B
You
can
open
up
this
specific
template
in
the
online
editor
and
then
from
there
make
your
changes,
for
example,
and
then
at
this
point
you
can
sign
into
GitHub,
make
your
fork
deploy
to
test
net
logging
to
Wallace
lecture,
deploy
to
mainnet
and
then
be
able
to
interact
your
specific
contract.
So
this
flow
is
really
really
early
and
we're
going
to
take
this
through
user
testing
to
make
sure
that
the
develop
you
know
is
something
that
addresses
your
need.
B
But
one
thing
that
we
do
want
to
do
at
this
point
is
to
make
it
so
easy
to
get
started
and
a
lot
of
developers
when
they
first
start
working
with
near
they
need
to
set
up
a
local
environment,
and
that
can
be
challenging
for
some.
So
this
is
just
a
really
easy
way
for
you
to
play
around
with
the
existing
project
with
minimal.
B
B
Get
part
environment
it
would
be
a
environment
with
its
own.
Backhand
will
allow
you
to
build
the
contract,
but
gitpod.
Isn't
it
isn't?
Well,
it's
one
of
the
possibilities.
I
think
gotcha,
all
right
so
I
think
that
actually
covers
everything
that
we
want
to
talk
about
from
the
dev
developer,
2
team
in
the
November
call.
So
if
you
guys
have
any
questions
happy
to
answer.
A
Cool
well
yeah.
Please
drop
your
questions
in
the
Q
a
button.
If
you
have
any
ask
away
I
guess
we
could
tackle
this
one
question
that
was
asked
earlier.
That
was
a
little
off
topic,
but
the
question
is:
can
you
share
any
news
about
mine,
your
wallet?
Will
it
be
replaced
or
moved
back
to
wallet.near.org.
B
B
A
A
Coming
from
the
tooling
team,
yeah
lots
in
development,
lots
of
lots
of
cool
things
coming
down
the
pipe
yeah
we'll
give
a
minute
or
oh
Jacob
is
here
for
the
giggles
nice
thanks
thanks,
Jacob
I
appreciate
that,
but
yeah
no
I'm
really
excited
to
see
a
lot
of
people
attending.
This
call
I've
had
actually
more
people
in
this
tooling
call
than
we've
had
in
in
our
other
ones.
So
yeah
I'm
super
super
happy
that
y'all
are
showing
up
asking
good
questions
being
engaged.
A
Yeah
absolutely
would
love
to
continue
the
conversation
and
yeah
like
where,
where
can
people
continue
conversation
or
where
can
people
give
feedback
on
on
devtools
team?
It
would
be
like
the
repository
is
the
best
way
to
provide
that
feedback
or
like
how
would
you
like
like
say
the
IDE
you're
requesting
kind
of
feedback
for
that
that
doesn't
really.
B
A
B
C
B
A
Out
to
the
devrel's
team,
there
we
have
office
hours
every
day
near
dot,
org
forward,
slash
office,
Dash
hours
come
talk
to
us
in
person.
If
you
have
any
feedback,
if
you're
watching
this
video
after
the
fact
and
yeah
got
some
got
some
feedback
on
anything
or
any
questions
that
you
have.
We
can
definitely
get
those
to
the
team.
Matthias
strange
that
Vlad
is
in
here,
avlad,
isn't
on
the
tooling
team
anymore.