►
Description
Live at Zcon1: Zero to Privacy Hero - Day 2
Presented by Zcash Foundation in Split, Croatia
A
Where
we've
been
working
on
it
for
many
years
and
our
goal
that
whole
time
has
been
about
moving
the
world's
economy,
all
the
ways
that
people
cooperate
online
onto
the
decentralized
web
in
a
way
that
they
can
cooperate
safely
with
more
people
and
so
the
focus
of
doing
that
or
our
technique
or
our
technology
or
our
approach
for
doing
that
is
enabling
the
millions
of
programmers
out
there
to
be
able
to
build
large-scale
decentralized
systems
and
smart
contracts
safely
and
easily.
So
we
basically
can't
take
over
the
economy
until
all
of
the
programmers
out.
A
There
can
do
this
stuff.
So
we've
built
you
know,
large-scale
payment
systems
have
built,
brokerage
systems
have
built.
You
know
large
scale,
information
systems
and
our
core
members
of
the
JavaScript
committee,
which
is
relevant
because
the
system
that
I'm
going
to
show
you
today
the
systems
that
we're
building
are
in
a
secure
subset
of
JavaScript,
so
that
all
the
you
know,
80%
of
the
programmers
in
the
world
have
a
chance
of
understanding
and
building
it.
A
So,
first,
what's
a
smart
contract
because
that's
an
important
element
and
we
go
and
talk
to
people,
they
have
very
different
ideas,
all
the
time
that
we've
been
doing
this
here's
our
definition,
write
a
contract
like
arrangement
not
of
Inc
contract,
but
a
contract
like
arrangement
expressed
in
code
where
the
behavior
of
the
code
enforces
the
terms
of
the
agreement.
So
this
is,
you
know,
a
work
flow
across
interests,
businesses.
A
You
know
people
that
are
where
the
orchestration
happens
because
of
the
execution
of
software
and
that's
really
valuable,
but
it's
even
been,
and
it
was
really
valuable
thirty
years
ago,
when
these
ideas
were
first
coming
together,
but
it's
even
more
valuable.
When
you
add
blockchain
in
you
know
our
view
of
blockchain,
is
it
basically
introduced
new
machines
built
out
of
agreement
rather
than
out
of
silicon?
A
So
what
that
means
is,
is
you
know
when,
when
aetherium
first
came
out
right,
it
was
a
computer
about
the
power
of
an
old
cell
phone,
but
with
vastly
higher
integrity
right
with
vastly
higher
assurance
of
correct
execution
of
the
program.
Now,
when
the
program
that
you
run
is
one
that
is
enabling
cooperation
and
enforcing
rights
transfer,
that's
something
that
you
really
want
to
run
with
high
integrity.
A
You
really
want
to
be
able
to
directly
trust
its
execution
without
having
to
worry
about
who
happens
to
be
running
it,
and
that's
the
thing
that
that
that
these
computers
built
out
of
agreement
and
spread
across
administrative
and
sovereignity
domains,
that's
the
thing
that
they
enable
so
so
we,
but
our
model
of
doing
smart
contracts
was
about
cryptographic
protocols
between
machines.
So
when
we
added
these
new
kinds
of
machines,
the
model
could
work
in
them
and
stretch
across
them,
and
so
it's
it's.
So
it's
about
being
able
to
build
interoperable
systems.
A
We
have
a
compute
model
that
works
in
a
variety
of
environments
of
these
green
islands,
of
sequential
transactional,
computation,
the
simple
event
loops
of
browsers
are
node
or
or
or
you
know,
we've
seen
the
same
kind
of
implementation
in
c-sharp
and
Java
and
tickle
and
all
sorts
of
languages,
but
they're
connected
with
asynchronous
messaging
sort
of
this
asynchronous
see
of
the
world's
computation.
The
world
does
not
function
in
a
synchronous
fashion.
A
You
know,
activities
are
happening
in
lots
of
different
countries
being
able
to
easily
orchestrate
sending
asynchronous
messages
back
and
forth
enables
larger,
faster,
more
scalable
systems.
We
build
that
into
a
we
build.
We
produce
that
in
on
an
object-oriented
environment
for
programmers
where
they
can
build
simple
objects
using
their
simple,
familiar
programming
techniques
that
can
orchestrate
with
each
other
securely
between
these
different
containers,
which
we
call
vats
by
the
way.
A
So
in
our
system,
that's
in
a
secure
subset
of
JavaScript,
but
there
are
lots
of
systems
that
are
looking
at
using
wasm,
directly
and
other
languages
built
on
top
of
that.
But
it
allows
us
to
do
both
simple
programming
within
these
vats
and
and
then
asynchronous
messaging
for
large-scale
orchestration
above
that
and
finally
sort
of
the
final
layer
of
the
stack
or
maybe
there's
you
know
the
political
layer
and
everything
up
from
there.
But
the
final
layer
of
the
stack
that
we
implement
is
our
contract
layer,
so
the
world
of
software,
the
world
of
building.
A
You
know
fancy
web
pages
or
what
have
you?
Well,
you
know
people
are
used
to
being
able
to
build
that
not
by
starting
from
scratch
each
time,
but
by
being
over
able
to
go
over
to
Stack
Exchange
into
a
search
and
find
out
well
do
I.
Do
a
scrolling
panel
of
pretty
pictures
right
and
I,
don't
have
to
implement
JPEG
and
I.
Don't
have
to
implement
scrolling
panel
I
just
go.
You
know,
learn
this
pick
up
this
component.
A
You
know
place
it
in
my
application
and
I'm
done
and
I
can
go
on
about
building
my
art
auction
or
whatever
it
is
I'm
building.
Well,
we
want
the
same
thing
for
smart
contract
components,
and
so
that's
what
we
provide,
and
so
the
layer
above
this
is
escrow
agents
and
monies
and
and
auctions
and
futures
and
forwards,
and
and
and
all
those
kinds
of
components
that
you'd
like
an
expert
to
get
right
once
and
then
you
reuse
it
to
put
together
your
comparative
advantage
and
enable
your
cooperation
using
these
mechanisms
with
other
people
built.
A
So
that's
what
that's
the
stack
that
we're
building
and
we
have
things
that
we're
doing
across
that
whole
spectrum.
But
I
know
what
you're
thinking,
however,
which
is
where
that
gets
the
coffee,
but
but
but
before
that,
where
does
privacy
show
up
in
here
and
I'm?
Not
gonna
talk
a
lot
about
that,
because
we're
still
early
in
the
implementation
of
this
so
we're
getting
just
to
the
test
net
stage.
But
that's
the
thing
that
is
so
important
in
this
community
is
getting
that.
You
know
that
sounding
board.
A
So
when
I
say
where's
where's
the
privacy
in
here
I'm
gonna
want
that
feedback
over
the
next
year
or
so
of
where
a
place
that
we
can
use
the
magical
technology
of
zero
knowledge
and
put
it
in
here
and
that
sort
of
thing,
but
the
place
where
our
architecture
gives
us
the
ability
to
do
interesting.
Private
things
is
simply
that
it
is
uniform
across
public
chains,
consortium,
private
chains
and
individual
machines.
So
I
can
have
one
of
these
vats
running
contract
components
on
here
talking
to
my
machine
at
home
over
secure
protocols.
A
We'll
we'll
be
wanting
to
in
our
future
roadmaps
start
to
add
other
technologies
like
like
the
stuff
that
we're
seeing
in
the
in
the
much
more
technical
presentations
here.
But
there
is
a
thing
that
comes
up
given
the
where
we're
at,
which
is
where
we
go,
which
is
you
know,
we're
testing
that
stage
so
I'll
be
showing
and
I'll
say
a
little
bit
more
about
that
in
a
moment.
A
But
so
we've
been
going
out
and
talking
to
reference
partners
and
we'll
be
looking
for
people
to
work
with,
whereas
we
finalized
as
we
develop
more
of
the
stack,
we
can
go
out
and
work
with
partners
to
actually
help
them
build
their
application
on
our
system,
and
you
know
sanity
test.
You
never
want
to
do
an
API
without
having
a
real
use
of
it,
because
otherwise
you'll
go
off
in
space
right.
So
so,
when
we're
always
asked
you
know
what
are
the
use
cases,
why
would
I
use
blockchain
instead
of
a
database?
A
You
know
why
do
I
want
to
do
that?
It's
decentralized
thing
all
that
sort
of
stuff,
and
there
was
a
there's,
a
group
of
economists
from
RMIT
University
in
Australia,
and
they
had
a
fabulous,
a
great
description
of
why
that
is,
and
it's
that
blockchain
and
smart
contracts
on
blockchain
differentially
reduce
the
cost
of
trust.
They
make
it
easier
to
establish
new
kinds
of
trust
with
people
that
you
could
not
necessarily
cooperate
with
before
or
that
it
was
very
expensive
to
cooperate
with
before,
or
or
or
those
kinds
of
things
and
by
cost
of
trust.
A
I
mean
all
the
procedures.
All
the
processes
that
you
use
in
order
to
have
a
relationship
do
some
cooperation
and
feel
safe
about
it,
and
so
one
of
the
things
there
that
they
did
not
cover
that
I
will
note
is,
is
significant
areas
of
privacy,
which
is
as
also
important
and
as
I
hear
from
Zuko
and
I'm
sure
lots
of
other
people
also
repeat,
commerce
needs
privacy
too
right
and
so,
but
but
when
they
did
this
study
looking
at,
where
do
people
spend
money?
Where
do
organisations
spend
money?
It
was
a
broad
world
economy
study.
A
A
I
just
know
it
to
be
true,
because
I
can
see
it
in
this
high
integrity.
Ledger
just
that
would
raise
the
global
global
GDP
by
5%
and
increased
world
trade
by
15%.
So
these
are
huge
numbers
as
we
get
this
stuff
out
into
mainstream,
and
so
a
lot
of
Ag
oryx
goal
is
to
get
this
stuff
out
in
the
mainstream.
So
where
are
we
at?
We
started
last
year
just
before
Z
con
zero,
and
so
in
some
sense
we
announced
our.
A
Just
at
the
cosmos
hackathon
yesterday,
finally
put
together,
Aaron
come
on
finally
put
together
the
integration
obsess
into
their
build
structure
so
that
that
applies
generally
so
that
if
you've
got
a
large
JavaScript
project,
you
can
have
our
secure
ACMA
script
wrapped
around
all
your
safe
modules.
No
chance
is
integrating
this.
The
IOT
Standards
Committee
for
JavaScript
TC
53
is
actually
standardizing
on
our
secure
subset
of
JavaScript
as
the
JavaScript
for
for
embedded
devices
and
embedded
systems.
A
So
that's
made
a
lot
of
progress
and
it's
actually
having
a
security
impact
on
the
outer
world
on
the
mainstream
economy
on
web
2.
So
thank
you
for
people
for
helping
us
make
that
happen
so
where
we're
at
today-
and
this
is
sort
of
the
the
the
most
exciting
part
today-
is
we're
now
at
test
net.
So
we've
been
building
our
part
of
that
whole
stack
and
we've
now
got
a
live
test
net
up
on
the
on
the
internet
with
a
few
people
starting
to
poke
at
it.
Now
it's
private.
It's
not!
A
You
know
it's
invite-only
we're
going
to
gradually
growing
this
and,
of
course,
you
know
continually
enhancing
it,
adding
it
making
it
more
accessible,
making
it
more
exposed,
but
all
of
the
code
is
open
source
available
on
our
on
our
github
repository.
We
are
a
testament
where
we
don't.
You
know.
Our
primary
value
is
the
stack
on
up.
So
we
built
our
system
integrating
with
cosmos
SDK
so
using
tender
mint
as
the
consensus
algorithm
underneath
but
again
the
design
is
very
protocol
very
portable
across
different
infrastructures.
A
So,
as
we
go
forward,
possibly
after
we
get
to
main
net
we'll
be
adding
more
and
more
of
these
networks
to
be
able
to
provide
the
same
kind
of
infrastructure,
so
polka
dot,
integrating
as
much
as
we
can
with
Z
cash
and
bit
going
in
aetherium
and
so
forth.
So
what
comes
up
next?
Just
real,
quick,
we're
working
with
the
inter
blockchain
communications
protocol.
Folk
Chris
goes
key
wherever
they
are:
the
cosmos,
a
nice
ICF
folk
and
so
we'll
be
working
on
that
for
Interop
and
our
system.
A
Our
communication
layer,
asynchronous
messaging,
will
rely
on
that
directly,
we'll
use
that
directly
and
then
finally,
these
iteration
of
test
nets
we'll
be
adding
more
and
more
up
towards
the
contract
framework
which
we
have
in
the
current
system.
We
have
a
you
know
early,
you
know
primitive
one.
You
know
0.2
kind
of
version
and
then
finally,
of
course,
we
will
go
to
main
net
and
you
know
when
is
econ
2
since
I'm
sort
of
having
these
yearly.
You
know
I'm
not
promising
when
that
is
yet
ok.
So
what
did
we
build?
Smart
contract
Nano
kernel?
A
So
this
really
does
look
like
a
user
mode
system
mode
separation,
where
we
can
run
our
vats
as
approximately
processes
with
the
kernel
that
are
orchestrating
our
security
model,
our
object
capability,
security
model
underneath
and
enabling
us
to
remote
it
as
well
providing
persistence
and
so
forth.
So
that
provides
that
featherweight
compartments.
The
same
kind
of
thing
that
is
used
in
Salesforce,
we're
using
it
for
contracts
and
it
provides
the
async,
is
messaging
between
them
and
gives
us
replicated
deterministic
approximately
execution
of
the
secure
subset
of
JavaScript.
A
So
we
did
the
chain
integration
with
endermans
and
finally,
our
initial
rights
transfer
protocol.
That's
in
order
to
have
the
test
net
be
a
test
net
of
the
entire
stack
right.
The
goal
is
to
get
in
to
end
everything
working
and
then
you
make
each
of
these
layers
better
or
you
know:
hey
we're
open
source.
Anyone
out
there
that
wants
to
do
UI
framework
for
us.
A
You
know
come
talk
to
me,
so
we
did
our
own
UI
a
little
bit
in
order
to
be
able
to
exercise
and
be
able
to
enjoy
enhancing
the
test
net
over
time
and
give
people
some
pace
to
play.
So
if
you've
ever
seen
the
million
dollar
homepage
where
people
have
abstractions
about
or
party
on
the
pixels,
we
did
something
like
that,
obviously
starting
more
modest,
but
each
round
of
test
it
maybe
will
add
another.
You
know
set
of
pixels
here,
but
the
key
thing
we
did
here
is
each
pixel.
A
A
Call
where
what's
covered
is
the
right
to
some
pixels,
not
a
stock
or
not
a
bond
or
whatever
it's
the
right
to
color
some
pixels,
and
that
means
that
if
pixels
are
randomly
assigned,
I
can
start
to
purchase,
calls
to
try
and
get
together
a
rectangle.
So
I
could
Splatt
up
my
logo
in
a
rectangle
or
something
like
that,
and
then
there's
a
pixel
faucet.
A
So
people
in
the
test
debt
wake
up
not
with
any
money
but
just
with
the
ability
to
buy
some
pixels
and
then
they
can
go,
sell
them
on
the
market
maker
in
order
to
exchange
them.
For
in
this
case
it's
called
pixel
dust.
You
know
so
and
then
of
course
it's
extensible
not
going
to
a
lot
about
how
it
will
work,
but
I'll
actually
just
show
it
here.
A
But
but
but
are
you
I
remember
I
said
we
did
just
enough
is
display
of
the
pixels
and
a
you
know:
read
eval
print
loop,
so
I
can
just
type
JavaScript
expressions
and
since
of
course
we
have
a
secure
subset
of
JavaScript,
I
can
type
anything
I
want
and
I
can't
bring
down
the
any
of
the
system.
But
the
architecture
of
our
provisioning
and
we
have
a
secure
provisioning
thing
that
uses
Brian,
Warner's
magic,
wormhole
interactions
is
that
we
have
a
change.
A
You
can
see
the
chain
over
on
the
left
and
for
each
of
the
users
right
now.
It's
not
you
know
running
connected
directly
to
a
browser,
but
it's
you
run
a
solo
instance.
You
know
our
same
engine
running
on
a
single
machine
and
that's
able
to
do
you
know
relay
style,
ibc
stuff,
to
be
able
to
talk
to
the
server
and
so
I
will
jump
over
to
here's
the
real
version.
You
know
you
can
you
can
see
I've
got
paint.
A
You
know,
I'm
going
to
paint
see
that
blue
pixel
right
up
there
in
the
middle,
yes,
I'm
gonna
go
ahead
and
paint
that
paint
that
red
now
what's
actually
going
on
here
is
it's
sending
a
message
here.
I'm
actually
just
got
the
response
and
you
know
there's
the
whole
bitmap
you
can
see.
You
know
prototype
right
or
early
access,
there's
lots
of
layers
of
JSON
encoding
as
we
go
through
these
various
messaging
stages.
And
here
is
the
response
saying
you
know:
yes,
I've
got
the
answer
and
so
forth.
A
So
this
is
packaging,
a
message
of
sending
it
back
and
forth
the
the
the
test
net
servers
are
currently
deployed
out
on
to
mostly
digital
ocean,
but
I
think
we're
using
multiple
infrastructures
and
they
log
their
their
data
up
into
a
log
server.
So
this
is
I'm
connecting
now
to
one
of
the
log
servers,
but
you
console's
and
the
messages
go
back
and.
A
A
Here's
where
it
whoops
so
here's
where
the
chain
received
that
message,
we
receive
that
message,
tap,
faucet
and
and
of
course
it
goes
into
the
transaction
log.
Now
one
of
the
characteristics
of
all
of
this.
You
know
this
guy's
not
being
helpful.
Let
me
just
terminate
this
here.
That's
the
that's
the
solo
that
so
all
of
the
chain
nodes
all
of
the
solo
vats.
I
can,
just
you
know,
restart
it
and
I.
Don't
need
to
pull
it
again,
but
I
can
just
restart
the
solo
VAT
and
again,
all
of
these
layers.
A
Every
element
is
persistent,
so
the
basic
function,
the
basic
expression
of
smart
contracts,
is
now
it's
doing,
quick
replay
to
establish
the
state
of
the
transactions
all
along
and
this
browser
now
is
I
didn't
show
it
before
as
being
disconnected
so
this
browser
you
can
see,
it
knows
its
WebSocket
is
down.
It
knows
it's
disconnected.
It
knows
it
can't
do
anything
if
I
now
just
restart
my
restart
the
service.
This
is
my
my
solo
that
that's
talking
to
the
chain,
but
it's
got
persistent
state
of
what
it's
a
valley.
A
Whichever
pixel,
that
is,
history
12,
is
that
what
that
is,
yep
and
I
can
color
it
too
they're
all
used,
zebra,
cuz,
that's
showing
up
and
and
it'll
take.
It
will
send
the
message
you
know
here
that
then
is
encoded
broadcast
to
the
to
the
tender
mint
chain.
It
comes
into
the
tenorman
chain
here
which
writes
it
out
into
the
log
so
that
that
can
be
replayed
when
we
start
new
nodes.
A
That
then
does
the
processing
of
the
transaction,
whether
it's
trading
or
selling
or
coloring,
pixels
or
what-have-you
sends
the
results
back
by
writing
it
into
the
blockchain
into
the
transaction
record.
The
relay
service
then
scrapes
that
out
inside
of
the
solo
that
is
watching
those
events
pulls
it
out
and
will
end
up
when
it
sees
that
block
confirmed.
A
A
That's
because
I'm
I
will
that's
because
I
killed
in
the
middle
of
a
message:
I'll
I'll
talk
about
area
all
right,
so
so
I
could
have.
A
page
of
I
can
have
a
page
of
of
caveats,
of
course,
since
this
is
a
early
version,
but
that
particular
bug
just
showed
up
three
days
ago
and
I
have
no
idea.
What's
going,
there's
you
know,
Kate
knows
what's
going
on,
but
but
but
I'm
several
thousand
miles
away
from
it.
A
So
so
so
I
said,
don't
change
anything
because
I
know
what
I
know,
because
I
know
what
will
work
so
we
will
be
rolling
out
new
versions
on
a
regular
basis.
You
know
in
a
couple
of
days
that'll
go
away,
and
then
we
will
have
versions
that
start
to
be
available.
Where
people
can,
you
know,
pull
requests,
you
can
do
your
own
contracts
and
we'll
deploy
them
building.
A
You
know
games
or
applications
that
can
grab
multiple
of
these
pixels
in
order
to
be
able
to
in
order
to
be
able
to
do
interesting,
abstractions
or
patterns,
or
what
have
you
and
and
then
gradually
making
it
available.
So
you
can
dynamically
deploy
new
contracts
in
the
network
and
you
know
token
models
and
all
that
sort
of
stuff.
So
so
that's
what
we
have
it
is
now
operational.
A
You
can
go
to
our
tests
net
sites
in
order
to
put
in
your
information
so
that,
as
we
start
to
add
people
or
make
it
accessible,
it's
easy
to
contact
you
and
get
you
connected
in
and
and
we
look
forward
to
seeing
what
you
guys
build
with
it.
We
look
forward
to
hearing
your
recommendations,
always
on
which
things
we
should
add
first
or
which
things
you
would
like
to
see
and
use
in
the
framework.
So
thank
you
very
much
and
I've
got
a
few
minutes
for
questions.
A
A
And
coffees
right
outside,
so
if
no
one's
awake,
that's!
Okay!
All
right!
Thank
you!
For
your
time.
Hi
Arielle,
hello,
Dean!
You
said
something
about
determinism
and
then
gave
a
caveat.
Is
that
because
it
fails,
stop
determinism
or
is
there
a
different
caveat?
Oh
no!
No!
It's
actually
quite
deterministic
and
the
goal
will
be
full
determinism
with
with
detailed
specifications
about
that
we're
written
closely
with
the
embedded
systems
group.
That
cares
a
lot
more
about
that
than
the
than
the
normal
JavaScript
standards
group,
and
so
the
kind
of
non
determinism
is
is.
A
A
From
the
point
of
view
of
programmers,
it
would
look
identical,
so
the
question
is,
since
he
was
in
the
mic,
was
that
example
was
on
a
single
blockchain.
What
would
it
look
like
to
do
a
cross
chain
system?
Many
of
the
elements
of
the
protocol
we
have
there.
It
worked
cross
chain
and
our
original
prototype
worked
worked
cross
chain
from
programmers
point
of
view.
It
would
look
identical
in
this
particular
case.