►
From YouTube: Splintering of the EOS Mainnet
Description
Meet.One and BOSCORE are two new public EOSIO chains that were recently announced. There are also some prominent EOS applications that have gone the route of private EOSIO chains, instead of utilizing one of the existing public chains. In this episode, we explore the driving force behind this recent surge of EOSIO chains, and we question whether the initial vision of EOS might need to be adjusted.
CONTACT US:
Twitter: @EOSWeekly
Telegram: @eosweekly
SOURCES:
Dawn 4.0 post:
https://medium.com/eosio/introducing-eosio-dawn-4-0-f738c552879
Meet.One website:
https://meet.one/
Meet.One sidechain vision:
https://medium.com/meet-one/1-what-is-the-vision-of-meet-one-side-chain-a35d76faeae0
BOSCORE website:
https://www.boscore.io/en/index.html
BOSCORE whitepaper:
https://github.com/boscore/Documentation
Everipedia press release:
https://coinjournal.net/blockchain-encyclopedia-everipedia-unveils-improvements-expansion-plan/
EOSBet Scaling Post:
https://medium.com/@eosbetcasino/scaling-eosbet-6f1ada9def0a
A
Welcome
to
Yost
weekly,
there
have
been
some
interesting
developments
over
the
last
month,
or
so
with
regards
to
the
landscape
of
the
EOS
ecosystem,
with
several
new
yo
Co
chains
being
announced,
and
when
you
look
at
the
landscape
and
how
it's
been
changing
lately
to
some
extent,
it's
what
we've
been
expecting
all
along
a
rich
ecosystem
of
yo
Co
chains
with
a
lot
of
experimenting
going
on.
This
is
a
good
thing,
but
there
is
also
something
about
the
current
landscape.
A
That
is
a
bit
surprising
and
might
be
construed
as
a
bit
concerning
as
well,
and
the
concerning
part
is
that
the
number
of
private
yo
Co
chains
that
have
been
spinning
up
lately
is
increasing,
particularly
for
our
most
prominent
and
arguably
most
promising
applications
to
date.
It's
not
ideal
that
we
have
a
trend
like
this
starting
before
IBC
is
in
place
and
we'll
explore
this
further
throughout
this
episode.
A
Looking
at
this
private
chain
trend
objectively,
it
calls
into
question
whether
the
initial
vision
of
yose
is
still
a
valid
one,
or
if
maybe
we
should
be
embracing
a
slightly
altered
version
of
that
vision.
Before
we
get
into
this,
though,
just
to
quickly
mention
that
we
are
still
waiting
for
black
ones,
formal
set
of
governance
proposals
which
we're
expecting
to
be
released
any
time
now
we
covered
in
last
week's
episode.
What
we
believe
will
be
in
black
ones,
proposals
and
we're
excited
to
see
how
close
or
how
far
off
we
were
with
these
predictions.
A
But
in
the
meantime
there
is
this
important
issue
of
CPU
congestion
and
the
trend
towards
private
chains.
So
that's
what
we
wanted
to
cover
today,
let's
start
by
giving
a
high-level
overview
of
the
new
chains
that
have
been
recently
announced,
which
includes
a
combination
of
both
private
yo
co
chains,
as
well
as
some
new
public
chains
and
then
we'll
explain
this
potential
mind
shift
that
we
mentioned
earlier.
So
first
of
all,
we
have
two
new
chains.
A
Spinning
up
one
is
a
chain
by
meat
dot,
one
and
the
other
new
chain
is
called
Baz
core
or
we're
going
to
call
it
Baz
for
short
BLS.
Now
these
new
chains
have
been
referring
to
themselves
as
side
chains,
but
according
to
our
definition,
these
would
officially
be
considered
sister
chains,
not
side
chains.
A
With
this
definition,
side
chains
would
use
the
same
base
token
as
the
main
net
for
that
chain.
For
example,
on
the
EOS
main
net,
the
same
Neos
tokens
would
be
used
to
procure
side
chain
resources
on
the
Telos
main
net.
The
same
Telos
tokens
would
be
used
to
procure
this
Telos
I
chain
resources
now
currently
the
IBC
inner
block
chain
communication
that
is
needed
to
spin
up
a
few
side.
Chains
like
this
is
not
developed
yet
so
there
are
no
yo
side
chains,
yet
there
are
only
sister
chains.
A
The
meet
dot
one
chain
is
being
created
primarily
to
address
CPU
and
RAM,
becoming
unaffordable
on
the
EOS
maintenance
and
so
meet
dot.
One
is
launching
this
sister
chain,
with
resources
priced
in
there
meet
dot.
One
token
what's
driving.
This
is
that
the
EOS
main
net
has
been
having
some
congestion
issues
which
ends
up
resulting
in
affordability
issues
as
well
being
that
gaps
might
need
to
increase
their
yos
token
ownership
in
order
to
ensure
they
get
enough
processing
power
to
run
their
application
and
meet
dot.
A
A
Baz
core
is
coming
into
existence
for
similar
reasons
like
meet
dot.
One
Bosco
has
noted
the
CPU
and
RAM
congestion
issues
that
the
EOS
maenette
is
experiencing,
as
you
can
see
here
in
the
Bosque
or
white
paper,
but
Baz
is
more
of
an
experimental
chain
when
compared
with
meet
dot.
One
in
that
Baz
is
trying
out
some
new
approaches,
particularly
with
regards
to
the
consensus
algorithm,
we'll
do
a
deep
dive
into
the
baz
core
enhancements
in
a
future
episode.
Some
of
their
changes
do
look
promising,
also
like
the
meet
dot
one
chain.
A
A
Every
pedia
has
their
own
IQ
token
and
they
plan
to
use
the
IQ
token
for
managing
resource
procurement
on
their
new
private
chain.
The
ever
a-p-d
adapt
itself
will
run
on
this
new
chain,
along
with
some
other
new
taps
that
ever
pedia
is
building
they're
working
on
some
exciting
stuff,
a
prediction
market
kind
of
like
an
auger
and
also
an
oracle
service.
A
Now
Eva
coupe,
the
ride-sharing
app,
is
currently
running
on
their
own
private
yo
silo
chain
here
as
well.
Eva
does
have
a
desire
to
make
the
leap
over
to
run
on
the
EOS
main
net,
but
they
need
to
work
on
optimizing.
Their
CPU
and
RAM
usage
first
before
they'll
be
able
to
justify
doing
it
due
to
the
cost
involved
with
running
an
application
of
their
size
on
the
EOS
maintenance.
A
You
start
to
get
a
much
different
picture
of
what
Yeo's
looks
like
today
when
compared
to
how
we
might
have
envisioned
it.
Looking
say
a
year
ago
before
we
had
anything
concrete
to
look
at
before
the
EOS
maenette
launched.
Most
of
us
thought
it
would
look
more
like
this,
where
there
was
one
main
yose
blockchain
that
was
so
massively
powerful
that
pretty
much
the
entire
world
could
operate
on
top
of
this
one
main
chain.
A
And
yes,
we
did
have
this
horizontal
scaling
plan
of
side
chains
where
we
could
double
or
triple
the
processing
power
of
our
EOS
maenette
as
needed.
But
the
general
assumption
was
that
there
wasn't
a
huge
rush
on
this.
Horizontal
scaling
wouldn't
be
needed
for
a
while.
The
one
main
eels
chain
would
be
so
incredibly
powerful
so
as
to
easily
support
a
wide
spectrum
of
the
early
adopter
applications.
There
would
be
plenty
of
time
to
build
out
this
IBC
thing
for
the
horizontal
scaling.
It
would
be
ready
by
the
time
we
needed
it
right
wrong.
A
It's
a
chain
that
might
be
able
to
handle
a
few
hundred
small
to
medium
sized
applications,
but
once
any
of
those
applications
reach
a
certain
critical
mass
they're
likely
going
to
have
to
jump
ship
and
go
over
to
a
less
expensive
sister
chain,
or
they
could
go
the
route
of
spinning
up
their
own
private
US
I/o
chain.
At
least
this
is
the
bee,
we're
seeing
so
far
in
these
real-world
examples
with
these,
arguably,
our
most
prominent
us
aisle
applications
to
date.
A
A
Will
we
ever
be
able
to
run
something
the
size
of
Facebook
visa
and
the
Nasdaq
simultaneously
on
top
of
a
single
ousmane
net
chain?
The
answer
to
that
should
be
obvious.
By
now,
it's
a
resounding
no,
at
least
not
anytime,
soon,
the
early
vision
that
we
had
of
use
the
vision
of
it
as
this
one
main
chain,
with
a
few
side
chains
on
either
side
of
it,
serving
as
the
global
Internet
upgrade
and
supporting
a
new
version
of
the
financial
system,
social
networking
systems,
healthcare
and
insurance
systems.
A
All
these
industries
migrating
over
to
run
on
top
of
this
single
all-powerful
Yosa
chain.
This
vision
needs
to
be
adjusted.
What's
needed
right
now
is
a
mindset
shift
instead
of
holding
on
for
dear
life
to
the
one
chain,
with
a
few
side
chains
supporting
the
whole
world
vision.
We
need
to
start
thinking
in
terms
of
one
app
one
chain
or
even
one
app
multiple
chain
in
the
revised
modern-day
eos
vision.
A
It
will
be
common
for
depths
to
start
out
on
a
may
net
on
one
of
these
public
chains
here,
while
they
build
test
things
out,
make
sure
they
have
a
product
market
fit
and
so
on,
but
once
they
reach
a
certain
level
of
success,
a
certain
critical
mass
at
that
point,
they'll
graduate
to
their
own
side
chain.
It
would
be
naive
of
us,
the
EOS
community,
to
look
at
some
of
our
most
prominent
and
promising
set
of
us-based
applications
to
date
and
think
it's
an
aberration
that
they're
all
running
on
their
own
chains.
A
This
is
no
aberration,
and
this
is
no
coincidence
either.
It's
no
coincidence
that
all
of
our
most
prominent
apps
have
gone
in
this
direction.
What
you're,
seeing
here
without
a
doubt,
is
the
beginning
of
a
trend,
and
some
of
these
apps
will
even
take
it
a
step
further.
The
really
successful
applications
will
need
to
spin
up
a
second
or
a
third
yo
CEO
chain
under
the
same
application.
In
this
way,
the
initial
vision
has
been
completely
turned
on
its
head.
A
Now,
if
we
want
to
ensure
Yoast
continues
to
be
a
success
and
continues
to
dominate
the
third
gen
blockchain
realm,
there's
a
few
things.
We
need
to
focus
on
right
now.
First,
that
sidechain
and
a
blank
version
of
IBC
that
we
discussed
earlier.
This
needs
to
be
the
absolute
top
priority,
because
none
of
these
applications
here,
none
of
them,
want
to
go
through
the
arduous
process
of
recruiting
their
own
VPS
from
around
the
world
and
attempt
to
spin
up
their
own
decentralized,
govern
Depaz
blockchain.
A
This
is
the
future
that
we
need
to
be
working
towards
the
side
chain
and
abling
version
of
IBC
is
on
black
ones
roadmap,
but
we
haven't
gotten
an
update
from
block
one
on
the
progress
or
the
timeline
of
this
anytime
recently
it
seems
they
are
more
focused
on
building
gaps
at
the
moment.
So
the
question
is
why
why
is
block
one
not
more
worried
here?
A
Surely
they're,
seeing
what
we're
seeing,
surely
they're
seeing
the
trend
here
where
any
application
with
a
decent
amount
of
traction,
has
been
running
into
CPU
and
affordability
issues
and
leaving
the
public
chain
to
go
off
and
launch
their
own
private
chains.
So
why
hasn't
block
one
reprioritized
its
backlog?
Why
have
we
heard
more
about
ubi
over
the
past
several
months
than
we
have
about
IBC?
A
Why
have
they
not
bumped
side
chain
and
abling
IBC
to
the
very
tippy
top
of
the
list?
We
don't
have
an
answer
for
this.
If
block
1
were
to
deploy
a
mass
adoption
type
of
app
an
app
that
will
potentially
go
viral
if
they
were
to
deploy
something
like
that,
on
top
of
the
EOS
main
net,
utilizing
some
or
all
of
their
10%
Yeo's
token
supply
to
procure
network
resources.
A
This
will
only
exacerbate
the
current
congestion
and
affordability
issues
that
applications
like
elos
bet
are
experiencing,
and
it
would
likely
price
a
lot
of
the
existing
players
out
of
the
game.
We
know
that
block
1
is
targeting
a
q1
launch
of
their
first
application.
So
what's
going
to
be
super
interesting
to
watch
here
is
how
they
go
about
deploying
it.
They
will
likely
want
to
play
it
safe
and
deploy
on
their
own
private
Yoshio
chain.
A
Otherwise,
like
we
just
explained,
they
risk
crowding
out
the
existing
gaps
that
are
running
on
the
EOS
maintenance
going
to
be
a
politically
sensitive
issue,
and
if
they
do
announce
launching
their
app
on
a
private
block,
one
chain
like
we
believe
they
will.
It
will
trigger
a
backlash
from
the
token
holders
because
most
token
holders
have
not
shifted
their
mindset
over
to
the
new
reality
yet
and
mindset
shifts
like
this
take
time.
It
won't
happen
by
the
end
of
q1.