►
From YouTube: The Baseline Show: w/ zkPass part 1
Description
On the Baseline Show this week we will host zkPass to learn more about their composable identity protocol leveraging zero knowledge cryptography.
https://zkpass.org/home
Tune in live to participate in the discussion or save for later. Email us at baseline-team@oasis-open.org to join the live audience or be featured on a future show.
Baseline Protocol is an emerging standard for state synchronization across different systems of record. This standard can be applied to traditional corporate systems of record and utilize any kind of database or state machine, including different blockchains or distributed ledger technologies (DLTs).
Join us every Wednesday at noon EST on our live show, 'The Baseline Show'. Each week, we host industry leaders who share their insights and expert opinions on data governance, security, digital supply chain, multi-party workflows and collaboration.
Tune in via YouTube or LinkedIn Live.
#BaselineProtocol #DataManagement #Blockchain #DataSharing #MultiPartyWorkflows #DataGovernance #InformationSecurity #BusinessAutomation #BusinessSynchronization #DataIntegrity #IndustryTrends #LiveShow #LiveStream #LiveDiscussion #ExpertOpinion #YouTube #LinkedInLive #B2BBlockchain #DigitalSupplyChain #Innovation #SupplyChain
A
C
It
takes
about
15
minutes
and
then
we're
gonna
show
you
our
MVP
demo,
which
give
you
a
pretty
straightforward
idea
of
what
we're
trying
to
build
and
then
we'll
start
the
Q
a
from
there.
If
that's,
okay,
yep,
so
us
here
at
ZK
pass,
we
are
trying
to
build
a
composable
identity
protocol,
that's
based
on
multi-party
computation
as
well
as
ZK
approved
technology.
C
So
essentially,
what
we're
trying
to
do
is
to
leverage
zero
knowledge,
a
test
station
from
not
just
web
3
world
but
also
web
to
world,
and
what
does
that
mean
if
I'm
telling
you
guys,
my
name
is
Annie
I'm
over
at
25
years
old,
I'm
of
Australia
nationality,
I
graduated
from
lse
and
I'm,
a
family
member
of
ZK
pass
and
besides
that
I
own
a
Porsche.
Would
you
believe
me?
Maybe?
Yes,
maybe
not
if
you
do
great,
but
if
you
don't
believe
what
I
said,
you
probably
want
to
verify
whether
what
I
said
was
true.
C
And
how
are
we
doing
that
in
the
old
web
2
world,
so
very
likely
in
order
to
prove
that
I'm
Australian
I'm
over
25
years
old
I
need
to
show
you
a
my
possible
bio
page?
I
need
to
submit
a
scanned
copy
of
that,
and
what
that
means
is
want
your
overly
disclosing
your
private
information,
because
you're
essentially
telling
them
not
just
the
fact
that
you're
over
25,
but
exactly
how
old
you
are
and
your
place
of
birth,
your
your
passport,
expiration,
day,
etc,
etc.
C
That's
you
know,
you're
essentially
telling
them
a
lot
more
than
what
they
needed
to
know,
and
not
just
that
once
you
click
that
submit
button,
your
private
data
is
essentially
out
of
your
hand.
It
resides
with
a
centralized
platform
that
needs
to
verify
your
information
or
it's
with
some
other
third-party
kyc
agent
that
they
engage
with
to
verify
your
identity.
C
So
that's
the
problem
we
have
with
the
current
web
2
world
way
of
verifying
and
what
we
think
you
know.
Some
of
the
problem
that
the
web
3
world
has
is
that
we
have
only
limited
data
source
and
you
know,
despite
the
fact
that
we
do
have
a
lot
of
old
chain
data,
but
when
it
comes
to
Identity,
a
lot
of
the
data
still
resides
within
the
web
2
world.
So
hence
we
think
that
you
know
a
lot
of
the
issues
with
web3
kind
of
I
purely
web3.
C
Identity
solution
is
that
they
have
quite
limited
data
source
and
they
can't
really
expand
into
you
know
the
web
2
world
with
a
lot
more
than
you
know,
just
your
own
chain
data
and,
on
the
right
hand,
side.
We
have.
You
know
a
lot
of
the
stats
of
how
many
data
breaches
there
are
each
year
and
how
costly
they
are,
and
we
all
know
that
on
social
platforms
like
LinkedIn
or
you.
C
C
First,
privacy,
preserving
your
personal
data,
should
be
controlled
by
you
and
yourself
only
and
should
only
be
selectively
disclosed
on
a
need
to
know
basis.
Second,
verifiable:
we
have
a
decentralized
zknotes
network
to
make
sure
that
compatibility
right.
This
is
what
we
reckon
sets
us
apart
from
a
lot
of
our
competitors,
and
we
I'll
mention
that
more
in
details,
but
essentially
because
we
redesigned
TLS
and
that
has
enabled
us
to
be
licensed,
free
and
making
us
very
very
compatible.
C
C
A
C
Know
passport
bio
page
and
still
sent
through
you
know
to
to
to
get
verified
and
that'll
likely
work,
but
in
our
way
of
verifying
because
we
are
essentially
getting
the
verification
results
straight
from
the
trustworthy
Tire
source
and
through
multi-party
computation.
We
make
sure
that
the
the
credential
holder
or
the
approval
will
not
be
able
to
tamper
with
that
data
so
just
to
quickly
recap.
Essentially,
you
know
without
solution.
C
Your
data
access
and
the
ZK
approve
are
generated
by
user
themselves
locally
and
we're
licensed
free,
which
makes
us,
which
means
we
don't
need
apis
to
adapt
to
new
data
source,
and
that
makes
us
very,
very
scalable,
so
essentially
the
new.
You
can
see
the
new
kind
of
flow
chart
here
instead
of
me
submitting
that
possible
bio
page.
Essentially,
what
I
need
to
do
is
so
here
in
Australia
we
have
what
we
call
mygov
Australia,
which
is
like
the
government
official
website
that
has
everyone's
digital
ID.
So
essentially,
what
I
need
to
do?
C
The
fact
that
I
am
you
know
of
nationality
Australian,
true
over
25,
true,
and
that
secret
credential
can
then
be
passed
on
to
whatever
business
platform
that
want
you
to
verify
that,
and
here
we
have
two
kind
of
like
simplified
technical
process
flowchart.
It
might
be
very
hard
for
you
to
read,
but
don't
worry
so
the
left
hand
side.
One
is
to
show
you
what
we
did
to
enable
the
multi-party
computation.
So
essentially,
what
we
did
is
we
redesigned
TLS
transport
layer,
security
and
turn
a
two-party
handshake
into
three-party.
C
So,
instead
of
you
know
the
traditional
way
of
me:
user
talking
to
the
website,
mygov
Australia
and
we're
essentially
the
ZK
pass
node
and
myself
bundle
together
talking
to
the
user.
So
you
know
we
log
in
pretty
normal.
The
website's
gonna
return
with
my
data
and
then
with
the
data
that
it
comes
back.
C
C
You
know
around
the
10
seconds
kind
of
level,
and
we
believe
you
know
that's
that's
actually
making
us.
Hopefully,
more
commercially
viable
than
other
Solutions.
That's
gonna,
take
you
know
over
one
minute
for
each
kind
of
like
CK
proof
generation
and
here's
another
example
of,
for
example.
If
today
compound
tells
us
hey
can
any
if
you
can
prove
that
you
have
let's
say
over.
C
So
in
that
case,
what
I
need
to
do
is
I
will
need
to
log
into
my
internet
bank
account,
let's
say
bammo
in
this
case
and
per
normal
right
just
using
my
username
password
and
then
pamel
is
going
to
return
with
up
accounting.
Any
account
balance
x
amount.
So
we
will
need
to
tell
ZK
pass
hey
ZK
pass.
Please
help
me
verify
that
I
have
over
500
000
with
bammal.
C
C
So
why
do
we
call
ourselves
composable?
Because
there
are,
you
know,
multi-dimension
to
one's
identity
from
the
very
basic,
your
legal
identity,
who
you
are,
how
old
you
are
where
you're
from?
What's
your
nationality
to
you
know
your
degree,
verification
I,
graduated
from
LSU
I
would
have
a
lse
alumni
logging
and,
through
that,
I
can
essentially
verify
that
I'm
actually
graduated
from
LLC
your
Dell
membership.
C
C
If
I
wanna
verify
my
my
real
world,
I
said
my
internet
bank
account
balance
without
telling
them
exactly
how
much
I
have
I
will
be
able
to
do
that
so
because
of
the
breadth
of
kind
of
like
the
dinosaurs
that
we
can
adapt
to
which
we
hopefully
want
to
build
the
number
one
application
for
web
3
identity
pass
right.
So
we're
not
really
a
did
project.
C
Obviously,
so,
essentially
anything
that's
web
page
based
if
you
have
a
login,
you
can
prove
that,
and
here
are
a
list
of
used
cases
that
we
will
be
able
to
to
to
adopt
and
from
the
very
basic
and
straightforward
customer
onboarding
ZK
kyc
compliance
to
anti-sibil
attack,
whitelist
distribution,
Solace
distribution,
professional
networking,
credit
score
check,
educational
background
check,
very,
very
high
level
of
user
profiling.
Imagine
you
know
like
a
LinkedIn
or
like
a
dating
app,
where
you
know
whatever
people
say
are
actually
true.
C
You
know
whether,
when
I
say
I
work
for
10
years
at
Microsoft,
it's
actually
true
whether
I
graduated
from
Ivy
Leagues,
it's
true
right
I
will
be
able
to
achieve
very
accurate
and
very
high
level
of
user
profiling.
I
can
specify
I
only
want
to
match,
with
fellow
Ivy
leaks
people
and
Etc
whatever
it
is,
and
here
is
a
quick
chart
of
our
business
model,
but
essentially
we
will
be
able
to
face
not
just
the
business
user
side.
Who
has
verification
needs
right?
It
can
be
a
project
that
goes
okay
pass
team.
C
Can
you
guys
help
me
verify
that
I'll
use?
This
are
not
from
a
certain
jurisdiction,
which
is
actually
a
very
common
verification
needs
for
a
lot
of
the
project
they're
just
like
we.
We
can't
really
deal
with
you
know
like
users
from
American
or
or
China,
or
what
whatever
it
is
right,
and
on
top
of
that
we
can
also
have
individual
users
who
just
wanna,
you
know
mint
kind
of
like
identity
sbts.
C
C
We
are
launching
our
pre-alpha
test,
Nets
these
two
weeks
and
Alpha
test
net
in
Q2,
and
we
will
be
on
magnet,
V1
evm
compatible
in
Q3
and,
oh
actually,
my
teammate
just
prompt
me.
Actually,
our
latest
stats
on
Twitter
followers
is
70k
yeah.
So,
instead
of
45
I
need
to
update
the
slides,
and
here
are
a
quick
intro
of
the
team.
We
actually
got
our
core
team
members
on
the
call
we
got
Bing
he's
our
Tech
lead
and
Josh
he's.
Also
one
of
the
co-founder.
C
We
got
Dr
Sherry,
Shu,
she's
she's,
our
kind
of
research
advisors,
she's,
a
cryptography
expert
she's,
a
lecturer
at
actually
here
here
in
Australia
unsw,
and
also
a
PhD
researcher
from
data
61,
which
is
quite
a
Prestige
Research
Institute
here,
based
in
Australia
as
well.
I
got
myself
Annie
on
a
call,
as
well
as
Ryan
Valerie
from
the
BD
slash
marketing,
side
and
yeah.
Obviously,
you
know
we
have
being
who's
like
ex
senior
engineer
from
NTT,
docomo
and
Josh.
He
also
has
multiple.
C
He
graduated
from
pitched
with
a
PhD
from
University
of
Missouri
and
has
many
years
working,
not
just
in
the
States
but
also
China
and
globally,
and
you
know
quite
a
quite
an
ambitious
slogan,
I
would
say,
but
we
want
to
definitely
bring
more
people.
You
know
more
potential
ZK
users
into
the
space.
I
want
to
be
that
bridge
between
web
2
and
web
pre-World,
which
is
very
important
because
we
think
you
know
the
next
special
projects
that's
going
to
come
through
and
survive
through.
C
The
cycles
are
going
to
be
the
one
that's
trying
to
reach
the
gap
between
web3
and
web
2
world.
So
yeah.
Essentially,
you
know
simply
poo.
We
can
verify
everything
for
not
just
part
three,
but
also
web
2
world.
As
long
as
you
have
a
login
to
a
to
a
portal
to
a
web
page
and
that
will
do
and
yeah
that's
it.
C
Here
it
is
I
definitely
have
way
too
many
windows
open.
Can
you
guys
see
it?
Yes,
okay,
perfect,
okay,
so
essentially,
I'll
just
talk
it
through
as
we
go.
So
essentially
what
you
do.
This
is
the
MVP
version,
so
you
know
don't
mind
the
kind
of
like
simple
interface
and
kind
of
UI,
which
will
be
obviously
optimized
as
we
go
so
essentially
in
this
example:
I
click,
mint
ZK,
SBT
and
then
you're
gonna
come
to
here,
which
you
tell
ZK
pause.
C
Okay,
hey
I
want
to
Mint
a
financial
SBT
from
anz.co.nz,
which
is
actually
the
New
Zealand
ANZ
website,
and
obviously
this
is
how
we
make
sure
that
you're
grabbing
data
from
the
verified
data
source
in
the
first
place,
because
we
will
maintain
a
list
of
you
know
the
verified
data
source,
so
it
can't
be
official
website
or
whatever
it
is.
So
you
know
it's
trustworthy
data
source
from
from
the
beginning
already,
so
we
tell
them
essentially,
I
want
to
verify
that
my
available
balance
is
over
30.
C
C
If
you
log
on
with
your
username
password
per
normal
and
then
that's
gonna,
you
know
come
back
with
your
data,
which
then
we
will
start
the
multi-party
computation
from
here,
and
this
is
quite
a
we're
trying
to
tell
you
what
we're
doing
at
the
back.
So
here
you
see
it's
going
at
already
done
with
the
MPC
part,
and
then
this
is
the
ZK
approved
generation
part
which,
like
I
mentioned
it
takes
us
around
16
seconds
right
now,
and
you
can
see
it's
going
at
40,
46
50
is
is
actually
very
fast
and
voila.
C
C
B
B
C
D
C
D
D
Saying
it's
assigned
right:
are
you
using
the
the
the
signed
by
the
by
the
by
the
public
key
of
the
of
the
cert,
because
otherwise
you
can
you
can
you?
Can
you
can
spoof
the
out
of
everything
right
but
I
mean
I?
Can
I
can
pretend
to
be
Google
right
unless
I've
actually
am
using
I'm
signing
something
with
a
with
a
public
key
that
that
has
been
issued
by
the
Google
ta
right?
Otherwise?
Otherwise,
it's
like
who
cares
right.
E
So
our
approach
is
slightly
different
from
like
at
the
issuer
side.
That's
the
issue
has
a
you
know
the
key
to
sign
it,
but
our
approach
is
more
like
a
TRS
level,
so
it
will
be
number
one.
We
do
not
need
authorization
from
a
data
source
to
in
order
to
for
user
tools
to
issue
the
circulation.
That's
the
major
difference.
You
know
in
the
traditional
way,
let's
say
traditional:
okay,
you
need
a
loads
of
data
thoughts
to
authorize
kind
of,
like
you
are
able
to
use
your
credential
based
on
my
data
source
right.
E
That's
kind
of
an
easy
amount
of
users
in
it.
So
to
get
the
proposal
from
JK
pass
would
be
okay,
users,
Center,
basically,
okay,
user
own
account
on
your
data
source,
so
which
means
that
this
is
a
piece
of
assets
you
have.
So
what
Digger
password
does
is
okay,
we
kind
of
help
with
users
okay
to
to
reach
out
to
their
data
source
without
any
authorization
without
any
API,
without
earning
kind
of
like
a
signature
from
the
data
source.
E
So,
but
we
do
have
a
mechanism
to
to
prove
to
prevent
the
user
from
like
cheating
number
one.
It
could
be
a
fake
data
data
source
of
Google,
as
you
said
right,
but
we
do
have
like
a
template
number
one.
We
have
a
template.
Okay,
we
need
to
audit
it
to
make
sure
okay,
you
are
logging
to
a
real
Google
website
because
number
one
number
two:
would
it
be?
E
Okay,
while
user
is
kind
of
like
a
click
on
the
data
from
the
data
source
it
there
is
a
potential
for
users
to
forge
a
data,
let's
say:
I'm,
I'm,
actually
25
years
old
and
the
data
source,
it's
possible
user,
wants
to
forge
it
back
to
like
18
years
old
at
the
end
right.
So
we
do
have
that's
why
we
have
this
multi-party
computation,
decentralized
system
to
prevent
the
user
from
a
forging
data
data.
So,
okay,
so
number
one.
The
data
source
is
just
worth
it
right.
B
Yeah,
actually
we
we
checked
the
sick
and
just
that
they
did
Sir
certificate
from
the
website
yeah,
because
actually
each
certificate
will
corresponding
to
one
exact
website
and
during
the
handshake
we
will
also
check
the
signature
which
is
sent
by
the
certificate
as
a
private
key
in
the
certificate.
So
we
can
make
sure
that
you
have
exactly
access
the
real
data
source.
B
D
Right,
you're
validating
that
the,
but
still
there's
there's,
there's
your
your
your
your
your
you
should.
Don't
you
verify
that
the
that
they
that
the
that
the
start
that
the
the
signature
is
actually
valid
in
the
zero
knowledge
proof,
because
otherwise,
you
telling
me
that
you
verified
the
signature
doesn't
mean
anything
right.
It's
like
it's
like
I'm
I'm.
Unless
I
have
the
signature
itself,
then
I
can
I
can
verify
that
that
that
the
signature
that
you're
claiming
comes
from
the
website
actually
came
from
the
website.
D
B
It's
not
the
signature
in
in
the
certificate.
The
certificate
will
have
a
private
key,
which
is
belongs
to
the
the
actor.
The
corresponding
data
source
I
mean
the
website,
so
during
the
handshake,
the
website
will
use
this
private
key
to
sign
the
handshake
data.
Let
me
do
it
during
the
TRS
handshake,
so
we
we
just
need
to
check,
because
we
we
have
the
public
key
of
the
certificate,
so
we
can
check
if
the
signature
is
right
or
Not.
D
Yeah
yeah,
that's
clear.
The
point
is:
let's
say:
if
I'm
compound
right:
what's
the
predicate
that
I
need
to
that,
that
I
actually
need
right,
I
need
to
know
that
the
identity
of
the
of
the
user
is
there
right
so
and
that
the
the
that
the
issuer
is
authentic
right
and
that
the
balance
is
over.
Let's
say
500K
right.
D
So
in
order
to
know
whether
the
the
the
the
in
order
to
know
whether
the
the
signature
is
authentic,
right
and
and
that
the
data
actually
came
from
that
from
that
data
source
I
need
to
have
a
I
need
to
verify
the
signature
in
the
circuit,
because
otherwise,
as
compound
I,
like
did
your
node
verify
the
signature
doesn't
mean
anything
right
doesn't
mean
anything.
I
can
verify
that
you've
verified
the
signature.
Unless
the
circuit
verifies
the
signature
and
then
I
can
verify
the
circuit
and
then
I
could
that
I
can
trust.
E
No,
actually,
we
don't
need
this.
This
is
a
different
approach
from
us.
So
what
what
do
we
want
to
use?
How
to
prove
that
this
data
is
from
like
the
the
real
data
source
is
a
is
a
way
we
touch
this
and
the
TLs
level,
just
when
user
log
into
their
account
on
the
data
source.
This
is
we
treat
this.
You
can
say:
okay,
this
is
a
piece
of
electricity.
If
you
want
to
say
that
away.
So,
it's
okay.
E
If
user
able
to
log
into
number
one
I,
I
I,
we
already
made
sure
okay,
this
website
is
trustworthy
right.
It's
a
real
website
of
a
boa.
That's
number
one
number
two,
as
another
user
is
able
to
log
into
their
account
under
Bank
of
America.
We
treat
this
as
a
single
chain
from
the
Bank
of
America
side,
so
this
single
digit
is
done
by
the
TLs
level.
Is
so
that's
why
Bank
of
America
do
not
need
extra
signature
and
the
data
which
use
a
all
out
from
the
data
source
yeah.
D
The
hat
with
a
handshake
that's
signed
right,
you
use,
then
then
you
use
different
Helm
and
key
exchange
to
to
generate
the
the
internal
encryption
key
right.
That's
what
you
do
so
it's
like
it's
like
and
then
you're
you're,
you're,
you're
you're.
The
data
is
return,
but
initially
you
have
that
you
have
the
encryption
by
the
by
the
by
the
key
and
you
have
an
initial
signature.
That's
that's
verified
in
the
initial
handshake.
E
That's
that's
a
credit
so
with
over
the
TRS
level,
it's
okay!
There
is
an
access
token.
So,
when
user
log
into
the
Bank
of
America
website
any
website,
there's
access
a
token
right.
So
the
access
token,
you
can
see
it's
one
type
of
like
a
creating
Shields,
okay,
so
the
server
side,
the
Bank
of
America
server
side,
because
the
database
kind
of
like
a
quick
initial
site.
Okay,
just
pass
it
over
to
verify.
Okay.
This
is
my
user
okay.
Here
she
is
able
to
have
access
to
my
data
source.
E
So
that's
how
you
know
we
are
able
to,
or
user
is
able
to
gather
the
trustworthy
data
from
the
Bank
of
America.
So
in
this
sense,
okay.
So
after
this,
so
this
is
a
TRS
after
the
TRS
level,
okay,
Bank
of
America,
already
authorized
kind
of
this
user
is
able
to
kind
of
get
their
data
source
from
you
know,
Bank
of
America
and
understand
yeah.
That's
that's!
Okay!
So
that's
the
TRS
level
once
the
TRS
level
is
passed.
E
Okay,
we
move
on
onto
the
MPC
multi-party
computation,
like
second
stage,
so
this
stage
is
two
okay,
because
users
now
have
already
authorized
to
get
to
the
data
through
the
login
okay,
so
the
Second
Step
would
be
data.
Potential
user
is
able
to
forge
the
data
now
right.
So
we
do
it.
So
that's
how
we
move
to
the
MPC
modified
computation.
Okay,
we
have
two
keys
and
one
is
incubate
key.
We
another
one
is
the
market.
Key
Market
key
is
okay.
Is
the
data
in
technically?
E
E
D
Now
I'm
I'm
not
saying
that
you
need
to
sign
the
the
their
knowledge
proof.
If
I
am
if
I
am
the
verifier
the
certificate
certificate.
Verifier
right
I
need
to
know
that
that
that
the
that
the
the
site
from
which
the
data
comes
is
authentic,
which
is
the
which
is
the
signature
that
the
site
not
generates
from
the
from
the
over
the
data
that
it's
received.
D
It's
from
the
initial
handshake
right,
where
you're,
where
were
the
the
where
the
side,
the
ANZ
Bank
digital
digital
start,
has
signed
the
initial
handshake
and
you're
verifying
that
it
belongs
to
this
URL?
And
that's
that's
all
you
need,
but
in
order
for
me
as
a
verifier
certificate,
verifier
to
to
trust
right
that
the
circuit
itself
needs
to
verify
the
that
initial
handshake
signature
from
the
digital
start
of
the
of
the
issuer.
If
you
don't
have
that
it's
like
then
I
need
to
trust
your
network.
Why
would
I
trust
your
network
right?
C
What
we're
doing
in
the
first
place
right
so
like
the
first
thing
of
the
essentially
once
we,
you
know
we're
doing
a
three-party
handshake
right.
We,
the
first
thing
we
do
is
obviously
you
know
that's
the
legit
URLs,
and
then
we
check
the
the
the
the
the
the
site
signature
like
being
mentioned,
and
we're
essentially
doing
that
like
very
first
thing
right
before
we
even
yeah,
so
in
so
to
you,
that's
not
enough
or
not.
D
D
C
Yeah,
essentially,
what
how
do
you
trust
it
like?
We
will
be
open
source
and
obviously
everyone
can
audit
it,
and
we
actually
will
have
periodic
audit
of
a
list
of
like
the
trusted
data
source
that
we
maintain,
and
you
know
everything
will
be
open.
You
know,
if
you
want
to
know
whether
are
you
actually
running
a
decentralized
ZK,
node
Network.
B
B
D
Actually,
there
there
is
a
there
is
a
handshake
proof
with
the
signature
from
the
site,
so
the
public
data
consists
of
the
URL
and
the
and
the
public
key
you
know
of
the
of
the
of
the
site.
Besides
the
the
public
key
of
the
of
the
of
the
user
right,
those
are
at
least
three
public
input
sources
that
you
need
for
the
for
the
for
the
snark.
But
if
you
have
that
then
I
can
you
can
verify
the
actual
signature
right
in
the
in
the
in
the
circuit?
D
So
if
you
do
that
right,
then
you
can
you
can
you
can
verify,
then?
Then
you
have
assurances
right
that
there
was
a
signature
and
the
signature
is
correct
right,
because
otherwise
I
need
to
trust
your
network,
that
you
verify
the
signature
right
and
and
and
why
would
I
trust
your
network
right?
It's
like
it's
like
because
of
because
there's
no
truck,
there's
no
traffic
trust
assurances.
D
E
E
E
D
B
E
E
D
E
Okay,
so
here
is
basically
okay,
so
basically
the
whole
kind
of
like
interaction
we
divide
into
like
three
stages:
the
stage
it
would
be,
the
TRS
right.
That's
how
you
know
you
you
get
a
subject
and
then
you!
So
that's
how
you
see
you
get
the
register.
You
choose
the
template,
so
this
is
a
template
that
it's
the
specification.
E
Sorry.
So
this
this
template
is
kind
of
like
what
you
that's
a
compound.
Okay,
what
you
need
to
verify
your
name,
you
need
to
verify
the
get
the
bank
balance.
That's
that's!
What's
in
the
template
right
and
then
you
that's,
you
send
it
over
the
kyc
entrance.
You
get
this.
You,
you
URL
and
then
so
redirect
ticket
pass
and
that's
basically
the
first
step
and
then
what's
happening
here.
I
think!
That's
that's
what
you
are
asking
or
wondering
is
here
so
the
whole
tell
us
how
we
can
flag
it.
The
user.
D
E
Okay,
got
it
so
yeah
number
one
is
okay.
We
we
mentioned
like
we
change
from
traditional,
like
two-party,
TRS,
clients,
client
server,
like
a
user
and
a
server
into
three
party
into
like
a
V
by
saying
three-party.
We
add
this
gig
person
node
as
a
one
part
okay.
So
this
is
a
V
and
the
P
working
ticket
as
a
one
party
and
the
parking
to
the
website
side
as
a
server
right.
So
the
first
step
would
be
okay.
E
They
do
the
the
client
Hollow
into
the
handshake,
send
it
over
the
inquiry
and
then
this
the
website
side.
You
know
responsible
back
with
responsible,
yes
with
the
credentials
right
and
then
once
we
have
the
script,
it
shows
okay,
now
so
the
the
P,
the
user
side
and
the
V
side,
and
they
both
the
generated
this
public
key
and
based
on
the
responses
from
the
server
site.
You
see
you
can
see.
E
You
know
this
pretty
massive
key
and
that
that's
how
it
generates
and
then
what's
this
so
each
V
and
the
pH
both
each
side
generating
their
public
key
and
then
now,
okay,
we
so
step
five,
so
there
will
be
a
combined
the
premaster
key
generated
from
based
on
p
and
v.
So
this
combined
the
key
and
as
a
one
party
talking
to
the
server-side,
that's
and
then
server
server
with
the
server
side.
Okay,
several
several
rate
kind
of
like
recognize
this,
like
a
pretty
master
key.
E
So
that's
how
easy
PMS
would
be
the
pre-master
key
secret.
So
generally
generally,
this
is
a
pre-master
secreted
based
on
the
responses
from
the
server
side
and
then
so
so
this
is
basically
the
whole
TRS
level.
So
that's
how
you
know
the
server
set
is
able
to
recognize-
or
even
you
know,
to
to
recognize
the
the
user
side
from
from
this
certificate,
the
the
certificate
you
know
the
server
issued
all
right
and
then
so
that
that's
the
TRS
once
this
is
over
okay,
so
so
the
the
extension
will
help
to
generate
the
Supreme
master
secret.
E
So
you
can
see.
Okay,
this
the
server
side
create
master
secret
s
is,
would
be
the
premise
of
the
secret
for
the
server
side
and
also
you
know
this
would
be
the
pre-master
secret,
for
you
know
the
prover
side,
the
user
side,
and
also
here,
it's
a
pretty
much
the
secret
for
the
verify
site.
So
that's
how
okay
with
this
Freemason
secret,
we
do
have
like
a
two
keys
over
two
keys
one.
Is
you
see
the
encrypted
key
here?
Second
one?
E
So
while
this
server
has
a
responses,
we
have
two
keys,
the
encrypt
key
and
also
the
market
key
in
group
key
right
and
the
previous
side
has
both
the
keys.
Why
so
encrypt
key
is
to
just
to
encrypt
this
responses
from
the
server
side
correct
and
then
the
Clover
only
has
the
key
the
market
key
and
then,
if
you
take
a
look
at
the
verification,
the
node
only
has
this
Market
key.
E
The
reason
the
node
do
not
have
this
encrypted
key
because
we
do
not
want
to
know
to
have
access
to
them
correct.
You
know
this
is
a
response
to
the
information
right.
That
makes
sense
right.
Okay,
so
now
so
each
party-
and
they
have
this-
you
know
Market
key.
So
at
the
end
of
this,
the
MPC
site,
we
need
to
check
this
h
mark.
We
need
to
check
this
Market
key.
This
is
encrypt.
Okay.
We
need
to
clear
step
nine
step:
nine.
Okay,
we
need
to
check
the
h
mark.
This
is
the
market
key
okay.
E
F
E
And
then
we
have
this
Market
key
here
right,
Market
key,
which
means
okay.
If
if
a
market
key
is
verified,
which
means
the
prover,
the
users
have
to
not
change
this
data.
Okay,
so
that's
a
September
10.,
now
11
side.
Okay,
we
checked
this
Market
key
okay,
we
check
this
Market
key
and
then
so
both
the
party
are
going
to
able
to
verify.
Okay,
did
you
change
the
data
or
not?
So
we
need
to
verify
this
Mark.
E
What
that's
how
it
is
so
once
so,
once
you
check
this
Market
here,
okay,
we
are
able
to
decrypt,
so
the
the
user
side,
the
approval
side
is
able
to
decrypt.
You
know
this
script,
the
information
right.
So
that's
how
basically
that's
how
you
user?
Now,
okay
through
the
TRS,
the
root
You
Know
MP3.
Now,
okay
user
is
able
to
generate
this.
E
So
that
would
be
this
next
step,
which
would
be
because,
okay,
we
now
okay,
we
check
the
market
key.
Now
users
do
not
change
the
data.
So,
okay!
Now
it's
it's
about
the
time
to
generate
the
zkp
now
so
in
terms
of
the
dkp
okay,
even
before
even
the
generating.
So,
over
the
dkp
or
period
we
do
have
just
a
few
constraints.
If
you
look
at
that,
so
that's
these
constraints
are
the
ones,
as
you
mentioned.
E
That's
probably
what
you're
wondering
is
where
is
the
English
here
is
the
kind
of
like
the
singularity
you
mentioned,
okay
over
this
3kp
generation.
We
do
have
this
verification
of
the
constraints
you
see.
The
first
constitution
would
be
okay.
We
need
to
verify
this
encrypted
key.
We
you
see
right.
You
see
that
one
right
encrypt
key,
so
this
this
is
to
make
sure
okay,
this
data
is
came
out
from
Bank
of
America,
and
right
is
encrypt.
Second
one
we
verify
if
the
second
line
is
the
market
key
Market.
E
Okay,
we
need
to
verify
that
the
user
change
this
marketing
or
not.
We
need
to
verify
this
is
the
two
right
and
then,
after
this
both
verified
and
complicated
Market
key
okay.
Now
it's
about
time
to
okay!
This
is
the
asset
asset
which
is
okay,
that's
to
to
make
sure
okay,
this
url
url
is
the
real
URL
we
refer
to
which
this
is
to
prevent
the
user.
E
From
like,
say,
okay,
you
are
logging
into
a
fake
website
whatever,
so
that's
the
way
to
do
it,
and
the
query
is
just
the
template
side
of
the
name,
the
bank
Advantage
right.
Okay,
with
all
this
verified,
now,
okay,
we
generating
the
proof
of
zero
knowledge.
So
that's
that's!
Okay!
You
get
this
proof
and
then
you
transfer
this
approved
to
to
to
the
compound
side.
That's
basically
and
then,
once
you
have
the
CK
manage
generated.
Okay,
compounding
just
verify
the
analogy
through
the
Unchained,
some
other
contract
that
that's
basically,
how
the
whole
flow
yeah.
E
D
B
D
Should
be,
it
should
be.
The
W
is
the
public
input
right,
private
input,
it's
a
private
input
because
it
has
encryption
key
right,
so
X
should
be.
The
X
should
be
the
public
X.
Is
the
public
input
right?
Oh,
okay?
Okay,
all
right
right
now,
I
was
just
wanted
to
make
sure
that
I'm
not
I'm,
not
I'm,
not
dreaming
here,
no,
that
yes,
okay,
so
I
I,
I
I
understand
because
the
commitments
are
are
generated
off
of
the
response
from
the
from
the
website.
E
F
Yeah,
so
just
to
contrast,
your
approach,
it
sounds
like
it's
a
little
bit
similar
to
what
git
coin
passport
is
doing
in
a
sense
where
you
have
this
source
that
you
get
some
data
from,
and
then
you
just
issue
this
credential
that
you
can
check.
In
your
case
it's
a
it's
a
proof
right,
so
you
would
be
maintaining
I
guess
a
set
of
templates
from
various
sources
that
you
trust
you
mentioned
like
a
bank
and
so
on,
and
then
the
person
would
sort
of
self-issue
this.
F
E
Yeah,
so
we
we
basically,
we
do
need
to
maintain
kind
of
like
a
template,
because
the
reason
for
the
template
number
one
would
be
okay.
There
is
that's
why
we
need
to
make
sure
that's
a
trustworthy
website.
You
are
using
that's
number
one
number
two,
the
functioning
of
the
template
would
be
okay.
We
only
want
the
user
to
disclose
the
information
they
want
to
disclose.
E
I
see
the
age.
If
you
go
to
a
bar
okay,
they
only
need
to
verify
you're
18
years
old.
Somehow
you
you
just
support
me.
The
uid
contains
page
name
address
even
color,
whatever
too
much
information
disclosed.
That's
why
we
have
this
template?
Okay,
you
just
need
to
be
very
specific.
What
type
of
information
you
want
to
verify?
No
extra
information
disclosed
yeah,
and
so
that's
kind
of
like
where
you
can
doing
this
with
the
okay,
it's
a
user
Center,
and
also
it's
a
little
and
individual
level.
E
D
D
D
The
initial
computation,
ideally,
you
would
generate
zkp
for
that
which
you
could
and
and
because
you
can,
you
know
the
the
the
private
key
could
be
the
the
private
input
and
then
you
can
you
can
you
can
verify
that
the
that
the
computation
was
done
correctly?
You
can
do
that
and
then
you
recurs,
then
you
then
the
the
the
witness
becomes
becomes
becomes
an
input
into
the
into
the
circuit.
So
you're
you're
you
actually,
then
you
need
a
recursive
circuit,
obviously,
but
it
it
would.
D
It
would
prove
that
because
right
now,
the
the
the
trust
point
right.
Everything
everything
is
trustless,
everything's,
fine,
if
you,
if
you're,
if
you're,
if
you
you
know
because
you
can
verify
that
the
that
that
the
keys
generated
used,
if
you
want
to
go
through
the
troubles
actually
from
the
website
from
the
digital
sort
Etc,
you
can
you
you.
D
The
trust
point
is
then
still
the
multi-party
computation
between
user
and
CK
pass
on
the
on
the
initial
initial
shared
secret
that
you're
that
you're
that
you're
generating
that
is
then
included
into
the
into
the
into
the
as
a
secret
in
the
handshake.
For
the
for
the
between
between
the
between
the
user
and
the
website,.
E
B
F
D
Right
now,
the
trust
point
is
that
decay
path
isn't
cheating
right.
So
it's
it's
the
the
the
the
either
you
have
a
you
know,
so
the
the
the
the
there's
no
collusion
between
the
user
and
DK
pass.
So
ideally,
you
would
have
a
a
a
proof
that
the
computation
right
that
the
that
the
Fiat
shot
me
or
secret
secret
sharing
step
was
done
correctly,
and
then
you
include
that
into
every
other
proof
that
uses
that
initial
shared
Secret
yeah.
D
B
Yes,
so
so
first
I
think
the
all
the
the
node
for
this
task
each
task
they
will
they
will
be
randomly
assigned
during
the
in
the
contract.
So
there
will
be
a
real
possibility
to
assign,
for
some
militias,
I
mean
for
some
other
advertisery
node,
and
also
we
use
and
advertiserable
pro
protocol
here
for
the
MPC
so
which
means
so
if
there
is
one
node
which
is
semionist,
and
this
task
or
or
it
can
be
detected
if
other
nodes
and
they
may
be
advertised
three.
B
A
D
Are
that
are
executing
the
same
code
and
you
can
check
that
that
it
is
done
securely.
You
don't
need
to
you,
don't
need
to
cross
clarify
so
you're
you're,
reducing
your
trust
assumptions
and
that's
really
what
you
want
to
do
right.
You
want
to
you
want
to
to
to
to
minimize
your
your
trust
assumptions,
ideally
to
zero
yeah.
Yes,
that's
true,
anyway,
just
all.
A
Right,
yes,
we're
a
few
minutes
over
time,
but
there's
lots
to
discuss.
Thank
you
for
coming
on
and
sharing
and
showing
and
walking
us
through.
What
you
guys
are
working
on
I
feel
like
we
will
need
a
part
two
in
the
near
future,
because
we
didn't
even
get
to
get
too
far
into
things
like
the
use
cases,
and
you
know
different
partners
or
projects
you're
working
on
at
the
moment
from
those
different
use
cases
that
you
explained.