►
Description
Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on Swarm, IPFS and more.
https://archive.devcon.org/archive/watch/6/build-a-dapp-on-optimism-how-to-conquer-l2-bridging/
L1 to L2, L2 to L2, L2 to L1...bridging is complicated, messy, and difficult! In this workshop, we'll teach you how to easily build a DApp that leverages Truffle's L2 Bridge Box, which helps you quickly set up a DApp configured to handle all the complexities that come with L2 bridging.
Speaker(s): Emily Lin
Track: Layer 2s
Keywords: Bridging,Optimism,L2
Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/
Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/
A
A
Emily
I
am
the
Truffle
developer
Advocate.
Today
we're
going
to
be
talking
about
building
a
Dap
on
optimism,
specifically
talking
about
how
to
incorp
bridging
into
your
optimism.
Daps
just
want
to
give
a
brief,
disclaimer
I
do
not
work
for
optimism.
Nor
do
I
represent
their
opinions.
However,
I
really
love
the
project.
A
So,
let's
start
off
optimistic
Roll-Ups,
here's
a
crash
course.
So
for
those
of
you
who
don't
who
don't
know
just
brief
introduction
right?
What's
a
layer
one,
what's
a
layer,
two
layer,
one
ethereum
Bitcoin
that
base
layer,
Layer
Two,
that
a
separate
blockchain,
that's
focused
specifically
on
increasing
transaction
speed,
scalability
and
what's
really
interesting
here
as
well,
is
utilizing
ethereum
for
data
availability.
A
So,
specifically,
the
point
of
posting
transaction
data
and
getting
it
from
ethereum
I
do
want
to
note
one
specific
thing
you
might
wonder:
Layer
Two
specifically
are
defined
by
deriving
its
security
from
ethereum.
So,
if
you
think
about
something
like
a
side
chain,
for
example,
they
don't
so
they
those
are
not
qualified
as
a
layer
two.
So
that
is
like.
Basically,
the
key
caveat
you
need
to
think
about.
A
So
why
do
I
even
care
about
this?
Why
am
I
here
again,
if
you've
been
around
in
the
space
you've
probably
heard
blockchain
trilemma?
It's
a
pick
two
out
of
three
decentralization
security
and
scalability
for
those
of
you
who,
in
the
ethereum
community
I
hope
we
have
all
agreed
that
decentralization
and
security
is
the
most
important
thing
right.
So
what
happens
about
scalability?
Well,
this
is
something
we
still
really
need
to
care
about,
because
scalability
right
affects
gas
costs
and
gas
costs
is
going
to
affect
the
adoption
of
ethereum.
A
So
this
is
something
we
really
need
to
think
about,
and
who's
here
to
help
us
layer,
twos.
Okay,
thank
you
right.
So
definition
again
of
a
layer
two
is
to
decrease
L1
congestion
by
bundling
up
transactions
and
submitting
that
to
ethereum
again
things
to
note
right
gets
its
data
availability
from
ethereum,
specifically
deriving
its
security
from
ethereum
and
helping
us
maintain
that
decentralized
aspect.
A
So
next
piece
we're
going
to
talk
about
optimistic
Roll-Ups,
because
that's
what
we're
focusing
on
today
I
am
not
going
to
touch
on
zero
knowledge.
There
are
so
many
talks
at
Bogota
about
zero
knowledge,
so
talk
to
them
not
me,
but
to
briefly
touch
about
optimistic,
Roll-Ups,
Roll-Ups,
again
pretty
self-explanatory,
you
roll
up
a
bunch
of
transactions
and
you
submit
it
and
post
it
once
to
the
L1
again.
This
comes
in
two
primary
flavors
right
now
optimistic
Roll-Ups,
as
well
as
zero
knowledge
to
touch
upon
optimistic
Roll-Ups.
What
makes
those
different
is?
A
They
are
optimistic
right.
So
when
we
submit
these
transactions
to
ethereum,
we
just
assume
they
are
valid
and
you
might
say
wait
that
seems
kind
of
bad
right.
Well,
actually,
there
have
there's
this
thing
called
The
Challenge
period.
So,
essentially,
during
this
challenge
period
anybody
can
come
and
say,
like
hey,
I,
think
this
is
wrong
and
if
they
do
that
they
have
to
submit
a
fault
proof
and
basically
the
fault
proof
basically,
either
validates
hey.
A
If
you've
ever
walked
on
a
bridge
before
connecting
to
blockchain
ecosystems,
things
to
note
about
bridges.
Right
again
is
this
transfer
of
assets
and
information.
So
a
lot
of
times
we
talk
about
transferring
eth
tokens,
but
you
can
also
transfer
arbitrary
data.
The
other
piece
is,
you
know,
we're
moving
towards
a
multi-chain
world.
Basically,
the
point
of
that
right
is
to
take
in
the
pros
of
one
chain
to
alleviate
the
cons.
A
So
when
we're
talking
about
l1s
and
l2s
we're
talking
about
the
pros
of
decentralization
security
of
ethereum
while
alleviating
the
cons
by
using
an
L2
chain
for
that
scalability
aspect,
the
important
part
with
Bridges
is
it
allows
us
to
call
an
L1
contract
function
from
the
L2
and
vice
versa.
So,
if
I'm
on,
like
optimism,
contract
and
I,
say
hey
ethereum,
contract
I
want
to
call
your
function,
but
just
say:
okay,
we
can
do
that.
The
typical
way
of
doing
this
right
now
is
this
idea
of
locking
assets.
A
So
it
kind
of
looks
like
user
one
will
lock
Assets
in
a
big
bridge
contract.
The
equivalent
amount
of,
like
token
will
be
I
guess
created
on
the
L2
and
then
when
we
want
to
put
it
back.
All
of
that
is
burned
off
and
then
released
for
the
person
on
the
L1
again
big
disclaimer.
There
is
no
bridging
standard
that
exists
yet
again.
A
lot
of
research
has
gotten
into
this
I
think
also,
probably
one
of
the
reasons
bridges
are
a
little
bit
unsafe
because
it's
totally
a
new
frontier
right.
A
A
There
is
a
a
study
done
basically
60
nine
percent
I,
don't
know
if
that
was
like
fake
number,
but
69
of
attacks
have
been
on
bridge
hacks
and
then
very
recently,
actually
like
right
before
I
was
creating
this
presentation
Finance
by
a
BSC
Bridge
rest
in
peace,
but
you
did
good
for
my
presentation
because
I
got
to
talk
about
you
on
the
next
slide,
but
anyways.
Why
does
this
happen
again,
as
I
had
mentioned
in
that
previous
section
about
how
bridges
are
typically
Run?
A
Is
it
locks
up
liquidity,
and
that
is
like
a
prime,
centralized
location
for
bridge
hacks,
so
something
people
might
also
think
about
when
creating
Bridges
is
the
idea
of
decentralized
bridges?
I,
don't
know
much
too
much
about
it,
so
I'm
not
going
to
go
into
it,
but
you
can
kind
of
think
about
like
that
is
a
consideration
you
need
to
take,
and
centralization
is
again
a
big
part
of
why
Bridge
hacks
are
so
intense.
A
A
So
for
currently
the
way
these
Bridges
identify
and
authenticate
Target
and
source
blockchains
is
through
its
chain
ID,
and
the
BSC
case
specifically
did
not
check
the
chain
ID
through
the
cross
chain
message
and
again
something
to
think
about.
So
obviously,
if
you're
building
a
bridge,
maybe
read
up
on
all
your
predecessors
and
do
everything
they
did,
but
better
private
Keys
again,
that's
something
we
really
care
about
different
ways
of
handling
it.
A
Hardware
wallet,
you
know,
multi
key
chain
system,
Etc
and
then
I
think
something
people
don't
necessarily
always
think
about.
Is
there's
always
that
web
layer
right
so
the
way
bridges
are
surfaced.
Right
now
is
often
through
a
UI
right.
We
talk
about
hardening
your
smart
contract.
Maybe
one
way
to
also
think
about
how
you
harden
security
is
at
that
UI
level.
A
There's
a
lot
more
I
added
a
link
of
like
some
research
that
people
were
doing,
but
you
could
probably
just
Google
and
then
like
read
every
single
page,
because
it's
it's
intense
guys
so
anyways,
yes,
like
I,
said
bridging
is
hard.
What
are
we
doing
here?
We're
actually
going
to
go
over
optimism's
Bridge
contracts?
They
have
already
written
a
few
contracts
as
well
as
provided
an
SDK
for
us
to
do
this
for
a
simple
use
case
again.
I
think
it's
awesome
because
basically
Bridge
contracts
probably
require
a
lot
of
security.
A
Auditing
I
am
poor,
I'm,
not
a
student
anymore,
but
I'm
poor
I
can't
do
that.
So
optimism
kind
of
has
provided
that
ability
for
us
to
incorporate
bridging
through
battle
tested
contracts
as
well
as
an
SDK.
If
you
don't
want
to
do
any
solidity
at
all,
so
let's
actually
walk
through
what
optimism
has
provided
so
that
first
thing
I
talked
about
was
transferring
of
data,
so
this
is
kind
of
the
base
level
of
what
it
looks
like
there's
two
contracts
called
L1
cross
domain.
Messenger
L2
cross
domain
membership.
A
Again
these
are
pre-deployed
by
optimism.
So,
if
you're
bridging
on
optimism,
you
will
be
interacting
with
these
contracts.
You
can
get
their
addresses
from
their
GitHub
repo.
They
will
have
one
for
each
one
for
each
chain
ID.
So
there's
an
address
for
Gurley
optimism.
There's
an
address
for
Gurley
ethereum,
mainnet,
Etc
kind
of
diving
into
this
deeper.
The
way
this
works
is
essentially,
we
have
I'm
going
to
highlight
the
probably
the
two
most
important
functions
in
this
interface.
Specifically,
the
first
one
is
send
message.
A
So
that
is
what
allows
us
to
say:
hey
I'm,
L1
contract,
but
I
want
to
call
Contract
function
on
L2.
The
way
this
works
is,
let's
start
over.
I
am
ethereum.
Contract
I
am
calling
L2
contract.
That's
the
target
address
so
I'm
going
to
input
that
in
there
the
second
piece
is
call
day
data
right.
So
if
you
don't
know
how
basically
solidity
call
functions
right
now,
it's
encoded
in
two
bytes,
specifically
by
like
the
function
string
name
as
well
as
the
inputs
that
go
into
it.
A
So,
in
order
to
call
it
on
the
L2,
I
have
to
encode
that
function,
name
and
inputs
to
be
passed
over
to
the
L2
contract
and
the
gas
limit
actually
is
pretty
complex.
It
seems
simple
to
understand,
but
it's
how
much
you're
willing
to
pay
so
I'm
going
to
go
into
the
math
here
specifically
posting
from
L1
to
L2
requires
gas
on
the
L2
section
right.
A
In
order
to
do
that,
optimism
says
we
will
provide
1.92
million
L2
gas
for
you
for
free.
However,
in
the
case-
and
this
is
pretty
rare-
assuming
that
like
maybe
you
actually
need
to
spend
more
gas
than
that,
you
actually
would
have
to
specify
that
ahead
of
time
and
that
gas
is
coming
from
your
L1
gas
at
a
1
to
32
ratio.
So
in
this
specific
example
right
suppose
the
transaction
actually
took
2
million
gas
on
optimism.
You
have
80
000,
L2
gas.
A
You
need
to
cover
which
is
equivalent
to
2500
L1
gas
I
hope
that
made
sense.
If
not,
we
can
talk
about
it
and
I
will
just
say
the
same
thing
over
until
you
understand
it.
On
the
other
hand,
we
moved
from
L
to
L1.
This
is
going
to
be
more
expensive
because
there's
two
transactions-
we're
posting
specifically
the
L2
fee
to
post
initialize
a
transaction
and
then
the
L1
fee
to
actually
finalize
it
on
the
Chain.
So
this
is
more
expensive.
A
L1
is
significantly
more
expensive
than
L2,
but
that's
because
scalability
wow,
okay,
good
next
piece-
is
cross
domain.
Messenger
sender.
Okay,
again,
for
those
of
you
who
don't
know
when
you
call
contract
functions
on
a
smart
contract.
Message.Sender
is
how
you
know
the
address
that
it's
calling
it
right.
But,
for
example,
when
we're
thinking
about
bridging
right,
say:
I'm
like
L1
contract
calling
L2
contract
function,
message.sender
is
actually
gonna.
What
do
you
call
it
surface?
A
The
address
of
the
L1
contract
domain
cross
domain,
messenger
contract
right,
I,
don't
know
if
I
said
that
correctly,
but
you
know
what
I
mean
the
pre-deployed
optimism
one.
So
what
do
we
want
to
know?
Actually
I
want
to
know
my
address
I
want
to
know
the
L1
contract
address.
The
way
this
is
implemented
actually
allows
to
say:
okay,
when
I
call
X
domain
blah
blah
blah
I'm
going
to
return
my
address
not
the
address
of
the
deployed
messenger
contract
again.
The
next
piece
here
is
transferring
Ethan
erc20
tokens.
A
This
is
probably
the
most
common
way
of
doing
bridging,
which
is
why
optimism
has
kind
of
put
that
between
behind
an
SDK
I'm
not
going
to
get
into
it,
because
I
only
have
50
minutes.
Thank
you
Dev
vakoda
or
Devcon,
but
there
is
a
really
great
ethereum
tutorial
written
by
a
person
on
there
that
actually
steps
through
the
contract
step
by
step.
A
So
if
you
are
interested
in
understanding
how
the
token
Bridge
works
at
a
smart
contract
level,
I
suggest
going
there
if
not
I,
will
be
diving
into
more
of
the
part
about
using
the
SDK
itself.
I
want
to
know
as
well.
There
are
some
things
to
know:
you
cannot
Bridge
every
erz
20..
So
the
way
the
token
standard
Bridge
works
is
it
identifies
both
the
let's
say,
erc20
token
address
on
the
L1
and
then
a
token
address
on
the
L2.
A
A
So
if
you
want
to
add
to
that
token
list,
you
have
to
create
a
PR
so
that
the
token
Bridge
knows
which
contract
to
bridge
between
and
then
two
keywords
here,
deposit
so
deposit
means
I'm,
depositing
eth
going
from
L1
to
L2
withdraw
is
going
to
be
withdrawing
so
going
from
the
L2
to
the
L1
yeah
okay.
So
let's
do
the
build
person
portion?
What
are
we
building
so
starting
off?
I?
A
Think
one
of
the
most
common
use
cases
where
you
might
want
to
embed
a
bridging
UI
is
an
nft
Marketplace,
so
we're
building
one
on
optimism
and
I
want
to
talk
a
lot
about
bridging
because
of
the
ux
problem.
So
if
you've
interacted
kind
of
with
bridging
right
now
oftentimes
it's
a
separate
UI.
So
you
go
to
another
website
or
something
do
the
bridging
and
then
come
back.
We're
smart
here
we're
at
Devcon.
We
understand
how
to
do
that,
not
necessarily
the
best
ux
for
I,
don't
know
my
mom.
A
So
what's
the
solution,
her
name
is
Bridget
the
bridge
widget.
Hopefully
you
understood
that
ton,
if
not
I,
will
explain
it
to
you
many
times
until
you
understand
it
but
anyways.
The
point
is
to
embed
this
kind
of
UI.
It
is
just
a
component.
So
imagine
if
I
took
the
time
to
put
this
on
npm,
you
could
just
npm
download
into
your
app
I.
Didn't
do
that
because
I
don't
have
time
but
anyways.
A
A
A
A
We
are
going
to
be
connecting
to
the
girly
test
net,
as
well
as
the
optimism
test
net,
because
we
are
working
with
these
deployed
contracts,
so
you
will
need
that
information
from
inferior
you'll
create
a
project
separately
to
that,
because
this
is
an
nft
Marketplace.
We
will
be
uploading
metadata
up
to
ipfs.
You
can
do
that
through
inferior
as
well.
They
have
an
ipf
dedicated
ipfs
Gateway.
You
can
create
for
yourself
as
always
metamask.
A
You
need
that
for
everything
and
then
Gurley
East
optimism,
Gurley
East
and
specifically
I
was
going
to
mention
girly
die.
So
when
I
was
talking
about
the
part
where
we're
going
to
do
the
script
with
the
SDK,
when
we're
transferring
tokens,
the
one
we
decided
to
choose
was
die.
So
if
you
want
to
actually
run
the
scripts,
you
will
need
some
die
in
your
wallet.
A
In
order
to
do
that,
the
process
for
doing
it,
I'm
just
going
to
quickly
say,
is
take
early
East,
go
to
uniswap
change
your
test
net
over
to
Gurley
and
then
do
the
swap
between
girly
eat
and
girly
die,
and
that's
how
you
do
it
so
are
we
doing
this?
Live
no
I'm,
just
gonna
walk
through
all
the
contracts,
and
hopefully
you
will
understand
if
not
I
I
can't
explain
it
to
you
over
and
over
again,
because
the
Wi-Fi
is
not
my
fault.
So,
let's
move
forward.
A
First
thing
you
would
do
assuming
like:
let's
not
let's
say
we're
not
in
this
UI
is
a
truffle
unboxed
optimism,
fridge
and
then,
if
I
wasn't
here,
I
would
have
called
it
Devcon
demo
and
it
would
Manifest
this
box
right
and
so
I'm
going
to
step
through.
What's
in
this
box,
that
makes
it
optimism
compatible.
So
the
first
part
here
is
going
to
be
your
contracts,
so
in
a
multi-chain
world
you're
going
to
have
different
contracts,
we
should
separate
that,
logically
into
ethereum
contracts,
as
well
as
our
optimism
contracts.
A
A
Specifically
in
truffle,
you
have
the
ability
to
number
your
migrations
or
your
deployments
so
which
is
really
helpful
for
multi-chain
deployments,
because
then
you
can
decide
I
care
about
this
migration
in
this
order,
Etc,
which
is
why
they're
prefixed
by
numbers.
The
next
piece
is
scripts.
So
this
is
just
this
script
is
actually
just
calling
the
different
migration
functions
or
doing
the
different
deployments.
I
want
to
speak
specifically
to
the
syntax
right
here
right,
so
the
first
thing
that
we're
doing
is
going
to
be
deploying
to
L1.
A
We
choose
a
network
which
I've
defined
in
a
truffle
config
and
by
default.
Actually,
you
know
know
what
stop.
This
is
really
hard
to
explain
until
I've
explained
something
else.
So
let's
pretend
that
never
happens
and
move
on
to
this
portion
right
here.
Okay,
travel
config!
This
is
the
last
part
for
configuring,
a
optimism
depth
right,
so
we
have
two
different
configs.
The
first
one
is
your
vanilla
config.
This
is
what
truffle
will
default
to.
If
you
don't
specify
a
network
or
a
config.
A
Essentially
all
it
does
is
Define
your
build
directories
whatever,
and
then
your
networks
I
want
to
note
one
thing:
the
default
would
just
be
like
a
build
to
normal
contracts,
but
in
this
case
we
have
due
to
two
different
types
of
contracts.
We
will
need
to
specify
the
build
path,
so
that's
build
slash,
ethereum
contracts
as
well
as
hey
Trestle,
where
do
I
even
what
contracts
do
I
use?
A
Well,
you
pull
it
from
slash
contract,
slash,
ethereum
and
then
here
is
just
identifying
the
network
and
as
always,
specifying
your
private
Keys
that
sucks,
but
I'm,
not
gonna,
show
you,
but
I
can
show
you
the
way
to
circumvent
it
later,
which
is
cool,
that's
a
sneak
peek
but
anyway.
So
that
is
what
our
truffle
config
looks
like.
Let's
move
back
into
our
migration
script,
now
that
we
understand
that
this
is
the
first
part
we're
using
our
first
truffle
config,
we
are
deploying
to
our
L1
on
the
network.
A
Girly,
like
I,
said
with
that
one
two
three
four
process:
we
actually
have
the
ability
to
specify
which
deployment
we
care
about.
In
this
case,
we
clear
about
the
first
one.
The
second
case,
if
you
notice
here,
we
are
choosing
optimistic
girly
as
the
network
we're
going
to
deploy
to
and
then
specifically
specifying
this
configuration.
So
that
way,
when
we
run
this
migration,
we
know
hey
we're
going
to
pull
our
contracts
from
the
optimism.
A
Folder,
hey
we're
going
to
pull
or
we're
going
to
build
everything
into
this,
build,
slash
optimism
and
again
kind
of
this
specification
of
whatever
and
then
skip
dry
run,
self-explanatory,
you're,
just
skipping
the
extra
part.
These
two
pieces,
as
well
I
want
to
do
know,
is
kind
of
anti-pattern.
I
am
sorry,
but
this
is
the
part
where
we
will
actually
be
calling
the
messages
on
each
contract.
A
So
if
you
look
in
the
actual
deployment,
you
can
see
right
here
we're
getting
the
instance
of
like
the
greeter
contract
on
the
other
L1
one
and
setting
that
greeting
typically
stuff
like
this,
where
you're
interacting
with
your
contract
might
exist
in
your
dap
or
in
a
separate
script.
Migrations
are
for
deployments,
I
just
put
it
there
to
show
you
hey,
you
can
put
four
migrations
in
right,
so
it
still
works,
but
don't
do
this
anyways
so
that
that's
the
structure
of
the
Truffle
box.
A
Let's
actually
now
talk
about
how
to
integrate
optimism
contracts
into
your
depth.
So,
let's
start
with
the
contracts.
This
is
the
transfer
data
section,
not
the
SDK.
So
optimism
has
already
deployed
this
example.
Contract
onto
their
various
test
sets
and
mainnet.
So
again
you
can
find
those
addresses
in
their
GitHub.
Essentially,
this
is
super
easy
all
it
does.
Is
this
contract,
which
does
a
version
exists
on
L1
and
a
version
exists
on
L2?
Has
a
function
set
grading?
A
So
if
you
set
the
greeting,
say
hello
and
you
call
contract.greet,
it
will
say
the
hello
that
you
had
put
in
there
cool
and
then
this
part
here
is
just
getting
the
appropriate
cross
domain.
Messenger
sender
address
so
these
each
of
these.
What
do
you
call
it
addresses?
Are
the
cross
domain
Messengers
solidity
file
that
exists
on
each
chain?
Id
I!
A
Guess
like
these
kind
of
don't
matter
because
all
of
it's
deprecated
but
doesn't
matter,
we
only
care
about
420
and
five,
and
then
this
is
kind
of
how
you're
going
to
get
the
actual
domain
sender.
So
the
OG
contract
that
you
care
about
so
that's
kind
of
the
base
contract
of
what's
already
deployed
now
say
we
want
to
create
contracts
that
interact
with
that.
So
we
have
this
greeter
which
exists
on
L1
again.
All
it
does
is
have
this
function
called
set
greeting.
A
So
if
somebody
calls
that
greeting
what
we
care
about
is
number
one,
the
message
this
is
how
you're
going
to
encode
that
message.
So
this
is
set
greeting
from
that,
whatever
message
you're
sending
in
and
then
specifically,
you
could
put
a
different
contract
address
here.
This
is
the
permanent
address
of
the
greeter
contract
on
the
L2.
So
essentially,
if
you
call
set
greeting
on
greeter
L1,
it
will
call
the
set
greeting
function
on
greeter
L2.
A
Hopefully
you
digested
that
L2
does
the
same
thing
again
talk
to
me
afterwards,
I
have
so
much
free
time,
anyways,
greeter
L2
does
the
same
thing
set
greeting
again
right
here
is
gonna,
be
calling
this
function
on
greeter
L1
and
telling
it
hey.
This
is
my
target
blah
blah,
oh
and
then
guess,
like
I
said
gas
limit
is
irrelevant.
A
We
have
up
to
1.92
million
gas
for
free
calling
stack
reading
on
optimism,
hopefully
I'm
gonna
say
100
does
not
take
1.92
million
guess
so
that's
where
we're
at
essentially
to
run
this
we
would
have
just
done
run
the
script
I'm
not
going
to
run
it,
but
you
could
see.
The
output
essentially
looks
like
this.
A
Where
it
will
compile
your
contracts
and
then
start
the
migrations
right,
so
this
is
the
first
one
where
we're
deploying
it
the
L1
contract
and
then
deploying
the
L2
contract
as
well
as
then
doing
the
the
fake
part
where
you
actually
call
the
greetings,
and
what
is
interesting
about
this
is.
It
is
calling
the
greeting
on
a
deployed
contract
on
the
girly
test
net,
as
well
as
the
optimism
girly
test
net.
So
what
can
we
do
when
that
happens?
We
can
go
to
etherscan
yay
and
and
see
it
in
action.
A
I'm
not
going
to
open
up
ether's
skin
I
took
a
screenshot.
That's
what
happens?
We
opened
up
one
of
the
contracts
on
etherscan
called
the
greeting
function
here,
so
it
says:
greetings
from
truffle
I
do
want
to
know
if
you
do
follow
this
tutorial.
Like
I
said
this
is
a
public
pre-deployed
address.
So
if
all
of
you
decide
to
follow
this
tutorial
afterwards
and
you
decide
to
change
the
greeting,
you
might
see
somebody
else's.
A
I
have
definitely
like
gone
to
this,
and
it's
like
all
in
Chinese
and
they're
like
wow
web3
is
global,
but
you
can
just
go
back
and
find
your
transaction
hash
in
the
history
and
then
be
able
to
read
whatever
you
had
specifically
decided
to
set
the
greeting
as
and
just
to
prove
to
you.
This
is
the
one
from
L2
setting
greeting
on
L1.
That's
what
it
looks
like
it
looks
the
same,
because
it's
basically
the
same
contract.
Where
are
we
moving
on
okay
cool?
A
Let's
talk
about
the
script,
so
this
is
complex
but
I'm.
Just
gonna
I,
don't
know
how
much
time
I
have
left
so
I'm
just
going
to
talk
faster
because
that's
my
style.
Okay,
so
here
is
basically
a
script
of
how
we
decided
to
use
the
SDK
I'm
going
to
point
out
a
few
important
parts
here
right.
So
the
first
part
is
pretty
self-explanatory.
A
We're
just
setting
up
all
the
things
that
we
need
to
get
our
cross
domain
sender
thing
set
up,
so
you're
going
to
need
assigner
for
each
L1,
which
is
L1
sign
or
L2
signer
as
well
as
here.
This
is
specifically
for
if
we
wanted
to
do
the
SDK,
withdraw
and
deposit
functions
for
the
erc20,
so
you're
gonna
have
to
pass
in
what
erc20
addresses
you
care
about.
A
Like
I
said
we
are
interacting
with
die
so
that
die
address
for
L1
address
die
address
for
the
L2
is
from
their
list
here,
and
so
you
can
find
it
it'll
say
like
chain,
ID
five
die
and
then
there's
the
address,
and
that
is
what
you'll
be
using
in
the
SDK.
If
you
specifically
want
to
do
die
wanted
to
die
okay
but
anyways
before
I
dive
into
the
functions
themselves.
Let's
actually
talk
about
what
this
is
going
to
do.
A
I
am
a
bit.
Frazzled
report
balances.
Okay,
this
is
just
a
helper
function.
All
it's
going
to
do
is
log
what
your
balances
are
for
your
or
your
eth
balance
or
your
die
balance.
This
is
just
for
tracking
purposes
in
the
script,
so
you
can
see
that
hey.
It
actually
transferred
wow,
good
job
optimism;
okay,
no
one
cleft
cool,
so
that
that's
kind
of
just
helper
methods
we're
going
to
actually
dive
into
the
deposit
function
so
specifically
to
deposit
each
super
simple.
A
You
just
call
deposit,
eth
and
then
put
it
on.
One
thing
to
note
here:
right
is:
there:
are
these
things
called
statuses,
so
the
problem
with
bridging?
Is
it
takes
time
to
move
back
and
forth?
How
do
you
know
when
it's
done
so
optimism
will
provide
different
types
of
statuses
to
allow
you
to
know
hey
when
it's
done
with
relay.
That
means
it's
been
properly,
I
guess
committed
or
posted
or
whatever.
A
A
So
again,
like
I
said
we
have
that
caveat
of
the
L2
optimism
standard
token
Bridge
needs
to
know
what
L2
address
you
are
interacting
with
and
specifically,
in
order
to
do
this,
you
need
to
give
approval
to
say:
hey
I
approve
that
we
are
using
this
L2
address,
because
if
you
had
given
it
a
random
address,
it
doesn't
understand
all
that
token
is
gone.
So
this
is
a
very
manual
step
that
you
have
to
take
in
order
to
complete
a
ERC
token
transfer,
and
then
we
go
into
the
withdrawal.
A
This
is
exactly
the
same
thing
between
the
two
I
just
want
to
call
out,
specifically
we've
added
in
a
new
status.
So
when
we
talk
about
going
from
L2
to
L1,
I
had
talked
about
that
thing
called
challenge
period
right
because
that's
when,
like
things
get
real
right,
it
goes
to
mainnet,
so
that's
kind
of
I'm,
just
logging
that
to
say
hey
I'm
in
the
challenge
period.
A
So
if
you
run
the
script
once
we
get
to
the
withdrawal
part
that
takes
a
lot
longer
than
the
part
where
we're
just
depositing,
because
we
have
this
part
where
we
have
to
wait
for
people
to
be
like
no
that's
wrong
or
yeah,
that's
right,
so
yeah
that
is
using
the
SDK.
Let's
move
on
into
actually
building
adapt
and
seeing
that
how
we
can
integrate
the
SDK
into
our
application.
Wow
I
did
so
much
live
coding
here
it
is
okay,
essentially
I'll.
A
Tell
you
two
things:
I
did
or
I
did
a
lot
more
things
on
two
things.
First
off
right
now
we
have
a
client
in
so
when
you're
building
like
a
full-end
app
you
probably
want
to,
but
no
not
probably
you
should
be
separating
your
folders
into
your
client
section
and
the
part
you
care
about,
which
is
your
contract
session.
So
essentially,
what
I
had
did
in
this
process
was
just
copy
paste,
all
the
relevant
smart
contract
or
truffle
code
into
this
truffle
folder.
A
We
didn't
need
any
ethereum
contracts
anymore,
because
that
was
for
the
greeter
example
I,
just
replaced
them
with
optimism
contracts,
so
this
is
specifically
just
a
optimism.
Nft
contract,
as
well
as
a
Marketplace
contract
that
handles
all
of
the
transfer
of
like
lists,
buy
Etc.
One
thing
to
note
here
is:
if
you
notice
nothing
really
looks
any
different
optimism
is
evm
equivalent.
So
when
you
start
writing
your
evm
or
optimism
daps,
you
can
pretty
much
copy
paste.
There
is
a
caveat,
though,
with
like
four
op
codes
that
are
a
little
different.
A
You
might
not
run
into
them,
I'm
not
going
to
get
into
it,
but
please
be
like
aware:
I'm
not
preaching
like
the
golden
standard
of
evm
equivalents.
It's
like
the
golden
minus
four
op
codes,
equivalent
of
evm
standards
anyways
in
this
case
right
so
now
we
actually
have
to
deploy
our
contracts.
I
hope
this
will
work.
This
is
the
part
that
I
wanted
to
say
was
really
cool,
so
I
don't
have
to
show
you
my
environment,
Keys.
A
A
Annie,
okay,
well,
anyways
dang.
This
is
loading:
oh
okay,
cool,
okay.
So
it's
committed
to
my
oh
man.
This
is
going
to
take
a
long
time.
How
much
time
do
I
have
left
it's
11
30.,
oh
dang,
I
finished
all
this
in
30
minutes
wow.
We
have
20
minutes
for
questions.
Okay,
sorry,
I'm!
So
surprised
it's
not
connecting
okay
I'm
just
going
to
explain
what
would
have
happened
here
right
so
essentially,
oh
actually,
I
never
deployed
it.
That's
why
nothing
has
happened.
Let
me
go
backtrack,
so
truffle
dashboard.
A
This
is
usable
with
any
project.
If
you
notice
it
is
open
up
on
localhost,
24012
I'm.
Sorry
I
see
someone
squinting
in
front
of
me
yeah
whatever.
Where
is
it?
It
opens
up
on
24012.
So
if
you
are
using
like
a
hard
hat
config
for
example,
the
way
you
do
it
is
you
just
specify
one
of
your
networks
as
dashboard
and
that
Local
Host
and
it
will
open
up
this
UI.
Specifically
what's
cool
about
this
here.
A
A
And
I
think
that's
it.
I
do
want
to
know
as
part
of
this
box
that
we
have
provided
like
npm
scripts,
that
you
can
just
run,
but
I
always
forget
what
they
are
dang.
Where
am
I
I,
don't
know,
I,
don't
remember
what
I'm
doing
here.
What
is
wrong
here
cannot
find
thought.
Oh
did
I
not
migrate.
It
in
oh
did
I
spell
it
incorrectly.
Guys
did
I
spell
it
incorrectly.
A
A
Please
check
that
your
ethereum,
oh,
this
is
my
Local
Host
died.
Oh
I
did
I
did
oh
I
did
this
on
purpose,
so
you
guys
know
how
to
use
it.
Joke's
on
you,
you
thought
I
didn't
know
what
I
was
doing.
I
do
because
I
work
for
trouble.
Okay,
so
I
think
it's
connected
now
and
okay,
no,
what
happened
here!
Oh
I
heard
someone
like
trying
to
suggest.
Like
hey,
you
just
opened
a
new
terminal.
That's
why
it's
not
working!
Okay,
compiling
your
contracts,
nice,
okay,
oh
wow,
fancy!
Oh.
A
I'm
so
happy
clapped
without
me:
coercing
you.
This
is
awesome,
okay,
cool
and
then,
if
you
notice
here
actually
I
did
want
to
point
out
in
this
migrations
contract
we
are
deploying
both
of
them.
The
marketplace.
Contract
is
dependent
or
sorry.
The
nft
contract
is
dependent
on
the
marketplace.
Contract
I
did
that
specifically,
because
when
we
mint
and
transfer
nfts,
you
need
to
add
approval
for
it
to
do
that.
A
A
It
is
a
next
JS
project,
just
kind
of
the
steps
to
do
that
would
just
be
like
a
create
next
app
and
then
I'm
using
Tailwind,
because
I
suck
at
CSS,
so
that's
like
in
it
Tailwind
I
have
instructions
somewhere
I'm
not
going
to
show
you
I'm
going
to
blame
it
on
the
Wi-Fi
again.
But
essentially
what
that
looks
like
is.
We
have
a
bunch
of
different
pages
and
I
think,
because
this
is
going
to
be
local.
A
I
can
just
actually
just
do
this
cool
wow
local
development
is
so
good
if
only
there
was
something
called
ganache
forking
that
could
fix
this
okay
anyways.
So
this
is
kind
of
like
the
different
views
that
we
have
and
I
want
to
talk
specifically
about
the
Gurley
Bridge,
so
I
embedded
it
here.
What
does
this
actually
look
like
in
terms
of
code
right?
A
Let's
say
split
left,
so
all
we
cared
about
in
that
bridge
was
transferring
East
between
the
two
right.
So
if
we're
here
on
the
Gurley
Bridge,
here's
all
the
gross
HTML
stuff
that
I
hate,
because
I
was
never
a
front-end
Dev,
but
we
have
two
things:
we
care
about
right,
depositing
eat
and
withdrawing
eth.
A
So
if
we
look
at
the
deposit
each
function
here
and
the
positive
function
here,
don't
they
look
almost
the
same
yeah
wow,
very
cool,
I
copy
and
pasted
that
except
added
some
other
things
that
you
need
because
State
matters
and
whatever.
But
you
get
what
I'm
saying
right.
It's
exactly
the
same
right
and
the
same
thing
with
withdrawal
ease
here
as
well
or
I.
Don't
know
where
it
is.
A
Eve
yeah
and
it
looks
virtually
the
same
as
well.
The
only
piece
I
took
out
here
is
going
to
be
report
balances
as
part
of
my
UI
I
pulled
that
out
into
just
to
get
L1
East
and
a
get
L2
East
specifically,
so
that
we
could
demonstrate
this
information
right
here,
I'm,
not
I,
guess
we
could
try.
Okay,
well,
everyone
pray
for
me.
Why
did
I?
Do
this
inspect
console?
A
Okay?
So
if
I
do
something
like
0.001
I
deposit,
you
can
see
like
the
console
stuff
that
I
had
before
was
damn
it.
Oh,
this
is
something
yeah.
Okay,
sorry
I
forgot
to
configure
some
stuff,
so
let's
pretend
I
configured
everything
properly
and
then
it
understands
the
RPC
URL
and
everything,
but
I
have
a
screenshot,
and
that's
all
that
matters
so
and
we
did
everything
correctly.
This
is
what
it
looks
like,
and
this
specifically
is
the
version
of
like
moving
it
from.
Oh,
that's
highlighted
in
blue
awkward,
okay
anyways.
A
This
is
the
part
where
we're
migrating
over
optimism.
Gurley
eth
over
to
Gurley
East
I,
do
want
to
note
one
thing
actually
now
that
I
remember
when
you're
moving
from
L2
to
L1-
and
you
remember
I
said
it's
like
more
expensive
because
you
have
that
double
transaction
right.
So
in
the
script,
when
we
move
it
over,
we
actually
add
a
little
bit
more
Ethan.
We
directly
are
transferring
because
otherwise
that
would
be
burned
as
part
of
the
process
and
you
would
probably
actually
lose
eth.
So
that's
one
thing
to
notice,
but
anyways.
A
This
is
when
I
did
everything
correctly
this
morning
and
it
failed
now,
but
that's
what
it
looks
like
and
that
is
I
think
our
full
depth.
How
much
time
do
I
have
left
wow
good
job,
Emily
I
have
20
minutes
left,
so
we
can
talk
about
what's
next,
so
what's
next
a
crash
course,
and
what's
next
just
kidding,
that
is
not
the
definition
of
a
crash
course.
So
we're
just
gonna
talk
about
it.
I
went
through
this
really
fast
right
and
this
was
like
the
nft
marketplace.
A
Utilizing
the
SDK
scripts
I
would
challenge
you
guys
to
actually
take
this
information
and
build
something
you're
on
your
own
right.
So
maybe
like
a
chat
messenger
between
L1
and
l2s
right,
because
you
can
transfer
that
data.
In
this
case
you
will
be
needing
the
Truffle
stuff
to
be
deploying
information
back
and
forth.
A
Alternatively,
like
it
only
does
eth
right
now,
only
on
Gurley,
you
can
configure
it
basically
to
select
the
network
and
then
always
like
I
was
talking
about
optimism,
because
that's
what
we
have
we
have
other
L2
boxes
specifically
arbitrim
exists
right
now.
What's
in
the
works
is
actually
a
stark
net
box,
which
is
super
cool.
A
How
is
truffle
working
with
a
non-evm
compatible
language
I,
don't
know
we'll
find
out
that's
in
the
future,
but
it's
happening
and
it's
exciting
and
then
just
in
general
I
want
to
talk
about
what
our
plans
are
for
multi-chain.
So
again,
like
I
said:
multi-chain
dapps
are
hard,
complex,
I
said
a
lot
in
40
minutes,
I,
don't
know
how
I
did
that.
But
what
are
some
kind
of
pieces
that
we
thought
was
difficult
about
our
demonstration
that
we
are
fixing,
so
first
thing
is
declarative
deployments.
A
So,
if
you
remember
in
that
scripting
portion,
it
was
very
simple:
I
just
had
an
L1
and
an
L2
right,
but
imagine
if
now
things
were
dependent
on
each
other's
addresses
or
now
we've
introduced
like
a
new
L1
or
a
new
L2.
These
scripts,
like
in
production,
can
get
really
intense
and
that's
hard
to
maintain.
A
So
declarative
deployments
is
essentially
you
saying,
like
I,
have
a
Json
or
a
yaml
file,
we're
still
figuring
out
the
actual
structure
of
it
yet,
but
you'll
say
like
this
is
kind
of
what
I
wanted
to
look
like
and
then
truffle's
like
wait,
I'm,
so
intelligent
I
can
do
it
for
you
and
and
that's
kind
of
how
it
goes
and
along
those
lines
of
what
comes
with
development.
Declarative
deployments
is
being
able
to
declare
environment-based
configurations.
A
So
again,
if
you
remember,
when
I
was
talking
about
the
network
configs,
it's
just
like
a
bunch
of
lists
of
like
girly
mainnet,
sepolia
Etc,
but
what
if
you
could
actually
bundle
those
up
into
your
own
environment,
so
you'll
say
I
care
about
these
networks.
Only
in
testing
I
care
about
these
networks
only
in
production,
instead
of
doing
like
a
truffle
migrate
and
specifying
every
single
Network,
you
could
just
say:
truffle,
migrate,
testing,
environment
and
that's
how
you
would
get
there.
A
So
that's
pretty
cool
ganache,
plugins
I'm,
actually
probably
the
most
excited
about
this,
because
the
Wi-Fi
was
bad
here.
It
would
have
done
everything
locally
right.
So
the
reason
I
had
to
go
on
Gurley
and
optimism.
Girly
is
because
we
were
interacting
with
pre-deployed
contracts.
So
if
you
do
like
vanilla,
mainnet
I
mean
ethereum
development.
Right
now
we
do
have
forking
right
where
you
can
basically
copy
the
state
of
the
chain
main
neck
early.
A
A
All
of
those
pre-deployed
contracts
were
actually
also
copied
locally
because
of
the
forking
and
I
could
have
just
done
this
all
on
localhost
and
because
it's
not
on
localhost
ganache
is
compatible
with
our
other
development
environments.
So
again,
I'm
here
to
say
we
do
not
require
you
to
work
with
other
or
be
married
to
truffle
itself
we
are
coopetition
is
what
I
call
it
and
the
last
thing
I
think
in
a
caveat
of
this
so
many
times,
I
am
not
an
expert,
but
we
are
bringing
on
an
expert.
A
So
if
you
don't
know
I
do
this
weekly
live
stream
called
web3
Unleashed,
where
I
basically
say
hey
I'm
interested
in
this
who
do
I
know
or
can
I
figure
out
will
teach
me
about
it,
so
we're
bringing
Annie
she
does
like
partnership.
Protocol
Partnerships
with
optimism
to
come
talk
a
bit
a
little
bit
more
about
bridging
security
and
then
specifically,
if
you
guys
don't
know,
optimism
had
like
a
huge
announcement
about
like
Bedrock
changes.
I
don't
know.
What's
in
it,
Annie
will
tell
you,
but
this
is
coming
up
on
November
3rd.
A
It
will
be,
what
do
you
call
it
recorded?
So
you
don't
have
to
join
live
if
you
don't
want
to,
but
that
is
everything
so
thank
you
so
much
for
joining.
Follow
me
on
Twitter.
That
is
a
QR
code
to
more
of
links
that
are
important
to
me.
Man
I'm,
so
scared,
I'm,
not
ready
for
13
minutes
of
questions,
usually
I
just
take
the
full
60
minutes
and
then
run
so
if
you
have
any
questions
about
this,
my
life,
okay,
yes,.
A
The
question
is
it
possible
to
call
the
concerts
to
another
and
between
l2s
and
l2s?
Okay,
I,
don't
work
for
optimism,
so
I,
don't
know
I
my
guess
and
I'm
gonna.
Actually
I'm
gonna
write
this
down,
so
I
can
ask
Annie.
My
guess
is
probably
no
because
we
are
interacting
with
those
pre-deployed
cross-chain
Messengers,
and
that
is
what
is
doing
like
the
communication
right.
So
maybe
they
have
deployed
ones
on
other
l2s.
A
The
L2
Space
is
really
crowded
and
they're
fighting
each
other,
so
I
don't
know
if
they
would
actually
do
that
which
is
antithetical
to
the
spirit
of
ethereum
but
yeah
that
that's
my
guess.
Let
me
write
this
down.
Oh
my
God,
my
notes
are
so
messy
where's.
My
phone
I'll
write
it
on
my
phone,
so
you
guys
don't
see
it.
Oh
shoot,
where's
my
phone
okay,
I'll
just
remember
in
my
head,
but
yeah
cool.
Do
we
have
any
other
questions?
Yeah.
A
A
A
A
Oh
like
when
should
we
use
L1
versus
L2
I
guess,
my
specific
thing
is
like
I
think
l2s
are
the
future
of
ethereum.
The
problem
with
l2s
like
I
had
mentioned,
is
probably
the
ux
problem,
as
well
as
the
adoption
problem.
So
when
we
are
building
like
say
your
first
step
right,
the
biggest
kind
of
cohort
of
people
you
could
take
on
is
probably
going
to
be
just
mainnet
or
ethereum
development
right.
A
But
if
you're
trying
to
do
like
plan
ahead
and
stuff,
you
know
I'm
thinking,
layer,
twos
are
important.
Okay,
let
me
let
me
backtrack.
Let
me
just
talk
about
what
I
would
think
about
when
I'm
choosing
where
to
develop
right.
So
it's
who
is
my
audience?
How
big
is
that
right?
The
second
piece
is
Dev
support.
If
I
am
building
this,
how
good
is
that
layer
two
at
providing
support?
How
good
is
their
documentation
stuff
like
that,
and
then
the
third
piece
is
also
just
like
general
adoption
be
of
developers
right.
A
So,
if
you
look
at
that
space,
is
there
anyone
who
can
even
code
with
you?
Is
there
anyone
you
can
build
with
and
layer?
Twos
are
new
right,
and
so
there
is
going
to
be
some
trade-offs
there,
but
it's
kind
of
what
you
want
to
do
in
the
future.
I
know
optimism
is
doing
really
cool
stuff
with
promoting
L2,
dapps
and
I.
A
A
A
I
I,
don't
think
it
would
change
in
the
sense
that
if
you
want
to
interact
with
like
a
layer,
two
like
a
zero
knowledge,
roll
up
right,
you
still
care
about
where
those
contracts
are
coming
from,
so
that
build
directory
is
still
important.
The
network
IDs
are
still
going
to
be
different,
where
you're
deploying
to
so
all
this
different
configuration
is
going
to
change.
A
Actually
I
did
mention,
so
we
have
Stark
net
is
zero
knowledge.
We
are
working
on
a
ZK
sync
integration
as
well,
which
is
also
zero
knowledge,
so
I
think,
regardless
of
where
you
choose
to
go,
this
is
going
to
be
a
configuration.
You
still
need,
unfortunately,
but
I
think.
Hopefully,
if
you
have
submission
or
like
what
do
you
call
it
suggestions
whatever
like
we're
open
source?
Why
don't
you
just
contribute
to
our
code
base
or
create
an
issue?
We
have
GitHub
discussions
as
well
during
our
Discord
Community.
A
A
A
Wow
we're
getting
professional
like
personal
here,
dang
okay,
we
have
seven
minutes
to
answer
questions
about
Emily,
Lynn.
Okay,
why
did
I
choose
to
go
into
devrel
versus
you
know,
be
a
core
developer!
That's
a
great
question!
So
if
you
want
to
talk
a
bit
about
my
background,
so
I
graduated
college
with
a
CS
degree,
I
went
immediately
into
back-end
development.
I
did
that
for
like
two
years
and
then
was
like.
Oh,
this
is
kind
of
boring.
What's
cool
and
fancy
and
I
was
like
wow
devops
is
such
a
sexy
word.
A
It
is
the
worst
word
ever
I
hate
kubernetes,
but
anyways
I
moved
into
devops,
right
and
I.
Think
I
was
so
I'm
in
my
20s
I.
Don't
know
why
I'm
getting
into
this
tangent
but
I
was
kind
of
in
that
space
of,
like
figuring
out
I'm,
not
totally
satisfied
with
my
job.
Part
of
the
reason
I
moved
into
devops
was
one
thing.
It
was
sexy
at
the
time,
but
like
also
like
I
really
wanted
to
learn
something
new
right
and
I
haven't
got
to
the
devrel
portion
of
it.
A
You
know
what
I
mean,
and
the
second
piece
was
the
thing
I
enjoyed
the
most
about.
My
engineering
job
was
the
cross-collaborative
communication
when
I
got
to
kind
of
background
wise.
So
my
when
I
joined
the
devops
team,
we're
really
focused
on
reaching
sock,
2
compliance
and
security,
so
I
was
working
very
closely
with
a
security
team
and
so
being
able
to
translate
technical
Concepts
on
our
side
to
other
team
members
was
something
I
really
enjoyed
and
knew
I
wanted
to
take
into
the
next
job.
A
So
when
I
was
considering
my
different
options,
developer
relations
came
up
and
I
thought
it
was.
This
perfect
marriage
of
I
get
to
keep
my
technical
skills.
I
am
required
to
learn
something
new
all
the
time.
So
that's
why
I'm,
not
an
expert
in
anything,
obviously
but
I,
know
know
a
little
bit
about
everything
and
I
think
that
is
something
I
really
liked
and
then,
in
terms
of
the
impact
part
just
being
able
to
interact
with
devs,
like
my
job
is
figuring
out
like
what
people,
what
pain
points.
A
People
have,
what
they're
working
on
et
cetera
and
like
trying
to
fix
that
like
felt
more
tangible
to
me
right
and
I.
Think
that's
why
I
kind
of
fell
into
devrel,
I'm
going
to
say
one
more
thing
and
I
always
say
this
and
she's
in
this
room
and
she
hates
that
I
say
this.
My
sister
actually
started
in
devrel
first
and
then
also
works
in
devrel
in
web.
A
Three
yeah
wow
crazy
and
she
is
like
one
of
the
biggest
Inspirations
in
my
life,
and
so
maybe
that's
part
of
my
motivation
as
well
or
maybe
I'm,
just
like
the
bratty
little
sister,
I
I
think
my
tagline
is
like
do
everything
she
does
but
better.
So
so,
maybe
that
that's
also
why
I
got
into
devrel
cool
I,
don't
know
if
we
have
any
more
time.
We
have
oh
God,
four,
more
minutes,
dang
it.
A
Okay,
otherwise
feel
free
to
go,
wait
in
line
for
other
talks
or
come
catch
me
wherever
yeah
I
mean
I'll,
be
at
like
the
conference
I'll
be
at
near
con
consensus,
which
truffle
works
for
is
gonna,
be
having
a
event
this
Friday
so
feel
free
to
stop
by.
We
have
a
lot
of
different
panels
and
things
like
that,
yeah
cool.
Thank
you.
So
much.