►
From YouTube: Aurora Update [2021-05-28]
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
seems
like
we
are
live.
We
are
here
on
the
weekly
update
from
the
aurora
team
and
happy
to
have
all
you
here.
We
have,
as
always,
some
some
news
for
you,
as
you
know,
aurora
ships
every
week
where
we
are
deploying
something
to
the
to
the
community
and
showing
some
some
new
functionality,
and
we
are
pleased
to
announce
that
this
week
we
have
a
set
of
updates
that
are
available
for
you
right
here
right
now.
A
Moreover,
our
partners,
sushi,
swap
and
dodo,
has
launched
two
liquidity
pools
on
their
amm.
Solutions
that
are
together
are
worth
of
one
million
in
liquidity,
and
this
is
this
is
one
of
the
major
updates,
and
I
want
to
thank
all
of
the
team
who
was
who
was
preparing
this
and
releasing
this
in
a
pretty
short
time
frame.
A
Besides
that,
we
also
have
some
additional
things
for
you.
So,
first
of
all,
yeah
and
just
one
step
back
story.
You
are
able
to
see
the
transfers
of
near
token
in
the
ethereum
dot
bridgestoneyour.org
this.
This
is
our
usual
front
end
for
the
rainbow
bridge,
you're
able
to
create
new
transfer
and,
in
the
token
list
you
are
able
to
check.
You
are
able
to
see
near
as
a
token
for
the
transfers.
A
So
how
cool
is
that
you
can
just
transfer
near
to
ethereum
now?
The
second
thing
is
we
are
launching
is
this
is
for
for
the
developers
that
want
they
want
to
explore
more
of
aurora
and
want
to
integrate
more
many
people
have
been
requesting
this
and
we
are
launching
the
limited.
A
A
The
transfer
bank
is
going
to
be
disabled
for
now,
but
later
it
is
going
to
be,
the
connector
is
going
to
be
updated
and
enabled
so
you
will
be
able
to
get
back.
Your
robson
east
that
you
have
not
spent
for
the
transfers
and
third,
and
also
the
thing
that
was
heavily
requested
by
our
community
is
some.
This
is
these
are
the
tutorials
that
people
can
use
in
order
to
develop
something
on
aurora,
I
invite
you
to
visit
docs
doctor
tororo
the
dev.
He
said
this
is
the
website
for
our
documentation.
A
Again,
I'm
just
reminding
everybody.
Since
the
project
is
in
a
very,
very
early
stage.
I
advise
it
to
go
often
to
change
lock
and
see
what
are
the
things
that
are
changing
here.
So,
for
example,
this
week
we
have
changed
the
end
points,
and
please
be
please
please,
please
be
attentive
to
this.
A
A
A
So
now,
coming
back
to
our
weekly
updates,
let's
go
on
and
let's
see
what
is
happening
and
what
are
the
updates
of
the
team
members
ahmet?
B
Yeah,
so
mainly
from
my
site
this
week
I
was
working
with
r2
to
debug
and
to
troubleshoot
some
some
rpc
issues
and,
as
you
mentioned,
that
we
have
this
and
then
change
log,
the
8th
coal
issue
and
also
troubleshooting
the
remix
with
metamask
issue
and
working
on
the
truffle
truffle
tutorial
and
also
we're
gonna
have
the
hard
hat
very
soon.
But
it's
still
like
I
have
it.
Okay,
I
didn't
push
this
so
hopefully
by
first
of
the
next
week,
we're
gonna
have
another
tutorial
for
the
hard
hat.
A
Okay,
that's
cool,
that's
cool
short
update
from
my
side,
I'm
working
heavily
on
investor
rounds,
having
usually
around
10
meetings
a
day
with
different
investors.
We
have
really
big
interest
investing
in
in
in
this
round.
In
aurora
I
was
hoping
it's
a
bit
too
much
with
the
in-ear
launch
management.
In-Ear
is
an
internal
eternal
name
for
this
project
that
we
have
launched
today.
I
was
doing
a
little
bit
of
a
bridge
support
for
some
users.
A
That's
the
major
act.
It's
oh
yeah!
One
thing
I
completely
forgot
hiring
of
a
senior
engineer,
aurora
position.
I
believe
we
have
some
prominent
candidates
there.
So
hopefully
we
can
fill
this
pretty
soon
yeah!
That's
that's!
That's
it
from
my
side
arthur
what
about.
C
You
another
busy
week,
mostly,
I
supported
partners,
troubleshooting
issues
with
the
help
of
ahmed
in
particular,
and
we
we've
done
a
lot
of
work
on
the
aurora
layer
to
make
it
easy
to
use.
So
it's
truly
a
turnkey
solution.
Now
you
can
just
do
a
docker,
pull
and-
and
you
can
run
run
that
thing
with
docker
compose
and
it'll
it'll.
C
Just
look
so
that's
great
and
the
there
are,
I
believe
at
least
two
partners
who
are
already
using
the
relay
themselves
in
local
deployments
and
the
relay
deployments
on
that
we
host
in
the
cloud.
C
Those
have
also
been
upgraded
to
use
the
new
docker
deployments,
which
makes
it
a
lot
easier
to
manage.
I
I
put
in
place
a
standalone
proxy
for
the
legacy
endpoints.
So
these
are
the
rpc.testnet
auto,
because
we
will
of
course,
continue
to
support
those
endpoints,
but
people
should
migrate
to
the
new
ones
and
by
having
them
in
a
standalone
proxy.
C
They
incur
a
little
bit
of
a
latency
penalty,
so
there's
an
incentive
to
to
migrate
and
they
are
easier
to
manage
and
and
don't
screw
up
the
rest
of
our
infrastructure
and
a
lot
of
work
on
preparing
new
new
servers
all
around
the
world
for
the
coming
edge,
endpoint
launch,
which
is
coming
very
very
soon,
and
the
initial
results
are
very,
very
promising
on
how
low
over
latency
we
can.
We
can
enable
for
for
users
all
around
the
world
so
more
on
that
next
week.
C
Also,
I
I
did
a
survey
of
all
of
the
open
source
block
explorers,
a
comprehensive
survey,
so
the
there's
a
lot
of
projects
actually,
but
the
most
important
ones
are
for
so
that's
block
scout
ethereum,
light
explorer,
svm
and
expedition,
and
it's
not
a
hugely
great
situation.
With
the
open
source
block
explorers.
C
I
wouldn't
say
that
any
of
them
are
really
satisfactory
compared
to
you
know
what
we
are
used
to
for
etherscan
as
a
standard,
but
block
scout
is
clearly
the
the
best
one,
as
in
most
most
usable
best,
best
best
ux,
most
indexed
data
fastest
and
and
actually
looks
good
and
so
on.
So
we're
going
to
deploy
block
scout,
but
it's
fairly
complex
operationally
compared
to
some
of
the
others
that
don't
even
do
any
indexing,
don't
have
a
database.
C
So
that's
going
to
be
next
week
as
in
in
the
next
days
we
will.
We
will
deploy
brook
scott
and
make
it
available
to
everybody
and
yeah
there's
a
long
tail
of
other
projects,
but
none
of
them
are
particularly
interesting
for
any
number
of
reasons,
including
including
crazy
licensing
and
in
some
cases,
missing,
missing
bits
of
source
code
and
and
so
on.
A
Great
super
cool
eugenie.
D
I
was
working
a
bit
on
host
functions,
so
this
work
is
still
ongoing,
so
probably
not
going
to
submit
this
request.
A
Okay
copy
that
again,
you
have.
D
So
it
was
a
lot
of
knowledge
of
pull
requests
and,
most
importantly,
it
was
implemented
additional
tests
for
proof.
So
for
that
time
I
think
probably
we
cover
all
possible
cases
for
s
connector
and
also
is
that
proofs
what
was
found
some
parts
related
to
integration
tests.
All
of
that
was
fixed,
and
additionally,
we
improved
functionality
for
integration,
tests
and
coverage
of
probably
all
things
and
and
that
time
that's
kind
of
completely
ready
for
release.
E
Well,
it's
going
good
a
ton
of
coding
this
week,
so
so
on
the
low
level
I
extended,
the
near
api
go
with
great
account,
so
I
could
completely
remove
the
near
cli
dependency
there,
but,
more
importantly,
like
the
bully
replay
has
a
new
setup
flag
which
basically
sets
up
all
the
state
like
sets
up
a
clean,
near
core
starts
in
the
edema
and
creates
accounts
deploys
the
contract.
Then
we
place
everything
and
then,
if
we
have
a
breakpoint
set,
so
that's
basically
the
state
we
want
to
save.
E
It
saves
all
of
that
up.
So
that
means
the
state
of
near
core
the
the
heads
of
the
near
core
repository
and
the
aurora
engine,
the
the
account
key
and
the
failing
transaction,
and
then
I
implemented
the
new
command,
which
is
the
replay
transaction
which
then
basically
takes
such
a
thought
up.
State
and
this
build
option.
Also
rebuilds
the
correct
neocore
version
we
build
aurora
engine
starts
near
daemon,
and
then
we
place
a
transaction
that
was
failing
so
basically
that
that
is
what
I
will
then
can
give
to
developers.
E
They
just
need
the
one
tar
file
which
contains
the
reproducible
state,
and
then
I
can
we
we
play
the
trailing
transaction
and
it
will
allow
to
allow
us
to
override
the
deployed
contract.
So
I
mean
it's
not
very
useful.
If
you
just
replay
the
failing
transaction
on
the
deployed
contract,
you
actually
want
to
change
the
contract
and
then
see
if
that
fixed
the
problem.
E
So
so
that's
basically
not
possible
and
well.
That
gives
the
first
program
to
death
next.
A
Okay,
that's
cool.
I
feel
that
that
that
the
bully
becomes
more
and
more
of
a
standalone
big
project.
We
can
sell
it.
Don't
you.
D
E
Yeah,
it
actually
turned
out
to
be
quite
a
lot
of
code
so
far,
yeah,
oh
right.
A
Okay,
I
thought
it
was
a
joke
and
it.
C
Looks
like
no
joshua,
he
did
mention
a
birthday
party.
A
Yeah,
okay,
so
then,
I'm
going
just
to
read
the
updates
from
joshua
joshua
have
spent
a
considerable
amount
of
time
getting
gas
costs
to
the
new
math.
Api
methods
had
calls
and
worked
in
collaborative
with
michael
okay
and
handed
off
the
work
to
capable
team
familiar
with
it.
A
C
Here
is
guess
that
means
that
the
contract
runtime
team
is
is
on
the
case
now:
oh
yeah,
okay,
that's
it
nicole,
nikolai
matt,
clad
and
paul.
A
C
Correct
correct,
insofar
as
the
actual
assigning
of
the
costs
to
the
functions,
yeah
depends
on
actually
getting
this
parents
runtime
estimator
to
work,
and
that's
that's
mostly
what
nikolai
is
helping
with
right.
So
right
so.
D
C
D
A
Okay
cool
so
then,
but
it's
a
bit
of
additional
tests
that
he
added
a
couple
of
full
requests
and
an
additional
request:
apple
requests
that
he
reviewed.
A
Okay,
kirill.
What's
on
your
site,.
F
So
this
week
I
worked
a
lot
on
pr's
on
creating
vrs
and
reviewing
and
merging
some
of
them
and
most
important
things
is.
I
spent
a
lot
of
time
working
on
the
implementation
of
carcass
for
level
connector
pro
compiles
and
also
started
working
on
integration
tests
to
verify
promise
differing
that
is
needed
for
pre-compiles,
also
updated
the
f
custodian
to
use
0.8
solidity
and
the
latest
trademark
breach,
which
required
some
patching
to
fix
the
hard
hard
terror
we
had
in
the
rainbow
bridge.
F
I
also
did
needed
my
they
needed
modifications
for
the
custodian
to
support
coverage
of
all
test
cases
in
our
engine,
for
the
integration
tests
and.
F
I
added
some
more
hardcard
examples
and
the
linkage
thing
was
this:
merge
the
developer
branch
into
that
connector
to
resolve
my
merge
conflicts
and
to
prepare
for
some
release
of
it
more
details
available
in
the
look
here.
G
Yeah,
it's
going
very
good
busy
working
half
time
here,
but
I've
been
doing
some
hiring
I've
been
doing
some
reviews.
G
I
fixed
the
issue
like
I,
I
found
a
workaround
to
fix
the
issue
with
testnet
kid
already
mentioned:
it's
not
working.
I
used
like
it's
working
right
now.
It
should
be
working
right
now,
I'll
get
offline.
The
theme,
if
it's
not
working
for
him,
so
yeah
pretty
much.
I
have
in
my
plate
the
finishing
the
pre-compiles
finish,
the
pre-compile
exit
for
for
it
connector
and
rc20
connector.
It's
very
close
to
be
finished.
I
just
need
to
allocate
some
time
to
it.
H
Recovering
yes,
this
crazy
week,
so
yes,
we've
been
doing
at
the
beginning
of
the
week,
the
e,
the
e-near
testing
and
then
iterating
with
pierre
on
that
and
then
the
rest
of
the
time
has
been
coordinating
the
junior
launch
today.
So
coordinating
liquidity
talking
to
some
partners
in
the
marketing
and
the
bridge
update.
A
Cool
cool
yeah.
I
just
wanted
to
say
that
that
matt's
developed,
if
you
go
to
out
to
aurora
dev
to
our
website
and
you
will
go
to
the
blog
blog
part
of
it
right
and
now
it
is
now.
This
is
the
the
place
we're
going
to
put
our
our
updates
nobody's
expected
every
week.
We're
going
to
put
something
here,
for
example,
the
availability
of
the
near
token
on
the
ethereum
that
we
announced
just
in
the
beginning
of
this
call
so
good
job.
I
Yeah,
I
did
some
work
on
the
docs,
including
writing
the
metamask
tutorial
doing
some
reviews
on
the
truffle
tutorial
also,
as
was
mentioned
earlier,
spent
a
fair
bit
of
time
with
joshua
working
on
runtime
stuff
and,
ultimately
not
actually
getting
anywhere.
So
we've,
given
that
back
to
the
contract,
runtime
team-
and
I
did
some
pr
reviews-
and
I
pushed
a
small
fix
to
an
issue
that
marcelo
had
pointed
out
a
couple
weeks
ago.
A
Okay-
okay,
that's
good
one!
I
just
want
to
thank
to
to
michael
and
to
ahmed
for
doing
good
job
on
the
on
the
docks.
I
know
that
tarta
was
also
taking
part
in
this.
So
again,
good
docs
is,
since
we
are
a
platform
we
are
not
a
product
or
like.
We
are
also
a
product,
but
we
are
more
of
a
platform
and
we
want
to
incentivize
people
to
build
on
top
of
us,
then.
Obviously,
this
is
a
super
super
important
piece
and
it
was
missing
until
this
week.
A
So
thank
you
all
for
for
your
work
here,
pierre
and
now
the
superman
of
the
of
the
in-ear
front-end.
D
J
J
I
fixed
a
couple
things
in
the
fine
replacement
transaction
package
which
I
was
suspecting
we
would
have
last
week,
and
so
I
fixed
them
so
now
it
should
work
fine
with
even
when
multi-sig
transactions
are
speeded
up,
which
is,
I
think,
not
the
case
for
argent.
J
I
didn't
see
a
speed
up
functionality
on
argent,
so
if
you're
using
argent,
maybe
watch
out
that
your
transaction
stays
pending
but
yeah,
so
that
should
work.
There
was
also
a
small
issue
on
the
near
wallet
redirect,
which
was
pretty
rare
and
luckily
matt
also
was
able
to
reproduce
it,
and
so
that
was
fixed
and
also
did
some
ui
improvements
that
might
suggested
like
recording
the
bridge
transfer
direction.
J
So
it's
not
to
confuse
users
doing
the
new
wallet
redirect
so
that
when
you
come
back
you're
still
on
the
same
page
and
same
bridge
setup
than
when
you
left,
there
were
some
issues
with
back
button,
navigation
and
small
things.
Like
this
and
finally,
I
also
made
the
metamask
pr
to
add
erc20
near
as
a
default
token
on
metamos,
so
that
users
can
see
it
right
away
without
having
to
add
it
manually.
J
A
Okay,
yeah
cool
cool,
okay,
so
super
cool.
I
believe
that
we
need
to
have
this
to
have
the
somewhere
in
our
docs
when
we're
going
to
update
it
with
the
information
about
the
bridge,
we
need
to
put
there
also
the
the
addresses
of
the
contracts
on
the
testnet
and
on
the
maintenance.
A
A
Cool
julian,
are
you
with
us
yeah
I'm
here?
Maybe
you
can
also
update
us
a
little
bit.
D
I
think
pretty
much
all
the
same.
Just
kind
of
helping
you
out
with
the
operational
side
spoke
trails
with
your
potential
partners
and
yeah
and
we'll
coordinate
with
met
a
little
bit
on
this
release
for
you
and
the
legal
structure
so
same
stuff,
ongoing.
A
Yeah,
okay,
so
good
good
less
than
head
out.
We
already
like
how
much
we
already
half
an
hour
in
in
in
the
updates.
Let's
go
now
to
discussions
and
let's
discuss
the
some
pieces
that
that
you've
put
here
in
the
agenda
so
in
your
launch,
who
was
who
was
putting
this?
What
should
we
discuss
here.
C
H
H
So
that's
that's
very
exciting,
and
then
we
also
made
an
initial
well.
We
would
really
like
for
near
to
be
quickly
a
productive
asset
in
the
defy
space,
and
so
we
made
contact
with
the
ruler
protocol
and
ruler
is
a
is
a
lending
protocol
on
ethereum.
H
That
has
a
unique
feature
that
stable
coins
borrowed
against
crypto
collateral
cannot
be
liquidated
and
that's
achieved
by
having
a
peer-to-peer
lending
model
where
lenders
contribute
to
a
liquidity
pool
and
the
state
of
the
liquidity
pool
sets
the
current
interest
rates
and
borrowers
then,
can
borrow
at
the
current
interest
rate
and
as
long
as
they
pay
the
the
loan
back
by
the
end
of
the
month,
then
they
get
their
collateral
back.
If
they
don't
pay
back,
then
they
forfeit
their
collateral
and
the
liquidity
providers
then
get
to
share
in
that
collateral.
H
So
it's
it's
an
interesting
model
and
they
have
agreed
that
for
next
month,
near
is
going
to
be
accepted
as
a
collateral
asset.
So
that
was
another
interesting
aspect
to
the
near
launch
and
and
yeah.
We
we,
we
announced
it
on
the
on
the
website,
which
we
enhanced
to
be
able
to
separate
our
our
content
among
categories
and
so
currently.
Currently
we
have
news
and
and
blog
there
we
can
also
add
a
category
for
these
team
updates
and
whatever
we
like.
A
Okay,
that's
cool,
that's
cool,
great
f
connector,
or
do
we
have
anything
else
to
discuss
in
the
in-ear
launch.
C
Okay,
so
for
the
s
connector
kirill
and
I
will
be
working
on
the
deployment
today
martial
if
you're
available.
I
would
pull
you
in
as
well.
C
Okay,
and
let's
see
do
we
need
anybody
else,
I
think
we
can
probably
manage
the
three
of
us
and
the
most
important
thing
that
will
be
enabled
after
we
deploy
this
today
we
will
be
able
to
roll
out
the
net
faucet,
which
people
rightly
keep
asking
for
it's
a
little
hard
to
test
contracts.
When
you
have
an
s
balance
of
zero,
sometimes
you
actually
want
to
test
something
that
moves
a
little
eth
around.
C
So
the
that
means
that
for
for
next
week,
we'll
certainly
need
to
make
a
simple
faucet
front
end.
So
take
note,
I
believe
you
you
were
on
that
desk
in
any
case,
but
now
it
will
be
actually
possible.
So
we
can.
We
can
move
a
bunch
of
s
robsterneth
over
into.
We
can
actually
do
a
traditional
faucet,
as
in
we
can.
C
We
can
just
have
a
faucet
account,
which
is
gonna,
distribute
earth
from
that,
and
we
can
fund
that
faucet
by
transferring
ourselves
a
bunch
of
rocks
to
nest
over
so.
A
C
C
Well
that
that's
a
that's
a
secondary
problem
right,
you
know,
I
I
have
a
little
bit,
I'm
not
a
rockstar.
C
Yeah,
oh
yeah,
yeah,
that's
good,
all
right!
So
so,
let's
think
on
that
on
how
much
we
can
make
available
and
what
kind
of
limits
you
need
to
put
on
the
faucets,
but
in
any
case,
for
anybody
to
have
a
non-zero
balance,
even
if
it's
a
small
balance
that
already
helps
them
out
a
lot,
absolutely
yeah.
So
for
the
for
the
connector,
then
we've
been
so
far.
C
The
connector
has
been
deployed
on
developed
at
aurora
on
on
the
testnet
and
that's
what
kiril
and
others
have
been
using
for
for
testing
and
now
so
to
be
clear
from
from
the
deployment
today,
it
will
be
available
on
the
aurora
accounts.
I
think,
and
the
exit
will
not
be
available
this
week,
but
I
said
mostly
it's
about
enabling
the
default,
so
that's,
okay
and
and
for
the
if
somebody
wanted
to
use
the
faucet.
Sorry,
the
connector
themselves.
C
But
I
think
really,
I
think
99
percent
of
people
are
just
going
to
want
to
force
it.
So
that's!
That's!
Fine,
mostly
mostly,
we
will
be
the
users
of
the
of
the
connector
at
this
point
anything
else
to
add
to
curiel
to
that.
F
No,
I
think
here,
yes,
which
was
quite
exhaustive
in
this
case,
so
I
I
think
it
it
could
be
fine,
and,
as
marcella
mentioned,
that
the
athena
client
is
fixed,
we
should
be
fine
with
it
and
to
have
some
time
to
test
it
on
the
test.
C
Yeah
and-
and
I
suppose
the
other
thing
to
mention
is
that
what
I've
discussed
is
that
what
we'll
be
doing,
then,
is
you,
you
have
merged
the
developer
branch
into
the
s,
connector
branch
right.
C
Okay,
so
michael
is
reviewing
it
done.
Let's
see
if
joshua
will
have
a
chance
as
well
and
then
after
that,
what
we're
actually
going
to
do
is
is
the
reverse,
as
we
are
going
to.
You
know
that
that
sorts
out
all
the
merge
conflicts
then
we're
going
to
merge
the
s
connector
branch
into
develop
and
we
are
going
to
when
it's
ready
to
go
we're
going
to
merge,
develop
into
master
since
master
represents
what's
on
chain,
and
I
will
build
the
binary
on
my
build
server
and
I
will
deploy
it
to
desnet.
C
So,
let's,
let's
sync
up
marcelancero
after
after
this
call,
but
I
have
another
one
now
call
after
this.
So
I
will
I
will
book
you.
I
have
to
book
you
guys
after.
C
I
suppose
the
last
thing
there
is
that,
are
there
any
other,
and
this
is
a
question
for
everybody.
Michael
also:
are
there
any
other
pending
vrs
on
the
engine
that
should
be
landed
to
develop
for
the
deployment
today
and.
C
Okay
and
remember
guys,
you
need
to
actively
hound
people
that
you
need
reviews
from.
If
something
is
you
know
not
moving
hound
people
github
notifications
are
the
spammiest
and
noisiest
of
all
notifications.
I
have
I'm
not
going
to
see
anything
that
I
need
to
review
unless
you
send
me
a
link
specifically
that
you
need
me
to
review
it.
So
just
keep
that
in
mind
so
which
which
pr,
michael.
I
I
can
get
some
links
here,
so
the
the
one
pr
is,
the
state
migration
pr.
We
may
actually
need
this
to
do
the
eth
connector,
I'm
not
a
hundred
percent
sure,
but
we
should
maybe.
I
Sorry,
let's
see
number
103,
103,
okay
and
then
the
other
one
I
opened
yesterday
was
the
precompiles
dispatch
right.
Marcelo
pointed
out
that
yeah
that's.
F
C
I
thought
you
had
already
done
that,
but
yeah,
if
you
haven't
had
them,
let's
do
no.
I
haven't.
I
will
please
please
send
a
pr
for
that.
Okay,.
C
C
Yeah,
and,
and
also
okay,
when
you're
doing
the
feature
flap
you
you
could
also
think
about
from
now
on
the
if
connector,
since
it's
gonna
be
on
master,
it
should
just
be
enabled
by
default.
It
doesn't
have
to
be
behind
a
feature
flag,
so
it
could
be
possible
to
take
off
the
feature
flag
there.
It
doesn't
have
to
be
today,
that's
not
important,
but
we
don't.
C
No,
I
meant
the
the
whole
f
connector
if
there
was
any
feature
flag
involved
with
that.
We
don't
need
to
keep
it
any
longer.
Oh.
D
C
C
Okay
yeah
for
the
math
api.
If
joshua
were
here,
I
would
have
asked
him
to
update
us
on
the
deliberations
with
nikolai
at
all,
but
we
can
come
back
to
that
next
week.
In
any
case,
bowen
is
aware
of
all
developments
and
and
wants
to
see
it
merged
soonest.
C
So
it's
moving,
but
it
does
pretty
much
need
to
get
merchant
in
the
next
week
in
order
to
hit
the
yeah.
Actually
it
should
get
immersed
in
the
next
days,
preferably
otherwise
it's
going
to
be
not
a.
D
A
Okay:
okay:
let's
discuss
a
little
bit
the
plans
over
the
next
week.
If
we
don't
have
anything
more
for
the
discussion
section
of
the
call.
C
Nothing
nothing
from
me,
mostly
internal
matters.
We
can
deal
with
one
decal,
all
right.
A
Okay,
okay,
cool
yeah,
then
let's
go
over
the
plans
for
the
next
week.
Ahmed.
B
Yeah
so
mainly
for
the
next
week,
I'm
gonna
focus
on
the
hard
hat
and
the
sample
dab
as
a
use
case,
and
also
I'm
gonna
work
on
the
rainbow
page
for
the
solidity
part.
So
so
far
the
solidity
code
is
missing
some
documentation.
So
we
need
to
finish
up
this
part
and
also
troubleshooting.
The
meter
mask
confirmation
notification
with
our
pcie
layer.
B
So
if
you
can
see
when
you,
when
you
invoke
a
transaction
through
the
metamask,
it
didn't
show
up
any
confirmation
if
this,
like
transaction,
was
failed
or
successful.
So
I
need
to
investigate
this
one
as
well.
Yeah.
C
Okay,
actually,
actually
one
one
quick
backtrack.
There's
one
more
item
for
discussion
that
I
should
just
mention
as
an
announcement,
so
the
aurora
team
will
be
attending
the
fcc
conference
in
in
paris
in
july.
C
Maybe
you
can
show
the
site,
that's
cc.io,
I
believe
yeah,
and
we
have
so
so
far
six
hard
commitments
from
members
of
the
team
to
to
be
there,
including,
including
myself
and
alex,
and
if,
if
anybody
else
from
the
team
would
like
to
join
us,
hit
me
up
after
the
after
the
call
and
we'll
get
tickets
for
you.
C
And
we
do
plan
to
submit
a
workshop
proposal
as
well
still
this
week.
C
So
they'll
be.
The
conference
is
only
a
couple
days,
but
I
think
it
might
be
sensible
to
stay
stay
a
few
more
days,
so
it
will
be
a
full
work
week
of
team
building
as
well,
which
I
think
everybody
is
a
little
bit
desperate
for
after
covered
year.
C
So
those
who
can
be
there
consider
consider
being
there
and
talk
to
me
afterwards.
A
Cool
my
plans
for
the
next
week
are
unchanged.
We
have
more
more
time
for
to
to
discuss
with
the
investors
in
restaurants.
However,
soon
this
is
going
to
wrap
up.
We
have
like,
according
to
our
plan,
we
have
like
one
and
a
half
week
or
something
like
that
for
for
the
restaurant
and
then
we're
going
to
to
wrap
it
up.
As
I
said,
we
are
doing
very,
very
good
job
there.
So
no
problem
in
in
you
know
in
in
finding
the
investors
that
are
interested
in
this.
A
We
just
need
to
talk
to
everybody
and
to
give
everybody
the
opportunity
to
take
part
in
this
and
yeah.
There
are
slowly
but
surely
partners
I'll
be
coming
to
to
build
the
integrations
with
aurora
and
also
they
starting
to
to
develop
some
applications
and
with
all
of
these
people,
I
also
need
to
need
to
speak,
need
to
figure
out
what
are
going
to
be
the
terms
of
the
partnerships
and
and
so
on,
yeah
and
probably
probably
working
on
the
legal
setup.
A
So
we
still
need
to.
We
we've
made
a
decision
how
we
are
going
to
structure
the
company.
So
this
is
a
good
thing
now
we
need
to
need
just
to
execute
this,
and
I
believe
there
will
be
lots
of
lots
of
the
tasks
within
this
project.
A
I'm
also
going
to
continue
hiring
activities
again.
I'm
I'm
now
focusing
on
the
senior
engineer
for
aurora
in
on
this
role,
but
most
probably
we
need
to
accelerate
on
the
marketing
and
business
development
sides
too,
and.
D
C
A
Okay,
so
let
me
let
me
put
it
then:
here
devops
and
marketing.
A
C
Yeah,
I'm
going
to
roll
out
the
edge
infrastructure,
so
massively
lowering
endpoint
latencies
for
all
users,
making
a
much
better
developer
experience
and
we're
going
to
roll
out
vlog
scout
as
mentioned.
C
In
addition,
of
course,
there's
going
to
be
a
ton
of
ongoing
things
on
the
ethernet
s820
connectors,
supporting
that
and
and
then
there's
a
lot
of
technical
support
to
partners
and
documentation.
Pretty
pretty.
D
D
A
E
Yeah,
I
want
to
add
a
small
small
extension
to
determine
breakpoints
automatically
so
right
now.
I
basically
have
to
run
it
see
where
it
fails
and
then
set
it
manually,
and
it
would
be
nice
to
just
attach
it
automatically
and
then
you
know,
get
the
feedback
for
for
the
new
replay
transaction
command
and
see
if
it's
actually
helpful
for
fixing
the
problems.
D
A
That's
cool.
It
will
be
really
really
nice
to
well.
If,
if
there
will
be
room
for
you
within
the
next
week,
it
will
be
really
nice
to
understand
what
is
the?
What
is
the
place
where,
where
we
are
breaking
and
how
this
thing
is,
how
the
how
the
height
of
of
the
blockchains
is
updating
over
time
so
with
with
our
new
releases
one
once
we
are
fixing
these
problems.
A
E
Yeah,
I'm
gonna
like
add
a
bit
of
documentation
how
to
use
it
and
then,
basically,
just
like
file
bug
reports
for
the
three
chains.
D
E
A
Okay:
okay,
nice
arter!
Do
you
have
in
mind
what
you
are
going
to
to
ask
joshua
to
work
on
next
week.
C
Sure
so,
of
course,
we
gotta
wrap
up
this
math
api,
it's
literally
the
last
week
for
being
able
to
get
anything
into
the
june
release,
so
whatever
needs
to
be
done
and
on
that
is
the
top
priority.
After
that,
there's
a
number
of
pending
pending
matters,
most
important
is
likely
the
self-destruct
question.
C
A
Week,
okay,
cool
cool
carriel.
F
So
I
will
continue
working
on
project
tests
for
become
files
and
on
integration
tests
for
promise
different,
which
is
really
important
to
have
it
on
the
next
week
and
as
soon
as
possible.
I
will
also
continue
reviewing
everything
coming
to
our
engine
and
probably
working
on
any
urgent
things
that
might
might
happen
on
the
next
week.
G
H
Yeah
so
for
monday,
we'll
try
to
have
out
the
testnet
e
transfer.
Ui
that'll
appear
as
a
separate
website,
possibly
the
main
neti
transfer
ui.
If
that,
if
that
becomes
possible
during
next
week,
I'm
going
to
review
the
e-near
situation
and
follow
up
with
the
partners
and
then
finally
continue
a
bit
with
the
base
camp
organization
and
I'm
trying
to
get
us
going
more.
There.
D
A
Cool
mike,
what
are
your
plans.
A
A
Right:
okay,
pierre.
J
Yeah,
I
think
working
on
east
transfers
to
aurora,
and
I
think
we
can
also
add
the
ethereum
to
near
transfer
finalization
check
like
we
were
talking
earlier,
which
remains
to
be
determined
whether
we
have
to
use
an
indexer
on
near
or
to
have
a
view
function
on
the
factory
contract.
A
Okay,
cool
cool
you're
done.
D
Sorry
I
lost
my
tub,
so
I
mean
my
plan
is
just
to
continue
supporting
you,
so
we
can
yeah
figure
out
the
fundraising
situation,
keep
pushing
legal
city,
legal
stuff
and
yeah.
That's
pretty
much
it
and
continue
like
marketing
support,
see
what
we
can,
what
we
can
do
there:
okay,
cool
cool
super
nice.
A
Super
nice,
any
additional
things
that
that
be
discussed
or
to
update
our
people
who
are
watching
this
show.
A
Okay,
so
I'm
just
I'm
going
to
to
take
this
on
me.
Aurora
token
is
not
there
yeah.
So
if
you
anywhere
see
the
information
about
the
aurora
talking
there
about
raw
talk
on
sale,
this
is
incorrect
information.
Most
probably,
this
is
a
scam,
that's
that
is
specifically
for
you
to
spend
your
money
actually
there.
What
do
you
mean
alex
by.
A
Yeah
well,
there
was
some
kind
of
we
have
found
some
kind
of
aurora
tokens
from
the
projects
that
that
have
been
there
later
yeah.
So
so
these
are.
This
might
be
alleged
tokens
for
that
projects,
but
for
our
projects
for
our
aura,
there
is
no
talking
right.
A
So
all
of
the
information
that
you
about
aurora
token
that
you
can
see
in
the
internet.
This
is
incorrect
information.
There
is
no
token
again
and
there
is
no
clear
understanding
whether
this
token
is
going
to
be
implemented
and-
and
if
is
then,
then
it's
going
to
be
there.
Our
approach
for
the
aurora
project
is
to
gather
a
dao.
A
We
would
like
to
would
like
to
help
people
to
organize
a
dao,
and
then
this
dao,
the
inception
of
the
token,
may
be
one
of
the
questions
that
this
dao
is
going
to
discuss
so
right
now
there
is
no
again
just
repeating
for
everybody
right
now.
There
is
no
talking.
Please
do
not
become
a
victim
of
the
scammers.
A
Right,
okay,
so
it
seems
like
that's.
That's!
That's
a
nice
point
to
end
up
this.
This
week's
update.
We
are
right
at
one
hour,
even
a
little
bit
less
since
we,
since
we
started
a
bit
after
so
thanks
for
being
with
us,
see
you
next
week
with
the
next
round
of
of
aurora
updates
number.
If
we
can
prepare
something
interesting
for
you
for
the
next
week,
see
you
guys
have
a
nice
weekend
too.