►
From YouTube: Agoric Community Call #31 (April 2023)
Description
00:36 Update on Chainboard Academy Bootcamp
03:29 Mainnet-1B Release Update
05:15 Contract Upgrades and State Sync
11:02 Contract Audits and Liquidation Testing
13:46 Scalability and Documentation for Mainnet-2
16:00 Delegation Program Update
18:19 Discussions on Community Forum (community.agoric.com)
19:30 Upcoming Events and Conferences
A
A
Yeah,
let's
kick
it
off
so
yeah
thanks
everyone
for
being
here,
31st
Gore
Community
call
always
awesome
yeah
bringing
bringing
updates
across
a
bunch
of
different
departments
and
initiatives
we
have
going
on
at
agork
and
I.
Think
I
think
it
would
be
kind
of
fun
to
kick
it
off
with
you
know
the
chambered
Academy's
recent,
the
gork
boot
camp
that
they
just
launched
last
week
or
actually
this
week
technically
with
their
first
course.
A
B
C
B
Yeah
so
they're
covering
a
bunch
of
topics
including
Sony
Smart
contracts,
ER
TP,
working
with
different
apis,
so
working
with
oracles,
so
really
being
able
to
fully
launch
adapts
coming
out
of
it.
So
yet
again,
just
really
excited
to
see
the
kind
of
projects
that
people
be
working
on,
and
hopefully
you
know
this
will
truly
be
almost
like
an
incubator
for
different
products
that
are
building
on
agoric.
C
That's
cool,
that's
very,
very
cool
I'm,
so
excited
we
have.
We've
had
people
that
we
that
that
came-
and
you
know
have
have
been
looking
digging
into
the
code
and
being
able
to
point
them
at
chamber
Academy
and
they
dive
in
and
go
wow.
This
is
really.
This
is
really
great
stuff,
so
that
it's
been
great
to
hear.
A
Awesome
awesome,
yeah.
My
understanding
too,
is
it's.
It's
it's.
You
know
it's
meant
for
fairly
entry
to
intermediate
level
developers
right
familiarity
in
JavaScript.
It's
it's
that's
correct
yeah,
so
it
is
accessible,
so
yeah
I
think
for
the
people
on
this
call
or
if
you
know
folks,
who
are
looking
to
dip
their
toes
and
they
are,
you
know
traditionally
more
JS
leaning
this.
This
would
be
a
really
good
opportunity
and
yeah
the
yeah.
The
next.
The
second
lecture,
which
is
actually
also
open,
you've
mentioned
you
know,
is-
is
on
Monday
April
10th.
A
So
that's
kind
of
the
the
opportunity
there
to
get
your
foot
in
the
door
if
you're
interested
so
yeah
definitely
we'll
be
announcing
that
and
sharing
more
information.
You
know
throughout
this
week
until
that
second
lecture
starts
again
cool.
Thank
you
Gene.
You
know
why?
Don't
we
dive
into
some
of
the
you
know?
Maybe
the
one
of
the
hearts
of
topics
around
mainnet1b,
maybe
Roland
and
and
Dean.
If
you
want
to
jump
in.
C
D
Okay,
okay,
color
commentary
yeah.
So
so,
as
lots
of
you
know,
the
the
next
release
that
we're
targeting
is
mainnet
1B,
which
is
really
the
completion
of
what
we
had
been
calling
magnet,
one
which
is
sort
of
the
the
release
of
the
virtual
machine,
smart
contract
framework
and
the
full
set
of
inter-protocol
contracts
which
again,
inter
protocol
controls,
IST,
which
is
the
gas
token
that
pays
for
execution
in
the
virtual
machine.
D
D
This
release
includes
a
whole
bunch
of
additional
contracts
to
control
the
inter
protocol,
which
include
vaults,
liquidation,
Reserve,
some
additional
updates
to
governance,
some
updates
to
the
smart
wallet,
but
then
critically
also
includes
a
bunch
of
platform
upgrades
that
needed
to
happen
to
get
us
to
the
point
where
we're
sort
of
in
a
position
for
third
parties
to
build
and
deploy,
and
so
that
includes
kernel
and
contract
upgrades.
So
the
ability
for
your
contracts
to
survive
a
chain
upgrade.
It
includes
validator
statesync,
which
I
know
validators,
have
been
asking
for.
D
C
Me
jump
in
on
on
a
couple
of
those
just
to
expand
on
them
if
any
yeah,
the
the
upgrade
there
are
multiple
way
there
are
multiple
forms
of
upgrade
and
that
contracts
can
opt
into.
Obviously
you
can
send
simply
say
I'm
going
to
make
a
version
2,
that's
a
new
contract
users
can
migrate
over
at
their
Leisure
for
system
level
contracts
or
for
contracts
that
have
you
know
long-lived
service
state
or
what
have
you
being
able
to
upgrade
in
place
or
have
contracts?
C
Opt
into
upgrading
in
place
is
really
valuable,
really
powerful
and,
as
it
turns
out
really
hard,
that's
important
for
the
inter-protocol
contracts,
because
they're
so
integral
to
to
the
operation
of
an
economy
that
being
able
to
upgrade
in
place.
If
there's
you
know
performance
or
scaling
or
security
or
even
new
features
that
that
might
drive
an
upgrade,
is
really
really
valuable,
and
so
the
mechanism
is
a
contract
says
you
know
it.
It
says
what
its
government
governance
is.
C
It's
got,
you
know,
declared
governance
parameters,
and
it
says
what
electorate
you
know,
whether
it's
the
Builder
Dow
or
the
econ
committee,
or
a
contract's
own
electorate
that
can
vote
on
and
determine
what
what
changes
happen
to
param
meters
and
one
of
the
things
that
a
contract
can
say
is
and
I
can
be
upgraded.
If
the
electorate
says,
I
can
be
upgraded
where
the
electorate
would
say:
okay,
we're
going
to
start
a
new
contract.
C
That
is
the
replacement
for
that
old
contract.
The
old
contract
shuts
down
and
all
the
what's
referred
to
as
baggage
all
of
the
the
the
the
the
the
the
State
data
that
is
critical
to
that
original
contract
is
made
available
for
the
new
contract
starting
up,
and
so
a
lot
of
the
abstractions
and
wiring
and
libraries
to
make
that
straightforward
is
what
would
what
have
been
built
in
this
mainnet
1B.
C
It
allows
upgrade
to
new
versions
of
the
contract,
can
trolled
by
the
contract
selected
process
of
governance,
and
that
ladder
is
really
important,
because
this
is,
you
know,
lots
of
support
for
upgrade.
But
it's
not
the
case
that
the
Builder
Dow
that
that
that
build
sneakers
can
upgrade
third-party
contracts.
It's
up
to
the
third
party
contracts.
What
process
of
upgrade
they
want
to
provide
and
the
system
can
have
multiple
multiple
of
these
strategies
nicely
coexist.
So
it's
been
a
lot
of
work
going
into
that
it's
going
to
be.
C
You
know
it's
going
to
be
really
really
powerful,
really
really
big
deal
and
people
have
been
working
on
various
forms
of
how
to
do
upgrade
for
for
years
and
years
and
how
to
do
it
balanced.
With
the
interests
of
you,
know,
stable
immutable
contracts
and
and
and
and
declining
ability
to
change
things
that
people
are
relying
on.
So
you
can
have
you
know
what
it
takes
to
upgrade
go
down
in
the
future.
You
know
or
require
more
unanimity
in
the
future,
all
those
kinds
of
things.
D
I
and
I
was
just
gonna
say
you
know
it
sort
of
speaks
to
also
what
what
inter
protocol
has
done
for
the
Agora
team
in
terms
of
helping
us
pull
features
into
the
platform
and
make
them
available
to
third
parties,
because
we
need
them
right.
You
know:
I,
I've,
I,
work
really
hard
to
avoid
saying
eat
our
own
dog
food,
but
it.
D
C
Instead,
they
can
get
a
snapshot.
That's
not
just
oh
I'm,
going
to
trust
what
that
other
validator
that
I've.
You
know
that
I
kind
of
know,
as
friends
I'm
just
going
to
trust
whatever
code
they
provide
me
or
whatever
chain
State
they
provide
me.
Instead,
they
get
a
a
snapshot
that
that
there
was
consensus
about
that.
Multiple
validators
agreed
that
this
is
a
snapshot
of
the
system
at
the
right
time.
They
can
start
from
that
to
get
a
leg
up
to
to
to
be
able
to.
C
You
know
start
from
the
state
from
only
a
couple
of
days
ago,
replay
forward
and
get
get
a
new
validator
launched
and
running
in
in
much
much
shorter
period
of
time,
and
you
know
as
anyone
who's
started
validators
on
on
chains
that
didn't
have
that
feature.
It
can
take
quite
some
time
for
a
validator
to
catch
up
with
consensus
and
start
participating.
Like
you
know,
days
or
weeks
in
some
cases-
and
you
know
we
know-
we
want
people
to
be
able
to
start
validators
much
more
easily
than
that.
C
You
know
the
fact
that
it
also
helps
with
testing
and
and
reproducibility,
and
that
sort
of
things
is
is
just
gravy.
This
is
this
is
a
key
feature
in
Cosmos
that
one
and
mature
is
available
as
part
of
the
the
agoric
platform.
You
know,
even
though
there's
a
lot
more
state
to
be
encompassed
in
one
of
these
snapshots.
D
So
so
yeah,
so
looking
looking
at
what
we
accomplished
in
March,
a
lot
of
it
was
driving
all
these
efforts
forward.
Obviously,
but
then
a
couple
key
things
also
got
started,
which
was
the
contract
audits,
got
scheduled
and
actually
began.
I
think
that
might
have
technically
been
April,
but
it
was.
It
was
close
to
the
end
of
March,
and
so
so
contract
audits
started
from
an
auditor
that
we've
worked
with
in
the
past
and
have
we.
C
D
We
also
I
I,
think
on
the
last
Community
call
I
mentioned
that
we
were
just
starting
to
test
vaults,
we're
now
at
the
stage
where
I'm,
actually,
when
I'm
off
this
call
I'm
going
to
continue
testing
our
example,
liquidation
tools,
triggering
liquidations
of
those
vaults,
placing
bids
making
sure
everything
is,
is
working
there.
It's
a
liquidation,
testing
is
getting
rolling
and
to
that
end
we
have
an
example:
liquidation
CLI.
D
That
would
let
third
parties
bid
on
vault
liquidations,
and
so,
if
that's
you
or
if
you
are
someone
that
wants
the
opportunity
to
bid
on
liquidations
like
spitting
on
liquidations,
knows
people
that,
like
bidding
on
liquidations,
you
should
please
reach
out
to
us,
because
we'd
love
to
get
feedback
on
does
this
example
tool
make
sense,
is
there
could
we
document
it
better?
Would
you
like
to
run
through
a
few
tests
with
us?
D
So
that's
something
we're
we're,
certainly
interested
in
in
driving
forward
and
you'll
probably
hear
more
from
us
specifically
on
that
over
the
next
over
the
next
several
weeks,
but
just
figured
I'd
mention
it
on
this
call
as
well
and
I
know
I'm
taking
a
lot
of
time
here.
So
let
me
let
me
go
ahead.
Dean.
C
I
was
gonna,
add
and
the
other
thing
part
of
the
reason
we
did
the
command
line.
Is
it's
a
really
nice
illustration,
a
of
being
able
to
do
command
line
back
again
where,
where
you've
got
command
line
tools
that
can
exercise
the
JavaScript
contracts
with
arbitrary
offers
and
all
that
sort
of
thing,
but
also
it
should
be
a
nice
illustration
of
what
it
would
take
to
programmatically
drive
processes
like
liquidation
through
the
the
JavaScript
objects
and
account
objects
and
so
forth.
So
so
so
it's
it's
a
good
Exemplar.
D
In
addition,
if
you're
somebody
or
know
somebody
that
is
interested
in
building
a
UI
for
liquidations,
that's
something
to
reach
out
to
us
about.
Also,
we
sort
of
expect
that
at
launch
liquidation
will
be
driven
through
CLI
or
third-party
Bots,
but
front
end
to
to
drive
liquidation
is
is
certainly
something
that
would
be.
D
It
would
open
it
up
to
a
whole
bunch
of
people
in
the
in
the
ecosystem,
okay
and
then
beyond
that,
we
also
have
done
an
awesome
awesome
Sprint
over
the
last
couple
weeks
on
scalability
and
that's
going
to
be
a
focus
not
only
for
April
but
then
moving
past.
This
mainnet
1B
release
doing
doing
work
to
make
sure
that
the
observability
of
swing
set
is
clear
so
as
as
contracts
execute
in
Vats
and
how
they
interoperate
with
each
other,
how
they
consume
resources.
D
So
that's
been
awesome
and
then
yeah,
post
post
main
net
1B.
It
really
is
all
mainnet2,
so
it's
scalability
product
and
Engineering
have
already
started
reaching
out
to
the
main
two
partners
to
make
sure
that
we're
we're
driving
in
their
requirements
into
the
platform
or
at
least
understanding
how
to
prioritize
them.
D
Why
you
need
to
use
them
and
and
starting
to
go
through
those
processes
too,
so
there's
sort
of
as
usual
a
lot
going
on,
but
that's
been
our
Focus
over
the
you
know
the
previous
month
and
and
what
we're
looking
forward
to
in
April
and
then
obviously
we're
looking
forward
to
a
mainnet
1B
release
as
soon
as
as
soon
as
we're
confident
in
liquidation,
and
we
have
some
internal
targets
for
that
date.
But
I'll
I'll
leave
it
leave
it
unsaid
for
now
so
I'll
turn
it
back
to
Santi.
A
E
Yeah
yeah
so
yeah
a
couple
of
things
from
me.
First,
some
context
for
those
unfamiliar
agoric
is,
of
course,
a
proof
of
stake.
Blockchain
relies
on
a
decentralized
community
of
validators
to
operate
and
secure
the
network
and
in
an
effort
to
support
the
network,
opco
kicked
off
a
delegation
program
in
early
2022
that
had
two
phases
to
it.
E
First
phase
was
to
sort
of
bootstrap
the
agork
Min
support
the
validators,
who
were
there
in
participating
in
the
incentivized
testnet
and
then
phase
two
was
some
additional
delegations
with
a
new
requirement
around
security
standards
such
as
using
TM,
KMS
or
horcrux,
and
so
moving
forward
we're
going
to
be
updating
the
program
requirements.
So
it's
not
just
a
new
round.
E
Like
the
phase
two
was
there's
going
to
be
a
new
questionnaire,
a
new
application
form
going
out
the
requirements
for
this
will
maintain
that
strong
focus
on
secure
infrastructure,
as
we
want
to
support
a
high
performance,
high
quality
validator
set
and
we'll
so
we'll
be
Distributing.
A
new
questionnaire
application
form
in
the
coming
weeks.
So
stay
tuned
for
updates
on
that
in
the
Forum
I'll,
be
posting
I'll,
be
posting
there
and
then
I'll
relay
that
to
Discord
and
hopefully
get
an
announcement
on
Twitter
around
the
same
time.
E
For
those
who
follow
here
and
then,
if
you
have
any
questions,
if
you're
a
validator
listening
in,
feel
free
to
reach
out
to
me
on
Discord,
you
can
find
me
there,
JD,
Lorex,
zero,
triple
seven
and
and
so
yeah
I've
been
working
with
cheat
on
that
and
I'll
just
I'll
just
poke.
If
there's
anything
that
I
may
have
missed
or
anything
you
may
want
to
add
about
the
delegation
program
updates.
E
One
more
to
that
is
again
just
stay
tuned
for
those
updates
in
the
Forum
at
community.org.com
and
on
the
topic
of
the
Forum
I.
Just
wanted
to
also
mention
that
so
notional
recently
became
categoric,
validator
and
right
away
started
a
discussion
about
adding
build
external
incentives
on
osmosis
and
that
topic
led
to
another
discussion
started
by
Red
Rabbit
about
IST
osmo
as
a
possible
superfluid
pool
on
osmosis
and
so
there's
some
there's.
A
little
discussion
started
in
the
Forum
about
that.
E
So
if
anybody
has
opinions
or
if
we
have
thoughts
on
the
matter,
please
join
us.
There
that's
community.org.com
and
would
just
love
to
see
more
feedback
and
to
see
people
start
to
lead
that
discussion
forward
and,
of
course,
agoric
governance
can't
make
that
decision.
But
the
community
can
work
together
and
seek
that
get
the
support
needed
to
bring
that
forward
to
osmosis
governance.
E
A
A
So
if
you're
interested
definitely
Mark
that
they
should
be
sending
a
reminder
out
pretty
soon
I
think
we
will
be
around
nft
NYC,
which
is
April
12th
and
14th,
we're
actually
sponsoring
a
cosmos
Meetup
hosted
by
the
one
and
only
Jeet,
and
that's
on
April
13th.
So
if
you're
in
the
city
around
that
time,
definitely
stop
by
the
registration
link
is,
is
on
Twitter
and
we'll
we'll
be
sharing
that
again,
a
little
closer
to
the
event
as
well.
A
B
A
A
Yeah
yeah
I'm
excited
about
that
one
I
know
we
have
a
few
folks
from
agorkoric
attending
that
so
yeah
very
much
looking
forward
to
to
to
that
student-run
hackathon
and
then
there
is
Cornell
blockchain
conference
on
April
21st
and
probably
one
of
the
larger
events
coming
up,
which
is
consensus
in
Austin.
That's
April
26-28th.
So
if
anyone
is
there,
Dean
will
be
speaking
at
protocol
Village
on
the
28th,
and
there
is
an
IBC
Summit
happening
on
the
20th
as
well,
so
a
bunch
of
stuff.
A
C
Nope
other
than
we're
we're
busy
cranking
away
getting
this
stuff
out
and
really
excited
to
to
bring
it
out
to
the
the
community
in
the
very
near
future,
so
so
and
and
the
extended
Community,
including
the
inter
the
inter
folks,
when
is
the
next
Inter-Community
call
right?
That's
a
that's
a
another
important
question:
that's
a
the
a
a
as
I
said,
our
our
symbiotic
symbiotic
partner
that
drive
that
drives
the
economy.
Yeah.
A
C
A
C
Yeah
and
otherwise
look
for
you
know
otherwise
for
validators
look
for
the
delegation
policy,
as
JD
said
for
discussion,
you
know
graphs
for
discussion
up
in
the
community
in
the
not
too
distant
future
with
with
JD
and
jayton
and
Jesse
and
others
participating
there.
So
we
look
forward
to
seeing
all
of
you
all
for
the
next
round
of
Delegation
and
and
all
of
you
all
in
the
testing
and
rollout
of
the
next
release.