►
From YouTube: Aurora Update [2021-06-18]
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
So
hello,
everybody
welcome
to
aurora
update
today
is
18th
of
june
and,
as
always,
every
friday
we're
doing
the
public
update
to
our
community
to
share
what
is
happening
in
aurora
and
what
a
new
alpha
licks
you
can
get
from
us.
A
This
week's
this
week
we
were
working
quite
a
lot
on
multiple
things,
mainly
around
the
bridge,
and
we
have
some
exciting
news
to
you
well.
A
First
of
all,
I
would
like
to
start
with
the
contracts
for
f
and
e
or
c20
connectors,
and
these
have
been
fully
released
on
the
test
net
and
by
saying
fully
I
mean
that
the
transfers
for
both
of
these
connectors
are
working
in
every
direction
in
between
ethereum
near
and
aurora
right
here
right
now,
you
can
try
it
out
on
test
net
pretty
soon
they
are
going
to
be
on
mainnet,
not
not
this
week,
but
you
will
see
it,
but
you
can
try
it
already
on
the
test
for
these
changes
to
be
valid,
we
have
updated
two
times
aurora
engine
you
can.
A
Besides
that
we
have
and
like
this
is
not
a
visible
update
to
you,
but
this
is
the
most
important
thing
that
we
have
been
working
since
the
release
of
aurora
the
initial
release
of
aurora.
So
this
is
a
huge
success
for
the
team
and
congratulations
to
all
of
us
here.
A
A
test
net
faucet
ui
was
updated.
We
have
been
showing
it
to
you
on
the
previous
week
and
now
it
looks
awesome
just
take
a
look
here.
A
This
is
aurora's
test
net
faucet
and
you
are
able
to
get
your
faucet
you're
able
to
get
your
aurora
f
on
test
net
right
here
you
can
go,
you
can
go,
you
can
request,
one
add
from
faucet.
Actually
I'm
okay
request,
yeah,
okay,
so
yeah!
It
says
there
is
some
kind
of
limit
in
here
also,
so
I
have
enough
test
and
f.
A
So
sorry,
no
test
and
add
for
me
probably
need
to
move
it
somewhere
and
then
I
will
be
able
to
get
more
and,
as
you
can
see,
I
I
already
connected
with
aurora.
I
have
8.52
f
here.
So
that's
why
I
cannot
play
more,
but
this
is
working.
You
can
go
there.
You
can
go
and
see
it
on
testing.dev,
slash,
faucet
and
in
case
you
are.
You
would
like
to
navigate
to
this
to
this
url.
You
can
go
to
aurora.dev.
A
And
then
you
are
able
to
go
to
resources,
test
and
bridge
and
then
in
testnet
bridge
you
are
able
to
get
here,
need
some
aurora,
and
this
is
the
link
to
the
faucet.
This
is
the
way
how
you
are
navigating
stuff:
okay,
so
cool
new
test
and
faucet.
Please
use
it
share
your
feedback
on
this.
I
think
it
looks
just
awesome.
A
We
also
have
released
the
testnet
bridge
video,
and
this
is
the
video
for
everyone
who
would
like
to
to
understand
how
how
to
how
to
breach
things
in
aurora.
This
video
is
made
by
michael
super
cool
super
nice.
Only
three
and
a
half
minutes.
It
will
give
you
the
full
understanding
of
how
aurora's
bridge
is
working
and
yeah.
You
can
just
take
a
look
at
it
and
and
and
and
continue
step
by
step
with
the
aurora
bridge,
really
nice
and
smooth
experience.
A
A
We
updated
the
way
how
the
transfers
are
working
in
between
ethereum
and
near
inside
of
the
rainbow
bridge.
This
will
actually
going
to
be
this
is
this
is
the
thing
that
is
going
to
be
required
for
the
transfers
to
aurora
too
so
now,
all
of
the
transfers
that
are
going
from
ethereum
to
near
independently,
whether
it
is
near
native
environment
or
aurora
environment.
A
These
transfers
are
going
to
be
automatically
finalized.
What
does
it
mean?
It
means
that
a
user
doesn't
need
to
schedule
an
additional
transaction
and
wait
for
this
10
minutes
in
between
the
initial
set
of
transactions
on
ethereum
and
additional
finalization
transaction
on
near,
and
the
reason
why
we
did
it
is
obviously
to
enable
transverse
aurora,
because
users
of
our
users
will
not
be
able
to
send
transactions
to
near
native
runtime,
and
this
is
how
the
bridge
is
working.
A
So
that's
why
we
need
it.
We
need
to
do
it,
but
the
good
outcome
of
this-
and
this
is
the
second
thing
that
we
have
here-
is
that
this
we
are
finally
fixing
the
issue
for
the
rainbow
bridge
users
that
have
ledger
protected
accounts,
as
you
know,
or
maybe
maybe
you
don't
know,
but
ledger
protected
accounts.
A
Now,
this
finalization
is
happening
automatically.
This
is
a
dramatic
improvement
to
the
user
experience
and
it
will
be
absolutely
the
same
as
you
can
see
right
now
in
aurora
bridge,
on
the
test
net.
So
you
are
just
starting
the
transfer
and
then
once
your
ethereum
transaction
is
confirmed,
yeah
you
can
just
go
and
make
some
tea
for
yourself.
You
do
not
need
to
do
anything
and
in
around
five
or
maybe
10
minutes,
the
transfer
is
going
to
arrive
to
near
and
the
funds
will
be
automatically
deposited
to
your
near
or
aurora
account.
A
This
thing
is
this:
new
nuclear
feature
is
already
deployed
to
the
test
net
you're
able
to
experience,
experience
it
there
and
a
little
bit
later.
Today,
it's
going
to
be
available
on
the
mainnet.
So
again,
just
just
congratulate
everybody
on
this.
We
finally
will
be
able
to
remove
that
yellow
mark
from
the
rainbow
bridge.
Ui
that
says
that
ledger
account
ledger.
Protected
accounts
are
currently
not
supported,
so
congratulations
to
all
of
the
teams.
A
You
have
been
doing
a
good
job
here,
super
cool,
so
these
are
the
main
updates
for
for
today
on
you
know,
on
the
high
level,
so
let's
go
deep
into
each
and
each
team
member
update
for
this
week
and
as
always,
we
are
doing
it
in
alphabetical
order.
So
that's
pretty
simple
to
understand
when,
when
people
are
going
to
to
do
their
updates
ahmed,
let's
start,
as
always
with
you.
B
Yeah
hi
everyone,
so
mainly
for
my
site.
This
week
I
was
working
on
fixing
the
rpc
relayer
in
the
points,
and
I
have
updated
the
deployment
scripts
for
lily
swap
on
aurora.
So
now
you
can
deploy
vlogs
weapon
very
easily
and
working
also
on
a
minor
documentation,
facts
and
they
fixed
the
gas
price
issues
that
was
reported
on
telegram
on
the
hard
hat
examples
and
reviewing
a
couple
of
pr's
and
researching
the
alternative
for
speeding
ups,
our
ethereum
transaction
finality,
I'm
gonna
add
my
proposal
on
this
discussion.
B
A
Yeah,
I
just
wanted
to
say
so
ahmed
here
he's
not
selling
this
a
lot,
but
just
just
to
tell
you
now
a
lot
of
swap
guys
that
are
building
their
own
amm
solution,
which
is,
I
believe,
a
fork
of
a
sushi
swap,
so
they
now
deployed
their
solution
to
the
tester
right.
So
they're
already
testing
it.
So
this
is
a
very
cool
thing.
A
They
were
fixing
the
box
and
ahmed
was
helping
them
a
lot
with
this
on
the
on
the
side
on
the
aurora
side,
so
ahmed
good
job
at
last,
it
is
here
it
at
last.
It
is
like
a
very
a
pretty
complicated
smart.
Con
set
of
smart
contracts
are
deployed
to
aurora
and
everything
is
working.
So
that's
super
cool,
okay,
my
update,
mainly
I
was
working
on
funding
around
and
this
week
is
the
final
week
for
the
funding
rounds.
I
was
finishing.
All
of
the
investor
meetings
still
need
to
do
several
of
them.
A
Later
today,
I
started
to
gather
the
feedback
from
the
investors
on
the
underground
and
on
on
the
structure
of
the
round.
So
this
will
help
me
and
julian
together
we're
going
to
to
compose
around
over
the
weekend
and
for
some
investors
I
was
communicating
the
updated
term
sheet.
As
I
said
last
week,
we
have
our
drum
sheet.
We
have
made
the
decision
to
update
the
term
sheet,
so
we
need
to
communicate
this
to
the
investors.
A
I
was
participating
in
a
couple
of
events
or
like
three
events.
One
is
the
reimagine
version,
9.0
panel
discussion
with
dota
and
our
bedroom.
It
is
pretty
nice,
it
was
a
pretty
nice
discussion,
it
was
pre-recorded
and
it's
going
to
be
released.
I
believe
on
saturday
or
sunday
so
check
out
the
at
the
conference
and
you
will
be
able
to
see
it.
A
It
was
pretty
nice
nice
discussions,
not
nice
teams
and
also
I
was
participating
in
the
arab
blockchain
week,
and
this
is
pretty
large
summit
with
multiple
tracks
there.
I
was
given
there
a
talk
about
aurora,
a
solution
to
extend
the
ethereum
economy
and
was
participating
in
the
panel
discussion.
Investing
in
blockchain
also
some
interesting
insights
there,
some
pretty
strong
opinions
discussed
there
internally,
I
was,
I
was
spending
quite
a
lot
of
time
on
the
spin
out
management
matters
right
now.
A
Nier
is
trying
to
figure
out
how
to
do
the
spin
outs
properly
and
at
least
includes-
and
this
is
not
only
valid
for
aurora-
there's-
a
probably
one
of
the
biggest
spin
outs
right
now,
but
this
is
valid
also
for
for
other
spin-outs.
So
anir
is
trying
to
to
make
sure
that
these
spin
outs
are
happening,
smooth
and
clean,
and
there
is
some
kind
of
framework
how
to
do
it.
A
I'm
congratulations
congratulating
the
team
again
during
this
call.
We
have
a
new
hire.
Dmitry
is
going
to
join
us
as
a
at
a
devops
position.
His
manager
will
be
frank.
Some
of
you
already
have
spoken
to
dmitry
within
our
interview
process
and
he's
going
to
join
us
in
july.
A
So
so
just
I'm
happy
that
additional
people
are
coming
on
board
and
and
they're
going
to
help
us
with
all
of
our
complicated
infrastructure
right,
an
additional
topic
this
week.
The
discussions
around
the
bridges
were,
you
know,
coming
out
of
nowhere
near
ecosystems
starts
to
build
bridges
and
obviously
they
start
with
exploring
of
of
rainbow
bridge.
A
So
the
rightly
I
have,
I
have
been
contacted
by
two
teams
that
are
built
in
dragon
bridge
and
unknown
bridge
right
now,
and
the
dragon
bridge
is
the
british
in
between
near
and
bc,
and
another
bridge
is
the
bridge
to
polygon.
A
So
these
two
teams
are
currently
building
their
solutions.
They
are
in
different
stages,
though
I
believe
the
interconnected
future
is
quite
close
to
us,
especially
taking
into
account
the
bsc
and
polygon,
are
evm
compatible
chains.
So
these
teams
can
reuse
almost
fully
the
code
of
the
rainbow
bridge
and
I
believe
we
need
to
so
I'm
we're
going
to
discuss
it
in
our
internal
call
yeah,
but
there
are
multiple
things
that
that
how
we
can
help
these
teams
to
work
with
this.
C
On
my
side
as
every
week
I
troubleshooted
and
fixed
issues
with
ahmed
this
week.
My
my
main
focus
was
the
aurora
engine
releases
to
support
the
fn
ps820
connectors.
So
we
did
two
releases
this
week,
which
means
our
cadence
is
picking
up
the
in
the
previous
weeks.
We
didn't
quite
manage
to
average
one
one
release
a
week
now
now
we're
doing
two
per
week
and
intend
to
continue,
we
reviewed
and
merged
and
released
about
20
different
pull
requests
for
for
the
engine
during
this
week.
C
So
that's
also
quite
a
quite
a
record.
The
one
1.3
release
was
quite
big
and
1.4,
more
incremental.
In
addition
investigated
issues
on
on
testnet.
This
currently
actually
an
and
our
first
proper
incident.
It's
not
due
to
our
infrastructure
per
se.
It's
the
near
near
endpoints
are
having
some
trouble.
You
could
maybe
show
the
api
page.
So
people
know
what
what
I
incident
look
like.
D
C
So
this
is
currently
being
investigated.
We
we
are
aware
that
some
transaction
submissions
on
the
on
the
disney
are
receiving
an
internal
server
error,
not
not
all,
but
but
some
of
them,
and
we
are
working
with
upstream,
as
in
with
the
sra
team
at
near
to
troubleshoot.
C
What's
ailing,
ailing
the
this
net
rpc
nodes.
D
C
C
C
C
So
I
sorted
out
the
dependency
hell
made
it
work.
I
tested
different
rpc
compatibility
modes
that
it
has
so
it
supports
geth,
parity,
bezel
and
ganache.
C
So
I
I
went
both
through
those
and
the
geth
mode
works
best
with
our
rpc,
but
in
any
case
in
in
any
of
these
modes
it
required
some
additional
rpc
non-standard
rpc
methods
to
be
implemented.
So
I
implemented
those.
So
we
have
now
gets
a
tx
pool,
apis
implemented
in
you,
know,
reliable
and
we
have
some
some
equivalent
priority
apis
implemented
as
well.
So
now
it
appears
that
the
the
blocks
called
per
se
does
work
and
get
us
back
to
the
question
of
backfilling
the
historical
data
that
it
needs.
So
that's
that's.
E
C
F
I
was
working
on
a
host
math
api
pull
request.
It
appears
to
be
more
difficult
than
I
expected,
because
not
just
there
is
it's
not
trivial
to
implement
the
hash
correctly.
Actually,
there
is
some
problems
with
easy
recovers,
so
basically,
there
are
some
different
ways
that
ethereum
uses
to
verify
its
signatures
like
there
is
one
way
that
it
uses
to
verify
transaction
signature,
another
way
that
it
uses
to
verify
signatures
in
its
ibm's
ec
recover
pre-compile,
and
it's
not
as
easy
as
just
calling
a
library
function.
F
We
need
to
actually
so
it's
all
because
of
historical
reasons,
and
now
we
want
to
get
100
compatibility,
so
we
need
to
implement
the
host
function
that
can
actually
correctly
implement
all
those
use
cases
that
we
have
only
in
the
evm
and
also
outside
the
evm.
We
want
this
cost
function
will
be
not
just
for
the
vm
but
in
general
to
verify
those
signatures.
F
A
Yeah
yeah
we
need
to.
We
need
to
have
full
compatibility,
so
let's
push
for
this,
but
I
just
want
to
reinforce
the
fact
that
this
is
a
probably
the
most
important
update
of
the
protocol.
That
is,
that
that
the
most
for
aurora
for
aurora,
okay,
we've,
given
you
honor.
D
I
completed
the
implementation
related
to
our
ordered
our
ui.
Currently,
all
functionalities
related
to
aurora
dao
run
a
smart
contract.
A
D
Yeah,
I'm
doing
pretty
good.
Are
you
also
good
I
this
week
I
set
up
slack
with
select
connect
for
aurora
labs,
so
you
all
have
invites
if
you
haven't
signed
up.
Please
do
so.
You
will
soon
be
kicked
out
from
the
near
slack
and
yeah
with
slack
connect.
It's
super
easy
to
connect
to
other
organizations,
so
we
can
basically
create
channels
across
two
organizations.
D
I
also
did
a
lot
of
infrastructure
work.
A
lot
of
that
is,
you
know,
security
related,
so
I'm
not
gonna
discuss
it
on
the
public
call,
but
you
all
have
been
heard
from
me
about
that
already.
So
you
probably
know
what
I'm
talking
about
interviewing
a
few
candidates
this
week
and
then
on
thursday
we
had
a
distributed.
An
island
service
attack
on
the
bridge
front
end
which
was
taken
down,
and
then
I
spent
the
most
of
thursday,
together
with
marcelo,
bringing
it
back
up
and
also
had
some
lessons
learned
there.
G
Yeah
good
yeah,
good,
you're,
good,
it's
going
good
yeah.
So
this
week,
I'm
mostly
focused
on
the
math
api
and
also
preparing
berlin,
because
we
gotta
we
gotta
change
a
lot
to
to
sputnik
to
to
support
to
support
it.
So
I
spoke
a
little
bit
to
a
tang.
G
I
still
gotta
come
up
with
a
plan.
I
got
an
idea
how
we're
going
to
tackle
it
and
then
next
week
we're
basically
going
to
going
to
hammer
through
that,
but
also
this
week
vip2565
is
in,
which
is
the
first
for
berlin,
so
we're
getting
there.
F
Hey
everyone,
so
for
me,
on
this
week,
my
update
is,
I
was
working
on
the
implementation
of
years,
20
exits,
heart
attacks
and
the
storage
regression
test.
It
will
be
finished
really
soon.
I
also
worked
on
the
in-ear
connector
sometime
debugging.
Some
issues
working
on
some
bug
fixes
and
new
functionality
also
did
some
improvements
to
ventral
air
and
started
doing
refactoring
and
additional
props.
F
That
will
be
able
to
help
us
on
the
devops
things,
so
we
will
be
able
to
check
the
healthiness
and
lightness
of
the
eventual
layer
quite
easily.
F
A
Yeah
good
stuff
for
those
of
you
who
who
hear
about
eventual
air
for
the
first
time.
This
is
the
thing
that
actually
automatically
finalizes
the
transfers
right
so
yeah.
I
think
that
developed
by
kirill,
so
good
job,
good
job.
E
It's
doing
good
hi
everyone,
so,
on
my
end,
I
was
helping
from
brown
frank
with
the
incident
about
our
front
end.
That
was
quite
funny
quite
interesting.
For
me,
yeah
biggest
task
of
this
week
was
the
release
of
aurora
of
the
rc20
and,
if
pre-compiles,
that
allows
transfer
not
only
inside
of
roda
but
also
outside
of
rotating
here
into
ethereum,
so
that's
already
deployed
on
testnet.
E
So
that
was
a
big
part
of
the
of
the
work
this
week
and
we're
still
testing
all
the
workflows
part
of
what
we
release
it
to
testnet
is
because
it's
way
easier
to
to
test
stuff
there
even
connecting
the
front
end
and
everything
so
other
than
that
I've
been
working
on
this
tool
for
easier
testing
in
the
future,
which
are
the
docker
image
of
all
our
tech.
E
So
with
these
images
we
will
be
able
to
release
it
locally,
have
a
good
way
to
test
a
lot
of
stuff
there.
So
well,
working
on
the
relayer,
eventually
layer
that
you
were
mentioning
before
and
I
started
reviewing
the
nft
connector,
but
have
done
little
work,
get
there
just
understanding,
high
level
ideas.
A
Okay,
that's
great
yeah,
just
for
for
the
information
of
everyone
who
is
watching
the
this
video.
We
have
a
community
member
that
was
developing
the
nfc
connector
for
us.
This
is
something
that
is
highly
requested
by
the
community.
A
People
want
to
move
nfcs
to
near
and
be
able
to
transact
them
at
the
for
at
really
really
low
prices.
A
So
yeah
we
have
been
building
the
nft
connector,
and
this
is
this
is
the
connector
that
supports
erc721
tokens
and
even
patched
batched
move
transfers
of
this
tokens
to
near
all
right.
So
it's
in
a
good,
more
or
less
good
shape,
but
obviously
we
need
to
review
it
thoroughly
and
yeah.
Thanks
marcel
for
picking
up
this
matt.
H
Hey
so
this
week,
what
we
didn't
get
done
was
the
hope
for
bridging
ui
of
the
ethan
erc20
tokens
between
ethereum
and
aurora.
H
We
added
google
analytics
to
the
website
and
removed
google
tag
manager.
As
we
discovered
it
was
breaking
some
client-side
navigation
stuff.
We
added
author
attributes
to
the
blog
articles
so
that
we
can
attribute
who
who
write,
who
writes
our
articles
and
link
them
to
twitter.
H
I
had
a
discussion
with
pierre
about
near
to
aurora,
bridging
and
then
miscellaneous
meetings
and
administrative
issues
around
the
support
system
that
we
that
we
will
probably
be
using
and
how
will
the
process
by
which
will
populate
a
knowledge
base
based
on
the
incoming
questions
into
that
support
system
and
a
little
bit
of
cleaning
up
how
our
team
me
alex
and
pierre
are
working
in
base
camp.
D
I
Are
you
today
yeah
good
thanks,
good
thanks,
so
this
week
I
did
the
video
tutorial
and
a
presentation
for
some
near
folks
internally
and
I
was
helping
out
joshua
with
the
eip
2
565
added
a
little
more
validation
on
our
documentation,
ci
a
couple
minor
refactors,
and
that
was
also
helping
with
the
exit
pre-compiles
that
are
that
are
now
released
and
so
yeah
a
lot
of
small
pieces
of
work.
This
week.
A
I
A
Great
pierre
how's,
your.
H
Night
but
yeah
so
this
week,
I
I
did
some
work
on
the
new
faucet
with
alex.
I
started
to
look
into
the
aurora
near
bridge
ui,
so
seeing
how
we
can
fork
the
front
end
and
discussing
with
that,
how
how
we
actually
want
to
do
this.
I
made
a
draft
with
like
having
the
new
token
set
up
and
all
of
that
so
yeah
most
of
the
architecture
of
it.
H
I
did
a
bit
of
refactoring
in
the
client,
libraries
and
since
last
night,
I've
been
on
the
exit
of
east
from
aurora,
so
I
developed
the
client
and
integrated
it
into
the
front
end
and
had
some
last
minute
issues.
A
No
problem,
no
problem,
it's
going
to
be
it's
going
to
be
pretty
soon.
The
main
thing
is
that
smart
contracts
are
there,
so
everyone
are
able
to
use
them
already
right
now
and
developers
they
need
to
have
a
working
solution
rather
than
the
front
tent.
So
oh
cool
I'll
call
julian.
A
I
just
want
to
say
to
say
that
everyone
we
finalized
last
week
over
the
weekend.
It
was
made
the
final
decision
that
yurian
is
going
to
to
be
with
us
so
just
publicly
embracing
this,
and
welcome.
Welcome
to
the
to
the
public
calls
as
an
official
member
of
the
aurora
team.
Thank
you.
B
So
this
week
I
was
basically
talking
a
lot
to
potential
candidates
was
exploring.
How
can
we
close
bg
and
social
media
roles
for
now?
Not
a
lot
of
success
there,
but
I
think
it's
a
work
in
progress.
B
So
then
I
also
was
helping
alex
with
identifying
some
founders
to
participate
in
the
round,
also
like
kind
of
started,
slowly
preparing
for
ethereum
event
in
paris-
that's
coming
up
next
month
and
trying
to
get
us
to
kind
of
sponsor
a
few
things
since
we
don't
have
dedicated
event
persons.
So
I'm
trying
to
basically
coordinate
as
much
as
possible
with
a
new
court
team.
B
Then
I
also
semi
hired
two
contractors
on
media
operations.
Side
they've
been
helping
me
with
a
lot
of
research
to
understand
basically
better
how
we
can
improve
our
social
media
strategy
and
execute
on
this
identifying
some
of
the
channels
that
I'm
missing.
Basically,
we
did
just
like
competitive
research
to
understand
who
is
using
what
and
things
where
we
should
be,
and
maybe
things
that
we
should
be
doing-
and
I
know
these
guys
are
new
and
they've
been
also
posting
on
basecamp.
B
So
I
would
encourage
everyone
to
participate
in
those
discussions.
We
also
want
to
kind
of
know
your
opinion
on
this
and
yeah.
So
this
is
basically,
you
know,
most
of
the
stuff
that
I've
been
working
on.
A
Okay,
cool
cool,
so
with
that
we're
concluding
the
weekly
updates
of
all
of
the
team
members
here
thanks
everyone
for
your
work
and,
let's
head
directly
into
the
discussion,
we
have
multiple
topics
to
discuss
here
and,
let's
start
with
the
rainbow
bridge
outage
due
to
ddos
frank,
would
you
like
to
to
cover
it.
A
Maybe
not
in
the
details,
but
maybe
just
just
to
update
everyone,
some
some
kind
of
general
info,
for
example
the
one
that
we
have
shared
you.
A
So
yeah,
if
you
will
take
a
look
at
our
twitter
accounts-
and
you
will
take
a
look
here
at
this
particular
tweet
rainbow
bridge
front
end
was
inaccessible
yesterday
june
16th.
So
actually,
two
days
ago,
in
this
time
frame
because
we
have
been
exp,
we
have
been
under
the
targeted,
ddos
attack
on
our
front
end.
A
We
have
been
contacted
by
the
attacker
and
he
was.
He
was.
A
He
was
misleading
us
with
with
the
way
how
how
he
is
trying
and
how
he
is
doing,
but
in
general
it
was
just
the
ordinary
ddos
attack.
So
in
order
to
in
order
to
now
make
sure
that
this
type
of
attacks
are
not
they're
not
going
to
be
possible,
we're
going
to
change
some
pieces
of
our
infrastructure
and
probably
the
updates
are
going
to
be
in
the
following
weeks
and
nobody
will
experience
any
problems
with
accessing
the
bridge
front
end
again.
This
attack
was
focused
only
on
the
front
end.
A
So
some
of
the
people
from
the
from
the
community
have
seen
have
experienced
this
this
attack
because
they
were
not
able
to
get
to
the
front
end.
But
now
everything
is
up
back
again
and
some
intermediary
measures
were
taken,
so
we
can
leave
so
so
the
front
end
will
be
stable
until
the
moment
when
we
are
going
to
to
implement
the
full
protective
measures
here,
just
just
a
just
a
general
update
here.
Obviously
we're
not
going
to
go
into
into
the
details,
how
we
are
protecting
our
front
end.
D
D
A
Yeah
yeah,
okay
cool,
so
I
want
to.
I
want
to
thank
the
team,
because
at
the
moment
when
we
were
contacted
an
attacker
within
10
minutes,
at
least
four
people
were
gathered
together
on
a
call.
So
that
was
a
super
quick
reaction.
Thanks
everybody
for
this.
A
I
believe
it
was
a
very
good
test
case
for
us.
So
the
issue
was
not
is
not
that
big,
but
I
believe
we
were.
We
were
doing
good
job
in
terms
of
the
the
reaction
on
this.
So
we'll
go,
oh
cool,
okay,
arthur
you
want
to
bring
this
thing.
The
sporadic
test,
net
transaction
issues
right.
C
Well
right,
so,
just
to
reiterate
the
issue
is
that
due
to
upstream
rpc
endpoint
problems
right
now
during
during
today,
apparently
I
don't
know
yet
the
exact
start
time
we
are
looking
in
the
logs
to
see
when,
when
the
trouble
started.
C
We
we
currently
return
an
internal
server
error
to
some
transaction
submissions
and
the
the
issue
there
is
that
we'll
will,
on
the
one
hand,
need
to
coordinate
faster
with
upstream,
so
it
took
some
some
time
to
get
a
response
and
get
people
working
on
the
problem
and-
and
the
second
second
thing
to
improve-
is
that
we
currently
don't
have
any
concept
of
a
mempool
per
se,
which
could
also
be
called
a
transaction
queue
which
means
that
when,
when
we
get
a
transaction
submission,
we
just
try
to
contact
the
upstream
rpc
endpoint
and
and
submit
the
transaction,
and
if
it
fails,
we
pass
through
the
failure
to
the
client.
C
So
this
obviously
can
be
improved.
We
we
don't
need
to
give
up
on
a
transaction
just
the
first
time
around.
We
can
keep
them
around
and
try
even
a
few
different
rpc
end
points
for
submission.
C
A
Okay,
then,
let's
go
to
the
next
part,
the
the
the
concluding
part,
our
our
our
priorities
for
the
next
week.
So,
let's
start
with
ahmed.
B
Yeah
so
for
now,
mainly
I'm
going
to
continue
working
on
the
east
connector
issue
for
the
ci
and
adding
my
proposal
to
regarding
the
the
transaction
finality
on
the
ethereum
side,
more
documentation
as
well,
and
maybe
if
there
is
any
other
discovered
issues,
so
I'm
gonna
working
on
them.
Yeah
regarding
the
rpc
or
later
and
etcetera.
A
A
So
I
I'm
not
quite
sure
whether
it's
going
to
be
finished
next
week,
but
but
this
will
be
already
off
my
table
and
it
will
be
managed
by
by
the
lawyers.
A
I
would
like
to
to
start
the
discussions
about
dao
and
specifically
about
the
dao
formation,
because
we
would
like
to
move
on
with
with
the
governance
and
with
our
approach
to
the
governance,
and
I
believe
there
will
be
quite
a
lot
of
work
there
and-
and
I
would
like
to
support
all
of
you
with
the
with
f
and
erc20,
a
connector
release
on
maintenance.
C
D
Yeah,
I
continue
with
infrastructure
and
security
work.
I
added
tons
of
like
small
tasks
in
basecamp,
going
to
sync
on
the
continuous
integration
with
michael
and
also
sync
with
auto
regarding
infrastructure.
D
So
it's
mostly
at
this
point
trying
to
define
what
I
can
take
off
artists
plate
and
get
an
overview
of
everything
and
create.
A
Yeah,
I
think
that
for
for
this
specific
point,
let's
let's
discuss
it
on
our
monday
call,
but
I
will
end
here
that
you
probably
need
to
sync
also
with
marcelo.
A
Because
because
of
the
bridge
right
so
martial
knows
a
lot
about
the
bridge.
Okay,.
D
A
A
G
Yeah,
basically,
berlin,
artwork
stuff,
with
with
michael
and
also
finishing
up
math
api
and
getting
that
ready
for
wednesday.
F
I
plan
to
finish
all
tests
that
are
in
progress
and
get
them
to
say
and
support.
I
think
in
year,
c
20
connect
for
at
least
one
minute
and
also
finish
improvements
for
eventual
error
and,
as
usual,
probably
expect
a
lot
of
feature
or
engine
reviews.
E
Well,
I
was
planning
to
also
continue
testing
with
an
end-to-end
test
for
our
release,
two
of
the
rc20
units
transfers.
There
are
several
cases
that
we
need
to
make
sure
they
are
working.
Fine
like,
for
example,
when
you
try
to
transfer
on
an
account,
doesn't
exist
or
a
contract
doesn't
exist.
You
need
to
take
care
of
those
fixing
the
ci
rainbow
bridge,
which
is
and
working
right
now
and
well.
E
It's
the
same
situation
with
the
token
connector,
because
the
pipeline
it's
broken
and
well,
there
are
several
pr's
open
in
the
rainbow
bridge
repository
that
some
of
them
are
actually
live.
Some
of
them
are
not
so
I
want
to
merge
them
or
close
them
and
make
a
release
to
make
sure
that
we
understand
what
is
being
and
continue
with
the
with
the
tool
for
testing
with
the
docker
images
for
bridge,
and
also
I
missed
here-
continue
reviewing
the
nft.
A
We
are
going
to
pass
it
to
to
the
explorer
team
because,
as
far
as
I
know,
explorer
team
right
now,
a
near
explorer
team
right
now
is-
is
implementing
the
support
of
nft
in
inside
of
explorer.
So.
A
A
Okay,
let
me
put
it
as
question
what
to
do
with
the
front
end
for
this
okay
matt.
What
about
you.
H
Assigned
the
first
actions
on
the
dow,
I
already
had
a
discussion
with
with
alex
this
week.
I
forgot
to
mention
that
in
in
the
updates
about
about
that
and
then
looking
into
setting
up
help
scout
as
a
as
an
inbox
for
our
community
help
and
support
questions.
I
Michael,
so
another
presentation
lined
up
for
this
week
and
there's
a
test
that
I
want
to
write
following
up
a
bug
fix
just
to
so
that
you
know.
We
guard
against
regressions,
we'll
sing
with
joshua
about
more
details
on
this,
but
probably
supporting
him
with
berlin,
and
then
some
other
refactoring
trying
to
you
know
make
the
code
always
more
more
testable.
B
What
are
your
plans
help
helping
wrap
up
the
fundraise
then
basically
working
with
matt
on
a
few
things,
with
this
help
scout
and
as
analytic
staff
to
create
basically
like
a
solid
base
for
experimentation
and
being
able
to
unders
like
track
results
and
yeah
and
basically
kick
off,
probably
like
first
martian
campaign
at
least
start
coordination
with
one
of
the
kind
of
companies
we
work
with
and
yeah
that
would
and
continue
recruiting
recruiting
will
be
ongoing.
B
So
if
anyone
has
any
good
candidates,
please
send
them
my
way,
especially
like
non-technical
ones.
H
The
way
alex.
A
H
Are
we
looking
for
any
community
managers?
I've
had
a
couple
candidates
reach
out.
B
F
A
Yeah
in
general,
udon
now
is
taking
care
of
everything
that
is
connected
with
with
hiran
so
yeah
forward.
Everything
to
you,
then,
okay,
great
any
closing,
remarks,
closing
thoughts.
A
So,
just
to
conclude
everything
then,
once
again,
I
would
like
to
reinforce
what
we
have
been
deployed
and
what
we
have
been.
What
we
are
releasing
this
week
go
check
out
the
testnet
ui
of
a
test
and
faucet
ui.
It
looks
super
cool
in
case
you
in
case.
A
You
would
like
to
share
how
aurora
bridge
is
working
with
your
friends
or
you
would
like
to
to
get
a
tutorial
on
it
and
see
how
how
it
works
check
out
our
new
video
that
is
available
on
aurora's
own
youtube,
channel,
actually
yeah
and
try
out
the
testnet
rainbow
bridge
deployment
and
how
it
auto
finalizes
transforms
from
ethereum
to
near
right
now
so
super
cool
stuff
and
in
case
you're,
a
developer.
A
You
you
are
able
to
try
out
the
full
full
bridge,
full
bridging
abilities
on
the
testnet.
So
now
you
are
able
to
transfer
funds
in
between
all
of
the
runtimes
that
we
have
ethereum
near
and
aurora
is
pretty
simple,
though.
Obviously
you
need
to
you
need
to
use
your
cli
or
any
other
tool
that
you're,
using
normally
using
for
scheduling
transactions
in
near
end
ethereum.
A
So
with
that,
I'm
concluding
this
call
thanks
for
no,
no,
no,
I'm
not
concluding
it.
Let's
figure
out
whether
we
have
any
comments
on.
C
We
have
more
and
more
people
watching
every
week.
A
A
Okay,
so
I
see
yeah,
I
see
here
in
joining
us,
so
it
seems
like.
Maybe
this
is
my
friend
ilya.
If
it
is
you
hello
to
you,
nice,
seeing
you
here
long
time,
no
see
okay,
how
near
holders
participate
in
aurora
token
sale
and
governance.
There
is
no
aurora
token
right
now,
whether
the
token
is
going
to
be
created
or
not.
This
is
a
decision
that
is
going
to
be
made
by
the
aurora
dao.