►
From YouTube: Dan Connolly at ZCash Gardening Club
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
Again,
right
welcome
to
the
latest
episode
of
the
zcash
gardening
club,
it's
december,
7th,
2021
and
so
for
today's
agenda.
We
have
this
welcome
message,
a
few
short
announcements
and
then
we
have
dan
connolly
from
agoric
who's,
going
to
give
a
presentation
on
how
to
develop
smart
contracts.
A
So
I'm
really
excited
for
that
and
then,
as
always
in
the
zcash
gardening
club.
If
anyone
wants
to
raise
their
hand
to
share
about
any
open
source
development,
they're
working
on
related
to
zcash
either
you
know
sharing
a
new
project
idea
or
sharing
an
update
for
a
project
you're
working
on.
A
A
We
also
published
sort
of
a
summary
of
different
kinds
of
market
research
and
economics
research.
We
did
around
zsas
so
that
that
stands
for
zcash
shielded
assets,
and
this
is
the
notion
of
future
protocol
features
that
could
enable
multiple
assets
on
the
zcash
blockchain.
A
So
we've
published
that,
if
you
haven't
noticed
elsewhere,
there
is
a
company
called
cadet
who
has
applied
for
a
large
grant
to
like
carry
forward
development
of
zsas.
So
you
should
check
out
both
their
announcement
and
our
blog
post.
If
that's
something
of
interest
to
you
all
right,
so
our
guest
today
is
dan
connolly,
he's
an
engineer
at
agoric,
and
I
wanted
to
sort
of
describe
a
little
bit
how
I
ended
up
inviting
him
here.
So
agoric
is
a
smart
contract
platform.
A
It's
in
the
cosmos,
ecosystem
and
ecc
is
an
investor
in
agoric
and
I'm
really
excited
about
their
approach
to
smart
contracting.
I
I
am
very
hopeful
for
it
and
because
one
of
the
main
strategic
protocol
goals
at
ecc
on
our
roadmap
is
interoperability.
A
I
thought
it
would
be
interesting
to
hear
about
developing
agorik
smart
contracts
kind
of
at
this
early
phase
of
their
network's
life
cycle,
and
you
know
with
an
eye
of
course.
I
have
an
eye
on
how
that
might
interact
with
zcash
in
the
future,
and
so
I
invited
dan
because
he
was.
B
A
A
B
All
right,
so
you
took
care
of
that
stuff,
and
you
mentioned
that
stuff,
so
I'm
gonna
go
right
into
it
here.
So
these
are.
This
is
a
talk
given
by
kate
sills
in
2019.
B
She
does
really
did
really
great
work
so
a
little
bit
quickly
through
this
offer
safety
partitioning
risk
in
smart
contracts,
so
it's
sort
of
starting
with
the
agorik
special
sauce
in
a
way
there's
a
bunch
of
parts
to
it,
but
I'm
going
to
focus
on
one
layer.
B
So
what's
the
smart
contract,
it's
it's
a
contract-like
arrangement
expressed
in
code
where
the
behavior
of
the
program
expresses
enforces
the
terms
of
the
contract,
so
we
look
at
it
as
pretty
broadly
including
things
like
ebay
and
and
amazon,
and
things
like
that.
Those
are
all
small,
smart
contracts
too.
The
way
we
look
at
it,
okay,
so
a
lot
of
stuff
goes
on
on
blockchains,
with
the
one-time
payment
payments,
a
one-way
payments
right
alice
sends
some
tokens
to
bob,
and
after
that
bob
has
some
tokens,
but
a
lot
of
stuff.
B
B
The
trick
is,
you
know,
alice
gives
10
bucks
to
bob,
and
now
bob's
got
the
widget
and
the
10
bucks
and
he
could
skate,
and
this
has
been
a
problem
for
a
long
time.
Kate
knows
more
about
these
philosophers
than
I
do.
Okay,
so
one
thing
you
can
do
with
this
new
technology
is
alice
and
bob
can
both
give
their
stuff
to
the
smart
contract
and
smart
contract
can
redistribute
the
rights
yay,
okay,
but
and
so
alice
and
bob
never
have
access
to
both
x
and
y.
B
At
the
same
time,
this
is
great
okay.
So
what
if
the
smart
contract
is
buggy
or
malicious.
B
And
this
is
not
a
theoretical
question:
it
happens
a
lot.
I
don't
expect.
I
need
to
go
into
that
in
this
audience.
Zillions
of
dollars
went
away.
Okay,
so
mark
miller
is
our
chief
scientist
and
he
kind
of
had
this
idea.
What
if
we
never
give
the
digital
assets
to
the
smart
contract,
so
the
way
we
partition
the
risk
in
this
zoe
is
the
agoric.
B
Smart
contract
framework
is
there's
two
jobs,
one
is
escrowing
and
redistributing
the
digital
assets
and
the
other
job
is
deciding
how
the
digital
assets
should
be
redistributed.
So
the
escrowing
and
redistributing
is
done
by
zoe,
which
is
this.
You
know,
sort
of
platform
component
and
then
digital
deciding
how
the
assets
should
be
redistributed.
Is
you
know
a
zillion
different
contracts
right
swap
auction
exchange?
We've
got
several
of
them
developed,
we
hope
you'll
develop
more
okay
and
the
way
it's
it's
based
on
these
things,
not
just
sending
stuff
in
a
transaction.
B
It's
based
on
offers
and
an
offer
has
a
want
in
it
and
a
give
it
says
offers
here.
The
current
implementation
is
is
give
so
alice
wants
a
y,
and
she
offers
an
x
and
bob
wants
an
x
and
offers
a
y
feed
these
both
into
zoe
and
you
get
a
match
and
the
rights
get
exchanged,
and
so
there's
this
property
called
offer
safety,
where
both
parties
are
guaranteed.
All
the
parties
are
guaranteed
that
they
either
get
what
they
they
state
they
wanted,
or
they
get
a
refund
of
what
they
offered.
B
Either
get
what
you
wanted,
or
you
get
a
refund
and
there's
no
other
possibility,
so
there's
nothing.
The
smart
contract
could
do
whether
it
has
bugs
or
or
it's
malicious
or
anything,
there's
no
way
to
sort
of
you
know,
rug,
pull
or
anything
like
that
at
the
basic
level.
There's
there's
ways
you
could
do
it.
B
You
know
complicated
ways
on
top,
but
the
basic
framework
means
that,
if
you're
developing
a
smart
contract,
you
don't
have
to
worry
about
accidentally
eating
your
users
funds,
because
the
if
you
have
a
bug
the
the
platform
will
catch
it,
and
if
for
your
user,
you
don't
have
to
worry
about
it.
The
smart
contract
is
going
to
run
away
with
your
money
without
giving
you
what
you
stated
that
you
wanted,
because
the
platform
protects
you
from
that.
B
There's
also
payout
liveness,
you've
heard
of
bugs
where
funds
get
stuck
in
in
things.
Zoe
also
guarantees
that
you
can
get
your
phones
back.
There
are
conditions
in
that
in
some
cases,
but
there's
a
guarantee
there.
Okay
and
then
this
is
just
the
pictures.
So
the
digital
assets
go
back
and
forth
between
the
parties
to
the
contract
and
zoe,
and
then
the
smart
contract
just
sort
of
sends
and
receives
information
from
zoe
and
the
parties.
B
So
you
escrow
your
the
rights
and
then
you
say
something
to
the
smart
contract
and
there's
custom
behavior
and
the
smart
contract
and
the
one
of
the
apis,
for
example,
is
reallocate
it
can
reallocate
x
and
y
between
the
parties
or
it
can
instruct
zoe
to
do
that.
But
it
never
directly
has
access
to
the
to
the
funds,
and
it
can
only
do
the
reallocation
in
ways
that
respect
the
the
offers
that
the
parties
made
and
then
you
complete
offers,
and
then
the
parties
get
their
payouts
there.
B
It
is
in
order
okay
and
that's
the
the
quick
version.
This
is
a
talk,
that's
also
in
our
youtube
channel,
for
when
she
gave
it
originally
that's
the
high-speed
version
of
it.
I
have
a
question.
I
don't.
B
A
Yeah,
if
you
don't
mind
so,
are
there
some
kinds
of
smart
contracts,
or
at
least
maybe
on
ethereum
some
kinds
of
affair
maps
where
the
design
doesn't
quite
fit
into
this
notion
of
offers?
B
Could
be
and
and
the
platform
this
isn't
the
only
way
to
do
things
in
the
platform.
You
can
sort
of
go
around
it
and
do
your
own
way,
but,
for
example,
our
wallet
won't
interact
with
any
apps
that
that
don't
follow
this
pattern,
so
the
wallet
sort
of
protects
all
the
users
in
this
way,
you
could
do
things
another
way,
but
you'd
have
to
get
other
users
to
play
along
with
you.
A
B
But
so
far
we
you
know:
there's
we
haven't
had
too
much
trouble
fitting
things
in
just
as
an
example.
So
we
ibc
is
going
to
come
up
here
and
in
ibc.
You
might
just
want
to
send
some
tokens
from
one
chain
to
another.
You
can
do
that
by
offering
the
tokens
and
having
a
want
of
nothing.
B
So
you
can
do
unilateral
transfers
and
we
have
a
automatic
market
maker
and-
and
you
know,
there's
and
governance,
and
all
this
kind
of
stuff
that
that
fits
into
this
framework
one
way
or
another.
Does
that
answer
the
question.
A
For
me,
my
screen's
kind
of
small,
a
few
font
sizes
larger,
would
be
helpful.
Like
a
couple
yeah.
B
I'm
not
experienced
with
that
appearance
zoom
in
hey.
Look
at
that
how's
that
yeah,
that's
good
okay.
So
this
is
a
hello
world.
Smart
contract
following
the
framework
and
so
a
smart
contract
is
a
javascript
module
and
it
exports
a
start
function
and
we
have
not
just
any
javascript.
We
recommend
it's
hard
hard
in
javascript
and
in
fact
we
enforce
it
in
various
ways,
because
ordinary
javascript
somebody
could
replace
the
array.push
method
and
then
you'd
have
this
very
confusing
world
to
live
in.
So
we.
A
Don't
let
that
happen,
quick
question
for
you,
dan
and
so
in
agorik
you
have
the
secure,
ecma
script
right
and
then
jesse
is
like
a
subset
of
that,
so
this
contract
kind
of
written
in
jesse,
so
to
speak.
B
Yes,
it
is,
in
fact
I
can.
I
can
have
the
tools
check
that
okay,
let's
see
if
I
violated
jesse
anywhere
here,
so
if
I
yeah
so
there's
a
lint
profile
for
jesse-
and
I
happen
to
be-
I
haven't
strayed
outside
of
jesse
here,
okay,
excellent,
so.
B
B
B
You
start
with
the
whole
world
of
messy
javascript
right.
You
take
out
non-static
scoping
things
that
you
know
modern
programming
languages
don't
have
so
you're
in
strict
mode.
You
take
out
some
stuff,
that's
dangerous!
That
I
won't
mention.
Well,
I
mean
object
capability
security.
Is
you
know
what
you
work
on
in
this
cess
realm
here
or
box
if
you're
familiar
with
that?
B
Okay,
so
that
collar
and
collie
or
syntax,
and
things
like
that,
these
are
mostly
globals,
that
you
just
don't
get
when
you're
in
jesse,
there's
var
and
this
they're
also
outside
jesse
and
class
and
super
and
then
proxy
and
realm
and
symbol,
and
things
like
that
and
then
jesse
is
this
subset
of
javascript
that
we
recommend
for
so
that
humans
can
write
smart
contracts.
B
A
B
Yeah,
so
you
know,
if
you're
in
in
the
editor
here
and
you
write,
what's
some
syntax
that
you're
not
supposed
to
use.
I
can't
even
remember
any
because
my
brain
is
trained
this
way
anyway.
You'll
get
red
squigglies
underneath
it
stuff
like
that.
So
you
get
real-time
feedback,
one
of
the
nice
things
about
working
in
the
javascript
world.
B
B
Redefine
a
whatever,
whatever
thomas
just
said,
about
redefining
a
variable,
so
we
have
mutable
variables.
You
can
redefine
variables,
but
you
can't
do
things
like
if
I
try
to
object
assign
now
I
don't.
I
might
go
over
time.
If,
if
I
entertain
all
these
questions
in
line,
I'm
happy
to
do
it.
Sorry.
B
Yeah
see
so
you
don't
want
that
nice.
But
if
I
do
here,
if
I
do
that
and
if
I
oops
yarn
test.
B
It'll
blow
up
cool
can't
do
that,
but
if
I
take
this
out,
if
I
just
run
test.
B
Right
so
we
have
javascript
with
this
fun
little
edges
around
it
and
to
do
it
jesse
sorry
to
do
a
zoe,
smart
contract,
you
export
start
function
and
you're
you're.
It
gets
access
to
something,
but
we're
not
going
to
use
it
in
this
in
this
fun.
In
this
contract,
we're
going
to
have
a
value
that
we
can
change.
That
starts
with
hello
world
and
we're
going
to
have
a
public
facet
which
you
you
give
out
widely.
B
B
So
then
the
the
tests
we
write
them
with
a
thing
called
ava,
which
is
a
reasonably
popular
testing
framework,
and
then
we
customize
it
a
little
bit
and
you
make
is
always
a
fake
zoe
service
for
testing
purposes.
And
then
you
know
you
get
the
value
and
you
test
it
works,
and
then
you
set
set
it
and
then
sure
enough.
That
worked
too.
B
Now
this
little
e
widget
here
it
might
be
a
little
strange,
so
the
the
contracts
and
zoe
and
stuff
operate
in
different
vats
and
vats
are
kind
of
like
iframes
or
something
so
this.
B
This
call
here
goes
between
one
sort
of
event
loop
and
another,
and
what
happens
is
the
method
and
the
arguments
and
stuff
get
serialized
up
and
sent
over
to
zoe
and
come
back
and
it's
done
asynchronously.
So
you
get
a
promise
for
the
result,
so
we
avoid
re-insurancy
hazards
there.
So
that's
how
the
way
the
distributed
computing
works.
B
B
B
Here
we
get
points
for
primes
and
the
way
this
works
is,
if
you
can
guess
the
next
prime
number.
You
get
if
you
guess
the
first
prime
number,
you
get
one
point:
if
you
guess
the
second
prime
number,
you
get
two
points
etcetera,
and
so
I
actually
got
the
prime
generator
out
of
stack
overflow,
but
it
was
written
in
python
and
javascript
doesn't
have
set
default,
so
I
had
to
add
set
default.
This
just
takes
a
map
and
a
key,
and
if
the
map
has
that
key
value,
then
it
returns
it.
B
Otherwise
it
assigns
the
that
key
to
the
default
and
gives
you
back
the
default,
and
so
this
is
just
a
generator
for
prime.
So
actually,
if
I
put
jesse
check
on
top
of
that,
I
think
I
won't
be
able
to
use
generators.
B
Yeah,
so
this
is
rocket
science
a
little
bit
so
work,
you're
kind
of
advised
against
it
because
you
might,
it
might
be
difficult
to
read
the
smart
contract,
but
you
you
can
still
do
it
so
that
generates
primes.
Believe
me:
I've
tested
it
and
everything.
B
So
that's
just
ordinary
javascript
programming
up
there,
and
so
now
we
start
our
contract,
and
so
earlier
we
didn't
make
use
of
this
widget.
That
was
passed
in
and
this
is
our
connection
to
the
zoe
world.
This
is
called
the
zoe
contract
facet,
and
one
of
the
things
you
can
do
is
make
a
mint
so
we're
making
we're
just
making
up
a
new
token.
B
I
think
you
called
them
anyway
erc20
token
and
it's
pretty
similar
and
then
we're
gonna
get
a
thing
called
a
brand
whenever
you
make
a
mint
there's
a
mint
and
an
issue
or
a
brand
and
a
brand
is
sort
of
how
you
recognize
this.
It's
a
little
bit
like
the
contract
address
in
ethereum,
but
it's
just
a
javascript
object
all
right.
So
then
we
got
our
generator
and
when,
when
the
way
the
the
clients
interact
with
contracts
that
make
offers
and
stuff
like
that
is
an
offer.
B
Hander
comes
in
sorry,
we
have
a
public
facet
and
then
the
clients
can
make
an
invitation
which
is
part
of
this
business
of
composable
smart
contracts,
which
I
won't
even
get
into
that's
a
whole
other
thing
you
can,
when
you're
participating
in
a
contract,
you
can
take
your
seat
in
a
contract
and
sell
it
to
somebody,
and
then
you
know
so
that
things
compose
so
they
on
the
public
facet.
B
They
call
make
invitations,
so
they
get
an
invitation
and
then
they
can
make
an
offer
and
when
an
offer
comes
in
with
a
guess,
if
they
got
the
guests
right,
then
we
meant
some
some
tokens
and
give
them
to
them,
and
and
and
we
tell
them
that
they
won.
B
Otherwise
we
say
guess
again
and
if
I
hit
save
it'll
run
the
tests
again,
and
so
we
can
see
that
when
the
guess
was
two
the
guy
won
and
he
got
one
token
and
he
guessed
three
and
the
guy
won
and
he
got
two
tokens
and
then
they
guessed
four
and
nope
that
wasn't
right.
B
So
that
is
a
little
teeny.
It's
like
a
faucet
where
you
have
to
do
a
little
bit
of
computing
to
get
your
to
get
your
money.
So
that's
a
you
know
a
20
or
30
line
smart
contract
and
then
we've
got
auctions
and
and
all
kinds
of
financial
instruments
built
in
so
that
you
can
just
use
them
instead
of
having
to
build
them
yourself,
and
that
is
kind
of
the
short
version
of
all
this
stuff
I
do
have.
B
I
did
study
up
on
ibc,
so
I
can
either
talk
or
answer
questions
about
that,
but
the
the
javascript
smart
contract
stuff,
I'm
kind
of
done
with.
A
Yeah,
thank
you.
There's
a
there's,
a
yeah,
a
couple
questions
nate.
You
see
this
in
the
queue.
Yeah,
okay
and
let
me
start
with
this
one
first,
so
you
said
that
the
idea
behind
zoe
is
avoiding
smart
contracts
owning
the
assets
that
that
are,
the
users
are
interacting
with,
and
so
then
it
lowers
the
risk
if
those
are
hacked
but
isn't.
B
Okay,
yes,
it
zoe
is
very
central
to
the
to
the
whole
thing.
You
know
hacking
zoe
would
be
a
little
bit
like
hacking,
any
of
validators
or
something
yeah
that
it's
a
little
bit
game
over
at
that
point.
So
we're
you
know
having
extensive
security
reviews
and
that
sort
of
thing
with
so
it's
very
much
central
to
the
platform.
A
B
Yes,
when
tokens
come
over
ibc,
they
just
show
up
like
any
other
token
here
that
I
was
playing
around
with
photons,
which
are
from
the
cosmos
test
net,
and
so
I
had
to
fidget
around
a
whole
lot.
But
then
I
had
photons
and
I
had
photons
over
ibc
in
my
purse,
and
I
can
you
know,
send
it
to
smart
contracts
and
make
offers
and
do
all
that
kind
of
stuff.
So
it's
just
an
ordinary
token
in
the
in
the
javascript
framework.
B
Yes,
so
one
of
the
things
you
can
do,
for
example,
is
const,
you
call
zcf
dot,
get
terms
and
you
have
something
like
brands,
and
you
say
so.
This
is
the
oh,
let's
see
the
wages
and
then.
B
So
now
we
have
a
wage
brand
and
if
somebody
cr,
if
somebody
instantiates
this
contract
and
puts
the
rap
zek
as
the
you
can
either
have
issuers
or
you
have
brands
anyway,
if
they,
if
they
fire
up
the
smart
contract
and
give
the
the
exec
issuer
sorry
the
zac
issuer
and
the
zek
brand
here,
then
this
thing
will
traffic
in
zach
it
won't
be
able
to
it,
wouldn't
be
able
to
mint
it
because
the
zek
mint
is,
you
know
I
can't
just
make
that
out
of
nowhere.
A
Cool,
so
the
other
piece
of
the
question
is:
how
does
zek
get
to
a
gork
in
the
first
place
and
there's
no
answer
currently
and
there
are
different
possibilities
but
kind
of
the
most
obvious
one
is
ibc.
Can
you
explain
a
little
bit
about
what
ibc
is
and
how
agora
interacts
with
it.
A
A
B
All
right
so
ibc,
interblockchain
communication
or
ibc
yeah,
so
in
general,
it's
a
way
to
send
just
sort
of
data
packets
between
blockchains
and
the
the
the
they
come
with
sort
of
a
proof
that
they
actually
happened
on
the
on
the
other
block
chain
right.
So
they
come
with
the
markle
proof
or
that
kind
of
thing,
and
so
the
receiving
end.
B
If
it
cares
to
listen
to
that
blockchain
and
you
send
it
a
miracle
proof,
it's
sort
of
compelled
to
accept
that
there
was
such
a
transaction.
You
know
a
packet
emitted
from
the
other
blockchain,
so
that's
the
messaging
layer
and
then
there's
conventions
on
top
of
that
called
ics
20
for
sending
tokens
across.
B
So
I
was
figuring
out
how
this
actually
works,
and
I
made
a
picture
so
there's
you
know
the
cosmos
hub
test
net
and
agorak
dev6,
which
is
you
know.
We
have
an
ordinary,
well
extraordinary,
it's
really
cool
cosmos
blockchain,
but
it's
also
a
cosmos
blockchain.
So
the
regular
cosmos
tools
work
with
it
anyway,
so
agoric
dev
is
over
here.
B
The
atom
is
the
main
net
tokens,
but
on
the
test
net,
it's
folk
on
photons,
so
I
can
send
it
from
one
cosmos
thing
to
an
agoric
thing
and
then
my
relayer
is
listening
on
that
chain
and
then
sending
to
the
agora
chain,
and
then
it
goes
into
some
contract
soup
and
ends
up
in
my
wallet
is
just
an
ordinary
token.
B
Well,
there
is
one
there
is
kind
of
an
important
step
where
these
tokens
can
come
in
from
some
other
chain
or
whatever,
but
am
I
going
to
treat
them
as
work
as
valuable
currency?
So
there's
a
there's,
a
step
in
my
wallet
where
I
say
I'm
going
to
import.
Oh
sorry,
I'm
going
to
import
an
issuer
and
that's
kind
of
the
trust
decision
where
you
say
it's
kind
of
like
grabbing
the
erc20
token
address
and
saying
yeah,
I'm
going
to
actually
accept
that
as
money.
A
Okay
and
when
you
import
you're
pasting,
some
sort
of
like
opaque
blob,
that's
hopefully
cryptographically
authenticated
and
you
so
do
people
rely
on.
This
is
actually
a
general
question
I've
had
about.
Is
it
ics
20
the
the
ibc
standard
for
tokens?
A
What
happens
if
two
tokens
want
the
same
ticker
symbol
like
I
want
to
make
a
new
token
and
call
it
atom.
What
do
wallets
do
so?
My
understanding
of
the
igoric
wallet
is,
I
would
have
to
convince
people
hey,
please
import
my
token.
Here's
this
blob,
I'm
really
trustworthy
by
the
way
it's
called
atom.
A
So
that
makes
sense
to
me.
Do
you
know
if
other
cosmos
wallets
do
a
similar
thing
so.
B
Yeah,
the
the
sort
of
general
solution
in
the
egoric
world
is
called
pet
names.
I
could
talk
about
that
at
length,
but
not
just
now,
but
yeah.
It's
basically.
You
have
to
convince
people
that
that
this
is
an
atom
and
it's
worth
something
and
the
the
convention
in
in
the
ibc
world
follows
to
some
extent
the
convention
from
uniswap,
which
is
basically
there's
token
lists.
B
B
A
Okay,
cool
so
going
back
to
the
diagram,
it
sounded
like
there's
the
ibc
components,
including
the
relayer
and
then
there's
a
special
purpose.
Smart
contract
is
that
pegasus.
B
A
A
Interesting,
okay,
so
one
thought
about
that
is,
it
seems
like
the
ibc
pipeline
lets
users
move
assets
across
and
then
smart
contracts
can
do
stuff
once
it's
over
on
agoric.
Are
there
plans
in
the
future
for
smart
contracts
to
be
able
to
like
more
directly
transfer
to
like
target
destinations
on
another
cosmos,
blockchain.
B
Yeah,
you
can
send
back
as
well.
The
pegasus
supports
sending
back
too.
So
that's
straightforward.
The
other
thing
is
so
that's
token
transfer
back
and
forth.
The
other
thing
that's
kind
of
interesting
is
we
do
this
distributed
object
messaging
and
you
can
do
that
over
ibc,
so
you
could
actually
have
two
agorak
blockchains.
B
A
B
That
is
an
interesting
question.
I
think
our
current
chain-link
technology
doesn't
directly
involve
ibc
nor
divc,
but
that's
a
little
fuzzy,
and
that
would
take
me
another
three
days
to
to
get
all
the
bits
and
pieces
to
exactly
understand
it,
but
yeah.
So
the
the
chain
link
is
a
different
protocol,
and
so
it
it's
sort
of,
I
don't
know
exactly
how
it
integrates.
There
is
a
there
is
a
thing
called
band
protocol
that
that's
a
cosmos
zone
that
speaks
ibc,
but
I
also
don't
have
very
much
experience
with
that.
B
Oh
so
it's
kind
of
specialization
thing
so
ibc
is
this:
general
ship
records
or
ship
bites
around.
You
know
they're,
they
tend
to
be
json
things.
One
of
the
things
you
can
do
with
it
is
is
ics
20,
the
you
know,
token
transfer
standard
and
then
the
rest
of
it
is
dibc
in
a
way.
The
rest
of
it
is
okay.
B
You
just
put
more
javascript
on
the
chain
and
it
does
whatever
the
new
protocol
is
without
upgrading
your
your
you
don't
have
to
take
the
blockchain
down
or
upgrade
it
or
all
kind
of
stuff.
You
just
sort
of
put
more
smart
contracts
out
there.
A
Great
so
yeah
we
still
have
more
questions.
Trickling
in
oh,
the
question
was:
if
you
have
two
agorica
blockchains,
what
does
that
mean.
B
So
it's
not
really
on
our
plans
or
anything
like
that.
Well,
on
the
other
hand,
so
the
the
gorek
company
right
builds
the
software
and
then
our
validator
community
decides
what
to
do
with
it.
So
we
plan
to
so
currently
this.
This
is
our
mainnet,
which
is
only
running
cosmos,
layer,
stuff.
It
doesn't
have
the
javascript
stuff
and
we
expect
at
some
point
there
will
be
a
governance
vote
to
take
the
the
javascript
stuff
and
and
make
it
live
and
stuff.
B
But
if
somebody
else
wanted
to
reproduce
the
whole
system,
you
know
just
do
it
again:
it's
all
open
source,
so
there
could
be
another
one.
The
other
thing
is:
if
you
know
we
got
the
scaling
limits
and
wanted
to
just
do
horizontal
scaling,
just
fire
up
another
zone
and
off
you
go.
A
All
right,
so
the
question-
and
this
may
be
a
couple
levels
below
like
ibc,
that
you
mentioned
governance-
and
I
know
cosmos-
is
a
pretty.
You
know
the
the
design
intent
is
for
to
be
pretty
modular
like
you
can
pull
in
common
modules.
Like
governance,
for
example,
did
did
you
all
use
like
the
the
I
don't
know,
I
hate
to
call
it
off-the-shelf
governance
module,
but
did
you
leverage
the
module
that's
available
in
the
sdk.
B
So
yes,
the
the
our
mainnet
is,
has
the
cosmos
governance
module
in
it,
and
then
we
are
also
building
a
bunch
of
governance
stuff
on
top
of
that,
so
okay
yeah
there's
a
bunch
of
javascript
smart
contracts
and
stuff
that
I
actually
am
pretty
deeply
involved
in
that
kind
of
stuff,
but
unpluggable
governance,
stuff
yeah.
A
Okay,
all
right,
so
you
then,
with
a
module
like
governance,
you
can
kind
of
pull
in
the
base
and
then,
if
there's
some
specifics
for
your
application
blockchain,
you
can
just
add
those
on
top
whatever,
through
whatever
means
is
best.
B
For
you
right
so
yeah,
this
is
cosmos
governance
and
it's
in
its
stake,
weight,
voting
stuff.
So
there's
and
there's
right,
yes
or
no
proposals,
a
lot
kind
of
stuff
and
then
at
the
javascript,
smart
contract
layer.
It's
it's
not
sorry!
It's
not
a
matter
of
building
a
separate
blockchain,
it's
just
a
matter
of
putting
more
contracts
into
the
gorick
economy.
If
you
like
right
and
so
the
the
the
governance
does
things
like.
B
Okay,
we'll
have
a
stake,
weight
vote
to
elect
a
committee
and
then
the
committee
will
be
in
charge
of
the
interest
rate
on
the
amm
and
then
the
committee
can
replace
itself
with
some
other
form
of
governance
and
that
kind
of
thing.
A
A
All
right,
so,
if
like
open
source
hackers
are
on
this
call
or
watch
a
video
later
and
they
were
curious
about
agoric,
how
could
they
get
involved
and
what
areas
do
you
think?
B
B
So
there's
development
and
smart
contracts
and
stuff,
so
that's
definitely
the
way
to
get
involved.
The
we
do
have
some
bounties
posted
so
and
several
of
them
are
cross
chain
bounties.
B
B
The
z
cash
side
has
to
would
have
to
play
the
ibc
game
right
right
at
that
point,
there's
all
kinds
of
fun
things
to
do,
and
I
maybe
I
got
a
question
for
you,
which
is:
if
you
did
some
sort
of
interoperability
protocol,
is
there
any
hope
of
doing
shielded
stuff
across?
I
guess
you
could
do
them
as
nfts.
A
So
yeah,
my
thinking
on
that
is
like
from
my
reflective
strategically.
It
seems
wise
to
just
plug
into
what
works
well
and
so
that
could
be
ibc.
A
And
if
we
did
that,
then
from
the
users
like,
let's
from
the
user's
perspective,
let's
say
they
want
to
participate
in
an
agora
contract
like
an
amm
and
they
have
a
zika
shielded
wallet.
And
so
their
funds
are
sort
of
sitting
in
this
private
store
of
value.
A
Then
they
might
be
able
to
do
an
interaction
with
that
smart
contract
and
in
the
ideal
world.
The
wallet
is
going
to
take
care
of
getting
the
funds
out
of
the
z
cash
shielded
pool
across
ibc.
So
the
value
would
become
revealed,
but
it
would
have
no
history
and
then
that
value
would
show
up
on
that
users
either
like
at
the
contract
in
a
gorick
or
at
that
user's
wallet
in
negoric,
and
then
they
can
interact
and
then
later
they
could
withdraw
kind
of
on
the
reverse
path
back
to
their
private
storage.
A
Making
it
less
distinguishable
from
all
other
users
who
are
doing
the
same
with
their
shielded
zcash
wallets,
so
I
feel,
like
that's
already
a
really
good
step
and
that's
just
plugging
into
existing
something
existing
like
ibc
and
then
research
on,
like
how
to
add
better
privacy
to
bridges
or
smart
contracts
is
definitely
something
I'm
interested
in
longer
term.
B
B
Yeah
one
other
thing
to
mention
in
that
area,
which
is
the
so
the
stuff
I've
been
talking
about.
Is
this
agora
framework
running
on
a
public
blockchain,
but
you
can
run
it
on
a
single
machine
or
or
a
cluster
or
a
consortium
chain,
or
something
like
that?
So
you
can
you
can
do
your
your
smart
contract
stuff.
B
You
know
in
the
privacy
of
your
own,
whatever
it
is,
if
you
choose
so.
A
A
Okay,
I
think
there's
a
new
question
from
thomas
greco.
The
question
is
this
might
be
a
question
for
the
zcash
team.
Would
it
be
possible
to
write
zk
snorks
in
javascript
and
use
that
code
for
enabling
privacy
within
transactions
yeah
my
I'm
sort
of
going
out
on
a
limb
here?
I
think
it
might
be
possible.
It
might
be
not
very
practical,
like
the
the.
A
A
So
in
a
module
could
you
have
a
module
that
was
like
written
in?
Let's
just
say:
russ,
for
example,
that
you
know
leverage
halo
2
to
do
some
sort
of
you
know
proof
verification,
for
example,
and
then
call
that
from
your
javascript
smart
contract,
you
can
kind
of.
B
Not
anytime
soon,
but
these
so
these
vats
sort
of
are
can't
tell
what
the
programming
languages
the
other
vats
are
written
in
in
a.
A
B
So
doing
one
of
them
in
wasm,
for
example,
is,
is
you
know
we
can
imagine
doing
that
and
there's
there
was
a
little
bit
of
prototyping
and
rust
early
on
of
the
actually
the
the
kernel
that
goes
between
them,
not
the
vats
themselves,
but
yeah.
If
you
want
to
play
rocket
science
yeah
these
things
are
are
within
the
realms
of
possibility.
They're,
not
you
know,
straightforward
engineering
by
any
means
right
sure,
yeah.
A
All
right,
thank
you
so
much
dan
for
coming
and
showing
up
to
the
gardening
club
and
sharing
I'm
really
excited
about
this
stuff.
I
think
it's
it's!
It's
really
promising.
I
notice
a
lot
of
little
details
which
I
compare
to
ethereum,
because
that's
I'm
not
super
familiar
with
smart
contracting
and
all
the
different
platforms.
A
A
Thanks
dan
all
right,
so
I
think
that
concludes
this
episode
of
the
zcash
garden
club.
Thanks
for
everyone
for
showing
up
and
asking
great
questions
thanks
for.