►
From YouTube: Presentation from Hyperledger HyperHack 2020
Description
HyperHack 2020 was a hackathon organized by the Hyperledger India Chapter in February 2020. This video features presentations from hackathon finalists. For more details about the event, see the page at:
https://wiki.hyperledger.org/display/CP/Hackathon+Feb+2020
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
A
A
A
B
D
D
D
D
D
B
C
B
B
B
B
Needs
to
report
it
to
regulator
in
a
what
we
called
a
yellow
card
adverse
event.
This
is
quite
serious
and
it's
a
legal
mechanism.
We
need
to
pay
them,
I'm,
asleep,
I
click
by
collecting
the
patient
data
using
private
data
collection
and
then,
when
a
patient
sees
the
doctor,
the
doctor
can
be
added
to
the
patient
channel
and
it
will
be
synchronized
with
the
patient
data
and
then
the
patient.
And
then
the
doctor
can
use
a
cross
channel
chain
code
to
copy
the
data
from
the
patient
cannibal
to
the
medical
channel.
B
C
B
So
the
institution's
regulator-
voice
of
them,
the
shipping
agent
pharmacy
and
the
doctor
with
office
clinic
pharmacy
shop,
so
they
have
the
financial
incentives
and
the
money
to
actually
run
it.
The
patient
would
be
a
patient
advocacy
group
or
some
other
data
management
system.
The
patient
doesn't
actually
manage
any
of
this.
It's
a
black
box
to
them.
This
is
a
web
app
on
a
mobile
phone,
so
the.
B
C
C
H
Hi
everyone-
this
is
CD
reconciliate
team
and
I-
have
Prakash
and
her
ship
with
me.
So
this
is
basically
about
the
application.
What
we
have
come
up
to
reconcile
this
ideas,
so
this
is
the
application.
What
it
looks
like
so
here
the
when
the
operator
logs
in
he
would
be
able
to
see
his
contract
with
an
agreement,
so
this
agreement
would
basically
have
a
kind
of
a
bonding
agreement
with
a
partner
B.
H
So
you
can
see
that
there
is
a
mapping
from
A
to
B,
so
a
and
B
both
being
partner,
and
there
is
an
agreement
with
the
ID
agreement
1:01,
and
you
would
see
all
the
summarized
version
of
the
CDR
here
and
in
the
agreement.
Basically,
you
can
see
the
rates
and
everything
for
the
services
being
offered.
You
click
on
any
of
the
load
information
I.
Can
you
would
see
that
particular
CDR
in
detail?
H
Then
we
have
an
option
of
listing
all
the
CDR
in
detail
and
then
we
we
do
also
have
a
functionality
of
basically
reconciling
two
CDs
from
different
operators
and
joining
it
to
a
single
CBR.
So
coming
back
to
the
infrastructure
an
end.
So
here
you
can
see
like
we
basically
have
two
instances
of
GCP
wherein
we
have
fabric
setup
and
we
have
employed
for
Kafka
here,
the
three
orders
and
CouchDB
and
similarly
like
on
GCP
2.
That's
the
second
instance.
We
have
cows
DB
and
the
pr
node.
H
H
Yeah,
you
can
see
when
you
contract
getting
created
so
same
way
like
we
ever
given
the
functionality
of
adding
an
agreement,
contract
and
basically
batch
load
of
CDR,
so
you
can
see
like
we
have
basically
have
quite
used
number
of
syria's
in
our
system.
Basically,
these
are
all
the
testator.
We
have
come
up
to
be.
I
H
So
as
like,
as
we
depicted
in
our
PPT,
we
kind
of
over
committed
ourselves
before
we
started
in
it,
and
so
we
were
able
to
do
the
loading
of
contracts,
every
man's
loading
of
CDRs,
we're
able
to
agree
through
the
partners
and
then
like
load
of
CDRs,
and
we
were
kind
of
able
to
get
a
chain
code
rule.
It
says
that
okay,
our
unified
Syria,
can
be
populated
based
on
related
CVS
comparison.
H
C
H
Yeah
so
we
have
a
field
called
call
ID,
which
we
are
checking
along
with
the
a
number
and
B
number
that
is
source
and
destination
number,
and
that
we
are
basically
fetching
data
from
some
relevant
fields
from
both
the
syria's
and
then
formulating
into
a
unified
Syria.
So
we
have
a
caller
ID,
basically
that
that
is
kind.
H
I
H
C
J
I
C
H
C
H
F
H
Because
I
design
says
that
basically
operator
a
and
operator
B
are
like
generally
what
happens,
they
would
reconcile
from
their
their
own
and
with
basically
a
prone
to
lot
of
mal
practices
and
errors
right.
So
once
the
reconciliation
is
done,
the
unified
Syria,
what
we
say
is
basically
treating
it
as
a
single
source
of
truth,
which
is
non
temp
variable
which
cannot
be
altered,
should
be
cryptographically
secured,
so
that
information
definitely
needs
to
be
on
same
and
then
based
on
that,
then
vison
should
have
so.
C
H
So
idea
behind
the
bulk
upload
is
generally.
What
happens
is
the
CDs
would
be
like
what
we
are
whatever
we
have
read
about
in
the
blocks
and
all
CDs
I
generally
uploaded
in
a
frame
of
24
days
or
like
there
are
some
time
frames,
so
we
are
kind
of
assuming
that
okay,
this
would
be
uploaded
every
day
only
once
from
both
the
parties
and
then
there
the
reconciliation
activity
should
happen
only
once
like
so.
C
H
Because
because
you're
unified
CDR
is
ultimately
getting
reconciled,
based
on
the
data,
what
you
are
getting
from
the
individual
CDs
from
the
operators
who
you
would
have
your
own
rules,
which
would
actually
check
based
on
the
call
ID
that
are
there
any
discrepancies
in
terms
of
pricing
and,
let's
say,
call
duration
or
any
any
call
status.
Like
short
termination
like
assuming
that,
if
the
operator
a
has
is
saying
that
okay,
it
has
been
short
terminated,
but
still
you
you
are
seeing
this
area
operator
be
for
the
same
quality.
Definitely
that
that
is.
H
L
L
So
I
am
today
joined
by
my
team,
Ravi
and
Shweta,
so
we
all
work
together.
This
week
we
bring
the
solution
to
life,
so
hi
everyone
a
very
good
morning,
thanks
for
providing
us
the
opportunity
to
participate
in
the
hyper
hyper
t20
finals
for
this
hackathon,
we
have
chosen
to
help
solve
the
problem
of
the
fitting
of
luxury
goods.
It
is
a
major
pain
area
for
manufactures
sellers
insurance
and
financial
across
the
globe.
L
It
has
some
direct
and
indirect
impacts
for
a
brand,
such
as
loss
of
revenue,
damage,
took
product
and
brand
reputation,
unwarranted
product
warranty
and
liability
claims.
It
is
pegged
at
one
point
eight:
two
billion
dollars
of
revenue
leakage
this
year
for
enterprises,
but
now
blockchain
presents
a
unique
in
genuine
approach
to
tackle
the
problem
of
counterfeiting.
We
will
showcase
that
luxury
good
starter
as
we
named.
It
is
a
viable
solution
for
tackling
counterfeiting.
L
Let
me
give
you
a
level
zero
view
of
the
solution,
so
we
manufacturers
are
moving
goods
to
dealers
to
retailers
and
retailers
who
are
selling
them
to
customers.
We
also
have
insurance
and
financials
into
the
mix,
because,
for
those
you
know,
insurance
for
in
you
know
ensuring
the
luxury,
goods
and
financials
for
financing
them.
So
they
are
luxury
goods
and
they
definitely
need
financing
at
times.
So
we
have
ensured
that
each
of
these
persona
has
lot
to
gain
from
this
solution,
including
that
they
are
all
working
on
an
authentic
good.
L
Every
transaction
here
is
getting
recorded
on
a
shared
blocks
in
ledger,
powered
by
hyper
laser
fabric
in
terms
of
nodes,
while
each
of
them
bring
their
own
own
into
the
network
manufacturer,
will
provision
will
have
to
provision
a
node
to
be
shared
by
its
customers
or
a
high
net
worth
individual
may
choose
to
bring
their
own
node
into
the
network.
We
will
be
creating
channels
for
each
different
product
from
each
different
manufacturer.
L
Thus,
the
ledger
is
only
shared
between
the
permission,
students
who
are
actually
you
know
interested
in
it
and
who
are
actually
working
on
it.
The
main
characteristics,
cryptographically,
secure,
identity
of
the
owners,
association,
verification
using
zero
knowledge
proof,
secured
ownership
transfer
by
using
secret
keys,
even.
A
L
L
L
L
L
Will
allow
us
zero
knowledge
proof
now
an
insurer
will
connect
to
its
node
and
choose
to
void
insurance
and,
for
some
reason,
or
probably
a
financial
may
choose
to
close
a
mortgage.
So
he
can
do
that
using
this
and
now
the
important
aspect
will
be
that
customer.
Can
you
know
customer
can
choose
you
know
to
log
in.
You
will
connect
to
manufacturer
node
and
he
will
you
know
he
can
perform
all
those
actions
and
cannot
be.
You
know,
identify
directly.
L
You
will
key
in
the
necessary
details
and
the
keys
and
the
new
customer
details
and
a
new
set
of
keys
are
generated
which
allowed
him
for
the
new
owner
and
at
last
let
me
show
case
you
zero
knowledge
proof
using
the
verification
phase,
so
he'll
put
in
key
in
the
verification
phase
without
divulging
his
own
details.
He's
done,
you
know,
he's
verified
that
he
owns.
Thank.
C
C
F
L
So
for
that
what
we
could
do
is
there
are,
you
know,
multiple
ways,
one.
You
know
we
could
have
a
unique
ID.
You
know
like
I
gyd.
Otherwise,
you
know
if
incremental
ID,
but
you
know
in
both
ways
can
work.
So
you
can
have
a
smart
contract.
You
know
which
only
you
know,
takes
care
of
deleting
those
unique
IDs.
Now.
A
F
L
L
So,
for
that,
what
we
did
is
you
know
we
came
up
with
a
solution
to
use
in
your
random
keywords
as
the
keys
and
no
so
we
are
using
the
keyed
hash.
You
know
message
authentication
code
and
you
know
we
are
using
five
hundred.
You
know
twelve
bits
of
sharp.
You
know
to
generate
hash
using
the
key
and
an
input
freeze,
so
key
and
the
input
sense
both
together
combined.
You
know,
form
of.
L
C
L
Forth,
so
it
is
only
in
the
wallet
to
ensure
that
you
know
if
I
wanted
to
diverse
details,
he
could
still
do
that
without
actually,
you
know
divulging
his
own
details.
So
what
we
did
is
you
know
we
provided
him
with
a
set
of
keys.
One
set
of
key
will
ensure
we
know
if
she
can
prove
that
you
know
he
knows
that
he
knows
he
has
the
input
phrase
and
he
that
means
he
is
associated
with
this.
L
C
L
C
But
how
are
you
generating
I
mean
creating
this
ownership
keys
so
unless
and
until
you
generate
of
these
keys
from
some
very
Hardware
valid
I,
don't
think
this
might
be
much
sicker
right.
So,
if
still
you
are
creating
these
keys
from
from
a
software
perspective,
this
keys
could
go
out
of
control
from
the
customer
right.
So
someone
else
could
claim
the
ownership
ee
if
they
want
yeah.
L
L
A
M
A
M
Just
to
prove
myself
that
I'm
gonna
come
back
and
I
will
be
presenting
the
solution
for
reconciliation
issue
so
for
the
solution,
I
have
used
a
hyper
ledger
fabric
framework
and
chain
code.
I
am
going
to
write,
I,
have
it
in
node.js
and
continuous
attack
of
a
database.
Okay.
So
in
this
solution,
both
operators
will
be
there
and
they
will
have
endorsed
it
with
a
meteor
and
execute
right
now,
I
have
used
to
peers.
Only
one
will
be
like
test.
M
We
are
enjoined
or
separate
both
and
another
will
act
as
a
committing
fear
for
both
organizations
and
then
it
with
the
private
channel.
Now
both
the
parties
will
send
the
CDR
file
to
the
channel,
where
the
smart
contract
will
run.
No.
These
both
operators
are
in
different
time
zone
right,
so,
in
short,
that
length
of
CD
at
file
is
processed
first
it
both
the
CIA
reports,
are
on
the
same
time
frame
so
that
consolidation
can
correctly
okay,
so
it
is
going
to
be
the
best
processing.
M
M
So
before
that
office,
let
me
show
you
how
the
reconciliation
looks
like.
So
this
is
it's
all
in
the
CLI
right
now,
but
we
can
enhance
it
to
be
shown
on
UI
or
maybe
in
some
log
file.
So
this
is
like
just
what
kind
of
frame
the
recon
solution
didn't
happen,
so
it
is
showing
that
okay,
the
CTS
matched
they
are
in
equal
incoming
and
outgoing
everything
is
equal
for
225.
We
do
see
that
there
is
some
mismatch.
M
The
total
counter
is
$1.99
for
a,
but
for
people
you
only
receive
34,
so
that
has
been
highlighted
and
for
228
it's
still
zero.
I.
Don't
disagree
just
ensure
that
cast
it
is
still
0,
so
this
is
0,
so
I
am
going
to
insert
the
records
for
them
and
now
so
so.
These
are
the
two
are
CDA
files
that
are
having
for
both
operator
a
and
operator
B.
M
F
G
M
M
M
M
M
M
M
C
C
C
N
N
N
Coming
to
the
problem
statement
in
the
existing
system
dispute
settlement
is
a
long
and
time
taking
process
which
is
blocking
the
revenue
of
the
operators
for
months
to
year.
To
address
this
problem,
we
came
up
with
a
solution
based
on
blockchain
for
storing
call
records
for
faster
settlement.
A
solution
also
preserve
privacy
of
individual
call
records.
N
N
The
initial
step
is
the
setup
phase.
In
this
phase.
Each
operator
creates
SS,
private
and
public
people
and
has
a
fiber
data
collection
with
the
other
collaborator
operator.
Sensitive
data,
such
as
call
details,
are
stored
on
PI
with
data
collection.
There
are
the
proof
details,
hashes
are
told
on
the
blockchain.
N
After
the
setup
phase
is
done,
the
reconciliation
is
done
for
the
time
interval.
L
ll
may
be
a
day
for
a
week.
As
you
can
see,
the
exile
value
is
the
aggregated
call,
duration
for
time
interval
L.
Similarly
for
operator
2,
it
is
by
Ike
L
for
this
aggregated
call,
duration,
authenticators
are
computed
and
each
operator
submits
the
transaction
proposal
with
a
call
record,
its
hashes
and
its
Authenticator.
N
After
this
step
is
done,
we
do
the
billing
settlement
for
a
deed,
a
cycle
at
the
end
of
30
day
cycle.
A
proof
is
computed
for
that
cycle.
Using
these
aggregated
call,
durations
and
Authenticator.
These
proofs
are
stored
on
the
blockchain
teacher,
X
accessible
to
all
and
call
records
are
stored
privately
on
the
private
data
collection.
As
a
next
step,
the
these
are
constructed
Merkle
tree
on
each
peer
using
the
X
IKEA
land
vehicle
as
a
pair
of
leaf.
This
novel
tree
has
the
auditors
in
case
of
dispute.
N
After
the
proof
generation
is
done,
we
go
with
the
verification
step,
verify
it
retrieves
the
required
information
from
the
blockchain
and
runs
the
verification
algorithm.
If
the
verification
succeed,
the
settlement
step
is
done
and
if
it
fails,
the
data
with
the
data
residing
with
the
auditor,
a
root
hash
is
computed
and
to
see
which
record
is
mismatching.
G
Yeah
I,
initially
we
created
a
puc
network
of
our
ecology
with
four
operators,
where
all
four
operators
will
share
common
public
database
and
between
the
two
up
between
the
participating
operators
like
operator,
1
and
operator.
Today
we
are
creating
his
private
data
collections,
which
we
are
going
to
store,
call
durations,
call
durations
in
the
separate
database.
So
for
each
of
the
participating
operators
we
are
have.
We
have
created
four
different
of
private
color
private
data
collections.
Harika,
you
can
start
the
video
yeah.
N
N
G
Yeah,
ok,
now,
before
submitting
the
aggregated
call,
durations
I
am
just
coring
the
blockchain.
Now
we
are
submitting
aggregated
call
duration
for
a
time
interval
of
seven
days
in
the
POC.
We
are
doing
the
settlement
process
for
a
first
seven
days.
Time
interval.
Now
you
can
see
seven
aggregated
call
durations
for
operator,
one
alright.
C
F
N
Yeah,
so
the
data
privacy
comes
in,
so
we
have
so
each
operator
has
aggregated
call
duration
right.
So
these
these
call
durations
should
not
be
shared
with
others.
So
these
these
durations
are
stored
on
a
private
data
collections
which
are
accessible
only
to
those
operators
that
are
involved
in
the
consensus
process.
So
other
details,
such
as
the
authenticators,
are
stored
publicly
because
they
can't
retrieve
anything
from
the
Authenticator.
They
are
just
proves
that
the
aggregated
call
durations
are
computed
correctly
and.
G
N
N
N
G
Are
sending
aggregated
call
duration
for
a
cycle
of
D
days
to
the
BLS
here
I
mean
to
the
pairing
based
librarian.
We
are
generating
the
proof
we
are
giving.
We
are
storing
this
proof
into
the
blockchain
and
the
auditor,
while
verifying
the
profiler
will
reveal
that
I
mean
auditor
will
get
that
trip.
N
G
G
N
A
C
G
Actually,
we
have
created
a
wrapper,
like
clients
are
client-server
architecture.
We
had
BBC,
we
are
making
use
of
Stanford
BBC
library,
with
all
these
functionalities
and
from
the
train
code.
We
are
calling
this
server
PPC
server,
which
is
running
on
the
host,
or
we
can
run
this
PPC
server
on
some
central
repository.
Also,
as
of
now,
we
are
running
this
BBC
server
inside
each
here.
Each
operator
knows
from
the
train
code.
The
call
will
go
to
the
BBC
server
from
there.
It
will
generate
the
proof.
C
C
C
J
E
E
Yeah
finally
yeah,
so
our
idea
is
basically
an
ecosystem
of
applications.
It
starts
with
a
web
browser
it.
We
are
supposed
to
make
into
a
module
that
can
be
deployed
in
the
backend
as
well,
so
what
this
module
will
be
calling
itself
sovereign
for
now,
what
it
basically
does
it
once
you
install
it
on
your
browser,
it
generates
a
public
key
pair
and
public/private
key
pair
on
your
account.
It
creates
a
password
also
and
gives
you
that
password,
which
is
not
stored
on
the
ecosystem
anywhere.
E
E
Sorry,
one
second,
what
this
extension
basically
will
do
is
it
will
any
any
see
now
once
it
was
installed.
It
gives
me
the
fall
this
key,
which
is
going
to
be
my
password
for
this
ecosystem,
complete
ecosystem,
one
password
that
I
have
to
remember,
and
it's
not
stored
anywhere
now
after
this,
what
happens
with
any
requests
that
we
make,
for
example,
we
go
to
facebook.com
what
this
app.
What
this
extension
will
do
is
this
extension
intercepts
the
request
to
facebook.com
it
redirects
the
request
to
a
blockchain
ecosystem.
E
In
this
scenario,
right
now,
we
just
have
an
application
to
show.
We
do
have
a
blockchain
ecosystem
of
our
own,
but
we
haven't
implemented
this
egg
connected
this
extension
with
the
the
existing
launch,
an
ecosystem.
What
we'll
do
is
this
will
redirect
the
request
to
blockchain
ecosystem,
where
this
requests
are
written
down
and
any
application.
For
example,
if
it's
Facebook
Facebook
will
need
to
create
a
application
on
this
back-end
on
this
block
chain,
a
chain
port
which
will
map
these
API
calls.
E
For
example,
if
I
just
did
facebook.com,
it
should
do
an
authentication
call
and
that's
what
Facebook
has
to
take
care
of
in
the
chain
code.
Now
why
we
are
doing
this
is
because
every
request,
once
it
gets
logged
on
to
a
public
system
and
the
requested
body,
the
secret,
is
that
requested
body
is
encrypted
now
any
application
that
needs
access
to
that
requested
body
needs
to
request
the
user
for
that
data.
E
For
example,
if
I
have
to
use
Facebook
I
can
go
use,
Facebook
Facebook
has
a
chain
put,
it
will
keep
redirecting,
but
everything
that
I
do
will
be
encrypted
using
a
secret
password
that,
if
I
share
with
Facebook
Facebook
will
have
access
if
I
share
it
with
Google
Google
will
also
have
access.
So
it's
like
a
public
ledger
of
all
the
activity
that
I
am
doing
on
the
Internet.
Now
this
is
not
relay
this
does
not.
This
is
not
bound
by
any
sort
of
identity
for
me.
E
So
what
we
have
done,
we
have
gone
ahead
and
done
is
that
we've
created
a
separate
platform
which
is
actually
running.
It's
called
identity
on
a
skills
chain
platform.
I'll
show
you
in
a
different
browser,
so
this
connection
part
is
something
that
I
could
wasn't
able
to
finish.
I've
been
like
sick
for
last
three
days
but
yeah.
The
basic
idea
is
this:
only
now,
based
on
incentives,
I
can
ask
user
to
map
their
public
key,
which
is
shown
here
in
this
QR
code,
to
an
actual
account,
maybe
to
an
identity.
E
E
That
does
a
lot
more
and
now
about
requests.
I
can
show
you
like
any
request
that
is
generated
on
the
platform
or
any
data
that
is
encrypted
is
stored
on
a
ipfs
and
can
only
be
viewed
after
using
that
password,
for
example,
I
uploaded
my
degree,
for
example,
onto
the
network.
It
was
stored
on
the
public
law
chain,
but
it
can
be
stored
encrypted
using
this
password
and
I
can
be
in
this
case,
for
testing
I
uploaded
my
fan
card,
but
yeah.
The
idea
is
that
yeah,
so
that's
pretty
much
idea.
C
E
So
we
are
building
self
see.
The
idea
of
self
sovereign
identity
is
that
you
can
do
anything
on
the
network
without
the
network.
Knowing
who
exactly
you
you,
you
are.
You
declare
your
identity
now,
what
I'm
showing
you
here
with
this
identity
application?
This
is
something
else.
It's
something
built
on
top
of
that
ecosystem.
It
will
reward
user
to
create
identity
like
connect
their
real
world
identity
to
to
this
crypto
identity.
This
this.
E
We've
been
building
this
for,
like
three
years
now,
actually
I've
been
playing
around
with
this
idea.
I
want
it
to
be
essentially
very
simple
now
this
crypto
extension
that
I
appeal
can
also
be
used
for
very
simple
authentication.
Using
digital
signatures,
like
a
login
request,
is
sent
to
a
back-end.
E
E
Business
we
haven't
thought
about
to
be
honest.
For
example,
different
applications
can
have
different
business
models
in
this
case
in
case
of
identity,
for
example,
it
so
it's
directly
1500
per
per
user,
because
it's
a
verification
thing
for
the
blockchain
itself.
We
have
type
5%
transaction
fees
like,
for
example.
This
is
an
application
that
we
made,
for
example,
Facebook
registers
with
us,
then
for
every
transaction
fees
like
pay
payment
wise,
where,
for
example,
user
opens
up
his
data
to
let's
say
or
Google
a
Facebook
data
to
Google,
for
which
he
is
rewarded.
Of
that
reward.
E
J
C
C
E
Will
tell
you,
for
example,
so
the
things
in
this
picture
are
essentially
a
user
and
application
correct
and
our
blockchain
ecosystem.
So
in
this
case
we'll
consider,
for
example,
in
your
case,
suppose
an
application
maybe
wants
my
data
or
an
individual
person
wants
my
DM.
All
the
things
are
possible
right.
So.
E
For
that,
what
we
essentially
do
is
we
have
called
something
called
access
requests.
If
you
can
see
here,
a
person
can
send
access
requests
or
receive
access
requests.
This
is
a
request
protocol
that
we
have
integrated
in
the
background.
What
it
does
it?
Basically
it
so
each
item
has
a
unique
key
which
encrypts
it
and
that
unique
key
is
only
shared
with
every
user.
Each
time
a
request
is
made
now,
incentives
have
to
be
provided
so
that
this
does
not
lead
out
of
the
system
and,
of
course,
that's
where
game
theory
comes
into.
C
E
C
E
We
are
exploring
the
cryptographic
part,
there's
a
cryptographic.
Research
of
course
involved
in
that
and
there's
one
algorithm.
I
forgot,
the
name,
for
god
sake,
I,
don't
know,
but
in
which
it
like
keys,
can
be
shared
with
thousand
users,
also
with
much
ease,
and
we
have
made
our
modules
crypto
modules,
very,
very
modular,
so
it
can
be
replaced
later.
We,
of
course
we
have
to
think
about.
That
is
one
issue
you
what
you
pointed
out.
That's
a
big
big
issue
and
we
are
thinking
about
it.
C
J
C
To
be
a
commercial
solution,
I
would
advise
you
to
things.
Follow
this:
don't
roll
your
own
crypto
in
your
own
signatures
and
signing
schemes
and
stuff
like
that,
follow
the
standard
protocol
and
build
your
value-add
application
on
this.
The
way
this
is
structured
today
is
not
going
to
fly,
because
you
are
very,
very
divergent
from
the
standard
and
all
the
other
theory
questions.
Have
you
know
kind
of
some
of
the
challenges
that
you
have,
including
the
last
you
remember
was
asking
the
question
sure
sure
just
look
at
the
redesign
of
this
alright.
E
A
M
K
K
K
K
K
K
K
E
K
C
J
J
C
Record
so
this
is
the
normal
thing
in
the
and
see
there
is
one
will
ask
you:
it
has
partnered
with
our
other
two
company.
Now
you
can
see
the
records,
the
record
that
is
saved
from
our
end
agreement
with
them
and
the
billing.
So
in
the
building
we
will
have
the
record
set
by.
Let's
say
what
at
one
table
Center
this
record,
that
we
have
safe
and
we'll
match
them
and
we
will
build
them
and
there
will
be
in
this
of
speeded.
N
O
C
C
A
C
C
K
K
K
K
K
K
O
C
C
C
A
C
F
O
Right
I
will
start
with
an
architecture
over,
and
so,
if
you
look
at
the
problem,
it's
on
this
area,
different
selection,
we
have
to
carry
a
scary
and
it
themselves.
No,
we
want
that.
You
start
with
problem,
but
and-
and
we
have
a
cycle
at
the
fabric,
so
so
I
think
this
should
be
sad
but
dude
if
I
do
it
in
my
school
and
so
with
that
being
said,
I
am
NOT
going
to
go
with
the
architecture.
That's
that's
me.
That's
me,
eccentric,
contrary
so,
and
it's
and
just
want.
O
Is
unique
the
way
we
differentiate
our
simple
order
plates?
So
if
you
look
at
the
grout
in
statement,
it
said
like
nearly
eighteen
thousand
and
ten
thousand
three
years
are
being
shared
between
our
fingers.
It's
not
feasible
for
you
clue
all
the
data
into
blockchain
right.
So
what
we?
What
we
do,
this
length
we
are
using
our
else
are,
is
something
that
is
going
to
which
whatever
is
referring
for
smart
contact
and
then
right,
instead
of
loading
all
the
assets
to
Block
C
right.
O
O
That
is
the
link
like
why
I
could
go
and
find
them,
and-
and
yet
these
number
four
and
five
I
am
already
probable
and
just
to
keep
it
off
easy
to
instance.
We
are
writing
it
and
I
mean
we
are.
We
are
using
it
to
small
instance
for
demo
purpose
and
we
have.
We
have
not
distributed
the
public
with
different
arts
using
create,
but
we
are
just
using
one.
O
O
There
you
go
so
if
you
look
at
this,
this
is
something
that
got
loaded
today
on
the
left.
Is
you
say
we
need
the
Syria,
the
Syrian
format
we
shared.
This
is
been
listed
here.
If
you
go
and
look,
what
are
all
the
attributes
that
we
are
using
in
the
dashboard
can
be
referred
from
this
line.
Okay,
we
are
using
call
number,
you
know
the
subscriber
is
receiver,
call
number
of
the
call
number
and
then
start
time,
end
time,
call
type
and
then
charge
Andy
called
results,
so
these
are
all
the
important
attributes
of
Syria.
O
When
we
investigated,
we
thought
to
load
only
these
things
if
you
into
the
demo,
so
so
this
is,
these
are
all
you
know-
are
operated
by
smart
contracts.
Okay,
if
you
look
at
this,
we
have
we
have
something
called
as
a
bad
job.
So
if
you
look
at
the
architecture,
this
is
I
am
doing
it
from
operator
tape.
Okay,
so
operator,
VA
has
got
two
shadows
operated,
be
exchange
AP.
O
O
O
C
O
C
O
D
O
C
I
So
that
that
willing
to
see
they're
going
to
come
up
with
the
dispute
changes,
but
you
know
our
place,
so
what
are
they
going
to
be
every
day?
They
agree
anyway,
transfer
via
CBS,
but
in
operator
care
system,
I
offer
to
people
in
state
they're
going
to
expose
all
the
serious.
This
is
going
to
be
pulled
quite
our
case,
so
when
they
do
the
data
size
is
a
given
number
of
auxin
indicating
we
we
created
section.
I
That
is
one
validation
and
each
record
will
be
validated
into
small
conference
to
go
the
opposite
way
and
after
to
be
an
acceptance
and
then
never
be
finding
dispute.
That's
going
to
be
no,
he
said
until
the
in
annually,
so
everything
is
going
to
be
copied
into
other
database
system
found
the
on
launching
their
business.
This
is
what
is
going
to
happen
when
both
the
people
having
to
share
their
Gideon's,
so
the
smaller
guys
is
going
to
make
us
by
reducing.
O
Yeah,
so
we
have
certain
rules
like
you
know:
Colleen
I
win
when
one
of
the
circuit
or
tower
goes
down
right.
These
are
all
defeated,
filtering
criteria,
VM
instances
just
give
mock.
You
know,
colleague,
you
have
called
number
three
is
the
person
who
is
trying
to
call
your
number
now
if
this
is
not
empty
and
you
are
being
charged
which
is
not
work,
which
is
not
a
valid
scenario.
Eight,
we
just
flag
that
immediately
in
the
real
time.