►
From YouTube: Instant Finality Leap Integration Status, Deferred Transactions Phase-out & More! August 16th, 2023
Description
The EOS Node Operator Roundtable meets every Wednesday at 14:00 UTC to share and discuss feedback to improve the Antelope protocol.
00:00:00 Instant Finality Leap Integration Status: September Target with Potential Delays
00:02:32 Deferred Transactions Phase-out: The Why and How of the Upcoming Change
00:03:28 Technical Steps for Node Operators: Disabling Deferred Transactions
00:21:14 Coordinating and Communicating with Key Stakeholders
00:35:48 Other node features with config
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://www.eosnetwork.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #Web3
A
B
So
the
first
update
is
that
we
are
still
exploring
possibilities
to
try
and
bring
in
this
date
for
the
instant
finality
leap
integration
Milestone
here,
but
as
it
stands
today,
the
the
Target
date
is
September
29th.
Previously
we
were
kind
of
we
were
relying
on
that
date
being
a
little
bit
sooner.
That
was
speculative.
There
wasn't
a
commitment
that
it
would
be
sooner,
but
it
was
a
sort
of
speculatively
hoping
it
would
be
sooner.
B
That
might
still
happen,
but
as
it
stands
now
it
has
not.
What
that
means
is
that
the
plan
as
it
stands
today
is,
is
a
bit
broken
and
there
are
some
things
that
need
to
slide
out
specifically
because
of
this
dependency
here,
replay
replay
test
prior
to
tagging,
leak,
5.0
and
obviously
the
leak
5.0
rc1
itself.
B
They
kind
of
they
depend
on
that
delete
integration
of
instant
finality.
So
obviously
they
can't
happen
before
that
date
so
that
you
know
that
boils
down
to
up
to
two
weeks
of
delay
on
the
current
plan,
I'm
hesitant
to
update
it
yet
because
this
week
some
of
that
exploration
is
occurring
to
to
see
if
there
are
ways
that
we
can
pull
the
data
in
so
I'm
Gonna
Leave
the
plan
broken
at
the
moment
next
week,
we'll
either
have
the
dates
slid
or
have
a
wonderful
update
that
we've.
C
B
Is
you
know
what
what
steps
need
to
occur
in
order
to
coordinate
disabling
deferred
transactions
and,
as
far
as
just
a
make
sure
we're
all
on
the
same
page,
with
very
like
specific
details
here,
it's
it
is
a
config
option.
Max
scheduled
transaction
time
per
block,
Ms
or
milliseconds
equals
zero
is
how
you
would
how
you
would
be
able
to
disable
that,
and
of
course
we
can.
B
We
can
put
together
a
more
detailed
written
instructions
so
that
you
can
refer
to
those
later,
but
that
would
be
the
actual
step
for
an
individual
node
operator
to
disable
deferred
transactions,
but
coordinating
a
coordinating
for
a
community
of
node
operators.
To
do
so
is
obviously
a
little
bit
more
involved.
A
A
few
questions,
so
it's
not
an
msig
right,
so
this
is
something
that
each
individual
BP
has
to
change
the
configuration
and
do
is
there
a
minimum
threshold
of
BPS
that
need
to
have
that
or
it's
all
of
the
top
21
or
even
all
like
what?
What
is
what
is
the
target
right
except
that
needs
to
have
this
in
this
change
done
yeah.
B
Let's
break
that
into
bits,
so
the
very
the
first
part
correct:
it
is
not
an
msig,
it's
it's
just
a
configuration
change
that
you
would
individually
apply
and
yeah
that
would
that
would
disable
running
deferred
transactions
as
far
as
the
the
threshold
yeah.
Let's,
let's
talk
about
that
I
think
Kevin
is
on
and
Kevin
can
probably
help
us
with
this
one.
D
Yeah,
so
it
would,
it
would
need
to
be
all
active
BPS
to
get
a
true
test.
Otherwise
any
BP,
let's
say
there's
one
out
of
the
21
that
still
had
it
enabled
well
during
their
round.
They
would
then
process
any
deferred
transactions,
so
the
you
know
now,
depending
on
how
many
deferred
transactions
are
out
there,
that
might
be
enough
to
get
somebody
limping
along.
So
a
true
test
would
be
all
21
of
them
to
disable.
It.
C
B
The
the
reason
to
do
this
in
advance
is,
if
we
so
there's
no
way
to
have
full
confidence
and
understanding
of
what
the
impact
of
this
would
be.
Besides,
you
know,
having
it
removed
in
some
form
or
fashion
disabling
it
via
config
is
one
way
to
do
that
disabling
it
via
you
know,
via
code
in
nodeius,
is
another
way
to
do
that
and
disabling
it
by
actually
removing
the
code.
That,
which
is,
is
a
variation
on
that
option
right.
B
But
if
we
wait
until
5.0
deploy
for
this,
then
it's
then
it's
one
more
like
point
of
complexity.
Where
that
we
could
have,
we
could
have
gained
that
information
sooner
right,
like
we
won't
know
until
we
roll
it
out,
and
we
could
run
into
issues
that
require
you
know
patch
release
on
5.0,
because
oh
whoops,
this
is
this
is
a
bigger
deal
than
we
intended.
You
know
that
sort
of
thing
does
that
make
sense.
C
Why
doesn't
that
already
add
that
to
the
config
or
requiring
and
config,
if
somebody
still
needs
to
use
it
for
msig
or
something
else
make
it
a
requirement
in
the
config
that
you
still
have
to
have
like
deferred
enabled,
regardless
of
whatever
flag
you
have
in
the
milliseconds,
and
that
way,
actually
anybody
who
has
it
before
it
doesn't
like
forget
about
it.
It's
like
forces
them
to
take
an
action
if
they
want
to
actually
have
it
enabled
assuming
they.
A
E
Changes
in
a
patch
release
right
unless
we're
doing
a
4.1,
we'll
breaking
changes.
If
I'll
say
a
couple,
things
number
one
I
agree
with
Shaq
that
I
think
that
it's
better
off,
because
you've
got
backup
VPS
just
on
your
actives.
You've
got
secondary
nodes.
You've
got
some
chains
that
are
rotating
that
schedule
pretty
rapidly,
and
you
know
so.
Coordinating
you
know
is
definitely
an
issue.
E
It
very
recently
became
easy
for
chains
to
get
away
from
the
system
level,
deferred,
transaction.
Some
I
don't
think
even
have
yet
to
be
honest
with
you,
but
I
I.
If
it's
going
to
be
code
removed
in
5-0
I
would
think
offering
a
later
Oro
version
that
disables
it
by
default,
but
allows
you
to
enable
it
because,
if
you're
in
the
scenario
you
need
to
enable
it,
then
you
can
coordinate
your
BPS
and
if
they
don't
they
just
don't
process
deferred
transactions.
Right
I
mean
it's
not
like
it's
going
to
Brick
the
chain.
E
Making
the
node
operation
default
and
not
doing
deferred
transaction
prevents
a
hell
of
a
lot
of
the
ways
it's
gonna
break
versus
the
few
people
that
intentionally
want
to
run
deferred
transactions,
go
ahead
and
start
pushing
people
off
of
the
ledge
before
the
code's
completely
go
on
just
do
it
by
default
and
then
oh
we're
not
getting
deferred
transactions.
Okay,
turn
them
back
on
I.
Think
Michael.
C
A
D
Yeah
I
mean
you
could
certainly
just
look
at
any
block
Explorer
and
see
if
there's
any
deferred
transactions
for
a
given
producer
right
for
a
given
time
frame,
and
that
would
verify
you
know
the
the
idea
here
is
yeah.
Definitely
we
could
just
change
the
default
for
deferred
transactions
and
Five
Below
to
where
it's
default,
not
there,
so
that
when
people
upgraded,
if
they
didn't
do
anything
it
would,
they
would
automatically
automatically
be
disabled
included
in
5.0.
D
We
could
add
a
protocol
feature
to
turn
it
off
so
that
when
the
protocol
feature
is
enabled
deferred
transactions
are
are
gone.
What
our
attempt
here
to
do
this
ahead
of
time
to
do
this
test
or
try
to
get
all
the
BPS
to
go
ahead
and
just
disable
it
with
their
current
software
is
to
get
feedback
before
we
do
the
work
of
a
protocol
feature,
because
if
we
do
the
work
of
the
protocol
feature
once
the
protocol
feature
is
Switched,
there's
no
going
back.
D
We
don't
have
at
least
currently
any
way
to
to
undo
a
protocol
feature.
Now,
apparently
we
could.
We
could
do
all
that
effort.
It's
just
a
matter
of
like
how
much
do
we
want
to
expend
on
the
terms
of
resources
of
doing
this,
so
we're
hoping
to
get
some
feedback
right
away
on
hey
if
we
can
get
the
BPS
to
just
disable
it
now?
What
sort
of
feedback
to
get
you
know?
D
C
I
think,
as
long
as
eventually
it
will
be
like
like
a
feature,
that's
basically
going
to
be
like
a
fork.
If
the
node
is
not
aware
of
that
feature,
then,
and
the
people
that
are
going
to
be
testing
are
limited
in
scope,
I,
don't
think
it
matters
much
and
might
as
well
take
the
effort.
The
the
path
of
least
effort,
as
in
like
delay
during
the
future
right.
B
Yeah,
so
the
the
intent
is
through
testing
to
make
code
removal
a
non-event
right
like
and
and
therefore
reduce
the
the
amount
of
risk
mitigation.
That's
required,
because
we
already
know
that
it's
you
know
it
can't
be
being
used
right
now.
I
do
want
to
follow
that
logic
of
a
like,
a
4.1
versus
a
versus
just
a
rolling
out
a
config
change,
so
I
think
the
the
assertion
is
that
it
would
be
easier
on
node
operators
and
and
maybe
easier
to
get
enough
uptick
to
get
a
valid
test.
E
Don't
see
the
difference
in
effort
for
those
two
options:
I,
don't
know,
I.
Think
that
that's
that's
what
I
wanted
to
tagging
it
with
four
one
I
mean
if
you're
really
just
kind
of
wrapping
things
around
this,
and
maybe
some
other
things
that
you're
scoping
for
some
things
that
you're
really
targeting
for
getting
ready
for
5.0.
It
might
be
good
to
if
you
make
a
full
one
and
say
hey
look,
I
mean
404
is
a
wonderful
code
and
you
can
keep
running
that.
Maybe
a
405
if
you
know
what
bug
fixes
but
keeping
4-0.
E
As
you
know
now,
this
is
before
I
stack
and
it's
fine
anything
full
one,
four
one
one
for
whatever
is
flipping
on
any
of
these
extra
features
that
may
be
getting
ready
for
five.
Oh
man,
I
didn't
deported
over
to
five.
You
know
because
they're
temporary,
but
it's
in
my
opinion,
much
easier
to
coordinate,
guys,
update
your
binary,
make
sure
you're
running
four
quad
one
and
the
default
doing
whatever
it
needs
to
do
versus
making
sure
everybody
has
it
in
their
config.
E
A
huge
amount
of
engineering
effort
to
create
a
4.1
release
for
very
little
value.
The
way
to
do
this
is,
as
somebody
said
earlier,
write
a
you
know:
Aloha
EOS,
mechanics
thing
that
just
generates
a
deferred
transaction.
Every
few
seconds
write
a
report
that
shows
which
transaction
which
BPS
executed
those
transactions
and
then
go
harass
them
until
the
report
is
blank
right.
E
You
hear
that
pet
to
do
as
long
as
that
gets
done
on
all
the
major
chains
that
are
that
we're
ultimately
trying
to
Target
in
the
testing
scope,
if
it's
only
jungle
that
yeah
easiest
pie,
if
you
really
want
like
the
coalition
to
do
it,
you've
got
several
other
networks
that
yeah,
but
somebody
has
to
do
to
me.
That's
a
lot
less
engineering
work
than
doing
a
4.1.
E
F
B
B
E
To
get
are
you
trying
to
get
the
result
at
the
BP
node
operator
level,
or
are
you
trying
to
get
the
result
at
the
debt
level?
That's
potentially
about
to
lose
a
feature
they're
using
because
most
chains
have
deprecated
deferred
transactions
at
the
system
level
and
probably
wouldn't
run
into
many
issues?
E
It's
the
stats
that
still
have
access
to
them
right
are
gonna,
go,
oh
deferred
transactions
are
gone,
I
didn't
know
that
was
disappearing.
Just
like
the
exchanges
didn't
know.
B1
history
was
disappearing.
Yeah
you
watch
it
trigger
the
dapps
and
you're,
not
gonna
jungle.
You
might
have
a
few
because
people
brunch
it
there,
but
that's
the
the
question.
B
A
E
A
report
handy
curiel,
writing
one,
yes
right,
but
that's
what
you
probably
want
to
see
right.
You
want
to
see
a
report
that
shows
how
many
deferred
transactions
are
running
over
the
last
I,
don't
know
month
or
something
right,
and
then,
if
you
can
figure
out
what
those
are
then
go
up
around
those
people.
Ask
them
some
questions
right.
There's.
E
Here's
the
date
and
we're
going
to
start
turning
it
off
and
the
iris
I
assume
what
you're
trying
to
get
I
assume
what
you're
trying
to
get
it's
the
same
thing
we
always
get
as
we
you
know,
take
something
away
is
to
get
the
coders
that
have
solved
a
problem
by
using
it
that
are
about
to
go.
I
can't
do
this,
and
this
was
how
I
got
around.
So
it's
like
the
unique
use
case,
and
that's
why
I
say:
I
I.
E
If
you
want
a
shotgun
at
an
infrastructure,
an
operational
level,
absolutely
we
can
roll
it
out.
The
jungle
turn
some
things
off,
but
all
right
it
feels
like.
But
until
you
don't
turn
it
off,
then
people
don't
react,
so
you
need
to
turn
it
off
in
life.
That's
exactly
test
net
or
something
where
there's
really
active,
apps
that
are
running
that
could
potentially
trigger
it
or
even
go
out
to
a
mainnet
level
because
yeah,
it's.
B
B
Two,
if
we're
able
to
track
down
depths
that
are
relying
on
this
or
seem
to
be
relying
on
this,
then
yeah
as
a
courtesy
reaching
out
and
saying,
like
hey,
wanted
to
make
sure
you
saw
this,
but
ultimately
forcing
functions
are
often
required
right,
like
a
date
like
this
is
when
this
is
going
to
be
disabled.
So
you
know
make
sure
you,
if
you
are
relying
on
it,
that
you
find
a
way
not
to
be
relying
on
it
right.
B
B
Yeah
yeah,
that's
the
other
side,
and
that's
actually
that's
that's
one
of
the
reasons
why
I
work
doing
this
is
you
know
that
it
is
of
course
possible
that
we've
we've
missed
something
here
and
and
like
we
cannot
get
rid
of
this
and
that's
why
we
don't
want
to
just
like
pull
in
a
china
shop.
Remove
the
code.
You
know
all
together.
E
So
I
think
you're
gonna
have
to
rip
the
Band-Aid,
so
I,
don't
I,
don't
know,
but
let's
come
up
with
a
communication
plan
yep
to
rip
the
Band-Aid.
So
it's
not
first
round
last
gripping
the
Bandit
dude
I
definitely
think
it's
worth
you
know,
I
mean
we
can
run
a
report
on
EOS
and
see
you
can
do
juggle
too
all
right
that
I
I,
just
as
I
hear
it
like
say
it's,
not
us!
That's
going
to
notice
it.
It's
everybody
else,
and
the
only
way
to
do
that.
C
But
that's
my
point
is
like
here:
it
might
not
apply
because
the
the
date
for
5.0
is
so
close,
but
in
general,
if
things
are
going
to
be
depreciated
and
it's
not
in
advance,
you
don't
make
a
necessarily
a
special
version
for
it,
but
any
subsequent
versions
should
require
just
like
another
flag.
So
the
operator
knows
like
this
is
being
depreciated
and
you're
going
to
have
to
do
something
about
it.
C
A
So
the
the
opportunity
here
to
to
start
warming
up
the
EO
support
email
list.
You
know
they've
they've
gathered
all
the
contacts
of
known
dapps,
maybe
there's
some
work
that
has
to
be
done
to
adjust
that
I'm
not
sure
if
there's
any
new
or
no
longer
relevant
and
I
think
there's
maybe
a
couple
audiences
here
we
have
to
consider
there's
the
node
operator.
A
Maybe
there's
a
survey
to
or
some
way
to
provide
feedback
if,
if
you're
using
it-
and
you
want
to-
let
us
know-
hey
I'm
using
this
and
I
need
it,
and
this
is
why
I
need
it
probably
makes
sense.
It's
just
for
you
to
live
on
the
blog
and
then
an
email
blast
that
once
that's
published,
we
get
that
EO
support
emails,
roll
into
Point
everyone
to
that
blog
sorry
go
ahead.
Matthew
yeah.
E
And
then
I
was
just
going
to
add
to
this
plan.
Is
you
know,
run
a
report
see
if
you
can
figure
out
who
those
people
are
that
are
right,
knock
on
their
doors,
front
attraction
today
and
then
you
know,
build
a
deferred
transaction
simulator
thing
that
will
push
deferred
transactions,
so
we
know
which
BPS
are
still
executing
them.
E
E
F
E
E
A
E
C
B
A
B
E
A
E
Could
be
one
blog
post
with
typical
engine
for
the
not
node
operators,
probably
maybe,
but
the
blog
it
needs
to
be
long
right
or
long.
It
needs
to
provide
the
motivation.
What
we're
doing?
What
is
the
timeline?
You
know
how
to
report
if
your
impact
did
how
to
configure
it
if
you're
a
node
operator,
there's
a
bunch
of
stuff,
we
need
to
cover
here.
A
C
I,
don't
think,
there's
any
point
in
getting
feedback
from
dapps,
because
even
if,
like
whoever
comes
back
to
you
and
tells
you
hey,
we
need
it
like.
Are
you
actually
going
to
change
the
plan
like
I?
Don't
think
so!
So
might
as
well
just
explain
why
it's
being
done
and
potentially
suggest
Alternatives
if
needed,.
F
B
B
B
B
F
F
B
B
E
I
said
I
was
going
to
bring
it
up
Nicole
this
evening.
Marco
actually
mentioned
that
the
wax
DP
cool
law
slot.
Apparently
he
mentioned
something
about
Kevin.
If
you
guys
have
got
like
a
matrix
that
you
created
of
all
of
the
various
features
in
in
the
actual
leap
software,
something
that
you
use
to
go
back
in.
Maybe
it's
your
personal.
E
E
Base
layer
configuration
of
config
that
we
should
be
using
and
that
even
us
us
operators
that
have
been
using
the
software
in
various
forms
over
the
last
five
years,
often
taken
by
surprise
by
some
of
these
cool
features.
We
probably
told
them,
and
we
forgot
about
them-
and
you
know,
is
there
a
better
way
for
us
to
realize
that?
Oh,
you
know,
that's
quite
a
good
thing:
that's
going
to
improve
the
performance,
we
should
probably
enable
it
that
I
I,
think
I
explained
it
or
at
the
end,
my.
D
I
mean
the
short
answer
is
no
right,
I
mean
some
of
what
Brian's
been
trying
to
do.
I
think
in
previous
calls
is
to
to
focus-
or
you
know,
try
to
focus
in
on
that,
but
no
I
personally
I
think
we're
probably
long
overdue
on
trying
to
get
some
of
that.
That
information
out
just
in
terms
of
like
you
know
if,
if
I
was
running
a
node
here,
is
what
I
would
here's,
how
I
would
configure
it?
D
The
interesting
thing
about
that
is
we.
You
know
we
probably
put
that
together
and
then
Matthew
would
come
back
and
say
well
that
that's
dumb
you,
you
do.
Obviously
you
do
this
for
that
and
we
go
okay
and
you
know,
and
so
yeah
I
think
there's
it
could
be
some
back
and
forth
there
for
sure,
in
terms
of
like
here
is
a
better
explanation
of
like
things
that
you
know.
C
He
was
going
to
say,
I
think
there
are
many
different,
like
things
involved
here
like
there's.
Obviously
the
system
contracts
that
could
enable
certain
things,
but
it
seems
we'll
be
talking
more
about,
like
plugins
or
or
other
things,
I
think
the
first
really
like
thing
that
should
be
concentrated
on
is
like
the
docs
on
Euros
Network
that
one
for
it
to
have
things
like.
Okay,
these
are
node
features
that
you
can
enable,
such
as
you
know,
compute
API
read
only
transaction.
C
If
you
have
that
and
then
like
a
version
number,
which
is
the
minimum
version
number
of
the
lead
binary
that
enables
that
feature
that
will
go
a
long
way
in
there
and
then,
as
we
talked
about
in
previous
calls
and
and
Matthew
also
talked
about.
A
lot
is
having
these.
You
know
specific
configs,
for
you
know,
you're
running
a
BP
like,
depending
on
the
role
of
the
node
itself,.
E
E
If
you've
got
this
one
enabled
because
it's
counter
protected,
you
know,
I
know
that
we're
still
learning
about
some
of
these
new
ones,
like
I,
just
learned
that
apparently
trickled
down
from
Matthew
that
on
a
BP,
you
should
disable
all
read
threads,
because
you're
wasting
CPU,
which
may
or
may
not
be
too
impactful
but
I'm
still
finding
them.
People
I
talked
on
the
other
day
and
I'm
looking
at
their
default
big.
So
what
I'm
doing
is
I'm
trying
to
reach
out
to
you.
You
can't.
E
Does
it
not
default
the
three
like
all
the
other
nodes
spun
up?
Maybe
I,
don't
realize
that,
but
anyway
long
story,
short
I
I'm,
trying
to
kind
of
gather
from
a
lot
of
you
know
kind
of
no
node
operators
and
try
to
get
a
consensus
and,
in
my
mind,
when
I'm
and
maybe
I'll
build
it
in
an
Excel
spreadsheet
Ross
will
collaborate
on
it.
E
But
the
idea
is
almost
like
a
product
Matrix
to
know
if
you're
at
3-0,
3141
and
I'm
gonna
go
to
404.,
what
are
all
the
different
things
that
are
either
getting
deprecated
or
getting
added.
As
a
recommendation,
I
definitely
agree
with
Shaq
I
mean
the
docs
that
do
kind
of
detail
like
I,
had
to
ask
Kevin
what
subjective
billing
and
how
that
kind
of
worked
and
I
mean.
E
These
features
came
out
even
if
it's
not
a
default
setting
people's
settings
are
great
I'm
going
to
have
that,
but
just
to
even
know
hey
by
the
way
you
should
have
just
like
at
one
point,
we
shifted
in
2-0
from
a
static
last
blocks
time
offset
to
a
percentage
and
we're
still
dealing
with
you
know.
I
mean
I
just
put
both
of
them
in
there
and
hope
for
the.
E
And
you
know
what
that's
starting
to
burn
me,
because
now
I've
got
chains
that
are
extending
their
CPU
limits
and
I'm
realizing
I'm
capping
my
blocks
at
200
milliseconds,
because
that
was
the
original
whatever
anyway
long
story
short,
even
all
the
way
back,
which
is
not
as
important
going
back
three
and
four
and
now
five
we're
really
hitting
it
hard
with
new
features-
and
you
know
oh
I
had
on
subjective
billing
yeah
the
new
subjected
building
4.0
and
later
maybe
a
3.2
something
before
whatever
has
a
whole
new
mechanic
to
it.
You
know.
E
Yes,
it
needs
Shacks.
You
know
stock
article
to
give
a
better
non-tech
spec
of
it,
but
just
the
kind
of
a
summary
he
was
saying
it
is
going
to
be
tickets.
Technical
documentations,
yes,
I
mean
I'm,
assuming
he
means
like
like
user
manual
type
of
thing,
and
we
definitely
need
to
work
on
that
so
po.
This
is
yeah
yeah.
E
E
These
are
the
features
that
we're
working
on,
and
this
is
why
we're
doing
it,
because
a
lot
of
the
time
we
we
finding
out
that
on
the
on
the
public
release
and
whether
it's
brought
up
the
being
like
a
side,
conversation
somewhere,
yep
I,
think
this
is
the
place
even
if
it's
just
a
short
amount,
though
hey
guys.
This
is
this
is
the
different
consensus
mechanism
that
we're
going
to
be
implementing
in
far,
and
these
are
the
where
it
could
potentially
go.
You
know
that
kind
of
thing
whatever
it
may
be.
E
F
Yeah
yeah
I
I
mean
we've
got
240
something
PR's.
Now
we
merged
ends
between
a
four
zero
four
and
five,
so
I
I've
been
actually
writing
scripts
to
go
through
all
of
them
and
pull
them
out
so
that
then
I
can
go
back
into
GitHub,
annotate
them
or
you
can
add
more
useful
information,
so
it
could
provide
more
reporting,
there's
so
much
stuff.
F
There
I
think
it's
got
to
take
place
from
London
Heating
I'm
working
on
it
and
and
the
dials
and
the
the
features
we
talked
about
that
too
and
I
think
it's
good
feedback,
because,
as
an
organization
enf
had
focused
on
developers,
the
DF
folks
and
the
documentation-
and
you
can
talk
to
Nathan
he'll
tell
you
the
same
but
really
after
feed
when
it
came
to
sort
of
operators
manual,
so
I
think
we
gotta
add
make
some.
You
know
really
add
a
little
bit
of
love
back
into
that
stuff.
C
With
the
config,
you
can
easily
add
a
like
a
config
generator
on
the
docs
or
or
some
site
where
you
can
see
like
oh
I
want
to
be
an
EP
I
know
it
I,
want
it
or
like
I,
want
to
be
in
yeah
an
API,
node
and
I
want
to.
You
know
enable
compute
and
I
want
to
enable
read
only
and
you
kind
of
check
things,
and
it
gives
you
a
suggestion
with
like
placeholders
for
things
like
how
many
threads
you
want
to
use
or
or
whatever
else
that
may
be
specific
to
that
machine.
B
Some
of
that
not
just
because,
like
I,
want
to
make
node
operator
lots
better,
but
also
for
things
like
you
know,
it's
it's
difficult
to.
You
know,
coordinate
getting
exchanges
to
do
an
upgrade,
and
you
know
stuff
like
that.
Right,
like
the
easier
we
can
make,
that
the
more
effective
we
could
be
at
at
sort
of
innovating,
on
on
leap's
capabilities.
B
Where
was
I
going
with
this?
Oh,
but
an
analogy
I
wanted
to
sort
of
bring
up
is
that
you
know
we're
we're
tool
makers
and
we
know
all
the
features
of
the
tool
right,
but
your
Woodworkers,
you
know
hey,
and
you
know
about
how
you
use
the
tool
you
know
like.
We
so
I
think
this.
It
does
need
to
be
collaborative
so
like
yeah,
we
could.
We
could
put
together
sort
of
configuration,
generator
thing
sort
of
it's
speculatively.
B
How
we
think
it
should
be
used,
but
you're
gonna
have
boots
on
the
ground
knowledge
that
says.
Actually
this
is
how
it
should
be
used
and
here's
why
right
like
and
that's
that's
that
was
the
purpose
of
the
conversation
theme
we
had
around
like
node
types
in
the
past.
We
didn't
follow
that
conversation
all
the
way
through
and
and
would
need
to
Circle
back
on
some
of
that.
B
But
yes,
and
and
configuration
generator
in
particular,
is
a
a
solution
that
we've
discussed
and
might
be
a
Way
Forward.
We've
also
talked
about
more
special
purpose
binaries
as
a
either
complementary
or
alternative
solution.
For
that,
in
all
of
these
cases,
documentation
is
needs
to
be
improved
for
sure.
C
And
documentation
is
not
that
like
difficult,
but
it's
a
lot
of
documentation.
So
you
need
somebody
who
you
know
read
everything
that
has
to
do
with
these
features
and
can
at
least
put
the
like
the
skeleton
of
everything.
And
then
people
can
come
in
and,
like
you
know,
the
more
specialist
in
the
future
can
overview
it
and
make
sure
you
know
that
they
they
edit
some
things
that
may
be
inaccurate
or
incomplete,
and
that
could
be
like
a
way
like
if,
if
NS
James
I
think
is
the
one
doing.
C
The
docs
now
like
I
might
be
wrong,
but
whomever
it
is
like
like
having
like
dogs
that
yours
Network
like
having
that
just
updated
with
just
all
the
features,
even
at
least
holder
and
allow
even
the
community
like
I
use.
Almost
all
these
features
and
I'm
familiar
with
a
lot
of
settings
like
because,
because
I
write
that
and
I
you
know
run
the
the
node
operation,
so
I
get
kind
of
a
view
from
both
these
places.
But
there's
no
way
for
me
to
go.
Add
information.
F
B
B
I
guess
affordances
for
using
them
whether
that's
configuration
or
something
else
so
I
think.
One
thing
that
that
points
to
is
that,
like
as
a
first
step
like
that
information,
ideally
should
be
in
the
release,
notes
which,
as
a
best
effort,
we
intend
that
they
are
already
doesn't
mean
they
ate,
like
everything
is.
E
B
That's
the
next
thing.
Yes,
so
it
sounds
like
what
you're
asking
for,
because
the
release
notes
are
are
even
with
whatever
missing
details.
There
are
they're,
still
very
verbose,
there's
a
lot
of
information
in
them
right,
so
it
sounds
like
you're
looking
for
the
roll
up.
That
shows
you
across
many
releases
manual.
E
E
From
my
perspective,
it'll,
it
would
enable
me
to
make
use
of
all
the
cool
features
and
amazing
development.
That's
taking
place
because
I'll
tell
you
right
now:
guilty
I
run
stuff
based
on
my
experience
and
what
I
know
that
works
and
I
only
necessarily
go
and
change
something
where
I'm
forced
to,
because
there
is
a
there,
is
a
change
in
the
software.
There's
not
supports
it
for
there's
something
broken
on
the
network
that
involves
some
changes.
E
C
A
E
Me
enable
that,
yes,
definitely
I,
think
it's
too
little.
One
is
yeah
more
information
about
it.
I
was
talking
about
kind
of
a
sun
rate
for
just
like
node
operators,
but
the
conversation
evolves,
I,
think
the
bigger
you
know
the
EOS
docs
and
just
having
more
whatever
that
also
led
to
Shaq
and
Eric
having
the
chat
about
it.
Your
community
is
happy
to
provide
you
a
lot
of
that
in
life.
E
Lessons
that
we've
learned
if
there
were
some
sort
of
contribution
mechanism
through
GitHub
as
a
markup
sounds
like
that
helps
facilitate
let's
get
the
docs
better
get
y'all
provide
some
framework,
I'll
have
oversight,
but
then
even
allow
a
mechanism
to
when
we
learn
something
we
can
go
submitted
as
a
PR
and
it
can
get
added
into
the
EOS
docs.
You
know.
So
it's
not
always
you
guys
have
to
make
that
it
can
just
be
no
I,
think
it's
how
I
understood
it
kind
of
an
evolution.
C
C
E
I
know
we're
at
the
end,
I'd
say:
there's,
maybe
a
you
guys
can
yeah.
You
know,
focus
on
the
dark
side
of
things.
You
know
and
filling
out
all
the
features
and
and
markup
submissions
and
stuff
like
that
me,
and
maybe
some
of
my
other
technical
Compadres
can
I'm
gonna,
throw
something
together
like
just
even
a
Google
sheet
or
kind
of
that
Matrix
I'm
talking
about.
E
F
I
think
there's
a
there's.
Also.
Another
thing
is
that
there's
so
the
the
level
of
detail
that
we
do
put
out
with
hey
it's
all
in
git
up
or
it's
all
in
the
pull
request
is
so
fine
and
we
need
something.
That's
aggregated
at
a
higher
level
right,
which
is
really
shouting
out
like
these
are
the
chapter
titles
for
all
the
awesome
stuff.
That's
in
beat
and
I.
F
Think
that's
good
for
us
here
in
this
call,
but
I
also
think
it's
good
for
people
who
aren't
even
operating
you
know
in
in
leap
or
nodeeos
and
they'll
see
oh
wow.
It
has
all
this
full.
Stop,
that's
great
with
enough
technical
details.
If
you're
you
can
see.
Oh,
this
is
a
real
thing
and
transactions.
E
Yeah,
if
I
understand
it's
really
hard
like
right
now,
you
can
print
a
default
config
and
basically
get
like
a
one.
Maybe
two
line
geek
explanation
of
what
dictator
you
know,
all
of
them
together.
You
don't
even
always
see
hey
this
one,
and
this
one
are
related
so
having
some
of
that
in
user
manual.
But
yes,
yeah.
C
There's
a
point:
trust
was
making
like
having
exact
node
EOS
dash
dash
help
on
the
website.
You
know
where
each
each
layer
each
option
that
you
can
put
there
or
each
key
or
each
item
has
some
sort
of
explanation
outside
node,
EOS
and
potentially
how
the
explanation
might
have
changed
or
depreciated
between
versions,
bingo.