►
From YouTube: Eth2.0 Implementers Call #15 [2019/3/28]
Description
A
A
Cool
we
are
going
to
go
ahead
and
get
started.
We'll
start
with
testing
updates.
I'm
gonna,
give
a
brief
on
what
I've
been
up
to
and
fro
to
lamda
will
give
a
brief
on
what
he
stood
up
to
continuing
to
add
just
on
the
PI
tests
of
the
executable
spec
we've
been
as
we've
been,
adding
features
of
even
updating
every
been
modifying
and
fixing
bugs
I've
just
been
kind
of
adding
testing
that
passed
through
the
general
flows.
A
C
A
D
So
that
means
we
should
be
running
a
short-lived
private
single
client
test
that
in
the
next
couple
of
days,
which
is
pretty
cool,
we're
also
working
the
past
state
transition
vectors
and
we've
found
that
slow
tree
hashes
has
been
really
inhibiting
us
from
operating
smoothly.
So
for
a
couple
of
days
into
a
case
tree
implementation,
and
we
should
have
something
in
the
coming
couple
of
days.
It's
pretty
close
and
finally
we're
looking
to
swap
from
GPL
two
to
Apache
yeah
for
us
great.
E
Second
finds
him:
we've
also
had
a
pretty
big
week.
We
were
about
to
PRN
like
our
first
kind
of
rough
plumbing
about
a
to
client
and
we're
really
close
to
being
able
to
actually
just
kind
of
spin
up
what
we
hope
would
be
a
similar
to
like
a
single
client
situation,
processing
blocks
and
whatnot,
and
then
we're
gonna
move
to
try
and
get
that
spun
up
and
multiple
load
cycle
lines,
but
other
than
that.
Pretty
much
we're
at.
F
F
Artemis
is
up
to
date
with
version
0.4
of
the
spec
in
version
0.2
of
the
hobbits
fire
protocol,
we're
currently
working
on
implementing
RPC
methods
for
request,
block
routes,
request,
block
headers
and
request
block
bodies,
block
bodies
and
we're
hoping
to
be
running
on
a
white
block
test
net
within
the
next
week
or
so.
Okay,.
G
A
H
H
We
also
optimized
a
lots
of
low-hanging
fruit,
because
processing
was
so
slow
that
he
didn't
fit
into
a
slot
and
for
test
night
we
even
switched
to
42nd
slots
4/4
time
and
we
also
started
to
integrate
new
state
tests.
So
first
step
was
loading
the
llamó,
validator
and
deposit
coffee
to
be
able
to
generate
genesee
state
state
state
from
it.
So
that's
done
and
then
the
next
step
is
loading
the
become
the
beacon
state
from
the
ml
file
and
compare
the
hashes
of
both.
H
H
You
know
I
think
framework,
because
we
had
some
clock
drift
during
simulation
and
regarding
the
p2p
we
did
some
architectural
research,
but
for
now
a
fascination
we
will
stay
on
our
P
X,
because
it's
more
solid
and
the
big
news
is
that
we
started
a
development
private
test
net
on
AWS
this
week
with
instruction
in
a
blog
post
and
in
our
repo
we
reached
out
to
non-members
steps.
Colleagues
and
a
couple
of
people
in
the
you
know,
jitter
channel
and
we
managed
to
install
run
the
client
connect
and
sync
or
private
test
net
successfully.
H
So
right
now
we're
just
are
running
out
on
boring
and
we
have
a
couple
of
issues
to
solve
regarding
that
traversals
and
pure
connectivity
like
low
ID,
hi
heidi.
If
people
remember
from
email
and
candy
mia
times,
and
we
should
have
something
to
show
at
larger
scales.
But
if
you
interested,
please
contact
us
great
about.
I
Harmony,
we
need
some
consensus
layer,
optimizations
like
question
of
keys
of
world
leaders
and
cash
in
shuffle
in
some
other
of
our
essence
of
ice.
Cash
were
added
also
did
a
slight
refactor
and
improvements
in
the
simulator.
So
now
a
transit,
faster,
finished
work
on
the
Bo,
SSD
and
shufflin
best
suits
and
now
working
on
consensus
tests
already
fascinate
a
few
of
them.
I
I
This
work
is
almost
done
encounter
the
several
issues
with
cross
link,
processing
I'm,
trying
to
make
some
rework
of
that
part
of
the
spec.
Actually
I
did
some,
but
not
sure
that
this
is
the
best
way
of
doing
that,
actually
going
to
open
a
pull
request
and
maybe
discuss
it
there.
So
that's
it
on
our
side,
great.
J
On
public
sort
of
test
net,
we
have
the
pol
cluster
running
it's
able
to
like
survive
restarts.
We
constantly
restarted,
though,
as
we're
upgrading
in
a
team
or
bug
fixes
a
bunch
of
like
strong
monitoring
and
spanning
tools
to
check
out.
What's
going
on,
people
can
join
in
from
the
outside
and
sync
up
with
the
network,
and
we
use
curly
for
the
deposit
contract
and
for
incoming
validator
deposits.
Pretty
much
yeah
we're
using
only
ghosts
and
there's
only
a
few
more
bugs
to
fix
and,
like
post
changed
our
validator
activation.
J
We
get
some
like
weird
base
conditions
or
requesting
assignments,
but
aside
from
that,
like
yeah,
we
just
want
to
leave
this
running,
for
we
make
sure
they
can
run
for
many
days,
do
a
little
bit
more
stress,
testing
and
then
have
some
more
people.
Try
it
out
before
we
go
out
into
the
wild,
but
yeah
things
are
getting
pretty
close.
We've
just
been
in
like
debugging
Hill.
We
were
like
at
a
bug
for
like
two
weeks.
We
didn't
know
what's
going
on
and
it
was
because
we
were
passing
India.
J
A
A
L
A
M
Zero.
The
other
good
news
is
that
we're
making
progress
on
phase
one
so
phase,
one
as
a
spec
will
be
split
into
three
parts.
Part
number
one
will
basically
specify
the
shot
blocks
and
the
structure
of
the
blocks
and
the
structure
of
the
attestations
in
the
shot
and
the
focus
rule
and
then
in
a
separate
document
that
will
basically
be
updates
to
the
beacon
chain
regarding
the
custody
game
and
it's
very
nice
and
simple
and
readable,
and
so
we're
kind
of
going
through
all
the
edge
cases
and
trying
to
make
it
super
solid.
N
O
P
Sorry
I
have
to
catch
a
train,
so
I
have
to
pop
out
right
after
this,
so
the
yeah,
so
the
en
our
spec
is
through
the
process.
So
it
was
accepted
when
the
last
orders
meeting
so
we're
able
and
I'll
try
to
get
some
people
to
actually
implement
it.
Now
that
we've
sort
of
formally
accepted
it
and
on
the
disk
e5
side,
what
we've
done
is
we
kind
of
solved
this
packet?
Signature
problem
was
talking
about
last
time,
so
just
briefly
capsule.
P
There
is
this
issue
where,
basically,
if
you
have
multiple
notes
using
different
sort
of
crypto
systems
for
their
node
identity,
then
the
big
question
was
how
they
could
authenticate
each
other's
packets
and
in
the
github
issue.
There's
now
looks
like
we
have
a
pretty
good
solution
using
H
Mac
to
verify
authenticity
of
the
packets
and
right
now,
I
am
implementing
that
so
I
I
don't
have
any
code
to
share.
P
You
know
yet
for
the
implementation,
but
it
is
progressing
and
we've
also
updated
the
specs
quite
a
bit
and
on
the
eighth
one
side,
we've
actually
sort
of
moved
all
the
related
specs
to
the
Deaf
PD
repo.
So
they're,
really
all
in
one
place
now
and
on
the
side.
I've
also
been
working
on
and
Eve
to
get
Ian.
Our
support
into
the
ROP
expects
so
that
that
will
be
an
e
for
our
case
version
6.
But
it's
not
super
high
priority,
so
it
might
actually
take
like
a
month
or
more
to
finalise
that
one.
A
Ok,
next
up
we'll
talk
about
the
network
spec
that
lives
in
the
repo.
There
was
obviously
a
ton
of
discussion
and
likely
to
be
a
ton
more
discussion,
but
given
that
we
kind
of
at
least
have
the
general
framework
I
merge
it
last
night
and
from
now
on
we'll
address
things
via
issues
and
subsequent
PRS
that
are
smaller,
more
digestible
Matt.
Do
you
have
any
specific
update
you
want
to
give
on
that?
A
Q
A
R
We've
been
working
with
Artemis
and
we're
also
working
with
lodestar.
I
agree
with
what
you're
kind
of
said
in
what
we
said
in
the
in
on
github
about
a
you
know,
single
client
essence
getting
the
clients
to
talk
to
one
another
before
working
on
any
interoperability
type
of
tests.
So
that's
kind
of
what
we're
focusing
on
and
after
we
get
load
start
talking
loads,
miss
Hawking
Artemis,
then
we'll
get
them
to
talk
to
each
other.
S
Yeah,
so
we
finalized
the
me
and
Antoine
finalized
the
Hobbit
0.2
spec.
We
just
stripped
down
to
basically
some
envelope
formats,
so
it's
agnostic
to
anything
else.
That's
going
on
the
community.
It's
just
sort
of
like
a
scaffold
until
the
p2p
is
there
sort
of
thing
and
that's
why
I
really
got
to
say
so
anyone
wants
to
use
up
at
zero
points
here.
It's
not
changing
anymore,
so
yeah
great
thank.
T
T
We
can
better
serve
any
questions
and
engage
discussions
and
so
on
right
now
those
discussions
are
kind
of
split
across
many
venues
and
I
think
that
putting
them
on
there
will
help
the
rest
of
them
to
be
to
be
team
to
participate
and,
in
general,
the
p2p
community,
so
I'll
be
once
this
is
set
up.
I
hope
to
finish
with
us
today
make
an
announcement
on
you
or
it
gets
a
chow
great.
A
A
U
This
is
one
request:
seven,
eight
seven
innate
to
from
specs
repo
anybody
wants
to
look
at
it.
Well,
I
talked
about
it,
so
this
is
updating
the
SSD
serialization
spec
to
include
an
offset
based
mechanism
that
was
originally
proposed
by
Peter
with
your
iam
team.
This
makes
essentially
dynamically
looking
up
data
within
a
stereo
eyes.
U
Objects
have
it's
constantly
fast,
it's
I
believe
o
log
in
or
something
along
those
lines
for
for
index
lookups.
It
also
actually
reduces
the
overall
serialize
size
of
SSD
objects
by
a
small
amounts,
essentially
just
by
touching
delete,
lengthy
fix
and,
in
general
seems
like
a
better
format
for
serializing
and
makes
this
formats
more
useful
for
being
able
to
reason
about
objects
within
context
like
bbm
or
other
resource
constrained
areas
and
I
am
NOT
a
hundred
percent
sure
on
this
last
one.
U
If
you
have
questions
that
you'd
like
to
ask
me
and
I
think
the
plan
would
be
for
this
to
take
effect
in
one
or
two
releases
of
the
2.0
spec,
so
not
something
that
would
be
dropped
in
immediately,
but
that
once
we
have
general,
you
know
unless
anybody
object
strongly.
That
sort
of
thing
to
include
this
as
part
of
a
spec
update
within
the
next
I
would
say
one
or
two
releases.
U
But
that's
that's
a
very
fuzzy
number
one
thing
that
was
proposed
and
that
we
generally
I
think
I
have
rejected
is
including
a
length
prefix
and
the
intent
behind
that
was
to
have
some
sort
of
forwards.
Compatibility
and
the
ability
to
have
extra
fields
be
added
to
objects
and
still
have
them
be
somewhat
backwards
compatible,
and
this
was
rejected
essentially
just
because
it
adds
ambiguity
to
the
serialized
representation
of
these
things,
and
that
ambiguity
can
have
a
number
of
like
unknown
consequences
down
the
road.
U
I
W
W
So,
basically,
a
lot
of
these
fixed
length
formats.
They
tend
to
align
fields
to
to
their
own
sized,
such
that
when
you
read
it
say
using
m
map
or
or
from
flash
memory.
You
don't
have
to
worry
about
insulin
issues
when
so.
Basically
what
you
do
is
that
you've
had
things
like
onions
to
a
slightly
larger
size,
just
make
it
easier
to
use
or
certain
kinds
of
hardware.
U
This
is
something
that's
outside
of
my
expertise
and
so
I.
Don't
think
I'm
qualified
to
comment
on
it,
but
I'd
be
happy
to
to
look
into
this.
Maybe
you
could
open
up
an
issue
or
something
kind
of
discussing
this.
My
initial
reflex
is
that
adding
things
out
further
decreases,
or
just
essentially
bloats
object,
sizes
and
that
I
have
some
resistance
that
initially,
but
also
I'm,
not
working
on
extremely
resource
constrained
devices.
So
I
don't
have
you
know
this,
isn't
the
problem
that
I'm
familiar
with.
W
A
Okay,
thank
you.
The
next
thing
I
have
in
there
is
test
net
progress,
roadmap,
project
management,
etc.
Mcara
brought
up
propose
bringing
in
the
cat
herders
to
potentially
help
us
as
we
are
moving
towards
more
public
test.
Nuts
I
did
leave
my
at
least
opinion
and
the
current
time
in
github,
which
is
there's
three
things
before
anyone
should
be
dealing
with
multi
client
test
nuts
one.
Do
you
have
a
long-standing
client
test
net
of
your
own
I?
Can
it
withstand
itself?
A
Is
it
targeting
if
it's
gonna
be
speaking
to
another
client?
Is
it
targeting
the
same
exact
version
of
the
spec
and
three?
If
targeting
that
version,
is
it
passing
set
of
consensus
tests
and
then
the
asterisks
on
three
is
actually
that
even
if
you're
targeting
105
one
right
now,
those
consensus
tests
are
very
much
sandy
tests,
they're
very
much
they
passed
through
a
handful
of
common
flows.
They
don't
handle
very
exceptional
or
interesting
cases.
A
So,
even
if
you're
passing
oh
five,
one
and
you're
both
passing
oh
five,
one
you're
ready
to
talk
to
each
other
cool,
get
ready
for
some
issues,
because
those
test
vectors
are
not
super
robust
and
we
expect
to
find
a
number
of
bugs
in
the
next
couple
of
weeks.
I'm
resist
I
know:
people
are
very
excited.
I
want
to
have
multi-client
test
nuts.
I.
A
A
Y
We
are
not
actually
working
on
someone.
It's
one
stuff
I
joined
a
call
today
to
just
to
understand
a
requirement
for
x2
p.m.
work
over
here
we
are
helping
mostly
with
the
heartful
thinged
upcoming
Istanbul
heartful,
and
would
be
happy
to
help
if
we
can
do
anything
about
the
PM
stuff
which
is
required
here
in
multi-client
as
night
stuff.
So
it's
just
the
introductory
one
and
trying
to
understand
the
requirement.
Y
A
So
the
requirements
from
my
perspective
are
so
and
the
way
I
see
things
progressing
at
this
point
are
for
people
to
I
know.
There
are
a
number
of
simulations
and
private
nuts
that
are
being
worked
on
right
now,
private,
as
in
a
single
client
and
internal
not
exposed
to
outside
users
as
these
mature
over
the
coming
months
to
two
months.
I
do
expect
clients
that
are
targeting
the
same
version
and
do
have
breast
implementations.
To
begin
to,
may
be
communicating
one-on-one
and
being
aware,
beginning
to
be
aware
of
those
processes
and
kind
of
figuring
out.
A
The
require
I
mean.
Ultimately,
the
idea
is
to
have
a
multi-client
test
net
long
long-lived
that
targets
a
single
specific
version
that
we
invite
people
from
the
community
to
participate
in
I.
Imagine
will
go
through
a
number
of
these
I've
also,
if
you're,
if
you
haven't
checked
out
cosmo
stood
of
handful
of
experiments
called
game
of
stakes
where
they
had
people
join
and
try
to
kind
of
break
some
of
the
economic
considerations
of
the
tests,
nets
and
gamify
the
test.
Nuts
and
game
fights
participation,
so
maybe
doing
some
of
that
down
the
line.
A
Z
Hey
this
is
late.
I
agree
with
everything
we
just
said:
I
just
wanted
to
jump
in
and
out
one
quick
thaw,
which
is
you
know
the
the
catheters
was
set
up
as
sort
of
a
community
resource
right.
So
it's
a
group
of
about
10,
experienced
project
managers,
we're
very
kindly
volunteered
their
time
to
help
out
with
whatever
needs
needs,
help
right.
A
A
A
E
Yeah
I
mean
after
you
disagree,
I
think
it's
really
important
that
we,
you
know,
weather
or
whatever,
use,
whether
it's
hobbits
or
something
like
that,
just
to
like
kind
of
get
some
float
whatever
the
two
multiple
nodes
together,
multiple
different
clients,
I
think
it's
super
important
like
if
Lupita
Pisa,
blocker
right
now,
for
instance,
for
us,
it's
a
huge
blocker,
because
the
JI
side
is
just
not
there
and
we're
working
on
it.
You
know
switching
to
something
like
hobbits
just
to
get
like
some
clients.
A
A
Yes
and
there's
also
a
daemon
available
that
a
couple
of
clients
are
beginning
to
use
and
so
between
either
getting
that
the
PDP
implicative
implementation
up
to
stuff
or
getting
kind
of
the
daemon
integrated
into
their
flows.
That's
that's
the
blocker
I
believe
on
the
NGO
side
and
Russ
side,
things
are
stable
and
currently
being
used
internally
and
then
on
the
Python
side.
We
have
some
bindings
that
we've
put
in
place
embedded
and
there's
also
I.
Think
all
the
p2p
native
implementation
being
worked
on
right
now.
A
R
O
V
V
He
says
that
he'll
provide
kind
of
more
of
an
update,
I
guess
at
the
end
of
this
week,
which
I
guess
would
be
today
or
tomorrow,
but
he
says
they're
pretty
close
to
having
a
some
basic
functionality
going.
So
I
think
that
that
applies
to
Artemis
and
in
harmony,
and
so,
if
the
harmony
guys
know
anything
else,
they
might
be
a
good
would
be
good
to
us
as
well.
Oh.
V
I
actually
kind
of
supported
that
you
know
that
methodology,
because
it
would
be
kind
of
cool
you
know
to
have
bindings
for
whatever
language
wants
to
use.
Lupita
be
not
the
wait
for
that
native
implementation.
However,
you
know
the
web
3j
guys
graciously
jumped
in,
and
you
know
said
that
they
were
already
planning
on
doing
a
job
on
plantation,
so
it
kind
of
removed
the
necessity
for
us
to
do
that
at
least
from
a
Java
side,
but
honestly,
like
I,
think
that
would
be
a
cool
thing
going
forward.
D
T
Know
it
talked
to
RO
quite
a
bit
and
by
the
way,
I
completely
agree
with
you
guys.
There
is
experimentation
on
this
ground
that
has
been
some
previous
experimentation
as
well.
I
know
that
that
peer
from
Russ,
the
p2p
has
been
also
experimenting
with
combining
down
to
Waddle
and
running
in
a
browser,
so
different,
runtime
modes
and
different
runtime.
The
program
motors
coordinates
is
something
that
I
mean.
I
would
personally
be
very
keen
to
explore
with
you
guys.
H
From
the
embassy
in
general,
we
also
had
this
question
about
how
to
move
on
with
Lea
p2p,
which
was
first
to
use
the
go
demon.
So
now
that's
working,
and
we
also
have
on
the
side
early
p2p
in
pure
name
implementation
that
is
going
on,
though,
for
testing
right
now
we
are
using
our
px
and
regarding
wrapping
rust
into
with
a
C
interface.
That's
something
that
we
ask
ourselves
a
lot
of
time
for
first
BLS,
because
Zika
is
done
in
rust
as
well,
and
there
is
no
and
desai
as
a
see
library
for
BLS.
H
AB
H
T
So
the
rust
and
the
go
implementations,
interoperate
wealth
and
in
fact
we
have
had
past
successes
in
this
regard,
so
so
that
is,
that
is
that's
complete
and
then
regarding
the
specs.
We
definitely
are
aware
of
this.
We
aim
to
be
aspects
first
project.
We
have
made
progress
in
some
critical
specs
like
prit
since
a
long
word.
A
few
elements
that
were
small
warrants
in
the
in
the
specs
have
showed
up
and
we
try
to
iron
those
up
and
as
we
go
forward,
we
will.
T
We
will
continue,
building
out
or
Rito
actively
specking
parts
of
the
system
to
make
them
to
make
them
available
to
you
guys
so
that
you
don't
have
to
always
refer
to
a
specific
implementation
in
parallel,
we're
also
writing
or
if
you
check
out
dr.
Pete,
Pete
Ohio,
that
is
already
taking
form
and
there
sections
that
are
already
fluid
content.
T
This
has
been
done
progressively,
so
it's
more
user
facing
documentation
so
to
speak,
but
I
think
that
would
be
useful
for
for
some
people
in
this
code
as
well
to
get
you
can't,
acquaint
it
and
get
familiar
with
some
of
the
concepts
and
there's
one.
A
third
track
that
we
are
working
on
is
an
it's
an
implemented
guide,
so
basically
a
1:1
manual
for
people
who
are
spearheading
an
implementation
of
canopy
to
be
to
have
a
single
reference
about.
You
know
from
the
viewpoint
of
an
implementer.
What
exactly
you
need
to
know?
T
What
are
the
ongoing
discussions
for
each
for
each
particular
element,
for
example
multi-stream
or
tea
stream,
2.0?
What
we
expect
to
change
in
the
future
where
it's
happening
with
cross
references
to
to
github
issues
or
requests,
and
so
on,
so
that
you
have
kind
of
like
one
canonical
walkthrough
that
you
can
use
to
thread
everything
together.
I
Thank
you
regarding
the
p2p
Chow
option.
We
are
still
considering
as
a
temporal
option,
making
a
Java,
binding
or
repeatedly
daemon
this.
This
would
work
in
a
case
if
we
would
be
a
broker
for
us,
I
mean
the
pure
Java
implementation
of
lipid
B,
and
this
is
something
that
could
be
crafted
in
a
reasonable
amount
of
time.
I.
G
A
Okay,
so
it
sounds
like
everyone
at
least,
has
one
or
two
potential
paths
forward,
depending
on
how
native
implementations
and
other
things
shake
out,
I
see
I
feel
like
we
jump
back
to
the
p2p
anything
else
related
to
the
PDP.
Obviously,
raul
is
an
awesome
resource,
Thank
You
Raoul
for
being
here
again
anything
else
on
this
before
I
move
on.
A
Okay,
general
spec
discussion,
I
have
something
so
I
found,
I
think
a
bug
related
to
some
Genesis
stuff.
The
way
we're
doing
it
and
I
think
maybe
another
bug
was
reported
yesterday
related
to
this
I
over
the
past
week
have
been
leaning
back
in
the
direction
of
moving
towards
Genesis
slot
0
and
putting
an
explicit
boundary
conditions.
This
became
a
little
bit
more
appealing
to
me
now
that
we
have
testing
and
now
that
we
have
an
executable
specs,
so
these
become
a
little
bit
simpler
to
integrate
into
the
spec.
A
A
A
That's
what
I
have
on
the
Specht
stuff?
There
have
been
at
least
the
stuff
that's
going
to
come
out
in
206.
There
are
a
few
decent
changes
that
are
like
radically
simplifying,
which
is
super,
exciting,
I'm
thinking,
probably
in
the
week
week-and-a-half
that
we
will
get
that
out.
Greg
a
Suzuki
drop
you
in
64,
no.
A
A
W
W
Is
good
because
we
get
apart?
This
is
important.
We
have
a
lot
of
the
reorg
switch
and,
and
then
it's
fairly
expensive
to
switch
switch
forks.
Unless
you
can
make
some
assumptions
about
things
being,
you
know
stable
in
mistakes,
so
it
would
be
very
nice
to
make
those
kind
of
demands
will
literally
help
yeah.
A
W
AB
A
So
I
numbers
are
gonna,
be
meeting
in
person
and
Sydney
on
the
9th
and
the
general
topics
and
I
wanted
to
put
these
out
here
in
case
I've
missed
something
glaringly
obvious
that
we
should
be
getting
together
is
we're.
Gonna
have
three
breakouts
in
the
morning.
I
have
to
breakouts
in
the
afternoon
right
now,
but
I'd
like
to
make
it
three
so
face
two
slash
walls
and
slash
data
execution.
A
A
A
Networking,
maybe
in
the
morning
could
be
focused
on
more
of
the
networking
protocols
and
things
we
need
to
work
through
there,
whereas
maybe
in
the
afternoon
we
could,
if
there's
maybe
some
value
and
extending
that
and
talking
about
network
aggregation
strategies
and
things
like
that.
I
know
the
handle,
guess
we'll
be
there.
A
Guess
it's
a
short
meeting
cuz
everyone
has
so
much
to
work
on
cool.
Thank
you.
Everyone,
good,
beating,
productive,
again,
super
exciting
to
see
all
the
progress
I've
people
have
been
kind
of.
I've
definitely
continued
to
be
a
resource
like
if
you
run
into
some
weird
bugs
or
like
some
weird
spec
stuff
like
please
just
hit
me
up,
because
I
can
probably
save
you
some
time
or
sometimes
I
could
save
some
time
cool
thanks
guys,
I!