►
From YouTube: Eth2.0 Implementers Call #17 [2019/5/2]
Description
A
A
B
Now,
big,
that's
fair,
I!
Suppose
the
zero
point,
six
point:
one
is
interesting:
we
have
been
dabbling
if
the
ID
or
we
can
unify
some
of
the
testing
between
the
PI
tests,
tested
tests
back
and
a
test
that
infinite
are
the
test,
generators
factors
for
their
clients,
and
so
it's
like
the
cone
part
here.
It's
the
this
setup
part
very
set
up
an
edge
guys,
and
this
edge
case
is
applicable
to
both
to
both
types
of
test.
A
C
B
A
A
A
E
New
plan
for
the
next
six
months
is
regarding
a
freedom
2.0.
So
so,
if
you
want
to
know
who
is
working
on
what,
within
the
team
you
can,
you
will
be
able
to
check
out
this
like
next
week
also,
otherwise,
regarding
updates
on
the
core
spec,
we
started
to
implement
a
0.6.
We
have
state
transition,
changes
partially
done
or
current
focus
is
ins
get
become
proposal
index.
That
was
a
reward
significantly
in
0.6
and
it's
a
broker
for
us
for
several
things
like
for
choice,
testing
tests
and
stake,
pulling
something
to
optimize.
E
Everything
related
to
to
state
another
issues
is
that
we
met
with.
We
found
some
under
flows.
We
epic
and
we're
interested
in
to
what
other
users
of
subtly
compiled
language
with
unsigned
int
like
do.
We
also
make
the
same
changes
upon
issues
because
in
Python,
since
it's
always
signed
integers,
maybe
that's
hidden
yeah
and
they
it
was.
We
have
a
PR,
although
we're
still
figuring
out
the
best
way
to
do
this
for
handling
the
particular
under
flows
and
also
potentially
overriding
some
of
the
integer.
A
E
On
how
to
update
the
library
and,
for
example,
hello,
how
to
read
fields
without
this
relation
everything
which
is
like
the
big
upsell
of
SOS,
so
that's
it
for
core
and
now
regarding
networking,
we
had
did
NAT
traversal
to
become
a
beacon
change
simulator.
So
now
we
don't.
We
have
much
better
connectivity,
even
if
everyone
is
behind
waters
and
the
test
net
was
not
working
on
Windows
due
to
not
traversal.
We
had
some
windows
socket
issue
and
this
is
fixed.
E
A
F
So
we're
up
to
0.06
and
just
kind
of
waiting
to
see
what
the
tests
say
at
the
end
of
it
and
we
just
actually
merged
in
flood
sub,
no
flood
sub
and
we're
gonna
be
using
that
kind
of
as
like
a
test
ground
as
well
as
we've
got
so
we're
gonna.
Do
that
hobbits
and
basically
yeah
Oh
point
six.
We're
kind
of
seeing
what's
gonna
happen
with
test
suite.
F
F
We've
started
to
kind
of
separate
out
the
validator
from
that
will
be
contained
kind
of
how
they
a
little
thanks
or
using
the
RPC
kind
of
like
roughly
implementing
from
what
Luke's
proposed.
Our
BC
methods
are
for
the
validated
communication
we've
implemented
on
me,
ghost-like
kind
of
reoptimize
it
from
proto's
I'll
go
and.
F
I
I
It's
whatever
the
function
to
validates
the
Merkel
branch
right
from
the
deposits
and
so
yeah
part
of
a
part
of
in
doing
that.
We've
generated
some
test
data
from
the
deposit
contracts
and
we'll
be
sharing
that
shortly.
I
think
and
organizing
and
planning
this
workshop,
but
mostly
just
troubleshooting
or
zero
point,
five
point:
one
branch
and
that's
it
any
questions,
nope
great.
Thank
you
about
harmony,.
I
J
J
K
The
be
0.6
updates,
our
tester
will
probably
go
live
with
around
be
0.4
with
some
some
bug
fixes
from
latest
releases
and
yeah.
Let's
mostly
what
we've
been
up
to
recently,
just
fixing
that
up
we
optimized
we
removed
all
the
like
event
square
blow-ups
in
the
spec
and
like
epub
processing,
so
we
managed
to
optimize
some
stuff
by
like
400
X,
it's
pretty
nice,
so
yeah
I
start
from
that.
Just
cleaning
things
up
and
getting
things
ready.
C
C
L
A
G
Sniffing
telegram
and
you
can
go
for
it's
a
repay
stat
in
the
same
place,
yeah
so
I
guess
I,
just
I
kind
of
do
other
the
present
presentation
about
it.
The
basic
idea
is
that
this
is
meant
to
be
a
proposal
for
kind
of
the
core
of
how
faced
you
were,
so
the
state
execution
would
work
and
it's
Tiki
and
it's
specifically
taking
the
direction
of
having
a
relatively
minimal
and,
if
consensus,
away
or
execution
system.
So
it's
not
quite
as
minimal
as
the
proposal
that
Casey
made
a
new
research
a
couple
of
weeks
ago.
G
So
this
proposal
does
have
execute
happening
in
different
charts,
does
have
state
routes
for
different
charts
and
it
does
have
some
amount
of
state
storage
for
different
charts.
But
the
consensus
way,
your
stuff
is
deliberately
extremely
available.
It's
only
a
couple
of
hundred
lines
of
high
spec
and
the
idea
is
that
everything
else
that
you
would
expect
to
get
built
on
top
would
instead
be
built
here,
saying
a
kind
of
layer,
2
framework,
that's
designed
inside
of
this
relatively
minimal
base
layer.
G
So
kids
said,
then
consensus
layer
will
only
recognize
contracts
as
I'm
existing
on
the
beach
in
chains,
so
there
will
be
verified
and
stored
by
everyone,
and
these
contracts
can
hold
each
and
they
also
have
functions
that
you
can
call,
and
if
and
in
this
frame
a
proposal
ether
as
they
had
a
base
way.
Your
thing
can
only
exist
on
the
PGA,
Tour
and
so
ether
is
either
held
by
a
validator
or
it's
being
held
by
a
freaking.
G
While
so,
you
can
have
there's
a
few
new
beacon
chain
operations
that
I
introduced,
but
the
basic
idea
is
that
one
of
them
is
creating
a
new
freedom
pylon.
The
other
two
are
transferring
eath
from
a
validator
to
a
pre
compile
and
from
a
premium
aisle
to
a
validator.
Now
the
there
is,
even
though
the
contracts
kind
of
are
stored
and
live
on
the
beach
educate.
G
So
basically
the
transaction
just
specifies
kind
of
what
what
the
stage
transition
function
is
that
it's
paying
attention
to
the
the
the
code
has
act,
has
access
to
a.m.
or
in
function
interface
and
which
gives
ed
the
ability
to
read
and
write
from
a
particular
region
of
state
in
the
shard
and
issue
receipts
and
to
execute.
G
You
would
basically
arbitrary
code
that
you
provide
to
it
so
like,
even
though
contracts
don't
exist
inside
of
shards
as
a
base
level
concept,
you
can
still
make
contracts
exist
as
a
higher
level
concept
by
just
setting
up
a
precompile
of
that
under
certain
conditions
like
loads
code
from
this
and
then
execute
the
code
using
some
other
data
provided
as
input.
So.
G
G
So
that's
the
for
the
first
section
and
the
second
section,
the
third
section,
so
this
is
implementing
in
shard
each
transfers
and
the
fourth
section
dealing
with
expiry
both
have
to
do
with
basically
giving
an
example
of
what
it
would
actually
look
like
to
implement
a
an
employer
to
thing
that
does
something
useful
on
top
of.
This
is
a
framework
right,
so
the
the
scheme
that
that
there
is
third
section
basically
defines
three
functions,
so
one
of
them
is
a
depositing
ease
into
the
system.
G
If
you
own,
Eve
inside
of
the
system,
then
the
way
that
it
would,
what
it
looks
like
at
consensus
layer
is
that
when
you're
depositing
is,
you
are
both
transferring
East
from
your
validator
into
the
pre-compile,
but
also
issuing
a
receipt,
and
then
you
can
send
a
transaction
in
a
shard
which
claims
that
receipt
and
the
inside
of
a
shard
saves
a
record
that
says
that
some
of
that
eats
that
your
transfer
that
e
that
you
just
transferred
into
the
pre-compile
I'm.
Actually,
it
does
belong
to
you
and
then
in
send.
G
If
to
other
people,
you
would
just
be
tray
extending
transactions
that
call
the
transfer
function.
You
would
be
transferring
these
records
ownership,
adjusting
balances
and
then
to
withdraw.
You
would
first
call
the
withdraw
function
using
a
transaction
inside
of
a
shard,
and
then
that
would
generate
iterator
receipt
and
then
on
the
beacon
chain
level.
You
would
call
the
you
validator
function,
which
would
consume
a
merkel
proof
of
a
receipt
of
the
receipt
that
you
generated
inside
of
a
shard
and
it
would
withdraw
it
from
the
pre
compile
into
a
evaluative
slot.
G
For
you
and
like
this
framework
is
really
or
that
particular,
and
the
second
layer
system
is
deliberately
really
simple
like
all
it
does.
Is
it
just
lets
you
move
heath
around,
but
you
described
but
get
the
very
bottom
in
the
fifth
section
how
to
like,
but
basically
what
you
would
have
to
do
it.
You
extend
that
into
a
scheme
where
you
can
just
implement
an
entire
sport
contract
system
on
top
of
it
and
then
in
the
sections
below
that
I
talked
about
like
how
you
enable
Metamarkets.
G
N
G
Using
sort
of
minimal
b.I
consensus
layer
and
put
ends
up,
pushing
more
things
to
higher
higher
layers
and
there's
definitely
a
big
design,
space
of
and
trade-offs
to
a
finer
grain
trade-offs
that
we
can
make
in
terms
of
these
that
are
faced
way
or
protocols
and
I
expect
the
layer
two
schemes
to
just
keep
on
improving
over
time.
In
the
same
way
that
say,
plasmas
improve
over
its
final.
G
So,
just
to
put
this
little
of
our
context,
these
contracts
that
exist
on
the
beacon
chain
generally
can
be
thought
of
kind
of
like
execution,
environments,
yeah
and
so
by
by
deferring
it
to
these
execution
environments
that
can
be
built
and
upgraded
over
time.
We've
like
become
less
opinionated
on
layer.
One
yes,.
A
N
You
know
the
process
of
fine
combing
is
is
also
for
finding
these.
These
final
bugs
one
of
the
you
know
things
that
might
be
possible
when
we
do
is
tech.
Freeze
thanks
to
all
these
simplifications,
both
you
know,
cosmetic
and
substantive,
is
that
we
might
be
able
to
fit
the
state
transition
function
of
phase
zero
in
in
five
hundred
twelve
lines
of
code.
So
proto
show
how
to
do
it
in
in
the
thousand
twenty
four
few
months
ago,
and
we
would
definitely
simplified
it
a
lot
since
then.
N
So
one
thing
that
that
we're
doing
a
lot
of
progress
on
kind
of
a
parallel
effort
is
a
bi
destination,
so
I'd
say
we're
very
much
on
track
for
Standardization
to
be
completed
by
q2
by
q3
and
in
q2.
You
have
very
good
visibility
as
to
what
the
final
design
will
be
and,
generally
speaking,
things
are
lining
up
very
very
nicely.
N
In
terms
of
to
dues
that
I
want
to
get
done,
you
know
before
the
spec
freeze,
one
is
the
focus
rule.
You
know
it
still
needs
some
love,
there's
a
few
edge
cases
that
I've
known
and
it
needs
to
be
made
executable
and
I'm,
also
working
on
the
static
state
and
Barents,
which
will
be
nice
in
the
context
of
first
testing.
N
O
A
There's
really
a
lot
of
updates
to
share
with
you
guys.
So,
first
of
all,
we
have
worked
on
the
gossip
service
and
Kronus
validators.
This
is
something
this
is
a
feature
that
many
of
you
asked
for
it
we've
implemented
recently
and
going
to
be.
The
PRS
interpret
here
right
now
and
put
the
public
this
off
to
the
demon
in
the
next
few
weeks
so
be
available.
There
we
recently
merged.
P
A
P
1.3
spec,
as
well
as
the
reference
implementation
and
go
we've
introduced
an
experimental
flag
in
ipfs
which
we'll
be
using
to
roll
this
feature
out
slowly
in
the
public
net,
where
it
can
conduct
canary
tests.
Essentially,
we've
hired
a
security
firm
tour
that
let
me
to
be
their
auditing
most
of
live
interview
with
the
exception
or
second,
which
will
be
facing
out
and
basically
discouraging
in
favor
of
TLS
1.3.
Once
the
experiment
is
successful.
P
P
We
also
have
a
dedicated
engineer
now
getting
our
specs
cleaned
up
finally,
and
writing
specs
for
for
unspecified
area,
so
we're
putting
together
an
impact
plan
and
we'll
be
publishing
this
as
soon
as
I
saw
it
so
basically
expect
kinda
like
a
rough
schedule
of
the
specs
that
we
plan
to
address
and
when
they'll
be
available
over
the
next
weeks.
We've
also
made
progress
with
our
test
lab,
which
is
a
tool
that
we
crafted
to
Tesla
p2p
at
scale.
P
The
next
logical
step
here
is
the
network
simulation,
which
is
something
that
we
miss
a
still,
and
there
are
really
several
actors
in
the
decentralized
space
that
are
in
need
of
a
common
low-level
API
that
can
be
used
programmatically
to
basically
configure
virtual
lakes,
link
them
and
said
Lisa
latency
is
packet,
loss
did
jitter
and
other
network
conditions
such
that
orchestrators
test
hole.
Constraints
can
then
use
this
API
programmatically
to
configure
different
test
scenarios.
P
Basically,
JUnit
tests
distributed
systems
under
a
variety
of
network
conditions
and
personally
I
would
like
to
have
seen
several
actors
wanting
this
and
we're
kind
of
like
going
our
own
different
directions
and
I'd
like
to
create
an
open
interest
in
the
community
to
start
building,
basically
a
common
asset,
a
common
standard
API
for
this,
because,
as
we
get
more
and
more
sophisticated
with
testing
these
systems
at
scale,
it
is
definitely
something
that
many
of
us
couldn't.
So
if
you
want
to
participate
in
this,
then
get
in
touch
with
me.
P
P
One
thing
that
I've
done
is
they've
created
a
web
RTC
direct
transport
which
basically
enables
communication
between
the
browser
and
the
backend
directly
without
their
without
the
need
of
signalling
servers.
So
this
is
great
kudos
to
them
for
taking
the
lead
on
that
and
an
aspect
that
we
started
to
discuss
a
little
bit
as
decentralized
what
decentralized
signaling
in
US
interests,
unlike
fashion
for
hole
punching,
would
look
like.
P
So
if
you
have
any
thoughts
about
this
reach
out-
and
we
could
discuss
this
and
last
but
not
least,
I
wanted
to
put
the
the
upcoming
ipfs
cam
up
on
your
radar.
This
is
basically
afford
a
hacker
retreat.
That's
gonna
be
taking
place
in
beautiful
Barcelona
at
the
end
of
June,
so
this
between
the
27th
and
the
30th
of
June,
there's
gonna
be
a
dedicated
course
for
literally
to
be
hackers
that
basically
covers
from
A
to
Z,
to
Z
of
limited
me
as
well
as
a
lot
of
insightful
workshops
and
discussions.
P
Challenges,
chrome
features
in
peer-to-peer
networking
that
that
we
already
so,
if
you'd
like
to
join
biggie
and
we'll
get
an
application
going
for
that
and
I'll
also
be
reaching
out
to
the
field.
To
a
few
of
you,
I
am
by
a
law.
Basically
those
who
lose
even
address
I
have
that's.
That's
all
for
me.
Any
questions.
P
P
P
P
D
P
Sure
what
the
difference
is
right
now,
but
I
can
still
come
back.
Okay,
cool
yeah
that'd
be
great
Thanks
and
related
to
battles.
You
consider
it
also
using
GRP
ship.
It
has
been
some
implementation
from
the
browser
about
starting
to
get
out
so
the
problem
with
gr
PCN.
We
considered
this
in
the
context
of
another
project,
which
is
that
network
visualizer,
the
nipi
to
be
network
visualizer
that
we're
working
on
is
that
it
is
not
possible
to
access.
P
P
So
the
question
so
Greg
has
a
question
on
the
chat.
What
is
the
issue
between
the
browser
and
the
browser?
So
the
issue
is
that
a
browser
cannot
openly
accept
connections
directly
unless
it's
with
the
signaling
server.
So
when
you're
speaking
with
a
back-end
directly,
that
is
not
a
browser
that
is
able
to
accept
incoming
connections
without
without
needing
a
signaling
server.
Then
the
web
part
is
the
kinda,
like
the
signaling
part
of
the
WebRTC
stack.
That
comes
their
benefits
for
you.
So
that's
where
the
web
RTC
direct
transport
comes
in.
P
P
P
D
P
Cool
the
next
thing
on
the
agenda
is
relevance
looking
to
be
I
know
that
there's
a
couple
of
teams
who
are
interested
in
figuring
out
as
they
begin
to
work
on
discovery,
five,
how
to
fit
it
into
the
context
of
bleep.
You
I
know
Felix,
isn't
here,
but
I
wanted
to
hear
your
thoughts
on
that
role
and
there
might
be
a
conversation
going
on
in
a
different
Channel
and
Wilson.
H
A
I'm
sorry
to
be
calling
me
I,
don't
have
any
so
I'm
just
getting
up
to
speed
with
the
conversations
in
that
channel
I
was
unaware
of
that.
So
I
just
directly
respond,
I'm
I
started
to
respond
to
those
thoughts
there
and
I.
Just
I
think
we
can
keep
a
conversation
there
cool.
So
there's
an
ongoing
conversation
in
the
dev
GDP,
getter
I
believe
Elvis
yeah
I
think
it
would
be
great
if
maybe
Adrian,
who
has
sort.
P
A
P
M
A
A
Next
is
just
the
spec
discussion:
the
o61
is
almost
ready.
There's
a
couple
PRS
that
I
haven't
had
a
chance
to
look
at
this
morning
that
I'd
like
to
get
in
there.
It's
primarily
a
few
bug
fixes
and
a
couple
of
cosmetic
things.
There
are,
as
we
mentioned,
some
tests
released
or
o6o
on
the
new
testimony
go
and
we
will
have
those
output
four
six
one
as
well,
and
we're
looking
about
a
week
from
now
to
have
a
more
extensive
set
of
tests
for
o61
it's
few
days.
A
A
Yes,
there's
a
little
bit
of
a
refactor
on
community
compute
committee
and
get
across
think
many.
It's
actually
just
the
clinical
action
as
well
anyway,
thanks
for
getting
ready
that
simplifies
it
much
and
makes
it
more
general
and
usable
and
a
phase
one
context
that
we
needed.
You
can
take
a
look
at
that
PR.
A
A
F
F
Yeah
because
I
I
do
see
it
kind
of
important
if
we
start
I
think
we're
at
a
point
where
it's
good
to
start
asking.
You
know,
tooling,
teams
kind
of
you
know,
pain
points,
they've
had
or
they
have
currently
and
see.
If
we
can
try-
and
you
know
account
for
a
bunch
of
these
early
on
yeah
as
we're
approaching
spec
Freeza
I've
been
wanting
to
open
up
the
dialog
with
the
web.
Three
people,
the
block,
explores
the
anyone.
F
That's
really
consuming
directly,
these
guys
so
glad
to
see
that's
getting
steady,
yeah
yeah,
we're
gonna,
be
starting
just
for
anybody
that
needs
it.
Cuz
Preston
actually
brought
this
the
other
day.
Our
SSD
jess
is
like
ready
for
browser.
It
should
be
actually
but
we're
also
gonna
start
doing
like
kind
of
like
a
web.
Three.
A
Mean
one
thing:
I'm
not
sure
we
discussed
before
is
the
idea
to
have
different
slot
durations
for
the
beacon
chain
and
for
the
shards.
So
the
idea
here
is
that
maybe
we
can
increase
the
slot
duration
for
the
beacon
chains
to
something
like
eight
seconds
or
twelve
seconds,
and
that
will
have
several
benefits.
One
is
that
it
would.
It
would
make
the
beacon
chain,
you
know
more
robust
kind
of
as
this
central
piece
of
infrastructure.
N
N
Right
and
just
quick
comment
when
I
bring
this
up
at
people,
a
common
reaction
is
wouldn't
that
increase
the
time
to
finality
and
the
answer
is:
if
you
kept
everything
else
the
same
yes,
but
you
can
actually
you
could
just
have.
You
could
have
twice
if
you
have
places
long
slots
and
you
have
twice
as
long
twice
as
low
it's
blocked.
Isn't
it
including
twice
as
many
committees,
you
don't
change
the
time.
N
A
A
N
Smaller
stock
durations
on
the
shots,
so
you
know
we
doesn't
matter
so
much
if
the
shots
have
a
bit
more
forking,
you
know
we.
We
do
care
about
the
to
see
from
a
user
experience
standpoint,
so
we're
considering
bringing
the
the
duration
for
the
shots
down
to
three
seconds
and
in
that
way,
we'd
be
competing
with
the
more
centralized
approaches
like
lucky
us
and
the
the
swaps.
Sorry,
the
committee
sizes
on
the
shard,
so
the
actual
the
amount
of
people
that
have
to
sign
an
attest
suit.
N
Each
shard
block
is
actually
capped,
I
think
one
twenty
area
now,
rather
than
it
just
scaling
indefinitely
with
the
size
of
the
persistent
committee,
and
so
there's
a
little
bit
of
that
game
in
there
as
well,
for
being
able
to
have
smaller
slot
times.
Vitalik
is
your
proposal
on
the
trick
for
calculating
just
requiring
one
pairing,
as
that
published.
A
I'm
actually
still
not
not
sure
if
it's
published,
okay,
I,
don't
think
anyone
I,
don't
think
any
implementation
teams
they've
had
a
a
whack
that
it
might
be
good
to
have
somebody
trade
off
I
think
it
might
have
missed
that,
but
I
thought
I
would
write
up
a
doctor.
Then
just
forgot
to
do
it
so
I
guess.
Well,
let's
not
forget
to
do
it.
G
A
G
I
I
I
I
I
A
A
A
N
Including
Tim
berners-lee
and
Bill
Gates
and
reversed
and
sham
erm.
So
if
you
want
to
join,
please
email
me
and
on
may
17th
is
going
to
be
a
mini
btf
day.
So
the
reason
these
two
things
are
kind
of
together
is
because
the
math
behind
the
time
lock
puzzles,
is
basically
the
same
as
the
math
behind
VD
PDFs
and
as
part
of
the
vdf
R&D
we've
with
implemented.
N
Fpga
vdf
evaluator,
which
we
tested
on
the
tiny
puzzle,
and
so
this
time
a
puzzle
is
a
is
a
twenty-year-old
puzzle
and
that
was
designed
to
take
thirty
five
years
to
crack
and
the
FPGA
just
takes
two
months
to
crack
the
puzzle.
So
there's
some
exciting
stuff
that
will
be
kind
of
presented
on
on
May
15th
and
May
17th
at
MIT.
N
So
you
can
make
it
to
em
I,
see
em
a
15th,
make
it
to
New
York
for
the
workshop
and
make
it
back
say:
I
might
see
for
the
70
all
right,
then
you
raise
your
hand.
Yeah
I'm,
sorry
so
like
in
terms
like
a
SSC
like,
as
we
were
going
from
0.4
to
0.5
1
like
we
had
like
so
much
like
complexity,
just
like
SSC
and
the
tax
owed
slows
down
a
lot.
And
the
reason
is
that,
like
a
mostly.
A
Q
Q
A
Treated
the
same
right,
for
example,
when
you're
serializing
the
list
with
a
mix
on
the
mix
and
goes
at
the
front
and
when
you're
doing
the
hash
tree
root
of
the
list,
the
mixin
goes
at
the
end
of
it
yeah
it
just
made
it.
It
made
it
a
little
bit
more
complex
to
deal
with
in
the
previous,
which
is
once
it's
serialize
to
serialized
they're,
all
kind
of
the
same.
F
N
We
we
want
is
to
avoid
basically
have
pure
mirco
paths
to
two
leaves
in
in
the
block
data,
for
example,
and
the
reason
is
that
we're
looking
to
do
these
fancy
data
availability
proofs,
where
the
complexity
of
mixing
in
the
length
might
make
the
circuits
you
know
significantly
slower
or
unworkable.
So
by
having
these
fixed
size
things,
we
we
unlock
the
possibility
of
using
you
know
of
making
easier
proofs
for
SSD
objects.
The
other
thing
is
that
it
makes
it
just
makes
the
spec
cleaner
throughout.
N
So
I
mean
it's
a
minor
thing,
but
now,
when
you
want
to
initialize
the
beacon
state
or
initialize
any
kind
of
object
like
a
beacon
block,
you
just
initialize
it
with
default
values
and
the
type
which
for
vectors
will
basically
specify
the
length.
The
number
of
elements
just
fills
everything
with
zeros
and
it
turns
out
that
that's
that's,
basically
the
right
answer
every
time
pretty
much,
so
you
can
initialize
objects
for
free,
which
is
kind
of
nice,
and
it's
the
same
thing
that
go
does
so
in
a
way.