►
From YouTube: Protocol Community Meeting (March '22)
Description
The first NEAR Protocol Community Meeting! 🎉
Here we give updates on the protocol development progress, discuss new features being released, and then open it up for a community Q&A!
Join us on 3/10 and every second Thursday of the month @ 3PM UTC.
Register here to join! 👉 http://near.ai/protocol-meetings 👈
Bowen: https://twitter.com/BowenWang18?s=20&t=6XgbaMAVj2taVm1Mrm-38w
Josh Ford: https://twitter.com/thisisjoshford?s=20&t=6XgbaMAVj2taVm1Mrm-38w
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 https://github.com/nearprotocol
#Blockchain #FutureIsNEAR #NEAR #nearprotocol
A
Welcome
everyone
to
the
first
public
protocol
meeting.
My
name
is
josh,
I'm
the
devrel
team
and
we
have
bowen
and
jane
here
as
well
to
kind
of
kick
things
off.
This
is
the
first
time
we're
doing
this
so
it'll
be
an
iterative
process,
we'll
figure
it
out
as
we
go,
but
yeah
you
want
to
introduce
yourself
bowen.
B
A
B
B
B
So
I
still
test
things
out
and
I
didn't
prepare
a
lot
of
agenda
for
today,
so
there
will
be
a
lot
of
time
for
a
free-form
discussion
and
yeah.
If
you
have
suggestions
on
how
we
can
improve
the
format
and
make
it
more
interactive
or
more
engaging
for
for
people
who
are
listening,
feel
free
to
let
us
know
and
yeah,
if
you
can
either
talk
to
me
or
talk
to
to
to
josh
about
it
so
yeah.
So
why
are
we
doing
this?
B
I
think
there
are
a
number
of
reasons,
so
we've
got
this
feedback
that
a
lot
of
the
protocol
development
right
now
is
down
kind
of
in
the
dark
from
the
community
perspective.
People
are
not
really
aware
of
what
we're
working
on,
what
our
priorities
are
and
how
to
contribute
to
the
protocol
development
process,
and
we
would
like
to
to
fix
this
problem.
B
After
all,
this
is
supposed
to
be
eventually
a
community-driven
project
and
we
should
not
just
talk
the
talk
but
also
work
for
work,
and
hopefully
this
is
going
to
be
the
first
step
towards
towards
that
goal.
We
may
not
get
there
immediately,
but
nevertheless
we
want
to
take
it
one
step
at
a
time
and
slowly
getting
more
people
engaged
on
in
the
protocol
development
process,
but
yeah.
So,
regarding
this
meeting,
mainly
we're
going
to
to
do
pretty
much
three
things.
B
B
So
one
caveat
of
mentioned
here
is
that,
since
this
is
a
public
meeting,
we
will
not
be
discussing
anything.
That's
security
related,
for
example.
If
some
security
vulnerability
would
not
be
discussing
them
here
unless
they've
already
been
patched
and
if
yeah.
If
someone
mentioned
the
topic
or
ask
a
question
that
I
think
may
be
related
to
one
of
those
things,
I'd
probably
just
say:
yeah,
it's
not
a
good
place
to
discuss
them.
So
just
keep
that
in
mind,
okay,
so
yeah.
B
Let
me
just
provide
a
high
level
update
on
what
we're,
what
we're
doing,
what
our
current
focus
are
and
so
on.
So
this
is
the
slide
from
town
hall.
I
I
just
want
just
like
reinsert
it
here
in
case
not
everyone
watched
the
town
hall
february
town
hall,
so
so
yeah
just
to
reiterate
our
current
priorities,
so
mostly
around
optimizations
for
stability
and
performance.
B
To
that-
and
I
think
two
important
things
now
working
on
one
is
making
aurora
run
faster.
I
think
ours
still
contribute
to
the
the
most
amount
of
gases
among
all
the
applications
or
all
the
smart
contracts
is
running
on
mainnet
right
now
and
we're
working
with
the
our
team
on
making
them
run
faster.
I
believe
there
are
people
from
the
oral
team.
B
Yeah.
Another
thing:
that's
another
important
thing:
we're
working
on
is
faster
storage,
making
optimizing
for
both
storage
reads
and
storage
rights,
as
they
are
an
important
component
for
most
transactions
on
here.
So,
on
the
other
hand,
yeah,
we
would
like
to
increase
commuting
involvement,
as
I
mentioned
previously.
B
B
B
So
the
the
hope
is
that
this
will
be
a
place
that,
where
we
track
all
the
all
the
protocol
features
that
are
that
are
either
being
developed
or
in
in
in
the
ideation
stage.
Right
now,
it's
not
it's
far
from
complete,
but
yeah
we're
in
the
process
of
iterating
on
it
and
adding
more
things
there
and
right
and
also
right
now.
This
board
is
not
public
and
yeah.
B
I'll
also
work
on
that
to
make
sure
that
everyone
can
get
access
to
to
viewing
the
sport,
oh
yeah.
So
that
aside,
I
want
to
talk
about
what's
upcoming
in
terms
of
protocol
features.
So
so,
let's
start
with
this
waiting
for
release
column.
So
this
essentially
means
that
the
implementation
is
done,
and
it
is
just
in
the
process
of
being
being
rolled
out
to
test
the
mainnet.
So
this
this
thing
here
in
christmas,
max
gas
burned
to
300
turkeys.
B
B
There
are
many
reasons
for
that,
but
one
of
the
reasons
is
that
we've
now
observed
more
and
more
expensive
transactions
or
our
applications
that
want
to
perform
more
expensive
operations
in
a
single
transaction,
and
previously
the
limit
of
200
tera
gas
sometimes
isn't
sufficient,
and
there
is
a
need
for
having
more
capacity
in
a
single
transaction
and
that's
especially
important
for
aurora,
but
also
for
some
other
large
applications
that
sir,
that
is
also
important.
So
we've
made
this
change:
it's
already
live
on
testnet
and
it's
going
to
be
live
on
main.
B
B
So
that's
essentially
a
inefficient
or
rather
not
ideal
way
of
charging
gas
because
the
execution
from
the
point
of
view
of
the
exclusion,
that's
totally
fine
and
nothing
wrong.
Just
that
the
way
we
charge
guys
does
not
really
correspond
to
the
amount
of
computation
we
do
so.
This
will
fix
that
and
we
actually
expect
that
this
would
give
a
pretty
significant
boost
to
a
lot
of
transactions
on
here,
especially
those
that
involve
storage,
a
lot
of
storage
operations.
B
So
this
out
beyond
108
support
is
essentially
cryptography,
cost
functions
that
would
provide
support
for
for
private
transactions
on
here.
So
once
this
is
enabled,
I
think
we
can
yeah.
The
use
cases
for
private
transactions
would
mostly
be
unblocked
and
yeah.
Finally,
there's
this
feature
of
splitting
unused
gas
across
promises.
What
it
does
is
that
today
there
is
a
common
pattern
that
let's
say
you
have
a
function
call
and
then
it
would
generate
further
function.
B
The
problem
with
that
is
that
well,
first
of
all,
you
need
to
to
find
those
numbers,
and-
and
it's
not
easy
to
it's-
not
always
easy
to
to
estimate
how
how
much
gas
you
need
to
attach,
and
also
because
the
amount
of
gas
a
transaction
can
a
receipt
can
consume
also
sometimes
depends
on
the
state,
so
that
is
actually
changing
and
having
a
static
number.
There
isn't
always
the
best
option.
B
So
what
this
does
is
that
it
would
allow
developers
to
specify
like
a
weight
on
each
each
of
the
promises
created.
It
was
seeing
the
function
call
so
that
it
would
automatically
just
distribute
unused
cash
within
the
function.
Call
to
towards
those
promises
it
doesn't
it
doesn't.
It
doesn't
change
the
kind
of
current
behavior.
B
You
can
still
attach
a
a
fixed
amount
of
gas,
just
in
addition
to
that,
you
can
also
specify
how
you
distribute
the
remaining
cash
so
that
that
would
be
add
on
top
of
the
static
amount
that
you
attached
to
a
function
call
so
hopefully
that
would
make
it
easier
for
developers
to
write
smart
contract
and
not
worry
about
their
smart
contracts
being
broken
one
day
if
something
changes
on
the
product
side
or
the
state
gets
larger
in
their
small
contract
yeah.
So
basically
that's
kind
of
what
we're
currently
focusing
on.
B
Then
there
are
a
bunch
of
things
in
the
backlog
that
maybe
we
can
discuss
if
people
have
questions-
and
there
are
obviously
more
that
should
be
added
but
yeah-
that's
kind
of
the
current
state
yeah
and
I
think
that's
yeah.
It's
all
for
the
presentation
part,
and
ideally
there
should
be
a
section
where
we
discuss
new
protocol
features.
But
since
this
is
the
first
meeting
I
didn't
actually
I
don't.
A
Yeah,
there's
there's
a
couple
questions
in
here
and
again,
seeing
that
this
is
the
first
time
we're
doing
this,
we'll
kind
of
go
through
the
questions,
and
maybe,
if
it
becomes
kind
of
more
of
a
back
and
forth,
we
can
bring
them
on
the
bring
it
bring
bring
that
individual
on
the
panel
and
they
can
discuss
it
with
you.
The
first
question
we
had
guest
fees
are
increasing
because
of
increased
space
and
time
complexity
of
operations
on
aurora
as
more
daps
are
created.
With
the
fees
keep.
B
A
A
A
B
B
That's
a
great
question,
so
some
so
the
max
burnt
gas
is
essentially
the
maximum
amount
of
gas.
You
can
burn
in
a
single
execution
of
a
single
receipt,
but
the
maximum
attached
cash
is
the
the
maximum
amount
you
can
attach
to
a
single
transaction
which
may
result
in
multiple
receipts.
So
previously
the
maximum
amount
you
can
attach
is
300,
but
the
maximum
it
can
spend
on
one
single
receipt
is
200,
so
there
is
a
discrepancy
there,
which
means
that
previously
you
can
that's
300.
B
A
A
B
A
A
Yes,
cool,
that's
that's.
That
seems
to
be
all
the
questions
so
far.
If,
if
anybody
else
has
any
questions,
we
have
a
bunch
of
time
left,
but
if
nobody
else
has
anything
else
to
ask,
we
can
we
can
oh
another
one
came
in.
Is
it
possible
to
attach
a
fungible
token
in
contract
method?
Calls
yeah
like
an
attached
deposit,
yes,
yeah.
B
B
Yeah
damien
has
a
question,
though
he
didn't
ask
in
the
q
a
yeah,
so
yeah,
that's
a
good
question.
I
would
say
no
because
because
because
of
the
focus
of
the
team
I
mean,
if
the,
if
the
focus
of
the
team
isn't
sorry
on
performance
and
stability,
then
we
would
actually
push
for
phase
one
of
charting.
Then
there
wouldn't
be
a
need
to
do
anything
in
the
meantime
right.
So
that's
not
it's
not
that
we
view
that
is
not
important
thing.
B
It's
a
question
for
the
aurora
team:
actually
we
do
have
some
one
from
the
oral
team
here
it's
to
come.
Maybe
you
can
yeah,
I
mean
that's,
not
the.
This
is
not
the
best
medium,
but
not
the
best
meeting
to
answer
that,
but
like
things
since
the
question
is
already
asked,
we
might
as
well
try
to
find
a
way
to
to
answer
them,
but
yeah
in
the
future
for
bridge
is
just
not
there.
A
A
B
How
was
300
targets
limited
yeah,
so
the
the
short
answer
is
that
it's
it's
decided
somewhat
arbitrarily.
It's
not
entirely
arbitrary.
The
reason
is
that
we
don't
want
to
change
the
the
maximum
gas
at
attack
allowed
to
be
attached
to
a
single
transaction,
and
that
is
300
targets
so
yeah,
because
we
because
we
don't
want
to
make
the
the
change
very
invasive.
B
We
just
wanted
to
draw
something
quickly,
so
we
just
changed
the
max
gas
burnt
to
be
300
so
that
yeah
nothing
else
needs
to
be
changed
and
and
yeah
there's
another
concern
which
is
like
if
we
increase
the
number
even
further.
Let's
say
we
also
obviously
don't
also
need
to
increase
the
maximum
max
gas
attached.
Then
then,
there
is
a
concern
that
you
know,
because
this
essentially
only
goes
one
way
you
it's
pretty
much.
You
cannot
lower
it
again
because
then
you
potentially
break
contracts.
B
The
concern
is
that
if
there
is
some
some
like
undercharging
that
people
that
potentially
attackers
can
exploit,
then
if
we
cannot
lower
it,
then
other
than
that
means
that
the
wiggle
room
it
becomes
smaller
and
potentially
the
which
basically,
that
means
we
cannot
lower
the
the
block
gas
limit
below
below
what's
allowed
for
a
single
transaction.
Otherwise
there
would
be
transactions
that
cannot
be
fitting
in
one
block,
so
there
are
some
concerns
there.
B
Yeah
good
question:
I
don't
think
the
step.
It
depends
on
what
you
mean
by
stability.
If
you
mean
the
kind
of
security
of
the
network,
then
this
actually
not
affected,
because
in
phase
1
of
sharding
block
block
producers
would
still
validate
all
the
shards
and
the
trunk
only
producer
wouldn't
actually
sign
in
blocks.
So
the
security
of
the
network
should
pretty
much
be
the
same
if
you're
talking
about
stability.
Otherwise
I
mean
yeah
a
good
question,
but
we
will
make
sure
that
the
stability
wouldn't
degrade
before
we
revolve
the
change.
B
Yes,
but
that
that
is
outside
of
the
protocol,
I
think
the
liquid
staking
initiative
is
definitely
one
of
them.
Essentially,
the
liquid
sticking
pool
like
would
rebalance
the
the
stakes
among
among
our
auditors,
and
would
I
think
it
would
do
something
that
would
essentially
stake
to
validator
with
lower
stake
and
so
on.
So
but
yeah
that's
outside
of
the.
I
was
the
other
side
of
the
scope
of
this.
A
B
I'm
a
bit
confused
by
the
question
to
be
honest,
because
I
believe
today
we
also
support
docker.
There
is
a
document
like
compose
you
can
you
can
use
to
run
on
your
core
and
we
even
publish
a
docker
image
on
our
docker
hub,
so
yeah
not
sure
what
the
question
is
about.
Maybe
if
you're
going
to
clarify
a
bit
more.
A
A
B
Sure
yeah,
I
would
say
there
isn't
anything
super
concrete
right
now
as
a
proposal,
I
think
I
think
there
was
a
forum
post
that
I
think
was
written
by
max.
That
summarizes
the
situation
and
also
the
approaches
we're
taking.
Maybe
we
should
how
about?
Let
me
just
quickly
try
to
find
us
and
send
a
link
here.
A
A
B
A
B
A
A
Yeah
absolutely
and
then
feel
free
to
ping
me
on
discord
as
well.
I
can
drop
my
discord
link
in
here
or
just
ask
in
like
the
the
community
channels
for
some
clarifying
questions.
If
whatever
answers
you,
you
don't
have
or
you
didn't
get
any,
you
know
answers
out
of
the
presentation
that
we
did
give
but
yeah
this
the
recording
tozilla's
have
been
asking.
This
is
being
recorded
right
now.
A
A
B
B
A
Yeah
on
the
on
the
devrel
side,
documentation
is
something
that
we're
actively
working
on
to
consolidate.
It's
definitely
been
something
that
we
are
recognizing,
that
we
have
kind
of
our
documentation
everywhere
and
we're
looking
to
create
little
areas
that
are
more
discoverable
and
yeah
working
with
the
foundation
on
the
wiki
end.
A
If
you
have
any
questions
about
how
to
develop
on
near
even
like
protocol
questions,
we
might
not
necessarily
have
the
answer,
but
we
can
definitely
reach
out
to
the
team
and
help
field
or
answer
any
of
those
questions
that
you
may
have
feel
free
to
drop
in.
We
do
it
every
day.
I'm
actually
doing
it
twice
a
day
now
once
in
the
morning.
A
Well,
it
depends
on
what
time
zone
you're
in
so
one
that's
more
caters
towards
the
european
africa
and
asian
time
zones
and
then
one
that's
more
for
the
americas.
I
will
type
out
the
there's
a
link
from
bowen
on
your
question,
but
I'll
type
in
office
hours
link
feel
free
to
click.
On
that
link.
You
can
see
what
times
that
we
have
our
office
hours
twice
a
day
and
you
can
there's
a
link
to
excuse
me.
A
Add
it
to
your
calendar
and
yeah,
that's
in
discord
under
the
office
hours
channel
in
the
development
section,
so
anybody
on
call
that
would
like
to
ask
any
further
questions
or
comments.
Any
yeah
feedback
from
today's
session
greatly
appreciated
but
yeah.
I
haven't
seen
any
other
questions
come
in,
so
maybe
we
could
wrap
it
up
a
little
early
yeah.
This
is
this
has
been
a
great
great
start.
I
I
think,
really
really
enjoy
yeah.
I
think,
like
yeah
you're
welcome
yeah.
A
I
am
too
looking
forward
to
these
sessions
each
month,
it's
cool
to
get
to
pick
the
core
team's
brain
a
little
bit
and
ask
questions
as
they
come
up
and
then
yeah.
Maybe
we
can
gather
some
feedback
from
you
guys,
maybe
I'll
send
an
email
out
to
all
those
people
that
registered
and
see
kind
of.
You
know
how
you'd
like
to
see
this
meeting
shape
up
as
we
move
forward,
but
yeah
any
parting
words
bone.
B
Yes,
thanks
everyone
for
joining
and
yeah,
we
will
definitely
iterate
on
the
on
the
process,
iterate
down
the
format
of
the
meeting
and
know
that
this
is
definitely
not
perfect.
The
first
time
we're
doing
it
so
but
yeah,
that's
you
know
we
have.
We
have
to
start
somewhere
and
yeah.
I
hope
that
in
the
future,
it'd
be
more
engaging
and
there
will
be
more
discussions
in
this
meeting,
but
yeah
thanks
josh
for
for
helping
hosting
the
meeting
and
and
also
help
with
everything
around.