►
From YouTube: Aurora Update [2021-06-04]
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
good,
hello,
everybody,
it
seems
like
we
are
live
hello.
Everybody
welcome
to
aurora's
weekly
updates,
aka
alpha
league,
we're
happy
to
to
have
you
with
us
today.
We
would
like
to
discuss
some
some
news
of
the
aurora
project
with
you
share
some
insights
and
some
things
that
we
are
currently
working
on.
A
I'd
like
to
start
with
the
status
and
the
current
goal,
and
actually
to
show
you
some
some
cool
new
features
that
we
have
so.
First
of
all,
we've
launched
a
faucet
and
the
front
end
for
the
f
bridging
on
the
testnet,
and
it
looks
like
this.
If
you
will
go
to
the
aurora
website,
you
will
go
to
the
resources
page.
A
You
will
see
here
that
there
is
a
link
to
the
testnet
bridge.
This
is
the
thing
that
you
need
to
that.
You
need
to
click,
and
I
already
connected
my
robson
testnet
wallet.
As
you
can
see,
I've
got
a
bunch
of
f
there,
so
I
can
try
to
transfer
to
transfer
a
little
bit
of
f
from
robsten
to
aurora,
I'm
continuing
with
this
transfer.
A
Okay,
my
metamask
pops
up
says
that
I
need
to
confirm
the
transaction
and
the
transaction
went
in
the
in
the
network.
So
probably
right
so
right
now
the
transaction
is
going
to
be
confirmed
by
the
robson
network.
As
you
can
see,
it
is
there
already
and
now
we
need
to
wait
a
little
bit
for
the
confirmations
of
several
confirmations
in
robson
network
and
these
confirmations
need
to
be
also
sent
to
near.
A
Well
we're
going
to
come
back
into
this
for
a
while,
but
please
expect
that
this
step
is
going
to
take
around
in
general
around
10
minutes,
maybe
20
minutes
or
something
like
that.
So
not
a
long
step
and
it's
going
to
go
it's
going
to
be
done
automatically.
A
So
I'm
just
going
to
my
transfers
just
seen.
Well
what
is
happening
here
and
I'm
going
to
switch
to
it
to
another
to
another
pieces
here.
Also
in
the
raw
test
net,
you
are
able
to
go
to
the
resources,
also
documentation
maintenance
bridge,
and
you
also
are
able
to
get
some.
If
tokens,
how
cool
is
that
you
are
able
to
get
it
on
the
robstone
from
the
metamask
faucet
and
you
are
able
to
get
it
from
the
aurora
faucet?
A
So
if
I
click
aurora
faucet,
it's
just
a
simple
metamask
faucet
too.
Here
right
now
we're
going
to
update
it.
It's
going
to
be
built
into
our
website.
It's
going
to
look
really
nice,
but
for
now
you
are
able
to
claim
a
robston
eath,
so
testnet
aurora
eth
directly
from
this
faucet.
A
So
how
cool
is
that
coming
back
to
our
updates?
I
want
also
to
say
that
a
little
bit
later
this
week
we
are
going
to
launch
the
block
explorer
for
aurora
and
also
one
smaller
update.
We've
announced
a
partnership
with
injective
protocol
during
this
week,
so,
together
with
injective
team,
we're
going
to
well
injective
team
is
going
to
include
aurora
into
the
list
of
supported
networks.
They
are
going
to
help
bridging
stuff
with
other
solutions
that
are
using
evm
chain.
A
So
that
was
the
update
for
today
and
let's
go
on
for
the
personal
updates
for
this
week,
as
always
in
the
alphabetical
order.
B
Yeah,
so,
first
of
all,
so
mainly
this
week,
I'm
throttled
shooting
lots
of
rpc
calls
and
we
fixed
some
of
these,
so
we
almost
fixed
two
rpcs
calls
and
one
of
them.
Actually
we
was,
we
were
shooting
some
stuff
related
to
sushi
swap
and
the
metamask
as
well
and
lots
of
documentation.
B
So
so
far
we
have
this
hard
hat
example.
Gonna
be
released,
maybe
this
week
or
like
hopefully
by
monday,
because
also
we
are
relying
on
the
some
blocked.
It's
blocked
by
some
some
minor
issues
in
the
rbc,
so
yeah.
So
hopefully,
next
monday
we're
going
to
have
the
hard
hat
on
available
on
our
documentation
capacity.
A
Okay,
that's
cool!
That's
cool
update
from
myself.
Quite
a
lot
of
investing
partner
calls
this
week
again
these
this
thing
continues.
A
We
were
finalizing
the
legal
setup
work
and
we
were
marching
towards
the
the
company
incorporation,
so
this
process
already
started
so
the
setup
we
already
understand.
What
is
the
setup
and
we
are
just
executing
it.
I
was
taking
part
in
in
couple
of
events.
First
one
was
the
unblocked
podcast.
We
were
speaking
there
with
guys
from
s
o
b
s
about
polterror
in
general
and
near
and
also
it
was
the
russian
language
binance
or
ama,
with
around
5k
views,
so
quite
important,
just
an
event.
A
Lots
of
comments,
lots
of
funny
stuff
generated
from
it
yeah
and
also
was
focusing
on
hiring,
because
I
understand
that
that
you're
under
some
it's
a
massive
load.
So
let's,
let's
find
additional
people
and
help
that
that
are
going
to
come
and
help
to
us.
That's
my
update.
C
Arthur
yeah,
on
my
part
mostly
this
week,
I
supported
a
lot
of
others
in
their
work.
I
also
did
a
little
bit
of
interviewing
interviewed
a
business
candidate
and
another
technical
candidate.
More
on
on
those.
Next
week
I
stood
up
the
test
net
faucet.
So
thanks
pierre
for
the
good
tip
about
the
software
we
could
use.
So
it's
it's
not
super
super
pretty
right
now,
but
it
does
work
and
people
will
be
able
to
get
their
test
net
f
there
right
now.
We
have.
C
We
have
only
a
little
bit
of
if
there
I
see
that
the
balance
is
shrinking
as
people
are
claiming
something,
but
I'm
going
to
talk
to
the
ethereum
foundation
folks
over
the
weekend
to
get
us
a
a
larger
amount
of
robson
f
to
bridge
over,
and
I
I
worked
on
deploying
the
the
block
explorer
but
given,
given
that
I
was
pulled
in
so
many
other
directions.
I
I
wasn't
able
to
deploy
that
prior
to
this
call
I'll
continue
on
that
tonight
and
yeah.
C
We,
as
ahmed
mentioned,
we
fixed,
troubleshooted
and
fixed
a
ton
of
issues
with
various,
obviously
calls
I
think
by
next
week.
We
are
most
likely
going
to
have
a
situation
where
everybody
getting
started
is
going
to
have
a
pretty
smooth
experience
also
also
because
of
you
know,
being
able
to
actually
have
definite
death
easily
and
so
on,
and
also
I
I
organized
everything
about
scc,
the
conference
in
in
july,
the
most
important
conference
in
europe.
C
This
year
we
are
going
to
with
a
large
team.
Eight
eight
tickets
currently,
and
we
have
submitted
two
talk
proposals
and
may
submit
a
workshop
proposal
as
well,
and
I've
already
got
my
tickets.
I
assume
most
team
members
have
theirs
and
we
have
accommodation
and
a
plan
plan
for
the
week.
A
Great
great
actually
want
to
publicly
thank
you,
art
and
and
ahmed
for
supporting
guys
from
lolliswap,
mainly,
I
believe
they.
They
should
be
pretty
happy
with
how
we
are
doing
this.
That's
that's
super
important
for
early
developers.
A
Okay,
prior
to
transitioning,
to
evgeny
kapoon,
I
need
to
tell
everybody
yeah,
since
you
can
input
you
put
it
here.
So
eugenie
is
going
to
transition
to
near
core
team
he's
not
going
to
to
live
near
with
us
starting
next
month.
So
in
months
from
now,
evekin
is
going
to
be
working
there.
A
Obviously
we
will
have
the
connection
too,
and
I
already
discussed
with
bowen
that
we
will
be
able
to
ask
evgeny
to
review
some
of
our
code
and
help
with
some
of
our
architecture
discussions,
but
in
general
eugene
is
going
to
to
live
there.
D
B
B
From
previous
week,
kirill
abramov
found
a
bug
related
to
parson
json.
I
created
a
pr
and
fixed
that
bug
covered
with
additional
tests
for
the
json
parser,
an
additional
test
for
empty
values.
So
from
arguments
also,
it
was
a
big
investigation
of
was
putting
down
version
2
and
I
tested
cli
and
ui,
and
we
should
discuss
it
more
in
our
discussion
section.
B
Yeah,
I
documented
how
to
replay
failing
transactions
from
a
directory's
order
data.
I
also
added
the
contract
option
I
mentioned
last
week,
so
you
can
actually
update
the
contract
before
replaying.
If
I
definitely
transaction,
but
you
need
to
yeah
properly
fix
something
also
edit
some
auto
break
option.
Up
to
now
it
was
always
manual.
You
had
to
run
it
once
and
find
where
the
block
breaks
and
then
set
this
manually.
B
So
I
made
that
automatic,
so
you
can
get
yeah
to
a
failing
transaction
without
any
manual
intervention,
then
the
evm
bully
build
broke
on
a
raw
engine.
So
I
added
that
to
the
ci.
So
that
doesn't
happen
again
and
then
I
package
up
all
the
three,
the
three
failing
tests
for
the
three
test:
nets:
ticketed
them
out
for
josh,
who
just
got
started
on
that
and
we'll
be
working
on
that
together
to
fix
those
issues
and
then
get
you
the
numbers.
You
always
ask
for
updated
every
week.
B
A
B
Super
cool
the
last
one,
unfortunately,
is
yeah
non-deterministic
failure.
So
that's
gonna
be
interesting.
Why
that
sometimes
fails
and
sometimes
doesn't?
Oh.
A
B
Yeah
it's
at
the
beginning
of
the
week
I
focused
on
the
math
api
because
we
got
to
get
that
out
asap,
so
I
worked
with
bowen
a
bit
to
make
sure
that
that
he
was
happy
with
it
and
then,
after
that
I
started
working
on
berlin
support
because
we
had
to
get
that
going.
So
I
got
the
costs
in.
I
also
changed
a
bit
of
the
structure
and
then
I
started
looking
into
frank's.
A
B
Which
which
he
already
touched
dutch
base
on
and
then
yeah,
I
guess,
that's
the
main
ones.
B
F
Yeah
so,
since
last
call,
I
worked
a
lot
with
aurora
engine
created
and
reviewed
several
prs
there,
and
also
I
was
doing
like
several
things
like
preparing
all
new
things
for
the
earth,
near
ventral
layer
to
be
released,
and
I
was
made
it
with
marcella
and
currently
it's
released
for
the
rainbow
token
connector
on
the
testnet
it's
deployed
and
it's
live.
We
will
shortly
update
it
for
the
main
net.
F
Probably
at
the
beginning
of
the
next
week
also,
I
discovered
and
fixed
some
storage
failure
ratio
when
upgrading
the
aurora
engine
contract,
but
no
worries.
It
was
only
on
the
develop
instance
and
the
test
net
and
main
network
instance
are
not
affected
by
this,
but
to
handle
this
in
future
and
to
easily
catch
it.
I
started
implementing
the
storage
regression
tests
also.
I
was
working
a
lot
on
testing
and
fixing
and
debugging
the
f
connector
exit
pre-compiles
and
also
spent
some
time
on
testing
promise
different.
F
Yeah
and
so
there
was
like
a
couple
of
tweaks
to
the
f
connector
with
scripts
and
guides
and
supported
some
members
of
the
team
on
helping
to
interact
with
it.
But
more
updates
yeah
are
in
the
are
in
the
comments.
G
Hi
then
good
here,
so
while
I
was
working
with
kirill
in
the
automatic
layer,
as
he
reported
like,
we
already
have
deployed
a
new
version
of
the
token
connector
that
allows
us
to
verify
proof
that
they're
used
there's
still
some
stuff.
That
needs
to
be
updated
on
the
front-end
side
to
allow
good
user
experience
for
users
that
are
actually
locking
up
are
making
transfer,
so
they
do
not
double
unlock
token
on
each
side.
G
So
this
needs
to
be
implemented
also
for
for
the
two
other
connectors
that
we
have
the
inner
connector
and
the
with
connector
it's
implemented
for
date
connector,
but
it's
not
deployed
yet
and
it's
to
be
added
to
the
to
the
front
end.
We
are
having
like
we're
discussing
this
now
with
with
pr2.
G
On
the
other
side,
I've
finished
the
rc20
connector
and
all
pre-compiled
to
exit
from
aurora
from
near
yeah
from
north
to
near
and
to
ethereum
it's
finally
working,
there's
still
some
small
things
that
are
that
are
not
are
not
finished
there.
One
is
that
jenny
kapoor
pointed
out
that
we
don't
want
to
allow
calling
this
pre-compiled
from
a
static
function
from
a
static
call.
G
I
try
to
using
that
that
value,
but
it's
it's
not
working
as
I
expected.
So
I
need
to
check
if
I'm
doing
something
wrong
myself
or
or
if
there
is
any
issue
with
the
evm
either
the
way
we
are
implementing
the
way,
we're
calling
it
or
the
vm
itself,
but
yeah
it.
It
is
mostly
done
and
it
works.
It
should
be
merged
soon
and
basically,
I
mean
like
in
the
beginning
of
the
next
week.
G
A
Yeah,
that's
cool
yeah,
just
one
want
also
to
thank
to
to
marcelo
and
to
joshua
to
help
me
with
hiring,
because
they
are
the
first
ones
to
whom
I
fire
out
all
of
the
candidates
that
are
passing
the
first
test
with
me
testing
to
first
interview
with
me,
so
yeah
thanks
for
doing
this
matt.
H
Very
good,
most
of
the
week
was
spent
with
a
test
net
bridge
ui,
collaborating
with
pierre
and
alex
and
coordinating
that
and
doing
testing
and
then
finally,
the
launch.
H
I
began
a
blog
article
about
how
the
bridge
works,
because
once
we
finally
got
the
ui
there,
I
had
a
chat
with
pierre
to
like
really
deeply
understand,
what's
happening
in
the
bridge,
and
I
think
that's
interesting
for
people
to
know,
and
there
was
a
medium
article
published
on
it
that
I
really
didn't
follow.
So
I'm
gonna
take
like
a
stab
at
making
a
a
really
clear
understanding
of
how
all
the
components
fit
together,
because
it's,
I
think,
that's
it's.
H
It's
unique
to
other
bridges
and
so
it'd
be
good
to
have
a
very
good
explainer
article
about
that
on
our
blog
and
then
I
began
the
dow
app
specification
and
the
first
approach
is
just
trying
to
scope
out
like
what
the
iterations
that
will
make
sense
are
so
the
first
iteration,
basically
just
showing
the
council
seats.
So
people
can
explore
who's
on
there
and
explaining
the
the
approach
that
the
concept
that
our
dow
will
have
and
what
what
the
implementation
is
and
then
kind
of
what
the
roadmap.
H
So
what
what
future
iterations
people
should
expect
to
find,
and
then
we
had
some
internal
and
partner
meetings
around
inner
liquidity
and
then
yeah
just
today
added
the
robson
aurora
faucets
to
the
test
net
resources
tab.
So
at
least
until
we
get
that
integrated
into
the
ui
next
week,
people
will
be
able
to
quickly
find
where
to
get
destiny.
A
H
Pierre
did
a
really
great
job
of
explaining
it
to
me
and
then,
like
two
hours
later
at
lunch,
I
tried
to
explain
it
to
my
son
and
I
think
I
went
from
like
80
percent
comprehension.
I
went
from
zero
to
eighty
percent
with
pierre
and
then
at
lunch
with
my
son.
I
realized
I
had
already
dropped
down
to
like
fifty
percent
comprehension
because,
like
some
you
know
so
the
best.
B
A
Cool
michael.
E
This
week
I
spent
a
fair
bit
of
time
on
documentation.
Most
of
those
pull
requests
are
sort
of
small,
but
the
last
one.
There
is
substantive.
We
have
some
new
screenshots
and
explanations
around
the
bridge
front
end
and
getting
eth
over
from
robson
into
into
the
test
net,
and
I
fixed
a
bug
around
handling
of
gas
limits
and
there
was
a
dependency
we
had
that
had
a
license
that
that
didn't
really
match
the
rest
of
the
the
code.
So
we
were
able
to
switch
that
out
for
for
something
else.
E
So
that's
a
little
bit
more
permissive
and
I
reviewed
few.
A
few
people
requests.
E
It
was
parsing
related
parsing,
the
argument
string
to
like
when
you,
when
you
have
you
know
these.
These
meta
calls
right,
you're
supposed
to
give
the
type
signature,
and
so
we
were
parsing
out
the
the
type
signature
using
lunarity,
which
is
sort
of
like
a
specialized
parsing
thing
for
specifically
solidity
types
and
solidity.
Syntax
and
logos
is
just
a
generic
parser,
but
it
was
pretty
easy
to
put
in
the
you
know.
G
Hey
so
I've
been
working
on
a
bunch
of
improvements
to
the
client
libraries
preparing
the
east.
B
A
Right
right,
cool
so
before
we
will
head
up
to
the
discussion.
So
first
of
all
I
will
ask
you:
maybe
you
can
bring
additional
topics
that
we
need
to
discuss
because
we're
here
we
have
hero
or
dao.
I
was
starting
to
put
here
slow
transfers,
but
I
need
to
actually
delete
it.
It's
not
that
that
big
issue
to
discuss.
A
Let's
check
what
is
the
so,
while
you're
thinking,
let's
check
what
is
happening
on
the
on
the
bridge
and
you
can
see
that
the
transfer
is
completed.
Actually,
so
you
are
able
to
to
see
what
is
happening
there.
Actually,
I
can
create
a
new
transfer,
okay
in
case
okay,
so
in
case
I'm
trying
to
to
change
the
the
direction
of
the
transfers,
what
it
what
it
tries-
and
this
is
a
fairly
new
feature
in
metamask
it.
A
It
asks
to
add
a
new
network
to
to
a
meta
mask,
so
you
can
improve
the
stuff,
I'm
switching
the
network
and
now
I'm
connected
to
aurora
test
net
and
look
here.
The
front
end
is
showing
that
I
have
1.01
f
already
there.
So
this
is
exactly
what
we
are
expecting
to
have
here.
A
Not
a
video
like
this
is
actually
the
first
time
when
I
use
it.
As
you
see,
I
added
the
network,
you
know
all
of
this
stuff,
okay,
cool
cool,
so
let's
go
to
to
discussing
aurora
dao
right.
What.
C
Are
the
points
that
we
have
here?
Yes
wanted
to
know
what
he
should
focus
on
in
the
investigation
of
sputnik,
and
I
I
told
him
that
we
would
intend
to
launch
the
aurora
dao
in
about
a
month's
time
and
that
doesn't
only
involve
the
contract.
It
also
involves
the
ui,
so
we
we
would
want
to
fork
the
ui
and
theme
it
to
be.
Our
specific,
of
course,
all
right.
So
anything
which
supports
the
goal
of
governing
aurora
using
these
v2
contracts
is
is
in
scope
of
this
investigation.
A
A
Well,
first
of
all
what
how
we
are
going
to
do
it,
we
are
going
to
fork
or
we
are
going
to
take
the
some
kind
of
release
of
sputnik
dao
version
2
and
we
are
going
to
deploy
the
separate
smart
contracts.
So
this
is
going
to
be
a
dao
smart
contract.
A
We
we're
going
to
deploy
the
smart
contract
with
our
own
key,
but
then
we
are
going
to
transfer
we're
going
to
delete
this
key
and
then
the
dell
members
will
be
able
to
update
the
smart
contract
by
themselves.
A
So
what
are
the
things
that
we
expect
the
dao
to
to
work
on
in
the
very
beginning
right?
So,
first
of
all,
it's
this
is
the
management
of
the
of
the
seats
yeah
or
member
member
management.
A
A
A
So
this
is
the
most
you
know
crucial
thing.
Then
we
need
to
make
sure
that
we
understand
how
to
create
different
levels
of
different
control
groups.
A
Well,
I
I
I'm
not
not
quite
sure
how
how
how
these
are
names
and
how
these
are
named
in
inside
of
sputnik
the
ov2,
but
as
far
as
I
understand
as
far
as
what
from
what
india
is
saying
is
that
we
are
able
to
specify
what
groups
of
people
are
able
to
vote
on
some
kind
of
specific
decisions
right,
and
in
this
case
the
question
is
about.
Why
do
we
need
to
have
it
is
that
we
need
to
have?
We
need
to
set
specific
permissions
for
rainbow
bridge
contracts
and
aurora
contracts.
A
So
these
are,
we
will
need
to.
We
will
need
to
use
some
kind
of
specific
groups
of
of
you
know
some
kind
of
safety
safety
council,
or
something
like
that
because,
for
example,
there
is
no
point
in
casing
the
dow
there
is
a
company
that
that
is
or
like
and
see
that
is
represented
by
the
vc.
There
is
no
point
in
asking
the
vc
to
to
vote
for
the
contract,
update
right,
so
they're
not
going
to
look
into
it.
So
why
not?
Why
not?
To
use
the
control
groups
right,
but
this
this
is.
A
This
is
a
good
feature
that
it
is
there.
Then
I
believe
there
is
a
high
probability
that
one
of
the
first
discussions
in
the
dial
will
be
around
the
token.
A
So
we
need
to
make
sure
that
we
understand
how
to
how
the
token
can
be
created
and
again,
you
know
all
of
the
permissions
are,
on
top
of
the
token
updating
of
the
smart
contract
of
the
token
and
stuff
like
that
and
the
most
important
here-
or
maybe
this
is
not
the
most
important
here-
is
that
not
only
the
creation
of
the
token
but
also
attention
the
existing
token
to
adele?
A
So
so
the
dao
is
managing
the
existing
token,
and
the
reason
why
this
is
important
is
because
of
some
limitations
of
the
rainbow
bridge.
As
you
know,
at
the
moment,
users
are
not
able
to
transfer
near
native
fungible
tokens
to
ethereum
right,
so
we
we
have
disabled
this
functionality
in
the
rainbow
bridge
and
in
order
to
enable
it
well,
it
will
take
some
time.
I
would
say
this
is
not
the
the
primarily
path
for
the
tokens
and
for
liquidity
in
general.
A
It
seems
like
this
is
the
case.
A
That's
why
well,
it
can
take
some
time
and
now
the
question
is
whether
we
would
like
to
have
aurora
token
to
be
installed
inside
of
the
ethereum
defy
ecosystem
right,
because
if
so,
then
we
need
to
originate
our
token
snare,
c20
and
then
fully
bridge
it
to
near
all
of
the
supply
and
then
on
near.
We
will
have
the
aurora
token
contract
that
is
automatically
created
by
the
rainbow
bridge
factory,
and
then
we
will
need
to
attach
this
contract
to
dao,
so
the
dao
is
managing
this
stuff.
A
I
got
it
so
we
need
to
understand
how
to
do
this
stuff,
yeah,
and
so
these
are
the
functions
from
the
dial
that
are
going
to
be
really
really
needed
right
here.
A
Right
now
and
yeah
and
token
creation
attention
exists
and
talking
to
a
dao
and
talking
contract
updates
too,
because
at
the
moment
when,
when
the
tao
is
going
to
decide
well
again
in
the
doubt,
to
decide
to
have
a
token
and
if
the
and
when
the
dao
is
go
in
this
case,
when
the
dao
is
going
to
decide
what
is
going
to
be
the
tokenomics
of
the
token
or
what
use
cases
for
the
token
are
these
use
cases
need
to
be
implemented
inside
of
the
token
contract
right.
So
this
so
this
thin.
A
A
So
we
we
need
to
understand
what
to
do
with
it,
and
then
there
is
an
additional
thing
that
is
not
connected
with
dow,
but
rather
nap,
141
bridging
to
aurora,
and
so
in
case.
Aurora
now
is
going
to
be
a
bridged
asset
over
the
bridge,
and
now
we
have
an
np
141
assets
and
when
we
are
bridging
it
to
aurora,
we
will.
A
We
will
create
an
erc20
instance
right
and
in
case
the
and
obviously
it's
better
for
us
to
to
provide
the
additional
functionality
for
the
aurora
token
holders
inside
of
aurora
right,
because
they
do
not
have
near
accounts
and
that's
why
it's
pretty
important
for
us
to
be
able
to
update
the
vanilla
implementation
of
your
c20
inside
of
the
bridge
near
620
inside
the
inside
the
overall.
A
But
this
is
also
something
that
that
we
need
to
explore.
I
I
believe
we
we
already
know
how
to
do
it,
but
just
in
case
just
a
reminder
that
this
the
the
here
is
the
piece
that
that
where
we
would
need
to
have
it
yeah
with
regards
to
the
timelines
of
the
of
the
dow
creation.
A
So
we
are
in
the
final,
like
in
the
finish
line,
almost
with
the
with
the
picking
up
the
investors
in
this
round
and
and
then
obviously
will
be
some
kind
of
process
to
form
a
dao
and
to
invite
people
to
to
form
the
dao
actually.
And
it
will
take
some
time.
A
But
I
I
cannot
say
that
we
have
lots
of
time
and
it's
better
for
us
to
move
fast
with
the
dao
and
like
having
clear
understanding
on
how
to
work
with
all
of
these
things
will
help
us
to
breathe,
to
bring
the
front
end
closer
to
to
deliver
con
front-end
for
this
and
and
then
we
can
build
on
top
of
it.
Some
additional
functions,
maybe
some
token
holders
pollen
something
like
that
yeah,
so
that's
it.
So
these
are
my
like
general
inputs
here.
B
B
Yes
and
the
one
important
things
related
to
hackmd
documentation
with
comments,
most
of
them
is
broken.
I
don't
know
why,
but
it
it
was
related
to
a
token
management,
and
I
don't
know
who
author
of
that
comments,
so
I
think
I
should
connect
with
him
and
understand
what
what
problem
is.
A
I
think
that
this
is
ibiya,
because
he
is
a
major
contributor
there
like
there
is
a
high
probability
that
this
is
ilia,
so
it
will
be
pretty
hard
to
connect
with
him,
but
what
you
can
do?
Actually
you
can
contribute
to
that
hack
and
documentation
because,
well,
I
believe,
are
you
reviewing
also
the
code
of
the
smart
contract.
B
A
Okay,
okay,
well
maybe
you
can.
Maybe
you
can
get
in
touch
with
him,
mm-hmm,
okay,
it
would
be
easier,
but
you
know
lots
of
the
us
forks
are
this
week
on
on
bitcoin
miami
right.
B
A
B
A
Cool
cool
yeah,
one
additional
thing:
I
want
to
ch
a
question
to
you,
since
you
already
have
looking
into
this
contract
the
dao
updating
how
how
how
the
updating
contract
is
looking
like
in
the
dao.
So
imagine
the
dao
is
managing
some
kind
of
contract,
either
itself
or
some
kind
of
external
contract.
How
the
update
is
happening
so.
B
It's
special
function
for
updating
writing
by
ilya,
so
I'm
not
testing
that
functionality.
But
but
when
I
look
into
the
code
it
looks
pretty
good
and
I
believe
that
we
don't
have
any
issues
with
it,
but
I
I
will
test
us.
B
As
I
remember,
it
load
some
additional
additional
contract
data
and
I
I'm
not
prep,
I'm
not
remember
all
that
code,
but
I
remember
it
it
can
solve
update.
A
Okay,
yeah
yeah
yeah,
I
also
was-
was
getting
the
same,
the
same
perception
that
it
can't
self
update.
So
so
I'm
just
take
a
look
at
this
please
once
once
again,
I'm
trying
to
check
whether
my
hypothesis
is
correct
and
the
hypothesis
is
the
following-
that
somebody
submits
a
proposal.
He
uploads
the
wasm,
the
compiled
version
of
the
contract
and
then
it's
just
stored
in
the
storage
over
there
and
then
this
on
this
proposal.
A
People
can
vote,
and
you
know
the
last
vote
that
actually
says
that.
Well,
it
goes
over
the
over
the
over
the
line,
like
obviously
we
can.
We
can
adjust
this
when
there's
enough
propose
votes
for
this,
then
the
last
vote
is
this
transaction
is
actually
doing.
The
update
of
the
of
the
contract
and
sputnik
dao
is
actually
taking
this
uploaded
binary
and
put
it
there,
because
sputnik
dao
has
has
an
ability
to
update
a
third
party
contract.
A
This
is
this:
is
my
hypothesis
and
just
need
to
check
whether
this
is
this
works
like
that
this
is.
This
is
important
from
the
compliance
perspective,
so
this
is
important
for
for
legal
reasons,
to
understand
whether
it
works
like
that.
B
A
Okay,
any
additional
questions
around
roar,
though.
D
D
G
D
Think
yeah
so
probably
having
this.
So
if
it's
plain
like
bridge
tokens,
it
can't
have
any
aurora
specific
functionality
on
your
blockchain.
It
can
only
have
such
functionality
on
ethereum
blockchain,
and
this
is
doesn't
look
great.
I
think
we
may
want
some
specific
functionality,
specifically
near
blockchain,
so
a
different
approach.
There
are
multiple
approaches
to
solve.
This
one
is
to
actually
finish
the
erc20
connector
and
make
it
possible
to
bridge
tokens
from
near
to
ethereum.
D
A
Yeah
even
yeah,
I
ca
I
in
general,
I'm
okay
with
you.
I
do
not.
I
do
not
agree
with
with
your
fern
thesis
that
that
you
say
that
that
the
bridge
tokens
need
to
be
all
absolutely
the
same.
The
reason
for
this
is
that
again,
there
are
lots
of
tokens
that
that
are
having
compliance
on
top
of
them
and
in
order
for
them
to
work
correctly,
they
need
to.
A
A
Compliance
I'm
talking
exactly
specifically
about
the
stable
coins,
so
stable.
The
way
how
stable
coins
are
working
right
now.
Well,
some
of
the
stable
coins
are
working
right
now
is
that
they
are
regulated
right
behind
the
usdt.
There
is
a
germany
exchange
and
there
is
a
u.s
bank
and
they
need
to
take
care
of
the
illegal
activities
that
that
are
happening
with
with
the
usd.
A
So
that's
why
usd
token
has
an
ability
to
ban
user
with
those
with
all
of
his
funds.
So
that's.
This
is
something
for
everybody
to
know.
Actually,
if
you
are
using
usdt,
you
can
be
banned.
You
can
lose
these
tokens.
You
can
lose
the
ability
to
transfer
these
tokens,
and
this
is
a
specific
requirement
right.
So
actually
in
case
you
used
it,
you
will
find
that
there
were
some
kind
of
bad
activities
happening
and,
in
your
you
know,
funding
terrorism
or
something
like
that.
A
Then
they're
going
to
ban
you
and-
and
they
need
to
have
this
opportunity
because
of
this-
they
have
this
functionality
now
in
order
to
be
fully
compliant
with
this,
we
actually
need
to
provide
the
same
functionality
or
like
not
we
but
use
the
t
to
provide
the
same
functionality
on
near
blockchain
right
now
we
are
small,
and
you
know
people
can
also
exchange
the
t
in
in
in
the
uni
swap
and
in
other
solutions
right,
so
I'm
not
quite
sure
how
they
are
dealing
with
that
stuff,
but
in
case
in
case
there
is
one
billion
worth
of
usd
bridge
to
to
aurora.
A
It
will
be
very
interesting
for
for
usd
for
tether
to
make
sure
that
they
are
compliant
on
aurora,
too
right
and
and
that's
why
we
need
to
have
an
ability
to
update
this
smart
contract
so
for
the
so.
The
the
right
way
for
for
us
to
work
with
the
smart
contracts
that
are
deployed
by
the
bridge
factory
is
actually
in
case
the
original
provider.
Of
the
token
will
come
to
us
or
to
you
know
the
aurora
dao
in
this
case,
because
eventually
aurora
dao
is
going
to
manage
the
rainbow
bridge
contracts
too
right.
A
Why
not,
if
in
case
this,
this
entity
is
going
to
prove
the
fact
that
it
is
them
who
own
this
token,
then
we
need
to
hand
over
the
the
keys
from
the
the
full
access
keys
from
from
these
contracts,
and
then
they
will
do
anything
that
what
they
want
to
do.
The
only
thing
that
we
can
rely
on
is
the
nap141
standard.
For
this
token,
and
that's
it
all
of
the
additional
functionality
can
be
implemented,
and
there
should
be
an
ability
to
implement
this.
A
So
we're
just
not
facing
this
issue
right
now,
but
eventually
we
we
will
need
to
to
take
care
of
this
yeah,
but
for
now
customer
or
token
connector
can
be
yeah,
and
also
I
just
want
to
mention
that
the
bridging
aurora
from
year
c20
to
to
near,
is
not
a
good
idea,
at
least
because
the
majority
of
the
token
supply
is
going
to
to
be
hauled
by
rainbow
bridge
contracts.
Right
in
case
aurora
is,
is
going
to
hit
the
valuation.
A
The
token
aurora
token
is
going
to
hit
the
variation
of
1
billion
or
10
billion,
like
almost
the
whole
supply,
is
going
to
be
in
in
the
british
smart
contract
right
and
well,
as
we
know,
it
is
enough,
even
tens
of
millions
worth
of
tokens
for
the
hackers
to
try
to
hack
everything
right.
So
we're
just
introducing
an
additional
point
of
attack
here,
so
it's
better
to
have
indeed
a
near
native
token.
A
That
is
so
less
less
contracts
that
I
included
in
in
this.
In
these
things
just
to
have
less
lower
risk
here,
but
yeah.
So
maybe
we
will
need
to
make
a
custom
aurora
token
connector
or
finalize
your
c20
connector,
or
something
like
that,
so
both
so
all
of
this,
all
of
these
things
are
are
correct.
A
Let's
discuss
it
on
monday,
probably
what
what
would
be
our
choice
here,
because
if
we
would
like
to
finalize
your
620
connector,
as
we
know,
connectors
are
not
that
simple
to
build,
especially
if
we
want
to
do
all
the
checks
and
all
of
the
reviews
so
yeah.
Let's
come
back
to
this
on
monday.
D
D
So
if
we
we
really
don't
need
the
rainbow
bridge
for
those
tokens,
because
if
they
control
the
near
smart
contract.
For
this
token,
they
can
just
build
any
amount
of
this
token
on
the
near
side.
So,
for
example,
if
someone
wants
to
transfer
some
usd
from
ethereum
to
near
they,
the
tether
which
already
have
full
access
to
those
to
the
stock,
and
they
can
just
burn
some
of
these
tokens
on
the
ethereum
site
and
mint
the
same
amount
of
near
size
right.
So
all
right.
A
But
but
like
this,
this
is
more
of
a
type
of
religion.
So,
let's
not
get
in
into
these
discussions.
We
are
not
going
to
say
to
tether
what
what
to
build
right,
whether
they
need
to
to
build
their
own
trusted
bridge
in
between
aurora
and
and
ethereum
right.
So,
let's
just
move
on,
I
believe,
are
there
any
additional
points
in
the
discussion
section
that
we
would
like
to
address.
B
A
Okay,
yeah.
Well,
then,
then,
I'm
going
to
do
a
quick,
quick
mention.
It
seems
to
me
marcel
that
we
need
to
check
whether
the
bridge
is
actually
relaying.
No,
I
believe
we
fall
into
this
attention
when
the
bridge
is
relaying
at
the
last
blocks
in
the
e-book.
So
we
are
again.
You
know
a
little
bit
offset
from
the
current
state.
I
was
trying
within
the
last
couple
of
days
you
know
to
to
speed
up
their
lane,
but
just
just
yeah.
I
think
it's
worth
checking.
A
So
we're
not
we're
not
delaying
the
transfers
from
here
to
ethereum.
G
A
Right
and
yeah
before
going
to
the
next
week
just
wanted
to,
since
we
were
talking
about
the
we
were
talking
about
the
the
value
of
the
bridge
that
that
bridge
contracts
are
holding
just
wanted
to
to
show
to
you.
A
So
we
have
this
awesome
dashboard
from
from
zavadil
and
look
together
in
near
and
in
other
tokens.
We
already
have
right
now,
more
than
three
million
in
total
assets
bridgette.
So
congratulations!
All
of
you!
All
of
these
contracts
that
that
you
have
developed
now
are
managing
three
million
tokens.
C
Do
we
have
this
link
somewhere
on
the
site?
This
would
be
good
stats
to
show
highlight.
B
A
C
A
Right
yeah,
so
it's
it's
a
good
analytics
and,
as
you
can
see,
people
are
starting
to
appreciate
the
fact
that
that
they
are
able
to
transfer
near,
and
this
blue
thing
is
actually
near
actually
near.
A
There
is
the
majority
of
the
liquidity
right
now
so
yeah
you
can
see,
people
are
transferring
usdt,
people
are
transferring
wrapped,
eth
and
so
on,
but
but
yeah
lots
of
people
are
plugging
in
near
in
the
in
the
defy
space
of
ethereum
and
and-
and
this
is
just
one
week
and
just
reminded
to
everybody
near
transfers
to
ethereum
were
launched
just
one
week
ago
in
this
particular
call.
So
this
is
what
you
are
doing
guys
with
the
market.
A
Okay,
yeah:
let's
go
back
to
the
to
the
next
week
and
what
are
the
plans
to
know
for
the
next
week.
H
And
yeah
one
one
question:
I'm
sorry,
I
was
muted
so
when
we
were
discussing
how
how
the
bridge
works
and
where
was
understanding,
why
it
takes
16
hours
to
to
bridge
from
back
to
ethereum
and
it
seems
to
be
related
to
controlling
the
the
gas
costs.
H
A
H
A
A
A
Maybe
we
can
write
them
with
some
kind
of
other
programming
language,
but
it
depends
really
on
the
on
the
on
the
libraries
that
we
have
for
connecting
with
the
networks
right,
so
we
heavily
rely
on
there
on
the
web
3gs
and
near
api.js,
so
maybe
maybe,
where
we're
going
to
stick
with
javascript
or
typescript,
and
for
this
specific
task
for
managing
of
these
of
these
three
layers
and
making
them
work
in
a
good
way.
I'm
right
now,
I'm
focusing
on
hiring
an
additional
person
to
help
us
so
yeah.
A
When
this
person
is
going
to
join
us,
he
is
going
to
own
these
three
layers
and
he
will
be
able
to
you
know
to
to
improve
this
and
improve
this
logic
right
now.
The
way
how
layers
are
working,
we
can
specify
just
the
the
offset
or
like
the
the
periodicity
of
the
transactions
that
we
are
sending
to
from
near
to
ethereum
so
yeah.
A
Unfortunately,
it
looks
like
that
and
no
additional
you
know
complicated
behavior
like
relayers,
would
like
to
submit
the
transaction
right
now
it
tries
to
take
a
look
at
what
is
the
price
tries
to
analyze
the
trend
in
the
gas
price?
In
case
it
goes
down?
It
potentially
can
wait
a
little
bit
right
and
not
know
that
type
of
things
no
smart
behavior,
unfortunately
there,
but
there
is
a
a
lot
of
room
for
you
know
some
kind
of
heuristics
and
ways
how
how
this
to
be
improved.
A
A
Okay,
how
can
I
put
it
here?
Let
me
put
it
three
layers
update.
A
B
A
Okay,
okay,
so
good
idea
with
you
on
this
now,
actually,
just
just
for
for
the
sake
of
everyone's
information,
we
are
now
spending
less
than
one
ether
per
week,
which
means
14
or
15
transactions,
so
one
transaction
is
is
less
than
one
fifteenth,
so
factor
which
is
kinda
cool.
So
we
are.
We
are
not
spending
lots
of
time.
No
lots!
Lots
of
money!
Sorry!
In
the
beginning
of
the
execution
of
the
bridge,
it
was
a
pretty
common
thing
that
even
one
transaction
was
over
one
ether,
so
yeah
great
improvements.
B
Yeah
so
yeah,
so
mainly
I'm
gonna
focus
on
finishing
up
the
hard
hat
example.
If
there's
no
issues
in
the
future
and
also
I'm
going
to
iterate
on
this
with
r2
and
the
metamask
so
so
far
we
don't
have
this
notification
issue.
That's
always
yet,
and
I'm
still
also
having
some
issues
with
the
invalid
argument.
Coming
back
from
the
rpc
earlier.
B
A
Right,
co,
yeah.
I
also
asked
ahmed
to
join
the
interview,
so
we
have
more
people
who
are
interviewing
new
engineers,
so
cool
I'm
going
to
work
on
on
the
legal
setup.
Continue
this
because
most
probably
next
week
is
going
to
be
very,
very
intense
with
this
stuff
and
actually
are
so
this
will.
This
will
most
probably
influence
a
little
bit
yourself
too.
C
A
Yeah,
I'm
going
to
continue
the
invest
round.
Actually
it
is
not
that
much
time
left
for
us
to
communicate
with
our
well
to
have
talks
with
the
with
potential
investors.
A
I
I
believe
it's
maybe
one
week,
maybe
a
little
bit
more
than
that,
but
but
that's
it
so
pretty
soon
you
will
have
me
in
my
full
capacity
and
yeah
I'm
going
to
continue
hiring,
because
I
believe
we
have
some
some
good
candidates
in
the
stack.
So,
let's,
let's
close
them,
let's
choose
the
right.
One.
C
Yeah
so
for
for
me,
there's
a
lot
of
support
and
documentation
work
every
every
week,
so
that's
a
staple.
By
now.
Also,
as
I
mentioned,
we
need
to
get
the
default
funded.
People
are
gonna,
be
hitting
it
pretty
hard.
So
we
need
to
get
a
get
a
big
pile
of
f
point,
I'll
sort.
It
out.
C
A
Right
cool
evgeny:
what's
on
your
side,.
D
And
joshua
said
that
it's
ready
for
reviewer.
A
Here:
okay,
cool:
you
gain
your
hanukkah.
B
So,
of
course,
it's
putting
down
currently
deployed
to
testnet.
I
should
test
all
things
that
we
previously
discussed
and
understand
is
work.
B
B
A
Okay,
frank.
B
B
Well,
we
have
some
some
things
that
work,
but
I
only
implemented
stuff
so
far
that
I
needed
for
the
bully.
So
all
right
told
me
it's
like
low
prior
to
to
have
like
all
the
api
running
so.
A
B
We
go
along,
but
it's
not
a
high
priority.
A
Yeah,
if
it
will
be
good,
it
will
be
a
nice
addition,
because
yeah
coming
back
to
the
earlier
discussion
with
this
thing,
we
potentially
can
write
it
in
in
go
right.
It
will
be
much
simpler.
C
A
C
Indeed,
we
have
so
right
now
we
have
a
lot
of
coding.
B
C
Typescript,
which
probably
going
forward,
is
going
to
have
to
get
rewritten
in
something
more
robust,
let's
say,
and
the
only
two
choices
really
are
rush.go,
so
we'll
come
back
to
this.
This
question
for
sure.
B
A
Actually
mike
well,
my
question
to
joshua
would
be,
but
maybe
someone
knows
the
burden
hard
fork.
Are
we
actually
contributing
here
to
sputnik
vm.
C
Correct
we
will
be
making
upstream
contributions.
Okay,.
A
That's
that's.
That's
super
cool.
I
just
want
to
mention
that,
let's
do
it,
let's
help,
let's
help
parity
here
as
much
as
we
can.
A
F
A
Oh
yeah
yeah
something
pretty
common
cool
marcelo.
G
Well,
we'll
be
finalizing
the
even
layer
to
how
it
deployed
to
our
infrastructure
and
finalizing
rc20,
connector
and
access
to
compile,
making
sure
they're
safe
to
be
released
and
hopefully
releasing
next
week.
I
think
that's
definitely
double,
and
then
there
is
some
sanity
job
that
I've
been
doing
in
background
about
our
our
repositories
related
with
the
bridge
like
making
sure
we
annotate
the
deploy
contracts,
which
is
our
checking
that
we
have
up
to
the
agreed
me
matches
everything
there.
G
Analyzing,
eventually,
layer,
eventually
yeah
and
deploying
to
our
infrastructure.
That
involves
also
like
adding
monitoring
and
alerts
for
that.
G
We
have,
we
have,
we
have
exposed
metrics,
but
we
have
no
monitoring.
A
G
B
A
G
Yeah
yeah:
that's
how
it
will
happen
also
well
related
to
the
layer
I'll
work
with
peer
to
make
sure
that
the
ui
is
able
to
work
nicely
within
roller,
so
user,
don't
double.
A
A
A
Okay,
cool
matt.
H
Yeah
so
integrate
the
faucet
into
the
bridge.
Ui
continue
with
the
dial
specification,
try
to
get
the
ui
going
on
the
on
the
first
iteration
finish,
the
bridge
blog
article
and
then
there's
a
couple
of
small
things
that
I
I
have
to
support
on
the
in-ear
liquidity.
Next
steps.
A
Okay,
okay,
let's
discuss
oh,
it
seems
like
a
pretty
solid
plan.
I
actually
have
a
couple
of
bucks
to
submit
to
you
here
with
the
rainbow
bridge
yeah.
But
let's,
let's
do
it
outside
outside
this
call.
C
A
C
B
A
There
is
a
category
updates.
There
is
only
one
weekly
update
here
from
the
last
week,
so
yeah
please
come
here.
You
will
see
the
short
resume
of
what
is
happening
here
and
yeah
always
can
you
can
check
the
links,
I'm
trying
to
keep
the
info
very
consumable
for
you,
okay,
great,
so
thanks
for
joining
us.
Hopefully
that
was
interesting.
A
Call
for
you
for
all
of
the
guys
who
want
to
go
deep
into
what
we
are
doing.
Go
to
try
test
the
faucet
go:
try
our
f
region,
connector,
an
ability
to
bridge
ether
from
robson
to
aurora
testnet.