►
From YouTube: Peep an EIP #8: EIP-2848 with Giuseppe Bertone
Description
EIP-2848: https://eips.ethereum.org/EIPS/eip-2848
Slides from the video: https://docs.google.com/presentation/d/1AuUsn4LuvmDEIWOmmIIiQwno_9QXkp4PWo4CzB_8S5g/edit#slide=id.p
GitHub: https://github.com/InternetOfPeers/EIPs/issues/1
Follow at Twitter:
Giuseppe Bertone @GiuseppeBertone | Pooja Ranjan @poojaranjan19 | William Schwab @William94029369 | Alita Moore @alitamoore85
Watch an episode on other exciting proposal in Peep an EIP: https://github.com/ethereum-cat-herders/PM/projects/2
Contact Ethereum Cat Herders
Discord: https://discord.gg/sgdnxZe
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
GitHub: https://github.com/ethereum-cat-herders/PM
Email: support@ethereumcatherders.com
Website: https://www.ethereumcatherders.com/
A
A
This
is
basically
a
standard
track
erc
created
in
august
this
year,
so
it's
like
straight
out
of
the
oven
proposal,
recently
added
as
a
draft
and
is
looking
for
your
attention
available
to
help
with
your
project.
So
without
further
ado,
let
me
pass
it
to
the
author.
Please
let
us
know
a
little
bit
about
yourself
and
then
we'll
dive
into
the
proposal.
B
B
Bad
blockchains,
like
order
and
viper
ledger
fabric,
but
for
for
work
so
that
I'd
like
to
to
try
to
participate
in
the
community.
So
I
find
many
pr's
to
clients
like
ethereum,
parity
and
so
on,
and
I'm
still
learning
and
I
like
to
achieve
some
some
result
in
this
in
this
field.
So
you
can
find
me
around
the
web
in
many
in
many
places
like
github
linkedin
stock
exchange.
So
if
you
want
to
contact
me,
don't
hesitate
and
that's.
B
It
so
I
I
can
start
with
the
with
the
the
why
so,
since
maybe
the
why
I
I
try
to
do
this
standard
essentially,
I
think
that
we
must
start
from
some
pain
points,
so
I
think
that
sharing
ideas
and
opinions,
it's
still
difficult
to
be
to
be
done
and
it
is
still
very
dependent
on
centralized
services.
So
this
kind
of
dependency.
B
Led
to
some
unreliable
ability,
sorry,
some
non-censorship
resistant
services
and
lack
of
single
source
of
truth
and
another
thing
I
another
thing
that
I
find
very
difficult
to
achieve
is
understand
when
a
message
comes
from
a
specific
author
and
essentially
it
is
updated
and
it's
not
not
valid
anymore
message,
so
the
the
the
the
word
trustless.
I
hope
that
I
want
is
a
word
when,
where
I
for
as
a
developer,
I
can
easily
talk
with
my
user
base.
B
That
is
not
the
case
actually
now
and
I
have
control
of
my
reputation
so
when
I
say
something
I
want
the
others
understand
that
it's
set
by
me
and
it's
not
something
modified
in
any
in
any
manner
and
as
a
user.
I
want
to
easily
verify
this
kind
of
things
and
I
want
to
easily
share
my
thoughts
even
not
as
a
developer,
maybe
as
a
journalist
or
an
author
or
anything,
and
I
want
to
control
my
content.
B
So
I
don't
want
other
platform
to
be
able
to
block
my
contents
or
don't
let
the
others
see
what
I
think
they
we
shouldn't
see.
Okay,
so
we're
gonna
call
sorry
mom,
it's
the
the
the
chrono
understander.
It
is
meant
to
be
a
standard
to
create
the
hero.
Your
very
own
public
always
updated
unstoppable,
verifiable
message
board
so
essentially
how
it
works.
There
are
two
main
parts
of
the
of
the
standard.
The
first
one
is
the
the
part
on
the
blockchain,
essentially
an
ordered
list
of
messages.
B
B
In
this
way
you
fill
essentially
the
blockchain
with
a
list
of
operation
and
oops.
I
think,
and
the
other
client
can
read
this
operation
and
create
a
local
index
of
your
updated
messages.
This
kind
of
operation
can
be
done
in
a
very,
very
easy
way
and
they
are
very
cheap.
So
essentially,
if
you
think
that
the
base
transaction
is
21
000,
yes,
you
had
only,
for
example,
for
an
ad
operation
with
the
256
multi-you
had
only
548
guests.
B
B
The
second
part
of
the
of
the
of
the
protocol
states
that
you
essentially
need
to
store.
If
you
want
the
the
content
in
some
persistent
service
where
you
can
then
lead
your
users
to
get
the
content
from
so
I
I
suggest
you
use
the
content
addressable
network
like
ipfs
or
swarm,
but
because
the
client
knows
the
ash,
the
content
you
can
share
with
them
the
content
with
any
other
services,
even
centralized
one
like
os,
s3
or
onedrive,
and
so
on.
B
You
here
you
can
see
the
a
summary
of
the
specification
that
you
can
read
in
fully
on
the
on
github,
but
essentially
I
want
to
mention
the
the
data
structure
that
you
can
see
here.
The
address
that
you
send
the
transaction
to
is
must
be
the
same
as
the
sign
as
you
essentially
so
this
is
a
self
transaction.
The
it
must
be
zero
way.
B
This
is
important
because
this
standard
must
be
simple
and
must
avoid
the
as
much
as
possible
scans
that
can
give
that
can
lead
you
to
think
that
you
are
sending
some
money
to
yourself.
So
it's
not
a
problem,
but
so
it's
a
it's
good
to
have
this.
This
kind
of
constraint
and
the
data
is
at
least
two
bytes,
because
the
first
one
is
the
operation
code.
The
second
one
can
be
parameters
and
the
row
option
is
the
the
least
expensive
one.
But
it's
not.
B
It's
particular,
then
we
will
talk
then
about
that.
So
this
is
a
very
simple.
This
is
a
very
simple
data
structure
and
it
is,
it
is
intended,
and
it
is
intended
that
any
transaction
that
don't
strictly
adhere
to
this
constraint,
it's
considered
invalid,
okay
and
the
content
part
we
could
that
later.
But
essentially
you
have
two
kind
of
comments:
the
core
commands
and
the
extended
commands.
B
This
is
done
because
the
specification
want
to
be
as
easy
to
implement,
so
you
can
implement
the
core
commands
and
release
your
your
client
and
then
you
can
add
extending
command
later,
for
example,
and
here
you
can
see
the
basic
functionality
that
you
can
imagine
when
you
share
some
messages,
so
you
can
have
the
some
content.
You
can
update
some
content,
you
can
reply
to
content
of
other
and
you
can
delete
some
command
some
content.
B
B
B
You
need
to
have
some
switch
off
function
that
says
to
others.
I
I
don't
trust
anymore.
This
kind
of
account
please
stop
and
maybe
use
other
okay,
so
the
client
must
in
your
any
other
operation
that
comes
after
this
comment.
So
it's
one
time
and
their
operation,
it's
because
maybe
you
don't
want
to
use
this
kind
of
content
type
to
keep
it
simple
and
to
have
something
that
that
works
from
the
beginning.
B
B
Okay,
in
the
in
the
version
two
of
the
of
the
standard,
I
thought
to
introduce
a
smart
contract
that
let
you
define
the
new
content
type
and
new
operations
of
the
meaning
of
the
operation,
but
in
the
first
place
you
need
to
stick
to
this
to
this
specification
and
the
extended
commands
are
for
what
can
be
seen
as
a
the
the
beginning
of
something
that
is
more
social.
So
you
need
you
start
giving,
for
example,
endorsement
to
other
messages.
B
So
this
is
because,
while
developing
the
this
kind
of
standard,
I
I
felt
that
that
they
need
to
talk
with
someone
that
I
don't.
I
don't
know,
but
I
find,
for
example,
some
smart
contracts
that
are
wrong
or
some
others
that
acting
in
that
acts
in
some
strange
behavior,
and
I
want
to
talk
with
them
in
some
way,
and
currently
I
cannot
do
that.
B
So
this
is
a
way
to
say
hey
if
you
are
listening
to
this
kind
of
standard
and
I
can
send
a
message
and
you
can
respond-
maybe
not
necessarily
on
on
the
blockchain.
This
is
the
the
summary,
and
here
you
can
see
an
example
of
a
payload
where
you
can
see
the
the
first
height
is
the
command
and
the
rest
is
the
multi-ash.
B
Mustache
is
very,
very,
very,
very
useful
in
this
case,
because
you
don't
need
to
stick
with
a
single
hashing
function,
but
you
can
do
it
dynamically,
and
these
two
bytes
essentially
are
saying
this
is
a
sha
256,
hashing
algorithm
and
the
ash
is
32
bytes.
So
you
can
read
the
other
30
bytes
and
you
have
the
edge
of
the
of
the
content,
and
this
is.
B
B
I
have
also
yet
some
some
function
to
implement,
but
I
want
to
show
you
the
basic
functionality,
so
you
have
a
very
I'm,
not
a
designer,
so
this
is
a
very
basic
implementation,
but
essentially
I
have
run
I'm
running
two
nodes,
one
ipfs
in
local
and
one
get
in
girly
network,
and
it
is
very
important
to
use
your
own
notes.
Please-
and
so
you
can
see
here
that
I'm
connected
to
that
and
you
can
change
settings
and
so
on.
B
But
what
is
important
here
is
that
you
have
an
operation
list
and
a
message
list
so
here
the
client
has
already
scanned
my
my
transactions
that
you
can
see
on
the
nearly
network
here.
So,
as
you
can
see,
it
is
kind
of
already
recognized
in
some
way
this
kind
of
transactions,
so
the
step
to
implement
this.
B
This
specification
is
really
really
really
fast,
and
here
you
can
see
the
various
the
different
operations
that
I
done
in
the
in
this
network,
so
because
there
is
not
a
smart
contract
to
implement
this
kind
of
standard,
you
can
use
it
already
in
any
kind
of
network,
so
you
can
switch
between
main
network
girly,
carbon
and
so
on.
Without
any
problem-
and
here
we,
for
example,
you
can
create
an.
B
B
Okay-
and
so
I
can
see
here
that
the
transaction
is
waiting
and
when
it's
done,
I
will
have
my
message
in
the
message
list,
so
I
can
essentially
do
this
and
I
can
modify,
for
example,
the
current
message
bye,
bye,
bye.
I
think
it
was
three
bye,
so
you
can
see
this
and
I
publish
an
update
so
again
it's
on
the
ipfs
and
I
can
send
a
transaction
okay
to
update
that
content
also.
So
this
is
the
the
the
idea
and
that
this
is
already
working.
B
Sorry
this
window
is
on
away
and
these
also
support
and
different
accounts.
So
if
I
switch
the
account
or
the
network,
the
client
already
knows
that,
and
so
I
still
need
to
implement
the
dynamic
loading
of
this.
But
okay,
so
here
you
can
see
that
my
messages
are
now
updated.
So
everyone
can
see
that
I
want
to
share
this
kind
of
messages
and
to
check
they
only
need
to
find
in
some
way.
In
this
case
is
it's
very.
B
B
This
is
not
my
message.
I
can
get
the
the
id
from
any
other
sources
and
ask
to
download
that
content,
so
I
can
see
here
that
the
content
is
downloaded
correctly,
so
just
thinking
time.
So
what's
next,
this
is
not
still
the
version
one
of
the
of
the
client,
but
I
I
try
to
work
on
that
in
my
spare
time,
so
it's
not
fast,
but
I'll
complete
him
sooner
or
later,
and
this
is
what
I
think
can
be
a
a
roadmap
for
this
kind
of
project.
B
I
would
like
to
send
a
pr
to
metamask,
so
it's
even
easier
for
users
to
send
this
kind
of
messages
and
having
these
on
wallets
is
really
really
useful
in
this
case
and
the
the
the
real
turning
point,
I
think,
is
if
some
explorer
in
particular,
I
think
it
has
kind
of
the
best
explorer
we
have
in
the
ethereum
community
now
can
support
this
kind
of
standard.
I
think
the
the
step
is
really
it's
really
easy
to
do.
B
Maybe
maybe
I
can
talk
later,
but
what
we
lack
we
lack
essentially
is
events
for
addresses.
So
now
I
cannot
listen
to
easily
listen
to
something
really
easy.
That
sounds
really
easy,
so
how
many
transactions
are
an
account
is
doing
or
if
someone
send
money
to
some
other,
I
cannot
listen
to
them.
I
need
to
create
a
another
program
that
reads
the
the
the
the
client
constantly
and
then
create
something
separate
from
the
index
of
the
the
client
this,
because
essentially
it's
it's
storage
consuming
this
kind
of
operation.
B
So
I
I
hope
that
I
can
find
some
way
to
create
this,
this
improvement
and
then
let
the
user
enable
that
with
the
flag.
Okay.
So
if
you
want
to
index
some
transaction
from
some
address,
you
can
do
it
inside
the
the
client
and
not
be
in
another
another
program
outside
and
the
last
thing
is:
if
all
this
goes
well,
the
next
step
will
be
to
have
a
smart
contract
that
let
you
define
what
the
meaning
of
that
comments
and
define
the
the
media
type.
You
support.
B
So
this
now
the
the
standard
is
forced
by
the
consensus.
So
everyone
need
to
agree
what
the
the
specific
comma
means
and
everyone
need
to
agree
on
the
content
in
particular
markdown,
for
example,
in
the
step
two,
you
don't
need
to
agree,
because
you
are
choosing
your
comments
and
you
are
choosing
your
content.
So
if
I
want
to
read
your
messages,
I
must
I
are
adhere
to
your
standard,
not
the
common
one.
Okay,
so
this
is
a
bit
more
complicated,
not
so
complicated,
but
a
bit
more
complicated.
B
B
B
I
think
that
is
a
you.
We
will
have
an
immediate
benefit
for
the
community.
The
technology
is
already
there.
So
you
do
not.
You
don't
need
to
invent
anything
complex
and
because
the
centralized
finances
is
coming
and
it's
rushing
and
scams
again
becomes
more
and
more
common.
I
think
that
we
need
an
easy
and
efficient
method
to
verify
who
thinks
who
save
what?
Okay
and
also
you
can
create
a
lot
of
memes
about
mom.
B
B
You
already
have
the
information
when
you
send
the
transaction,
so
a
smart
contract.
In
this
case,
it's
only
a
cost
in
gas
that
is
not
needed,
so
sending
transactions
is
even
is
very,
very
much
cheaper.
So
if
you
need
only
to
set
a
state-
and
you
don't
need
to
do
anything
with
that
state-
you
don't
need
a
smart
contract.
B
A
developer
creates,
for
example,
smart
contract
that
sends
all
just
events,
for
example,
even
that
I
think
it's
not
efficient,
because
again
you
send
a
transaction
in
the
blockchain
that
that
you
fire
again
the
same
exact
data.
So
you
are
duplicating
data
inside
the
recipient,
so
I
don't
think
it's
an
extra
way
to
do
that
so
yeah
and
also
you
cannot
do
mistake,
because
if
you
have
a
smart
contract,
you
need
to
trust
that
address.
So
someone
will
need
to
tell
you
that
that
is
the
smart
country.
B
B
So,
no
way
to
do
mistakes
in
that
kind
and
again
I
already
said
that,
with
the
smart
contract
we
will
come
in
the
version
2,
but
not
for
storing
messages,
and
another
question
that
I
have
come
through
is
the
batches,
so
it
sounds
very
inefficient
to
store
a
single
ash
for
a
single
message.
So
someone
says
why
don't
you
store
a
batch
of
messages?
It
is
a
quite
not
so
easy
to
to
respond,
but
essentially,
if
I
use
batches,
I
need
to
give
a
structure
to
the
content.
B
If
I
give
a
structure
to
the
content,
it
means
that
the
client
cannot
understand
the
state
of
my
board
without
downloading
the
content.
Okay,
so
it's
not
a
good
way
to
do
it
because
you
can
create
loops.
So
I
can
continue
to
download
the
things
and
never
reaching
a
final
state
and
I'm
forced
to
download
the
content
to
understand
the
state.
So
this
is
not
what
I
want
to
do,
and
so
there
is
a
this
is
the
reason
why
all
the
all?
B
The
information
that
you
find
on
the
blockchain
must
be
enough
to
understand
the
the
the
state
of
your
message
board,
and
this
is
why
you
can
send
only
one
message:
okay,
this
is
not
meant
anyway,
to
be
a
chat
system
like
telegram
or
whatsapp
or
whatever
it
meant
more,
like
a
blog
or
something
that
you
share.
That
has
value
because
you
are
paying
for
that
message.
B
C
Well,
actually,
it's
very
nice
that
you
ended
with
that
line,
use
only
nodes
under
your
control.
Before
also
you
talked
about
the
importance
of
running
your
own
node.
Is
that
also
necessary
for
eip
2848,
or
are
you
saying
that
as
a
general
security
concern,
or
maybe
I'll
even
speak,
that
out
a
bit
more?
If
I'm
using
infira
or
something
like
that,
and
I
sent
a
message
using
mom?
C
B
There's
not
a
really
security
issue
here,
because
you
are,
you
are
only
sending
some
transaction
that
is
signed
by
you
and
is
as
a
specific
nuns,
so
the
the
the
the
the
bad
things
that
can
happen
is
that
they
don't
relay
your
message,
but
that's
it
so
the
if
you
see
that
those
services
that
service,
in
particular
in
fura
or
other
services,
don't
relay
your
your
transaction.
You
can
simply
send
with
another
node.
B
So
I
I
don't
see
many
many
security
constraints
here
and
also
you
are
not
sending
again
value
with
that
transaction
and
you
are
sending
to
yourself.
So
it's
very,
very
difficult
to
scam
you
to
send
something
or
to
do
more
than
just
not
reading
your
your
your
message.
So
in
this
case
I
think
it's
you,
you
can
send
that
message
through
showing
foreign.
B
You
should
not
read
that
kind
of
information
through
infor,
not
because
of
them.
They
are
for
sure
a
good
person,
but
you
should
not
use
the
party
service
history
from
the
blockchain.
It's
not
it's
not
useful
to
do
that,
because
if
you
trust
a
third
party
services,
fine
trust
them
and
use
them.
No!
No,
you
don't
need
to
to
have
this
kind
of
of
standard,
so
you
can
continue
to
use
facebook,
twitter,
medium
and
so
on,
and
you
can
continue
to
ask
yourself
I'm
seeing
what
the
others
see.
D
Okay,
I'm
just
wondering
like
have
you
ever
because
this
sounds
interesting
to
me
in
the
sense,
have
you
ever
considered
using
this
kind
of
messaging
framework
as
a
means
of
state
management,
ethereum
contracts,
state
management
being
analogous
to
like
in
react?
You
have
redux
or
at
angular.
You
have
some
sort
of
state
management
system
where
you
can.
B
I
think
that
I
don't
know
react,
but
there
are
many
messaging
systems
and
so
in
state
management
systems,
and
so
the
the
only
problem,
but
with
that,
it's
that
it's
that
they
are
not
meant
probably
to
to
be
used
with
this
kind
of
architecture
to
the
the
blockchain.
So
in
blockchain
you
have
to
pay
for
transaction.
You
have
to
wait
for
the
the
consensus
to
reach
consensus
to
the
to
have
a
a
final
state
of
the
of
the
of
your
application.
B
So
I
don't
think
that
using
that
kind
of
of
method
matches
the
the
the
the
needs
of
of
or
or
of
this
this
his
use
case.
So
I
think
that
when
I
use,
for
example,
a
decentralized
app
I
want
everything
goes
fast
and
I
so
I
can
change
my
my
ui.
I
can
do
a
lot
of
things
very,
very
fast
and
then,
when
I
come
to
an
agreement,
I
need
to
save
something.
B
D
Thank
you
so
much.
I
think
that
your
your
points
make
sense.
I
I
and
my
question
was
also
kind
of
broad
in
the
sense
of
because
I
think
that
you
know
small
focused
solutions
such
as
mom,
you
know,
often
have
side
effects,
and
so
I
was
just
wondering
if
you
had
ever
thought
about
that
sort
of
an
implication
in
any
case,
so
I
appreciate
your
your
feedback.
D
Well,
I
mean
I
I
don't
know
too
well,
but
so
basically
in
general
it
would
just
be
a
similar
functionality
to
state
management
except
for
for
the
full,
because
if
because,
if
you're
sending
a
message
which
is
just
in
general,
a
string,
that's
the
same
thing
as
every
other
state
management
system,
and
so
then
you
could
use
the
blockchain.
I
mean
this
is
just
a
random
idea,
but
I
was
just
I
was
interested
to
to
see.
D
B
Yeah
yeah,
I
think
that
this
is
this
can
be
the
the
starting
point
to
have
something
that
can
really
lead
the
the
a
new
way
to
share
content.
Okay,
so
aside
by
the
state
management
again,
I
think
it's
something
really
useful
for
for
applications,
and
I
think
that
we
lack
we
don't
have
a
way
to
share
knowledge
in
general
that
is
safe,
and
so
this
can
be
a
starting
point,
but
I
don't
want
to
go
to
further
with
the
specification
and
so
on,
because
it's
it's
really
hard
enough.
B
B
You
need
to
explain
your
idea.
I
I
think
that
this
is
not
a
small
point
because,
for
example,
in
remaining
in
the
ip
topic,
many
people
comes
to
me
saying
that
they
don't
understand
what
what
I
was
reading,
what
I
was
writing
in
the
iep.
So
I
try
to
add
more
and
more
information,
and
this
is
very
difficult
to
spread
an
idea,
not
using
your
your
own
language,
and
so
this
is
why
I
prefer
to
start
small.
C
And
maybe,
if
I
could
ask
one
last
technical
question,
we've
seen
the
message
messaging
protocols
on
ethereum
before
there's
whisper,
which
then
turned
into
wahoo.
Then
there
was
swarms,
pss
prototype.
How
would
you
compare
and
contrast
mom
to
those
two
systems
to
waku
into
pss,
like
what
would
you
say,
the
trade-offs
are.
B
Yeah,
so
then,
what
you
mentioned
are
what
I
call
ephemeral
messages
system,
so
they
are
meant
to
replace
some
chatting
system
like
what's
up
telegram
and
so
on
I,
so
this
is
not
an
a
standard
that
is
opposed
to
this
kind
of
of
of
messaging
system.
I
I
use
the
message
because,
as
a
word
because
of
the
of
the
point
of
my
own
messages,
but
it's
it's-
this
is
another
good
question,
because
many
people
ask
me
we
can
send
messages
in
other
in
other
with
other
techniques.
B
B
Instead,
what
you
have
said,
the
the
the
application
you
have
mentioned
are
for
transporting
the
message
and
the
chatting
okay.
So
here
I
want
only
to
be
sure
that
that
kind
of
information
that
piece
of
information
is
sent
by
me-
and
I
agree
with
that
information
and
that's
it
so
the
transfer
part
it's
not
in
this
standard
and
yeah,
it's
a
more
like
a
I
blog.
The
system,
so
blog
is
unlike
a
legacy
award
like
a
boom
award.
C
So
so,
what
you're
saying
is
that
waku
and
pss
both
talk
about
in
like
implementing
their
own
communications
layer,
whereas
you're
leveraging?
What
already
exists
in
the
ethereum
system
itself,
without
making
a
new
transport,
but
also
that
wawaku
and
pss
both
have
ephemeral
messaging,
whereas
your
messaging
is
not
meant
to
be
ephemeral?
Is
that
correct.
A
A
Is
it
something
that
could
be
used
for
ethereum
2.0
chain
as
well?
Like
I
heard
this
question
in
some
of
the
meetings
like
people
are
looking
for,
an
application
where,
if
a
notes
go
down,
the
client
may
be
able
to,
you
know,
notify
the
person
or
the
account
holder
that
your
node
is
down
for
this
much
period
and
you
may
be
slashed
or
kind
of
provide
warning
messages.
What
do
you
think
about
it?
How
this
proposal
I
mean
if
at
all,
at
all.
B
B
Yeah
another
point
I
want
to
address
if
I
have
just
a
few
minutes
also
it's
this.
This
standard
is
not
meant
to
identify
people.
So
it's
it's
really
important.
It's
not
identification
system,
because
I
only
want
to
know
that
the
author,
or
of
the
owner
of
a
contract,
for
example,
is
who
is
sending
that
message.
I
don't
care
if
the
author
is
john
paul
or
or
laura.
I
don't
know
so
this.
This
is
not
a
way
to
identify
people.
It's
a
way
to
identify.
B
We
say
something
in
a
that.
Currently
you
can
you
can
you
cannot
do
that
because
it
is
true.
You
can
sign
messages
with
the
classical
sign
method
in
ethereum
and
you
can,
for
example,
publish
that
message
on
facebook,
okay,
but
that
message
you,
you
are
not
sure
that
is
updated.
So
it's
it's
really
important,
because
once
you
have
sent
that
message
out
in
the
world,
any
anyone
can
say
that
that
message
comes
from
you
it's
true,
but
but
they
can
say
you
sent
them
that
message
in
that
moment.
B
A
I'm
so
loving
this
conversation,
but
there's
so
much
to
talk
and
our
time
is
up.
So
thank
you
so
much
for
joining
and
sharing
it
with
us
and
william
and
alita
for
making
this
session
even
more
interesting.
With
your
questions,
I
hope
our
viewers
must
have
gotten
many
of
their
questions
answered,
but
if
you
still
have
any,
please
write
it
down
in
the
comment
section
below
for
those
who
have
joined
for
the
first
time
make
sure
to
subscribe.
The
ethereum
cat
holders
youtube
channel.
A
If
you
have
any
proposals
that
you
would
like
to
know
more,
please
leave
a
comment
below
and
we
will
reach
out
to
the
author,
peep
and
eep
is
a
relatively
new
series
and
that
we
have
started
to
share
more
information
on
the
proposal
that
ethereum
has.
We
need
your
love,
your
support,
so
please
spread
word
around
and
do
watch
our
earlier
episodes
if
you
like
it,
give
it
a
thumbs
up.
A
If
you
don't,
let
us
know
what
you
would
like
to
be
included
for
this
episode,
the
slides
that
were
shared
by
the
author
and
the
contact
details
will
be
available
in
the
description
section.
Thank
you.
All
for
tuning
in
see
you
with
another
proposal
in
p
till
then
stay
safe.
Thank
you.
Everyone.
Thank
you
guys.