►
From YouTube: Live Demo of the Monax Platform - Silas Davis, Monax
Description
Join us for a live presentation of the powerful new platform, which allows consumers to easily procure lawyer-tested agreements and stay in full control of their business contracting.
----
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 #HyperledgerGlobalForum2018 #Blockchain
A
What
I'm
here
to
give
you
a
demo
of
is
a
thing
called
the
Mon
axe
platform.
The
mo
next
platform
runs
on
top
of
a
decentralized
network
based
on
burrow
called
the
agreements
network.
So
to
delineate
those
two.
The
agreements
network
is
about
representing
agreements
as
a
package
of
legal
pros.
Some
parameters
and
a
legal
process
and
it'll
become
clear,
I
think
as
we
go
through
the
demo.
A
What
what
that
involves,
but
the
layer
that
you're
seeing
here
is
Mon
axes,
sort
of
proprietary,
fairly
thin
layer
on
top
of
the
agreements
network
beneath
that
we
have
a
project
called
Blackstone
is
open
source
that
contains
the
solidity
contracts
that
power
the
agreements
network.
Other
people
could
build
different
types
of
platforms.
On
top
of
the
agreements
network.
We
have
a
group
of
network
co-founders
from
regal
tech
companies
and
others
who
are
running
the
validators
and
there's
a
underlying
market
model
and
other
things.
A
So,
if
you're
interested
in
that,
please
do
come
and
ask
me
or
come
to
our
store,
but
but
this
is
really
about
the
platform
layer.
So
this
is
this.
Is
me
just
logged
on
to
the
to
the
platform
and
I'll
just
talk
you
through
some
of
the
onboarding
screens
here.
So
the
idea
of
this
is
to
give
you
a
view
of
what
your
obligations
are
over
a
DOS
era
of
agreements,
so
we're
representing
agreements
that
have
some
moving
parts.
We
that
internal
state
as
the
agreement
progresses.
For
example,
we
go
into
a
default
clause.
A
A
A
We
wrap
up
agreements
in
a
template.
The
underlying
object
is
a
thing
called
a
archetype,
and
it's
this
triple
of
legal
pros
parameters
and
legal
process,
and
that
process
is
is
modeled
in
a
thing
called
business
process.
Modeling
notation
and
we've
implemented
an
engine
to
run
that
on
top
of
burrow.
So
what
I'm
going
to
do
is
take
you
over
to
some
templates.
So
here
we
can
see
some
publicly
available
templates.
Now,
let's
pull
up
a
rental
agreement.
So
I
choose
this
because
it
has
a
relatively
non-trivial.
A
Can
you
see
that
okay,
relatively
non-trivial
process,
so
you
can
see
here,
there's
some
metadata
at
the
head?
There's
some
parameters
that
I
was
mentioning
there
so
I'll
draw
your
attention
to
this
boolean
here
that
says,
building
before
1978
so
was,
was
the
building
that's
being
rented
out
here,
built
before
1978,
there's
some
relevance
to
that,
but
we'll
see
later
on
in
the
process
number
of
payments.
So
this
is,
for
example,
in
a
shortish
or
tenancy
in
the
UK.
You
would
have
maybe
12
payments
and
then
it
lapses
into
another
state.
A
A
The
way
that
we
do
process
is,
if
you
have
a
formulation
process,
so
a
formulation
process
is
the
thing
that
goes
and
collects
is
signatures
in
a
basic
model,
but
it
can
go
into
other
things.
It
could
call
off
to
a
kyc
service,
anti-money
laundering
check
or
something
like
that.
In
this
case,
it's
relatively
simple:
we
have
a
distinguished
start
state.
These
long,
rectangular
swim
lanes
represent
participants,
so
at
the
top
I
think
we
have
the
the
agreement
parties.
So
this
is
stuff
that
everyone
has
to
do
at
the
bottom.
A
We
have
the
tenant
and
then
the
enclosing
boxes
is
the
process.
So
this
is
a
bpmn
I,
don't
know
if
anyone's
familiar
with
it,
but
it
has
well-defined
semantics.
It's
an
executable,
workflow
standard.
So
if
we
have
on
the
agreement
building
before
1978,
what
we'll
have
to
do
is
sign.
This
lead
paint
disclosure
and
then,
after
that
we
can
go
into
signing
the
agreement
and
the
agreement
is
formulated
down
here
we
have
how
the
agreement
actually
runs.
So
again
we
have
the
full
signing
parties,
sorry,
the
system
system,
the
top.
A
So
this
is
no
distinguished
participant
and
then
we
have
a
few
different
types
of
tasks.
So
these
boxes
are
called
tasks
and
this
thing
with
a
cross
in
it
is
called
a
gateway.
That
is
a
choice
element.
So
we
start
here
in
the
system
start
we
go
through.
We
make
a
payment,
we
go
into
another
type
of
task
here,
which
is
a
system
task,
so
this
runs
a
smart
contract
to
do
a
check
in
this
case
it
just
checks
against
one
of
the
parameters.
A
A
A
The
visibility
here
all
of
the
process
modeling,
is
going
on
on
a
what
is
a
public
four
mission
chain.
Ultimately,
we
can
choose
to
hide
the
satellite
data
in
encrypted
form
of
chain,
but
it's
worth
saying
this
is
not
private
in
a
particularly
strong
sense.
For
example,
if
you
know
that
the
process
is
taking
100
payments
or
its
it's
usually
d,
anonymized,
it's
not
trying
to
be
private
in
that.
In
that
sense,
external
references.
This
is
to
do
with
how
many
pieces
of
evidence
we
can
attach
to
this
Agreement.
A
A
So
we
hit
here
a
quick
review
screen
of
the
process
and
then
a
final
review
now.
This
is
then
going
to
send
actions
off
to
the
chain
the
spinner
of
doom
comes
in
here,
so
we
have
a
few
transactions
on
which
need
to
be
serially
run,
so
we
end
up
waiting
there
for
a
confirmation.
So
that's
that's
gone
onto
the
chain,
so
we
now
formulate
your
disagreement:
okay,
fantastic!
A
So
if
I
go
through
now
into
the
tasks,
you'll
be
able
to
see
that
I've
got
a
few
other
tasks
that
have
been
generated
here
from
similar
agreements
and
my
rent,
my
shed
agreement
and
maybe
off
the
page
I'll
show
you
on
this
task.
So
tasks
come
up
here
within
the
agreement
and
you
can
sign
on
that
task
and
via
our
user
proxy,
your
signature
will
be
collected
and
we'll
move
that
task
along.
So
there's
other
ones
here
from
the
lead
paint
disclosure.
A
Now,
if
we
go
on
to
the
set
of
agreements
of
which
there's
a
number,
if
we
look
at,
for
example,
rent
my
outside
toilet,
there
I
think
I
moved
that
one
along.
So
you
can
see
that
there's
a
live
process
flow
through
through
the
agreement
and
if
we
go
back
to
the
tasks-
and
we
start
clicking
stuff
off
I've
created
a
slightly
too
much
task.
Spam
here
meant
my
shared
and
I've
also
called
too
many
rent.
My
shed,
not
very
creative
of
me,
but
I
think
you
can
get
the
idea.
A
So
this
is
this
is
another
one.
That's
pre-formulated!
You
can
see
that
we've
started
going
through
and
going
to
payments
and
the
processes
is
spinning
around
now
we
can.
We
can
absorb
events
from
this
with
the
service
that
we
have
and
we
can
drive
other
downstream
things
now
briefly
and
I'm
getting
some
emails
now
to
say
you
have
a
pending
task.
You've
signed
a
task
and
we'll
get
notified.
That
way,
just
like
to
show
you
the
other
thing
in
this
layer.
A
We
have
a
business
process,
modeling
engine
editor
here,
so
you
can
build
your
own
processes
and
the
the
breed
of
human
being
that
we
are
trying
to
get
on
our
network.
Is
this
emerging
discipline
of
legal
engineer
so
a
lawyer
who
can
scale
some
of
their
knowledge
automate
some
of
these
things
and
but
still
be
around
to
respond
to
things
and
to
do
this?
Have
we
have
three
types
of
essential
tasks?
We
have
a
user
task
that
waits
for
some
user
input,
so
it'll
sit
there
and
you'll
go
and
you'll.
A
A
We
have
this
by
directionality
on
on
the
smart
contract
application
activity
and
we
have
an
async
task,
which
can
say
I'd
like
to
get
some
information
from
an
Oracle
post
that
requests
the
Oracle.
That
can
then
put
it
back
and
the
process
will
wait
until
it
gets
in
from
that.
So
we
have
a
game
at
the
moment
that
is
live,
that
is
a
weather,
guessing
game
and
that
uses
the
process.
Modeling
and
youyou.
A
B
A
So,
within
our
node
distribution,
we
have
I
pledge
a
borough
which
is
providing
our
core
consensus
network.
We
have
a
stateless
encryption
service
called
hoard
that
stores
on
backends
ipfs
file
storage.
We
have
Blackstone,
which
is
a
project
we've
recently
open
sourced
and
we're
planning
to
submit
to
hyper
ledger.
So
if
you
go
MONUC
slash
Blackstone,
now
that's
a
set
of
smart
contract
libraries
that
do
the
business
process
modeling.
A
A
A
Right
the
front
and
yet
yeah,
which
and
I
think
we've
done
some
some
editing
to
that.
So
we
support
a
more
limited
set
of
BPMN
than
the
whole
thing,
so
I
mean
in
fact,
I
think
fully
fledged
peepee
men
is
not
even
an
unambiguously
executable,
there's
B
pal,
but
with
this
you
know
it's
kind
of
like
a
graphical
programming,
environment,
I,
guess
so,
there's
quite
a
bit.
You
can
do
with
it.
A
A
So
I
think
something
that
I
probably
elided
over
here
a
bit
is
that
the
underlying
agreements
network
is
built
around
the
notion
of
three
types
of
participant:
legal
producers
and
legal
consumers
and
legal
testers.
So
as
it
happens,
we're
a
company
that
has
a
legal
engineering
team
and
was
founded
by
a
lawyer.
In
fact,
so
we
will
be
producers
on
our
own
network,
but
we're
also
trying
to
bring
in
other
producers
who
will
be
solving
some
of
these
problems
themselves.
A
In
terms
of
standardizing
terms,
we
deliberately
have
the
templating
and
the
parameters
part,
it's
quite
a
black
box.
At
the
moment
there
are
other
legal
engineering
companies
that
are
trying
to
get
more
in
inside
the
legal
pros,
if
that's
what
you're
driving
at
we're
focusing
on
a
dual
integrated
piece
of
legal
text
with
a
process,
the
process
is
not
exhaustive
of
what's
contained
and
mandated
by
the
legal,
the
legal
text,
but
we
are
I,
guess
I,
guess
the
flat
answer
is
we're
not
working
at
the
the
term
or
the
clause
level.
A
At
the
moment,
however,
we
would
expect
the
agreement
network
to
be
able
to
support
tooling.
On
top
of
this,
so
some
interesting
things
might
be
around
contract
negotiation
platforms
are
working
in
the
text
and
maybe
you
can
omit
both
process
segments
as
well
as
bits
of
text.
That's
very
much
something
we'd
like
to
support,
but
we're
not
trying
to
solve
all
these
problems.
It's
a
it's
an
ecosystem
play
and
we
won't
control
the
agreements
Network.
Even
so.