►
From YouTube: Node Operator Roundtable - August 31, 2023
Description
The Antelope Node Operator Roundtable meets every Wednesday at 14:00 UTC to share and discuss feedback to improve the Antelope protocol.
00:00:00 Intro
00:00:47 Disabling of Deferred Transactions on Testnets
00:09:43 Software Status Update
00:24:33 NodeOS Config Matrix
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
All
right
welcome
everybody.
It
is
August
30th
and
we're
preparing
for
the
big
leap.
5.0
upgrade
big
hard
fork
with
some
hot
stuff
coming
through
and
I.
Think
we'll
we'll
bring
back
the
board
you.
May
you
may
remember
the
the
GitHub
board
that
we
use
to
track
some
of
our
progress,
leading
up
to
the
the
last
Big
Fork
I.
Guess
that
wasn't
4.0
that
would
have
been
three
dot
one
3.1
right,
yeah,
so
anyways
we're
back
back
with
the
board,
still
got
some
old
relics
here
from
the
old
upgrade
to
keep
us.
A
You
know
for
some
consistency.
The
stuff
I
want
to
focus
on
today
are
obviously
the
the
time
sensitive
stuff
we've
got
in
the
plan,
which
I
will
more
and
more
of
this
will
move
over
to
the
board.
The
the
pressing
matter
is
the
disabling
of
deferred
transactions
on
Jungle
in
Kailyn,
so
we
can
check
in
on
how
that's
going
and
the
goal
that
was
set
by
the
enf
there
is
by
September
1st.
A
So
that's
this
Friday
in
a
in
a
couple
days,
I
did
have
a
look
in
the
telegram
channels
to
see
how
we're
doing
there
and
actually
making
some
some
decent
progress
so
of
the
top
21.
We
have
some
a
couple.
You
know
a
few
BPS
that
are
running
multiple
BPS,
so
I'm
not
duplicating
them
here,
but
this
captures
the
top
21
on
Jungle
and
you
can
see
there's
just
a
a
few
that
have
yet
to
at
least
mention
acknowledge
that
they've
disabled
deferred
transactions.
A
A
Awesome,
thank
you
no
problem.
So,
like
I
said,
there's
still
you
know.
A
lot
of
a
lot
of
the
stuff
here
is
from
the
previous
upgrade
lots
to
add
still
for
the
upcoming
upgrade
new
views
to
play
with,
since
the
last
upgrade
they've
they've
added
some
fancy
new
toys
in
in
GitHub
projects
like
road
map
views
and
things
like
that.
So
maybe
we'll
experiment
with
some
some
more
timeline
based
views.
We've
still
got
the
the
status
view
here
and
yeah
we'll
continue
getting
this,
this
populated
as
as
items
approach.
A
So
thank
you
to
EO
support
I,
see
that
the
the
message
has
been
sent.
You
know
right
pretty
well
right
after
the
our
last
call,
as
as
we
discussed,
there's
been
emails
and
and
messaging
sent
out
to
all
the
app
developers
make
sure
that
everybody
is
aware
of
this
is
Dario
or
anyone
from
support
on
the
line
here.
I,
don't
think
so.
Oh
yeah
I
see
Daria
anything
you
want
to
speak
to
on
that
topic.
E
A
total
of
103
entries
related
to
Applications
exchanges
and
decentralized
exchanges
on
U.S
were
effectively
communicated
directly
in
cases
where
direct
contact
was
not
possible.
Emails
were
dispatched
totally
263
emails
sent
more
a
comprehensive
article
has
been
composed
and
translated
in
all
nine
languages.
This
information
has
been
actively
promoted
across
all
nine
of
our.
Your
super
Twitter
accounts
each
operating
in
a
different
language.
Additionally,
dissemination
across
more
than
80
public
channels
on
various
social
media
platforms
also
has
taken
place.
E
A
E
A
B
B
B
A
E
B
Yeah
I'd
love
to
get
a
direct
line
of
communication
established.
Just
because
you
know
obviously
like
Upland
is,
is
you
know
major
driver
of
usage
overall
on
yes
and
and
want
to
make
sure
that
they
have
direct
contact
with
us
in
case
they
haven't
run
into
any
issues
or
anything
like
that
and
need
need
additional
help.
So
I.
A
May
be
able
to
get
you
with
in
touch
or
dot
gems
team
who's
been
running,
the
the
Fireside
Chats
have
have
court
done,
some
coordinating
with
them
to
get
them
on
the
on
the
fireside
chat,
show
and
I
believe
they're
they're
in
touch
to
some
degree
at
least
can't
make
any
promise,
but
I'll
see
what
I
can
do
on
my
side
and
again
you
have.
Anyone
else
has
has
a
a
direct
line.
Yeah.
A
B
Eric
is
often
a
better
person
to
give
an
update,
but
in
this
case
really
it's
a
project
management
thing,
because
we
ended
up
removing
the
software
development
tasks
other
than
removal
of
deferred
transactions
itself,
which
is
down
below.
So
we
removed
those
tasks
because
and
the
just
to
remind
you
what
they
were
and
and
by
the
way
I'll
reach
out
to
you
and
to
make
sure
that
we're
aligned
on
the
the
GitHub
board,
because
I
I
did
that
here
in
this
spreadsheet.
B
So
anyway,
the
reason
we
removed
those
tasks
is
basically
just
you
know
time
and
resourcing.
We
determined
that
we
can
do
this
in
kind
of
a
low
Fidelity
way
just
using
block
explorers
rather
than
writing
scripts,
which
lets
us
keep
our
focus
on
the
like
instant
finality
integration
work
that
needs
to
be
done,
yeah,
which
you
know
obviously
is
kind
of
the
the
Keystone
of
this
release
in
the
first
place.
B
So
it's
a
good
place
to
keep
our
Focus,
so
I
don't
feel
like
we're
giving
much
up
there.
We
should
still
be
able
to
to
get
satisfactory
level
of
you
know
information
just
just
from
like
perusing,
black
logs
and
whatnot
to
see
level
of
usage
on
different
transactions,
as
as
it
relates
to
disabling
deferred
transactions
in
code.
We
still
don't
have
an
estimated
delivery
date
on
that
again,
just
our
our
Focus
has
been
elsewhere,
but
we
do.
We
are
confident
that
it
will
happen.
B
You
know,
prior
to
prior
to
a
release
candidate,
for
this,
so
I
mean
maybe
we'll
end
up
putting
a
date
that
aligns
with
the
release
candidate
just
and
just
so
that
it's
it's
not
that
it's
going
to
take
that
long.
It's
just
it
might
take
that
long
for
us
to
put
our
focus
on
it
right,
but
yeah
we
are.
We
are
confident
about
the
code.
B
B
B
Why
is
my
brain
just
keeping
a
beat
here?
Basically,
according
to
the
schedule
that
we've
previously
published,
you
know,
I
do
invite
folks
to
to
do
their
own
slew
thing.
If
they're
curious
and
interested
in
in
sort
of
confirming
there
but
yeah,
we
will
will
take
responsibility
for
reaching
a
you
know
satisfactory
level
of
confidence
that
it's
not
receiving
major
usage.
A
A
B
Yeah
you
know,
I
did
actually
I
have
not
sent
that
developer.
Reminder
at
this
point.
So
I
need
to
do
that.
But
yes,
we
we
will
do
that
via
telegram
channels,
the
on
kylan
I.
You
know
this
is
kind
of
embarrassing,
but
I
I
don't
actually
know
what
channels
that
is
discussed
in.
So
if
anybody
can
sort
of
point
me.
A
B
B
A
A
Okay
and
and
then
the
disabling
deferred
transaction
to
that
side,
how
are
we
progressing
on
the
on,
like
the
the
leap,
5.0
software
side
of
things?
Are
we
on
track
to
hit
the
timeline
set
out
here
in
terms
of
the
first
release?
Candidates
are
any
of
the
you
know.
The
final
release
dates
that
we've
set
here
at
risk
or
or
how?
How
is
that
looking.
B
B
But
we
we
have
decided
to
and
you'll
see,
you'll
see
this
little
new
block
of
things
where
it
says
early,
API,
testing,
those
three
tasks,
so
I've
decided
to
add
a
a
task
to
make
a
tag
for
basically
what's
already
in
Maine
as
of
Thursday,
and
that
will
include
almost
everything,
shy
of
instant
finality
itself
and
the
reason
to
do
this
is
it.
It
will
give
us
an
opportunity
if
we
can
find
some
Partners
willing
to
to
help
with
testing
it'll.
B
Give
us
an
opportunity
to
like
get
some
additional
confidence
and
testing
around.
You
know
the
larger
set
of
features
prior
to
doing
the
official
release
candidate.
That
includes
instant
finality
because,
overall,
basically
this
came
out
of
a
discussion
where
you
know
this
is
a
huge
release
and
we've
got
a
very
tight
schedule
here,
and
so
any
any
slippage
could
put
this
into
a
holiday
periods
both
in
the
west
and
in
the
East
and
so
also
historically,
we've
we've
had
multiple
RCs
for
any
release.
B
Right
in
this
schedule
only
accounts
for
one
now
after
talking
with
the
team,
I've
got
I'm
more
comfortable
with
that,
because
the
we
do
have
a
period
of
time
between
rc1
and
when
we
are
when
the
plan
says,
we'll
we'll
call
it
stable
right.
So
there
is
some
time
in
there
for
for
our
additional
RCS
to
happen,
but
anything
we
can
do
to
gain
confidence
and
find
issues
and
fix
them
earlier,
rather
than
later,
is
going
to
help
keep
this
thing
on
track.
So
that's
these
three
tasks
tag
it.
D
If
you
take
the
API
node
update,
I,
think
that
is
a
whole
conversation
for
another
meeting,
because
there's
a
lot
of
good
features
there.
For
example,
there
was
a
change
to
chain
base
which
saves
quite
a
bit
of
memory.
So
if
you
I
mean
just
loading
that
API
note
up,
you
should
see
a
smaller
memory
footprint
so
that.
D
And
that's
just
one
there's
a
bunch
of
other
features
in
there
too.
That
would
be
fun
just
to
try
out
I'm
gonna,
move
on
to
software
update
and
then,
if
anybody
has
questions
about
experimental
API
release
and
features,
I
can
answer
those
moving
on
to
software
updates.
We
are
making
progress,
we
are
on
track.
D
You
know
the
this
is
a
tight
schedule.
We
are
putting
a
lot
of
stuff
in
so
you
know
when
I
say
we're
on
track.
It's
not
like
oh
yeah,
we're
gonna
make
it
with
plenty
of
room
to
spare.
No
we've
planned
everything
down
to
like
the
final
minute
and
what's
changed
this
week.
Is
we
have
a
critical
path
for
our
release
with
issues
and
dependencies
and
every
day
we're
working
on
that
critical
path
and
moving
that
clock
forward
closer
and
closer
to
completing
all
of
our
critical
path
items.
A
A
D
Do
you
think
we'll
start
off
with
try
to
do
installation
instructions
and
then
go
through
what
you
would
see
right
when
you
first
installed
the
node?
There
should
just
be
some
environmental
stuff
that
you
should
see
right
off.
The
bat
like
I
mentioned
the
lower
memory
and
then
we'll
we'll
finally
go
into
benchmarking
right.
Some
things
that
you
can
try
out.
That
should
be
faster
or
just
validate
running
the
tests,
just
validating
for
correctness,
and
that.
A
C
D
Yeah
that
totally
makes
sense,
but
we're
gonna
need
some
help.
I,
don't
think
we're
gonna
have
that
this
week
we
probably
have
some
specific
config
dials
later
on
and
the
reason
is
we
don't
run
these
API
nodes,
so
I
don't
have
as
good
of
a
feel
as
some
other
folks
do
so
I'm
gonna
really
need
somebody
else's
config
file
and
walk
through
it
and
then
I
think
I
would
have
some
better
recommendations.
C
F
G
A
C
All
right,
hopefully,
you
see
a
bunch
of
green
check
boxes
on
a
Google
screen
right,
yeah,
all
right.
So
what
I
kind
of
started
and
Ross
is
helping
me
out
with
and
we're
really
trying
and
there's
several
other
BP's
around
the
space
we've
stolen
information
from
or
they've
provided
really
just
trying
to
get
a
bearing
on
what
are
all
the
different
parameters
that
you
have
in
your
config
files:
apis
peer-to-peers
ships,
whatever
BPS?
What
are
some
of
the
different
options?
I
tried
to
kind
of
group
them
up.
You
know
like
hey.
C
This
lovely
little
resource,
monitor
override
personal
favorite,
all
my
nodes
versus
you
know.
These
are
settings
that
are
kind
of
grouped
towards
API
and
really
just
trying
to
kind
of
get
a
if
you're
running
an
API.
These
are
the
things
you
should
at
least
look
at.
These
are
kind
of
see
how
they're
kind
of
together
right
and
then
even
trying
to
go
through
and
provide
English
versions
of
what
they
mean.
C
Why
you
do
them
like
a
log
splitting
you
know
kind
of
how
they
roll
I,
think
How,
They,
Roll
together
and
then,
along
with,
where
they
came.
Like
obviously,
all
these
new
apis
didn't
come
out
until,
like
a
404.,
I'll
fill
in
all
the
other
minor
versions,
but
trying
to
kind
of
get
a
bearing
for
when
5-0
comes
out,
you'll
be
able
to
look
and
see
all
these
parameters.
Oh,
they
didn't
even
show
up
until
this
version.
Here's
what
they
are.
C
Here's,
maybe
some
recommended
settings
right
so
enough,
for
you
know
20
seconds
whatever
it
is
120
seconds
and
then
an
hour's
worth
of
transactions.
Things
like
that,
so
really
trying
to
kind
of
go
through
and
and
even
I
mean
things
like
yo.
This
is
when
history
deprecated
actually
just
saw
somebody
run
into
that
this
morning.
Upgrading
a
node,
yeah
V1
history
is
deprecated
now,
but
you
would
know
that
if
you
were
able
to
compare
two
to
four
right
or
what
new
things
are
coming
out.
C
C
C
H
C
F
You
should
you
know
like
what
you
were
saying
like:
oh
there's,
just
no
time
to
document
and
whatever
but
hey
yeah,
there's
a
seed,
it's
already
started
to
grow.
There's
a
lot
of
of
the
groundwork
is
already
in
there.
You
know,
if
anything
you
could
just
build
on
top
of
it.
You
know,
and
that
would
be
like
gold
price.
C
And
a
lot
of
it
has
to
do
with
just
kind
of
this
basic
understanding.
What
the
hell
do
these
actually
do.
How
do
they
even
play
together
right
I
mean
some
of
these.
Don't
even
make
sense
that
they're,
together
and
I'm,
not
even
sure
you
know,
I,
don't
know
why
Aaron
does
this,
but
it
was
in
its
config.
C
So
I
was
like
yeah
that
looks
important
anyway,
but
like
a
real
world
description
of
it,
why
what
it
does,
how
to
do
it
and
then
a
bearing
on
this
way
as
we
go
forward
as
we're
you
know
doing
whatever
you
can
easily
know
I'm
going
from
three
to
five.
Therefore,
oh
I
didn't
even
do
four,
but
your
release
notes
aren't
going
to
say
a
damn
thing
about
this,
because
they're
going
to
skip
them.
C
G
C
G
C
G
Understand
this
either
man
so
yeah
make
some
comments
here
and
yeah
that
that
would
be
great,
I'm,
sure,
I'm.
Sure
Matthew
darling
would
have
some
some
good
commentary
as
well
as
as
well
as
others
I
mean
every
every
block
producer
out.
There
probably
has
commentary
there.
I
could
see
some
of
these
spurring
some
pretty
good
discussions
right.
Oh.
C
C
H
C
C
G
C
H
C
Thank
you.
Thank
you.
So
yeah
look
forward
to
this
great,
a
great
starting
point.
Let's
say
If
eventually,
maybe
it
could
become
some
official
Doc
or
something,
but
at
least
in
the
meantime
we'll
you
know,
try
to
get
a
bearing
on
it
and
that's
why
I
say
if
you
can
give
me
some
of
those
parameters
we'll
be
happy
to
pump
them
in
there
I
know.
C
C
Correct
links
to
I
mean
I,
know
and
sometimes
I'll
go
and
hit
up
the
you
know
the
antelope.io
docs
I
guess,
but
yes,
the
the
you
could
definitely
be
fleshed
out
more.
It's
just
kind
of
one
seeing
it
right.
We
keep
talking
about
the
Matrix
and
I'm
like
this
is
at
least
what
I
saw
in
my
head.
I
think
it
may
be
what
Russ
saw
and
whatnot,
because
he
was
always
big
on
it,
but
just
visual
indicators
and
then
yeah
and.
F
C
F
Just
just
a
starting
point:
I
mean
I
know.
Whenever
we
get
into
these
discussions
on
any
of
the
other
network.
Calls
everybody
says:
oh
no!
No!
We
must
never
ever
all
just
copy
paste.
The
exact
same
configuration
Everybody
Must,
put
forward
what
they
feel
is
necessary,
but
it's
nice
to
have
a
vanilla,
Baseline
starting
point.
You
know.
C
Remember
one
here's
at
least
all
the
topics
correct
number:
two:
here's
a
little
description,
maybe
they're
wrong
right
now.
Kevin's
gonna
help
me
fix
that.
But
ultimately
you
know
a
starting
point
and
maybe
you
do
look
at
it
and
go
you
know
what?
No
not
everybody
should
run.
Four
threads
I
think
I'm
gonna
go
big
nuts
and
go
12.
all
right
cool.
At
least
you
know
what
it's
doing,
yeah
or
like
I
know.
I.
Think
Sweden
runs
these
higher
right.
So
you
can
process
bigger
transactions
cool
by
all
means,
but
you.
I
At
least
this
is
like
the
this
like.
What
you
guys
did
is
amazing.
It's
like
the
difficult
part
like
once
his
dad
has
put
into
you
know.
Just
like
a
Json
or
something,
then
you
can
have
like
a
very
simple
UI
that
can
do
all
those
things
like
filter
for
the
view
of
the
version
automatically
Group
by
you
know
feature
so
you
can
say,
like
oh
I
want
to
do
the
retry
transaction,
so
you
just
click
it
and
boom.
You
just
see
it
in
the
sample.
C
But
I
don't
mind,
bringing
a
version
up.
I
will
say
this
is
that
in
working
with
a
lot
of
the
VPS,
it
has
been
interesting
to
learn.
There's
a
lot
of
people
that
have
written
deployment.
Scripts
I
know
nation
has
like
you
know:
Uber
click
a
button
and
it
just
you
know,
spins
up
a
whole
network
but
different
ansible
Scripts,
different
things
that
say
Hey.
C
H
F
C
D
B
I
C
I
think
it's
in
stero,
since
he
has
VM,
came
out
you
all.
You
had
the
threads
to
go
along
with
now.
What
you
will
notice
is
I
did
kind
of
default
it
under
a
ship
node
right
and
there's
all
the
arguments
about
what
all
you
can
use
it
on
can't
use
it
on.
But
ship
nodes
are
like
read-only
data
out
nodes.
Everything
else
look,
don't
you
shouldn't
unless
you
know
too
right.
C
C
I
learned
I
think
that
that
may
have
come
from
Nations
to
give
credit
where
credits
do,
and
it
has
found
its
way,
probably
from
Kevin
originally
but
like
I,
say
it's
this
little
stuff
that
for
years
has
trickled
along,
and
the
other
problem
is
is
that
these
types
of
things
exist
indefinitely.
So
in
version
seven,
that
may
not
be
a
good
thing
to
do,
but
you
did
it
in
five
and
it
keeps
rolling
over
so
anyway,.