►
Description
Using BTP Sextant we show how with one click you can deploy a Hyperledger Sawtooth network on a Kubernetes cluster in the cloud. We then invite you to play tic-tac-toe on this and see if you can beat the system by bending the rules to suit yourself! Key takeaway - We will show how easy it is to get up and running using the right tool so that you can become productive in a matter of minutes. Using the universal game tic-tac-toe we will show how storing its state on a blockchain you cannot - try as you might - beat the system.
----
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
Thanks
for
joining
joining
us,
so
the
title
of
this
very
short
ten-minute
session
is:
can
you
beat
the
system,
and
so
what
we're
actually
going
to
do
is
is
do
two
minutes
on
what
we
are
actually
show
showcasing,
which
is
a
product
called
sextant.
So
sextant
helps
you
spin
up
Sawtooth
environments
or
toothed
networks
on
kubernetes
in
the
cloud.
A
Having
said
that
super
briefly,
what
we're
about
is
creating
a
curated
version
of
or
distribution
of
sorties.
So
this
is
a
classic
professional,
open
source
support
model
where
we
build
tests
and
maintain
a
version
of
sawtooth
and
so
we're
at
1.05
at
the
moment
now,
one
that
one
was
announced
last
Friday.
That
means
we're
currently
going
through
the
whole
sort
of
testing
process
before
making
that
available.
A
So
it's
really
aimed
at
making
sure
that
you're
dealing
with
an
own
version
of
a
piece
of
relatively
complex
software,
but
if
that
was
all
we
did,
it
will
be
useful,
but
in
addition
we
then
provide
you
with
a
nice
easy
graceful
way
of
then
deploying
it
and
spinning
it
up
in
in
in
in
terms
of
a
runtime
environment,
so
that
you
can
then
experiment.
So
so
this
notion
of
one-click
deployment.
A
We
talk
about
a
lot,
it's
the
idea
of
taking
all
of
the
pain
and
strain
out
of
actually
standing
up
a
sorted
network,
so
you
can
actually
start
doing
some
useful
with
it,
because
the
end
of
the
day,
what
nobody
will
admit
to
is
this
is
just
middleware
right.
I
mean
you
know
it's
a
different
kind
of
middleware.
It
has
some
interesting
characteristics
that
differentiate
it
from
other
middlewares.
You
may
have
worked
with
in
the
past,
but
middleware
is
only
as
useful
or
as
variable
as
the
applications
and
services
that
it
can
support.
A
So
there's
there's
a
sort
of
direction
of
travel
which,
if
you
were
in
the
talk
we
gave
this
morning,
we
went
into
this
in
more
detail,
but
the
direction
of
travel
for
the
community
as
a
whole
is
that
we're
actually
looking
at
kubernetes
a
substandard
or
default
runtime
environment
for
all
of
the
frameworks
and
all
of
the
tooling,
and
that
makes
sense
because
you
know
it-
everything
we
produce
in
today
is
a
set
of
docker
images
in
some
repository
somewhere.
So
then
deploying
those
standing.
Those
up
cuban
days
is
a
very
logical
choice.
A
It's
also
available
on
pretty
much
any
cloud
if
you
want
to
experiment
so
nowadays,
kubernetes
is
a
supported
service
on
all
the
major
cloud
providers
anyway
and
end
of
end
of
spiel.
So
if
that's
the
case
now,
let's
look
at
here
is
here:
is
you
know,
I've
logged
in
you
can
see.
I've
been
we've
been
deploying
a
whole
bunch
of
different
environments,
so
some
it
says
are
purely
creative.
What
does
that
mean
if
I
drill
down
on
that?
A
That
means
that
we
have
here
a
kubernetes
cluster
that
we
and
in
classic
cooking
terminology
it's
one
we
stood
up
earlier.
It
takes
five
to
ten
minutes
to
stand
up
so
so
now
we
can
then
go
in
and
actually
specify
the
Sawtooth
configuration
we're
going
to
make
this
a
standalone.
So
it's
going
to
have
its
own
Genesis
block,
we're
going
to
go
with
the
poet
we're
not
going
to
put
in
any
custom
TPS,
but
we
will
enable
the
tic-tac-toe
transaction
process
and
then
deploy.
A
Okay,
so
what's
happening
now,
as
you
can
see,
if
you
unpacked
sort
is
it
has
the
notion
of
a
validator,
so
a
validator
is
is:
is
a
node
in
the
network,
so
you
get
a
sawtooth
Network
consists
of
a
network
of
of
validators.
In
addition,
we
have
a
monitoring
service
which
were
not
guys
you're
going
to
use
right
now,
but
that
that
lets
you
that
introspect
what's
actually
happening
under
the
covers,
so
it
uses
something
called
influx,
DB
and
gravano
to
visualize
that
data.
A
So
that
gives
you
a
sort
of
a
way
of
introspecting
what's
happening
on
sawtooth,
but
we're
more
interested
in
doing
is
actually
playing
tic-tac-toe,
so
at
the
moment
is
bringing
up
the
the
validators.
What
does
that
mean?
That
means
that
we're,
basically
in
communities
terms
we're
taking
a
manifest
that
describes
the
the
actual
configuration
we
want.
So
we
want
we've
got
a
three
node
could
raise
cluster.
We
want
to
run
a
validator
on
each
of
those
nodes
as
soon
as
that
comes
up
which,
hopefully,
we'll
do
in
the
next
couple
of
minutes.
A
A
Right
so
this
this
one,
we
we
fired
up
a
couple
of
hours
ago,
so
if
we
now
open
the
so
this
is,
this
is
basically
hands
up.
Who
knows
how
to
play
tic-tac-toe?
It's
probably
the
easiest
question
you've
been
asked
all
all
week:
okay!
Well,
some
of
you
know
and
the
rest
of
you
are
refusing
to
admit
that
you've
ever
played
noughts
and
crosses.
So
what
we're
going
to
do
is
we're
going
to
create
a
game.
So,
let's
think
about
what's
happening
here
this
this
looks
awfully
like
a
standard.
A
You
know,
client
app.
Well,
guess
what
that's,
because
it
is
a
standard,
client
app.
However,
what
it's
doing
is
it's
it's
going
to
interact
with
on
the
backend
the
server
side.
A
thing
in
sort
is
called
a
transaction
processor,
and
it's
going
to
we're
going
to
ask
it
some
very
simple
things:
we
like
to
create
a
game
so.
A
All
right
when
in
doubt
bear
laugh
on
that
guy
come
back
to
this
guy,
which
hopefully
has
deployed
by
now.
Yes,
right,
let
me
start
again.
This
is
talking
to
a
completely
separate
Sawtooth
networks.
The
beauty
of
this
is
I
can
have
as
many
of
these
as
I
like,
so
when
one
doesn't
work,
throw
it
away
start
another
one,
probably
not
a
good
advert
for.
A
A
All
right
victory,
oh
now,
I
will
now
quit
while
I'm
ahead,
I've
now
created
a
game.
Unfortunately
they
would
say
it's
not
a
very
interesting
game
just
now,
because
no
one's
made
a
move.
So
let's
take
a
step
back.
What
are
we
doing
here?
This
is.
This
is
really
being
used
really
to
just
teach
people
some
of
the
basic
concepts
so
I
have
a
client
that
client
lets
me.
Initiate
transactions
in
this
case
create
a
game.
It
also
lets
me
take
spots
so.
A
Interesting.
Okay,
so
can
you
see
what's
happened
here?
So,
although
this
is
a
terrible
demo,
a
free
admit
her
eyes
caught
up
so
I
attempted
to
take
the
same
space
again.
So,
even
though
my
client
genuinely
thought
that
that
space
was
was
available
on
the
back
end,
the
transaction
processor
is
maintaining
the
state
of
this
game
and
already
knows
that,
even
though
the
the
I
had
the
information
hasn't
flowed
back
to
the
client
that
space
has
already
been
taken.
A
A
Is
you
know
those
transactions
when
they
come
through
are
being
compared
with
the
state
of
the
world
as
understood
by
the
blockchain
and
clearly
tic-tac-toe
is
a
kind
of
naive
example,
but
if
we
continue
to
play
now,
it's
happy
because
we're
now
back
on
turn,
but
if
again,
if
I
try
and
take
doubles
so
double
spend
where
you've
all
familiar
with
the
concept
you
know,
is
spending
the
same
money
twice
here.
It's
making
this
yeah,
it's
essentially
saying
I
want
to.
You
know,
make
two
moves
rather
than
one.
A
A
There's
now
two
flavors,
there's
poet
SGX,
which
does
require
the
underlying
hardware
in
this
poet
the
proof
of
the
elapsed
time,
which
is
a
generalization
of
that.
That
does
not
require
the
the
Intel
chipset.
So
so
we've
moved
on
from
when
it
when
it
was
sawtooth
like
it
was
originally
contributed
to
the
community.
That
was
very
much
the
focus
proof
of
elapsed.
Time
was
was
geared
towards
SGX.
A
Love
that
question
I've
been
asked
it
for
the
last
couple
of
days.
The
simple
answer
is:
is
the
modularity
of
sawtooth?
The
fact
that
it's
you
know
it
is
extremely
simple.
If
you
look
at
the
number
of
components
there
are
validators,
there
is
a
network
of
validators.
Each
validator
has
a
number
of
transaction
processes
hanging
off
of
it.
You've
got
the
clear
separation
between
the
network
which,
after
the
global
state
and
they're,
both
the
save-the-world
have
in
the
history
and
the
TPS
which
are
at
the
application
level
are
not
completely
separate.
A
So
you
can
take
your
existing
knowledge
experience
of
things
like
client-server
development
and
apply
that
directly.
So
the
only
thing
you've
got
to
think
about
is
the
state
model
and
making
sure
you
understand
what
should
be
stored
on
chain
versus
what
does
not
need
to
be
stored
on
chaim,
but
it's
a
very
simple,
very
clean
application
development
model,
and
then
the
final
thing
is
there
is
first-class
support
for
solidity
and
for
web
assembly,
which
is
built
into
into
sorties.