►
From YouTube: NEAR Explorer Community Meeting (APRIL 2022)
Description
In our first NEAR Explorer Community Meeting, we reviewed the history of NEAR Explorer and a proposal for future changes. Then we hosted a mini AMA and answered community questions from those who joined the call. 🙂
We want your feedback! 💬
Here is a link to the NEAR Explorer Figma design proposal where you can comment and interact with the development team:
👉 https://bit.ly/explorer-proposal-feedback 👈
Register here to join next month's meeting and be a part of the conversation:
👉 http://near.ai/devconsole-explorer-meetings 👈
----
Follow the latest from NEAR Protocol on:
Website: https://near.org/
Discord: https://near.chat/
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near
#Blockchain #FutureIsNEAR #NEAR #nearprotocol #nearexplorer
A
C
C
D
B
B
Our
design
process
has
been
internal
for
a
little
bit
and
now
we're
opening
things
up
and
we're
really
excited
to
involve
the
community.
Since
you
are
the
users,
and
so
this
is.
This
is
the
first
of
many.
Hopefully,
events
like
this,
where
we
can
gather
your
feedback
and
collaborate
with
you
on
the
evolution
of
the
explorer
product.
A
Yeah
absolutely
thanks.
Everyone
yeah,
like
we
mentioned
in
the
announcement
that
I
tweeted
out
and
posted
in
our
community
channels.
It's
going
to
be
a
monthly
meeting,
we're
going
to
talk
about
the
progress
made
with
devconsole
and
explorer,
we'll
talk
about
the
features
that
we're
currently
working
on
and
then
discuss
kind
of
like
the
future
of
these
tools
and
yeah
again,
because
the
community
is
the
ones
that
you
guys
are
the
ones
that
are
actually
using
this
tool.
A
Last
month's,
if
you
guys
were
a
part
of
the
protocol
meeting,
we
had
kind
of
an
async
question
and
answer
format,
but
we'd
also
like
to
invite
anybody
that
wants
to
kind
of
come
up
on
stage
and
ask
question,
live
absolutely:
that's
totally
an
option
for
you.
So
ask
a
question
and
like
there's
a
question
and
answer
portion
at
the
bottom
of
your
screen.
D
D
D
I'd
like
to
say
that
explorer
went
through
a
lot
of
iterations
and
it's
still
an
ongoing
project.
We
started
with
a
very
small
tool
that
could
only
follow
the
very
latest
changes
on
the
network
and,
as
of
today,
we
can
have.
We
have
the
whole
history
of
the
blockchain
sitting
specifically
for
explorer
needs
out
there
and
explore
ui
lets
you
to
explore
whatever
you
find
interesting
about
the
changes,
history
or
basically,
the
the
sky's,
the
limit.
D
In
in
a
couple
of
minutes,
I
want
us
to
to
work
through
what
we
currently
have
and
what
they,
basically,
the
focus
of
our
work
lays
in
so
this
is
landing
page.
You
for
sure
have
seen
it
the
changes
here
yet
to
to
be
visible
in
the
future.
As
you
can
see,
it's
quite
quite
interactive
and
immediately
updates
all
the
values,
but
what
I
we
want
to
focus
on
right,
as
of
today
is
on
the
pages
that
you
usually.
D
Another
poor
part
of
this
page
is
this
list
of
transactions,
and
you
may
actually
notice
when
you
open
some
somebody's
eldest
accounts.
They
are
actually
not
that
easy
to
understand.
My
account
is
as
a
regular
users
is
not
that
complicated.
But
if
you
go
to
foundation.here,
you
can
start
noticing
that
it's,
it's
not
actually
helping
you
much,
because
it
just
says
that
this.
The
only
thing
that
is
happening
on
this
account
is
confirming
something
where
foundations
send
in
a
transaction
to
foundation
confirming
something
not
very
helpful
and
this.
D
What
will
present
you
in
just
a
bit
of
like
what
what
what's
in
there
and
then,
if
you
go
to
some
transaction
page,
you
can
also
see
it's
bloated
with
all
sorts
of
metrics
that
are
super
useful,
but
at
the
same
time,
not
very
readable
so
from
here.
I
want
to
invite
riff
to
jump
in
and
walk
us
through
about
the
future
yeah
rip.
B
A
B
Yep
right
fantastic,
so
what
I
want
to
do
before
anything
is
talk
about
how
we're
all
going
to
collaborate
together,
we're
using
figma,
I'm
not
sure
if
everybody
has
a
figma
account,
but
what
we're
after
this
meeting-
and
you
know
we're
we're
going
to
be
sharing
this
link
out.
We
want
people
to
give
us
inline
comments
and
feedback
on
these
screens
in
specific
locations.
B
So
the
only
thing
that
I'm
that
that
I'm
asking
of
you
is
to
please
create
a
free
figma
account.
If
you
don't
have
one,
we
really
value
your
feedback
and
want
you
to
engage
on
this
next
phase
of
our
design
process.
So
within
the
figma
file
that
we're
going
to
share
out
after
the
meeting,
this
will
always
be
there
some
instructions
on
on
how
to
leave
the
feedback.
B
So
I'm
not
going
to
go
through
every
single
detail,
but
I
do
want
to
talk
about
the
structure
and
the
reasoning
behind
things.
So,
as
you
saw
with
trolls
with
the
the
presentation
of
where
we
are
today,
we
took
a
step
back
and
we
tried
to
build
principles
before
touching
anything
in
terms
of
design
and
those
principles
were
hierarchy,
clarity,
brevity
and
some
guidance
along
the
way.
B
So
let's
leave
those
comments
until
the
next
meeting,
where
we'll
have
a
much
more
focused
effort
on
navigation,
let's
do
everything
from
from
the
header
down,
so
we
we
start
with
some
identicons
and
the
reason
that
we're
proposing
this
is
to
break
some
of
the
text.
Heaviness
of
explore
and
add
some
visual
language
to
kind
of
separate
and
make
things
easier
to
scan
up.
Here
is
basically
the
high
level
metadata
for
that
user.
Like
we
said,
we
want
to
create
some
hierarchy,
so
things
like
balance,
amount
stink.
B
B
Coming
down
to
the
list,
we're
using
a
tabbed
pattern
for
again
pointing
back
to
some
clarity
we
want
and
hierarchy.
We
want
simple
ways
to
organize
all
this
information,
so
some
of
the
ideas
that
are
on
the
horizon
are
being
able
to
display
assets
and
access
keys
and
lock-ups
associated
with
the
contract.
The
activity
is
literally
every
event
that
happens
for
that
account
and
I'll
go
through
the
the
table
here,
and
we
can
take
a
look
at
some
of
the
elements
that
were
that
we're
bringing
forward.
B
So
we
are
prioritizing
the
people
first,
the
the
accounts
that
are
the
accounts
for
each
transaction.
So
from
and
two
we
are
using
a
new
labeling
system
for
transaction
type.
So
that
again,
we
have
an
easy
way
to
scan
and
understand,
what's
happening,
we're
bringing
in
some
iconography
for
tokens
to
understand
what
tokens
have
been
transacted
we're
using
color
to
indicate
balance,
change
and
we've
we're
using
a
very
short
abbreviated
version
of
the
idea,
and
this
has
sort
of
been
a
point
of
contention,
our
first
initial
concept
we
removed
them.
B
We
didn't
see
a
reason
for
them
to
be
there.
We
got
some
feedback
that
from
some
people
and
some
use
cases
where
they
needed
those
things.
So
again,
these
these
are
some
of
the
things
that
we'd
love
your
feedback
on
and
not
really
so
much.
I
like
this
or
I
don't
like
this,
but
the
reasoning
behind
it
and
maybe
a
use
case
indicating
why
you
feel
the
way
you
do
this
stuff
will
really
help
us
understand
some
user
stories
and
and
maybe
some
journeys
that
we
haven't.
We
haven't
worked
into
here.
B
Another
thing
that
we're
doing
that
a
lot
of
explorers
aren't
doing
is
where-
and
this
is
sort
of
the
focus
principle
is
we're
not
making
everything
on
this
screen
clickable.
We
believe
at
least
our
assumption.
Our
hypothesis
is
that
people
are
here
to
navigate
the
explorer
itself
and
not
so
much
bounce
around
something
to
think
so,
as
you
hover
over
these.
B
This
is
one
element
that
will
allow
you
to
click
anywhere
into
a
transaction
instead
of
clicking
on
separate
accounts
or
other
things
of
that
nature
right
down
here,
since
we
do
have
tons
of
batch
transactions
and
they
they
can
range
from
two
to
a
hundred
that
really
blows
up
this
list.
It
makes
it
sort
of
unusable
right.
So
what
we're
trying
to
do
here
again
with
that
brevity
principle,
is
condense
things,
but
also
allow
people
to
understand.
B
B
So
again,
all
of
this
was
done
so
that
you
can
come
back
here.
If
you
forget
any
of
the
things
that
I've
mentioned-
they're
they're
they're
annotated
here-
for
for
you
to
do
a
little
refresh,
a
very
small
sort
of
concept
that
we're
conceptualizing
here
is
the
auto
search.
The
auto
suggests
the
type
ahead.
We
want
people
to
be
able
to
search
quickly,
find
where,
where,
where
who
they're
trying
to
go
to
and
that
sort
of
points
back
to
the
guidance
principle.
B
B
We
see
our
assumption
is
that
we
see
a
need,
especially
when
you're,
at
an
account
with
thousands
of
transactions
and
you're.
Looking
for
specific
things,
we
want
where
our
hypothesis
is
that
users
may
need
to
filter
by
the
accounts
from
and
two
transaction
types
the
amounts
range
of
of
near
tokens
and
the
date
range
as
well
again.
This
is
a
really
great
place
for
you
guys
to
comment
and
tell
us
either.
Why
or
why
not?
You
would
use
a
feature
like
this.
B
That's
really
valuable
to
us,
and
you
can
also
add
things
that
maybe
we
haven't
included
here
different
types
of
filters.
You
would
love
to
see
and
again
please
give
us
the
why
the?
Why
is
the
most
important
thing
we're
looking
for
here,
so
you
can
filter
this
list,
find
what
I'm
looking
for
and
now,
when
we're
clicking
into
the
transaction
detail
we're
using
the
same
sort
of
header
bar
pattern
to
add
that
hierarchy.
B
So
all
the
high
level
details
labels
for
the
state
of
that
transaction,
which
there
could
be
many
the
high
level
up
here
of
this
of
this
data,
the
fees
attached,
the
t
gas
these
are
up
for
this
is
these.
These
things
are
are
are
up
to
you,
guys
right.
We
want
to
understand
what
metadata
is
most
important
to
you
right.
B
The
result,
the
logs
the
balance
change
once
we
go
to
and
these
names
again
the
naming
conventions,
we've
heard
a
lot
from
people
about
these
things
sound
confusing
or
that
we
need
to
better
name
things
again.
This
is
a
place
and
a
time
for
you
to
suggest
such
names
naming
conventions.
Okay,
so
once
we
go
in
to
this
inspect
tab
now
we
see
the
rest
of
this
data
of
that
transaction.
B
Okay,
now
we're
moving
on
to
what
what
a
batch
would
look
like
right.
So
once
we
get
these
really
complex
transactions,
we're
using
an
expansion
pattern
so
that
we
don't
have,
as
we
have
today
this
long
list
of
things
now
you
might
say
I'm
used
to
that,
and
I
like
that
we'd
like
to
hear
why
or
why
not,
and
whether
this
organization
of
the
information
is
actually
much
more
helpful
or
useful
to
you.
Use
cases
are
really
important
to
us.
B
B
Other
ideas,
as
I
had
mentioned
before,
are
what
would
it
look
like
if
I
could
go
and
check
out
the
assets
or
the
access
keys
of
a
specific
account,
and
so
these
are
things
that
we're
working
on.
They
aren't
fully
fleshed
out,
and
so
your
comments
again
are
very
valuable
in
these
in
these
last
couple
screens,
as
well
as
as
we
haven't
focused
as
much
as
we
have
on
the
screens
that
you
previously
saw.
B
So
that's
that
that's
the
these
are
the
screens
that
we
wanted
to
present
to
you
guys
and
again.
I
want
to
sort
of
zoom
out
here
and
go
back
and
remind
people.
It's
really
easy.
You
don't
have
a
figma
account
once
we
share
this
link.
The
first
thing
you'll
see
up
top
is
a
bar
that
says
sign
up
right.
You
have
the
choice
whether
to
sign
up
or
not.
B
A
A
Just
saw
a
comment:
it
says
we
don't
get
to
see
other
people's
chance
or
answers.
Actually
it's
open
everyone.
The
check
should
be
open
to
everyone.
I
haven't
actually
gotten
any
questions
in
the
question
portion.
Yet.
Does
that
just
to
check
in
with
troll
and
sharif
is?
Does
that
conclude
the
the
presentation
part?
Are
we
ready
to
open
it
up
for
any
questions?
Okay,
cool
cool
cool,
yeah,
so
yeah
anybody
that
that
would
like
to
okay?
A
I
see
I
see
a
question
that
popped
up:
real,
quick
but
yeah.
So
what
we'll
do
now
is
we
will
take
any
kind
of
questions
or
comments
that
you
guys
have.
You
can
do
it
either
in
the
chat,
the
q,
a
portion,
it
should
be
a
little
tool
at
the
bottom
of
the
zoom
window
or,
if
you'd
like
to
join
and
yeah.
Just
ask
a
question
with
your
voice
come
up
on
stage
and
do
that
absolutely
it
can
do
that.
A
A
D
D
Right
now
we
went
with
a
simple
one
distinction
between
a
user
and
the
account
with
the
contract
on
it.
So
basically,
you
will
see
either
user
or
contract
label,
but,
what's
indeed
more
important,
is
to
see
the
source
code
of
the
contract
and
that's
going
to
be
a
separate
tab
on
the
on
that
page
account
details
page
where
we
will
pull
in
all
the
available
information
about
the
contracts.
D
Explore
currently
posing
information
about
the
validators
validating
nodes
on
the
validation
notes
page
you
can
see
there
is
a
metadata
with
a
home
page
description
and
a
few
other
and
and
like
country,
all
of
them
are
pulled
from
on
chain
from
the
contracts
from
a
contract
called
named
here.
If
I
don't
remember,
don't
misremember
it
so
yeah.
That's
that's
definitely
on
our.
Rather
though
there
is
no
timeline
yet
for
that
feature,
but
yeah
we'll
definitely
prioritize
it.
A
For
a
question
yeah,
I
think
the
little
follow-up
was
you
can
only
see
the
contract
if
the
owner
has
submitted
it
and
that's
actually,
I
think,
we'll
touch
on
that.
A
little
bit.
You
can
see
the
compiled
wasm,
that's
there,
but
it's
kind
of
hard
to
parse
exactly
what
the
contract
code
is.
So
you
can't
really
view
it,
and
then
I
notice
that
you
mentioned
stuff
like
stat
stack
gallery
and
you
think
that
they're
able
to
see
those
methods
based
on
transactions
made
to
the
contract.
It's
actually
not
correct.
A
The
individual
by
jacob
on
the
education
team,
is
the
one
behind
stat
stock
gallery
and
he
created
a
tool.
It's
like
a
near
contract
parser
that
allows
you
to
actually
look
at
the
wasm
and
it
can
show
the
methods
right
now
that
you
can
call
on
that
contract.
So
it's
actually
not
from
the
indexer,
but
it's
actually
looking
at
the
wasm
and
seeing
oh.
These
are
the
the
methods
that
you
can
call
on
that
individual
contract,
but
yeah
definitely
yeah.
If
you
want
to
ping
me
on
discord,
I'm
josh
pipener.
A
D
D
So
therefore,
rust,
tooling
team
who,
who
are
working
on
nearest
dkrs,
are
building
the
standard
which
will
allow
us
and
other
explorers
other
tooling
to
extract
information
about
the
methods
and
arguments
from
the
wasm
file
just
by
near
sdkrs,
providing
that
facility
by
compiling
that
info
into
the
binary
itself,
so
they
yeah.
That
would
definitely
unblock
us
and
many
other
projects
out
there.
A
Yeah
and
just
to
have
a
shameless
plug
on
that
so
next
week
we're
having
the
protocol
meeting
on
thursday
and
the
following
week
we'll
be
having
the
tooling
team
on
on
board
so
yeah.
If
you
want
to
talk
about
rus
sdk
assembly
script,
sdk,
like
anything
in
our
tooling
portion,
the
third
thursday
of
the
month,
we're
going
to
be
having
a
public
protocol
meeting
and
basically
yeah
every
week
of
the
month.
A
A
D
D
Sure
yeah,
absolutely
I
I
will
take
this
one
as
well,
so
in
initially
so,
let's
start
from
a
bit
of
a
high
level
overview
starting
from
the
blockchain
itself.
Blockchain
is
a
piece
of
technology
that
only
cares
about
how
to
reach
the
consensus
about
the
changes
and
how
to
move
forward.
It
doesn't
optimize
for
querying
the
data
and
optimize
for
like
use
from
the
external
world.
D
It
only
cares
about
how
to
not
get
stuck
and
how
to
make
sure
there
is
no
centralization
point
and
in
order
to
serve
explorer
needs,
we
need
some
tool
that
would
be
able
to
follow,
what's
happening
on
the
network
and
put
it
into
a
storage
that
is
easily
it
can
be
easily
queried,
and
you
know
in
the
ways
that
explore
needs
so
indexer
is.
Is
it
is
this
tool
that
follows
network
block
by
block
and
stores
it
into
right
now
into
a
postgres
database?
D
So
currently
we
have
a
positive
database
that
sits
in
between
from
the
like
in
between
the
blockchain
and
the
explorer
ui
and
serves
all
sorts
of
types
of
requests,
and
you
can
find
them
on
in
excel
for
explorer
project.
There's
even
an
public
shared
access
to
that
positive
database,
read-only,
obviously
where
you
can
yeah
play
with
the
data
as
well.
D
If
you
need
and
on
the
explorer
side,
what
we
do,
we
just
query
and
make
sql
queries
to
that
storage
to
podcast
instance,
and
if
we
need
information
about
transactions
and
stuff
like
that,
like
give
me
10
recent
transactions
by
this
account
id
blockchain
does
not
have
that
facility
to
serve
such
requests
to
you.
But
when
you
store
it
in
a
regular
database,
you
can
do
it
and
that's.
This
is
exactly
what
indexer
does
for
us.
So,
as
you
may
have,
if
you've
been
following
near
for
a
bit,
you
may
have
noticed.
D
I
posted.
Sometimes
announcements
like
there
is
a
downtime
of
explore
due
to
indexer
issues,
and
that
actually
means
that
indexer
got
stuck
for
some
for
one
reason
or
another,
and
it
could
not
put
the
data
into
the
database
and
therefore
explorer
wouldn't
be
able
to
display
that
latest
data,
while
the
the
whole
consistency
and
availability
is
there,
it
just
lags
behind
a
bit,
but
then
it
catches
up
and
everything
is
all
good
hope
does.
A
D
Shameless
plug
here
again,
the
indexer
is
a
separate
team
which
will
have
a
separate
call
later
this
month,
probably
we'll
see
and
it
actually.
As
I
mentioned
it,
it
follows
the
network
with
the
latest
data
and
you
can
do
whatever
you
want.
So
there
is
index
of
framework
that
allows
you
to
implement
your
own
indexer
and
do
whatever
you
want
with
those
blocks
you
can
put
them
on
postgres.
You
can
put
them
on
bigquery,
you
can
put
it.
You
can
ignore
99
of
the
data
and
put
only
certain
items
and
call
webhooks.
D
D
It
needs
to
store
five
recent
epochs
in
year,
which
means
like
two
and
a
half
days
of
data,
and
it
requires
you
to
to
have
a
half
a
terabyte
storage
ssd
drive
to
to
have
it
running,
and
recently
we
actually
launched
a
new
project
called
near
lake.
Nearly
a
system
which
significantly
loads
down,
lowers
down
the
requirements
and
allows
you
to
start
in
just
a
matter
of
seconds
actually
with
your
own
indexer.
D
B
D
A
Yeah,
no
thanks
for
that
plug
yeah,
the
indexer
data
rpc.
All
that
conversations
will
happen
at
the
last
thursday
of
the
month,
so
yeah
first
thursday,
explorer
second
thursday
protocol
third,
thursday,
tooling,
and
then
the
last
one
will
be
indexer
and
data
and
rpc
endpoints
mario,
had
a
follow-up
and
was
just
asking.
A
D
D
The
only
reason
indexers
leaves
is
that
you
can
implement
the
logic
which
will
put
which
will
react
to
the
incoming
blocks
and
do
something
with
them
indexer
for
explorer.
So
there
is
index
of
framework
which
allows
you
to
build
such
indexers,
and
there
are
plenty
of
them
actually
mean
base,
build
their
own
fire
and
blend
their
own,
and
I
know
like
a
dozen
of
those
already.
D
I
just
don't
remember
all
the
names
from
top
I
had,
and
and
after
you
store
those
events
in
some
storage,
you
can
do
whatever
you
want
with
indexer
for
explorer
implementation.
We
put
the
data
into
postgres
and
then
you
can
create
the
podgus
database.
I
do
not
recommend
to
be
honest,
to
run
the
your
own
indexer
for
explorer
foundation.
D
Unless
you
know
what
you're
doing,
because
it
will
require
you
to
run
a
few
nodes,
it
will
require
you
to
have
postgres
instance
so,
and
each
each
node
will
require
archival
node,
not
a
regular
one.
Archival
mode
is
over
seven
terabyte
data
right
now,
and
then
you
will
need
a
storage
for
postgre
database,
which
is
now
roughly
1.5
terabyte.
D
D
Yeah,
let's
mis,
let
me
start
from
the
first
one,
then
how
super
sub
accounts
shown
in
this
ui,
so
each
each
account
is
indiv
like
independent
from
all
the
rest
of
the
accounts.
Even
if
it's
a
sub
account,
the
only
relation
they
had
initially
is
that
their
parents
account
created
the
sub
account
after
it
is
created.
D
D
It's
a
link
drop
contract
which
allows
you
to
which,
which
can
create
new
accounts
underneath
so
whenever,
when
I
went
to
create
for
all.near,
I
actually
used
wallet
which
submitted
a
transaction
in
in,
on
my
behalf,
subsidizing
the
cost
of
creation
of
an
account
to
the
near
contract,
with
request
to
create
fraud.near
with
the
public
key.
That
was
provided
by
from
my
browser.
D
A
D
D
If
it's
deployed
whether
it's
when
was
it
deployed
with
which
transaction
it
was
deployed
or
like
recently
updated,
and
whether
it's
locked
or
not,
locked
meaning,
there
are
no
access
keys
on
the
account
left,
full
access
keys
on
the
account
left,
which
means
there
is
no
way
to
upgrade
the
service
code.
Unless
the
contract
itself
implements
this
logic
of
self
upgrade
which
well
well.
A
A
D
A
Absolutely
thanks
everyone
and
again
we'll
do
this.
Every
month,
first
thursday
of
the
month,
be
talking
next
month,
we'll
be
focusing
more
on
dev
council,
but
definitely
talk
a
little
bit
more
about
explorer
feedback
as
well
and
kind
of
be
a
shared
meeting
and
again
yeah
every
thursday.
We're
gonna
be
having
these
community
feedback
sessions
and
meetings
next
week,
thursday
will
be
the
protocol.
So
if
you
have
anything
for
the
core
team,
bowen's
team
feel
free
to
jump
on
and
chat
with
us
and
again.
A
A
A
C
C
So
everything
we've
been
talking
about
on
here,
explore
dev,
console
or
tooling
things
built
on
top
of
near
actually
are
now
going
to
be
not
necessarily
branded
pagoda,
but
the
company
that
develops
those
is
now
pagoda,
and
so
what
will
we
mention
this
at
the
top
of
the
meeting,
but
you
might
not
have
been
here.
This
is
actually
going
to
be
a
combined
dev,
console
and
explorer
meeting,
and
so
in
the
future.
Actually,
the
very
next
meeting.
I
will
be
talking
more
about
what
exactly
that
is.
C
But
if
you
go
to
pagoda.com,
you
can
check
it
out.
It's
a
tool
that
manages
the
operational
side
of
your
dap,
so
once
you've
got
it
deployed,
you
know
you
want
to
see
some
metrics.
You
want
to
see
a
combined
view,
focused
view
of
your
contracts,
things
of
that
nature
alerts
and
triggers.
I
will
be
talking
about
next
month.
C
Okay,
that
was
great.
I
thought
I
heard
someone
else
speak
yes,
and
you
guys
correct
me
if
I'm
wrong
here,
but
the
difference
between
near
ink
and
near
foundation
is
that
much
like
a
pattern.
You've,
probably
seen
elsewhere
in
the
blockchain
space
like
near
foundation,
is
a
non-profit
that
you
know
handles.
The
community
is
meant
to
like
advance
the
protocol.
C
Things
like
that.
Actually
josh.
You
can
correct
me
if
I'm
wrong
here
near
foundation
handles
like
grants
as
well.
Yeah,
that's
correct,
okay,
yep,
whereas,
like
near
inc
pagoda,
we
are.
We
do
kind
of
two
main
things.
We
build
tools
and
services
on
top
of
near
protocol
and
we
also
are
one
of
the
main
contributors
to
the
protocol
itself.
A
Any
follow-up
questions
we'll
give
it
one
more
okay,
cool.
She
says
thanks
or
heath,
says
thanks.
He
or
she
cool.
I
think
that's
it.
I
think
I
think
we
did
it.
I
think
we
did
our
first.
Our
first
explorer
dev
console
meeting
yeah
again
feel
free
to
drop
us
any
questions
in
chat
and
yeah.
If
we
didn't
answer
any
questions
that
you
have
today
shameless
plug
for
office
hours
deborah,
we
have
them
every
single
day.