►
From YouTube: Aurora Update [2021-05-14]
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,
we're
live
hello.
Everybody
thanks
for
joining
us
on
today's
aurora
update,
update
friday
call.
This
is
the
regular
call
that
we
are
holding
within
the
aurora.
A
A
A
Yeah
yeah
yeah,
that's
that's
correct,
so,
like
so
many
windows
open
there,
so
it's
somewhere
there.
There
is
a
window,
this
stream
on
the
youtube.
Okay.
So
coming
back
here
so
today
we
are
sharing
with
you,
the
updates
on
aurora
and
well.
The
general
update
is
that
aurora
has
launched
and
is
now
publicly
live
on
nearest
mainnet,
so
yeah
yeah!
Congratulations!
All
of
you
guys!
You
did
the
tremendous
work
in
in
the
in
the
last.
A
Actually
three
months
we
were
speaking
with
arthur
and
really
everything
got
updated
within
the
last
like
three
months,
actually
so
all
cool.
So
for
all
of
you
who
is
watching
this
recording,
I
would
recommend
to
go
to
near
dot.
Org,
slash
blog,
slash,
aurora
launches
near
this.
Is
a
public
blog
post
about
the
launch
of
aurora.
You
will
be
able
to
find
lots
of
information
here
about
the
specifics
of
aurora,
how
it
is
how
it
is
implemented.
A
What
are
some
important
architectural
decisions
that
are
made,
how
it
works
together
with
the
rainbow
bridge
and
some
stuff
like
ability
to
use
ability
to
use
f
as
a
base?
Token
and
many
many
other
different
things,
including
roadmap,
the
main
place
where
you
you
need
to
check
for
the
updates
on
aurora
right
now
is
aurora's
own
website.
We
have
it
under
aurora.dev.
A
A
A
So,
coming
back
to
the
aurora
update,
I'm
going
just
to
put
the
launch
or
like
aurora
is
launched,
so
that's
cool.
This
is
this
is
the
status
and
and
in
the
current
gold
the
current
goal
is
yeah.
The
aurora
is
launched.
Obviously,
all
the
team
right
now
is
working
super
hard,
I
believe,
even
harder
than
before
the
release
to
to
do
the
hot
fixes,
hotfix
and
stuff
and
yeah.
A
So,
for
example,
where
we
revealing
that
there
are
some
issues
with
with
truffle
and
hard
hat,
but
about
this
in
in
our
update.
Let's
keep
this
update
focused.
I
know
that
everybody
were
doing
lots
of
small
tasks
and
we
were
fighting
fires.
So,
let's,
let's,
let's
focus
on
on
the
stuff
that
that
was
like
the
big
ones
and
the
general
updates.
C
Yeah,
so
far,
so
good,
so
mainly
from
from
my
side,
just
working
on
the
onboarding
stuff
and
also
iterating
with
marthillo
and
curl.
Regarding
some
like
some
questions,
I
have
for
the
connector
and
the
bridge
and
also
working
on
some
like
the
minor
prs.
So
this
is
the
first
minor
prs
and
fixes
for
the
heat,
connector
and
also
working
on
the
spoiler
plate
dab
on
on
aurora.
C
Hopefully
it
should
be
like
next
week
we're
gonna
have
this
running
and
also
reviewing
some
stuff
like
the
if
the
proxy
youth
contract
yeah.
So
that's
mainly
from
my
side.
A
That's
cool
a
short
update
to
everybody.
Our
community
is
developing
this
this
contract
to
to
to
be
able
to
to
call
the
bridge
not
from
our
interface
but
through
the
market
maker.
So
pretty
cool
stuff
community
asked
us
to
review
this,
so
I've
met
this
he's
working
on
this.
A
A
And,
and
just
and
and
just
overall
communications
and
other
types
of
people
slash
entities,
so
lots
of
stuff
happening
right
now,
a
short
short
advertisement
to
all
of
you
right
now
it
happens
the
ama
session
on
the
reddit,
and
you
will
be
able
to
check
it
out
and
ask
any
of
your
questions.
Async,
I'm
asking
I'm
answering
these
questions,
so
we
can
actually
have
a
discussion
there,
pretty
good
questions.
Some
of
the
questions
appeared
there.
D
Yeah,
of
course,
too
much
too
much
stuff
to
even
remember,
but
some
of
the
highlights
here.
So
of
course
we
deployed
everything
everywhere
you
could
have
showed.
The
links
here
show
the
networks
page,
the
the
endpoint
urls
are
yeah
and
when
you
are
also
here
so
you
know
the
the
one
thing
that
we
certainly
did
not
have
enough
time
for
this
week
was
documentation,
so
the
dog
site
sucks
and
we
know
it
and
we
will
fix
it
over
the
next
week.
D
But
at
least
the
basic
information
is
there
for,
for
those
who
are
already
advanced
users,
and
we
we
set
up
an
api
status
page
where
you
can.
Oh
okay,
we
have
a
third
issue.
I
guess
I
had
already
accepted
this
in
my
browser
and
didn't
see
it
yeah
all
right.
D
That's
a
good
one,
that's
a
good
question.
Maybe
maybe
a
different
browser
will
let
you
show
it.
Google
is
very
opinionated,
let's.
Why
don't
I
share
it
from
here.
E
D
Will
see
what's
going
on
with
the
ssl
certificate,
but
we
have
our
nice
status
page
where
we
are
tracking
the
operational
status
of
our
services
and
they're
currently
running
on
google
cloud
platform.
So
we
also
highlight
the
current
status
of
that
and
we
are
tracking
the
various
metrics
right
now,
I'm
surfacing
here
the
average
latency
for
responses,
but
we
will
service
a
lot
more
in
the
future
and
here's
also
the
public
incident
log
which
will
keep
updated.
D
So
this
kind
of
things
yeah,
and
if
you
control
the
public
change
log
as
well
from
next
link
there.
So
we
we
we
want
to
be
as
transparent
as
possible,
which
means
that
any
and
all
changes
that
affect
developers
or
of
on
aurora
using
aurora
will
be
documented
on
on
this
page
here.
So
it's
a
good
one
to
bookmark
and
anything
anything
which
we
deploy,
which
could
potentially
you
know
negatively
or
positively
affect
somebody's
developer
experience.
It
will
be
here,
so
those
are
some
of
the
some
of
the
highlights
I'll.
A
A
Okay
yeah,
so
I
believe
there
is
a
plan
how
to
how
to
mitigate
this
already
so,
probably
in
the
next
couple
of
weeks
or
something
we
will
be
able
to
fix
it
and
and
deploy
it.
Okay,
cool
you've
gained
your
kind
of
what's
on
your
side,.
E
A
lot
of
reviews
fixes
and
almost
important
to
all
of
them.
Kyrie
lebron
found
a
bug
related
to
minting
and
burning
feet
for
real
layers,
so
it
was
critical
back
fixes
it
and
additionally,
as
josh,
propose,
probably
find
some
solution
to
for
early
checking
our
assertions.
E
E
So
I
think
we
shouldn't
have
any
issues
related
to
that
also
fixed
finish
deposit,
because
we
have
a
small
issue
related
to
improve
hash
because
for,
for
example,
if
we
have
some
problem
with
recovery
improve
we,
we
can't
successfully
mint
tokens.
So
that
issue
was
fixed
too,
and
also
fixed
tests
and
additional
tests
for
covering
assertions.
A
Okay
seems
like
quite
quite
productive
for
you,
as
as
for
all
of
the
other
people
here,
okay,
frank,.
G
Yeah
I
was
doing
research.
I
had
a
lot
of
conversations
with
different
contacts
about
the
legal
setup
and
some
discussions
and
wrote
it
up
and
yeah
a
lot
of
other
administrative
tasks
and
meetings
this
week
and
yeah
didn't
continue
with
the
testing.
Before
I
launched.
That's
what
I'm
gonna
do
next
week.
A
B
B
So
a
lot,
a
lot
of
the
prs
are
just
like
things
that
came
up
during
that
review
and
a
lot
of
it
was
through
discussion
with
r2.
For
example,
aren't
you
recognized
that
we
should
have
a
version
storage
system
so
that
if
we,
if
we
ever
were
to
update
the
storage
or
like
yeah?
Basically,
if
we,
if
we
implemented
the
storage
differently,
we
could
then
increment
that
that
version
and
and
not
have
to
migrate
everything.
B
So
that
was
a
big
thing.
There
was
also
the
block
cash
because,
as
as
people
that
I've
been
following
before
we've
just
been
returning
zero
for
that,
but
then
we
realized
that
won't
work
for
some
cases,
so
that
was
updated
to
more
closely
followed
ethereum.
B
There
was
an
emergency
update
for
evm
core,
which
luckily
just
came
out
just
before
we
launched,
so
we
quickly
pushed
that
out.
I'm
glad
I
glad
I
saw
that
just
in
time.
B
And
then,
or
at
least
an
hour
before
we
noticed
it,
and
then
there
was
also
the
backwards
generational
storage
or
backwards
compatible
generational
storage.
That
was
that
was
important
too.
I
guess
those
were
kind
of
all
the
updates
and
there's
just
reviews
and
lots
of
discussions
with
rt,
corel,
marcelo
and
others
yeah.
That's
my
beak
in
a
nutshell,.
A
Yeah
just
wanted
to
say
thanks
to
to
vaitan
who,
who
shared
with
us
specifically
the
security
advisory
yeah.
B
A
Okay,
cool
kirill.
What's
on
your
side,.
F
So,
on
my
side
on
this
week,
I
was
doing
a
lot
of
prerelease
and
post
release
things
with
aurora
kim
with
arto
joshua
marcelo
michael.
F
F
Also,
what
which
was
important
is
that
I
found
some
critical
bug
with
deposit
in
our
engineers
connector,
which
allowed
to
burn
any
proof
quite
easily
that
was
already
fixed
by
evgeny
o'hanov
but
yeah.
Obviously,
we
had
a
lot
of
reviews
on
their
test
connector
and
in
our
engine,
but
still
we
find
some
of
these
security
bugs.
So
we
need
to
put
even
more
attention
to
this
pr.
H
Well,
I
was
working
as
usual.
Maintaining
the
rainbow
bridge.
A
couple
of
wishes
arise
it
well,
we
will.
We
were
able
to
mitigate
some
of
them
only
in
robson.
So
that's
important,
not
none,
then
maintenance,
important
thing
to
say
that
right
now,
robstein,
like
near
to
e3
layer,
is
stopped
because
an
issue
that
we
can
discuss
later
so
other
than
that.
H
A
Yeah
a
short
note
to
to
all
of
the
rainbow
bridge
users.
You
potentially
might
experience
some
some
small
issues
with
with
the
timings
of
the
of
the
transfers
from
from
near
to
ethereum.
We
are
working
on
this.
It's
it's
a
known
problem,
so
transfers
might
take
a
little
bit
longer
than
10
hours
in
the
mean
okay,
mats.
H
Yeah,
so
we're
working
on
all
the
planned
activities
that
were
leading
up
to
your
aurora
launch
design
and
development
of
the
bridge,
prototype
response
to
several
issues
that
popped
up
after
the
launch
and
collaborating
with
pierre
and
alex
on
the
approach
for
the
test
net
bridge,
which
I
think
we
have
a
nice
nice
solution
for
that
and
then
organizing
some
following
activities
related
to
the
website.
And
then
several
meetings.
A
Yeah-
and
here
is
I
want
to
to
shout
out
to
to
alex,
and
if
this
is
not
me,
this
is
an
external
person
who
is
helping
us
with
this,
so
alex
say
if
you,
if
you
are
going
to
watch
this
video.
Thank
you
very
much.
We
appreciate,
in
your
help.
A
I
So
this
week
I
did
a
little
more
review
on
each
connector
and
helped
them
fix
up
some
of
the
tests
that
were
failing,
wrote.
Some
more
tests
for
the
engine
did
some
documentation
work
so
that
you
know,
like
karto,
said
our
doc's
still
stuck.
I
But
hopefully
this
is
like
slightly
less
now
and
was
working
with
with
marcelo
and
joshua
on
this
crate,
2
self-destruct
thing
and
was
also
addressed.
A
B
A
Okay,
okay,
yeah
and
shout
out
to
evgeny
kuzakov,
who
actually
did
audit
a
smart
contract.
So
thanks
for
doing
this,
pierre,
what's
up.
H
Hi
yeah,
so
the
first
part
of
the
week
I
was
working
on
the
test
net
pre-release,
so
to
be
able
to
send
eth
heath
to
aurora
testnet.
But
so
after
that
I
had
a
bit
more
time.
So
I
did
some
small
front
end
fixes
to
the
front
end.
Did
some
dock
styling
for
our
toe
and
recently
added
some
ci
and
github
actions
for
our
front-end
and
client
repositories.
A
Okay,
let's
go
sweet
and
nice
update
from
everybody
did
we
did
we
missed
some
somebody,
so
you
done
as
always.
Thanks
for
joining
us,
do
you
wanna
we
can.
We
can
put
you
in
this
updates.
If
you
want.
I.
B
G
A
I
think
that's
is:
is
this
correct
the
correct
spelling
of
your
last
name
nope?
It's.
A
Yeah,
okay,
so
I'm
going
to
put
you
actually,
why
not
you're
joining
all
the
calls
you're
actually
working
quite
a
lot,
focusing
like
a
hundred
percent
of
your
time
on
aurora
yeah?
Maybe
you
can
maybe
you
can?
Maybe
you
can
update
us.
G
I've
been
also
sort
of
doing
stuff
on
legal
structure
side
trying
to
coordinate
with
mikko
in
regards
to
certain
basically
research
on
legal
entities,
so
we're
considering
like
gibraltar
is
in
kaiman,
seychelles
and
lots
of
other
options,
so
I
will
be
connecting
with
mikko
on
monday
to
finalize,
basically
almost
like
sort
of
handed
off,
then
I'm
also
working
with
alex
trying
to
help
with
fundraise
so
we'll
help
to
structure
it,
we're
still
figuring
out
basically
who
to
reach
out
to
when
and
how
and
what
tools
to
use
so
yeah.
G
Today,
basically,
my
plan
is
to
try
to
structure
on
the
upside,
who
we
go
and
just
make
sure
that
we,
like
you
know
we
it
basically
to
make
sure
that
it's
easy
for
us
to
access
all
the
past
conversations,
future
conversations
and
so
on
so
yeah.
That's,
I
think,
that's
it.
On
my
end,
cool
cool,
oh
and
yeah,
and
I'm
trying
to
do
twitter
stuff,
I
don't
know
yeah.
G
A
Yeah,
oh
cool
thanks
for
doing
this,
so
do
we
have
any
major
things
to
discuss
because
it
seems
like
there
are
tons
of
tons
of
stuff
that
are
on
everyone's
plate
right
now.
Well,
as
expected,
you
know
any
any
big
things
that
needs
to
be
discussed
by
the
whole
team.
D
Well,
just
so
everybody
knows
we,
we
need
to
stand
up
one
more
relay,
so
we
on
this
net
testnet.
We
deployed
the
master
branch,
the
same
the
same
as
on
maintenance
for
the
engine
and
that's
to
keep
them
on
par,
so
that
it's
actually
a
useful
testing
environment
for
for
maintenance,
which
means
that
to
be
able
to
also
support
forward-looking
work
with
more
experimental
branches
of
the
engine,
we
need
to
have
a
separate
deployment
which
is
now
deployed.
D
It's
called
the
develop
that
aurora
on
and
that's
that's
pulling
in
currently
the
f
connector
branch
which
is
going
to
land
on
the
development
branch
soon,
and
the
problem
is
that
you
can't
really
do
much
with
that
without
our
layer
and
it
needs
its
separate
relay
because
it
has
its
own
transaction
history
and
account
balances
and
and
so
on.
So
this
is
a
blocking
appear.
I
believe,
and
my
plan
is
to
stand
it
up
in
the
in
the
next
days.
D
I
wanted
to
do
it
today,
but
there's
too
many
other
modifiers.
So
there
are
a
few
a
few
more
days
to
wait
potentially,
but
by
monday,
surely
we
will
have
it
for
you.
D
D
What's
happening,
there
is
that
although
the
transaction
gets
successfully
deployed
and
the
relay
returns
a
successful
result,
you
know
transaction
received
in
any
case,
truffle
believes
that
the
transaction
reverted
and,
of
course,
truffles
are
the
transitive
closure
of
truffle
code
base.
It's
a
humongous
code
base,
it's
it's!
It's
absolutely
insane,
and
it's
I'm
instrumenting
that
you
know
best.
I
can
to
try
to
pinpoint
why
truffle
would
believe
that
it
reverted
when
it
didn't
we'll
get
to
the
bottom
of
it
soon.
I
hope.
B
A
Well,
in
general,
I
think
that
the
plan
should
be
the
following,
and
this
is
something
that
is,
I
believe,
many
of
you
have
anticipated
for
a
pretty
long
period
of
time,
so,
right
now
after
the
launch.
Obviously
we
need
to
do
hot
fixes
and
we
need
to
clean
up
everything
and
we
exactly
have
the
time
for
this.
So
on
the
business
side,
we
are
doing
the
fundraise
and
we
are
aligning
a
set
of
the
partners
with
which
we
are.
A
We
would
like
to
you
know,
develop
stuff,
and
this
is
a
very,
very
yeah-
and
you
know
legal
setup
and
stuff
like
that.
But
this
is
exactly
the
right
time
for
us
to
to
clean
up
the
the
technical
depth
that
we
have
and
if,
if
there
is
anything
in
your
mind
that
you
think
that
can
be
can
be
made
better
can
can
can
have
a
purpose
of
speeding
up
speeding
up
the
development
in
the
future.
A
Then
well,
you
just
communicate
this
and
well
this.
This
is
the
moment
when
we
can
do
this.
Please
remember
that.
A
Well,
let's,
let's
use
this
this
time
wisely
and
let's
not,
let's
not
stop
right
after
the
release
yeah
so
once
once
we
will
we
we
will
finish
the
invest
round
and
and
then
the
setup
of
a
dow
and
maybe
with
some
additional
activities
after
it,
we
will
need
to
get
back
to
the
new
features:
development
yeah.
There
are
some
in
the
list,
but
this
is
obviously
up
to
our
discussions
but
like
right
now,
let's
not
waste
this
time.
Let's
organize
us!
A
D
I
think
we
probably
have
enough
files
to
put
out
that
it
makes
sense
to
end
early
today
and
next
week
we
can
come
back
with
everything.
Also
note
that
we
we
plan
out
to
every
every
week,
do
not
only
this
update
video
publicly,
but
then
follow
it
up
with
a
blog
post
starting
from
next
week,
because
this
week's
blog
post
is
already
the
aurora
launch.
D
So
yeah.
A
D
Yeah
yeah,
the
new
section
can
work
for
now.
It's
fine,
it's
a
little
bit,
maybe
too
formal
to
call
it
news
but
sure
yeah
yeah
until
we
do
a
technical
block,
it's
a
fine
division.
Yeah.
A
Yeah:
let's
do
it,
okay,
cool!
So
should
we
go
over
the
plans
or
for
the
next
week.
D
We
can,
of
course,
but
you
know
generally,
and
I
think
the
list
doesn't
make
too
much
sense.
We.
D
Discovering
issues
and
fixing
the
discovery
and
fixing
it
yes,
yeah
and
and
yeah
quality
quality
work
will
be
good
being
paying
off
a
little
technical
debt
all
over
the
place
yeah
I
I
I
would
suggest
that
it's
not
too
useful,
too
yeah
talk
specifics
here,
right
now:
cool
cool,
okay,.
A
Okay,
so
if
you
want
to
to
put
here
some
specific
things,
please
do,
but
in
general
yeah
this
is
what
we
are
going
to.
D
Do
I
think,
alex
the
most
useful
thing
that
somebody
listening
to
us
might
want
to
know
is
when
we
are
launching
the
bridging
of
ethan
erc20s.
So
maybe
you
can
comment
on
that
questions.
A
Yeah
preaching
of
f
in
and
and
earset
one
is.
We
are
finalizing
this
right
now.
Our
our
estimate
for
this
is
that
we
can.
We
would
be
able
to
deploy
to
the
mainnet
within
two
weeks
from
now,
so,
hopefully
sooner,
but
maybe
maybe
in
two
weeks
from
now.
So
this
this
is
the
plan.
A
I
believe
we
should.
We
should
fit
in
in
spring,
so
we
can.
We
should
do
it
in
spring,
so
yeah
and
that
this
will
be
obviously
crucial
for
for
applications
that
are
launching
and
actually
shout
out
to
the
development
community
of
aurora.
It
started
to
form,
and
we
are
happy
to
see
that
there
are
some
projects
that
are
that
are
already
planning
to
launch
on
aurora
and
they
are
already
there.
Actually,
they
are
already
developing
and
asking
some
questions
so.
H
A
There
is
a
solution,
the
the
the
uni
swap
version
to
clone
that
is
called
bloody,
swap
the
guys
are
planning
to
launch
extremely
soon.
I
would
say
so.
Kind
of
cool
ecosystem
is
developing.
B
E
B
D
Of
us
work
the
weekends
for
quite
some
stretch,
so
let's
take
it.