►
From YouTube: Protocol Community Meeting (April '22)
Description
This month we discussed best practices for creating a NEAR Enhancement Proposal (NEP) for the protocol. https://github.com/near/neps
Want to take part in next month's meeting?
Register here to join! 👉 http://near.ai/protocol-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 https://github.com/nearprotocol
#Blockchain #FutureIsNEAR #NEAR #nearprotocol
A
A
So
he
has
a
lot
of
thoughts
on
what's
the
process
to
proposing
a
new
standard
and
so
on
so
forth.
So
we're
going
to
kind
of
have
a
discussion
on
like
how
how
to
kind
of
combine
that
with
the
process
to
proposing
new
protocol
features.
And
then
maybe
there
are
some
differences,
and
I
hope
hopefully
it's
going
to
be
an
interesting
discussion
and,
of
course,
we'll
have
time
for
q
a.
C
I'm
jay
I've
been
working
with
pagoda
for
about
six
weeks
now,
just
kind
of
thrown
into
the
standards
deep
in
I
come
from
the
enterprise
software
development
world
so
spent
my
good
share
time
working
for
the
big
guys
like
oracle
and
dell.
I've
also
had
some
pepperings
of
of
startups
way
back
in
the
day.
Super
super
excited
to
kind
of
dive
into
this
this
project.
I
really
think
that
this
platform
represents
kind
of
the
version
3.0
of
blockchain.
So
yeah.
A
This
was
because
that
we
observed
that
some
instability
around
violators
missing
blocks
at
the
beginning
of
the
epoch
and
that
actually
persisted
for
a
period
of
time
which
led
us
to
thinking
that
we
should
focus
our
time
and
effort
on
figuring
out,
what's
going
on
and
prevent
things
from
happening
again.
So
I
just
want
to
provide
the
community
with
an
update
on
that.
So
we've
basically
formed
a
special
work
group
to
tackle
this
problem.
A
A
So
I
think
we've
made
a
very
good
progress
and
we
figure
out.
There
are
a
couple
causes
to
the
to
the
problem
that
we
observed
that
caused
value
to
the
missed
blocks.
At
the
beginning
of
epoch.
We
will
have
some
mitigation
strategy
implemented
and
or
some
of
them
are
fully
fixed.
So
so
we
started
resuming
the
release
process
and
it's
basically
going
to
resume
next
week.
A
So
I
think
next
wednesday
we're
going
to
have
the
tesla
release
for
1.26
and
then
four
weeks
afterwards,
we'll
have
the
release
for
for
mainnet
and,
as
I
said,
we
added
a
lot
of
observability
improvements
so
so
going
forward.
It
should
also
be
easier
for
us
to
understand
the
cost
of
problems,
so
they
occur
so
yeah.
That's
basically
the
updates
on
this
side.
I
think
that
has
been
pretty
much
our
focus
for
the
past
months.
A
I
would
say
and
charge
if
you
go
to
the
next
one
yeah,
so
just
kind
of
giving
an
update
on
what
we're
working
on
on
the
protocol
features.
So,
as
you
can
see
the
the
change
that
increased
maximum
gas
burns
has
already
been
released,
so
it's
not
fully
life
and
yeah.
It
basically
allows
for
more
capacity
in
a
single
transaction.
A
If
people
need
to
need
to
run
some
expressive
transaction
that
consumes
more
gas
than
what
was
previously
allowed
and
what
is
in
the
pipeline,
what
we're
currently
working
on
is
this
outbn128
support
that
would
allow
us
to
have
private
transactions
on
mainnet,
which
is
great,
or
I
mean
it.
It
by
itself
doesn't
directly
allow
that,
but
it
provides
the
crypto
primitives
for
people
to
build
private
transactions
split
on
used
cash
across
promises.
A
I
think
pretty
much
the
same
things
with
kaifeng
trying
those
that
already
talked
about
last
time
that
allowed
it's
an
optimization
that
would
allow
us
to
save
safeguards,
for,
I
would
say,
most
of
the
transactions
that
the
touch
storage,
either
storage,
reader,
storage
right
so
yeah.
That's,
basically
the
the
update
on
on
the
protocol
side-
and
I
I
guess
yeah.
B
Let
me
know
I'm
monitoring
both
the
chat
and
the
q
a
section
and
we
can
go
ahead
and
bring
you
on
stage.
So
you
can
ask
your
question
via
voice,
but
yeah
feel
free
to
drop
something
in
the
chat.
If
you
are
interested
and
participating,
I
guess
one.
One
question
would
be
you,
you
talked
about
the
release
schedule
and
that
we're
resuming
it.
Could
you
just
go
over
briefly
what
the
release
schedule
is
as
far
as
testnet
and
mainnet
and
with
the
regular
cadences.
A
Yeah
so
so
I
think
there
is
actually
a
blog
post
that
I
can
suggest
people
read,
but
basically
there
is
a
five
five
week
release
schedule
that
we're
following
right
now,
so,
basically,
four
weeks
between
tests
and
the
main
night
and
then
after
the
midnight
one
week
after
the
midnight
release,
it
would
be.
The
next
would
be
the
next
test
that
we
do
so
I
can
post
this
link.
B
Yeah,
I
have
a
few
questions:
they're
more
general
questions,
not
necessarily
pertaining
to
what
we
just
covered.
So
I
think
I'm
going
to.
Maybe
we
will
move
on
to
the
next
topic.
We'll
talk
about.
I
believe
the
next
oops
yeah
feature
proposals.
Yeah,
we're
gonna
have
a
discussion
around
how
you
can
propose
an
np
and
then,
after
that,
we'll
open
it
up
for
the
ama
general
questions.
A
B
B
A
A
B
A
Yeah
so
yeah,
so
I
think
this
is
something
that
people
are
very
interested
in,
since
we
kind
of
talked
about
last
time
that
we
want
to
move
towards
a
more
community-driven
development
process,
and
this
is
an
important
part
of
that.
As
being
so,
we
have
to
have
a
way
for
anyone
in
the
community
to
propose,
propose
new
features
or
improvements
to
the
protocol,
and
it
shouldn't
just
be
one
single
team.
A
A
So
let's
say
you
are
someone
who
is
interested
in
proposing
a
new
protocol
feature,
so
the
first
step
is
essentially
drafting
an
ap
pull
request.
So
I
think
j
worked
out
a
very
nice
template
which
we
can
present
later
on.
But
essentially
it's
a
somewhat
standard
rrfc
process
that
you
kind
of
describe
what
the
feature
you're
proposing
is
and
have
some
detailed
description
of
what
problem
you're
trying
to
solve
and
and
how
the
the
new
feature
works
and
then
how
it
works.
A
On
the
on
the
reference
level
on
the
project,
respect
level
and
then
at
the
same
time,
to
kind
of
to
kind
of
both
act
as
a
civil
resistance
prevention
and
then
also
as
acting
as
a
way
to
to
ensure
that
people
giving
enough
salt
into
into
their
proposal.
We
also
ask
people
to
actually
provide
a
prototype
implementation
when
they
provide
the
draft
and
ap
pull
request.
A
A
We
will
do
like
a
basically
a
final
check
in
english
meeting
that
I
think
we
can
discuss
how
exactly
we
want
this
to
to
happen.
But
presumably
the
the
proposed,
the
proposer
of
the
feature,
will
do
a
presentation
and
then
to
see
if
there
are
any
final
objections
and
then
we
can
essentially
make
the
decision
of
having
this
feature
or
like
approving
this
feature
in
this
meeting.
So
that's
kind
of
the
process
I
had
in
mind.
A
It's
definitely
not
perfect
or
it's
very
far
from
perfect,
but
but
I
think
we're
trying
basically
trying
to
balance
allowing
us
to
still
move
fast
and
also
allowing
people
anyone
in
the
community
to
have
the
ability
to
contribute
to
the
protocol
so
yeah.
I
think
I'll
just
pause
here
and
then
let
jay
speak
to
the
process
that
he's
working
on
on
on
the
contract,
standard
side
and.
C
Yeah,
that's
thanks
bo
and
that's
really
good.
I
was
so
part
of
my
goal
here.
I
kind
of
initially
came
in
here
from
the
contract
standard
side
right
trying
to
attack
things
from.
I
guess
the
application
side
or
standardization
of
applications
and
one
of
the
things
that
that
sort
of
was
different
right
off
the
bat
between
protocol
and
standards
was
the
implementation
of
a
prototype.
C
So
I'm
super
happy
on
point
two
to
see
you
to
actually
want
to
have
a
prototype
implementation
as
part
of
the
the
early
process,
because
I'm
like
a
very
strong
believer
and
show
me
the
code
early
right,
that's
awesome!
So
I
don't
know
if
that,
what's
the
best
way
for
me
to
present
this
just
take
the
screen
over
and
show
you
guys
the
nep
repo,
maybe
and
go
through
that
yeah.
B
And
bone
just
to
clarify
so
as
far
as
like
the
nep
process
moving
forward,
I
know
we've
had
kind
of
sometimes
started
in
the
governance
forum
and
having
you
know,
conversations
there
and
then
they'll
also
migrate
to
nep.
You
kind
of
want
to
consolidate
things
like.
If
someone
has
a
proposal,
let's
just
start
and
draft
that
proposal.
A
Oh
yeah,
that's
actually
yeah.
That's
a
great
point
josh.
I
think
here
I'm
more
talking
about
the
essentially
the
formal
part
of
the
process.
But
of
course
you
know,
we
still
very
much
welcome
discussions
on
the
on
the
governance
forum
and
then,
if
you
look
at
how
how
the
rush
rpg
process
work,
they
actually
kind
of
encourage
this
pre-rfc.
A
That's
not
really
really
like
formally
part
of
the
the
process,
but
they
encourage
people
to
you
know
just
discussing
proposed
ideas
on
the
forum
and
then
once
they
get
to
a
stage
where
they
feel
that
you
know
they
have
enough
confidence
to
formally
propose
a
new
feature.
Then
you
kind
of
move
to
the
this
formal
process.
Oh
chasers
disappear.
B
B
A
B
Cool
awesome
all
right,
let's
see
well
wait,
wait
a
second
for
jay
to
join
ravi.
I
see
that
you
asked
a
question
that
you're
stuck
on
nfts
near
blockchain
and
you
need
some
help.
You
can
this
that
actually
would
be
handled
by
my
team.
The
devrel
team
feel
free
to
ask
that
question
in
dev
support
on
discord,
and
one
of
my
teammates
can
help
you
out
with
that.
B
But
if
you'd
like
in
a
couple
hours
at
11
pm
pacific
we'll
have
office
hours
where
you
can
ask
this
question
live
and
actually
share
your
screen
and
yeah
a
team
of
deborah
individuals
and
community
members
will
be
on
that
call,
as
well
so
yeah
and
in
discord
office
hours
in
about
two
and
a
half
eight
yeah
three
hours,
ish
11,
pacific
time,
yeah
there
yeah
thank
thanks,
drew
for
posting
that
yeah
feel
free
to
join
and
get
some
support.
There.
B
Hosting
panelists,
yes,
true
yeah,
can
you
can
you
post
to
everyone?
You
did
just
post
the
hosts
and
pounds,
but
yeah
near.org
forward,
slash
office
dash
hours
is
a
great
place
to
check
out
all
the
different
support
live
events
that
we
have
but
yeah
go
ahead,
see
your
back
jay.
Do
you
have
screen
sharing
permissions?
B
B
C
Okay,
so
like
the
sort
of
side,
I
guess
my
corner
of
the
universe
is
in
this
nep's
directory
or
any
piece
repository.
Rather
I'm
sure
most
of
you
guys
are
familiar
with
it.
It
looks
like
it's
been
around
quite
a
while,
and
so
I'm
kind
of
taking
on
the
role
of
just
trying
to
get
my
arms
around
everything
and
and
sort
of
funnel
the
process
and
optimize
the
process
a
little
bit,
and
so
I
guess
the
first.
C
My
first
sort
of
order
of
business
was
to
try
to
collate
the
different
specifications
that
we
have
in
place
already
and
figure
out
a
way
to
create
a
standard
of
standards.
So,
following
a
similar
model
as
the
the
pip
bitcoin
and
ethereum
model,
I've
created
a
purpose
and
guidelines
document
which
is
a
living
document.
Bowen.
That's
that's
the
way
to
do
it.
If
you
don't
wanna,
get
yourself
out
of
corners,
just
just
label
it
as
living,
and
then
you
can
always
just
change
it
right.
C
C
Slash
near
that'll
be
responsible
for
accepting
and
rejecting
draft
proposals,
and
the
idea
is
to
be
as
fast
as
possible
there
right.
We
don't
necessarily.
I
don't
think
we
necessarily
want
to
have
drafts
sitting
up
on
a
pull
request
for
years
on
end.
I
know
that
a
lot
of
processes
do
that.
I
know
eip
does
that
I've
been
in
that
process.
As
an
author,
unfortunately-
and
I
know
that
there
are
speaking
with
alexi
there's-
there
are
other
processes
that
kind
of
struggle
with
that,
with
specifically
the
rust
rfc
process.
C
So
what
I'm
proposing
is
that
we
try
to
kind
of
and
try
to
snip
that
off
as
fast
as
possible.
Right.
You
know
put
things
into
a
rejected
mode,
and
then
authors
can
kind
of
amend
and
get
it
back
into
draft
if
required
or
just
leave
it
rejected,
and
then
we
kind
of
move
it
along
into
a
review
process
for
a
couple
weeks
slot
up
to
two
months,
I
haven't
really.
C
We
haven't
really
determined
the
length
of
the
time
yet
put
it
into
a
last
call
state
and
then
finally,
into
into
a
finalized
state.
So
that's
kind
of
the
50
000
foot
view
of
what
what
I'm
thinking
about
for
the
nep
process
state
and
then
I
just
get
into
like
what
doesn't
any
successful
nep
look
like
so
the
difference
sort
of
that
I've
I've
added
to
this
process
from
from
the
way
we
were
previously
doing.
It
is
I'd
like
to
have
these
rfc
822
style
headers.
C
It
really
really.
You
know
it's
a
standard
way
to
do
things
and-
and
it
also
allows
authors
to
have
their
name
on
an
np
which
is,
I
think,
is
a
very,
very
important
thing,
and
then
we
just
go
through
the
list
of
different
sections,
and
I
I
think
most
of
you
guys
have
seen
this
there's
a
template
for
all
the
all
this
stuff.
Just
I
guess
the
most
important
or
one
of
the
most
important
additions
as
well.
C
Is
this
reference
implementation
section
and
that's
what
I
was
sort
of
speaking
to
bowen
before
I?
I
also
believe
that
you
know
show
me
the
code.
Let's,
let's
see
how
this
thing
works,
that
you
know,
contracts
are
code
right,
so
you
often
don't
aren't
able
to
figure
things
out
without
actually
giving
it
a
shot
first
right.
So
definitely
a
believer
in
that
and
I've
also
added
the
security
implications
section.
C
C
Okay,
yeah,
okay,
perfect
and
then
I
just
get
into
a
bunch
of
how-to's
and
I'll.
Just
show
you
one
more
thing.
Importantly,
I
guess
we've
got
this
nep
template
that
just
kind
of
kind
of
kick
starts
things
right
gives
you
a
template
of
how
to
create
a
new
ndp
I'd
like
to
flush
this
out
further
and
I'd
like
to
really
work
with
with
you
bowen
and
maybe
create
one
for
a
good
example
for
what
a
protocol
would
look
like
protocol
level.
C
C
C
B
C
C
A
A
Yeah,
that's
a,
I
think,
that's
a
great
question
from
my
perspective
for
the
pro
school.
I
think
what
we're
going
to
do
is
that
we're
going
to
form
a
committee
and
initially
it's
probably
going
to
be
going
to
be
some
some
people
from
pagoda
and
we're
probably
going
to
looking
to
decentralizing
that
over
time.
A
B
Just
to
solidify
kind
of
what
you
were
saying
to
jay
so,
and
so
everyone
is
clear,
like
the
process
that
we'd
like
go
to
governance,
govdetneer.org
talk
about
things
incubate
your
idea,
when
you're
ready
to
make
a
proposal
then
go
to
the
nep
repo,
follow
the
kind
of
format
for
actually
making
a
proposal
and
then
you'll
also
link
to
the
zulu
chat,
which
a
lot
of
our
core
engineers
are
on.
When
do
I
go
there
to
to
chat?
B
B
C
A
Yeah
so
so
yeah.
I
agree
with
what
jay
said
so
to
elaborate
on
that.
Basically,
governance
is
forum,
is
for
like
a
longer
post
and
and
where
it
there
will
be
more
asynchronous
communication
around
it.
May
you
know,
may
take
people
a
day
or
several
days
to
post
a
longer
response,
but
also
if
it's
kind
of
more
synchronous
is
almost
like
semi-synchronous.
B
B
Standard
process
before
we
get
into
general
ama,
so
yeah
feel
free
to
drop
your
question
in
the
q.
A
portion
in
the
bottom
there's
a
little
icon
where
you
can
click
on
or
yeah.
If
you'd
like
to
just
drop
in
the
chat,
I
see
some
questions
in
the
chat
as
well
that
yeah
we'll
be
answering
right
after
this
conversation.
B
A
I
just
want
to
say,
like
this
is
still
in
a
kind
of
preliminary
state.
I
think
I
I
hope
to
work
together
with
jay
in
the
upcoming
weeks
to
have
something
more
polished,
written
down
and
posted
to
for
everyone
to
read.
So,
hopefully
I
can
give
an
update
in
the
in
the
next
month's
protocol
meeting
on
the
progress
on
this
one.
B
Cool
sounds
good.
All
right.
Let
me
go
to
some
of
the
questions
in
the
q.
A
I
I
see,
simon
as
smart
contract
developers
still
get
30
of
transaction
fees.
Yes,
they
do.
I
don't
believe
anything
is
changing
as
far
as
I'm
aware
unless
bo-
and
you
have
some
sort
of
insight
on
that,
but
I
don't
think
there's
anything
changing
with
that.
A
A
When
should
we
expect
new
sharding
roadmap?
That
is.
That
is
a
great
question,
so
I
think
I
can.
I
can
provide
a
high-level
update,
so
so,
as
kind
of
as
the
demand
on
near
grow,
especially
in
the
recent
months,
we're
being
focusing
on
making
sure
that
the
applications
that
are
already
live
or
are
about
to
to
become
live
on.
A
I
think
part
of
the
reason
why
why
I
don't
want
to
commit
to
a
super
long-term
roadmap
is
because
things
are
are
changing
rapidly
and
if
we're
talking
about
something,
that's
happening,
there's
something
that's
going
to
happen
a
year
from
now.
It
is
very
hard
to
give
a
even
like
an
estimate
on,
like
you
know,
one
exactly
that
would
be
become
live
so
yeah,
that's
basically
the
update.
I
have
written.
B
A
B
Cool
jafar
asks:
is
there
a
conference
scheduled
for
near
yeah?
I
can
take
that
one
there
will
be
near
khan.
This
fall
location
is
still
to
be
determined.
I
think
we're
targeting
maybe
october
or
something
like
that.
I'm
not
sure.
Actually,
the
the
dates
aren't
finalized
yet
as
well,
but
yeah
keep
an
eye
out
for
our
town
hall
as
well
as
yeah
our
social
channels,
and
we
will
be
certain
to
announce
that
once
we
have
that
finalized
interview,
individual
asked
about
a
public
repo
example
in
your
marketplace.
B
Yeah
again,
you
ask
in
the
dev
support
channel.
Devrell
can
definitely
help
you
out
with
that
yeah.
We
have
a
lot
of
examples
on
that
and
yeah.
If
you
can't
get
an
immediate
or
yeah
can't
find
it
in
our
dev
support
channel
we're
usually
really
responsive
there.
Please
hang
out
in
the
office
hours
and
and
ask
them
some
more
support
questions.
B
B
Let's
see
dennis
asks
what
is
the
future
of
wasm
support
for
the
protocol?
Do
you
plan
to
support
more
languages
to
run
on
nirwasm?
I've
heard
that
now
everything
mostly
is
focused
on
rust,
so
I'm
worrying
if
assemblyscript
sdk
support
will
lag
or
even
be
abandoned
in
the
future.
I
can
answer
a
little
bit
to
that.
Yeah
sdk,
our
assembly
script,
sdk
hasn't
been
updated.
A
lot
we've
been
primarily
focused
on
rust
and
also
we've
been
short
on
engineers
and
yeah.
B
It
looks
like
typescript
and
you
expect
it
to
behave
like
typescript
and
then
actually
it's
not
behaving
as
you
would
like
it
to,
and
it's
not
as
mature
of
a
language
as
rust
is
so
that's
why
we've
been
kind
of
shepherding
individuals
to
to
use
rust,
but
that
repo
is
currently
being
worked
on.
I
think
you
can
go
to
github
forward,
slash
near
forward
slash
near
sdk
dash
js
to
see
the
process.
B
Excuse
me
progress
on
it,
but
but
yeah
assembly
script
will
still
be
there,
but
we
won't
be
officially
like
near
or
pagoda,
as
I
should
say,
isn't
going
to
be
continuing
to
actively
support
that,
but
the
community
definitely
will
be.
I
don't
know
if
you
have
any
other
comments
on
that
as
well.
Boeing.
A
I
think
joshua
already
gave
a
great
answer
right
now,
we're
looking
at
supporting
javascript,
because
we
believe
that
is
more
friendly
to
developers
than
sunrise
group,
because
assembly
script
has
its
own
kind
of
quirks
and
and
it's
not
it
I
mean
yeah.
It
behaves
kind
of
like
typescript,
not
really,
and
then
people
kind
of
get
confused.
B
Cool
ivy
asks:
is
there
a
doc
that
lists
links
to
research
papers
used
in
near?
I
do
have
a
doc
link
that
I
can
drop.
It's
all
of
our
papers.
The
near
white
paper
charted
blockchain,
nightshade
design.
All
that
stuff.
I
will
go
ahead
and
drop
that
in
chat.
I
think
that's
your
question
and
if
it's
not,
please
feel
free
to
elaborate
on
that
cool
looks
like
that's
all
the
questions
in
the
q
and
a
section,
but
I
see
some
in
chat.
B
Can
you
guys
discuss
the
role
of
pagoda
in
protocol
and
availability,
futures
or
upcoming?
I'm
also
curious,
who
are
the
people
developing
the
near
protocol?
There
used
to
be
near
inc,
and
now
it's
a
distributed.
Group
of
people
from
a
variety
of
projects.
Question
mark
yeah,
near
ink
and
near
foundation
are
two
separate
entities.
Near
foundation
is
basically
the
individuals
that
manage
all
the
tokens
and
they
provide
grants
to
people
that
help
support
the
the
protocol
and
develop
on
the
protocol
near
inc.
B
Was
the
engineering
team
behind
the
protocol
also
the
tooling
sdks
near
api
js
all
that
stuff
and
near
inc
has
now
been
rebranded
as
pagoda
to
help
distinguish
the
two
entities
and
near
sorry
pagoda
is
now
the
company
that
will
be
contributing
directly
to
the
source
code,
but
it's
not
owned
by
pagoda.
It
is
still
welcome.
You
know,
pull
requests
are
welcome,
it's
still
all
open
source
and
yeah
definitely
community,
driven
as
far
as
how
we're
trying
to
shape
our
tooling
the
protocol.
B
A
Yeah
yeah,
I
just
want
to
add
a
couple
things.
One
is
that
pagoda
is
a
product
focused
company,
even
though
we
are
still
contributing
heavily
to
the
protocol
as
to
the
product
we're
building.
I
guess
we'll
just
leave
it
as
a
teaser
there
I
think.
Hopefully
more
announcement
would
come
come
soon,
and
another
thing
is
that
other
other
entities-
companies
in
the
near
ecosystem
are
kind
of
building
their
own
protocol
teams
as
well.
A
B
Awesome
I
see
that
daniel
also
asked
something
about
wanting
to
reach
out
and
help
support
the
near
ecosystem
and
trying
to
implement
some
web
free
architecture,
architecture
and
he's
not
a
dev,
but
he's
wanting
to
help
out.
There
is
a
whole
ecosystem
success
team
on
the
near
foundation
that
you
might
be
wanting
to
get
in
touch
with
ping
me
on
discord,
and
I
can
help
connect
you
with
that
team
and
also
help
answer
some
of
your
questions
that
are
kind
of
not
related
to
the
to
the
scope
of
this
conversation.
B
But
more
than
happy
to
to
answer
some
of
the
other
questions
that
you
do
have
do.
Oh
looks
like
this
is
kind
of
going
back
to
the
original
conversation
at
neps.
Does
the
proposal
need
an
upgradability
section
in
the
sense
of
describing
how
easy
or
complicated
it
would
be
to
upgrade
the
contract
in
case
of
the
change
of
the
new
nep.
C
Yeah
I
mean
possibly
one
of
the
unique
features
of
mirrors
is
kind
of
the
ability
to
do
upgrades
a
little
more
transparently
than
the
other
guys
yeah.
That's
that's.
Definitely
something
we
could.
We
could
consider
it's
probably
not
something
that
was
probably
not
a
protocol
question,
but
I
guess
you
kind
of
have
to
also
balance
that
with
so.
The
whole
point
of
having
a
standard
is
to
have
like
an
interface
that
the
rest
of
the
community
can
use.
C
A
Yeah,
I
think
so
on
the
protocol
side,
that's
also
a
great
question
and
I
think
yes,
we
should
actually
add
that,
because
certain
features
the
implementation
may
be
like
not
super
difficult.
The
difficult
part
could
also
lie
in
the
in
the
past
to
upgrade
the
protocol,
for
example.
Well,
that
might
not
be
a
good
example.
If
we
think
of
the
implementation
of
phase
zero
of
sharding,
the
implementation
itself
is
not
trivial,
but
I
think
what
is
even
more
difficult
is
to
to
kind
of
upgrade
the
existing
protocol.
A
A
B
A
Yeah,
I
think
it
depends
on
the
specific
collaboration.
I
think
I
think
most
conversations
are
happening
on
zurich
in
public
and
also
probably
on
the
governance
firm
and
the
kind
of
github
issues
here
and
there,
and
then
we
also
sometimes
have
meetings
with
other
teams
that
are
working
on
the
protocol
together.
B
A
Okay,
so
I'm
trying
to
find
where
the
question
is
so
I
can
yeah,
so
I
think
making
us
doing
that,
though,
like
yeah,
I
don't
have
like
a
a
up-to-date
answer
on
on
their
progress.
I
believe
they
were
heavily
impacted
by
the
the
unfortunate
events
in
ukraine
so
yeah.
I
cannot
provide
a
very
good
answer
to
that
question,
but
but
yeah.
So
basically
there
are
things
that
our
projects
are
working
on.
That.
B
B
Question
to
ask
yeah
again,
thank
you
so
much
for
dealing
with
our
technical
troubles,
we'll
hopefully
have
them
all
ironed
out
before
next
month,
but
but
yeah,
okay,
so
ken's
asking
a
follow-up
question
so
as
far
as
transactions
per
second,
in
theory
is
about
four
thousand
times
six
shards.
Is
this
correct.