►
From YouTube: EOS MANDEL Meeting #4 (March 2nd 2022)
Description
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37
#eos #mandel
Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// 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
All
right
welcome
everybody.
This
is
the
fourth
check-in
call
for
the
mandel
upgrade
it's
march,
the
second.
So
far,
I've
only
added
one
new
item
to
the
agenda.
Since
our
last
call,
this
was
brought
up
by
the
the
guys
from
node
one,
a
suggestion.
Perhaps
it's
time
that
we
have
our
own
developer
portal,
this
might
fit
in
with
the
assembled
developer
and
node
operator
resources
work,
that's
ongoing.
Maybe
it's
something
else
so.
B
We
just
to
confirm,
I
believe,
last
week
when
we
met
it,
wasn't
complete
yet,
but
we
did
sign
a
essentially
a
contract
with
oci.
I
see
that
a
few
of
them
are
online
and
they
will
be
working
on
api
transaction
life
cycles
and
adding
that
into
mandel
3.1,
so
that
is
now
confirmed
and
the
ball
is
rolling.
B
I
believe
we've
got
brian
on
the
line
and
we,
I
did
also
get
confirmation
from
dan
that
his
team
is
bypassing
2.3,
so
they're
no
longer
going
to
2.3
road
approach
and
they've
already
started
working
on
3.1,
including
the
diffuse
component.
So
essentially,
we've
got
cooperation,
we're
good!
That's
where
we're
that's,
where
we're
heading
and
the
enf
also
just
secured
three
developers
that'll
be
able
to
help
out
on
our
and
if
there's
anything
they
should
be
starting
roughly
beginning
of
april.
B
B
B
That's
not
found,
let's
say
the
block
one
repo
and
that's
a
soft
fork
type
of
of
change,
and
so,
if
that
inherently
is
enabled
or
it's
a
function
that
is
present
in
the
release
that
we're
let's
say
using,
then
inevitably
it
means
we're
not
on
the
block
one
repo.
So
that
means
the
consensus.
Upgrade
side
of
things
could
occur
later
on
it
wouldn't
need
to
occur
early
at
the
onset,
so
everybody
would
be
able
to
upgrade
from
2.1
or
2.0
to
3.1
or
whatever.
B
D
B
D
What
I
was
thinking
for
just
wanted
to
make
sure
that
that's
what
you
were
intending
you
know
not
to
have
us
that
the
window
for
for
changes
and
then
the
final
release
will
be
a
month
aft
or
within
a
month.
After
that
sure.
B
D
A
B
B
If
I'm
not
mistaken,
like
they've
been
there
since
2.1
and
some
of
them
since
2.0,
we
still
have
functions
in
1.8
that
we
never
turn
on,
because
they're,
useless
or
because
the
market
has
deemed
that
their
uses
or
developers
has
seen
that
they're
useless.
The
idea
with
the
consensus
upgrade
was
to
practice
and
to
use
that
as
a
means
to
to
to
re-grease
the
wheels
and
and
to
get
back
into.
D
B
For
what
happens
when
we
do
need
to
go
through
a
consensus
upgrade
so
that
we
could
plan
for
that's
an
arbitrary
date
we
could
say
fall
again.
We
can
say
september
that
there's
no
particularly
need
for
them.
Unless
things
change
and
developers
do
say,
actually
there's
a
function
that
we
now
need,
or
a
business
comes
about.
For
example,
fractally
says
we
need
this
particular
function
for
our
application,
so.
A
B
Else
has
a
different
viewpoint.
Go
for
it.
That's
just
my
understanding
from
speaking
to
to
a
lot
of
the
stakeholders,
developers
in
particular.
E
That's
quite
correct:
the
issue
2.1
features
are
not
compatible
with
mandel
features,
but
we
don't
have
them
anyway
in
the
network.
So
we.
F
B
With
2.1
the
two
that
you
mentioned
that
aren't
compatible
and
that
are
new,
can
you
elaborate
on
those,
and
I
guess
do
you
need
them?
Is
that
is
that
something
that
you
that,
for
example,
for
fractally
you
would
need,
and
so
that
would
accelerate
the
time
that
you
would
prefer
having
the
consensus
upgrade
happen.
F
B
B
The
hard
forks
are
strictly
needed;
it
just
makes
things
easier.
So,
on
a
I
mean
I'll,
ask
it.
I
guess
a
different
way
on
a
scale
of
one
to
ten.
How
pressing
is
it
to
turn
on
those
features?
In
your
opinion,
I
won't
hold
you
to
it.
I'm
just
trying
to
get
a
sense
of
how
important
are
these
because
other
than
than
you,
I
guess
nobody
else
has
asked
for
these
features.
F
B
F
B
But
if
we
work
towards
deployment
testing
and
the
majority
of
the
block
producers
upgrading
to
3.1
end
of
june
july,
that
time
frame-
let's
say
august,
so
it
takes
a
while
before
everybody's
there.
Typically,
the
block
producers
will
will
do
it
in
waves,
they'll
coordinate
to
make
sure
that
one
or
two
are
using
the
latest.
3.1
like
matthew
from
the
us
nation
will
typically
be
the
first
one
and
then
it'll
go
on
on
purpose.
This
is
this
is
the
idea
until
everybody's
done?
B
We
see
that
historically,
it's
about
a
two
month
process
give
or
take
that
would
bring
us
say
conservatively
to
the
end
of
august
end
of
august
everybody's
running
3.1
or
give
or
take
everybody's
running
3.1
at
the
broad
producer
level.
Then
we
could.
That
process
would
be
obviously
public.
Everybody
knows
what's
going
on,
we
can
still
aim
towards.
I
mean
now
would
be
six
or
seven
months
early.
B
We
can
aim
towards
saying
let's
turn
on,
for
example,
that
wasn't
configurable
wasn't
a
limit
function
in
september,
and
that
would
be
we
could
even
say
september
23rd,
which
would
be
a
symbolic
date
from
when
we
did
the
last
hard
fork.
I
mean
that
gives
us
six
months
to
work
towards
something,
and
I'm
not
necessarily
sticking
to
that
date,
but
that
would
give
us
half
a
year
heads
up
working
towards
something.
Would
that
seem
reasonable
for
you,
stephen
on
your
end
and
anybody
else
on
the
call
like
there's
anybody.
G
In
my
mind,
the
biggest
concern
there
is
just
making
sure
everybody
is
aware
before
you
turn
on
a
feature
that
forks
out
2.0.
Of
course,
I
o
you
know
just
so
everyone's
aware,
you
know
and
prepared
for
when
that
happens,
because
you
enable
that
particular
protocol
feature
or
any
either
one
of
those
two
that's
not
compatible,
or
even
one
of
the
two
one
2.1
protocol
features.
B
Surprised,
so
that's
why
we're
having
these
weekly
calls.
Originally,
the
idea
was
to
do
let's
say
that
consensus
upgrade
mid-may,
and
so
now
we've
we've
delayed
that
by
a
few
months,
but
we're
still
having
these
calls
we're
still
talking
about
it
right
now,
we've
still
started,
we've
already
started
talking
about
that
process.
B
G
B
Well,
the
process
has
effectively
already
started
right,
so
this
is
what
we're
already
doing.
So
to
me,
that
sounds
extremely
conservative.
I
I
really
don't
see
why
we
wouldn't
be
able
to
hit
that
date,
seeing
as
that
we're
six
months
ahead
of
the
time
and
already
having
these
weekly
calls
and
already
communicating
this
information.
One
thing
to
keep
in
mind.
A
Actually
running
so,
we've
got
a
pretty
good
plan
there
that
we,
you
know
we
did
the
same
thing
for
the
1.8
upgrade
on
the
agenda
for
today,
we'll
be
checking
in
on
our
progress.
We're
assembling
all
of
the
developer
resources,
nice
little
package
for
all
the
exchanges
and
developers
on
hey
here
are
the
impacts.
A
Here's
what's
coming
and
here's
when
you've
got
to
be
upgraded
by
otherwise
you're
going
to
have
a
bad
time,
we're
going
to
we're,
putting
together
a
survey
as
well,
so
that
they
can
respond,
and
let
us
know,
first
of
all,
that
they
can
acknowledge
they've,
received
it
and
give
us
input
on
whether
they're
running
a
node.
That
would
be
impacted
and
we're
also
in
the
process
of
actually
pretty.
I
think
we
we've
almost
completed
this.
A
We've
got
a
database,
we've
been
working
with
the
eos
support
team
and
we've
got
an
intern
on
the
eos
nation
team.
Who's
been
creating
a
database
of
all
of
the
eos
dapps
and
all
of
the
exchanges,
and
we've
got
a
contact
for
each
of
them
and
we're
going
to
be,
you
know,
sending
out
all
of
these
resources
and
and
getting
them
to
fill
up
those
surveys.
So
we'll
make
sure
everyone
is
well
aware
that
this
is
coming
and
and
that
we
have
a
good
sense
of
the.
B
Status
when
we
we've
been
having
the
discussions,
as
well
with
with
jungle
for
example
and
kyleen
so
like
the
whole
process
now
is,
is
already
under
works.
So
if
we're
going
to
be
doing
the
consensus
upgrade,
let's
say
september
23rd,
and
that
would
have
that
configurable
wasm
limits
and
wasn't
doesn't
have
the
second
a
it's
just
wsa.
I
was.
B
I
had
a
feeling
that
might
have
been
the
case,
but
this
would
would
it
would
make
sense
to
if
we
have
other
functions
to
turn
them
all
all
at
the
same
time.
So
we
don't
do
multiple,
which
is
the
other
one,
the
get
hash
one
stephen
or
is
it
a
separate.
F
One
yes,
the
other
new
one
is
the
get
code
hash.
F
Then
the
ones
from
2.1
are
the
action,
return,
value
and
configuration
additional
and
how
to
a
separate
hard
fork
for
configuring.
B
That,
and
do
we
are
those
people
on
the
call.
Are
those
functions
also
functions
that
we
wish
to
turn
on
so
sometimes
again,
like
I
said,
we've
chosen
not
to
turn
on
functions
because
they're
not
needed
and
or
nobody's
asking
for
them
and
or
it
can
cause
issues
if
if
we
do
turn
them
on
and
we
don't
maintain
them
or
we
don't
just
turn
on
functions
to
turn
on
functions,
do
you
in
your
opinion,
should
we
turn
on
those
functions
and
and
stan?
I
guess
you're
muting
yourself
to.
E
Yeah,
the
code
hash
is
important
for
contract
security
because
you,
as
a
contract
author
or
contract
maintainer,
you
can
certify
other
smart
contracts
that
you
working
against
smart
contracts
that
you
know
because
you
certify
their
hashes
because,
right
now
you
send
your
inline
actions
to
other
contracts.
You
don't
know
what
what's
going
on
on
the
other
side,.
I
B
I
Yes,
basically
stop
sending
there
any
transactions
if
it
doesn't
comply
with
with
what
you
know
about
it.
What
about
the
two
other
functions,
and
maybe
you
want
to
write
them
down
daniel
yeah.
E
I
don't
know
how
important
it
is.
Some
people
want
this
because
it
just
improves
the
functionality
that
you
can
use
on
a
blockchain.
F
B
G
So
the
return
value
is
also
useful
for
the
new
feature
that's
going
in
with
the
api
changes
you
have
a
read-only
transaction
and
so
one
of
the
ways
to
get
the
data
out
from
that
read-only
transaction
is
via
a
return
value.
It's
very
it's
a
very
easy
way,
as
opposed
to
like
console
output,
which
is
kind
of
the
hack
that
people
have
used
before
before.
Getting
the
information
out
or
put
put
it
in
an
assert
message,
which
is
even
more
of
a
kind
of
a
hack.
G
So
it's
just
a
nicer
way
so
that
that
certainly
would
would
have
my
vote
for.
G
And
then
for
the
other
two,
the
wasm
configuration
and
the
blockchain
configuration.
Those
are
very
useful.
I
think
I
I
think
they'll
be
turned
on
just
everyone
needs
to
know
that
they
need
to
be
very
cautious
with
those
like
you
would
never
want
to
to
ever
change
any
of
those
values
without
first
doing
it
on
a
test
change,
because
you
can
brick
the
chain,
if
you,
if
you
screw
up
the
values
like
you,
there's
like
you,
can
shoot
yourself
in
the
foot
with
those.
F
G
Them
so
low
that,
like
you,
can't
ever
fix
it,
no
that
that
is
forbidden
well
for
the
for.
F
F
A
A
F
G
A
B
Said
august
is
when
we
want
to
sorry
well,
because
it's
just
a
regular
update,
essentially
it's
it's
whenever
it's
ready
and
the
blog
producers
start
doing
it
one
by
one
right
it
I
mean,
and
we're
no
longer.
A
Right,
okay,
I'm
gonna
just
leave
that
for
now
next
up
test
mandel
on
jungle-
four,
I
don't
know
if
there's
much
to
discuss
besides
you
know,
I
see
that
block
producers
have
begun
registering.
Thank
you.
I
know
that
our
team
hasn't
registered,
yet
we
should
be
registered
before
the
next
call,
but
it's,
I
would
just
say
it's
we're
on
track.
A
number
of
we've
got
a
very
good
number
who
have
joined
and
once
we've
you
know,
we've
got
enough.
A
B
I
think
it's
it's
also
important
to
note
in
the
communication
that,
because
we're
changing
the
the
tentative
date
was,
let's
say
march
may
19th
and
now
we've,
let's
say,
moved
it
to
september
23rd
as
a
draft
that
is
essentially
four
months
later,
but
the
difference
in
what
you
get
by
then
is
significant
compared
to
what
we
were
getting.
Let's
say
on
may
19th
and
may
19th
was
was
just
for
the
current
functions,
essentially
with
that
with
that
twist,
with
the
wasm
limits.
B
But
what
we
get
slightly
later
is
much
more
upgraded
and
then
what
we
get
four
months
later,
let's
say
that
september
23rd
is
significantly
different
than
what
we
were
getting
in
may
right.
F
B
A
And
is
that
an
impact
on
testing,
I
guess
we're
going
to
have
more
testing,
I
guess
to
do
than
what
we
originally
were
scoping
out
for
to
do
since
there's
new
features
that
we're
not
as
familiar
with.
No,
I
wouldn't
say
that
to
be
the
case.
Okay,
so
I
have
I've
updated
some
we've
we're
we've
got
our
one
path
now,
so
I've
removed
our
nothing
hell.
I
guess
changes
here
now
that
we've
set
on
our
3.1.
B
B
Side
which
I'm
not
entirely
certain
of
at
this
point,
so
we
did
talk
about
last
week
and
I
think
stan
started
inputting
issues
in
the
github
fixes
that
are
currently
found
in
2.1
point
x
on
the
block.
One
repo
and
okay.
B
It
up
so,
if
we
put
those
in
then
that
might
change
the
timeline
for
the
3.1
portion
fixes
that
are
currently
addressing
challenges.
I
think
might
see
michael,
like
praying
fixes
that
are
currently
fixed
right
now,
but
that
weren't
in
the
3.0
release
candidate,
but
that
are
out
that
are
tested
that
essentially
would
just
put
in
the
3.1
they're,
already
written
out,
they're
already
even
been
tested
and
or
live.
Okay.
F
So
after
last
week
I
created
a
pr
that
merges
all
the
changes
in
the
2.0
point
x:
okay,.
A
Yeah,
it
sounds
like
maybe
there's
an
opportunity
here,
so
originally
we
had
planned
to
upgrade
from
2.0
to
3.0,
mainly
just
because
of
time
like
we
were.
You
know
up
against
that
tight
may
target
and
we
didn't
want
to
waste
time
waiting
for
3.1.
We
want
to
start
testing
the
features
now
that
we've
got.
A
E
B
A
A
Mean
yeah,
we
didn't
upgrade.
E
Right
now,
jungle's
still
on
2.0,
we
didn't
have
great
producers
on
the
whole
jungle
network
yeah.
So
we
can.
I
don't
know
if,
if
rc2
is
coming
out
within
days,
it
makes
sense
to
wait
for
it
and
also
the
the
thai
constraints
on
crypto
alliance
side,
because
they're
in
the
middle
of
a
war
now
right
so.
D
E
Might
not
be
available
so
yeah.
We
need
to
give
them
probably
more
time
to
set
up
everything
and
accept
those
vp
registrations
updated
so
yeah,
but
I
mean
if
those
mergers
are
available.
Maybe
let's,
let's
make
our
seat
so.
A
G
Remind
me
we
just
are:
it
was
decided
that
we're
not
doing
a
a
mandel
version.
That's
compatible
with
eosio
2.1,
correct
three
point:
one
will
be.
I
A
G
F
G
Being
dense,
I
guess
I
I'm
still
not
clear.
It's
still
not
clear
in
my
mind,
so
there's
esio,
2.0
and
2.1
2.1
has
a
number
of
things
in
it
that
I,
I
don't
think
the
community
needs
or
will
ever
want
right
since,
for
example,
transaction
pruning
in
a
new
transaction
format
and
a
new
block
format.
G
E
G
We're
good,
okay,
so
we're
planning
on
getting
the
features
we
want
by
backboarding
them
to
to
mandel,
as
opposed
to
cutting
another
branch
off
of
bsio.
Correct,
correct,
okay,
2.
G
A
C
An
engineer
that
said
they
would
kind
of
do
this
for
us,
but
they
recently
were
hospitalized,
and
so
they
said
they're
running
about
a
week
or
two
behind
on
it.
We
did
find
some
stuff,
that's
in
the
old
block,
one
repository,
but
it's
not
quite
the
dockers
and
they
discontinued
making
docker
images
available,
etc.
But
all
we're
looking
for
here
is
the
documentation
on
how
to
take
a
docker
image.
I
think
another
issue
we
should
decide
is:
are
we
going
to
pre-build
docker
images.
D
C
Our
core
set
of
of
you
know
ubuntu,
18,
whatever
and
and
and
20
version
2004
and
1804,
and
make
those
available
along
with
the
documentation.
But
the
engineer
I
talked
to
is
willing
to
just
write
the
documentation
for
us
and
it's
again
just
hospitalized.
So
he's
running
a
little
bit
behind.
Okay,.
A
E
Packages
are
always
needed,
they
just
need
to
be
verified
and
coming
from
trusts
or
trustful
source,
but
everyone
isn't
storing
those
different,
but
I
mean
except
exchanges
which
compile
everything
from
sources
because
of
security,
most
users
or
operator
system
operators.
They
they
download
different
packages
from
blockchain
repository
now.
So
we
need
to
provide
this.
This
kind
of
so.
C
Stan
you're
saying
they
people
don't
want,
so
this
might
have
been
driven
by
developers
wanting
docker
images
for
front-end
developers
and
you're
you're.
Adding
an
additional
requirement
stand
saying
more
of
the
block.
Producers
would
prefer
debian
packaging
like
a
dead
package
that
they
can
just
run,
but
which
group
wants
the
debian
packages,
because
you're
saying
the
block
producer.
E
C
E
Every
system
administrator
who
needs
to
install
an
eos
node
needs
different
packages
because
maybe,
like
five
percent
of
nodes
are
compiled
from
sources
because
of
security
concerns
like
on
a
block
producer
normally
compiled
from
sources.
If
you're
in
exchange
you
your
your
transact,
I
mean
you
operate
with
financial
data.
You
need
to
compile
from
sources
everywhere
else.
People
just
download
the
binary
dividend
packages
got
it
installed
because
it's
like
it
takes
five
minutes
to
install.
C
The
clarity
debian
packages
are
what
ubuntu
uses
anyway,
so
we're
staying
we're
staying
within
our
ubuntu
classes
of
what
machines
will
support,
but
so
I
think
we're
adding
to
docker
we're
also
saying
we'd
like
debian
packaging
as
well.
Okay,.
E
C
Was
asked
for
by
other
groups
we're
saying
they?
You
know
the
front-end
developers
and
smart
contract
developers
were
saying
you
know
I
don't
necessarily
want
to
run
the
whole
chain
or
I
might
be
on
a
windows
machine
or
on
a
mac
or
whatever
just
give
me
a
docker
image,
I'll
toss
that
on
and
then
I
can
work
on
my
smart
contract.
So
it's
a
it's
a
different
use
case
scan.
So
we
probably
if
we
can,
you
know,
provide
both
and
it's
also
to
help
new
people
start
to
work
in
the
eosio
environment.
C
H
C
A
A
Right,
okay.
Does
that
sorry,
we're
clear
here
now,
thanks
for
the
update,
we're
still
I
don't
know,
do
you
have
anything
any
progress
to
report
on
the
the
dev
resources,
you're
working
on
stan
I've
been
sick
and
I
I
didn't
no.
C
A
All
good,
I
gave
a
little
update
on
our
progress.
Like
I
said,
we've
got
a
pretty
good
database
of
exchanges
and
apps,
as
well
as
contact
information
for
them
so
we'll
once
we
have
our
our
whatever
we
need
we're
going
to
do
the
survey
and
and
kind
of
a
nice
package
explaining
everything
we
can.
We
can
hit
them
all
individually.
A
I
don't
think
there's
anything
new
to
report
here.
I
understand
blocks
is
now
available
on
kylin
and
again,
thank
you,
yeah,
michael
for
getting
your
hyperion
set
up.
That
was
what
enabled
that
and
I'm
not
sure
again.
I
think
we
had
identified
possibly
something
that
rio
is
going
to
have
to
do
in
the
longer
term.
H
A
A
H
A
H
May
not
be
best
to
be
titled
like
that.
Does
that
make
sense
kylan's
the
explorer
is
running
it's
more
history
in
general,
you
know
to
adapt
to
all
the
new
3.1,
whatever
reader
codes,
blah
blah
blah
blah.
So
I
don't
want
to
speak
for
igor,
but
I
think
it
was
much
bigger
down
the
road
things
are
running.
Fine.
A
Right
for
our
for
our
needs
for
testing
on
kailan
we're
we're
set
cool.
Let's
see
anything
here
to
discuss
enough.
No,
no
progress
on
the
survey,
I'm
still
coordinating
with
folks
on
kyland
we're
gonna
next
up
will
be
to
activate
powerup.
B
B
B
You
think
so
stan
I
would
be
okay
with
them
joining
these
calls
most
people
on
these
calls
just
listen
in
and
they
don't
necessarily
chime
up.
Unless
there's
anything
yeah,
we
can
invite
them,
of
course,
for
future,
I'm
specifically
the
eos
channel,
because
we
might
have
applications
in
there
or
people
building
and
yep.
I've
been.
A
Until
we
have
our
like
that
package,
like
hey
here's
everything
you
need
to
know,
but
there's
I
don't
think,
there's
harm
in
starting
that
getting
the
ball
rolling.
Can
I
let
him
know
hey
we're
having
these
calls
if
you're
curious
feel
free
to
watch
the
recording
and
and
our
meeting
summary
notes
and
join.
If
you
like-
and
you
know
we'll
have
more
details
to
come
in
in
our
package
of
resources
but
yeah,
that's
good
feedback
I'll
start
doing
that
going
forward.
A
The
developer
portal-
I
don't
have
anything
in
this
issue,
yet
it
was
raised
as
feedback
that
we
might
need
one
right
now.
I
guess
block
one
manages
the
developer
portal
and
it's
pretty
outdated
and
I
imagine
once
we
upgrade
they're
not
going
to
be
updating
their
resources
to
indicate
mandela
exists
or
any
of
that
stuff.
K
A
K
Have
a
background
that
is,
I
often
get
the
request
from
the
developers
from
the
community,
that
is
there
any
updated
resources
or
some
example
samples
or
training
resources
or
on
some
localized
contents
there.
So
I
was
not
sure
somebody
is
there.
Somebody
dedicated
person
for
the
documentation
in
enf
or
some
fractality
team.
So
I
was,
I
was
asking
you
and
then,
if
there's
no
people
then
no
person
to
dedicate
it
for
the
documentation,
then
maybe
it
will
be
the
community's
job.
I
think.
A
B
E
We
in
the
core,
plus,
we
indicated
a
whole
set
of
tasks
and
jobs
for
for
information
management,
information,
delivery,
creating
content
creation,
so
that
is
coming
up
as
soon
as
we.
So
now
we
have
paper.
Delivery
is
still
on
reviews
and
then
then,
as
soon
as
the
budgets
are
getting
allocated,
and
we
need
to
hire
people
to
actually
produce
this
content
so
that
that
is
coming.
That
is
covered.
At
least
there
is
a
roadmap
for
that.
B
So
we're
currently
in
the
feedback
cycle
for
the
blue
papers.
I
I
apologize,
I'm
not
sure
how
you
pronounce
your
name
june
hunk
or
that's
what
I'm
seeing
if
you
would
like
to
provide
feedback
on
the
the
blue
papers,
that
specific
one
that,
I
think
would
be
what
you're
looking
at
would
be
the
core
plus
blue
paper.
B
So
if
you
want
to
participate
in
that
feedback
or
if
you
think,
there's
something
missing,
I
invite
you
to
go
through
that
feedback
process
once
that
feedback
process
is
done
is
when
the
enf
will
gather
the
feedback
essentially
create
a
new
community,
enhanced
version,
if
applicable,
if
we
do
receive
feedback
and,
and
then
with
the
original
authors,
we
do
back
and
forth
and
we
deem
they
deem.
Essentially
that
should
go
in
and
then
we'll
start
allocating
work
based
on
that
feedback.
B
And
so,
if
you
think
that
this
should
be
addressed,
then
I
invite
you
to
go
participate
in
that
process.
Okay,
see
and
that-
and
that
applies
to
everybody
else,
on
the
call
as
well.
If
in
the
blue
papers,
there's
anything
that
either
you
think
was
missed
and
or
anything
that
was
addressed
and
that
you
really
want
to
see,
I
invite
you
to
participate
in
that
process.
A
Great,
so
I
guess
so
yeah
we'll
cut
consider
this
covered
outside
of
scope
of
this
and
I'll
call
it
done.
We
had
one
other
item
we
wanted
to
talk
about
that.
I
think
it
was
kevin
who
brought
up.
Where
did
my
security?
G
Yeah,
so
I
don't
think
just
but
to
really
to
say
here
I
mean
mid
mid-march
enough:
we'll
have
the
certainly
we'll
have
the
resources
to
handle
anything
that
might
come
up,
but
before
then
certainly
feel
free
to
reach
out
to
me.
If
anything
would
happen
to
happen,
and
you
need
some
need
some
support
there,
I'm
happy
to
help.
A
So
this
is
in
the
event,
so
what
I
understand
you're
offering
is,
in
the
event
we
run
into
any
security
issues
through
this
process.
A
G
I'm
happy
to
help
there.
You
know
I'm
sure
dan's
team
might
be
available
as
well,
though
I
certainly
don't
speak
for
his
team,
but
for
myself
I
can
speak.
You
know
if
you
need
some
help.
Let
me
know.
E
Awesome,
it
is
already
happening
actually
on
lux.
We
are
in
the
middle
of
troubleshooting
some
potential
security
concern,
so
it
is
happening
already.
Kevin
is
helping.
A
Okay,
do
anything
else
we
need
to
basically
hey.
We
know,
we
know
kevin's
our
man
if
something
happens,
call
kevin
and
everyone,
I
think,
knows
how
to
contact
kevin.
If
we
need
him
yeah,
we've
got
the
ghostbusters
phone
or
batman
type
of
single
yeah.
Great.
Thank
you
kevin.
I
think
that
covers
everything
on
the
agenda.
H
There's
one
thing
I
was
gonna
have
missed
on
the
kyle
and
faucet.
That
was
the
to
do.
I
don't
know
if
they're
calling
fawcett's
been
fixed,
but
I
got
a
bag
of
kylin
tokens.
I
went
and
claimed
like
three
years
worth
of
bpay,
so
I'm
around
and
I've
got
like
a
quarter
million
eos
over
there.
So
I'm
rich
if.
D
H
Needs
anything,
at
least
in
the
stop
gap
like
say
I
was
shoot,
I
shot
like
10
000.
You
know
it's
over
to
or
something,
but
that
may
be
a
good
stop
gap
and
at
least
I
take
some
pressure.
I
don't
know
who
runs
that
I
don't
even
remember.
A
Yeah
so
I've
I've
been
chatting
with
them
and
we're
yeah.
So
turning
on
the
faucet
activating
power
up,
we're
coordinating
that'll
that'll
come
hopefully.
B
H
There
you
go
great,
I'm
producing
a
lot
of
blocks.
I
can
keep.
I
keep
that
faucet
going
a
long
time
if
you
need
them
by
all
means.
B
You
can
have
them
that
means
you're
doing
something,
and
that's
that's.
That's
really
good,
actually,
because
kylian
historically
has
been
a
very
decentralized
and
it
is
kind
of
tricky
because
we
don't
have
a
potential
source
of
a
lot
of
tokens,
whereas
jungle
has
been
a
little
bit
easier
in
that
front.
So
thank
you
very
much
for
that.
A
Yeah,
great
okay,
anything
else,
oops.
Okay,
in
that
case,
I'm
happy
thanks.
Everyone
for
joining
we'll
see
you
again
in
a
week
I'll
put
out
the
recap
and
we'll
have
a
video
edited
to
share
with
the
community,
probably
the
next
day
or
two
thanks
everybody.
Thank
you.
Everybody.
Thank
you
guys.
Thank.