►
From YouTube: EOS Community Weekly Fireside Chat - June 29TH
Description
This week the Fireside community discusses the Recover+ blue paper security features, transaction life cycles, EOS Hackathon, Vitaliks steroid comment, and more!
00:00:00 This weeks topics by Stephane
00:02:37 Pomelo NFT give away and updates by Stephane
00:08:08 Recover+ Q & A by Yves, Zack
00:48:39 Pomelo previous season question by Stephane
00:49:22 Troubleshooting CPU issues by Ceskam, Yves, Denis
00:56:53 API transaction life cycle and Wallet+ by Aaron, Yves,
01:06:45 Hackathon update by Chris, Yves
01:14:56 Bithum and staking yields by Stephane, Yves, Joe, Zack
01:33:27 Vitalik’s “Ethereum on steroids comment” by Stephane, Yves, Zack
01:42:10 Community open mic
01:56:17 Wrapping it up with a GO EOS!
01:56:50 End
// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #enf
A
Welcome
everyone
to
another
edition
of
the
eos
fireside
chat,
I'm
your
host
stephane
and
we've
got
a
good
show
for
you,
planned
today,
shout
out
to
everyone.
Listening
in
on
the
various
platforms,
we're
on
discord
live
if
you
want
to
join
in
share
share
your
thoughts
share
your
questions
participate.
The
open
mic
join
us
on
discord,
but
you
can
also
watch
from
telegram
from
twitter
youtube
and
facebook
as
well
all
right.
A
So
this
week
we've
got
a
few
topics
planned
for
you,
guys
of
course,
and
as
always,
always
welcome
you
guys
to
jump
in
with
some
new
topics
or
otherwise,
questions
or
comments.
Of
course,
so
we'll
be
talking
about
some
pomelo
nfts
today,
we'll
be
talking
about
rip
cover
plus
we
mentioned
it
last
week,
but
it
was
pretty
fresh
wondering
maybe
this
week
some
of
you
might
have
had
time
to
read
the
blue
paper.
A
So
we'll
we'll
talk
about
that
a
bit
if
chris
burns
joins
us,
we'll
be
getting
some
hackathon
updates
and
some
of
the
news
news
that
came
out
this
week
just
earlier
today,
we
we
learned
about
bit
hum
offering
some
staking
awards.
We'll
talk
about
that
eve
had
some
great
tweets
again
this
week,
I'll
be
mentioning
some
of
my
favorites
and,
of
course,
the
vitalik
comment
earlier
on
that
created
quite
a
stir
in
both
the
ethereum
and
eos
communities.
A
But
before
before
we
get
into
that
wanted
to
remind
you
guys
this
is
the
last
week
to
get
your
raffle
tickets
for
the
end
of
the
month
raffle.
So
these
raffles
go
down
on
the
first
wednesday
of
the
month.
So
that's
going
to
be
next
week
on
july
6th
and
until
then
you
can
go
to
blend.gems.io
and
blend
four
pop
tokens
into
the
raffle
ticket.
We're
gonna
have
25
prizes
worth
10
eos,
each
at
least,
and
maybe
some
extra
goodies
as
well.
A
All
right,
I
see,
we've
got
a
lot
of
new
faces
that
have
joined
the
stream
in
the
last
few
minutes.
Welcome
everyone.
We've
got
dwayne
floska
john
at
boyd,
brandon,
lovejoy
mataj.
I'm
not
sure
how
to
pronounce
that
trimbot.
The
legend
yaro
welcome
guys
thanks
for
joining
and
yeah.
So
let's
get
it
started
with
some
pomelo
nft
talk.
So
earlier
this
week
on
tuesday
or
yesterday,
the
grand
collectible
packs
went
live
for
sale,
so
you
can
go
to
harvest.pomelo.io
for
all
your
pomelo
nft
needs.
A
A
Coming
in
by
wire,
you
have
to
give
you
a
little,
but
thanks
for
joining
yeah,
so
the
grant
collectible
packs
are
on
sale,
they're,
going
fairly
quickly,
there's
525
available
on
sale
through
atomic
hub
and
through
our
harvest.pomelo
platform
and
there's
300
left
so
almost
half
of
them
sold.
You
can
also
go
to
shop.pomelo
dot
io
and
buy
some
either
carbon
nfts
or
grand
collectible
packs
via
shopify,
with
your
credit
cards,
and
then
you
get
a
claim
link
and
then
you
can
get.
You
can
go
claim
your
nfts.
A
So
if
you
haven't
tried
that
out,
yet
we
encourage
you
to
try
out
the
shopify
integration.
It's
still
you
know
in
beta
we
could
say,
but
we're
looking
for
people
to
try
it
out
to
see
how
it
works
to
see
the
the
whole
transaction
flow.
And
if
you
have
comments,
concerns
something
is
buggy
or
whatever.
A
Of
course,
let
us
know
and
try
it
out
and
in
order
to
you
know,
incentivize
you
guys
a
bit
to
go
out
there
on
shopify
and
used
some
dirty
fiat
to
buy
these
pristine,
pomelo
nfts,
there's
a
little
slight
discount
as
well
on
the
on
the
shopify
platform.
So
take
a
look
denis.
I
can
see
here
denis
shared
the
link
in
the
stream
chat.
That's
awesome.
A
We've
got
eve
lacrosse
in
the
house
joining
us
today,
as
well.
Ns
james,
just
joined
as
well
welcome,
guys
and
alicia
as
well.
Also
yesterday
or
this
morning,
we
shared
a
new
article
that
we
published
on
the
pomelo
medium
account
that
kind
of
explains
the
nft
series
so
far
this
season.
So
I'm
gonna
share
that
link
for
you
guys
in
the
stream
chat
as
well,
and
so
you
can
see
there,
you
can
see
kind
of
the
nfts
that
are
available.
A
A
A
So
again
you
can
check
out
the
link
here
in
the
stream
chat.
If
you
want
to
go,
give
give
that
post
a
like
and
retweet.
We
appreciate
it,
and
hopefully
you
win
a
pack
out
of
it
all
right.
Final
piece
of
pomelo
nft
update
is
that
the
pomelo
achievements
are
now
live,
so
we've
been
distributing
some
non-transfer
tokens,
non-transferable
nfts
that
represent
the
top
donors
and
top
grants
from
both
season
one
and
season
two.
A
So
top
100
donors
received
an
nft
with
the
top
25
receiving
a
crown
on
their
on
on
their
achievement,
nft
and
then
same
thing
goes
for
the
top
10
and
top
50
grand
creators
from
each
season.
So
the
donors
you
know,
are
ranked
according
to
their
total
donations
in
eos
and
the
grant
creators
are
ranked
according
to
the
amount
of
matching
funds
that
they
were
able
to
earn,
and
so
you
can
go
check
out
your
accounts.
A
so
check
that
out
and
also
holders
of
these
achievement,
badges
are
going
to
be
those
who
we
reward
with
airdrops
and
bonuses
and
other
gifts
like
that
all
right.
So
that
covers
kind
of
the
introduction
and
what
I
wanted
to
talk
about.
With
pomelo,
if
anyone
has
any
questions
or
comments,
feel
free
to
jump
on,
I'm
gonna
give
you
guys
a
bit
of
a
bit
of
music
and
then
we'll
continue
on
with
the
show.
A
A
So
I'm
wondering
if
some
of
you
have
had
time
to
read
it
now
and
if
some
of
you
have
some
thoughts,
some
comments,
some
questions
general
feeling
that
you'd
like
to
share
and
in
order
to
incentivize
you
guys
to
share
I'll,
be
giving
out
one
bonus
pop
token
for
everyone
who
jumps
on
here
in
this
topic
and
shares
shares
their
ideas,
thoughts
whatever
it
is.
Yeah
we'd
like
to
hear
from
you
guys.
A
A
A
F
Trim
out
here
just
jump
in
real
quick
about
recover,
plus
question
for
eves
or
zach.
I
haven't
read
through
it
yet
so
even
said:
it's
like
insurance,
the
insurance
layer
of
d5
d5
3.0
on
eos.
What
exactly
is
recover
plus,
though,
and
how
will
that,
if
at
all
impact,
some
calls
where
some
people
say
you
know
eos
me
is
more
just
more
centralized
than
other
chains.
C
Because
this
would
be
an
opt-in
program
and
so,
if
you're
running
a
defy
application
on
eos
and
you'd
like
to
opt
in
to
recover
plus,
essentially
then
there's
going
to
be
a
process,
so
you
need
to
apply
for
it.
There's
going
to
be
a
comedian,
that's
going
to
be
reviewing
you're
going
to
need
to
go
through.
You
know
steps
in
order
to
qualify
for
that.
What
that
does,
though-
and
in
this
whole
process
is,
is
transparent,
there's
a
website,
it's
already
there.
C
I
believe
it's
eos
recover
or
eos
recovery.com
zach,
helped
me
out
here
and,
and
so
centralization
or
the
spectrum
of
centralization
is
somewhat
irrelevant
in
this,
because
the
the
people
participating
in
those
programs
would
have
asked
for
that,
and
that
is
the
I
guess
secondary
layer
to
this
is
the
fact
that
people
would
opt
in
to
this
program,
so
that
should
an
event
occur.
Recover
plus
doesn't
prevent
any
type
of
hack
from
happening,
but
it
does
all
of
the
work
beforehand,
and
it
has
a
you
know
the
the
foundations
laid
beforehand.
C
So
that
should
something
happen.
The
network
and
those
running
the
recover
plus
program
already
have
all
of
the
information
ready
to
potentially
stop
a
hack
while
it's
in
progress.
So
we
saw
that
on
two
occasions
on
eos,
where
hacks
occurred
and
the
applications
were
not
ready.
They
didn't
have
the
information
in
line,
but
that
you
know
the
block.
Producers
indicated
that
they
were
willing
to
help
and
willing
to
stop
and
and
in
both
instances
they
were
able
to
prevent
loss
of
funds.
C
C
I
can
I'll
try
to
answer
in
a
different
way.
There
was
another
hack
that
happened
back
in
december,
and
that
was
the
dad
e-curve
pizza
basically
was
leveraging
a
few
platforms
and
part
of
the
problem
with
trying
to
stop
the
hack
in
progress
was
that
the
metrics
that
were
needed
in
order
to
actually
do
something
about
it?
C
C
We
also
don't
know
whether
or
not
in
those
instances
the
project
itself
is
part
of
it.
Like
is
this
an
internal
hack
is
this
was
this?
Is
this
a
rug,
pull
having
a
lot
of
that
information
prior
to
makes
it
much
easier
to
ascertain
or
for
the
blog
producers
to
be
able
to
ascertain
whether
or
not
they
should?
C
The
the
determination
as
to
whether
or
not
this
was
a
scam,
rug
pool
or
whether
or
not
was
a
hack
aligned
with
all
of
the
information
was
being
present.
The
smart
contracts
were
open,
they
were
audited
et
cetera,
et
cetera
in
one
of
the
instances,
really
cleared
out
a
lot
of
that
information.
But
that
may
not
be
the
case
in
the
future,
which
is
why
recover
plus
was
created
so
that
any
other
application
in
the
future
would
want
to
benefit
from
that.
C
That's
true,
of
course,
the
networking
clearly
helped
the
fact
that
in
our
case,
with
default
and
the
fact
that
we
could
reach
out
to
block
producers
and
get
them
to
look
at.
This
was
a
key
component
of
this.
But
it
was
not
the
sole
component
at
all.
The
fact
that
we
had
a
lot
of
the
data
accumulated
and
could
showcase
that
this
was
in
fact
a
has
was
clearly
a
key
component.
C
Another
really
really
important
aspect
of
other
applications
saying
well.
Why
couldn't
I
be
saved
you
know
in
in
the
past
and
such
well
the
technical
requirements
to
be
able
to
do
something
about?
It
are
incredibly
difficult.
The
skill
set
required
to
be
able
to
do
something
are
extremely
hard.
There
are
only
a
few
individuals
on
eons
that
can
actually
write
the
smart
contracts
and
the
codes
and
deploy
the
script
to
even
do
something
about
it.
It's
not
like
anybody
could
do
something.
It's
extremely
difficult.
You
need
to
understand
how
eosio
operates.
C
Better
information,
better
metrics.
All
of
that
you
didn't
see
through
the
vault
hack
and
you
didn't
see
through
the
data
because
it
occurred
and
because
it
happened
to
prominent
members
of
the
community.
How
do
we
decentralize
that?
How
do
we
open
that
up
to
people
who
don't
necessarily
have
that
luxury?
That's
what
recover
plus
aims
to
address.
C
C
There
are
a
lot
of
things
that
people
can
do
to
mitigate
those
risks,
and
that's
also
what
recovery
plus
is
going
to
be
helping
with
is
to
help
guide
those
applications
on
best
practices
of
what
they
can
do
to
mitigate
and
to
minimize
the
chances
of
that
happening,
but
in
the
unfortunate
event
that
that
happens,
because
it
will
happen
at
gwen.
It's
just
a
question
of
time
and
the
unfortunate
that
that
event
in
the
unfortunate
event
that
that
happens
than
to
have
a
framework
and
a
system
in
place
to
potentially
be
able
to
stop.
C
That
is
what
recover
plus
aims
to
do,
but
is
very
much
opt-in,
and
so
this
idea
of
decentralization
centralization.
This
would
be
what
the
you
know.
Essentially,
the
people
would
be
giving
the
green
light
before
time
they
would
be
giving
the
okay
prior
to
that
and-
and
that
is
in
the
form
of
you-
know
what
the
requirement
the
requirements
for
recover
plus
is,
and
the
information
that's
being
accumulated
from
those
parties,
the
kyc
that
they'll
need
to
go
through,
etc,
etc.
H
I've
got
a
quick
question
regarding
recover
plus
yeah,
so
this
is,
this
is
andrew,
drew
drew
block.
I
am
just
curious.
Does
recover
plus
incorporate
any
riccardian
contract
considerations?
Does
it
use
ricardian
contracts
in
any
way
to
establish
the
intent
of
what
a
given
piece
of
code
is
supposed
to
do?
Anything
like
that.
C
No,
the
recover
plus
is
not
aiming
to
address
the
regarding
contracts.
However,
if
you've
read
the
wallet
plus
blue
paper,
ricardian
contracts
is
one
of
those
priorities.
That's
been
laid
out
in
paper,
so
recover
plus
would
be
able
to
come
in
and
leverage
the
ricardian
product
contracts
should
they
be
present.
But
updating
system
of
regarding
contracts
is
not
in
the
scope
of
recover,
plus,
okay
cool
but
oftentimes.
C
It
is
quite
black
and
white
in
terms
of
whether
or
not
the
code
behaved
as
was
intended,
and
so
this
is
also
part
of
the
recover
plus
program
is
to
go
through
with
those
teams
to
find
out
what
that.
What
is
the
intent
of
the
application?
What
type
of
defy
are
you
offering,
and
so
there's
somewhat
of
an
auditing
function
into
that
as
well?
C
But
yes,
definitely
if
our
system
for
cardium
contracts
on
eos
was
upgraded,
as
was
suggested
by
aaron
and
the
others
who
wrote
while
plus
that
would
come
as
a
benefit
regarding
contracts.
One
of
the
challenges-
and
actually
this
has
been
a
discussion
in
the
eosio
developers
chat
lately-
is
that
they're
not
they're,
still
workarounds
or
they're
still
ways
that
people
can
kind
of
gain
the
ricardian
contract.
C
At
the
end
of
the
day,
the
end
user
still
has
to
do
due
diligence
and
as
much
as
the
ui
can
facilitate
that
process,
and
there
could
be
ways
to
really
try
and
make
it
mitigate
that
you
know
the
final.
The
final
show
stopper
the
final
filter
is
the
end
user
and
so
increasing
that
education
facilitating
for
the
end
user
is
clearly
important,
but
scams
will
continue
happening
and
when
we
talk
about
recover
plus
we're
not
talking
about
phishing
scams,
that
is
not
in
scope.
C
C
Sense
thanks
and
that
issue
in
terms
of
phishing
scam
that
exists
outside
of
blockchain
as
well.
You
know
receiving
an
email
asking
you
to
you,
know,
click
on
this
link
and
give
your
banking
information,
your
social
insurance
number
or
receiving
a
phone
call
telling
you
that
you
know
the
irs
or
the
cra
or
wherever
you
are
in
the
world
is
going
to
sue
you
unless
you
give
them
ten
thousand
dollars
right
now.
C
G
So
terrible
question
is
it?
Is
it
going
to
address
or
study
con
non
accounts
and
contracts
that
we
know
that
are
very
well
known
for
being
scams
like,
for
example,
the
there
is
a
huge
account
that
we
know
that
it's
been
scamming
people
for
a
long
time
or
a
contract?
Then
we
know
that
it's
been
doing
the
same
for
for
a
while.
Is
he
going
to
address
or
study
those
cases.
C
So
recover
plus
is
not
about
phishing
scams;
it
is
about
applications
that
deploy
smart
contracts
and
those
smart
contracts.
It
gets
taken
advantage
of
due
to
an
oversight
in
writing
code
or
oftentimes,
really
complex
packs
that
you
know
are
just
pioneered.
I
mean
that
as
well
as
a
game
of
whack-a-mole,
you
could
be
really
really
good
at
writing
code,
but
if
you've
got
incentive
for
somebody
to
try
and
break
that
code,
we've
seen
that
it
happens
repeatedly.
E
It's
another
case
of
whack-a-mole,
so
I'm
assuming
it's
one
of
the
fishing
sites
that
has
you
swap
your
keys.
It
that's
vision,
it
turns
out,
I'm
not
talking
about
it
exactly
and
I'm
just
saying
it's
like
whack-a-mole,
because
even
if
you
froze
that
contract
null
its
keys
whatever
they
could
just
deploy
another
smart
contract
that
switches
your
keys
and
then
use
that
on
the
same
front,
end
of
the
website
and
it
does
the
exact
same
thing
it's
another
case
of
whack-a-mole,
like
you
think
you
just
keep
deploying
a
new
contract.
J
I
actually
got
a
quick
question,
a
couple
of
them.
Actually
this
is
tony
lucavoli
here
for
for
recover,
plus
and-
and
a
couple
of
I
can't
see
the
guys
gan
floska-
that
that
that
kind
of
ties
into
one
of
my
questions
of
so
the
recovers
plus
role
is
going
to
be
primarily
reactionary
and
not
preventative.
Right,
I
mean
that
seems
to
be
the
case
or
is
there
going
to
be
any
sort
of
like?
C
Now,
if
you're,
a
user
and
you're
going
to
be
interacting
with
the
default
application
on
eos.
This
is
not
financial
advice.
If
there
is
a
project
that
is
or
has
you
know,
joined
recover
plus,
and
they
get
that
badge
that
that
shield,
it
is
not
to
say
that
that
it
is
a
safer
application
or
that
nothing
will
happen,
but
it
does
give
more
trust
or
confidence
in
that
project.
So
in
that
sense
it's
also
somewhat
preventative.
C
So
if
you're
a
user-
and
you
are
looking
at
participating
in
one
of
the
d5
applications,
I
would
see
that
there'd
likely
be
a
trend
that
users
will
perhaps
migrate
to
projects
that
have
been
approved
by
recover.
Plus
more
so,
and
so
we
may
prevent
hacks
from
occurring
because
those
that
don't
participate
in
recover,
plus
maybe
at
a
higher
target
or
a
higher
risk.
J
It
seems
like,
like
almost
like
a
an
alarm
system
right.
You
get
an
alarm
system
installed
on
your
home.
People
are
gonna,
you
know,
they're
gonna
come
install,
it
they're
gonna
check
your
home,
so
you
look
for
any
weak
points,
look
for
any
potential
vulnerabilities
and
then
you
get
the
big
sign
out
front.
That
says
that
this
house
is
protected
by
an
alarm
system.
So.
C
So
I
mean
I
I
and
I
don't
wanna
again
having
an
alarm
system
does
not
mean
that
your
house
will
not
be
correct
victim,
corrects,
and
so
I
really
don't
want
the
you
know
the
community
to
get
the
impression
that
this
prevents
hacks
from
happening
or
that
it
guarantees
that
the
funds
would
be
recovered.
That
is
not
the
case
is
simply
trying
to
increase
the
likelihood
and
mitigate
the
risks
and
really
open
up
and
democratize.
J
C
C
It
will
also
help
fulfill
the
role
of
essentially
a
negotiator
between
potentially
the
hacker
and
the
application
project,
because
that's
a
particular
skill
set
that
not
necessarily
everybody
has
and
so
that
communications
layer
that
that
in
between
is
very
much
what
the
recover
plus
committee
would
do
and
that
recover
plus
committee.
If
you
read
the
blue
paper,
the
proposal
that
is
formed
of
various
community
members,
for
example,
a
few
blog
producers,
a
few
d5
projects
that
we
know
are
clearly
not
that
are
real
d5
projects.
C
It
increases
the
likelihood
that
the
block
producers
can
actually
intervene
that
they're,
that
you
know
that
they
have
the
information
that
they
need
to
be
able
to
intervene,
because
that's
another
issue
in
the
past
is
applications
despite
them
being
able
to
deploy
a
project,
don't
necessarily
have
the
either
the
technical
capacity
like
I
mentioned
earlier,
or
the
data
to
be
able
to
showcase.
Yes,
this
is
an
actual
hack.
This
is
not
a
rug
pool
by
us.
So
what
is
that
information?
What
is
required?
C
C
So
the
alarm
bells
rang
at
the
block
producers
before
it
even
rang
at
the
you
know,
at
the
application
the
application
woke
up
and
this
basically
their
funds
were
drained.
It
was
already
too
late
so
triggers
like
that.
As
an
example
will
be
part
of
the
monitoring
of
what
the
recover
plus
team
can
do,
and
that's
just
one
example.
E
In
depth,
there's
some
other
preventative
things
also,
so
it's
kind
of
like
an
insurance
company,
like
your
insurance
company,
always
sends
you
advice
on
ways
to
get
healthy,
go
see.
A
doctor
checkup
so
part
of,
what's
proposed
in
recover
plus,
is
a
bug
bounty
program
for
white
hat
hackers,
so,
basically
an
incentive
program
for
people
who
are
good
hackers
and
want
to
find
these
vulnerabilities
in
different
smart
contracts.
They
could
be
rewarded
to
do
so
so,
rather
than
being
incentivized
to
earn
their
profits
by
draining
the
funds
and
watching
over
their
back.
E
From
that
point
on
there
there
will
be
a
program
to
submit
bugs
and
vulnerabilities
to
everyone's
benefit,
because
maybe
they
find
something
that
could
potentially
exploit
multiple
contracts,
so
it's
basically
enhancing
best
practices
creating
best
practices
for
defy.
So
another
example
is
the
monitoring
tools
that
you've
mentioned.
So
maybe
there
could
be
an
open
source
monitoring
tool
that
other
projects
could
use
or
learn
about
best
practices.
Using
the
time
delay
functions,
that's
native!
E
E
But,
as
we
all
know
like
eos
is
very
fast,
also
so
the
you're
always
cat
and
mouse.
The
hackers
could
move
funds
faster
than
you
can
catch
them
and
and
freeze
tokens
or
freeze,
freeze
an
account
so
by
incorporating,
like
a
time
delay
for
example,
or
in
this
case,
if
there
were
best
practices,
documents
created
by
recover
plus
to
basically
say
this
is
what
we
believe
the
best
practices
are
explain.
It
maybe
provide
some
open
source
code.
E
Then
it
could
be
another
layer
to
slow
things
down
so
that,
even
if
there
is
an
exploit
there
might
be
a
limit
to
how
much
capital
could
be
drained
in
a
particular
day
or
a
particular
time
period.
Then
you
won't
see
things
like
the
axi
bridge
or
the
ronin
bridge
being
hacked
for
100
million
dollars
in
a
single
day,
or
things
like
that
that
you've
seen
from
other
ecosystems,
you
kind
of
could
put
a
cap
on
the
limit
for
for
a
given
day.
So
I
think
best
practices.
E
I
think
white
hat
hackers
and
a
bug,
bounty
program
and
then
also
like
it
doesn't
prevent
things.
But
it's
it's.
It
kind
of
gives
you
a
little
bit
of
reassurance
on
like
rug,
pools
and
things
like
that,
because
you
know
that
if
a
d5
project
submitted
and
got
approved
to
the
eos
recover
plus,
you
know
they
that
one
of
their
project
founders
went
through
a
kyc
process
with
recover
plus.
E
L
I
think,
most
importantly,
for
third-party
developers
is
the
fact
that
this
exists
period
is
a
huge
boon
for
their
existence,
so
it
makes
it
a
lot
easier
to
create
applications
when
you
know
that
this
part
of
your
stack,
which
is
mandatory,
is
already
being
handled,
and
you
can
adapt
to
it
instead
of
having
to
recreate
it
from
scratch.
I
think
that
it's
been
something
that's
been
missing
for
a
long
time
from
the
esio
ecosystem
and
eos,
primarily.
C
Keep
in
mind
as
well
that
recover
plus
is
a
new
initiative
right.
So
what
recovery
plus
looks
like
today
and
what
it
will
look
like
in
a
year,
hopefully
will
not
be
the
same.
This
is
something
that
eos
is
pioneering
there's
nowhere
else
out
there
that
we
know
of
that
is
doing
something
like
this,
and
so
the
iteration
of
what
you
know
the
program
or
the
initiative
is
ideally
will
continue,
improving
over
a
period
of
time
and
so
it'll
get
stronger,
it'll
get
better.
J
No,
this
is
a
fantastic
project.
I
I
hope
my
I'm
not
alluding
to
my
thoughts.
I
think
that's
anything
other
than
that
this
is
world-class.
I
I
wouldn't
expect
this
kind
of
how
to
expect
this
kind
of
care
and
support
out
of
most
enterprise
software.
So
it's
it's
a
great
thing
to
see.
The
last
thing
I
was
curious
about-
and
I
know
this
is
a
pretty
probably
pretty
variable
number
to
quote,
but
rough
ballpark.
J
What
would
be
the
time
to
engage
right
so
from
from
somebody
reaching
out
and
contacting
you
guys
to
say,
hey,
I'm
interested
in
this.
What
do
I
need
to
do
to,
and
I
understand
what
you're
explaining
you
know-
there's
there's
definitely
going
to
be
a
couple
meetings,
a
couple
of
review
processes,
but
is
it
something
along
the
lines
of
you
know
a
couple
weeks
couple
months
a
year,
something
along
those
lines,
just
rough
ballpark
timeline,
so.
C
That
is
francis
who
routinely
joins
our
calls
and
such
but
francis
from
from
pizza.
If
you
want
to
know
you
know,
I
would
say
the
answer
to
your
questions.
Just
be
very
direct
as
soon
as
possible.
Reach
out
to
francis
he's
been
in
the
developer.
Chats
he's
been
in
jungle
chat
as
well,
because
they're,
starting
to
run
the
test
and
stuff
so
reach
out
to
him
as
much
as
as
early
as
possible.
I
don't
think
there's
any
harm
in
doing
so.
C
I
believe
that
there's
projects
that
have
already
applied
and
started
going
through
the
process,
but
the
you
know
the
portal
and
the
initiative,
the
program,
the
committee,
all
that
is
still
underway,
and
so
you
know
insert
yourself
as
early
as
possible
in
the
process,
learn
about
the
process
and
ideally
come
and
help
and
improve
the
process
as
it's,
it's
literally
being
crafted
right.
So
the
what
you
see
in
the
blue
paper
is
the
idea
now
that
idea
has
been
put
in
into
motion.
C
As
of
you
know,
a
few
months
back
with
the
portal,
but
then
more
so
once
that
blue
paper
was
was
released
and
shortly
before
that,
and
so
it's
still
very
much
a
work
in
progress.
And
so,
if
you
have
an
interest
in
this
reach
out,
I'm
certain
that
francis
will
appreciate
walking
you
through
what
we
already
have
and
how
potentially
you
can
even
come
and
improve
and
participate
to
make
the
system
better.
J
K
C
I'm
not
sure
if
I
understand
the
the
question
correctly,
but
users
in
an
application.
I
guess
that
is
somewhat
an
irrelevant
piece
of
data,
so
whether
there's
five
people
in
the
defy
application
or
10
000,
I
would
imagine
that
the
same
code
would
need
to
be
written
to
potentially
stop
a
hack
from
occurring.
I
guess
I'm
not
really
sure
what
the
question
is.
Do
you
mean
the
number
of
applications
that
can
participate
in
the
program.
C
I
can't
tell
you
what
that
number
is,
because
I
don't
know
how
many
they'll
be
able
to
accommodate
and
then
once
they
hit
that
limit.
Do
they
just
say
you
know
this?
Is
it
done?
I
doubt
it.
The
idea
would
be
to
be
able
to
grow
with
the
demand,
but
where
that
number
lies
at
this
stage
I've
I've
no
idea.
C
Yeah
legitimate
projects
as
well
right,
so
we're
not
talking
about
somebody
who
just
deploys
a
smart
contract,
and
then
you
know
it.
It
needs
to
have
an
actual
project,
an
actual
application,
and
so
we
are
yeah
very
much
like
zach
is
saying
the
ceiling
right
now
was
nowhere
near.
I
believe,
the
the
potential
capacity
that
exists
at
this
stage
similar
to
yield
plus.
C
If
we
are
at
this
stage
well,
first
of
all
right
now,
we've
got
nowhere
near
that
number
number
of
applications,
and
that's
so
that's
not
a
problem,
and
if
we
are
there
well,
that
means
that
we
now
have
a
thriving
developer.
Community
we've
got
a
thriving
token
holder
community,
that's
participating
in
this
as
well,
and
then
it's
the
least
of
our
worries.
C
I
I
think
I
understood
the
question,
so
let
me
rephrase
and
just
because
your
mic
is
cutting
in
and
out
just
answer
with
a
yes
or
no.
I
think
you
asked
whether
or
not
because
this
would
bear
a
cost
on
the
network,
whether
or
not
there's
going
to
be
a
subscription
or
a
cost
to
participate
in
this
program.
That's
correct!
Yes,
at
this
stage,
there's
no
cost
to
participate
in
this
program.
C
However,
if
you
read
the
recover
plus
blue
paper,
there
is
mention
of
whether
or
not
this
initiative
in
the
future
could
become
very
much
so
like
an
insurance
layer,
and
so
they
have
that
section
in
there
where
applications
would
pay
and
then
then
it
really
would
be
an
insurance
layer.
Perhaps-
and
there's
only
exploratory
talk
in
that
blue
paper.
But
the
idea
that
if
this
was
highly
successful-
and
you
actually
had
just
like
an
insurance
in
in
real
life-
have
enough
people
that
participate
in
this.
C
That
then
the
insurance
layer
would
have
enough
funds
to
even
cover
hack.
Should
it
not
be
able
to
be
stopped
in
time
at
a
certain
you
know,
level
or
certain
percentage,
but
that
is
currently
out
of
scope
of
what
the
recover
plus
portal
and
and
team
are
working
on.
But
yes
that
was
mentioned,
so
I
invite
you
to
go.
Look
at
the
blue
paper
does
talk
about
that.
C
C
A
Well,
thanks
for
that
great
explanation,
eve
and
thanks
trimble,
trimbot
gunflaska,
drew
block
tony
mark
and
mel
for
jumping
in
and
joining
the
conversations.
If
you
guys
want
your
extra
pop
token,
send
me
a
message
on
discord
with
your
eos
account
and
I'll
drop
that
in
in
your
account
later
on
today.
A
A
Also
shout
out
to
everyone
in
here
we're
now
for
60
people
in
the
fireside,
so
I
think
it's.
This
is
the
first
time
since
our
new
year's
special
edition
that
we've
had
that.
So
it's
great
to
see
that
you
guys
enjoy
these
fireside
chats
and
more
and
more
of
you
are
joining
and
that's
not
even
counting
everyone.
Listening
live
on
telegram
youtube,
twitter,
facebook.
A
All
right,
looking
at
the
chat
here,
I
did
notice
a
question
about
pomelo
collectibles
from
previous
seasons
and,
if
they're
still
valid
for
this
season,
so
each
season
is
kind
of
separate,
but
if
you're
holding
some
diamond
fragments
or
a
diamond
potion,
you
can
definitely
continue
to
claim
your
diamond
fragments
if
there's
still
some
available
in
your
potions
and
also
blend
those
diamond
fragments
into
some
stunning
diamond
pomelo.
So
that's
still
going
on
for
this
season.
M
Chase
eskim
here
from
challenge
dac,
and
one
thing
I
wanted
to
ask
was:
has
there
been
any
major
changes
to
the
code
like
within
probably
the
last
two
weeks,
because
on
our
end,
we're
experiencing
a
lot
of
errors,
we're
having
we're
just
having
a
lot
of
errors
with
with
our
app
and
we
run?
Telos
too,
we
haven't
been
getting
the
errors
with
telo,
so
it
could
be
an
internal
issue
on
our
side
but
and
just
changes.
M
C
When
you
say
cpu
telos
did
not
switch
over
to
the
power
up
model,
eos
did
and
so
intel
is.
You
still
have
to
stake
resources.
That
model
has
not
been
the
case
in
eos
now
for
a
little
over
a
year.
So
when
you
say
have
you
have
cpu,
you
mean
you've
gone
through
the.
I
guess
at
this
point,
not
new,
but
new
process,
which
is
different
than
on
telos,
correct.
M
Yeah
yeah,
I
mean
everything
was
running
great
until
within
probably
10
days
ago,
or
maybe
two
weeks
so
we've
noticed
in
the
past,
where
sometimes,
if
there's
like
an
update
in
the
code,
sometimes
we
ought
to
change
things
a
little
bit.
But
yeah
we've
been
having
this
issue
for
probably
a
week,
and
so
I
mean
there's,
there's
been
no
major
changes
to
the
way
things
like
way.
Powerup
works
in
the
last
month
right,
any
all
changes
have
been
with
the
power
up
model
have
been
not
that
recent
right.
M
N
It's
mostly
like
yeah,
it's
mostly
the
subjective
building,
so
I'm
pretty
sure
that
what
you're
hitting
is
you're,
probably
running
everything,
sort
of
a
back
end
and
your
contract
is
probably
doing
more
than
more
than
the
average
transaction
and
whenever
your
account
actually
has
sort
of
a
level
of
cpu,
you
actually
have
if
you're
doing
a
lot
of
transactions.
Like
you
know,
more
than
an
average
user,
you'll
probably
hit
that
subjective
building,
and
you
have
to
over
subscribe
your
cpu.
N
So
you
might
see
that
you
have
available
cpu,
but
that's
not
when
you're
a
contract
constantly
pushing
a
lot
of
transactions
because
then,
essentially
the
endpoints
will
right
start
to
rate
limit
you
because
you're
pushing
a
lot
of
transactions.
So
I
think
the
solution
for
you
or
the
easy
solution
would
be
to
over
subscribe
your
cpu
to
have
more
access
to
not
hit
the
that
sort
of
subjective
billing
and
what
you
can
do
is
we
have
a
website
called
lost
transaction.
It's
still
very
beta
prototypey.
N
You
can
put
in
your
contract
name
and
you
can
see
which
type
of
errors
that
come
out
of
your
contract,
saying
it
might
run
out
of
cpu
or
it
might
be
failed
or
or
what
not.
So
we
can
give
you
the
link
for
that
and
you
would
just
put
in
your
contract
that
you're
operating
with
and
it
will
tell
you
which
types
of
errors
you're
receiving
or
which
type
of
errors
that
the
peer-to-peer
and
the
block
producer
nodes
are
reporting.
M
O
L
C
They're
still
on
blocks,
trying
to
use
the
free
cpu,
they
haven't
disabled
that
and
the
blocks
itself
is
out
of
cpu.
So
I
don't
know
if
this
applies
in
this
instance,
but
for
everybody
else.
Listening
if
you
get
the
error,
I
think
it's
the
same
error
that
everybody's
getting
it
says
something
like
240
milliseconds
of
cpu
required
and
you
know,
you've
got
greater
than
zero
and
then
you
look
at
your
account
and
it's
clear
that
you've
got
enough.
C
C
M
O
O
A
O
Might
be
able
to
retry
the
transaction
to
make
sure
it's
not
lost,
but
I
and
I
think
there
may
be
some
improvements
for
how
subjective
billing
is
calculated
like
like
we
were
just
talking
about.
If
you
submit
failed
transactions
over
and
over
again,
you
eventually
get
blocked.
Essentially,
it's
an
abuse
prevention
mechanism
and
one
of
the
tweakable
parameters
for
api
operators
is
going
to
be
to
be
able
to
set
how
long
that
window
is
right.
O
Now,
I
think,
by
default
it's
24
hours
and
the
3.1
feature
should
let
you
adjust
that
timer
api
operators
can
adjust
that
timer.
So
it's
like
an
hour
or
30
minutes
or
whatever
I
know
matthew
had
played
with
a
bunch
of
numbers,
and
I
think
a
lot
of
api
operators
on
eos
have
actually
lowered
the
24-hour
window
down
to
a
couple
hours.
L
O
But
we
need
the
registry
to
exist
first,
so
once
that
exists,
then
we
can
hit
a
point
where
we
can
identify
malicious
actors
and
the
wallet
interfaces
can
make
recommendations
or
provide
warnings
or
something
like
that.
If
a
user
tries
to
interact
with
a
malicious
user,
that
is
very
that's
not
as
far
out
as
recovery
or
it's
further
out
than
recovery
plus.
O
C
Same
as
the
the
ricardian
contracts
that
you
guys
suggested,
they're
building
blocks
that
can
be
leveraged
to
improve
the
user
experience
and
really
that
wallet
plus
blue
paper
was
all
about.
I
mean
people
keep
thinking.
Oh
you
know
you
guys
are
going
to
be
building
a
wallet.
I
get
terrible
choice
of
name
it
really.
It
really
is
about
the
user
experience
and
how
applications
connect
to
the
chain
and
facilitating
that
process
having
sdks
and
such
so
yeah.
That
application
registry
is
a
big
component
of
that
as
well.
Yes,.
C
I
guess
shift
of
things
over
the
last
couple
of
months
in
eos
a
few
months
back
or
I
guess
even
just
you
know
eight
months
ago,
one
of
the
larger
issues
was
not
having
access
to
funding
to
be
able
to
take
on
these
projects
or
these
initiatives,
and
now
we
do
have
access
to
funding
and
the
the
blocker
is
not
having
the
people
being
able
to
take
on
those
projects
or
the
skill
sets
being
able
to
do
so.
So
a
really
good
example
of
what
we
just
talked
about
the
sdks
and
application
registry.
C
You
know
the
people
saying
seemingly
they
could,
they
could
be
doing.
This
would
be
aaron
and
his
team,
and
we
tell
aaron
hey,
you
know,
we've
got
funding
available
for
this,
can
you
do
it
and
the
response
we
get?
Is
yes,
but
it's
going
to
take
a
while,
because
I
need
to
hire
more
people
or
I
have
other.
You
know.
I
can't
do
everything
all
at
once,
so
it's
been
an
interesting
shift
in
the
problem
or
the
issues
never
end.
They
just
get
moved
along
somewhere
else
in
in
that
in
that
in
that
path,
essentially,.
O
Yeah,
it's
really
true.
It's
been
interesting
like
the
start
of
this
year
was
blue
papers
and
research
and
all
that
and
then
there
was
like
a
small
lull,
but
immediately
after
that
it
was
not
necessarily
jumping
into
development.
It
was
jumping
into
like
organization
building
and
getting
to
the
point
where
we
could
actually
have
these
things
created,
because
I
mean
I
at
that
point
in
time
when
we
were
doing
the
blue
papers,
I
think
we
had
four
full-time
developers
and
we
have
three
versions
of
anchor
and
then
unicov
to
maintain.
O
So
that's
like
one
product
per
person
and
now,
if
we're
going
to
take
on
these
additional
responsibilities,
we
really
need
to
ramp
up
unless
we
abandon
anchor,
which
we
absolutely
cannot
do.
So.
It's
been
some
interesting
challenges
to
get
to
the
point
where
we
can
say
all
right:
we're
ready,
let's
go
and
get
started,
but
at
least
in
the
meantime,
we're
really
refining
those
ideas
and
getting
to
the
point
where
you
know
when
we're
at
the
start,
the
starting
position,
we
can
just
start
running.
C
C
Why
are
a
lot
of
these
initiatives
centralized
in
very
few
teams-
and
we
talked
about
this
months
ago
in
one
of
the
fireside
chats
that
aaron,
for
example,
was
wearing
seven
hats
at
the
time.
I
think
it
was
six
or
seven
that
we
counted,
and
it's
not
that
aaron
wants
to
wear
seven
hats,
it's
that
there
are
seven
hats
that
need
to
be
worn
and
there's
only
aaron
out
there,
and
so
the
problem
is
not
that
aaron
wears.
C
Seven
hats
is
that
we
need
more
people
to
be
able
to
take
on
those
responsibilities
and
that's
you
know
the
stage
of
growth
that
we're
in
right
now,
which
is
not
necessarily
a
bad
problem
to
have
we've
now
turned
you
know,
I
guess
turned
a
curve
or
we've
we've
done
somewhat
of
a
u-turn.
In
that
sense,
now
it's
creating
the
environment
so
that
more
people
can
come
more.
I
Yes,
sir,
I'm
here
so
hackathon
progressing.
We
are
at
the
ever
loved
everyone's
favorite
stage
of
lawyers
dealing
with
contracts.
I
hate
it,
but
so
we're
we're
at
the
stage
where
we're
just
reviewing
the
final
bits.
So
helios
is
working
in
partnership
with
the
enf,
so
there's
a
contract
between
us
and
then
also
between,
helios
and
devpost.
Who
will
be
the
platform
that
will
hold
this
virtual
idea-a-thon.
I
So
we've
settled
on
a
few
of
the
details,
one
of
them
being
that
it's
an
idea-thon
and
so
that
will
really
minimize
the
code
requirements
so
steph.
I
know
you
mentioned
before
that
was
exciting
to
you.
So
good
news,
that's
moving
forward,
so
the
start
date
is
still
to
be
determined,
but
basically
once
we
get
past
this
contract
stage
and
that
will
begin
about
a
five-week
timer
where
we'll
work
with
devpost
and
get
everything
populated
on
their
side.
So
it
can
be
all
up
and
running
from
their
end
and
then
the
event
will
begin.
I
It'll
be
roughly
eight
weeks
to
first
weeks
of
registration
and
if
folks
don't
have
teams,
then
we'll
try
to
help
facilitate
folks
finding
each
other.
So
they
can
have
a
good
team
and
then
six
weeks
of
the
main
event,
there
will
be
a
series
of
seminars
and
workshops
throughout
the
the
whole
duration.
The
first
one
will
be
like
a
kickstarter,
we'll
open
it
up.
Then
we'll
have
a
design
thinking
workshop
to
help
folks
think
through
how
to
how
to
design
an
application
or
a
project
and
what
are
the
do's
and
don'ts.
I
So
that
would
be
a
live
event
that
we'll
have
kind
of
running
on
on
youtube
and
it'll,
be
a
little
logistically
challenging.
But
that's
the
goal
so
it'll
be
kind
of
fun.
Hopefully
we
get
a
lot
of
engagement
and
some
live
participation
and
people
watching
folks
be
nervous,
delivering
their
pitch
kind
of
fun,
a
little
nerve-wracking,
but
hopefully
fun
still
I'll
have
an
opening
ceremony
and
a
closing
ceremony
and
yeah.
I
That's
that's
it
in
a
nutshell:
the
the
prizes
we
settled
on
75
000
for
the
total
prize
pool
so
not
a
huge
huge
amount,
but
also
very
low
barrier
to
participate.
So
we're
kind
of
factoring
that,
together,
where
we
don't
need
a
huge
prize
to
draw
people
in
to
participate
because
it's
really
easy,
hopefully
to
participate
so
the
goal.
Is
you
get
a
lot
of
the
folks
within
this
community
on
this
call
to
really
join
come
together?
I
Work
together
participate
in
these
seminars,
and
hopefully
it's
like
a
really
good
congealing
moment
and
then
also
using
the
reach
that
devpost
has.
We
bring
in
a
lot
of
new
folks
into
the
ecosystem
as
well
again
with
that
kind
of
low
barrier
to
entry
to
participate,
get
to
know
eoc
or
cio,
and
then
the
bigger
sort
of
where
this
goat
leads
to
is
future
hackathons.
I
Future
events,
where
we
kind
of
use
the
same
formula
and
then
really
branch
out
to
do
more,
tooling
and
developer
and
actually
like,
go
beyond
the
idea,
ideation
phase
and
actually
building
stuff
and
getting
it
built
out.
So
that's
the
rough
overview.
I
gave
a
lot
there,
but
hopefully
that
sounds
exciting
to
folks
and
and
kind
of
gets
get
your
brain
thinking
about
what
would
be
a
great
idea
to
bring
to
the
what
is
eos
need?
What
does
the
blockchain
world
need.
A
I
No
not
yet
so
it'll
be
sort
of
that.
The
start
I'll
know
that
we'll
know
that
once
we
get
through
this
again
beloved
contract
phase,
that
will
then
allow
us
to
sign
on
the
dotted
line
with
devpost
and
that
begins
a
timer.
Where
it'll
be
it's
a
five-week
timer
to
work
with
them,
that's
sort
of
their
requirement
to
get
everything
up
on
their
site,
and
so
and
then
after
that,
five-week
timer
ends.
The
actual
eight-week
event
begins.
I
So
as
soon
as
I
get
these
contracts
across
the
line,
I'll
have
dates
and
we'll
firm
all
that
up
and
make
sure
we
spread
that
far
and
wide
to
the
community.
So
we
know
exactly
how
that
will
line
up,
but
ideally
it's
soon
like
we
want.
I
want
this
to
kick
off
as
soon
as
possible,
so
it's
wrapping
up
by
sometime
in
august,
maybe
early
september
worst
case,
but
that's
that's,
hopefully
how
it
plays
out.
A
C
I
just
want
to
say
thank
you
to
chris,
so
the
idea
of
hosting
a
hackathon
was
brought
up
on
a
fireside
chat
multiple
months
ago
and
that
the
community
kind
of
picked
that
up.
We
had
phoenix
that
led
that
for
a
period
of
time
and
that
died
out
and
chris
really
picked
up
the
reins
and
has
been
really
pushing
this.
Towards
that
finish
line
and
chris
keeps
saying
you
know
the
contracting
phase.
The
contracting
phase
is
quite
key
to
this,
and
this
is
has
been
a
showstopper
in
the
past.
C
Somebody
needs
to
be
accountable
to
run
that
hackathon.
Somebody
needs
to
you
know
essentially
take
over
the
reins
of
that
project
management
and
give
assurances
to
the
network
that
the
funds
that
are
going
to
be
spent
will
be
properly
spent.
And
you
know
that's
what's
been
from
our
point
of
view
from
the
enf.
We
need
to
ensure
that
when
we
do
engage
with
vendors
or
with
anybody
that
we
do
so
protecting
the
eos
token
holders
and
that's
why
there's
a
lot
of
back
and
forth
on
that
front.
I
Thank
you
eve,
but
I
I
will
say
that
really
phoenix
really
did
kick
this
off,
so
we
certainly
owe
him
a
great
amount
of
debt
there
and
jesse
and
chev's
from
the
eos
bees.
They've
also
been
really
showing
up,
and
you
know
yeah,
so
they
need
a
lot
of
credit
as
well,
because
they've
been
showing
up
and
they're
going
to
help
deliver
this
event.
I
E
I
A
Can
google
translate
it
if
you
want
to
read
it,
but
basically
just
announces
that
their
users
who
hold
eos
on
that
exchange
can
now
you
know,
earn
rewards
through
a
sticking
program
which
is
nice
and
I'm
actually
going
to
read
a
tweet
by
eve
on
the
subject
from
today,
another
good
tweet
by
eve
explaining
a
bit
about
what
this
means.
So
let
me
just
pull
share
it.
A
So
eve
says:
you
may
not
realize
this,
but
bit
hum
global,
offering
eos
taking
rewards
is
a
very
big
deal.
This
will
create
a
domino
effect
that
benefits
the
eos
community
short
thread
bit
hum
is
one
of
the
two
largest
korean
crypto
exchanges.
Together
they
own
about
25
of
all
eos
tokens.
The
problem
is
those
tokens
have
been
sitting
idly
on.
Exchanges
with
no
yielding
opportunities
which
disincentivizes
eos
investment
in
the
past
korean
exchanges
have
claimed
they're
prohibited
from
offering
staking
rewards
due
to
regulatory
issues.
A
But
now
you
have
an
interesting
situation
now
that
bitcoin
global
is
offering
staking
rewards
with
yield
now
being
offered
for
staking
eos.
This
may
help
reinvigorate
the
korean
eos
community
and
push
more
exchanges
to
launch
staking
programs
of
their
own.
Remember
about
25
of
eos
tokens
are
held
by
the
korean
community.
This
is
a
big
deal.
The
question
everyone
is
wondering
is
why
now
it
seems
like
this
change
came
out
of
the
blue,
but
with
all
the
chatter
surrounding
the
new
eos
and
the
eos
comeback
story,
it
seems
appropriate.
A
So
this
is
foreshadowing.
What
will
likely
happen
elsewhere
across
the
world,
with
our
upcoming
yield,
plus
liquidity
incentive
program
expect
to
see
more
and
more
exchanges
offering
competitive
staking
rewards.
This
means
more
yield
for
token
holders
and
more
competition
to
buy
eos.
This
is
the
start
of
something
special
for
eos
major
exchanges
offering
competitive
staking
rewards
at
the
enf.
We
will
continue
to
fight
for
the
eos
community
yeah.
So
that's
really
really
nice
news
coming
out
of
the
korean
community.
P
P
So
that's
makes
up
the
bulk
of
their
yield
opportunities,
and
so
that's
why
you
only
see
them
give
a
range
of
one
to
two
percent
versus
someone
like
binance
or
or
these
other
exchanges
that
have
different
operations
or
different
staking
pools
with
you
know,
weeks
or
months
of
staking
required
to
hit
different
tiers,
but
the
other
component
to
this,
that's
so
important
is
binance,
and
I
didn't
read
the
details
of
bit
hum.
I
imagine
they
will
fall
into
the
same.
P
The
same
structure
is
that
they
will
limit
the
amount
of
participants
or
in
other
words
the
amount
of
eos.
Sorry,
if
you
can
hear
my
daughter
but
they'll
limit
the
amount
of
participating
tokens
so
that
they
can
keep
an
attractive
yield
and
that's
the
same
thing,
everyone
does
whether
it's
cfi
d5,
whatever
there's
a
finite
amount
of
tokens.
So
if
they're
earning
a
thousand
eos
a
day
in
block
rewards,
then
they
take
that
and
they
can
create
a
limitation
on
how
many
participants
can
receive
one.
P
Is
no
I
was
I
was
explaining
it.
It
often
comes
from
block
production
war
rewards.
I
saw
that
perry
who's-
usually
here,
but
not
here
today,
was
quick
to
reply
to
that
tweet.
Where
does
the
reward
come
from
and
then
he
he
responded
with
an
additional
tweet
of
caitlyn
long
she's
awesome
talking
about
leverage,
and
that's
really
really
nothing
to
do
with
where
these
staking
rewards
come
from.
C
So
I
I
don't
know
where
these
staking
rewards
are
coming
from.
What
I
do
know-
and
I
guess
this
is-
is
relevant
to
your
your
question
or
the
comment
that
you
made
is
that
the
regulatory
landscape
in
south
korea
is
quite
particular
and
it
has
been
being
tested
and
it
is
pushing
the
limits,
especially
as
we
see
with
what's
been
going
on
with
or
what
happened
with
terra
and
dope
one.
C
C
D
C
That
that
they're
offering
yield
on,
I
believe
those
are
the
only
tokens
that
they
offer
yield
on.
So
this
is
the
first
time
a
korean
exchange
offers
yield,
so
it's
not
like
they
had
yield
before
on
bitcoin
on
ethereum,
as
do
other
exchanges.
This
is
bit
hum
saying
we
are
now
going
to
test
the
regulatory
waters
within
korea
and
we
are
willing
to
do
that
with
eos.
As
the
first
accent.
This
is
monumental.
C
P
P
P
C
P
Exactly
I
call
on
that
right,
so
so
that's
not
what
their
end
user
agreement
says
it.
It
does
say
that
they
are
opening
the
possibilities
to
to
doing
validation
work
and
when
I
hear
that
I
hear
they're
going
to
start
reaping
reward
from
the
network
and
I'm
not
none
of
this
has
any
ulterior
undertones.
P
P
C
C
P
Right,
it's
it
it's!
I
only
highlighted
up
bit
there
because
for
some
reason,
I'm
a
proponent
of
the
koreans
pushing
around
this
this
change.org
thing,
because
it
is
something
they
seem
in
the
their
telegram
groups
to
be
excited
about,
and
I'm
I'm
for
that.
Whatever
gets
any
community
excited
about
something
in
eos
great.
C
And
so
I'm
wondering
how
that's
going
to
impact
the
developer
conference
that
I've
been
invited,
potentially
invited
to
or
invited
to
speak
at,
but
potentially
have
a
spot.
I
wonder
if
then,
the
narrative
and
what
they
want
to
discuss
will
change
by
the
time
september
comes
around
yeah.
I,
as
as
you
say,
as
well.
I'm
a
big
part
of
why
I'm
excited
about
this.
Is
it's
more
talk
of
the
eos
more
people
getting
excited
about
eos,
for
whatever
reason
it's
just
more
eyes
on
yours.
P
E
Well,
I
anticipate
that
the
on
chain
yield
will
be
better
than
one
to
two
percent,
so
just
from
the
yield
plus
incentive
program,
it's
essentially
a
five
percent
yield
on
the
eos.
So
what
the
d5
protocols
do
with
with
that
yield
is
up
to
them,
but
if
they're
passing
it
all
back
to
their
users,
for
example,
then
it
would
be
a
five
percent
yield.
E
So
that's
the
idea
with
yield
plus
is
so
it's
nice
to
see
that
these
exchanges
are
adding
a
little
bit
of
a
yield,
because
obviously
any
percent
is
better
than
zero
percent,
but
the
the
idea
is
still
to
move
the
activity
on
chain.
So
that's
very
much
part
of
the
yield
plus
initiative,
but
it's
nice
to
see
opportunities
presenting
themselves
to
people
who
didn't
have
that
opportunity
before
because
of
the
travel
restriction
or
that
I
figured
it's
called
the
travel
joe
help
me
out
here.
P
Quite
a
honors
barrier
for
people
to
try
and
hustle
around
to
to
pull
their
money
so
that
that
is
another
upside
to
these
staking
opportunities
on
exchange
is
for
these
people
that
aren't
going
to
go
through
that
effort
of
kind
of
hopping
exchanges
and
trying
to
withdraw
under
certain
limits,
and
you
know
the
people
will
do
that
and
collect
higher
yield
for
it.
But
it's
great
that
some
people
can
that
are
not
up
for
that
kind
of
effort
will
be
able
to
do
it
on
the
exchange
platform
itself.
E
I'm
noticing
there's
no
there's
no
lock
up
on
these
yields,
yet
so
it'll
be
interesting
to
see
if
they
incorporate
that.
That's
part
of
the
reason
binance
offers
some
good
yields
is
because
they
have
they
separate
the
pools,
so
they
have
like
flexible
staking.
They
have
like
one
month,
lockups
and
three
three
month
or
100
day
lockups,
and
they
they
wait
heavier
towards
those
willing
to
lock
up
longer.
E
C
E
E
A
A
I
before
we
get
in
here.
Let's
see,
let's
see
a
vote,
let's
see
a
vote
in
the
in
the
voice
chat,
not
the
stream
chat,
but
the
voice
chat,
which
has
been
pretty
active
today,
which
is
great,
let's
see
about
one,
if
you
think
it
was
not
sarcastic,
it
was
just
legitimate
and
zero
if
you
think
it
was
sarcasm,
what
about
the
it
doesn't
matter?
H
Q
E
I
I
E
E
E
C
P
J
Actually
yeah,
I
I
kind
of
agree.
I
think
it
was
a
good
move
to
not
really
react
to
anything
and,
just
you
know,
cool
yeah.
Well,
here's
here's,
some
facts
and
here's
some
interesting
things
going
on
and
not
being
like.
Oh
well,
hey
thanks,
bud
or
or
hey.
That's.
You
know
screw
you
for
whatever
no
just
neutral
approach
and
then
overload
with
information.
S
S
S
P
D
S
L
B
A
So
I
shared
I
shared
eve's
tweet
here
in
the
in
the
voice
chat,
I'm
not
gonna,
I'm
not
gonna
read
it
out,
but
it's
a
really
good
recap
of
basically
a
lot
of
the
things
that
have
been
going
on
lately
in
the
ecosystem
and
of
course
it
was
absolutely
great
opportunity
for
us
to
get
in
there
and
share
all
the
great
progress.
That's
been
going
on
to
the
wider
crypto
space
while
we
have
their
attention.
So
definitely
a
big
win
overall
this
week
for
eos
on
social
media
through
this
tweet,
regardless.
A
A
P
P
L
Depends
on
the
implementation
of
the
finality,
which
I
think
is
very
interesting-
I'm
not
saying
that!
That's
something
that's
going
to
happen
specifically,
but
depending
on
the
implementation
of
finality,
it
might
not
matter
how
many
block
cruises
there
are
to
reach
finality
as
long
as
there's
something
which
moves
towards
it,
though
it
could
be
more
than
that
or
it
could.
P
P
D
R
L
No,
I
was
just
saying
that
zach
was
saying
in
one
of
the
chats
that,
in
one
of
our
internal
chats
that
a
round
table
with
some
of
the
core
developers,
the
protocol
developers
would
be
really
good.
And
I
think
that
what
you
just
said
jolo
is
how
this
stuff
excited
you,
because
this
is
stuff
that
nobody
really
talks
about
outside
of
the
protocol
developers.
L
And
it's
barely
been
publicized
in
the
time
that
eosio
has
been
a
thing,
is
something
that
we
can
probably
change,
and
it's
probably
very
interesting
to
a
lot
of
people,
because
we
developers
might
not
think
it's
interesting
to
a
lot
of
people
outside
of
developers.
But
you
are
elucidating
that
it
is
actually
quite
interesting
for
people
who
are
just
in
the
ecosystem.
E
E
P
P
E
On
the
team
is
very
github-oriented
doing
things
out
in
the
open,
because
it's
the
opposite
of
what
used
to
happen
with
the
like
official
repo,
for
example,
there's
a
lot
of
nuggets
there.
Now
I
mean
even
with
the
grant
framework,
for
example,
the
grant
framework,
I
think,
was
public
on
the
github
for
two
weeks
before
we
actually
announced
it.
So
if
anyone
ever
wants
to
be
little,
do
some
detective
work,
the
github
is
always
a
fun
place
to
hang
out
and
take
a
piece
right.
P
P
P
B
C
C
M
C
A
All
right,
I
think,
we're
gonna
leave
it
there
we're
gonna,
wrap
up.
This
show
thanks
everyone
for
joining
the
eos
community.
Fireside
chat
this
week
and
tune
in
next
week,
like
brandon
hinterat,
will
hopefully
have
guillaume
on
here
to
talk
more
about
these
eat
proofs
and
more
more
of
that
stuff
and
next
week.