►
From YouTube: Agoric Community Call #27 (Dec '22)
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
A
So,
let's
kick
this
off,
so
obviously
last
Community
call
the
year.
You
know
my
thinking
for
this
is
you
know
a
really
high
level,
maybe
year
in
review
for
a
gorick,
because
I
think
a
lot
happened.
A
You
know
we
have
folks
who
joined
recently,
people
who
are
listening-
and
you
know
who
might
have
joined
mid-year,
who
missed
a
lot
of
what
we
what
we
did
earlier
this
year,
so
I'm
kind
of
thinking
we
could,
like
you
know,
just
shoot
through
some
things
that
you
know,
Milestones
accomplishments
of
a
gork
and
I
will
probably
miss
things.
So
do
not
hate
me
if
I
miss
anything
just
speak
up.
A
Jesse
Roland,
you
guys
tackled
a
lot
this
year
as
well.
So
you
know
if
we
do
miss
something.
Let's,
let's
you
know,
let
me
know
and
then
I
think
we
can
just
go
right
into
some.
Some
of
the
more
recent
updates.
You
know
where
we're
looking.
What's
the
future.
A
So
I
think
maybe
the
best
way
to
panel
is
I
can
kind
of
run
through
some
of
these,
and
you
know
if
anyone
wants
to
add
some
some
color.
Let's,
let's
do
it.
So
obviously
we
had
our
our
you
know.
Last
year,
technically
we
had
our
public
sale.
A
You
know
we
that
brought
in
about
48
000
new
token
holders.
It
was
you
know
we
had
about
50
million
build
purchased.
You
know
I'm
thinking
that
world
too
relevant.
You
know
we
we
brought
on
for
custody
providers
that
super
useful
shout
out
to
to
Vanessa
for
a
lot
of
work.
There
I,
don't
I,
don't
see
her
on
this
call
yet,
but
if
she
is,
you
can
jump
up.
A
You
know
I'm
thinking
around.
You
know
some
of
the
big
kind
of
engineering
milestones
and
product
Milestones.
You
know
agoric,
obviously
connected
to
IBC
huge,
shout
out
to
validators.
You
know
Jesse
I
know
you
worked
a
lot
on
that.
So,
if
there's
anything
you
want
to
include
there
quickly.
Please
do
oh.
B
A
Yep
yep
yep,
that's
great
yeah
and
I
think
that
that
kind
of
laid
the
the
road
you
know
for
those
unfamiliar
you
know
gork.
You
know
we
have
a
a
very
high
level
road
map
of
mainnet
phases
and
that
really
opened
the
door
for
for
mainnet,
one
which
you
know
Dean
maybe
want
to
touch
on
this
briefly,
but
you
know
really,
you
know,
did
a
lot
for
our
contract
platform.
Well,.
C
So
mean
that
one
was
you
know
we
we
had
the
cosmos
layer
out
which
the
the
you
know,
the
the
the
the
the
fires
in
in
June
July
were
were
resolving
issues
on
down
through
the
the
cosmos
layer,
along
with
other,
you
know,
other
folks
across
the
the
cosmos
Community.
But
in
October
we
launched
our
JavaScript
VM
with
the
initial
use
case,
which
is
of
course
IST
inner
inner
protocol,
and
so
you
know
having
running
JavaScript,
running
deterministically
with
failover
and
restarts
and
all
these
kinds
of
things
that
we've.
C
That's
just
a
huge
huge
step
forward
of
getting
that
that
real,
you
know,
looking
at
Zoe
offer
safety
for
those
of
you
familiar
with
it
or
the
the
the
the
the
the
durability
and
contract
upgrade
stuff
or
those
kinds
of
things
you
know
seeing
those
in
production
was
is
just
awesome
so
that
that
that
went
out
in
October
in
October
with
the
you
know,
launch
of
JavaScript
contracts
on
chain
and
the
launch
of
IST
and
again
back
to
that
Community.
C
The
community
you
know
pulled
together,
did
the
validation,
testing
roll
out
community
members
made
the
bridges
out
to
you,
know,
osmosis
and
and
and
axelr
and
Crescent,
Etc
gravity
and
so
forth,
and
you
know
set
up
the
the
pools
for
ist
ist
available
on
several
of
those
those
partner
chains.
C
So
so
that's
all
been
steadily
happening
since
the
PSM
launch
in
October.
So
that's
some
of
the
the
the
on
the
ISD
side
on
the
more
General
programming
platform
framework.
Of
course,
as
I
said,
we've
gotten
the
battle
testing,
but
we've
also
been
working
with
mainnet
with
partners,
for
you
know,
developing
their
own
applications
to
run
on
the
JavaScript
platform
and
framework,
so
create
from
crya
lh2
staking
crabble
agreeweek
Calypso.
C
Continuing
that
Community
thing.
Also,
of
course,
the
people
that
that
purchase
tokens
token
virtual
purchasers
with
the
network
up
with
rewards
turned
on
people
were
staking.
We
had
a
push
in
April
to
get
people.
C
You
know
to
get
the
chain
up
to
what
appears
like
30,
it's
now
up
to
40,
but
a
big
chunk
of
tokens
are
still
in
reserves
for
decentralization
in
community,
so
that
number
actually
looks
more
like
60
of
the
tokens
that
could
be
staked,
which
is
you
know,
the
Target
that
I
was
really
looking
forward
to
reaching
this
year,
and
so
so
I'm
really
happy
that
we've
got.
You
know
big
chunk
of
the
network
Stakes
even
before
we've
rolled
out
our
our
our
our
general
availability
of
the
programming
layer.
C
So
you
know
so
so
so
so
that's
going
to
be
a
lot
of
our
I.
Don't
know,
should
I
talk
about
shifting
Focus
for
next
year
or
save
that
for
the
end
good
question,
so
so
a
lot
of
what
we'll
be
doing
you
know
so
this
year
we
got
IST
out
it's
now
in
the
phase
of
of
you
know,
and
and
people
launch
it
it's
now
a
separate
Community,
it's
in
the
phase
of
integrating
with
other
chains
so
that
they
can
have
a
stable
token
that
works.
C
You
know
across
across
the
interchain
and
provides
as
I
say,
griefs
for
the
gears
of
Commerce
in
in
interchange.
Commerce,
which
is
you
know,
Cosmos,
is
leading
the
way
on,
but
the
platform
is,
of
course,
the
core
thing
that
that
is,
you
know,
sort
of
the
heart
of
the
agorak
technology
is
the
the
hardened
JavaScript
and
the
framework
that
enables
rapid
composition
of
components.
So
we
built
IST
as
components.
C
We
built
it
as
reusable
modules
and
we
built
it
to
be
extensible,
which
is
the
the
key
advantage
that
IST
will
have
over
other
stable
tokens.
C
Is
it
straightforward
to
add
new,
solvent
robust
modules
to
to
to
to
enhance
how
you
come
into
IST,
and
we
are
certainly
in
the
process
of
building
more
of
those
modules
or
finishing
up
more
of
those
modules
so
that
the
ISD
Community
can
roll
those
out,
but
but
the
goal
for
next
year
is
of
course
make
the
platform
generally
available
for
people
to
be
building
smart
contracts
on
so
I
mentioned
the
main
into
Partners,
but
other
things
we
did
this
year
there
was
even
in
February,
we
did
the
we.
C
We
worked
with
the
blue
lava
conference,
which
was
really
teaching
web
2
developers
about
blockchain.
So
it
was
a
purely
focused
on
brand
new
web
2
developers
to
see
which
things
got
them
interested,
which
things
excited
them
which
what
kinds
of
use
cases
they
wanted
to
pursue,
what
kind
of
problem
they
needed
to
solve.
You
know
we
carried
some
of
this
through
you
know
we
were
other
events
Gateway
in
Prague,
the
cosmos
Cosmo
verse
in
Medellin
consensus
and
massari
mainnet.
C
C
Then
the
last
thing
you
know
backing
up
to
sort
of
building
the
community
building
the
framework,
in
addition
to
all
the
community.
Building
that
Jesse,
spearheaded
in
in
in
in
in
June
and
the
validators
all
jumped
on
board
really
sort
of
helped
us
all.
Pull
that
ecosystem
and
Community
together,
DCF,
launched
and
and
and
Rick
can
talk
about.
What
DCF
did
this
year
is
right
is
Rick
here.
Yes,
we
have
DCF
in
the
house.
D
D
D
During
that
period
of
time
really
dcf's
focus
has
just
been
trying
to
get
all
the
nuts
and
bolts
operational
side
of
things
together,
but
we've
also
been
able
to
take
a
couple
of
steps
that
are
more
substantive,
particularly
going
through
that
first
round
of
Delegation
that
we
engaged
in
where
we
moved
45
million
tokens
that
we're
sitting
in
the
DCF
treasury
into
delegation
with
the
agoric
validators,
and
that's
something
that
we're
looking
to
reassess
and
evaluate
going
forward
into
2023.
D
You
know
taking
a
look
and
see
if
people
have
met
their
commitments,
seeing
how
the
security
profiles
are
looking
these
days
and
seeing
what's
new
out
there
that
that
deserves
support
as
well.
So
that's
something
we
will
be
reassessing
coming
in
q1
we're
also
looking
in
q1
at
things
like
getting
bounties
set
up
having
a
proper
Bounty
program
that
is
strategically
aligned
with
supporting
the
ecosystem
is
a
very
important
part
of
what
we
plan
to
do
and
2023
we'll
see
the
launch
of
that.
D
Similarly,
in
this
last
year,
we
we
took
some
very
first
baby
steps
in
that
direction.
Doing
some
support
for
things
like
events
at
consensus
and
massari,
and
and
also
supporting
what
was
happening
in
Gateway
in
Prague.
Sorry
I
was
drawing
a
blank
on
the
name
there
for
a
second
so
expect
to
see
more
of
that
from
us
going
forward
in
2023.
D
I
suppose.
Also,
probably
one
of
the
big
accomplishments
for
us
is
that
we
got
really
a
rock
star
board
of
directors
in
place
right
now,
we've
got
four
of
our
five
seats
filled,
we're
looking
to
fill
that
fifth
seed,
as
we
speak
going
through
interviews
for
that.
So
that's
an
ongoing
process,
but
I'm
really
happy
with
where
we've
landed
up
to
this
point,
and
it's
it's
really
been
a
pleasure
working
with,
with
all
of
you
guys
so
I
don't
want
to
monopolize
the
discussion
here
today.
D
D
Yeah,
slowly
slowly,
that's
that
is
coming
together.
I
mean
the
economic
committee
has
I
think
been
really
huge
for
us
on
the
ISDN
or
protocol
side
of
things
and
I
think
we're
going
to
be
doing
some
more
interesting
things
with
governance
going
forward.
But
right
now
it's
all
been
about
getting
the
mechanism
in
place.
Getting
the
processes
documented
and
con
communicating
that
to
the
community
so
slowly
slowly,
but
yeah
we're
getting
there.
B
To
add
one
little
thing:
I
was
looking
at
a
a
Tracker
that
we
have
on
community
items
and
Community
participation
since
August.
Our
community
alone
is
engaged
in
about
35,
separate
activities,
discussions,
governance,
participation,
hooking
up
IBC
channels
that
have
really
made
the
network
come
to
life.
It's
been
a
fantastic
year
for
participation
in
our
ecosystem
and
I.
Think
next
year
is
going
to
be
even.
C
E
So
you
know
that
was
a
great
overview
of
the
last
year
and
as
we
were
going
through
it
I
was
thinking
wow
there's
like
50
other
things
that
we
we
couldn't
mention
here,
but
it
just
so
much
happened
to
talk
a
little
bit
about
what
we're
actually
doing
now
and
sort
and
what's
upcoming,
I
want
to
start
by
saying
a
few
folks
in
the
community
have
asked
about
the
the
current
roadmap
and
I
really
appreciate
the
engagement
there.
E
We
are
targeting
sort
of
getting
back
into
the
rhythm
of
updating
the
road
map
so
that
there's
sort
of
always
this
view
online
of
of
what's
coming
over
the
next
several
months,
we
were
doing
that
through
most
of
the
year
and
then
with
the
Pismo
release
and
with
Ivan
coming
on
for
engineering.
We
we
sort
of
dropped
off,
but
to
give
the
overview
here.
E
We've
got
work
going
in
in
a
bunch
of
different
categories,
so
you
can
sort
of
think
of
it,
as
agoric
is
targeting
the
next
major
release
of
the
platform
after
Pismo,
which
includes
a
few
important
elements.
One
is
upgrades
to
the
platform
itself,
so
those
will
include
bringing
the
developer
experience
with
ag
solo
and
smart
wallet
back
together.
E
So
getting
everything
in
line
with
Pismo
release,
which
will
help
our
our
mainnet2
partners
will
help
third-party
developers
that
are
working
on
the
platform,
making
sure
that
they're
able
to
work
with
the
latest
software
so
that
actually
will
likely
go
out
prior
to
the
next
release,
because
it's
not
a
mainnet
upgrade.
But
then
the
upgrade
itself
includes
changes
to
inter-protocol.
So
we
have
the
vaults
release
coming
up
as
the
next
major
item,
and
so
that
has
been
undergoing
major
planning
effort.
E
C
E
That's
exactly
right,
and
so
in
particular,
for
example,
the
liquidation
mechanism
for
vaults
has
come
as
a
design
through
discussions
with
a
whole
bunch
of
different
stakeholders
and
we'll
we'll
look
to
get
that
posted
on
the
community
Forum
as
well
likely
this
week
or
early
next
and
and
so
that
has
been
a
major
effort
from
a
design
and
planning
standpoint
on
our
end
and
then
the
the
piece
that
goes
along
with
that
is
also
oracles,
which
you
know,
inter-protocol
will
be
the
first
major
consumer
of
price
feeds
via
oracles,
but
it's
also
critically
important
for
any
other
D5
protocol,
that's
launching
on
agoric
and
so
that
first
end-to-end
use
case
we're
we're
putting
together
in
conjunction
with
simply
staking
in
the
decentralized
Oracle
network
that
we've
been
speaking
with
and
there's
sort
of
software,
both
on
the
agoric
side
and
on
the
simply
staking
side
there
and
a
whole
bunch
of
testing
and
planning
to
to
make
sure
that
that's
up
and
running
effectively.
E
We
also
are
working
on
IBC
loopback,
which
is
a
really
cool
set
of
functionality.
That
I
knew
I
knew
Dean
would
jump
in
so
Dean.
C
Well,
so
IBC
loopback
is
one
of
the
the
pieces
of
IBC
that
was
specified
but
was
never
quite
implemented
and
it's
sort
of
a
core
basic
functionality
of
TCP
that
I
can
open
the
g2b
connection
to
another
machine.
I
can
also
open
it
to
my
local
machine,
and
so
that's
got.
You
know,
sort
of
basic
network
engineering
functionality
like
if
I
want
to
do
testing
of
IBC
on
the
same
machine
that
I'm
running
the
IBC
thing.
C
I
need
to
be
able
to
invoke
IBC
connections,
but
have
them
connect
to
processes
on
the
local
chain
the
place
where
that
shows
up
for
for
smart
contracts.
This
is
you
know
both
the
gork
and
it'll
matter
for
cosmoplasm
as
well
is
we've
already
had
bounties,
where
we
had
a
smart
contract
written
in
JavaScript
that
could
reach
over
ICA
entertain
accounts
to
control
a
a
seat
on,
for
example,
in
a
cost
chain
to
start
up
jobs
or
or
manage
jobs
or
detect
when
they
failed.
You
know
that
kind
of
job.
C
If
I
was
going
to
do
anything
useful
on
the
cosmo
side,
I
would
like
to
be
able
to
apply
that
contract
to
point
at
our
own
chain.
So
we've
we've
already
got
one
group
RH
thinking
that
that
they're
doing
liquid
staking
where
they
want
to
be
able
to
manage
staking
locally
they've
got
contracts
that
can
issue
these
requests
over
IBC.
So
you
could
run
a
smart
contract
on
a
gork
to
control
staking
on
another
chain,
but
because
loopback
is
not
yet
implemented.
C
You
can't
use
the
very
same
mechanism
to
control
staking
on
the
Agora
chain
and
so
that's
sort
of
a
basic
functionality
in
IBC
that
will
benefit.
You
know
the
entire
Community,
but
is
critical
to
to
one
or
a
couple
of
well
critical
to
this.
This
this
liquid
staking
use
case,
and
it's
also
critical
to
improve
systemic
testing
of
IBC
by
being
able
to
do
local
CI
with
a
with
multiple
parties,
all
engaging
in
IBC
Communications
with
each
other.
So
I'm
really
excited
about
that
I'm
working
with
Strangelove.
C
On
that
you
know,
and
and
and
the
folks
like
a
d
yeah
that
that
our
reviewers
and
provide
architecture
and
and
the
whole
IBC
thing
is,
you
know,
know
what's
coming
and
has
been
been
adding
in
their
their
their
feedback
and
comments.
So
so
I
think
that'll
be
a
really
useful
sort
of
community
good,
as
it
were.
E
Yeah,
that's
right
really
excited
for
IBC
loopback
and
then
we're
also
working
on
rapid,
secure
network
rejoin
for
validators
which
which
yeah
Jesse
is
named.
Statesync
plus.
C
I
mean
you
want
to
go
through
exactly
Ivan
did
so
so
State
think
is,
of
course,
the
cosmos
level
to
be
able
to.
You
know
rapidly.
You
know,
validate
your
sort
of
key
to
the
ecosystem,
key
to
the
system
working,
and
so
this
was,
you
know,
to
be
able
to
rapidly
create
a
new
validator
or
restart
a
validator
or
start
one
over
or
what
have
you.
Statesync
is
useful
at
the
cosmos
level
for
being
able
to
do
that.
C
Now
we
have
layers
of
software
above
the
cosmos
level
that
also
need
to
participate
in
that
kind
of
thing
and
and
satisfy
the
general
requirement,
the
general
goal
of
rapidly
starting
a
new
node,
and
so
this
is,
you
know,
statesync,
plus
all
the
additional
wrinkles
that
we
need
to
be
able
to
get
a.
C
You
know
asynchronous
message
in
communication
with
the
client
all
restored
and
you
know
vm's
all
restored
to
the
same
state
points
and
that
sort
of
thing-
and
so
that's
something
that
that
you
know
the
validator
community
has
raised
as
a
as
a
as
a
as
a
missing
feature
and,
and
we
very
much
want
to
get
you
know,
get
it
back
in
and
available
to
to
to
simplify
the
or
prove
the
the
validator
support.
C
So
that's
that's
in
the
process
of
investigation,
and
you
know-
and
some
development
has
already
started,
and
that's
one
of
the
things
that
we
expect
to
roll
out.
You
know
as
soon
as
possible
in
our
in
our
next
release
and.
E
So
we'll
we'll
make
sure
to
have
a
clear
summary
of
of
what's
being
worked
on
right
now
and
as
well
to
have
things
posted
on
the
community
forums
in
in
the
next
week
or
two
and
and
to
make
sure
that
that's
sort
of
up
to
date
as
we
move
forward
the
one
other
thing
that
we
we're
doing
a
bunch
of
work
on
is
making
sure
that
upgrade
of
the
chain
after
it's
already
live
and
has
a
bunch
of
JavaScript
State
is,
is
ready
to
go.
So
this
will
be.
E
This
next
release
will
be
the
first
upgrade
where
you
know
post
Pismo,
which
is
really
exciting,
so
I
think
with
that
I'll
turn
it
over
to
other
folks,
but
a
whole
lot
going
on
in
the
engineering
and
product
side.
B
B
Nets
are
going
to
be
an
incredible
playground
in
the
coming
year,
so
I'm
really
going
to
be
looking
to
our
community
and
folks
who
want
to
come
in
and
play
with
some
of
these
toys
we've
been
building
to
come
and
help
us
challenge
them
and
assess
them
and
dig
in
and
make
sure
they
do
what
we
think
they
do.
Let's
see,
besides
all
the
fun
stuff,
that's
coming
up
next
year,
as
usual,
I
have
an
update
on
security
audits,
woohoo,
we
just
closed
an
assessment.
B
Last
week
we
haven't
gotten
the
report
yet,
but
I'm
gonna
tell
you
some
stuff
anyway,
this
particular
assassination
agency
had
them
take
a
look
at.
We
had
them.
Take
a
look
at
Cosmic
swing
set.
We
had
them
poke
at
the
Smart
wallet
a
little
bit
more
and
we
also
had
them
look
at
the
giant
overall
whole
PSM
implementation
them
in
this
case
is
a
tritus
Partners.
Probably
one
of
the
best
firms
I've
had
the
pleasure
to
work
with
in
my
career.
They
dug
up
three
low
severity
issues,
a
couple
of
them.
B
So
we
will
be
publishing
the
report
as
soon
as
we
have
a
chance
to
get
it
and
comb
through
it
with
that's
going
to
show
up
on
agoric.com
security,
I
hope
that
we're
able
to
calm
down
for
a
minute
and
get
a
Blog
out
about
all
this
crazy
security
audit
work,
we've
been
doing
for
the
past
year
and
a
half,
but
that's
also
something
that
is
on
my
stretch,
goal
for
New
Year's,
so
keep
an
eye
again
on
our
security
page.
For
that
how
many
security
guards
I
quit
counting,
but.
B
So
here's
here's
something
Dean
won't
like
me
saying,
don't
say
it
anyway.
Our
new
trick
is
that
we
try
to
run
security
audits
without
deem
knowing
that's
how
regular
being
they
are,
and
it's
kind
of
amazing,
because
there's
at
least
one
he
didn't
realize
what's
happening,
which
means
on
the
security
front.
Our
security
engineering
Shenanigans
have
been
amazing.
B
B
Yes,
yes,
so,
besides
that,
most
of
you
know
that
we,
you
know,
work
on
security
things
quite
a
bit.
We've
actually
grown
our
security
engineering
team
significantly
and
a
thing
that's
been
on.
Our
list
is
to
get
started
with
threat
models.
Threat
models
are
essentially
a
kind
of
security
process,
documentation
where
you
enumerate
all
the
risks
that
live
in
code,
and
we
have
enough
security
engineering
muscles
that
we
can
really
dig
into
this
work
deeply
and
work
on
the
written
documentation
and
go
through
the
whole
fancy
framework.
B
We're
going
to
kick
that
off
in
tandem
with
the
development
of
vaults
and
Oracle
early
next
or
the
Oracle
Network
for
inter
early
next
year,
not
sure
when
we're
going
to
be
able
to
publish
them,
because
it's
a
really
significant
bit
of
work.
But
it's
super
exciting
I,
don't
know
of
another
team.
That's
actively
threat.
Modeling
like
it
is,
you
know
the
World
Cup
Final
in
their
blockchain
protocol,
so
that's
pretty
exciting
and
we
have
also
got
some
ongoing
work.
B
I've
mentioned
our
partnership
with
multiple
and
all
of
the
work
that
we've
put
into
fuzzing
with
excess
for
some
time.
Over
the
past
few
weeks,
we've
actually
gotten
to
a
really
interesting
place
where
we
noticed
that
there
was
a
Slowdown
in
finding
bugs,
and
so
we
decided
to
get
hacking
a
little
bit
more.
We
played
with
OSS
fives,
we
tweaked
physically
excess
is
written
in
C,
so
you
know
bugs
just
happen
there
and
that's
okay.
B
We
don't
freak
out
about
them,
but
we
have
a
new
hire
who
joined
us
in
October
Raphael
and
he
has
done
an
incredible
work
with
Peter
from
audible
to
just
make
these
wild
bugs
fall
out
of
the
code
over
the
past
year.
You
know,
we've
put
all
kinds
of
buzzers
and
harnesses
and
things
together,
but
this
past
month
has
been
particularly
exciting
and
I.
B
Just
really
think
that,
even
though
fuzzing
is
fuzzing
and
maybe
automated
security
testing's
boring,
we
really
have
to
celebrate
this
because
we've
had
a
great
year
and
a
half
with
this
work,
and
it's
going
to
set
us
up
for
an
incredible
name
at
three
when
it's
time
for
that
thing
to
show
up,
besides
that
on
the
community
or
on
the
main
net
operation
front,
we
do
have
some
updates.
B
A
couple
weeks
ago
there
was
a
little
validator
restart
issue
on
mainnet
and
I
might
have
made
a
little
bit
of
a
noise
about
that
one,
because
we
don't
like
it
when
the
nodes
can't
turn
off
and
turn
on
again.
We
think
we
know
what
the
root
cause
is,
but
our
engineering
team
is
getting
to
work
on
that
one
really
small
impact.
B
It's
only
I
think
we've
got
two
nodes,
so
we're
still
working
on
it,
but
we
will
probably
have
some
updates
on
that,
the
next
time
we're
ready
to
cut
a
software
release
and
then
on
Monday.
We
had
another
little
mainnet
hiccup,
where
the
network
sort
of
got
congested
and
took
a
half
an
hour
to
to
clear
itself
up.
B
We
also
got
to
work
on
that
in
less
than
an
hour,
we
were
able
to
respond
and
throw
up
a
Discord
thread
and
get
our
our
GitHub
issue
where
we're
collecting
information
and
troubleshooting
going,
but
validators
definitely
keep
an
eye
out
on
those
things.
We
are
working
to
make
sure
that
we
figure
out
the
root
cause
and
we
patch
it
up
and
ship
it
out
as
soon
as
we
have
answers
besides.
B
That
last
bit
of
news
is,
it
is
time
for
us
to
schedule
validator
office
hours
for
December,
so
if
you're,
a
validator
or
you're
thinking
about
being
a
validator
or
you
hang
out
in
devnet
and
test
Nets
keep
an
eye
on
Discord.
B
We
will
put
some
time
aside
so
that
we
can
do
a
couple
things
talk
about
what's
on
the
roadmap
for
next
year,
but
also
share
some
updated
security
run
books
so
that,
when
things
happen
in
you
all
know
how
we're
going
to
reach
out
to
you,
you
know
how
to
tell
us
something's
wrong:
hey
Discord
still
works
really
great,
though,
and
we
will
just
spend
a
little
time,
maybe
reflecting
on
some
of
the
adventures
we
had.
This
year
and
that's
me.
A
All
right,
I
think
that
sums
most
of
it
up
Dean.
Any
other
closing
thoughts
for
this
community
call.
C
You
know
it
has
been
an
education
getting
into
the
the
the
world
of
Cosmos
and
then
actually
launching
and
seeing
just
you
know,
I
mean
you
sort
of
you
know
the
community
is
important,
but
then,
when
they
start
when
they,
when
they
start
actually
carrying
the
ball
and
solving
problems
and
reacting
quickly-
and
you
know
and
and
and
and
and
really
you
know,
taking
ownership
of
of
of
of
getting
Solutions
out
there,
it's
just
it
it's.
C
You
know,
there's
just
nothing
like
that
feeling,
and
it's
also
such
a
relief
to
have
to
have
that
uptake.
So
I
am
looking
forward
to
to
providing
the
community
ever
more
things
to
be
able
to
do
stuff
with
the
big
thing,
as
I
said
is
we
are
you
know
it's
worth
worth
worth
repeating.
You
know
we
have
launched
IST
the
key.
The
econ
committee
is
out
there
and
is
you
know
and
is
doing
things
Beyond.
You
know
what
we
started
with
you
know
die
just
went
live.
C
Thank
you
community
for
doing
that,
and-
and
we
are,
we
are
continuing
to
build
the
software
for
that,
for
what
the
ISD
Community
will
need
and
want
leveraging
the
power
of
agorak,
and
we
in
in
2023
we'll
we'll
be
continuing
to
do
that
and
have
the
have,
the
the
you
know
really
start
focusing
on
building
up
the
development
environment,
development,
tooling,
developer,
documentation,
Etc
for
people
to
build
their
own
applications
and
businesses
on
top
of
on
top
of
the
igoric
platform.
C
So
you
know,
that's
been
our
long
time,
Mission
and
I'm
really
excited
to
to
to
be
you
know
to
to
to
to
to
have
laid
the
groundwork
for
that
where
I
said,
IST
is
a
big
part
of
the
groundwork.
C
Our
long-term
mission
is
an
economy
in
which
you
can
launch
things,
and
we
think
that
you
know
stable
token
is
a
critical
part
of
that,
and
so
and
and
it's
gone
from
an
economy
in
which
you
can
launch
that
into
we
care
a
lot
about
an
entertaining
economy
into
which
we
can
launch
things,
and
so
that's
going
to
be.
You
know,
that's
that,
that's
that's
going
to
be.
C
What's
driving
us
all
next
year,
so
I'm
really
excited
about
that
and
I
look
forward
to
working
with
everyone
and
hearing
everything
that
they
need
and
and
and
building
awesome
software
to
solve
those
problems.
So
thank
you
all.
A
Thank
you,
Dean
yeah.
Let
me
know,
there's
a
there's
also
a
in
a
protocol
Community
call
next
week,
Thursday
at
9,
30,
Pacific,
4,
30,
UTC,
so
yeah
I
think
there'll
be
some
fun
updates
from
that
team.
Yep
yep.