►
From YouTube: Node Operator Roundtable - April 19th, 2023
Description
This week, the EOS Node Operator Roundtable updates the community on Software Development and has a technical discussion on what hopes and dreams the developers have for the features and upgrades for Leap 5.0.0.
00:00:00 Start
00:00:03 Welcome to the Node Operator Roundtable and this weeks topics
00:00:17 Software Development update
00:02:00 Node Operators v5.0.0 genie’s lamp
00:08:34 Dynamic peer discovery
00:12:23 Supporting a multichain ecosystem
00:18:25 Getinfo 2
00:23:55 Payment system for small businesses
00:28:30 Experation dates on permissions
00:34:05 Parallelization of block validation
00:37:39 Native resource improvements
00:44:28 Loki integration for logging
00:49:03 Better peer management
00:57:10 End
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
B
That's
right
so,
as
was
discussed
last
week,
we
got
rc3
out
about
a
week
ago
yesterday,
since
it's
been
sitting
a
bit
and
things
seem
to
be
looking
pretty
good.
I've
not
had
any
truly
egregious
issues
come
through.
We
do
believe
that
we
should
be
on
track
to
likely
go
stable
sometime
early
to
mid
next
week,
so
we'll
just
be
tracking
against
that.
B
B
We're
also
closing
in
on
an
initial
RC
cut
for
CDT
v4.0.0,
the
versioning
being
the
same
number
right
now
isn't
any
sort
of
enforced
convention.
It's
just
coincidence
that
they
happen
to
be
the
same
version
number.
So
don't
let
that
confuse
anybody
tomorrow
at
9
00
a.m,
eastern
U.S
time
we'll
be
walking
through
the
the
antler
project
and
package
management
system.
That
is
part
of
all
of
that.
B
A
C
C
Yeah
cool
so
I,
say
5.0
here,
but
to
be
honest,
like
Let's,
Race,
The
Gaze
a
little
bit
and
just
say
you
know,
for
the
future
of
antelope
right
and
the
reason
for
that
is
because
there
might
be
something
that
you're
that
you'd
really
like
to
see.
That
you
think
is
huge
that
small
and
vice
versa.
There
might
be
something
that
you
like
to
see
that
you
think
is
easy
and
it
turns
out
that
it's
a
big
kerfuffle
to
to
build
it
right.
C
So
don't
worry
about
the
level
of
effort
involved
as
we
go
into
this
when
I'm
looking
for
is
just
you
know.
What
are
the
things
that
you
think
that
we
should
be
building
for
Antelope.
Obviously
we
have
a
we've.
Had
these
conversations
less
directly
over,
you
know
a
long
period
of
time,
and
so
we
have
our
own
sort
of
hypotheses
on
what
some
of
these
things
might
be,
that
you
know
I
want
to
I
want
to
sort
of
talk
about
it
directly
and
go
from
there.
C
C
B
C
C
There's
pragmatic
features
right.
So
the
thing
that
I
think
about
here,
whoops
I
lost
my
cursor
is
the
lighters
and
pain
relievers
right.
So
what
are
the
things
that
are
making
your
life
easier,
whatever
wow
I
just
misspelled
that
what
are
the
things
that
like
take
away
a
pain?
This
is
this
can
be
for
nude
operators
or
users,
and
so
from
that
restrictive
I'll
say:
what
do
you
want
to
say.
C
I
guess
I
should
say
a
user
of
an
antelope
Network
and
those
those
are
the
big,
the
big
sort
of
categories
just
I'd
put
those
there
more
as
a
context
setting
like
so
that,
if
you,
if
you
find
yourself
sort
of
struggling
to
feel
like
you
have
something
to
add
to
this,
you
know
take
a
look
at
some
of
these
and
and
give
it
a
shot.
There's
no
bad
ideas.
C
C
We
need
to
knock
this
down
several
notches
to
make
it
realistic.
You
know
that
that
can
come
later,
so
with
all
that
context,
set
I
do
want
to
do
this
a
little
differently
than
usual,
which
is
usually
it's
very
unstructured
and
and
like
we,
you
know,
I,
just
sort
of
have
an
open,
Forum
I
would
like
to
actually
kind
of
go
person
by
person
here
with
this
question
of,
if
you
had
a
Genie's
lamp
and
could
have
three
wishes
for
the
future
of
antelope
features.
What
would
you
wish
for
right?
C
If
there's
if
it's
instead,
you
don't
know
what
the
feature
is,
but
it's
a
problem
even
better
right,
so
problems
to
solve
right
and
so
with
that
before
I,
just
all
on,
if
I
call
your
name
and
you're
like
I,
don't
have
anything.
That's
that's
fine!
I'll
give
you
a
few
a
few
moments
to
speak
out.
Then,
if,
if
you
don't
I'll,
just
assume
that
you
don't
have
anything
I'll
call
someone
else
before
I
do
that?
Does
anybody
want
to
volunteer
to
be
the
first
to
speak
up.
D
So
you
know
to
look
at
black
routine
protocols
like
an
ospf
type
thing,
some
kind
of
idea
that
there
is
a
metric
associated
with
the
amount
of
latency
between
peer
A
and
P,
a
b
or
bandwidth
between
and
BP.
You
know
some
some
kind
of
table
that
is
dynamically
built
for
a
selection
of
which
is
going
to
be
the
the
best
pass.
D
Up
quite
like
it's
not
quite
latency,
optimization,
it's
more
about
selection,
so
you
can
discover
the
peers
and
then
you
select
the
best
pair
based
on
latency
or
bandwidth
or
whatever
the
criteria
is
number
of
I.
Suppose
it
wouldn't
be
hops,
then
right
whatever
it'll
be.
You
know
some
something
that
that
you
know
that
the
the
peer
that
is
selected
is
going
to
be
the
best
pair
right
and
I'm
sure
I'll.
D
C
D
Well,
you'll
be
sinking
blocks
with
to
the
chain
right.
You
turn
the
note
on.
Maybe
there's
an
option
in
config.inr
you
go
and
you
put
the
config
in
it's
saying:
Dynamic
selection.
You
know
a
lot
of
a
lot
of
usbps
like
to
force
where
we,
where
we
link
to
that's
all
good
but
then
enable
the
protocol
of
discovering
peers
some
kind
of
hellos
some
kind
of
Thomas.
Something
and
you'll
know
you
got
your
wish
because
you
didn't
configure
up
here
and
the
the
blockchain
was
synchronized.
D
And
two
right
well
well,
two
is
more
on.
You
know
that
you
are
thinking
really
quickly,
not
dropping
blocks
yeah.
A
lot
of
the
issues
we
have
when
you
have
a
latent
pair,
that's
being
used
is
because
of
what
you've
got.
You
know
if
you
go
and
throw
in
you
know,
20
odd
Piers.
One
of
them
is
running
out
of,
and
I
took
for
me,
it'll
be
really
fast
for
you,
guys
in
the
states,
it'll
be
slow.
C
All
right,
all
right,
so
just
to
recap:
we've
got
Dynamic
peer
Discovery
and
you
know
you
got
your
wish
when
you
sink
blocks
without
having
to
configure
peers
and
automatic
selection
of
best
peers
based
on
what
you
can
see,
bandwidth,
hops,
Etc
or
something
right,
and
you
know
you
got
your
wish,
because
syncing
is
fast
and
you're
not
dropping
blocks.
Yeah.
E
A
A
C
And
I
know
that
it's
more
of
a
problem-focused
statement,
but
that
is
fine.
Whoops
I
didn't
fighting
with
formatting,
which
is
my
least
favorite
thing
in
the
world.
There
we
go
so
I
know
this
is
more
of
a
problem,
Focus
statement
but
I
think.
Nonetheless,
if
the
problem
no
longer
exists,
did
you
would
have
your
wish
right?
So
how
about
a
statement
of
like
what
it
would
look
like
to
have
gotten
your
wish
here?
A
You
know
it's
compat,
it's
compatible
with
all
of
the
the
ecosystem
out
there
like,
for
example,
my
data
on
my
youth
application
is
easy
to
be
aggregated
on
the
data
aggregators
on
the
barato
one
three
space.
So
you
know
I
built
a
defy
app
on
EOS
without
a
huge
amount
of
effort.
My
data
should
start
getting
fed
into
all
the
you
know
D5
levels
of
the
world
right
now
you
need
to
build
custom,
connectors
or
EOS
to
be
able
to
feed
into
some
of
these.
These
aggregators,
for
example,.
C
C
A
And
that's
more
of
a
political
thing
than
a
technological
thing,
probably,
but
when
I
think
of
products
it's
more
than
just
the
tech,
it's
the
whole
package
and
support
around
it.
So
I
think
that
you
know
that
Tech
exists
and
make
this
easy.
But
there's
going
to
be
some
need
to
be
some
kind
of
Biz
Dev
work
to
to
make
that
really
truly
officially
supported.
A
C
G
H
G
Yep
that
additional
administrative
endpoint
that
expands
on
you
know
what
exactly
the
node
is
doing
running
plugins
the
information
about
the
the
the
node
itself.
Anyway,
we've
talked
about
that
in
some
of
those
other
conversations.
So
it's
kind
of
generalized
with
this
get
info
too
I
know
I'll
get
my
wish
when
there's
a
more
powerful
rest
query
that
you
know
in
a
Json
standard
that
can
be
used
to
better.
G
G
C
G
Fine,
it
I
think
Aaron
had
actually
kind
of
mentioned
it
like
in
one
of
the
last
calls
and
basically
to
help
but
know
better
indicate
whether
it's
synced
up
and
should
be
used
or
in
like
a
health
query.
Does
that
make
sense
like
the
problem
is?
Is
you
can
get
these
nodes
in
a
replay
or
resyncing
or
behind
or
whatever,
and
you
really
have
to
do
intense
Health
checking
on
it
when
the
node
knows
that
it's
not
in
sync,
so
if
it
would
be
able
to
say
no,
no
I'll
be
back
in
a
few.
G
B
G
G
There's
like
a
is
ready
and
point
that,
let's
the
you
know
a
200
response
or
a
Json,
okay,
whatever
it
is,
that
kind
of
lets
the
load.
Balancer
know
yep,
I'm,
ready
or
any
query.
I
mean
I'm
using
it
as
a
load
balancer,
but
you
could
use
it
publicly
as
well
check
is.
Is
this
node
think
it's
it's
okay
to
start
serving
requests?
Yes,
no
okay,
then
use
another
one
or
or
whatever,
but
yeah.
G
Correct,
like
say
I
mean
it
could
be
roll
wherever
Aaron
had
mentioned.
You
know,
quick
library
returns
a
200
status,
then
you
could
use
statuses
and
whatnot.
But
yes,
that's
what
I
say:
I
mean
it's
really
just
a
better
ability
like
when
it's
replay
it
knows
not
to
turn
the
API
out,
but
when
it's
syncing
or
or
it
doesn't
yeah
yeah
and
it
starts
serving
bad
stale
data
and
people
can
really
pick
it
up.
Yeah,
even
like
State,
history,
beans
and
stuff.
Like
that,
you
know,
I
mean
it,
it
doesn't
realize
it's
not
happy.
C
F
Yes,
sir
I
considered
a
functional,
more
the
most
functional
blockchain
we
have
or
as
folks
about
series
and
it's
been
years,
South,
America
and
Africa
for
Rick
and
mortar
things
and
branding
done
at
very
low
levels
and
I
thought
making
it
the
infantation
on
that.
Whether
it's
record
device
do
I
know
one
or
two
blockchain
storms
launching
with
your
own
mobile
phones,
cheap,
so
I,
don't
know
what
Delta
will
be
about
to
that
donating
the
deer
for
anybody
in
the
world.
Rather
just
they
have
an
internet
connection.
F
I'm,
looking
even
more
even
more
small
business
in
our
baseball
business,
I
don't
mean
100
million
dollars.
Anybody
with
a
business.
They
connect
to
the
blockchain
they're,
choosing
credit
cards
instead,
gotcha
illustrator,
but
yeah,
empowered
sport,
yeah
I'm
in
aviation.
So
at
least
talk
about
Supply
chains,
Architects,
Supply
chains,
I
just
thought
it
was
too
much
to
bring
up
I,
wouldn't
understand.
A
F
F
I
C
J
C
J
It
would
be
it
for
temporary
got
this
authorization
of
apps.
Essentially,
you
know
you're
using
an
application
with
a
wallet
yeah,
and
it's
annoying
that
every
time
you
want
to
sign
a
transaction,
your
wallet
has
to
pop
up
and
you
have
to
approve
it.
So
if
you
could
create
a
temporary
permission
that
expired
in,
say
five
minutes
a
day,
whatever
the
time
frame
may
be,
that
that
way,
you
could
do
transactions
more
easily
within
that
application.
J
You
know
it
might
be
a
game,
it
could
be
a
D5
app,
it
could
be
whatever,
but
that
permission
would
then
expire
and
whatever
the
time
frame
was,
you
know,
kind
of
the
developer
or
you
as
a
user
could
specify,
and
then
I
guess.
My
second
wish
to
come
along
with
that
would
be
more
granular
permissions.
To
be
able
to
to
be
able
to
like
put
a
like
a
really
granular
example
would
be
putting
a
budget
on
a
key
be
like
you're
allowed
to
spend
20
years
on
the
eosio
token
contract,
something
like
that.
J
Yeah
or
you
can
power
up,
but
the
recipient
has
to
be
this
account,
something
that
you
can
really
like.
We
have
granular
permissions
in
that
you
can
specify
which
contract
and
which
action
that
key
can
perform,
but
if
we
could
also
specify
rules
that
matched
the
data
that
was
also
being
submitted
and
then
if
it
didn't
match
those
filters
that
the
transaction,
like
the
permission,
wouldn't
be
valid
at
that
point.
C
No
problem,
I'm
learning
that
too
seems
to
be
the
cut
off.
You
know
it's
funny.
There's
versions
of
this
exercise,
though,
where
you
you
actually
have
everybody,
do
it
silently.
First
and
it's
a
it's
a
quantity
play,
everybody
has
to
come
up
with
20
ideas,
and
then
you
select,
everybody
selects
their
top
view,
but
the
thought
being
that
you
know
when
you
have
to
come
up
with
20.
C
J
J
Yeah
I
think
it's
similar
to
the
first
one
and
the
expectations
you
know
like
when
it
exists,
but
I
think
it
would
be
specifically
when
we
have
some
sort
of
standard
to
write
these
things
and
apply
them
to
permissions.
You
know
that
one's
going
to
be
more
complicated
than
the
first
one,
but
both
together
create
this
pretty
powerful
thing.
G
H
H
F
K
You
know
how
we're
pushing
transactions,
how
we're
allocating
CPU
and
all
of
that.
So
within
that,
let's
say
I-
think
we've
talked
about
it
having
a
single
ethereum
ethereumeral
resource.
So
everything
that
is
a
sort
of
a
temporary
resource,
Ram
I,
think,
is
always
going
to
be
Ram,
but
everything
that's
CPU
and
net.
K
Instead
of
having
two
resources
to
manage,
having
one
resource
to
manage
kind
of
like
gas
or
whatever,
we
want
to
call
it
just
having
it
one
to
manage
instead
of
two
to
manage,
which
would
then
would
fall
back
into
just
deprecating
net
entirely
and
then
kind
of
putting
net
into
that
single
resource
and
third
is
kind
of
like
right.
Now
we
have
power
up,
which
is
a
one
day,
a
one-day
CPU
sort
of
a
allocation.
What
would
be
more
interesting
is
kind
of
a
low
CPU
cost
one
shot.
K
Let's
say
you
want
to
push
a
transaction
and
you
only
want
to
push
that
transaction
only
to
kind
of
like
just
pay
for
the
CPU
of
just
that
transaction
kind
of
like
a
one-time
gas
fee.
I
know
that
Aaron
with
with
anchor
wallet,
they
kind
of.
Do
that
with
say:
hey.
You
want
to
pay
for
this
one
one
transaction
and
then
you
pay,
you
know,
point
zero,
zero,
five
EOS.
K
That
would
make
it
much
easier
to
manage
resources,
because
you
can
guarantee
that
if
you're
using
this,
let's
say
a
One-Shot
CPU
push
transaction,
it
guarantees
the
CPU
of
that
particular
transaction.
That
way,
you
don't
have
to
maintain
the
daily
balance
or
a
monthly
balance
of
CPU.
So
there's
a
lot
of
monitoring
tools
to
just
make
sure
that
your
account
has
CPU,
and
it
makes
it
just
much
more
difficult
because
you
can't
just
say,
like
hey,
just
pay
for
whatever
transactions
that
I
pushed.
K
C
C
K
F
K
K
But
that
is
an
alternative
and
it's
actually
pretty
cost
effective
compared
to
the
maintenance
like
compared
to
maintaining
your
balance
of
CPU,
which
is
you're
just
paying
before
you
actually
do
the
transaction,
instead
of
paying
only
on
demand.
So
it's
just
different
model
and
I
think
we
can
probably
have
both
running.
We
can
have
the
daily
top
UPS
or
the
one
shot
top-ups
I
think
we
can
live
in
a
world
where
we
have
both
options.
I
K
C
K
Well,
I
mean
the
single
resources
just
being
able
to
manage
one
single
affirmative
resource.
So
let's
say
like
when
I
don't
have
to
manage
net,
then
that's
that
that
wish
is
essentially
solved
and
the
other
one
is
just
one:
I
can
do
when
I
can
have
zero
CPU
in
one
account
and
still
be
able
to
push
transactions.
You
know
atomically
with
that
sort
of
top
up
or
that
one
shot.
So
when
I
have
series
of
you
and
I
can
still
push
a
transaction
and
not
have
to
not
have
to
monitor
my
account.
K
C
E
I'm
just
now
getting
into
playing
around
with
some
of
the
Prometheus
stuff
from
4.0.
So
if
I
could
Bang
the
Drum
of
monitoring
a
little
bit
more
and
go
step
further
and
say
maybe
Loki
integration
for
logging,
if
we're
already
hooked
up
to
Prometheus,
it's
next
logical
step,
see
BP
monitoring
some
sort
of
better
way
to
obviously
at
Grandma's
we
have
quite
a
few
block
producer
nodes.
E
Something
and
I
know
that
there's
split
between
Aloha
and
some
of
the
kickbots
and
something
so
it's
just
not
not
telegram
is
not
the
only
option
that
would
be.
That
would
be
outstanding,
something
that
where
we
don't
have
to
use
telegram
where
we
could
either
pump
that
directly
into
slack
or
or
there's
some
sort
of
API
that
we
could
call
to
get
that
information
a
little
bit
easier.
C
C
E
I
C
E
E
C
E
G
G
What'll,
probably
have
what'll
probably
help
him
is
being
able
to
expose
that
net
plug
in
in
that
isolated
environment,
how
y'all
are
expecting
different
ports.
The
problem
is
is
once
you
enable
the
net
plug
in
on
a
public
node.
Somebody
else
can
do
it
for
you,
but
if
you
can
hide
it
like,
we
were
talking
about
splitting
out
these
abilities.
Yes,
the
tool
exists,
but
he's
been
trained
not
to
turn
it
on,
because
we
do
you're
gonna
you
can
get
wrecked.
So
that's
probably,
is
that
Forum
or
Baba.
C
F
C
G
C
G
B
I
I
C
C
G
C
C
C
You
know
like
yes,
I
need
this
too,
like
that's
a
very
useful
comment
in
and
of
itself,
or
you
know
now
now
that
we
have
the
ideas
down.
If
there's
any
sort
of
like
critical
thought
on
some
of
these,
not
to
say
you
know
being
mean,
but
but
just
like
hey
here's,
why
I
think
this
wouldn't
be
a
good
idea
right?
Those
sorts
of
things
would
be
helpful
too
and
yeah.
So
the
you
know
I'm
just
this
is
basically
a
learning
exercise
that
we
know.
C
We
know
you
know
at
least
one
perspective
on
where
things
should
be
going,
which
is
the
node
operator
perspective.
You
know
we're
also
doing
similar
exercises
with
developers
and
folks
that
are
not
actually
in
the
web
3
space.
Currently,
you
know
like
prospective
targets
anyway:
I'll
stop
there
and
hand
it
back
over
to
Daniel.