►
From YouTube: zkDatabase ⚡ Community Demo
Description
zkDatabase uses a distributed storage engine that improves the availability of data. It utilizes Zero-Knowledge Proof to ensuring the correctness of data in verifiable manner. With zkDatabase, it's allow developers to focus on developing their ideas, rather than managing the complexities of data storage and management.
A
A
We
go:
okay,
welcome
everybody.
This
is
the
Community
demo
for
ZK
database.
We
have
chiro
who's,
the
founder
of
an
Orochi
Network
here
Cheryl
and
his
team
were
funded
through
ZK
ignite
in
cohort
one
and
the
topic
of
octane
storage
has
been
a
hot
one
for
a
long
time
and
there's
a
few
different
ways
that
you
can
go
about
this.
But
chair
is
going
to
talk
about
the
way
that
he
and
his
team
have
approached
it
for
built-in
CK
apps.
A
C
Yeah
hi
everyone,
I'm
chiro,
founder
of
Rog
Network
and
today
I'm,
going
to
introduce
you
about
GK
database
project,
this
project,
when
I
look
into
the
the
current
problem
of
the
web
tree
and
also
like
zkr,
like
everyone
they're
going
to
who,
who
build
ckr,
they
also
need
to
handle
the
memory
handle.
The
stories
handle
like
everything
regarding
to
the
storage
themselves,
so
I
think
what
what
happened.
C
C
So
we
see
the
bigger
transformation
from
on-chain
data
to
groupable
data,
so
on-chain
data
is
something
the
the
concept
that
put
you
put
everything
on
blockchain,
but
provable
data
is
different.
It
is
you
can
store
the
data
option,
but
then
you
can
prove
the
correctness
on
Smart
contract
on
on
GK
app.
C
So
right
now,
if
you
store
anything
on
blockchain,
it's
very
expensive
and
also
it
will
really
slow
in
a
couple
of
minutes
for
people
to
actually
like
get
the
data
from
the
Oracle
or
they
have
to
trust,
maybe
Oracle
provider
to
fit
the
data
for
their
smart
contract,
but
for
provable
data
or
verifiable
data.
It's
much
more
cheaper
since
it's
store
option
and
it
can
be
verified
very
easy
on
Smart
contract.
C
C
We'll
add
some
awesome
thing,
as
you
see
here,
like
the
zkr
actually
like
execute
on
the
front-end
side,
and
we
have
nothing
to
do
with
back-end
and
the
other
stuff.
So
even
the
smart
contract
it
run
option
and
it
runs
on
the
front-end
side.
So
it
can
it
really.
It
really
has
to
handle
the
data
or
update
the
data
and
synchronize
the
data
between,
like
maybe
the
same
people.
For
example
like
you,
want
to
make
some
sort
of
room
booking
on
on
gkr.
C
You
have
to
find
a
way
to
sing
the
people
together
to
make
the
booking
not
to
be
overlapped
and
I
think
they
are
much
more
stuff
to
be
handled
like
authorization
and
also
encryption
for
data,
but
right
now
the
first
priority.
It
makes
the
database
to
be
much
more
friendly
for
people
to
you
and
also
supports
on
ggap
or
on
Mina
protocol
ecosystem.
C
C
When
we
try
to
build
together
the
bay
project,
we
think
like
what?
What
do
we
need
if
we
are
engineer
or
a
ZK
engineer
or
a
people
who
use
a
one
chat
to
develop,
develop
a
ckr.
So
the
first
thing
we
try
to
make
the
interface
for
the
code
be
very
easy
to
you.
Allow
every
people
to
understand
how
to
write
the
query
by
using
the
odm
to
interact
it
with
the
zika
database
and
also
make
everything
very
clear
for
them
if
they
are
an
engineer,
besides
that,
we
provide
the
graphic
tool.
C
Allow
people
to
manage
the
database
much
more
easier,
I
think
right
now,
like
a
lot
of
people,
they
focus
on
building
circuits
or
building
a
lot
of
fancy
technical
like
technology,
but
then
they
forgot
about
usability
and
I.
Think
it's
also
important
to
help
more
people
and
more
Engineers
to
use
EK
database.
C
C
For
a
long
time
we
always
trust
Oracle
and
and
require
the
data
from
them
and
also
build
some
third
party
they're
going
to
provide
the
data
for
us.
So
no
one
going
to
ask
about
the
data
correctness
of
channeling
or
no
one
actually
asked
about
how
channeling
process
the
data
or
where
the
data
come
from.
There
are
no
way
for
them
to
prove
that,
but
I
I
think
like.
If
we
apply,
you
know
knowledge
proof,
we
can
build
something
really
amazing.
We
can
actually
like
Pro,
prove
everything.
Every
information
of
from
the
database
correct.
C
C
C
So
we
need
the
sampling
process
to
do
the
assembling
on
the
on
on
the
information
to
get
the
data,
and
after
that
we
can
do
the
processing
on
the
data
to
have
a
very
well
stocked
data,
and
then,
after
we
have
the
data,
we
can
do
lookup
on
it
and
also
do
the
update
or
inserts
or
anything.
So
we
need
to
also
prove
everything
from
sampling
to
lookup.
C
C
It
is
a
big
problem
that
people
write
as
ethereum
that
Foundation
like
Focus
right
now.
They
try
to
solve
the
data
availability
by
building
a
new
layer.
That's
allows
the
blockchain,
also
like
smart
contract
to
accept
the
data,
and
people
can
actually
like
pick
put
the
bigger
data
on
the
on
the
data
availability
layer
without
any
concern
about
the
storage
space.
C
C
C
C
And
and
right
now,
we
want
to
focus
on
bring
the
zika
database
as
a
service.
Allow
everyone
to
do
this,
and
because
the
infrastructure
for
web3
right
now
is
not
it's
not
quite
ready
like
we.
We
cannot
build
everything
like
fully
decentralized,
so
serverless
approach
may
be
good
for
this
stage
and
allow
everybody
to
use
the
zika
database
and
also
build
their
product
actually
like
easier
and
also
make
the
CK
app
or
decentralized
application.
Much
more
familiar
with
the
user.
C
C
And
we
also
Focus
to
build
a
provable
data
for
a
multiple
platform.
We
want
to
build
us.
We
want
to
make
sure
that
the
data
for
every
computation
for
every
input
of
maybe
Cairo
program
or
for
the
ZK,
VM
or
ZK
wasn't,
will
be
correct.
So
we
can
actually
build
a
new
kind
of
application
without
any
to
feeding
the
data
for
them
and
I
believe
in
that
future.
C
C
A
C
B
D
D
C
C
E
C
D
C
D
C
I
think
like
when
you
build
something
you
cannot
build
everything
at
one,
but
you
have
to
build
a
software
and
it
will
get
better
day
by
day.
So,
let's
see
right
now,
when
we
talk
about
Diego
knowledge,
proof-
and
you
say
you
may
say
that
they
know
actual
zero
knowledge
proof,
because
right
now
the
zero
knowledge
Pro
they
are
used
as
proof
of
honest
computation
and
there
you
know
GK
in
it,
but
right
now,
people
still
invest
time
to
build
like
very
cool
projects.
B
C
B
Think
there
are
also
some
questions
in
the
chat,
but
I
would
like
to
ask
and
learn
from
your
hero.
If
there
is
any
use
case,
you
can
give
an
example
like
a
good
product
fit
to
use
EK
database.
Any
any
example,
ZK
up
or
application
that
you
see
like,
which
can
use
like
as
a
case
as
a
use
case,
so
that
we
can
understand
better,
like
what
kind
of
scale
of
or
architecture
is
ideal
for
for
a
DK
database.
C
Actually
like
when
I
work
with
like
brainstorming
with
my
people,
we
try
to
make
the
secretary
as
a
generic
database,
so
people
can
help
them
an
idea
in
their
mind
and
they
can
use
the
database
to
maybe
replay
the
centralized
database
and
we
hope
we
can
do
that.
For
example,
like
some
people
come
up
with
ideas,
that's
where
they
want
to
view
like
decentralized
kyc,
for
example,
and
then
they
quantify
a
database
where
the
data
is
stored
on
it
and
also
the
data
is
maybe
encrypted
beside
that.
C
C
Maybe
the
information
about
item
or
the
the
transaction
between
the
player
to
transfer
the
item,
or
even
they
can
use
this
for
to
store
them
to
build,
maybe
Define
project
to
store
data
Define
or
also
do
some
sort
of
like
decentralizing
to
to
to
store
the
audible
on
the
zika
database.
I
think
it's
possible
yeah.
B
C
Here
is
a
question
from
Michael:
how
do
you
handle
transition
in
database,
for
example,
if
today's
topic
content
only
a
counter
that
can
be
increment
by
one
and
not
delete
this?
How
do
you
make
sure
that
the
characters
are
not
deleted
and
there
you
know
situation
where
the
commitment
on
completely
different
database
he
writes,
enduring
update
and
data
transaction.
C
C
So
you
you
have
the
data
and
you
actually,
when
you
want
to
change
something
in
that
data,
you
you're
going
to
generate
one
proof
to
prove
that
to
prove
the
transformation
beside
that
we
build
a
peer-to-peer
Network
to
handle
those
stories
and
also
maybe
it's
built
on
the
exiting
like
like
technology
already
access,
and
then
you
can
actually
like
synchronize
between
the
node
before
you
do
some
sort
of
update
or
you
do
one
transaction
to
transformate.
The
state
of
the
ddk
database
am
I,
am
I
answer
your
question.
F
Not
exactly
because
the
question
is
basically
regarding
how
to
you
guarantee
Integrity
of
your
database,
so
every
database
can
have
some
limitations
and
constraints
and
in
my
example,
there
are
counters
that
can
be
incremented
only
by
one.
So
the
question
when
you
generate
proof
that
is
checked
on
blockchain
during
their
day.
F
How
can
I
make
sure
that
this
proof
not
only
proves
that
there
is
new
database
with
some
miracle
t-root,
but
also
that
transition
from
old
Miracle
tree
to
new
Miracle
tree
made
in
such
a
way
that,
for
example,
only
one
item
has
changed
and
it
was
implemented
only
by
one,
not
by
two,
not
by
three
and
of
course
those
constraints
are
specific
for
every
database.
So
they
can
be
no
like
universe.
So
proof
when
I
did
some
similar
thing
with
ethereum.
Basically,
I
had
to
write
my
Instagram
circuits
for
various
scenarios.
F
Like
aging
item
updating,
item
delete
an
item
I
had
to
write
a
specific
circumcision
for
a
Serial
that
handles
the
situation
and
prove
correct
transition
of
the
miracle
tree
from
All
State
to
New
State.
So
how
you
can
handle
it
or
let
us
to
handle
it,
because
all
constraints
are
different.
Of
course,.
C
F
Not
necessarily
in
the
same
time,
but
they
can
be,
we
can
use
different
scenarios.
Let's
say
that
it's
not
in
the
same
time.
Let's
say
that
it's
so
processing
just
to
make
need
to
make
sure
the
transition
from
one
state
of
the
base
to
another
state
of
dog
base
is
follows
some
rules
to
make
sure
that
we
have
integrity
of
the
data.
For
example,
we
can
say
that
counters
cannot
be
deleted.
F
C
So
we
have
like
distributed
certain
distributed
Network
for
it.
So
when
people
do
update
on
the
database,
we
need
to
make
the
nodes
to
work
to
synchronize
with
each
other
until
like
they
dress
a
state
where
the
data
is
like
take
place
in
the
in
the
database
and
after
that,
every
note
going
to
recompute,
like
the
commitment
for
the
the
GK
database.
F
C
In
in
in
different
time,
we
provide
a
product
that
that
maybe
like
better
and
better
over
the
time,
so
so
right
now,
if
we
invent
into
invest
into
like
make
the
storage
Distributors,
so
we
have
to
trade
up
with
like
we
need
to
wait
to
generate,
like
the
actual
prop
the
actual
proof
for
the
data
transition
later
so
like
we
actually
don't
have
either
the
result
to
build
every
feature.
I
want
at
one.
Okay,.
A
Can
I
just
jump
in
really
quick
Cheerio
as
well?
Yeah
I
think
also
context
is
really
important.
Michael,
that's
a
great
question
and
it's
a
question
that
others
have
as
well
the
the
initial
it's
a
goal
of
this.
The
first
cohort
one
version
of
the
project
was,
if
I'm
understanding
it
correctly
churro.
Please
connect
me
if
I'm
wrong,
but
was
to
provide
an
off-chain
storage
solution
for
zika
app
Builders
yeah,
but.
A
From
the
very
beginning,
more
or
as
like
storage
as
a
service
and
I,
think
one
of
the
bigger
questions
that
multiple
people
have
different
approaches
to
solving.
Is
this
exact
question
of
of
State
transitions,
improving
off
chain
data
and
there's
a
lot
of
discussions
that
are
happening
on
Discord
as
well
and
across
other
teams
where
people
have
different
approaches.
So
I
think
I
mentioned
yesterday.
A
Like
you
know,
the
core,
the
core
team
needs
to
work
on
it
too
and
I'll.
Also.
I
would
also
just
point
you
towards
there's
a
there's:
a
there
is
some
documentation
on
actions
and
reducers
like
the
actions
in
reducing
the
API
for
o1js
that
also
talks
about
how
to
approach
this
strictly
within
Olympics.
That
I
think
jira
is
also
referring
to
so
I
just
want
to
also
yeah
I
just
want
to
kind
of
give
that
context,
and
earlier
tomorrow,
I'll
hold
your
question
as
well.
I
think
like
just.
A
We
want
to
keep
in
mind
that
this
was
just
a
like
only
three
months
out
of
a
much
longer
project
and
the
first
thing
that
we
had
asked
jira
to
deliver.
That
chair
was
was
kind
of
a
the
storage,
the
storage
part
of
it,
not
necessarily
the
the
full
picture
of
a
decentralized
protocol
on
how
to
deal
with
this,
although
that
is
the
that
is
definitely
the
long-term
Vision.
So,
okay,
next
I,
think
there's
one
more
question:
Tara
I'll
turn
it
back
to
you.
C
C
Oh
actually,
like
the
the
question
from
here,
is
I'm
not
entirely
understand.
Could
you
please
explain
the
process
of
updating
the
database
more
clear
when
the
data
you
update
the
the
database
needs
to
generate
a
proof
and
submit
it
to
the
blockchain
okay
as
I
I'm,
going
to
to
share
it
with
about
like
beside
like
doing
implementation.
Our
team
also
document
everything
here
and
you
can
see
here
in
zika
database.
C
They
a
lot
of
new
stuff
in
indicated
away
and
also
in
the
kimchi
as
well
like,
oh
once,
yet
they
actually
like
introduced
the
ability
to
do
accumulation
and
also
composability
so
right
now,
I
think
like
D2
Newton
can
can
be
used
to
make
the
secret
database
much
more
better
applies.
The
ZK
database
can
help
accumulate
a
lot
of
proof
to
send
it
to
the
send
it
to
the
smart
contract
on
chain.
So
you
don't
have
to
repeat
doing
like
generating
proof
for
for
Every
Chain
you
make
to
the
database.
C
Here
another
question
and
currently
GK
playing
the
role
of
helping
the
system
scale
better
due
to
sync
property
rtk,
helping
I
think
like
right
now,
people
focus
on
on
using
ZK
for
to
scale
blockchain
or
to
prove
the
the
correctness
of
computation
and
I
think
it's
much
more
important
than
than
privacy
at
this
stage,
but
in
the
future.
Maybe
when
we
have
like
better
gkp,
we
can
think
about
privacy.
G
C
It
depend
on
on
the
Pro
system
that
you,
you
I,
think
that
I
would
not
facing
the
problem
if
I
use
kimchi
like
the
proof
system
from
o1gs,
because,
like
people
build
the
the
requisition
proof,
snack
recursion
proof
with
the
kimchi
group
system,
so
I
think
I
would
not
facing
any
problem
with
this
and,
for
example,
like
folding
scheme,
you
can
think
about
us.
I
think
folding
scheme
can
actually
like
redo
the
code
to
do
the
accumulation
yeah.
D
A
Again,
thank
you
for
for,
coming
and
and
presenting
on
all
the
the
work
that
you
guys
have
been
doing.
It's
really,
you
know
seeing
it
firsthand
from
behind
the
scenes
as
well,
and
how
much
how
much
you
guys
have
been
hustling.
It's
it's
really
impressive
and
I
think
sets
a
a
great
example
for
the
rest
of
the
community.
A
One
one
question:
I
guess
just
there's
some
there's
people
on
the
call
who
are
just
starting
to
right
now
and
they're
all
for
some
people
building
things
through
ZK
ignite.
Other
people
are
building
things
outside
of
ZK
ignite.
But
what
is
you
know?
Do
you
have
any
advice
for
people
who
are
just
getting
started,
building
their
ZK
apps
either
in
regards
to
storage,
or
just
in
regards
to
things
that
you
learned
over
the
last
few
months
when
you've
gone
deep
in
the
documentation
for
the
first
time.
A
Yeah
I,
so
yesterday
we
had
the
cohort
to
build
phase
kickoff
and
one
of
those
things
that
I
had
said
just
in
regards
to
documentation.
It's
we're
at
that
stage
where
things
are
moving
so
fast
and
there's
now
multiple
teams
working
on
different
things,
that
expected
to
be
a
little
out
of
date,
but
also
expect
that
other
people
are
really
actively
working
on
it.
So
yeah
I
completely
agree
just
for
everyone.
A
Listening
just
keep
asking
keep
yeah
if,
even
if
we
have
some
work
to
do
on
improving
all
the
documentation,
but
in
this
in
this
interim
term,
if
we
can
kind
of
just
create
this
culture
of
sharing,
it
will
be
a
lot
easier
for
everyone
involved
and
starting
right
here.
Carol
like
this
is
really
helpful.
So
thank
you.
Thank
you
for
coming
to
present.
C
Yeah
actually,
like
I,
told
you
my
people,
like
my
team
security
team
to
maybe
like
when,
when
you
see
something
like
maybe
the
example
on
on
the
GitHub
up
like
o1gs,
and
if,
if
you
see
something
like
already
out
there,
you
can
actually
just
create
a
pull
request
and
help
them
to
update
it
the
sample.
So
the
the
other
engineer,
the
other
developers.
They
don't
run
into
the
problem
like
incompatible
between
the
version
and
stuff,
like
that.
C
C
B
Yes,
firstly
thanks
again:
hero
like
for
for
a
presentation.
I
also
want
to
remind
the
crowd
like
you
will
be
one
of
the
mentors.
So
thanks
for
being
mentor.
On
the
other
hand,
we
just
will
announce
yesterday
that
we
will
have
these
study
groups
both
executed
from
the
builders,
but
also
mentors
so
I
already
know
that
there
are
quite
people
here:
I
could
interested
in
off-chain,
storage
or
on-chain
execution
and
somewhere,
like
Rahul
or
other
strike
other
products
too.
B
So,
if
you
love
to
like
start
a
working
group
or
study
group
I
think
it
will
be
really
useful
for
ecosystem
because,
as
we
said,
there
are
different
people
working
on
different
pieces.
But
if
we
start
these
focus
groups,
adding
really
a
lot
efficient
and
you
know
create
knowledge.
Accumulation
yeah
if
you'll
be
interested
in.
C
I
think
I
think
it
will
be
great
yeah
guys
actually
like.
We
also
try
to
build
the
zika
community
in
Vietnam
and
also
like
try
to
maybe
guide
people
very
early
steps
to
generally
proof
so
I
I
really
love
to
work
and
share
my
experience.
When
I
do
research
and
also
stop
with
people
yeah,
it
will
be
cool
yeah.
A
C
A
Oh
sorry,
just
just
a
question
chair
what
what
is,
what
is
the
kind
of
next
steps
that
you
that
you
need
help
with
or
that
you'd
like
to
to
go
forward?
If
you
have
do
you
have
anything
that
you
want
to
share
with
like
in
terms
of
feedback
or
where
people
can
go
to
learn
more
information?
What's
the
best
next
next
next
step.