►
From YouTube: Aurora Update [2021-05-21]
Description
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
Okay,
hello,
everybody,
it
seems
like
we
are
live
thanks
for
joining
our
stream.
Our
weekly
aurora
update,
hello,
vagatlan,
unfortunately
didn't
see
you
first
time
welcome.
So
I'm
going
to
share
my
screen.
A
As
all
of
you
know,
this
is
the
regular
weekly
update
from
the
aurora
team,
we're
doing
integra
friday
at
this
time,
one
half
one
hour
and
a
half
call.
A
So
later
you
will
be
able
to
to
watch
the
to
see
the
the
millions
of
them
of
this
meeting
in
the
github
and
on
near
blog
and
actually
starting
this
week.
We
are
going
to
put
the
information,
quick,
quick
notes
on
the
most
important
things
in
aurora.dev
blog
that
you
are
able
to
find
on
the
aurora
website
here
so
so
expect
by
the
end
of
the
week
to
see
some
more
content
here
and
the
most
of
the
information
about
this
content.
You
will
hear
during
this
call.
A
So
I
already
put
a
couple
of
points
here
in
discussion,
so
guys,
please,
please
add
anything
else
that
you
would
like
to
discuss
here
and
while
I'm
I'm
doing
the
the
general
update
for
for
everybody,
what's
the
status,
what's
our
current
goal.
A
So
all
good,
we
see
some
activity
that
is
happening
on
testnet
and
on
the
mainnet.
Our
rpcs
are
working
pretty
okay.
So
if
you
want
to
check
to
check
the
the
status
of
the
rpcs,
you
can
go
to
api.dev,
you
see
that
everything
is
in
green.
Everything
is
okay,
art
will
most
probably
post
some
some
updates.
Sorry,
some
updates.
A
And
this
this
includes
also
speaking
to
additional
parties,
additional
partners,
composing
an
invest
round
and
and
figuring
out
how
we
are
going
to
work
after
this.
There
are
lots
of
activities
connected
with
this
lots
of
team
members
are
are
focusing
on
this.
A
The
other
thing
that
we
have
been
focusing
during
this
week
is
a
project
that
we
called
that
we
call
in-ear,
and
this
is
a
project
to
support
a
near
token
transfers
to
ethereum
it's
in
a
pretty
good
state.
In
general,
all
of
the
team
members
are
going
to
update
you
on
this,
but
in
general
we
are
pretty
close
to
releasing
this
project
and,
together
with
in-ear,
we
have
been
working
on
two
connectors.
A
First,
one
is
for
transferring
f
to
aurora.
This
is
the
something
that
is
not
yet
implemented.
We
are
finalizing
it
again,
pretty
close
to
to
finishing
it
finishing
it.
A
This
is
something
very
important
for
being
able
users
to
actually
schedule
transactions
on
aurora
now
right
now,
people
are
still
able
to
do
this
because
they
they
are
able
to
specify
zero
gas
fee,
and
the
rpc
is
working
correctly
with
this.
So
literally.
A
So
this
this
connector
is
already
released
in
general
for
transfers
from
ethereum
to
near,
but
transfers
to
aurora
is
not
yet
there
and
literally
no.
No,
no,
let
me
say
not
like
that:
not
ear
c20
to
aurora,
but
rather
any
p141s.
A
So
this,
for
example,
includes
wrapped
near
so
near
token
itself
can
be
transferred
on
near
blockchain
inside
of
aurora,
so
these
are
yeah
and
also
just
in
just
the
general
status
that
there
are
lots
of
of
work
on
infrastructure
and
plus
lots
of
debugging
and
fixing
fix
and
small
things.
A
A
That's
the
status
and
current
that's
the
status.
Our
current
goal
is
obviously
to
finalize
all
of
these
activities.
We
would
like
to
to
do
the
spin-off
as
soon
as
possible.
We
would
like
to
finalize
in-ear
and
this
additional
to
connect
us
and
make
sure
that
everything
is
working.
Okay.
These
are
our
main
goals.
For
now,
let's
go
with
weekly
updates
ahmed.
B
Yeah
so
yeah,
I'm
so
madly
from
my
side.
This
week
was
mainly
focusing
on
the
integration
and
troubleshooting
the
metamask
issues
and
and
running
some
examples
on
aurora.
So
so
far
the
truffle
deployment
of
the
contract
is
working
and
also
anybody
can
use
a
truffle
console
to
to
interact
with
the
rpc
relayer
and
the
same
thing
for
the
hard
hat,
but
we're
still
having
some
issues
with
metamask,
especially
when
we
read
the
contract
state.
B
So
that's
the
main
issue.
So
far.
It's
still
blocked
by
the
aurora
rpc
layer
because
are
to
mention
that
it
need
to
be
the
horizon
fist.
So
we
can
easily.
A
I
just
can't
confirm
the
need
of
the
qualization
of
rp
serial
layer,
some
some
our
partners
are
requesting.
This
too.
B
Yeah
yeah
we're
gonna
release
this.
Maybe
this
week,
or
maybe
this
monday
for
people.
B
So
so
far
we
have
it
as
a
repo,
but
we
can
just
add
it
yeah,
of
course,.
A
Can
you
please,
while
we
are
going
there,
wrap
a
link
put
here?
Okay,
so
on
my
sides,
I
was
mainly
working
on
on
partners.
Partners
and
investors
calls
so
lots
of
discussions.
There
need
to
align
lots
of
interests.
Well,
literally,
that's
it
that
this
is
how
my
days
are
structured.
A
Actually,
so
I'm
trying
to
to
do
the
general
management
to
help
to
help
structure
a
little
bit
the
legal
side
to
help
also
doing
a
little
bit
of
of
hiring
so
some
interviews
during
this
this
week
too,
because
again
we
have
quite
a
lot
of
open
positions
and
we
need
to
make
sure
that
that
these
are
going
to
be
filled
yeah.
A
C
C
So
that's
the
under
unreleased
version
of
the
engine
in
in
order
to
help
the
team
test
with
that
as
well.
We
do
want
to
keep
the
desnet
and
mainnet
deployed
engines
the
same
when
possible.
So
that's
why
we
needed
a
separate
instance.
C
C
So
right
now
today,
there's
a
protocol
upgrade
happening
on
the
neural
maintenance
and
because
of
that,
we
had
to
stand
up
some
new
new
hardware
and
apply
the
new
new
version
of
new
core
there.
So
we
have
new
new
archive
notes
coming
up
coming
online
and
they
will
be
going
online
right
after
this
call,
which
is
good
because
the
protocol
upgrade
will
will
kill,
kill
our
old
mainnet
nodes
when
it
activates.
C
It
should
activate
sometime
tonight,
hopefully
and
also
began
to
set
up
the
edge
hardware.
So
we
have
hardware
in
a
number
of
countries
now
and
we're
gonna
roll
out
edge
hardware.
Over
the
next
days
I
moved
most
of
our
configuration
to
terraform,
so
it's
managed
in
a
git
repository,
so
that
includes
things
like
dns
records
so
that
we
we
always
know
what
the
state
should
be
with
those
they're
not
just
floating
around,
and
I
redid
our
endpoints,
and
maybe
you
can
show
the
docs
page
for
the
endpoints
for
the
network.
Yeah.
C
Yeah
sorry
networks
that
one
yeah
yeah,
so
the
the
endpoint
urls,
are
now
far
simpler.
As
then,
we
took
off
the
rpc
prefix
and
we
took
off
the
84
8545
port
from
the
end.
So
these
are
now
easy
to
remember,
as
in
anybody
can
just
remember
that,
it's!
Oh
it's
testnet!
Oh,
it's
bitterness!
Maintenance!
Super!
Easy,
no
need
to
go!
Look
at
documentation,
and
importantly
these
these
are
now
hosted
via
observed
via
cloudflare,
which
means
that
we
have
a
ddos
protection.
C
C
In
addition
to
that,
we
have
a
red,
limiting
and
happy
blacklist,
also
on
the
back
end,
and
we
lower
lowering
latency
by
a
persistent
secure
tunnel
between
cloudflare's
edge
and
our
origin.
C
So
origin
is
where
the
endpoint
is
actually
actually
hosted
and
and
those
servers
where
we
host
the
endpoint
are
no
longer
directly
accessible
on
the
internet,
so
they
they
are
just
connected
directly
to
cloudflare,
cloudflare's
backend
and
they're
no
longer
possible
to
attack
directly
from
the
internet,
also
working
on
granular
rate
limits,
meaning
that
would
like
to
have
mutative
operations
have
a
lower
rate
limit
than
read-only
operations
that
one
run
into
some.
C
Some
issues,
hopefully,
can
make
progress
on
that
next
week
then,
and
I
set
up
an
internal
secure
network,
so
essentially
our
corporate
vpn
for
aurora
between
all
our
hosts
and
our
working
computers
as
well,
and
then
the
piece
of
robot
is
waiting
for,
so
the
auto
relay
is
dockerized
and
it
can
be
now
used
very
simply
on
your
own
computer
as
well
as
deployment
is
vastly
simplified.
A
A
D
I
was
this
week,
I
was
doing
some
code
reviews,
so
I
think
the
most
important
is
in
year,
which
is
currently
in
the
process
of
being
launched,
and
I
also
helped
joshua
with
api
editions.
So
we
are
planning
we
need
to
add
those
math
api
cost
functions
soon,
because
then
there
will
be
some
period
until
the
corresponding
update
will
be
actually
activated,
and
we
want
it
to
be
activated
not
too
late,
because
it
will
greatly
decrease
gas
usage
for
our
evm
contract
right.
B
Our
accounts
counter
also,
currently
it's
become
completely
implemented
and
tested,
and
so
after
you're
getting
kozeko
reviewed,
br
related
to
s
connector.
I
started
improvements
and
fixes.
So
in
that
time,
all
things
implemented
at
the
and
fix
it
enter
ready
for
review.
That's
all.
A
Okay,
can
you
please
can
you
please
send
put
here
link
to
your
pr
okay,.
B
A
Cool
frank,
frank:
how
are
you.
B
A
A
B
That
this
week
I
factored
out
the
near
api
go
which
is
basically
a
goal
library
to
develop
the
adapts
similar
to
the
near
api
gs
before
that
was
part
of
the
bully,
and
now
we
have
it
as
a
separate
package,
so
we
can
use
it
to
build
other
go
tooling
with
it.
Okay,
then
I
updated
the
bullet
to
the
current
globe
ethereum
code
and,
most
importantly,
I
brought
the
bully
to
a
stage
where
we
can
now
reproduce
problems
without
having
to
replay
change
from
scratch.
B
We
talked
about
that
on
an
earlier
call
that
the
further
we
go
in
the
in
the
replaying
of
ethereum
test
nets.
You
know
the
the
harder
it
would
be
to
repeat
these
problems
because
it
just
takes.
You
know,
potentially
hours
and
maybe
days
so
now.
Basically,
when
I
encounter
a
problem,
I
can
just
dump
dump
the
state
and
then
we
can.
We
can
retest
it
from
there
and
yeah.
Earlier
I
talked
to
josh
that
now
I
would
take
it
out
basically
such
problem
and
document
the
process
to
him.
A
What
is
what
is
the
current?
What's
the
current
height
that
that
evm
is
stopping
at,
is
it
still
that
12
000
something.
B
It's
like
for
girly,
fourteen
thousand
four
hundred,
sixty
or
so,
and
okay
for
the
other
two
they
did
they.
They
stopped
very
early
with
problems.
E
B
B
Basically,
as
soon
as
one
problem
is
fixed.
A
Yeah,
have
we
already
fixed?
I
I
remember
there
was
an
issue
with
a
very,
very
short
question.
The
issue
with
with
the
size
of
transactions.
Are
we
able
to
to
have
a
local
deployment
of
new
york
core
that
is
able
to
sustain
more
than
1
000
tera
gas
like
it
was
raised
to
800
per
transaction,
or
something
like
that.
B
B
On
the
local
setup,
so
otherwise
it's
not
working
it's
okay,.
B
Just
in
the
genesis
state
parameters,
you
know
that
can
be
adjusted.
A
Yeah,
cool
cool,
yeah,
okay,
let's
not
go
too
deep
into
it
sure!
Oh
my
gosh
joshua
you're
you're
writing
essays
every
every
time
it
is
is
more
and
more
okay,
nice
I
enjoy
reading
stuff.
Can
you
comment
on
this.
G
Yeah
sure
so,
basically,
the
most
of
what
I
did
this
week
was
the
math
api,
because
we
got
to
get
that
in
asap.
So
I
worked
with
cap
on
on
that
and
also
worked
with
michael
a
bit
on
that.
It's
like
right
now,
the
blank
two
functionality
is
in
there.
It's
all
working
and
you
can
do
it
step
by
step
depending
on
what
the
the
arguments
are.
G
I'm
still
gonna
write
a
couple
more
tests
just
to
make
sure
everything's
good,
but
that's
pretty
much
good
to
go
and
then
found
two
issues
with
the
get
state
while
talking
talking
to
michael
and
then
also
found
an
issue
with
their
current
version
set
up,
it
was
more
so
just
migration,
stuff
in
general
and
then
other
than
that
had
discussions
and
reviews
and
with
the
with
the
discussions,
I
guess
I
already
kind
of
already
mentioned
them.
G
H
H
H
I
also
had
configure
them
setup
the
explorer
for
the
developer
aurora
on
the
test
net.
This
blocker
explorer
uses
the
ethereum
light
explorer,
and
I
also
had
like
a
lot
of
important
discussions
with
almost
every
member
of
the
team
more
details.
I
in
the
report
and
such
a
huge
and
detailed
report
was
inspired
by
weekly
reports.
H
A
That's
cool,
that's
cool,
something
something
wrong
is
with
the
identitation
here,
but,
like
it
doesn't
matter,
okay,
cool
cool.
Are
we
able
actually
to
provide
the
link
to
the
light
explorer
or
it's
better
not
to
do
because
on
your
private
server.
H
It's
on
the
private
server.
I
can
provide
the
link
and
it's
only
set
up
for
the
developer
or
in
the
testnet,
the
branch
which
supports
the
s
connector.
I
can
put
link.
A
Yeah
yeah,
okay,
okay,
cool
marcelo.
E
E
Well,
I
was
helping.
I
was
working
with
joshua
and
michael
on
the
generational
nuns
implemented
to
solve
the
self-destruct
problem,
which
basically
is
resetting
a
contract.
I
think
that,
ultimately,
the
solution
probably
will
go
using
a
similar
solution
to
what
I'm
doing
for
the
rc20
contract,
like
modifying
the
state
you're
passing
inside
the
evm,
to
keep
track
of
of
nonsense
more
efficiently
and
well.
Last
two
points
are
like
regular
background
job.
Every
week
supporting
breach.
E
E
A
Yeah
yeah
yeah,
okay,
super
cool,
as
always
thanks
for
supporting
our
community
thanks
for
supporting
our
users
and
and
thanks
to
everybody
who
are
doing
this.
I
was
also
doing
a
little
bit
of
hands-on
support
this
week
for
our
users
and
actually
have
a
call
with
the
partners
that
are
also
working
on
the
bond
bridge
right
after
our
our
school
okay
cool
near
near
gosh
matt.
I
Yes,
aurora
so
coordinating
the
launch
of
enir
the
activities
around
that
investing
investigating
liquidity
options
for
niron
ethereum
testing,
the
rainbow
bridge
ui
update
with
pierre
and
making
a
few
tweaks
to
that,
and,
finally,
an
enhancement
to
the
aurora
website
such
that
we
can
now
categorize
the
content.
That's
in
the
publication
area
and
we
re
rename
that
from
news
to
blog.
A
A
Okay,
michael
also.
J
A
little
tech
de
refactor
worked
on
the
ci
cd
for
the
docs
and
also
the
the
engine
repo,
the
docs,
now
automatically
update
on
pushes
to
master,
which
is
nice
and
the
engine
repo.
The
the
tests
now,
instead
of
taking
20
minutes
to
run,
take
like
one
minute
to
run.
So
that's
that's
very
nice!
That's
thanks
to
the
cargo
caching
and
we
talked
a
little
bit
about
automating
test
net
deploy.
I
need
to
sync
up
with
with
arto
more
about
that.
J
He
was
very
busy
infrastructure
this
week,
but
I'll
need
some
some
help
to
get
the
automated
test
deploy
going
from
him
and
then
otherwise.
I
was
working
on
a
few
pr
reviews
and
the
state
migration
stuff.
So
this
this
came
out
of
the
the
audit
from
kuzukov.
J
So
he
pointed
out
that
when
we
change
logic,
we
may
also
need
to
change
state
an
example
being
adding
a
field
to
to
a
structure.
So
we
we
now
are
are
able
to
do
that
and
there's
a
nice
nice
test
for
it.
A
Okay,
does
this
already?
Does
it
use
the
state
versioning?
That's
that
that
we
have
been
implementing
just
before
the
release.
J
Right
right
now,
it's
it's
just
a.
J
A
step
like
it
like
the
the
skeleton
is
there,
but
because
we
don't
actually
have
any
state
to
prior
to
state
migration.
The
migration
method
doesn't
actually
do
anything,
but
we
did
talk
about
how
probably
we
will
use
the
version
state
in
the
future
to
to
do
one
of
our
first
migrations
when
we
actually
have
a
real
migration
to
do.
F
Yeah,
so
this
week
was
mainly
focused
on
getting
everything
ready
for
the
in-ear
functionality,
release
in
the
ui,
so
pre-releasing
different
client
library
packages,
which
include
some
refactoring
so
now
we'll
have
separate
packages
for
the
light.
Merkle
patricia
tree
for
the
connector
utils
for
the
fine
replacement
transaction,
and
so
those
are
packages
that
can
also
be
used
outside
of
the
bridge.
F
I
did
some
work
on
the
on
fixing
the
finalization
of
transfers
and
building
of
proofs.
So
now
we're
building
proofs
just
before
the
unlock,
which
has
one
small
downside,
is
that
building
the
proof
takes
a
second
with
the
different
queries.
So
I
I
suspect
that
that's
why
originally
the
proof
was
built
as
part
of
the
sync
so
that
the
user
would
not
notice
it.
So
now,
there's
this
extra
small
gap
in
between
the
time
that
metamask
has
actually
opens
and
the
time
that
user
clicked
on
the
to
make
the
finalization.
F
I
did
some,
what
was
it
yeah,
so
improving
the
recovery
features
so
now
we're
checking
when
recovering
a
transfer,
we're
checking
what
is
the
status
of
that
transfer,
and
so
we
were
able
to
do
this
by
querying
the
local
storage
directly,
because
we
don't
have
a
view
function
to
to
check
if
the
proof
was
used
and
so
we're
using
get
storage
at
to
use
to
read
the
state
directly
so
based
on
the
variable
position
inside
of
the
contract,
we
can
directly
read
to
it.
F
And
finally,
I
did
a
bit
of
testing
yeah,
so
the
fine
proofs,
so
that
that
raised
some
some
interesting
questions,
because
currently
the
most
of
the
logic
relies
on
a
combination
of
the
client
library
and
the
connector
library.
And
so
the
client
is
the
main
entry
point
which
controls
the
connectors.
F
But
what
we
might
want
to
do
is
to
add
more
flexibility,
to
use
the
connector
libraries
by
themselves
and
have
an
optional
provider
that
we
can
pass
into
those
functions
so
that
the
connector
doesn't
necessarily
have
to
use
the
the
connected
client
library
which
stores
the
providers.
So
this
way
yeah
mainly
flexibility,
I
think,
would
be
pretty
good,
probably
next
week,
I'll
open
an
issue
on
it,
and
maybe
we
can
get
some
feedback
for
the
best.
The
best
api
that
we
can
can
have
for
this.
A
Okay,
I
want
to
do
pretty
pretty
short
shout
out
to
to
raymond
fan
because
who
is
helping
with
this?
So
that's
super
cool
I
was
chatting
with
him-
was
supporting
little
bit
him
during
this
week,
so
really
happy
that
people
start
building
stuff
in
depth
in
in
the
guts,
I
would
say
of
the
bridge.
That's
super
cool.
F
Yeah
and
finally,
I
did
a
bit
of
testing
with
argent,
because
I
remember
a
while
back.
We
had
a
user
using
it
and
checking
the
behavior
with
multisig
and
wallet
connect
and
particularly
need
to
finish
checking
what
happens
with
the
cancelled
and
replacement
transactions
and
all
these
things,
because
for
now
we're
kind
of
assuming
that
external
accounts
are
used.
But
we'd
want
to
the
library
to
work
perfectly.
Also,
if,
if
it's
part
of
the
multisig,
for
example,.
A
Oh
yeah,
yeah
yeah,
that's
that's
very
important
thing,
because
what
so
what
what
our
partner
is
doing,
for
example,
right
now,
is
actually
doing
even
more
than
this
but
like
if,
if
something
is
multisig,
then
the
transaction
that
is
not
called
directly
from
from
like
metamask,
it's,
not
a
single
transaction
that
is
sent
to
our
contract.
It's
just
a
cross-contract
call,
so
it
might
work
a
little
bit
different
way.
Maybe
actually
that's
that
that
proof
code
has
some
problems
with
that,
but
well,
let's.
B
F
A
Yeah,
okay,
julian,
are
you
with
us.
A
I
will
put
crm
as
a
separate
thing.
Uran
is
doing
a
very,
very
good
job
that
he's
going
to
help
us
a
lot
in
in
the
future,
so
he's
populating
the
crm.
A
That
is
already
we
already
set
up
we're
still
in
in
the
testing
mode,
I
would
say,
but
but
it
is
already
there
and
lots
of
lots
of
data
is
already
there,
so
we
can
use
it
very,
very
convenient
top
notch
tier
one
crm.
So
that's
that's
cool.
A
Okay,
great
so
we
are
now
we
finished
the
updates.
We
are
now
in
discussions,
so
there
are
like
three
points
that
I've
put
here
any
any
additional
stuff
to
discuss
from
you
guys.
A
We
can
start
with
this
and
then
you
can
and
then
you
can
say
what
you
want
to
add
here.
So
I'm
thinking
that
we
are
now
there's
quite
a
big
mess
in
it's
like
channels.
So
this
is
my
proposal
to
use
actually
get
rid
of
anything
done,
alex.
C
Alex
alex
I
have
to,
I
have
to
stop
you
here.
Slack
is
not
something
publicly
visible,
so
we
might
have
discussed
it
on
the
monday
call.
Instead.
A
Sure
no
problem,
no
problem,
yeah,
let's
discuss
it
on
monday,
no
problem,
I'm
just
then
do
it
in
this
yeah
one
additional
idea.
I
think
that
this
is
this.
This
is
this
is
going
to
to
be
influencing.
Everybody
is
out
of
analyze
after
near
transfers.
So
we
have
been
speaking
about
this
for
a
long
period
of
time.
A
So
if
we
have
transfers
of
tokens
for
token
connector
that
are
going
from
ethereum
to
near
then
since
we
if
we
want
to
work
with
aurora,
we
know
that
our
ruler
need
to
do
this,
and
this
is
this
is
what
kirill
was
implementing,
and
this
is
one
thing
second
thing
yeah:
if
we
will
do
this,
it
will
just
simplify,
simply
simplify
the
onboarding
flow
and
how
the
users
are
sending
stuff.
A
So
this
will
be
pretty
straightforward
and
the
good
thing
also
about
this-
that
it
it
costs
not
a
lot.
So
I
was
just
checking
factory
bridges
near
and
the
amount
of
all
transactions
there
were
scheduled
to
factory
bridges
of
near
was
766
transactions
in
total.
So
that's
not
a
lot.
Obviously,
the
amount
will
go
up,
but
like
it's
and
like
many
of
these
transactions
are
deployment
of
the
of
the
other
smart
contracts
and
and
so
on.
A
Yeah
deployment
of
the
near
version
of
the
tokens
and
stuff
like
that,
and
there
are
other
things
there,
so
not
that
big,
which
is
kind
of
cool,
so
we
can
do
this
and
the
most
important
thing.
A
The
most
important
thing
is
that
this
this
will
solve
our
ledger,
bug
or
like
it
will
not
solve
the
bug,
but
users
will
not
see
it.
Okay,
as
you,
as
you
know
now,
ledger
protected
near
wallets
are
not
able
to
sign
the
finalization
transaction
just
because
it
is
not.
We
cannot
fit
it
inside
of
ledger.
A
Okay,
any
other
any
other
points
of
view
on
this.
H
Yeah,
I
think
the
cost
is
relatively
low,
so
for
the
whole
amount
of
transactions
already
happened,
that
we
would
have
paid
like
a
couple
of
years
or
so,
and
the
good
thing
is
that
their
layer
is
ready
for
that
stuff
yeah.
I
used
to
run
it
in
this
mode
like
a
months
ago
on
the
test
net,
which
brings
some
problems
to
members
because
they
tried
to
finalize
they
already
finalized
transactions.
H
E
What
about
near
to
its
transactions,
do
you
want
to
finalize
those.
A
E
B
A
F
A
Okay,
cool
matt,
what's
on
your
take
on
this,
are
you
still
with
us
yeah.
I
Yeah,
can
you
what
was
that?
What
the
question
I
was
just
I
was
having
a
side
chat,
coordinating
the
next
call.
A
Yeah,
sorry,
so,
what's
the
what's
your
take
on
the
outer
finalization
of
estonia
transfers
so
near
transaction
is
scheduled
automatically
absolutely.
A
All
of
the
transfers-
okay,
perfect
yeah.
This
is
what
I
expected
yeah,
so
so,
just
during
this
week,
I
I
understood
that
this
can
solve
the
the
ledger
problem
and
yeah
and
we
will
not
show
any
notification,
okay,
cool,
so
then
yeah
it
seems
like
we
are.
We
are
all
agreeing
that
that
this
is
something
that
that
we
should
do.
A
Okay,
let's
put
it
then
in
our
pipeline
cool,
arthur
feedback
on
web
3
and
points
usability.
Is
this
you
who
put
it
in.
C
Oh
yeah,
that's
right!
So
just
would
like
to
hear
feedback
from
anybody
who's
using
the
endpoint
internally
and,
of
course
otherwise
too,
on
whether
very
well
latencies
are
currently
acceptable,
for
example,
pr
when
you're
using
it
does
it
feel
faster
or
sluggish.
C
Any
errors
encountered
or
strange
things
encountered
do
do
provide
feedback,
so
we
know
about
the
metamask
issue
and
are
working
on
fixing
that,
but
anything
anything
else
we
we
haven't
heard
about.
So
if,
if
there's
something
else,
let's
let's
surface
it.
B
F
Yeah,
I
was
just
wondering
if
somebody
had
looked
into
this
already
once
we
have
erc
20
near
on
ethereum,
we'll
want
that
token
to
be
as
default
on
metamask,
so
that,
if
you
have
that
token,
it
will
directly
display
without
you
having
to
manually
register
it,
and
so
I
believe
for
this.
We
need
to
make
a
pr
to
have
to
the
contract
metadata
repository.
F
For
this
no.
F
Yeah,
nothing
new
on
my
side
in
terms
of
eth,
I
didn't
have
any
issue
at
the
time.
C
F
So
usually
they
require
tokens
to
have
some
volume
and
things
like
that,
so
they
might,
it
might
get
delayed.
I
don't
know,
depending
on
their
willingness
to
merge
quickly
or
not.
B
A
H
I
also
had
some
feedback
regarding
this.
I
don't
have
the
feedback
for
the
latency,
because
I
was
using
the
web3
endpoint,
which
points
to
the
developer
aurora,
which
doesn't
have
this
latency
improvements
made
by
arto.
The
endpoint
works
pretty
good.
I
think,
but
I
have
experienced
some
issue
when
I
set
up
the
block
explorer.
H
I'm
researching
this
stuff,
I'm
putting
just
a
little
effort
for
this,
but
I
think
that
maybe
this
is
because
their
layer
is
not
supporting,
like
all
json
rpc
methods,.
C
Yeah
there's
some
non-standard
ones.
We
don't
support
and
there's
standard
ones
that
require
the
server
to
have
your
private
key,
which
we
don't
support.
Additionally,
the
relayo
connecting
to
it
doesn't
have
archival
data,
so
any
any
blocks
older
than
a
certain
point.
You
wouldn't
get
the
responses
back.
C
You'll
get
errors,
okay,
okay!
Yes,
you
got
it,
but
but
yeah
good
good
at
your
exercise
exercising
it
don't
do
do
report
anything
sure.
I
Well,
I
just
had
one
comment
about
the
the
last
point:
making
a
metamask
vr
to
register
in
there.
One
thing
that
pierre
and
I
were
talking
about
was
the
possibility
of
adding
a
metamask
icon
on
the
bridge
to
automatically
add
the
near
token
to
your
metamask.
So
you
know
a
lot.
H
I
A
lot
of
adapts
have
have
such
an
icon
to
add
their
their
particular
token
to
metamask,
so
you
just
click
it
and
the
token
is
added
we
kind
of
punted
on
the
idea
at
the
moment,
since
the
bridge
is
a
general
purpose
thing
and
not
specific.
To
one
token,
however,
since
it
is
our
own
token,
it
might
make
sense
to
to
find
a
way
to
do
that.
So
that's
that's
also
an
option
to
help
people
quickly
get
the
the
asset
into
their
metamask.
C
And,
of
course,
that's
related
to
having
such
a
button
also
for
adding
our
endpoints,
which
is
known
it's
on
the
back
burner,
need
to
be.
A
A
Yeah,
okay:
this
is
like
this
is
even
I
believe,
a
bigger
task,
because
this
is
a
meta
task
that
we
need
to
solve
for
all
of
our
partners,
because
normally
a
user
that
will
come
to
to
us
well
to
transfer
the
tokens,
but
he's
he's
going
to
work
with
our
with
our
front
end
only
once
like,
presumably
not
very
often,
I
would
say,
and
all
of
the
rest
they
are
going
to
all
the
users
are
going
to
do
on
on
the
partners
front
end
on
the
depth
front
end.
A
A
Okay-
with
regards
to
these,
I
actually
wanted
to
update
you.
All
it
seems
like
ether
scan
is,
is
now
more
interested
in
in
doing
the
integration,
so
perhaps
we
will
get
some.
I
will
get
some
queries
from
them.
A
So
ether
scan
is
now
exploring
the
integration.
I
would
say
so
so
just
just
pay
your
attention
to
our
chat
with
them.
A
Okay,
so
probably
we
have
been
discussing
already
these
three
points
a
little
bit
dude.
Is
there
anything
to
add
on
the
ear
c20
display
in
metamask
mac.
B
Actually,
it's
like
a
general
issue.
It
is
not
only
displaying
displaying
here,
take
money
and
metamask
from
the
contract,
so.
B
C
A
Okay,
cool,
okay,
any
any
additional
topics.
What
do
you
want
to
discuss.
A
Going
once
going
twice:
okay,
cool,
then:
let's
keep
it
nice
and
short,
then
so,
let's
go
to
the
next
week
priorities!
No!
No!
Sorry,
sorry,
sorry!
I
I
have
one
thing:
the
the
docs
actually,
what
is
the
status
and
and
how
we
are
working
on
them,
because
we
wanted
to
update
them
and
well
still
need
to
do
some
some
stuff.
There
are
lots
of
lots
of
us
here.
So
maybe
we
can
move
this
on
somehow
yeah.
C
So
I'm
I'm
working
on
the
docs,
I
know
ahmed
is
working
on
the
examples
and
joshua
is
still
working
on
the
docs.
G
C
C
Docks
and
michael,
are
you
working
on
the
dogs.
J
I
haven't
made
any
big
contributions
lately.
C
Okay,
all
right,
so
it's
pretty
much
me
and
ahmed
and
anybody
else
working
on
the
docks.
C
Okay
sounds
like
we're:
it
yeah,
so
this
there's
a
lot
of
tutorials
to
write,
just
need
to
find
time
to
ride
it.
The
infrastructure
issues
were
more
pressing,
so
we
didn't
fall
down
and
sure
they
remain
a
little
bit
more
pressing.
So
we'll
certainly
improve
the
dogs
over
the
next
week.
C
I
just
have
to
fill
it
in.
A
Yeah,
let's
make
this
a
target
for
the
next
week.
Actually,
that's
that
we
are
providing
some
kind
of
tutorials
to
people,
because
many
partners
are
starting
to
ask
how
to
how
to
run
stuff.
Where
can
I
do
this
stuff.
C
C
Part
and
parcel
of
looking
through
those
truffle
hard
hat
metamask
remix
flows.
Oh
you
go
through
as
we
go
through
them.
We
we
can
document
it
at
the
same
time.
So
of
course,
the
idea
of
writing.
For
example,
a
truffle
tutorial
it
ran,
ran
aground
when
we
weren't
able
to
finish
the
actual
demo
scenario
due
to
the
problems
we
encountered,
but
those
have
been
fixed
now
and
I
need
to
come
back
to
to
that
task
as
well.
J
A
Okay,
okay,
cool!
Then,
let's
go
to
to
what
we
are
planning
for
the
next
week
ahmed.
What
do
you
think.
B
Yeah
mainly
from
mainly
the
docs
stuff,
and
also
the
metamask
issue,
and
investigating
also
the
remix
issue
as
well.
B
And
maybe
adding
more
more
more
examples
for
like,
for
example,
the
multi-site
wallet,
diagnosis
multisay?
Well,
so
anybody
can
actually
deploy
the
contracts
and
connect
the
multisig
wallet
ui
to
to
our
network.
B
Like
a
more
let's
say,
it
will
be
like
an
extra
example
like
running
gnosis
multisig
wallet
on
aurora.
So
it's
like
a
well-known
processing,
one
yeah.
A
Okay,
cool
nice,
so,
on
my
end,
is
still
number
one
is
spin-off
and
everything
connected
to
it.
There
will
be
a
little
bit
of
marketing
activities
so
next
week
on
monday.
A
To
join
our
talk,
aurora
talk
at
consensus,
you
probably
have
heard
of
of
this
conference,
so
we
have
a
slot
there
and
we
will
be
able
to
talk
a
little
bit
about
rural
there
and
bridge
rainforest
aurora.
So
like
a
half
an
hour
for
this,
so
which
is
kind
of
cool.
So
please
join,
and
you
will
be
able
to
see
us
next
week
on
on
monday.
C
Maybe
you
could
send
invites
to
to
that
calendar
event.
Everybody
on
the
team.
C
All
right,
so
just
do
you
no
alex,
doesn't
invite
everybody,
so
everybody
has
it
in
front
of
them.
B
I'm
not
sure,
though,
we're
gonna
have
tickets.
I
think
this
is
like
a
paid
event,
but
I'll
find
out
and
let
you
know:
okay,
okay,.
C
C
So
that
means
that
the
we
will
be
able
to
serve
most
requests
to
the
endpoints
directly
from
the
edge
as
in
a
location
geographically
closest
to
the
user.
So
geographic
load,
balancing
and
that's
that's
well
underway.
I
I
expect
we
can
roll
it
out
within
the
next
week
and
that
will
reduce
the
latencies
massively.
C
I
have
detailed,
detailed
statistics
on
on
how
long
it
takes
to
connect
to
the
endpoint.
Do
the
ssl
handshake
but
tcp
handshake,
ssl,
handshake
and
then
actually
get
the
first
bite
and
we
we
are
going
to
track
all
of
these
stats
and
we're
going
to
improve
them
over
time.
So
that's
that's
about
to
be
improved.
Then
there's
a
bunch
of
things
I
need
to
do
for
block
indexing
to
to
enable
the
block
explorer
so
hope.
C
D
I
think
I'll
need
to
work
on
host
functions
so
I'll
make
meth
api
cost
functions
to
make
test
vectors
for
those
functions,
especially
for
blake
2,
because
it's
not
stand
like
standard
function.
So
you
need
custom
test
vectors
to
make
sure
that
it
is
implemented
correctly
and
also
code
reviews
for
host
functions
and
for
other
stuff.
C
A
Yeah
yeah,
so
I
I.
I
have
intentionally
scared
bowen
a
little
bit
with
with
the
lordy
swap
so
now
he.
C
H
B
A
Okay,
cool
cool!
That's
that's
already
solid,
solid
thing,
frank.
A
So
bully
and
dogs-
that's
succinct,
yeah,
joshua,
yeah.
G
Yeah
math
api
test
and
possibly
getting
the
sdk
updated
because
that's
going
to
be
where
everyone's
going
to
be
using
the
math
api
through
there
yeah
because
like
if
people
use
the,
for
example,
the
black
two
methods
directly
they're
gonna,
get
probably
an
unexpected
hash
result
because
initialization
factor
doesn't
happen.
So
that
gets
done
through
the
sdk.
G
So
yeah,
just
basically
math
api.
Get
that
out
the
door
as
soon
as
possible
and
reviewed
and
follow
up
any
review
comments
and
then
sdk,
possibly
after
that
and
then
docks.
If
I,
if,
as
a
stretch,
goal.
C
I
think
I
think
we're
good
on
the
docks.
Don't
forget
about
the
self-destruct
issue.
You
need
to
work
on
that
as
well.
H
H
E
Yeah
I'll
be
I'll,
be
finalizing
the
the
rc20
connector,
mostly
to
block
fgnu
kind
of
with
the
connector
I'll,
be
final
prioritizing
the
the
issue
with
pro
compiles
from
his
calls.
A
I
Yeah
continuing
with
in
here
and
then
going
back
to
the
the
testnet
aurora
bridge,
ui.
A
Okay,
okay,
that's
that's
nice,
michael
okay,
docs
automatic
deploy
to
test
it.
Can
you
elaborate
a
little
bit
on
this.
B
J
Yeah
we
want
our
ci
to
automatically
deploy
the
test
net
on
merges
to
our
our
death
branch
so
that
we
always
have
an
up-to-date
version.
That's
you
know
being
tested
there.
F
I'll
be
working
on
making
a
final
release
for
in-ear
and
merging
everything
and
then
going
back
to
the
aurora
integration.
F
A
Is
this
correct
you
then
yeah,
okay,
cool
cool,
so
with
this
I
believe
so
last
round
for
any
questions
and
any
comments.
A
Okay,
then
thanks
everybody,
let's,
let's
save
a
little
bit
of
time,
and
if,
if
someone,
if
you
have
next
calls
you,
you
will
have
some
time
to
refresh
thanks
everybody
for
joining
this
overupdate
call
we'll
see
you
next
week,
and
hopefully
we
will
have
some
quite
a
lot
of
exciting
information
to
share
with
you
see
you
next
time.