►
From YouTube: CasperLabs Community Call
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
coming
to
us
from
my
name,
is
metta
parlikar,
I'm
the
cto
casper
labs
and
one
of
the
co-founders
here
and
today
I'm
presenting
our
weekly
update,
engineering's
update
product
demos,
talk
a
little
bit
more
about
the
system
and
tell
you
folks
where
we're
at,
because
I
know
inquiring
minds
want
to
know.
People
are
curious
about
what's
going
on
with
the
platform,
so
we
do
this
call.
Every
tuesday
morning
I've
been
doing
it
for
about
two
years.
Now
nine
o'clock,
pacific.
A
Our
team
has
started
the
third
weekly
sprint
of
the
20.12
release
cycle.
This
is
our
december
release
and
we're
going
to
be
focusing
on
networking
improvements
and
consensus.
Protocol
security
features
hardening
performance
security.
All
these
are
important
things
we're
pretty
much
close
to
being
feature
complete.
Now
we
will
just
be
making
small
and
minor
modifications
and
enhancements
that
come
out
of
requests
from
our
custody
provider,
our
security
review
and
end
users
right.
So
now
we're
going
into
the
real
small
incremental
bits
tag.
A
V0.1.6
was
cut
on
wednesday
november
4th
and
it's
deployed
to
the
delta
test
net.
We
announced
the
launch
of
the
delta
test
net
yesterday
with
the
launch
of
the
clarity
block
explorer.
So
now
clarity
works
with
the
delta
test
net.
The
scala
system
has
been
deprecated.
It
is
now
end
of
life.
Those
of
you
that
are
running
scala
nodes
can
kill
your
scala
nodes,
hop
on
our
discord
and
we
can
walk
you
through
and
provide
some
support
on
getting
started
with
the
rust
node.
A
A
I
will
also
be
adding
delegation
and
undelegation
here
as
well,
because
it's
possible
to
participate
in
the
network
by
delegating
your
stakes.
So
if
you
want
to
participate
in
the
test
net,
but
you
don't
necessarily
want
to
bond
a
node,
you
can
also
participate
by
delegating.
So
we
encourage
folks
to
get
familiar
with
the
system
and
if
you
pass
kyc,
maybe
we
can
give
you
some
tokens
for
that.
A
So
let's
go
through
delta
test
net.
So
this
is
the
rust
network
code
name
delta.
We
launched
with
four
validators
I'll
do
a
demo
later
today
to
show
you
folks
how
many
nodes
we
have
running
in
the
network.
It's
pretty
cool.
We've
got
the
test
net
explorer
running
clarity.
I
can
go
through
that
again
go
through
that
this
afternoon
this
morning,
in
the
call
it
supports
era's
configurable
round
exponent
with
a
minimum
round
exponent
of
about
two
minutes,
so
the
network
can't
go
any
faster
than
two
minutes.
A
If
and
when,
when
we
bounce
delta,
we
will
provide
a
way
to
take
this
down
further
right.
So
I
would
like
to
see
a
minimum
of
about
15
seconds
or
16
seconds
that
should
be
the
fastest.
The
network
can
go
and
that
will
get
us
a
chance
to
actually
observe
this
in
action,
because,
right
now
it's
going
as
fast
as
it
can,
which
is
two
minutes
which
is
nice.
It
hasn't
slowed
down.
A
We
currently
have
50
validators
and
we
are
seeing
contention
for
validator
slots.
So
what's
happened
is
people
have
been
kicked
out
of
the
validators
set
thanks
to
the
auction
contract
because
they
were
outbid
by
someone
and
they
had
to
go
back
in
and
bid
some
more,
so
the
top
50
bids
will
be
part
of
the
next
era.
That's
the
way,
the
or
three
eras
in
the
future.
That's
the
way
the
auction
contract
works.
A
It
supports
bonding
and
bonding,
slashing
and
rewards.
There's
it's
pull-based
rewards.
We
eventually
want
to
move
this
to
push-based
rewards,
so
we'll
probably
do
a
little
bit
of
rework
in
that,
and
all
the
smart
contracting
features
are
in
place
there.
We
also
shipped
a
rust
clarity,
a
rust
client
to
facilitate
interacting
with
the.
A
Node
the
beta
test
net
phase
is
over.
I
will
also
be
reaching
out.
We
are
in
the
kyc
process
for
our
alpha
test
net
validators,
and
I
will
be
communicating
those
rewards
here
very
shortly
and
we'll
be
sending
an
email
this
week
to
all
of
our
beta
test
net
participants
to
start
them
on
the
kyc
process.
So
we
can
understand
who
is
eligible
to
receive
their
credits
at
mainnet,
launch
current
focus
for
highway,
we're
supporting
the
security
audit
we
are
undergoing.
We
kicked
off
our
security
audit
last
week.
A
It
started
on
monday
with
trail
of
bits.
They
will
be
looking
at
the
consensus
protocol
and
the
highway
paper
and
with
the
goal
of
the
audit,
is
to
one
check
for
the
security
of
the
protocol
number
one
in
the
paper
and
to
verify
that
our
implementation
matches
the
paper
closely.
So
we
can
expect
all
the
properties
of
the
paper
for
with
respect
to
security,
to
be
available
in
the
protocol.
A
A
Okay,
I
will
find
out
what
lmc
validate
and
for
endorsements
against
equivocations.
This
means
that
if
we
see
an
equivocation
on
the
network,
then
we
make
sure
that
the
endorsements
are
not
coming
from
equivocators
right.
So
that's
just
an
obvious
security
thing
and
we're
going
to
design
the
disconnect.
So
if
we
find
a
node
that
is
sending
invalid
messages,
we
will
basically
disconnect
them
from
the
network.
A
Additionally,
we
also
discovered
that
we
have
a
couple
of
validators
having
a
serious
liveness
fault
in
the
test
net.
So
what
we're
going
to
do
is
basically
they
bonded
into
the
auction,
took
a
slot
and
then
didn't
participate
in
consensus
right,
and
so
there
really
isn't
much
incentive
for
them
to
do
this
from
an
economics
perspective,
but
that
doesn't
mean
it's
still:
a
zero
cost
for
a
malicious
validator,
and
so
what
we're
going
to
do
is
we're
going
to
rotate
them
out
of
the
auction
contract.
A
A
Your
senior
ridge
rewards
will
be
zero
because
you
had
a
total
liveness
failure
and
then
the
auction
contract
will
simply
rotate
you
out
of
the
set,
and
so,
if
you
want
to
grab
another
slot,
you'll
have
to
re-bid
in
and
this
costs
money.
So
you
will
eventually
you
know
you.
If,
hopefully
this
will
be
enough
of
a
disincentive
for
people
to
do
this.
Otherwise
we
will
have
to
introduce
liveness
slashing
right
so
that,
if
you
don't
participate
at
all
in
a
complete
era,
then
we
will
slash
you
right.
A
A
We
are
dropping
in
the
lib
p2p
network
component,
so
we
did
an
initial
pass
on
that
last
sprint.
This
sprint.
We
will
continue
to
work
on
that
and
harden
that
frazier's
doing
that
work.
We're
also
doing
improvements
and
testing
so
we're
getting
the
reactor
tests
in
place.
Those
of
you
that
are
running
a
node.
A
You
see
that
the
joiner
reactor
it's
the
internal
architecture
of
the
node,
it's
basically
how
the
run
run
running
of
the
system
works,
so
lnc
is
limited,
naivety
criterion,
it's
how
the
additional
validity
criterion
are
named
for
highway
messages.
This
defends
against
fork
bombs.
So
this
is
the
additional
fork
bomb
spam
protection
that
we've
built
into
highway.
That's
what
lnc
means
limited
naivety,
criterion.
A
We're
adding
a
json
rpc
endpoint
that
returns
endpoint
documentation,
so
this
is
for
so
you
can
understand
what
the
node
rpc
is
right.
So
if
you
want
to
build
your
old
client,
so
you
want
to
build
a
go
client.
You
need
to
understand
how
the
node
communicates,
because
the
client
provides
that
node
communication
right
communication
from
the
client
to
the
node.
So
this
is
the
the
json
rpc
in
the
node
itself.
Right,
don't
rely
on
event
order
and
deploy
buffer
and
fix
block
handling,
so
we're
making
the
deploy
buffer
more
robust.
A
A
Testing
sre
we
had
another
sre
joined.
The
team
robert
jennings
joins
us
from
australia
from
the
great
land
down
under
he'll,
be
he
has
a
partner
there
in
ajit,
so
we've
got
two
guys
in
australia:
that'll
be
providing
support
for
the
network
during
a
pretty
big
dead
zone.
We
have
right
now,
which
is
around
the
time
when
asia
wakes
up
we're,
putting
clarity
under
continuous
integration,
continuous
deployment
we'll
go
through
the
new
clarity
for
rust
and
for
s-tests.
A
We
are
extending
workload,
generators
and
improving
monitoring,
so
we
can
do
more
deeper
and
enhanced
complex
test
tests
against
s-tests.
A
The
idea
is
that
we
could
eventually
spin
up
s-tests
against
you
know
they
don't
like
me
talking
about
this,
but
you
can
actually
push
test
s-tests
against
the
delta
test
net
right.
You
just
point
it
at
a
node,
ideally
clarity
and
signer
we're
launching
a
new
release.
That's
what
we
did
last
week
I'll
show
you
the
clarity
clarity.casperlabs.io
we'll
get
to
that
javascript
sdk!
We
did
this
for
our
custody
provider.
A
We
have
great
news
to
share
about
our
custody
provider.
They
require
a
javascript
sdk,
so
we
built
that
and
published
it
to
npm.
So
those
of
you
that
want
to
interact
with
the
network
using
a
website
a
web
interface
or
mobile
interface,
there
is
a
nice
sdk
on
npm
and,
of
course,
documentation.
Updates.
I've
been
doing
a
lot
of
the
doc
updates,
specifically
around
the
dap
developer,
guide,
the
erc20
tutorial
and
launching
our
new
developer
portal.
A
We're
designing
the
initial
gas
pricing
model
and
this
becomes
important
because
we
talked
a
lot
about
how
we're
pushing
you
know
how
we're
going
to
size
the
blocks
right.
So
in
our
consensus
protocol
we
do
execution
after
consensus
and
what
that
means
is
at
the
time
that
a
block
is
proposed.
A
The
node
simply
selects
the
deploys
and
stuffs
them
in
a
block.
It
hasn't
run
those
deploys.
So
we
really
can't
put
in
a
traditional
gas
maximum
gas
limit,
as
you
would
think
about
it
in
ethereum,
because
in
ethereum
the
node
runs,
the
deploys
gathers
up
all
the
execution
effects,
and
then
you
know
mines
and
nonce
shoves,
those
all
in
right.
Our
system
doesn't
do
that.
There
is
no
execution
until
you
get
a
block
once
you
get
a
block,
then
you
run
the
block.
A
All
the
nodes
kind
of
update
their
state
together
right,
the
block
gets
propagated
and
it
gets
upgraded.
Updated
deploys
are
gossiped
across
all
of
the
network.
So,
in
order
to
run
a
block,
you
have
to
have
all
the
deploys
in
your
deploy
buffer
and
then
you
will
grab
those
deploys
and
run
them.
Based
on
the
block
that
you
just
received.
If
you're
the
leader,
you
decide
which
deploys
go
into
the
block
and
then
you
gossip,
the
protoblock
consensus,
runs
on
the
protoblock.
C
Right,
but
it's
important
to
point
out
here
is
there
is
still
going
to
be
a
limit,
just
the
difference
between
ethereum,
and
this
is
that
you
know
obviously
in
ethereum
you
can
pack,
you
know
the
block
up
to
the
limit,
whereas
in
our
case
it
will
be,
you
know.
Basically
you
will.
C
You
know
up
to
the
limit.
You
will
allocate
gas
two
people
in
that
block
right,
but
they
may
not
use
all
of
the
gas
right
so,
especially
at
the
beginning.
We
will
expect
that
blocks
will
typically
be
under
filled,
and
you
know
as
time
progresses
and
people
get
better
at
estimating
their
gas
needs
and
you
know
improves.
We
will,
you
know,
come
closer
and
closer
to
actually
achieving
you
know
like
the
actual
glock
lift
and
then
later
on.
A
Yep
exactly
ideally,
you
would
want
the
validators
to
be
able
to
do
it
right,
so
they
would
be
able
to
because
they
have
a
desire
to
shove
as
many
transactions
as
possible
into
the
block.
So
they
should.
We
would
want
to
empower
the
validators
to
do
that,
so
it's
not
a
hard
fork
or
anything
like
that.
Contract.
Runtime,
add
a
memo
destination
field
to
transfer.
This
is
coming
from
our
custody
provider
as
a
requirement.
Exchanges
really
need
this
memo
field
and
we
want
to
reduce
the
total
supply
on
slashing.
A
So,
let's
look
a
little
bit
at
clarity:
we'll
do
a
quick
product
demo,
so
we
have
the
casper
labs.
Clarity
looks
very
similar,
as
you
did
before.
We
didn't
do
a
huge
or
crazy
uplift.
There
shouldn't
be
a
graphql
console
yeah.
So
that's
a
bug
so
definitely
need
to
remove
the
graphql
console
I'll
file,
a
bug
for
that.
A
That
needs
to
be
fixed.
So
we
can
look
at.
We
have
a
faucet
here
so
same
as
before
you
can
go
ahead
and
fund
your
accounts,
I'm
not
completely
certain
that
the
old
keys
work
I
need
to
go
find
out.
If
it
does,
you
can
definitely
deploy
a
contract
from
the
browser,
so
you
can
either
you
can
upload
wasm.
If
you
want
to
upload
wasm,
you
can
call
it
by
name,
you
can
do
it
entry
point
of
the
contract
and
then
you
can
sign
it.
B
The
old
key
worked
for
me
yesterday,
but
but
again
I'm
not
100
sure.
A
A
Yeah
I've
tried
to
do
the
the
deploy
with
a
hash
and
it
hasn't
worked
for
me,
but
I'm
not
sure
if
my
arguments
were
incorrect,
you
can
also
view
blocks
now.
The
blocks
look
a
little
different.
We
do
not
show
the
internal
protocol
state,
so
it
used
to
be
that
you'd
be
able
to
see
all
of
the
really
cool.
A
You
know
ballots
and
attestations
here.
We
don't
see
that
here
you
see
just
the
era
id
and
the
block
hash
and
the
proposer.
The
nice
thing
is,
is
those
of
you
that
are
running
validating
nodes.
You
can
actually
see
if
your
node
proposed
a
block
right,
so
it's
possible
to
identify.
Did
my
node
propose
a
block,
you
know?
Is
it
participating
in
consensus?
I
wonder
what
happens
if
I
click
on
this?
A
Absolutely
nothing.
So
I
think
that
this
link
should
go
away
because
it
doesn't
do
anything
if
you
know
what
a
deploy
is
or
the
account
hash.
This
is
not
an
account
hash
is
it.
I
don't
think
it
is.
I
don't
think
I've
got
any
deploys
here.
A
A
Second,
I
have
to
scroll
through
some
stuff
here.
Execution
results.
Sorry,
so
you
guys
can
see
what
I'm
doing.
While
I
try
to
do
this,
I'm
over
here
in
my
terminal-
and
this
is
all
the
serialized
binary
for
the
contents
of
a
deploy-
it's
rather
boring,
so
I'm
not
going
to
you
know,
bore
you
with
that
by
scrolling
through
it.
So
let's
just
look
here
if
I
can
get
a
deploy
hash
here,.
A
A
This
is
a
if
I
recall
correctly.
This
is
a
bonding
request.
A
This
is
a
request
to
add
a
new
bid
to
the
network.
So
here
you
can
see
here.
This
identity
is
a
great
way
to
know
that
there's
an
identity
action
here,
there's
a
cost.
This
is
approximately
the
number
of
moats
it
costs
to
bond,
which
is
about
half
a
cent
to
do
a
bonding
request.
So
it's
not
a
lot
of
money
to
send
in
a
bid.
A
A
He
goes
by
dan
halford
on
discord
built
a
nice
little
host
dos
sh.
It
basically
pulls
in
all
of
the
host.
It
goes
through
every
single
ip
address
it
finds
and
then
it
pings
each
of
those
ip
addresses,
gets
the
block
height
for
each
and
here
you'll
find
that
there's
someone
that
is
useless
is
forked.
A
A
A
A
A
C
Yes,
yes
I'll.
C
Share
the
screen:
okay,
I
assume
you
can
see
it
right,
so
I
created
some
schematics
mostly
to
accompany
medes
existing
documentation
for
interacting
this
auction
contract
right
so
because,
while
conception
is
fairly
simple,
there
are
a
few
subtleties
about
how
the
single
place
right.
So
first
we
start
with
auction
entry
right
and
the
nodes
at
time.
You
know
flows
from
left
to
right
here.
Right
and
you
can
take
k
to
b,
is
a
distance
between
an
auction
and
when
the
results
from
that
option
are
actually
applicable
right.
C
So
when
the
new
validators
are
rotated
into
the
validator
set
right,
so
we
are
starting
at
some
error
n.
You
know
you
can
see.
There
are
free
existing
validators.
You
know
the
in
the
list
of
bidders.
We
have,
of
course,
the
same
validators,
because
also
these
are
just
standard
bids
and
the
two
potential
entrants
at
the
bottom
b1
and
b2
right,
so
the
one
being
just
under
the
last
validator
by
right.
So
what
happens
in
the
next
era?
C
Well,
the
next
era
is
the
one
where
the
option,
of
course,
is
going
to
run
for
the
era.
You
know
n
plus
k
plus
one,
but
something
new
happens
here
right.
He
leaves
a
steady
state
over
there
and
behind
something
new
happens
in
this
area,
and
what
happens
is
that
first
of
all,
b1
adds
20
to
his
bid
moving
him
up
above
v3
and
also
b3
enters
there's
a
bit
of
91.
C
So
we
have
two
of
the
existing
validators
from
previous
areas
displaced
in
the
bidder
list,
they're
still
validators
for
this
era,
but
then
you
know
the
option
runs
and
it
takes
the
top
three
right
from
the
bidders.
C
So
then,
in
the
applicable
era,
you
know
key
periods
later
you
can
see
that
the
value
you
know
the
list
of
three
new
validators
right,
v1
and
then
b1
and
b3,
and
that's
a
list
of
bidders
which
has
now
increased
because
you
know
so
there
are
a
couple
old
validators
trailing
there
behind
the
new
upstarts
right.
So
this
is
just
basically
that
that
you
know
that's
the
basic
mode
of
option
entry.
Then
there's
a
diagrams.
C
That
explains
how
delegation
works
right,
and
while
this
is
currently
not
implemented,
we
will
be
implementing
that
there's
going
to
be
platform
parameters
that
specifies
allowed
ratio
delegation
right.
So,
for
example,
here
these
diagrams
allow
the
ratio
is
150
percent,
which
means
that,
for
example,
if
you,
you
know
bid
100
tokens,
delegators
can
contribute
up
to
50..
C
Now
what
happens
is
that?
If
then,
you
know
you
decrease
by
the
way
nobody
is
allowed
to
delegate
anymore
after
that,
and
if
you
decrease,
you
know
your
own
bid,
your
weight
for
purposes
or
the
auction
is
capped
right.
So
we're
about
to
see
houses.
What
actually
happens
where,
in
era
n
we
have
this
example.
C
Validator
is
weight,
100
he's
contributing
70
of
his
own
weight
and
he
has
two
delegators
one
contributing
20
and
the
other
right
and
the
as
a
whole.
They
account
for
this
100.
That's
how
they're
weighted
in
the
auction
and
that's
how
they're
waiting
for
the
purposes.
B
And
alex
just
to
confirm
the
max
that
he
can
take
is
35.
Right
cannot
take
more
than
35
as
delicate
delegators.
C
Well,
he's
all
right
right,
yeah,
yeah,
exactly
right,
so,
like
there's
a
let's
say
advised
maximum
here
would
be,
you
know,
105.,
so
he's
almost
there
yeah
right.
So,
let's
see
right
so
what
happens
in
the
next
era?
C
Well,
what
kind
of
next
era
is
that,
first
of
all,
he
receives
a
new
delegation
of
so
the
the
d2
adds
another
ten
tokens
right
which,
by
the
way,
would
have
led
to
a
weight
cap
in
this
show
just
pointed
out,
then
we
have
a
new
delegator
enter
here.
So
by
the
way,
this
actually
suggests
that
I
should
let's
see
so.
C
Actually
I
have
to
change
the
numbers
in
the
example
slightly
because
right
now
they
are
kind
of
violating
the
no
more
delegation
rule
right,
but
that
it's
otherwise
the
logic
is
fine
right.
So
they
add
you
know.
So
he
has
this
added
delegation
from
d2.
We
have
a
new
delegator,
you
know
in
d3,
and
then
this
guy
also
decreases
his
bid.
C
His
actual
validator
decreases
his
bid
by
20,
so
now
he's
going
to
be
at
50,
which
means
that
the
limit
for
him
would
be
75,
total
right.
So
and
of
course,
he
is
currently
way
above
that,
so,
while
the
nominal
weight
after
all
of
these
manipulations,
is
actually
100,
the
functional
weight
for
the
purpose
of
the
option
and
the
reward
distribution
is
now
75
right,
and
you
know
you
can
observe
this
right.
So
then,
in
the
era
you
know
so
then
the
auction
runs,
of
course.
C
In
this
era,
for
era,
n
plus
k
e
plus
one-
and
you
know
the
end
result-
is
this
right
so
well
he's
sitting
as
a
validator
in
error,
n
plus
k,
plus
one
his
effective
weight
is
75.
You
know,
and
you
can
see
the
nominal
breakdown
here
and
notes.
That,
of
course,
is
this
kind
of
thing
you
know
I
mean
we
are
assuming
here.
Is
that,
of
course,
he
still
remained.
C
You
know
remained
in
the
validator
set
right
that
he
actually
wants
the
auction.
C
Well,
in
this
case,
slasher
works
fairly
simple,
I
mean
so
basically,
let's
say
is
that
so
so
he's
validating
all
these
errors
if
he
were
slashed
or
it
was
found
out
that
he
equivocated
an
era
n
plus
one.
You
know.
Let's
say
this
was
found
out
in
era
n
plus
two
then
what's
going
to
happen
is
that
we
are
slashing
leaders,
so
we
are
taking
his
bid,
which
is
already
locked
up.
C
We
are
taking
all
his
delegators
contributions
and
for
anyone
who's
currently
active
in
the
auction
contract.
That's
basically
it,
however,
or
you
know,
on
top
of
that
anything
that
we
can.
You
know
we
can
reclaim
still
will
also
be
slashed
right.
So
if
he
withdrew
some
tokens
and
they're
still
being
held
for
the
you
know
waiting
period,
so
those
are
going
to
be
slashed
and
any
delegators
who
withdrew
who
were
contributing
to
his
weight
in
the
air
where
he
equivocated
those
are
also
going
to
be
slashed.
C
C
Yeah
so,
and
let's
see
what
what
else
was
going
to
say
about
about
slash
and
well,
I
guess
that's
it
for
now
I'll
I'll
think
if
it's
war
file
maybe
add
in
a
diagram
for
it,
but
I
think
the
verbal
description
may
be
sufficient
because,
again,
basically
you
know
if
we
knew
that
your
weight
was.
You
know
present.
C
You
know
at
the
time
when
you
know
you
equivocated
right,
so
either
you
as
a
validator
right.
You
know
your
weight.
Was
you
know
you
equivocated
or
you
were
a
delegator
who
was
in
that
era
associated
with
you?
C
If
we
can
find
those
tokens
we're
slashing
basically
right
so
if
they're
still
in
the
bid
associated,
you
know
with
that
validator
or
you
know,
if
reserve
is
drawn
there,
there
is
some
subtlety
about
this
drone
delegator
tokens
that
will
have
to
work
out
when
we
actually
go
and
implement
this
right
because
you
may
need
to
differentiate
by
you
know
which
delegator
was
you
know
where
the
tokens
was
drawn
from
right
so
because
then
you're
avoiding
the
situation
where,
for
example,
you
have
delegated
to
five
validators,
then
you
withdrew
from
like
all
of
them,
and
you
know
we
have
all
of
these.
C
You
know
abundant
purses
floating
around,
and
then
you
know
one
of
those
validators
you
know
turns
out
to
have
equivocated
right,
so
we
would
prefer.
A
C
C
So
the
the
this
was
it
for
delegation
and
the
digression
into
slashing
and
then
there's
a
matter
of
distribution
right,
so
distribution
of
rewards
or
specifically
senior
rewards
and
the
similar
example
to
the
above
right
I
mean
so
now
our
example.
Validator
is
validator
two
of
two
on
the
bottom
here
right.
You
know
that
that
start.
Both
these
guys
have
you
know
same
total
weight
right.
So
then
the
same
manipulation
is
above
the
current
error
and
plus
one.
So
now,
of
course,
one
of
two
nothing
happened
to
him.
C
He
still
has
his
way
to
100
and
because
of
the
captain,
two
of
two
now
has
a
functional
weight
of
only
75
right.
So
then
we
fast
forward
so
now
here
in
this
era,
membership
was
validator
set
for
n
plus
k,
plus
one
is
determined
and
we
are
jumping
not
to
the
error,
n
plus
k
plus
one,
but
to
error,
n
plus
k
plus
two
right,
so
they
have
been
selected
for
that
validator
set
with
their.
You
know,
updated
weights.
C
They
did
all
the
work
that
was
required
with
perfect
liveness
and
then
well.
What
happens
right?
Well,
let's
say
proof
of
stake.
Contract
is
now
supposed
to
distribute
100
tokens,
and
you
know
these
are
the
only
two
guys
who
are
active
right.
So
a
hundred
tokens
are
minted
now
because
you
know,
based
on
their
fun
functionally
active
weight.
One
of
two
gets
57
and
the
two
of
two
gets
43.
C
note
that
if
you
know
if
there
were
no
changes
in
delegation
from
error,
one
both
would
have
received
the
50
right.
But
of
course
now
you
know
because
the
changes
ineffective
weight,
one
of
two
gets
more
now
what
happens
to
the
distribution
of
the
stuff
among
the
delegators?
C
Well,
the
thing
is
that,
like
the
ways
that
I
envisioned
this
and
know
that
this
is
not
yet
implemented,
is
that
while
capping
affects
your
effective
weight
right,
so
your
weight
as
a
unit,
you
know
this,
you
know
a
glob
of
both.
You
know
validator
and
delegators.
You
know
in
options
and
distribution
once
it
actually
comes
time
to
you
know,
determine
who
gets
what
you
know
internally
from
the
you
know,
rewards
that
the
validator
received
all
the
weights
count.
C
You
know
a
nominal
amount
right.
So
now,
suddenly
is
it's
like
a
it's
further
disincentive
to
reducing.
You
know
your
bid
to
the
point
where
you
actually
get
capped.
C
Right
so
in
here
it's
just
you
know,
this
distribution
is
simply
proportional
to
you
know
proportional
to
the
weights
of
the
delegators
and
own
weight.
There's
one
improvement
actually
to
this
diagram
is
that
I
should
add,
which
is
right
now
it
doesn't
display
the
validator
taking
his
cut,
and
she
normally
would
so
essentially
here
it
assumes
that
the
validator
is
taking
a
cut
of
zero.
C
But
yes,
so
these
are.
These
are
the
diagrams
for
now.
C
A
A
C
From
the
rewards,
as
that
you
know,
would
go
to
the
delegators
right,
so
you
know
it's
it's.
There
is
their
payment
for
assuming
the.
B
C
But
yes,
are
there
any
other
questions
about
these,
and
these
will
probably
appear
in
our
online
documentation
once
we
figure
out
how
to.
B
C
B
C
Before
we
put
it
in
the
docs
since
yeah
this
yeah
the
cloud
ratio
stuff
right
now,
there
is
no
allowed
ratio.
You
can
delegate
up
to
the
jails.
There
are
no
limits
at
all,
so.
A
A
A
Terrific,
that's
it
for
today,
folks,
we
are
40
minutes
in
so
I
think
this
call
has
been
meaty
enough.
I'll
talk
to
you
next
week
and
again,
don't
hesitate
to
ask
me
anything:
cheers
bye.