►
Description
Money 20 20 Europe 2017 Day 3 Track 1 10 00 The role of open source software in blockchain
A
Chello,
like
Explorer
and
creator,
and
then
we
have
also
working
groups
where
we
bring
people
together
to
discuss.
How
can
we
move
the
industry
forward
and
we
all
believe
that
open
source
is
the
way
to
go
forward,
because
if
we
develop
tools
that
or
frameworks
that
are
a
closed
source
and
within
house
within
a
single
company,
then
the
code
is
dependent
on
that
single
entity.
A
And
if
the
entity
is
not
really
interested
anymore
in
sustaining
the
code,
then
well
the
code
dies
and
people
who
are
using
it
are
no
longer
able
to
update
it,
use
it
and
the
whole
project
dies.
But
if
we
depend
on
an
open
source
community
in
any
domain
really
well,
the
code
can
be
sustained
by
the
open
source
community
and
it
is
no
longer
dependent
on
a
single
person
or
a
single
entity.
A
B
You
Mata,
so
mother
just
started
talking
about
the
actual
benefits
of
using
open
source.
You
know
looking
more
broadly
about
the
history
of
open
source
in
the
IT
industry,
which
you
know
again
I'm
happy
to
be
a
big
part
of
I
claim
to
be
a
pioneer
of
open
source
because
I
really
the
first
piece
of
code
in
open
source
in
1990.
It's
called
liebe
accept
X
p.m.
B
It
I
have
to
admit
that
is
pretty
cool
and
and
I
haven't
touched
that
code
in
many
years
and
just
like
Marta
said
the
thing:
is
the
community
picked
it
up
and
they
kept
updating
it
and
I
know
there
were
security
issues
related
to
it
at
some
point
and
it
was
addressed
and
fixed,
but
so
back
to
you
know
the
role
of
open
source
in
the
IT
industry.
I
think
everybody
know
that
you
know
the
beginnings
were
a
bit
difficult.
B
Microsoft
is
well-known
to
have
called
this
some
kind
of
communist
initiative,
and,
and
obviously
everybody
has
come
around
by
now-
it's
broadly
used
across
the
industry.
Ibm
was
a
pioneer
and
adopting
open-source
I'm.
You
know
we
are
lucky
that
we
had
a
CEO
who
realized
that
phenomenally.
It
was
very
similar
to
what
we
had
been
doing
in
science
in
research
for
a
long
time
where
researchers
share
innovations
right,
they
find
stuff
and
they
actually
have
these
meetings.
B
B
We
don't
have,
you
know
such
a
broad
audience
as
we
can
have
when
we
go
open-source,
where
you
have
a
community,
which
is,
you
know,
potentially
reaching
out
throughout
the
globe,
and
you
have
people
with
different
backgrounds,
different
skills
that
can
participate
and
they
bring
their
own
use
cases
and
requirements,
and
they
try
to
address
them
and
help
the
whole
system
make
it
better
for
everybody.
So
that's
the
you
know
a
sense
of
open
source
and
I
said
you
know,
I
think
it's
now
widely
accepted
as
a
good
way
to
do
things.
B
There
is
another
aspect,
though,
that
is
still
kind
of
you
know
not
so
well
understood
is
the
open
governance
aspect.
So
there
are
many
different
projects
that
are
open
sourced
today.
That,
in
my
books,
are
not
with
the
open
source
and
the
reason
is
there
is
a
single
entity
behind
it
that
controls
the
code,
and
you
see
a
lot
of
that
on
Gita.
B
Beyond
that,
they,
you
have
no
real
control
over
the
evolution
of
the
of
the
software
unless
you're
part
of
that
company
that
behind
the
code-
and
so
all
you
can
do
really
is
send
full
requests.
This
is
the
way
you
submit
changes
to
the
code
and
the
people
in
charge
of
the
project
behind
it
who
are
employee
of
the
company
who
owns
the
project,
basically
decide
to
either
they
feel
like
this
is
worth
it.
B
They
use
it
or
they
ignore
you
and
you
have
no
recourse,
and
you
have
no
say
in
the
in
the
control
in
the
evolution
of
the
software,
I
mean
one
of
the
key
elements
of
hyper
ledger,
which
we
all
share.
Is
this
aspect
of
open
governance,
so
the
project's
have
to
you
know,
agree
to
work
under
certain
rules
that
we
all
share,
which
guarantee
that
not
a
single
entity
will
actually
be
in
control
of
the
code
and
so
talking
about
fabric,
for
instance,
that
can
I'm
happy
to
say
that
you
know
we've
seen
that
happen.
B
It
was
contributed
by
IBM
initially,
so,
naturally,
most
of
the
developers
initially
were
from
IBM
we
had
40
or
so
developers
from
IBM,
Wilson
and
we're
part
of
the
group,
but
that
alone
didn't
really
make
it
open
source.
Right
and
now
we
have
like
something
like
150
contributors
from
27,
different
organizations
involved,
and
so
for
me
this
is
really
a
key
factor
of
a
successful
open
source
story
where
you
actually
create
an
open
source
community
behind
it
right.
So
with
that
being
said,
I
would
like
to
bring
up.
B
We
have
a
poll,
I,
don't
know
if
we
can
get
that
on
the
screen
or-
and
so
we
wanted
to
ask
the
audience
in
your
mind.
You
know:
does
open
source
play
a
role
in
your
selection
of
blockchain
technology
and
will
ask
again
the
question
at
the
end,
so
we
can
see
if
the
discussion
kind
of
influenced
you
at
all.
So
if
you
can,
you
can
use
your
devices
to
answer
the
questions
and,
by
the
way,
I
have
a
set
of
questions
that
we'll
be
asking
the
panel.
B
C
C
The
wiki
is
open
to
anyone.
This
type
of
model
is
a
great
way
to
build
a
community,
and
we
found
that
we've
been
able
to
get
much
better
traction
with
our
ideas,
namely
hybrid
redraw,
then
what
we
could
have
done
by
ourselves
as
our
company
and
because
other
ideas
from
other
contributors
outside
our
company
as
well
and
that
has
made
I,
think
a
much
better
project
than
we
could
have
built
built
on
their
own.
C
So
I
think
that's
one
of
the
large
advantages
from
a
I
don't
know
a
creator
standpoint
from
a
person
trying
to
put
out
ideas
and
doing
something
similar
to
dialectics.
In
from
that
side,
from
the
user
side
it
works
kind
of
the
other
way
where
small
company.
So
it's
very
hard
to
trust.
Someone
like
us,
because
we've
only
been
in
business
for
about
a
year
and
a
half
who
knows
that
will
be
around
10
years,
20
years,
30
years.
C
Who
knows
if
IBM
will
be
around
in
10
to
30
years,
so
having
open
source
is
a
way
to
kind
of
increase
trust,
because
even
if,
in
the
worst
case,
if
this
entity
were
to
go
away,
the
project
is
still
there.
The
community
is
still
there
by
Carlos
saying
even
years
later,
someone
can
take
these
ideas
and
bring
them
to
life
in
a
new
way,
and
so
that's
that's
been
a
huge
benefit
to
our
company
and
also
to
people
who
want
to
use
our
products
because
it
increases
the
levels.
C
C
But
if
it's
the
open
source
and
you
join
the
community-
and
you
could
collaborate
with
people
like
them
like
how
Sarah
is
doing,
then
that's
one
way
to
kind
of
build
a
sustainable
community
that
you
know,
can
you
can
get
new
ideas
and
it
kind
of
works
in
a
cycle.
So
in
Japan
we
we
use
or
one
of
the
professor's
we
work
with
at
the
University
of
idea.
Professor
Fuji
uses
the
analogy
of
a
miso
soup.
I
don't
know
if
people
are
familiar
with
it,
so
it
meat
so
soup.
C
You
have
this,
it's
warm
so
it
it
heats
up
and
it
comes
up
to
the
top
and
then
it
it
cools
off
and
goes
back
down.
So
if
you
look
at
it
it's
kind
of
like
cloudy
in
a
way
you
can
see
these
particles
moving
around.
So
it's
kind
of
like
how
this
cycle
works.
You,
you
kind
of
you,
know,
lift
up
ideas
and
you
get
maybe
some
new
ideas.
D
Nathan,
okay,
well
I
tried
to
with
my
vanka's
head
for
a
second
on.
So
if
you
are
a
financial
institution
and
you
need
to
go
and
promote
something
to
your
boss
and
this
basically,
you
need
to
come
up
with
a
set
of
features
of
what
is
usually
people
log
into
our
writers.
What
I
will
return
on
investment
or
kind
of
what
are
the
risk
associated
with
a
project?
A
song
or
the
vendor,
comes
to
you
and
gives
you
some
I,
don't
know,
I
feel
like
five
pitches.
D
It
gives
you
six,
but
you
don't
know
what's
going
on
in
the
code,
you
don't
know
how
many
people
are
using
it
and
how
it's
very
difficult
for
you
to
make
a
case
whether
somebody's
open
for
now
I'm,
not
saying
the
dog
assault
is
necessarily
safer
or
better,
because
the
I'm
telling
you,
even
as
a
release,
manager,
it's
very
difficult
to
make
progress
when
you
have
conflicting
interests
right.
So
the
upside
of
you
working
with
so
many
ways
open
source
is
that
you
don't
have
this
risk
of
having
the
vendor
lock-in.
D
We
talked
about
this
one,
probably
about
standardizations
but
basically
justified.
The
people
can
take
the
code
and
fold
it
to
another
system.
So
I'll
give
you
a
practical
example
we're
working
and
we
started
working
with
a
boom
tube.
Okay,
it's
a
version
of
Linux
and
that's
the
standard,
and
then
somebody
from
Wayne
had
said:
hey
guys,
we
would
like
to
certify
it
with
Reddit.
D
Is
it
possible
for
us
to
what
what
I
need
to
do
pane
and
then
I
started
talking
to
them
they're
going
to
get
like
two
engineers
working
full
time,
making
sure
that
the
build
works
all
the
time
now
you're
going
to
have
a
redhead
fault
of
our
code
base,
so
just
the
ability
for
you
to
take
some
stuff
improve
it,
contribute
it
back
and
then
have
the
infrastructure,
open,
I!
Think
it's
very,
very
useful.
So
the
first
thing
is
that
authorization
and
being
open
knowing
what's
happening.
D
The
second
thing
is
the
vendor
lock-in
that
everybody's
afraid
of,
like
especially
sorry,
but
if
you
look
at
IBM,
they
had
a
better
view
tation.
Before
of
kind
of
locking
you
in
doing
a
lot
of
studies
as
proprietary,
you
don't
understand
how
much
is
going
on
behind
the
scene.
Now
they
say,
look
guys.
You
know,
I'm,
not
saying
this
is
all
available.
There's
no
different
code
bases,
rather
not
several.
We
run
exactly
the
same
code.
D
If
you
want
to
take
it
and
fold
it
and
use
it,
we're
using
the
same
code,
I'm
deploying
fabric
on
Google,
Cloud,
okay,
so
I
don't
know.
So,
if
I
have
somebody
that
wants
to
do
it
on
bluemix
no
problem,
but
I
can
take
it
better
than
something
else.
There's
no
problem!
The
code
is
out
there.
So
there's
a
lot
of
benefits
in
you
having
the
base
line
that
is
available.
Think
about
the
Linux
kernel.
Think
about
all
the
open
source
kind
of
projects
that
you
have.
D
If
anybody
has
a
security
feature
that
we
promise
them
is
not
there
or
something
is
wrong:
I'm
not
releasing
it
right
and-
and
it's
nice
to
have
somebody
did
it's
kind
of
not
really
commercially
affected
by
the
pressure
that
some
any
any
of
the
27
companies
that
we
just
look
at
it
say:
look
if
I
sign
up
the
release,
I
need
to
make
sure
that
it
really
does
what
it
says
on
the
box
and
because
it's
open
I
cannot
even
lie
about
it,
because
it's
a
Halo
long.
That
was
the
Monday
that
we
gave.
D
D
A
Think,
that's
just
to
add
one
more
thing.
Well,
there
are
two
more
things:
one
is
diversity
in
open
source.
You
get
diversity
of
backgrounds,
experiences,
cultures,
that's
something
that
we
are
very
proud
in
hyper
ledger
of.
25
percent
of
our
members
come
from
Asia
25
percent
are
from
Europe,
so
we
have
a
very
diverse
group
of
members
and
people
who
contribute
to
our
projects,
which
means
that
from
that
diversity
comes
an
excellent.
That
would
not
be
possible
if
we
developed
in
just
a
very
homogeneous
environment
and
that's
what
open
source
gives
you.
A
It
brings
people
together.
That
crash
heads
and
really
fight
for
what
is
important
for
them
and
what
they
believe
is
the
single
most
important
to
single,
most
important
things
and
that's
not
as
I'm
saying
that's
not
possible
in
closed
environments,
and
the
second
thing
when
it
comes
to
open
source
is
that
when
it's
especially
when
it
comes
to
blockchain,
because
really
that's
we
can
advocate
for
open
source
in
any
anything.
But
when
it
comes
to
blockchain
is
that
it
is
important
to
understand
that
blockchain.
We
don't
really
yet
know
how
blockchain
will
come
out.
A
We
don't
really
fully
understand
the
technology,
it's
a
very
young
technology
and
that,
as
with
any
young
technology
that
we
don't
know
of
consequences
having
it
open
source
and
having
many
people
look
at
it
and
being
developed
in
a
kind
of
manner
where
many
people
look
at.
It
means
that
we
are
much
more
likely
to
catch
any
mistakes
and
have
someone
spot
that
there
is
something
going
wrong.
So
the
more
eyes
we
have
on
on
something
and
the
more
contributors.
We
have
the
better
really
all.
A
B
Told
the
conference
people
we'd
have
no
prime
talking
about
this.
For
a
long
time,
I
have
to
admit:
I
did
something
wrong
with
the
pad
and
so
I
lost
the
application.
I
can't
even
see
it.
So
if
somebody
comes
from
the
conference
could
reset
this,
that
would
be
helpful.
Otherwise,
I
wanted
to
see
the
result
of
the
poll
which.
B
You
Mata,
ok.
So,
following
up
on
the
on
the
questions
there
one
question
I
had
for
you
is:
do
you
think
open-source
can
play
a
role
in
helping
with
the
shortage
in
skills
we
have
in
blockchain
I
mean,
as
you
said,
blockchain
is
pretty
young
and
actually
I've
met
people
that
the
conference
already
saying:
hey
I.
Have
all
these
projects
coming
up,
but
I
don't
have
the
resources,
so
my
photo
yeah.
C
So
yeah
I
think
so
that's
another
thing,
so
one
one
aspect
of
open
source
in
bar
chain
is
trust.
Maybe
people
people
can
see
the
code
entrusted
another?
Is
that
it's
really
more
efficiency
for
spreading
ideas?
So
if
someone
has
an
idea-
and
they
want
to
build
something
rather
than
doing
it
all
by
themselves-
they
can
actually
maybe
take
an
existing
platform.
C
Maybe
do
some
changes
to
it
or
add
a
new
consensus
algorithm
for
instance,
and
and
try
out
new
ideas
and
open-source
allows
you
to
kind
of
create
this
other
sandbox
environment
that
you
can
try
out
new
ideas,
much
easier
and
it's
not
the
knot
of
the
putt.
None
of
the
platforms
and
hyper
ledger
are
completely
completed
yet,
but
eventually
we're
going
to
make
things
I
think
across
all
the
projects,
much
more
modular
so
that
we
can
maybe
cross
pollinate
algorithms
as
much
as
possible.
C
B
C
Few
number
of
people
who
have
experienced
building
block
chains
and
building
these
things
so
having
all
the
code
out
and
sniffing
and
having
the
more
importantly,
governance
in
the
open
people
can
not
only
see
the
design
decisions
that
are
made,
but
they
can
understand
them
and
that's
that's
the
best
way
of
educating
new
programmers
to
deal
with
this
technology,
because
it's
actually
quite
a
lot
of
small
details
that
are
non-obvious
and
once
you
get
into
building
a
project,
especially
from
scratch.
You
can
kind
of
understand
that.
C
Oh
this
design
decision
won't
work
because
of
you
know
this.
This
small
detail
that
that
you
understand
it
so
being
able
to
share
that
information
in
the
community
with
other
people
putting
on
a
wiki
putting
it
in
documentation
is
extremely
important,
and
it's
something
that
that
we,
of
course,
with
eater
heart,
can
do
better
on.
But
it's
something
that
I
think
it's
really
important
for
community
building
and
we
we
try
to
do
our
best
with
doing
things
like
study
groups
and
helping
people
understand
the
code
SAVE
all.
D
Jonathan
quickly,
the
quick
so
I
think
it
doesn't
building
scales
or
fanic
skills.
I
think
that
officers
actually
makes
it
very
easy
for
the
developer
to
shine.
So
you
can
easily
see
who
are
the
big
contributors
that
many
of
us
do
stuff
and
contribute
and
they
consult
in
the
advice
and
they
have
all
the
companies
or
the
build
of
the
project
so
being
available,
is
good
you're
not
trying
to
find
people
kind
of
little
flashlights,
but
on
the
other
hand,
it's
a
lot
easier.
D
When
you
have
a
platform
that
you
don't
need
to
build
all
on
your
own,
you
just
need
to
add
your
own
layer.
So
if
you're
looking
at
skills,
it
used
to
be
that
kind
of
you
get
like
a
lot
of
valuing
internally.
If
you
hire
like
50
or
100
people
for
the
new
blockchain
project.
Now
you
can
do
a
lot
of
things
with
like
ten
people,
five
people,
it's
very
quick
because
we
build
so
much
on
the
layer
that
you
don't
need
to
really
just
add
your
own
solution.
D
B
D
D
I
thought
the
best
person
if
I
speak
too
quickly.
Let
me
know
because
I
have
a
lot
to
say,
but
just
there
like
two
camps
right,
that
is
one
cam
that
says
it's
good
to
have
digitize
anything
work
change,
because
you
want
to
know
who
are
the
participants.
So
we
are
an
access
control
company.
So
we
allow
you
to
manage.
Who
can
access?
You
can
read
who
can
write
so
we
really
help
people
kind
of
get
the
blockchain
certified
in
regulated
environment.
So
that's
one
hand.
D
On
the
other
hand,
you
have
other
people
says:
look
all
this
identity
thing
should
be
completely
separate.
I
want
privacy
I
want
an
ability
of
transactions;
I,
don't
people
to
profile
me
I,
don't
want
to
track
what
I've
done.
So
if
you
look
at
regulations
of
course,
you
want
the
identity
of
the
people,
because
people
think
like
that
right,
there's
a
KOA
caml.
If
you
don't
have
authentication
and
authorization,
then
right.
What's
the
point
in
having
an
audit
trail
or
reporting.
If
you
don't
know
what
it's
the
participant,
why
do
you
care
what
they've
done?
D
But
identity
is
a
different
topic
because
we
say
that
if
you
want
inclusion,
it's
very
you
need
to
do
it
right.
You
need
to
the
identity
correctly,
otherwise
you
will
exclude
so
many
people.
They
don't
have
access
to
resources
because
they
don't
have
an
iPhone,
for
example
right.
So
that's
that's
kind
of
the
helots
aside
all
right.
Thank
you.
No.
B
C
So
some
cryptocurrencies
are
are
an
interesting
topic,
so
I
first
got
into
this
space
because
a
Bitcoin
just
because
it's
very
interesting
that
you
could
send
money
anywhere
the
world
just
like
email,
so
yeah
one
sent
money,
there
are
no
I,
don't
go
down
to
the
bank
and
type
in
some
numbers
and
oaks.
Past
4:00
p.m.
I
kept
ended,
but
yeah
just
said
just
like
email,
you
type
in
the
address
it
just
goes
at.
C
It's
really
just
digital
and
it's
it
just
made
a
lot
of
sense
to
me
and
so
I,
don't
I,
don't
use
cryptocurrency
much
I
used
it
to
book
my
hotel
here
in
Copenhagen,
but
it's
more
of
just
a
hobby,
I
guess
than
anything
else.
Our
company
deals
with
fiat
currencies.
So
we
worked
with
people
like
central
banks
and
banks
to
actually
create.
You
know
real
currencies,
not
crypto
currencies.
All.
B
Right
and
then
now
I'll
take
my
progressive
of
being
the
moderator
here
to
actually
answer
the
next
question,
which
was
one
of
the
question
haven't
got
to
which
are
the
drawbacks
of
open
source,
because,
of
course,
we
have
heard
of
supporters
open
source
and-
and
so
we
are
all
very
enthusiastic
about
it.
There
are,
there
are
drawbacks,
though
I
mean
one
of
the
main
ones.
I
would
say.
B
Is
that
it's
a
lot
messier
than
you
know,
development
in
a
closed
environment,
in
the
sense
that
in
a
company
typically,
you
have
some
hierarchy
and
there
is
a
management
chain
and
you
give
orders,
and
you
give
my
stones
deadlines,
that
the
the
developers
have
to
just
comply
to
in
an
open
source.
It's
much
more
democratic
and,
as
we
all
know,
democracy
tends
to
be
messy.
B
It
does
come
with
all
sorts
of
benefits
that
make
it
worthwhile,
but,
for
instance,
you
know
you
can't
just
set
a
deadline
and
say
you
guys
have
to
deliver
by
that
date.
You
have
to
work
with
the
community.
The
community
has
to
agree,
and
it's
a
much
flatter
organization
right.
So
there
is
a
level
there
is
the
notion
of
maintainer
x'
that
keep
control.
They
are
here
to
ensure
that
the
you
know
the
system
doesn't
get
broken,
but
it's
much
more
democratic
and
a
little
bit
more
messy
I
think
as
a
result.
D
So
a
few
things
right
so,
for
example,
again
I
take
fabric
as
an
example
and
I'll
take
a
certain
example.
So
if
I
we
have
27
companies,
sometimes
they
have
conflicting
interests.
Sometimes
they
have
like
commercial
needs.
So
if
I'm
in
an
open
source,
environment
and
people
are
telling
me
I
want
to
release
it
now
and
I,
don't
want
to
have
Android
support
because
I
don't
have
time
for
it
and
somebody
else
wants
it.
So,
just
think
about
this
example.
D
How
do
you
reconcile
if
it
was
a
commercial
agreement
and
we
didn't
have
to
go
up
the
source?
And
there
was
no
other
contributor
that
comes
in
and
pushes
for
it
for
direction?
Then
it's
a
lot
easier
to
make
the
decision.
Is
it
the
right
decision?
I,
don't
know
when
it's
in
the
open,
yet
it's
more
it's
more
messy,
but
it's
also
it's
more
messy.
If
you
don't
draw
this,
it's
more
messing.
It
takes
more
time.
D
I
argue
that
my
job
description
is
Jonathan
cannot
be
nice
because,
whatever
I
do
I
have
to
piss
off
people
right
because
I
make
decisions,
and
even
if
you
go
for
a
vote,
even
if
it's
like
six
out
of
ten,
therefore
wheelers
are
not
happy.
So
the
problem
with
open
source
is,
you
cannot
always
have
like
the
direction
and
then
do
the
the
one
thing
you
want
to
do
because
there's
so
many
opinions
now
look
at
her
Sarah.
The
VP
of
R&D
of
a
Sarah
is
Russian.
D
Is
the
good
friend
of
mine
from
Israel
and
he's
always
telling
me.
Look
all
this
democracy
and
all
this
opens
up.
It's
fine,
but
I
will
tell
you
like
what
we
say
in
Russian.
You
have
a
blanket
and
everybody
is
pushing.
You
know
in
each
direction,
there's
a
big
hole
in
the
middle,
so
he
doesn't
like
this
all
democracy.
He
comes
in
history,
comments
and
get
stuff
done.
D
There's
no
democracy
inside
the
company
in
a
way,
but
it
gets
up
faster,
but
sometimes
it's
nice
to
get
other
people
to
tell
us
what
they
think
about
things
right.
So
there
are
two
different
models:
I,
don't
know,
I,
don't
know.
What's
better
I
like
the
open
source
way
more,
despite
the
extra
I
call
it
investment.
You.
C
I
can
say
a
little
bit
about
my
philosophy,
so
I'm
a
huge
I
like
open
source
and
collaboration
in
execution,
fine,
finding
solutions,
but
for
design
I'm,
a
huge
fan
of
design
dictatorship,
so
I
think
that
there
needs
to
be
very
clean
and
clear
design,
and
that
should
that
should
guide
and
then
maybe
there's
lots
of
other
ideas
and
use
cases,
but
I
think
to
really
create
a
good
design.
You
need
to
have
you
know
someone
like
the
Steve,
Jobs
type
of
character,
who
sits,
sits
up
there
and
says
no.
It
helps
me.
C
B
Right
so
I
have
a
different
question
that
I
will
need
to
actually
bring
up
to
the
panel,
which
has
to
do
with
standards
and
I'm
like
I,
said
I'm
an
open
technology
person
and
it
includes
standards
and
I
get
a
lot
of
requests
from
different
standards
organization
about
launching
some
standards
activity
around
blockchain.
So
the
question
is:
is
it
too
early
to
be
thinking
about
standards
for
blockchain,
so
motor
making?
You
want
to
stop.
A
Yes,
so
yes,
and
no
I
I
think
it
is
too
early
to
produce
documents.
In
my
opinion,
because
documents
tends
to
carve
in
stone
what
people
are
doing
and
stop
actually
development
and,
as
I
said,
it's
a
new
technology
technology.
We
don't
really
understand.
We
are
still
in
in
the
high
from
the
top
of
the
hives.
There
is
a
bit
of
a
discussion.
We
are
developing
peers
offices
and
then
pushing
for
deployment,
but
wait
deployments.
Why
are
we
deploying
things
that
we
are
not
really
understanding?
D
C
Okay,
I'm
very
quick
to
add
so
I
think
for
standards.
It's
as
she
said
it's
way
too
early
to
create
standards
for
the
core
block
chain
levels,
but
at
a
higher
protocol
level,
so
like
for
payment
protocols
and
things
like
that.
It's
it's
a
good
time
and
the
reason
is
once
applications
get
built.
So
you
know
mobile
apps
web
apps.
They
get
locked
into
a
certain
way
of
doing
things.
Then
you
it's
really
hard
to
change
later.
C
So
my
company's
C
chief
operating
officer
created
the
digital
currency
in
Japan
called
Eddie,
both
digital
money
in
Japan,
it's
used
by
about
110
million
people,
and
so
it's
an
NFC
based
currency
and
but
there's
many
different
NFC
cards.
So
there's
the
same
technology
is
used
for
Sica
for
Peter
Paulson,
all
these
different
things
and
overseas,
like
oyster
or
octopus
card.
C
But
all
these
cards
are
using
the
same
NFC
technology,
so
maybe
say
vasilica
technology
developed
by
Sony,
but
they
don't
have
interoperability
because
the
data
formats,
the
data,
that's
actually
transmitted
to
the
reader,
is
different,
and
so
just
the
reader.
Looking
at
the
data,
that's
a
hard
time,
knowing
you
know
which
is
this:
is
this
Peter
Paulo's
this
whatever,
and
we
have
that
now
with
QR
codes?
So
if
you
scan
a
Bitcoin
QR
code,
all
the
houses
in
a
dress,
it
doesn't
tell
you
Bitcoin,
it
doesn't
tell
you.
This
is
etherium.
C
You
have
to
know
something
about
the
format
of
the
address
and
even
then
you
just
guess
most
of
the
time
with
ERC
20
tokens
now
you've,
no
idea
what
token
you're
dealing
with
you
all
you
have
is
just
this
address,
and
so
that's
that
type
of
thing
can
be
standardized
now
and
that's
that's
one
of
the
things
that
actually
we're
trying
to
promote
with
open
standards.
So
I
think
this
year
we're
going
to
see
a
lot
of
hopefully
movement,
Drechsel.
All.
D
D
But
what
happens
if
you're
going
to
have
so
many
different
implementations
and
they're
not
going
to
talk
to
each
other,
we're
going
to
create
actually
more
and
more
silos,
so
we
have
to
talk
to
each
other
and
if
you're,
looking
at
vidcon
and
oil
cerium
or
all
the
enterprise
business
level
kind
of
blockchain,
each
of
them
is
trying
to
solve
different
things.
Right,
one
is
like
I'm
allowing
anyone
to
come
in
I
care
about
censorship,
resistance,
for
example,
the
blacks
are
coming
in
listen.I,
obscenities,
customized
information,
I
cannot
just
share
it.
D
There's
some
rules
in
Germany
that
you
cannot
move
data
around
out
of
Germany
to
even
AWS.
So
if
you
want
to
have
like
an
enterprise
solution
that
has
different
requirements,
that's
fine!
You
can
address
it
in
an
enterprise
blockchain,
but
we
still
have
to
talk
to
each
other.
So
we
have
an
access
control
layer
that
talks
to
different
kind
of
block
chains
and
I'm
telling
you
for
us
to
do
the
adapter
in
a
way
that
we
don't
have
to
play
with
the
underlying
code
just
to
sit
on
top.
It
was
really
a
nightmare.
D
It
seems
like
two
years,
but
now
we
can
talk
to
any
blockchain
in
the
same
way,
I
think
it's
going
to
be
natural
for
us
to
have
a
standard.
At
some
point.
There
are
some
working
groups
in
the
making
because
we
are
trying
to
see
what
is
in
account.
What
is
a
user?
What
is
a
participant?
What
is
it
validator
and
most
of
that
most
of
the
technologies
are
trying
to
solve
the
same
thing
with
different
modules,
so
I
would
advocate
for
more
modular
kind
of
block
chains
and
yes,
some
working
groups
that
we
produce.
D
B
A
B
B
We
already
have
different
applications
in
predictions
today,
more
and
more
vendors
make
announcements
their
consortium,
it's
important
to
realize
it's
a
bit
more
difficult
to
adopt
than
some
other
technology
where
you
can
just
do
it
on
your
own.
Here
it
actually
takes
us
network.
So
you
it's
a
really
a
consortium
play
type
of
thing,
but
but
there
are
more
and
more
consortium
looking
into
it
and
actually
developing
applications,
and
so
you
know
I,
don't
want
you
to
think
that
this
is
just
something
for
the
future.