►
From YouTube: EOS MANDEL Meeting #12 (April 27th 2022)
Description
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues
#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.
00:00 Topics of the day
01:52 Progress made on different operating systems
05:09 Light versions of VMs
07:00 Support for Developers using iOS
09:03 Concerns regarding financial consumption
10:15 Time frame for testing the Mandel Upgrade
11:20 Survey for Pomelo participants, smart contract developers and node operators
13:11 Focus on Mandel with regards to Mac support and documentation
16:34 Clarification on why the survey is done (by Yves LaRose)
18:16 EOS Support and its Dapp developers
18:51 Entry points and potential issues with WEB IDE
23:09 Updating WEB IDE (regarding protocol features on different operating systems)
26:11 Different Environments to consider
28:55 Docker as an acceptable alternative with MAC and Windows support
34:17 Update on Items for Mandel 3.1 & 3.2
40:13 Testing progress made on the Jungle test-net
45:12 CPU issues on WAX with regards to account creation
// 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.
It
is
april
27th.
This
is
our
12th
time
meeting
quick
recap.
From
our
last
meeting,
we
discussed
the
survey
to
pomelo,
grant
participants
to
get
the
gauge
of
mac
dropping
mac
support
for
mantel.
I
can
give
a
quick
update
there
we
talked
about
now.
We
were
up
to
four
engineers
on
the
enf
and
there's
work
in
progress
on
a
process
to
prioritize
the
scope
for
3.1
and,
what's
going
to
be
moved
into
3.2
we've
made
progress
on
the
survey
to
node
operators.
A
A
A
B
A
C
Yeah
sure
so
so
so
the
current
state
of
that
is
everything's
working
under
linux,
windows,
10
and
11,
and
mac
os
arm
m1.
So
the
only
thing
I
don't
have
is
an
x86
64
to
basically
go
in
and
make
sure
everything
still
works
and
then
also
make
the
documentation
for
what
that
would
look
like
and
currently
what
this
is.
C
Is
it's
effectively
a
program
that
kind
of
straddles
over
docker,
nodeos
and
clios
to
kind
of
abstract
over
most
of
that,
so
from
a
developer
standpoint,
it
should
be
a
really
nice
tool
for
them
to
be
able
to
use
honestly
better
than
anything
that
we've
had
before
so
it
could
be.
You
should
be
more
of
a
win
than
a
loss
of
native
binary
packages.
A
Great-
and
I
I
was
while
discussing
with
my
team,
the
the
survey
to
gauge
the
the
sentiment
on
dropping
mac
support
denny
was
telling
me
that
there's
in
addition
to
docker
there's
other
options
that
are
becoming
more
widely
chosen
by
mac
developers,
it's
like
more
of
a
vm
type.
That's
easy
to
easy
to
run.
Anyone
familiar
with
that
and
whether
that
perhaps
an
alternative
option
we
should
be
documenting
or
or
does
this
docker
solution
is?
Is
this
kind
of
the
the
more
recommended
solution
we
should?
We
should
be
documenting.
D
B
C
People
are
using
the
cloud.
The
same
I
mean
the
thing
with
docker.
Is
that
there's
a
lot
there
of
composing
the
the
the
main
object
itself,
the
main
image,
so
it's
more
than
just
sort
of
you
know,
pulling
an
image
and
then
setting
everything
up,
there's
a
lot
there
with
port
forwarding.
So
there's
a
lot
of
niceties
that
you
get
with
having
multiple
instances
running
inside
this
docker
unit
and
then
effectively
kind
of
switching
the
porting
so
that
you
have
different
ports
coming
out.
C
B
Yeah,
the
other
thing
I
was
going
to
say
is
generally
docker
images
take
less
resources
on
a
machine
than
a
full
vm
vms
want
you
to
allocate.
You
know,
disk
space
and
a
whole
bunch
of
other
stuff
and
the
docker
container
kind
of
runs
inside
the
already
allocated
space
and
everything.
So
that's
why
people
tend
to
use
docker
they're
light
versions
of
vm
they're,
not
really
a
light
version,
but
they
use
less
resources.
B
C
So
so
I
had
to
make
a
a
couple
of
different
changes.
I
still
need
to
go
back
and
fix
a
few
different
things
before
I
push
up
the
pr,
so
we
had
to
make
some
changes
to
get
it
to
compile
properly
for
arms
and
then
a
few
other
things
so
that
basically,
the
the
vm,
the
ubuntu
version
that
we're
going
to
run
in
the
m11
is
a
arm,
so
there
shouldn't
be
any
degree
of
it.
C
The
thing
is
that
you,
don't
you
don't
have
the
same
back
end
of
the
esdn
did,
but
if
you're
for
development
purposes,
it's
really
not
that
big
of
a
of
a
deal
you
know
the
main
thing
here
is:
it
should
be
for
development
purposes,
somebody's
planning
on
running
a
node.
Definitely
they
don't
want
to
run
it
docker.
No,
they
don't
want
to
run
it
on
espn.
Without
you
know,
jits
I'd
say
that
there's
some
degree
of
figuring
out
who
the
main
who
the
main
person
is
that's
going
to
be
using
this.
B
B
E
C
C
The
interest
so
the
the
inline
assembly,
you
know
changed
it
out
for
some
arm
stuff.
That
needs
to
be
there
for
one
or
two
of
the
spots
that
actually
does
need
to
be
there
for
everything
else.
We
can
just
kind
of
if
it
out
for
right
now,
because
you're
just
losing
the
support
for
espn
jit
for
for
right
now,
if
we
decide
we
want
to
support,
you
know,
if
arm
becomes
a
big
thing
outside
of
just
mac
right,
then
we
can
allocate
resources
too.
It
might
I
mean
the
vendors
are
building.
B
A
Keeping
the
existing
mac
developers
happy
by
not
taking
away
their
ability
to
keep
working
the
way
they
work
awesome.
So
so,
though,
if
I
understand
correctly,
the
the
packages
are
done,
it's
been
tested
on
m1
you're.
You
need
an
intel
mac
to
do
the
testing
on
for
the
intel,
mac
and
and
some
work
to
be
doing
to
do
all
the
documentation
yep.
A
Can
we
do?
We
have
give
a
sense
on.
I
think
we
were
targeting
this
week
do.
Do
you
have
a
sense
on
when
how
much
time
that
would
I
guess
you
need
to
get
your
hands
on
them
on
an
intel
mac?
Do
you?
How
would
yeah
do
you
have
a
sense
on
timing
on
when
the
documentation
and
testing
would
be
done
for
this?
One.
A
Cool-
let's,
let's
assume,
let's
give
it
two
weeks
for
now.
Okay,
what
is
that
yeah
and
check
back
in
we'll
check
back
in
next
week
see
how
it's
going,
and
this
will
be
great
yeah
to
bundle
with
the
you
know,
we'll
be
putting
out
a
nice
package
for
developers,
letting
them
know
hey.
This
is
coming
here's
how
you
can
be
prepared-
and
this
can
be
part
of
that-
that
package
great.
Thank
you
on.
In
the
same
topic,
we
were
discussing
the
sending
out
a
survey.
A
So
after
discussing
the
the
survey
with
the
team,
the
problem
we're
trying
to
solve
the
audience
that
we
have
in
pomelo,
we
we
think
that
a
maybe
a
larger
a
couple
options
we're
going
to
be
sending
a
more
extensive
survey
survey
to
all
pomelo
participants
in
the
coming
weeks,
kind
of
a
thanks
for
participating
in
pomelo
survey
that
we
can
include
some
of
these
questions
about
you
know.
Are
you
a
mac
developer
and
how
do
you?
How
do
you
do
your
development
and
is
a
docker
image?
Gonna
be
is
gonna.
A
A
Would
there
be
value
in
having
a
separate
survey
kind
of
as
part
of
this
initiative
to
smart
contract
developers
just
about
mandel?
More
generally,
are
there
other
types
of
besides
mac
support?
Are
there
other
things?
We
should
be
surveying
smart
contract
developers
about,
and
would
it
make
sense
to
have
kind
of
similar
to
how
we've
got
the
survey
that
stan
put
together
for
us.
A
Is
there
something
like
this
that
maybe
we
want
to
send
to
all
smart
contract
developers
and-
and
we
got
the
eos
support
contact
list
as
well?
So,
in
addition
to
all
of
their
exchanges,
they've
got
contacts
for
they've
got
a
large,
I
think
300
or
so
contacts
in
total,
including
both
exchanges
and
app
developers,.
E
Well,
that's
not
related
to
mandel
upgrade.
I
mean
I
mean
it's
nice
to
have
some
opinions
from
from
the
crowd
about
tools
that
they
use
or
problems
that
they
want
just
to
be
solved,
but
it's
not
related
to
mandala
upgrade.
I
mean
we
have
the
whole
initiative
in
one
of
the
enf
streams
that
targets
the
developers
and
development
environments
and
new
debugging
tools
and
testing
frameworks,
and
so
on,
so
that
work
is
basically
a
different
stream.
I
mean
here
here
we
just
upgrade
the
network.
That's
what
we
should
care
about.
A
Sure
yeah,
but
the
so
the
enf
asked
us
to
gauge.
You
know,
put
out
a
try
to
gauge
what
the
impact
would
be
of
dropping
mac
support
doesn't
again
there's
many
different
ways
we
can.
We
can
do
that.
It
doesn't
have
to
be
part
like
you
know,
like
I
said,
I
don't
think
this
should
be
part
of
this
survey.
A
E
E
I
had
a
few
interviews
with
such
as
basically
that's
the
base
of
our
blue
paper
for
core
plus
yeah,
making
it
such
a
sorry.
We
didn't
focus
on
mac,
but
we
focused
more
on
on,
let's
say,
higher
level
topics
that
need
to
be
discussed
and
most
of
concerns
were
about
documentation
that
you
want
to
to
do
something.
You
have
no
idea
how
and
then
there's
no
guideline,
no,
no
documentation
so
that
so
yeah
for
mac
support.
I
mean
if
we
provide
an
alternative
to
to
mock
users,
they'll
be
happy
to
use
it.
A
Another
question
yeah
and
a
question
that
came
from
my
team
as
as
we
were,
you
know
thinking
through.
How
might
we
phrase
this
question?
Is
I
guess
what
what
would
the
enf?
What
was
the
enf
goal
with
the
like?
Is
there
a
threshold
that,
for
example,
would
make
make
us
decide
that
it's
worth
prioritizing
keeping
mac
support,
for
example,
or
you
know,
have,
has
the
decision
already
been
made
that
we're
dropping
back
support
regardless
of
what
results?
What
the
results
of
this
survey
are.
F
No,
otherwise
I'd
be
pointless
to
do
the
survey,
so
this
decision
was
made
prior
to
engineers
joining
the
enf
right.
So
this
group
right
had
already
decided
that
they
were
dropping
max
support
with
mandel,
and
then
the
issue
was
re-raised
and
we're
now
attempting
to
gather
more
information
to
see
whether
or
not
we
may
have
missed
people,
not
the
largest
database
of
developers
that
we
have
likely
is
through
pomelo
of
active
developers
on
eos,
and
so
that
would
give
a
sense
as
to
whether
or
not
they
would
benefit
from
that.
F
I
can't
tell
you
what
the
threshold
would
be
get
the
data
first,
but
yes,
the
idea
is,
then
we
would
be
open
to
re-opening
that
question
for
sure.
Otherwise,
there's
no
point
to
do
the
the
survey
but
get
the
data
first
and
we
can
see,
and
then
we
can
see
as
a
group,
because
as
a
group
we
made
that
determination
as
a
group,
we
would
make
the
determination
as
to
whether
or
not
the
threshold
is
is
now
being
met.
A
Okay,
so
yeah,
we
will
make
sure
we'll.
I
think,
in
addition
to
the
pomelo
audience
like
I
said,
I
think
our
team
looking
at
our
audience
is
probably
gonna,
be
it's
probably
minor
in
terms
of
the
smart
contract
developers.
But
let
me
talk
to
the
to
eos
support.
I
don't
think
randall
is
randall
on
the
call
about
yeah.
I
see
him
here
but
he's
on
his
iphone.
I'm
not
sure
if
you
can
speak
randall,
maybe
you
and
I
can
catch
up
offline
about
also
including
your
dap
developers
on
your
list.
F
So
one
of
them
would
say
is:
is
we're
now
delaying
this
delaying
this
the
longer
we
delay
this,
the
the
likelier
that
we
are.
We
can
actually
get
the
support
in
in
time
for
the
release.
So
right
now
we're
talking
about
increasing
the
scope,
increasing
the
scope,
increasing
the
scope.
We've
wasted
the
last
three
weeks,
not
sending
out
the
one
question
that
really
we
want
to
ask
so
just
be
cautious.
G
C
I
don't
believe
it
did.
I
haven't
seen
it
anywhere,
it's
a
you
know
the
the
it
is.
It
is
a
really
nice
tool
for
people
that
are
just
sort
of
getting
started
started.
I
I
think
that
there
was
a
lot
of
things
there
that
was
still
missing
and
still
needed
a
lot
of
work
to
kind
of
really
become
a
full-blown
set
of
tooling.
C
C
I
definitely
think
that
as
we
move
forward,
we'll
want
to
try
to
support
more
of
the
you
know
the
the
year
one
developers,
but
for
me
the
biggest
thing,
I
don't
want
to
make
sure
that
we
that
we
don't
lose
is
the
developers
that
we
currently
have.
So
this
is
sort
of
a
big
focus,
but
the
web
ide
thing
I
I
don't
know
I
would
be
interested
in
terms
of
the
survey
to
figure
out
how
many
people
were
using
the
web
ide
inactive
development
because
it
always.
B
B
C
C
It's
also
not
it's
incredibly
clear
of
how
to
restart
your
web
ide
in
the
same
context.
So
it's
sort
of
a
thing
of
if,
if
you
leave
it
long
enough,
then
it'll
blow
away,
and
then
you
lose
your
your
development
environment.
You
have
to
you,
know,
constantly
make
sure
that
you're
using
either
a
github.
C
G
I
can
only
report
for
for
my
team,
but
some
some
specific
features
like
working
on
different
branches.
You
spin
up
your
workspace.
You
spin
up
a
new
chain,
deploy
your
contracts,
some
front-end
developer
developer
can
directly
contact,
can
directly
communicate
with
the
with
the
web
ide
and
whatever
interact
with
it.
You
can
share
the
workspaces
you
don't
have
to
to
host
multiple
test
nets
with
different
smart
contract
states
and
stuff,
like
that.
A
C
There's
gonna
be
serious,
it's
basically
updating
the
I
mean
I
don't
really
know
what
all
we
want
to
do
there.
So
I'd
have
to
kind
of
come
back
to
you
so
who?
What?
What?
What
do
we
want
to
target
in
terms
of
the
different
components
that
are
in
it?
I
think
there's
still
some
open
questions
to
what
we're
still
going
to
continue
to
support
moving
into
the
future.
We.
C
Responsible
for
it,
he
needs
more
than
an
owner,
though,
like
there's
decisions
as
to
what
is
the
de
facto
tool
chain.
What
is
the?
What
is
the
scope
of
the
project?
And
you
know
that
kind
of
thing.
So,
at
the
beginning
of
this
it
was
just
literally,
let's
just
use
get
pod
and
you
know
get
get
a
thing
that
works
and
get
pot,
and
then
we
kind
of
stop
there.
So
it's
you
know
if
it
was
the
sport,
that's
really
just
a
docker
image
upgrade
right.
C
We
need
to
have
packages
and
releases
for
mandel,
then,
once
we
have
that
we
can
have
a
binary
package
that
comes
off
of
mandel,
that
we
build
the
docker
image
because
it's
all
based
on
docker
anyway
right.
She
saw
everything
in
the
world's
docker
at
this
point,
so
so
that's
the
main
thing
is
that
you
update
that
image
to
effectively
pull
the
manual
up
the
manual
binaries
and
then
you're
you're
pretty
much
good
to
go.
I
don't
think
that
anything
has
changed
in
terms
of.
C
A
How
many
are
using
web
ide-
and
I
guess
this
is
more
than
we
want
to
gauge
a
lot
more
broadly
than
just
mac
developers.
It
would
be
useful
to
understand
how
many
people
in
general
are
using
web
ide
is
this?
Am
I
does
this
make
sense?
What
development
platform
then
versus
environment
am?
I
are
these
categorized
correctly
yeah
and.
A
C
A
C
I
mean,
I
think,
yeah.
I
think
it
would
still
be
interesting
to
get
as
a
development
environment,
because
then
it
can
kind
of
guide
us
of
okay.
The
developers
typically
use
windows
for
their
main
boxes,
but
they're
ssh
against
cloud
vms.
You
know
they
can
still
give
us
a
good
degree
of
what
people
are
doing
with
their
sort
of
things
that
they
are
used
to.
G
C
There's
a
lot
of
different
repos
you
can
or
distros
you
can
pull
down
into
that,
but
it's
just
a
subsystem
for
linux.
Basically
it
redirects
syscalls
and
does
some
emulation
under
the
hood.
But
it's
pretty
it's
pretty
it's
a
pretty
nice
system,
especially
with
with
the
so
well,
and
one
thing
there
is
wsl
one
was
pretty
flaky
in
terms
of
supporting
nodeos,
because
the
way
that
it
handled
emulation
of
files
and
and
really
was
was
terrible.
Wsl2,
I
think,
is
pretty
good
in
terms
of
supporting
modeos
and
everything
that
we
kind
of
had.
A
A
C
Well,
not
necessarily
doctor's
success
and
acceptable
alternatives,
so
the
way
that
it's
set
up
is
that
you
don't
interact
with
any
of
the
doctor
stuff
yourself.
You
there's
an
abstraction
layer
there,
so
basically
blankets
over
all
of
the
docker
stuff,
and
you
use
it
much.
You
use
it
in
the
exact
same
way
that
you
would
nodeos
or
clios.
C
You
know
from
the
general
command
line.
If
you
have
files,
you
don't
have
to
worry
about
how
you
pipe
those
through
the
docker
or
create
the
volumes,
and
all
that
you
don't
have
to
worry
about
how
you
do
the
port
forwarding
through
the
thing
so
there's
there's,
there's
there's
sort
of
a
thing
there
of
it's
docker,
but
it's
sort
of
docker
behind
the
scenes.
So
I
don't
know
if
we
want
to
necessarily
say:
are
you
guys
good
we're
just
moving
to
docker,
because
it
is
a
fairly
big
headache
or.
C
Yeah,
I
don't
know
it's
still
not
like
the
thing
is
it's
trying
to
emulate
natives
right,
like
it's
just
the
whole
sort
of
point
of
this
thing,
just
trying
to
emulate
native
on
on
their
machine,
so
I
don't
want
to
make
it.
I
don't
want
to
label
anything
that
would
make
it
sound
like
we're
just
going
to
sort
of
stop
supporting
mac.
B
B
C
G
C
C
Plus
we
now
have
windows
support,
which
is
something
that
we've
never
really
supported
at
all,
and
you
know
and
it
once
again
it
works
perfectly
in
linux.
So
it's
me:
it's
a
nice.
It's
a
nice
general
solution
that
kind
of
solves
across
all
the
boundaries,
so
that
there's
consistency
in
terms
of
how
you
use
the
the
system.
I
think
that
that's
another
area
that
we've
kind
of
struggled
at
is
you
know.
B
A
A
A
B
I've
made
a
a
project,
a
3.1
release,
project
in
the
eos
network
foundation
organization
that
has
all
of
the
pull
requests
or
issues
that
were
marked
3.1
candidates
or
3.1
approved,
and
right
now,
there's
two
3.1
approved
log
splitting
and
then
a
an
interest,
an
inflation,
sorry,
an
inflation
bucket
pr.
So
those
two
pr's
have
been
approved
by
eve,
the
other
ones
we
need
to
kind
of
talk
about.
They
are
candidates
and
the
people
that
kind
of
mark
them
as
candidates.
B
We
should
kind
of
get
them
together,
I'll
need
to
pull
together.
A
meeting
of
you
know
the
engineers
plus
stan,
plus
maybe
matthew,
darwin
and
and
and
kevin
hefner
and
and
look
through
those
and
decide
do
any
of
those
really
need
to
go
in
or
were
they
kind
of
nice
to
have,
but
so
far
that's
how
the
process
is
working.
We
have
a
bunch
of
pull
requests
that
live
across
the
11
repos.
B
Stans
and
kevin's
list
are
linked
off
of
the
wiki
page
under
the
mandel.
Repo
matt's
list
is
still
kind
of
too
much
in
flux,
so
we've
just
people
that
would
like
to
see
it.
We
can
share
a
link
to
it,
but
it's
gonna
open
permissions.
So
we
don't
want
people,
you
know
random
people
from
the
internet,
changing
it
at
this
point
and
so
that
that
is
that
list
is
possibly
has
some
things
that
we
will
see
that
we
need
to
pull
in
as
well.
But
it's
you
know
times.
B
B
So
yeah,
why
does
we
click
on
that
and
see
if
it
pulls
up
something?
You
can
read
it's
in
the
chat.
Anyone
can
look
at
it
in
the
chat
for
the
zoom
call.
There
you
go
so
you
can
see
the
ones
mark
3.1
candidate.
You
can
see
the
ones
mark
approved.
Seven,
not
eight!
Sorry,
sorry
that
I
was
guesstimate,
seven.
B
B
And
the
the
seven
could
increase,
and
obviously,
if
some
of
the
seven
or
the
increasing
number
some
of
them
could
end
up
being
approved.
This
is
the
at
least
the
project
board
that
I'm
trying
to
track
off
of
so
that,
as
we
see
them,
you
know
we're
just
taking
issues
or
pull
requests
and
then
just
pulling
them
into
this.
B
D
I
A
I
F
I
I
Three's
there
yeah
jungle,
four
is
not
there.
I
I
think,
and
maybe
that's
somewhat
of
a
you
know.
Jungle
three
I
know
is
being
asked
in
the
channel.
You
know
where
the
nodes
they're
all
kind
of
spinning
down,
I
think
even
stan
said
jungle's
dead.
Juggle
30
is
dying,
you
know,
but
do
we
want
to
start?
You
know
shifting
more
over
blocks.
I
think
you
know.
I
mean
things
like
that.
I
think
that
was
another
question
about
explorers
and
whatnot
we're
kind
of
in
this
straddle
on
jungle.
But
I
don't
know.
I
F
I
mean
is
that
I
I
looked
into
it
yeah,
so
it's
not
really
for
mandel,
but
I
guess
more
so
for
edm,
but
kind
of
relates
all
together,
because
we've
moved
people
over
to
jungle.
Four
right
now
we're
basing
off
the
performance
that
we're
seeing
on
jungle.
Four,
to
give
us
an
idea
of
what
it
would
look
like
when
it's
ported
on
to
the
main.
F
So
we're
wondering
whether
or
not
it's
because
the
bps
are
running
lesser
hardware,
which
which
is
likely
because
it's
a
test
now
but
then
we'd
be
able
to
approximate,
give
or
take
how
much
performance
increase
we'd
see
when
we
afford
the
mainnet,
because
we
do
know
what
the
main
hardware
is
running
generally
and
I
just
ping
the
aloha
guys,
because
I'll
try
to
find
out
if
they
can
add
jungle,
four
to
the
benchmarks
list.
That's
that
way
we
would
actually
be
able
to
see.
F
So
we
wouldn't
even
need
the
hardware
itself
we'd
be
able
to
see
what
the
delta
is
percentage
rising
is
an
idea
of
what
we
see
in
terms
of
increase,
because
then
that
relates
so,
then
that
translates
into
what
the
average
cost
per
transaction
will
be
for
the
edm
and
then
that
flows
into
the
token
model,
etc.
That
is
important
for
us,
and
I
was
just
wondering
because
I
know
some
of
you
are
running
on
jungle.
Four
on
this
call
and
manchester's
here.
I
I
can
give
you
if
the
eos
usa
side
they're
both
running
on
i9s,
I
mean
I
think
jungle
may
have
a
little
more.
You
know
it
may
have
another,
a
couple
chains
test
nets
on
it,
but
yeah
same
hardware,
same
speed.
If
that
helps
provide
at
least
one
stable,
you
should
look
at
all
those
crypto
lines
ones,
I
think
they're
all
running
on
the
same
server.
So
then,
once
you
get
that
one,
you
probably
have
you
know,
two-thirds
of
the
vps.
F
E
E
F
F
A
I
I
F
Very,
very
big
differences
cool
all
right,
I'll
I've
reached
out
to
to
patrick
from
aloha,
but
I
see
you
tag
mate
as
well,
so
we
can
find
out
whether
or
not
we
can
add
that
on
there,
because
I
I
I'm
on
the
site
and
yeah
jungle,
three.
Is
there
two
still
there
which
yeah
it's
not
even
running
anymore,.
E
Right
now
we're
in
the
conversation
in
wax
bp
channel.
We
are
hitting
the
limits
of
because
those
fast
cpus
have
128
gig
of
ram
maximum
and
we
need
more
ram
so
basically
we're
discussing
what
what
will
be
the
next
standard
hardware
platform
and
that
will
be
most
probably
a
slower
cpu,
with
a
higher
memory
support
yeah,
that's
for
wax
right,
yeah
yeah!
That's
what
I
mean,
but
I
mean
eos
will
hit
that,
especially
if
you,
if
you,
if,
if
our
evm
flourishes
and.
I
I
All
the
eos
io
chains
are
gonna
hit
it
it's
due
to
the
account
creation
so
when
they
start
really
ramping
up
a
lot
of
those,
and
that
seems
to
be
the
best
or
more
efficient
use
of
the
memory.
Now
I
mean
I
say
that
I'm
not
the
developer
and
I
know
the
limitations
in
the
way
the
state
works,
but
you
know
I
mean
yeah
requiring
hundreds
of
gigabytes
of
ram,
it's
getting
harder
and
harder.
So
anyway.
I
F
E
But
evm
itself
will
will
increase
the
run
consumption
because
all
integers
are
256
bits,
so,
whatever,
whenever
you
store
an
integer,
you
consume
32
bytes
for
it
right
so
and
and
then
usio
memory
management
is
up
on
top
of
that
as
an
overhead.
So
we
will
increase
the
ram
consumption
on
ears
as
soon
as
evm
starts
production
production
in
production.
As
soon
as
any
anything
big
starts
deployment
on
evm,
we
will
see
the
memory
increase,
so
we
will
hit
this
128
gig
limit
sooner
or
later.
Maybe
in
the
year
on
the
use.