►
Description
The Scala Project joined us during the March meetup to talk about how they used IPFS to create a novel methodology to checkpoint block hashes to secure a blockchain.
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Join your local IPFS meetup to attend our next event: https://www.meetup.com/pro/ipfs/
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
A
So
hi
everyone,
I'm
mastermind,
which
is
obviously
not
my
real
name.
Well,
I'm
an
application
developer
at
scala,
I'm
with
hazam,
also
a
developer,
blockchain
developer
and
donovan
both
are
developer
at
scala.
We
are
very
excited
to
be
with
you
today
to
present
our
project
and
how
we
use
ipfs
technologies
within
our
ecosystem.
A
A
A
But,
first
of
all,
let
me
introduce
scala
and
we
are
and
what
we
do
so.
Our
first
goal
is
to
keep
privacy
as
a
priority
in
everything
we
do.
This
is
why
we
forked
from
monero
in
the
first
place
and
providing
a
pack
blockchain
untraceable
payments,
unlinkable
transactions
and
blockchain
analysis
resistance.
A
A
A
So
now
I'm
gonna
leave
I'm
gonna.
Let
donovan
for
the
next
part.
B
Yes,
thank
you
for
that.
One
of
the
goals
of
our
project
is
has
always
been
to
be
as
decentralized
as
we
can
possibly
make
it.
B
Another
goal
of
our
project,
like
it
was
just
mentioned,
was
to
have
ease
of
use.
We
want
to
make
it
as
simple
as
possible
for
anyone
to
get
involved,
and
for
that
reason
we
knew
that
our
ipfs
integration
needs
to
be
part
of
our
core
package
and
not
require
any
additional
dependencies
to
be
installed
or
any
additional
downloads
and
registrations
all
over
the
place.
B
Our
initial
integration
with
ipfs
was
actually
was
quite
low
level.
If
I
could,
if
I
could
call
it
that
our
library
would
set
up
initialize
and
run
ipfs
from
within
our
own
go
code.
What
I
mean
with
that
is
it.
We
used
a
lot
of
the
startup
logic
that
you
can
find
in
the
standard,
ipfas
daemon
itself,
and
we
ran
that
inside
of
our
library.
B
What
was
great
about
that
is.
It
allows
us
a
great
degree
of
control
of
what
we
start
and
what
we
don't
start
with
the
we
disabled
at
the
beginning,
the
http
api,
because
we
didn't
need
it.
The
other
reason
for
that
is
cryptocurrency
exchanges,
typically
don't
want
anything
other
than
the
core
network
tools,
because
they
don't
want
the
overhead,
especially
the
smaller
exchanges
that
don't
really
have
a
binance
kind
of
setup
to
to
operate
these
chains
on.
B
Apart
from
some
some
users
that
ran
a
very
restrictive
network
setup,
some
of
those
calls
were
blocked,
but
other
than
that
it
really
worked
really
well
fast
forward.
A
few
months
later,
we
reviewed
our
integration
and
we
found
that
dependency
management
in
the
long
run
is
going
to
be
really
really
tricky.
This
was
a
time
when
go
was
in
that
awkward
space
of
not
really
having
an
official
dependency
management
system
like
it
does
now
with
go
modules.
B
We
still
need
the
go
wrapper
around
ipfs
so
that
we
can
start
the
diamond
from
c
plus
plus,
but
instead
of
doing
all
the
work
initializing
the
network
and
connecting
and
all
of
that,
we
package
a
compiled,
ipfs,
binary
and
embed
that
inside
of
our
library,
with
a
tool
named
escape
or
esc,
and
when
the
daemon
starts
up,
it
calls
a
function.
It
extracts
that
package
starts
the
ipfs
daemon
and
we
can
communicate
then
using
the
http
api,
which
works
perfectly
fine.
B
What's
nice
about
this
approach
again
is
we
can
add
command
line
flags
to
our
c
plus
code
to
disable
that
functionality
for
exchanges
which
keeps
them
happy?
We
still
achieve
the
goal
of
not
having
additional
software
to
be
installed
by
our
users,
and
we
we
get
a
one
out
of
that,
so
that
we
don't
need
to
worry
about
dependencies
and
we
can
just
take
advantage
of
all
the
new
ipfs
functionality
as
it
becomes
available
by
just
repackaging
that
binary
into
our
code.
C
Hello,
everyone
hope
you're
all
doing
well,
I'm
gonna
start
by
actually
proposing
a
question:
why
do
we
need
industrial
security
for
the
blockchain?
Is
it
not
supposed
to
be
like
inherently
secure
without
the
free
third-party
applications?
C
I'd
say
it's
a
pretty
difficult
question
to
ask:
it's
not
a
necessity
for
a
point
like
bitcoin
or
something
like
that,
because
they
have
a
lot
of
miners
and
modes
and
all
this
stuff
to
ward
off
most
of
the
common
attacks.
C
C
So
before
we
jump
in
jump
into
how
their
image
is
all
the
problem,
let's
take
a
look
at
some
common
network
level.
Attacks
against
the
blockchain
in
particular,
distributed
denial
of
service
attacks.
C
They
are
pretty
common
on
blockchain
these
days
since,
if
you're
a
small
project,
especially
with
not
a
lot
of
players
hosting
the
chain,
it's
pretty
easy
to
take
out
with
those
that
are
good
to
cause
a
lot
of
havoc,
and
the
next
type
of
attack,
I
would
say,
is
cyber
attacks
and
recently
monero
had
this
very
specific
attack
for
a
bunch
of
nodes
pretended
to
be
honest
and
tried
to
find
origins
of
certain
transactions,
which
was
pretty
complex
and,
at
the
end,
was
able
to
pass
a
lot
of
problems
now.
C
One
of
the
best
in
the
market,
which
a
lot
of
coins
actively
use,
is
the
delayed
proof
of
work
by
komodo.
It's
actually
pretty
smart
as
well.
They
use
the
bitcoins
blockchain
to
store
arbitrary
data
in
this
case,
block
hashes
of
a
network
that
tomorrow
is
trying
to
protect,
and
it
is
regarded
as
one
of
the
go
to
solutions
for
a
lot
of
projects
at
the
moment,
especially
popular
ones
like
ninja
square
fire,
changes
for
professional
theories
and
another
solution.
That
is
also
pretty
popular
recent
times.
C
It's
just
pro
like
glasses
checkpoints
where,
basically,
they
just
don't
allow
any
kind
of
the
organization's
past
envelopes
in
the
past.
This
actually
could
cause
a
lot
of
issues
as
they
already
had
in
mind,
but
there
is
no
other
option.
C
So
now
that
we've
taken
a
look
at
some
of
the
existing
situations,
let's
take
a
look
at
our
solution,
which
is
called
dr
and
in
essence,
it
works
a
lot
like
kmd's
creative
work,
but
instead
of
using
the
bitcoins
blockchain
to
store
opportunity,
we
use
ipfs
since
it's
a
lot
cheaper,
faster
and
more
likely,
and
even
though
bitcoin
has
a
lot
of
compute
and
security
behind
it,
it
is
still
vulnerable
to
51
attacks.
C
Certain
nodes
that
consistently
take
block
caches,
which
are
blocks
in
the
network
and
then
publishes
those
block
hashes
along
with
the
height
and
some
other
parameters
onto
ipfs
and
then
ipip,
so
that
the
client
blockchain
demons
can
resolve
it
and
get
the
checkpoint
and
then
add
it
to
their
local
databases
and
then
the
way
we
pick
these
load
maintainers
is
by
a
yearly
election
that
this
gives
people
a
chance
to
be
a
part
of
this
secondary
network
and
also
decentralizes
some
of
the
power
that
these
notes
have,
because
they
have
a
lot
of
of
it.
C
Power
they're
also
incentivized,
with
tokens
from
the
network,
so
they
don't
have
an
incentive
to
cyber
attack
us
and
then
about
25
percent
of
the
blockchain
was
right
now
goes
to
location
on
our
network.
C
C
Yep,
this
is
the
thing
I
was
talking
about.
So
basically,
you
can
see
three
nodes
here.
They
are
taking
block
hashes
from
scalars
blockchain
right
now
and
then
adding
that
to
ipfs,
so
that
other
nodes
in
the
network
would
affect
these
hashes
from
here
and
add
it
as
a
permanent
block
so
that
there
cannot
be
any
organization
past
this
world
and
it's
pretty
cool
and-
and
I
would
say,
latest
update
pointing
it
is
really
fast.
A
All
right,
thank
you,
usm,
so
I
will
now
introduce
to
conclude
our
presentation,
some
other
users
of
ips
ipfs
in
our
project.
A
A
A
And
finally,
we
are
currently
working
on
phantom,
which
is
in
development.
It's
a
content,
delivery,
distributed
content,
delivery
network,
a
cdn,
it's
gonna,
hello,
allow
us
to
offer
our
users
a
secure
and
decentralized
file,
hosting
leveraging
our
ipfs
notary
nodes
and,
obviously
our
mobile
ecosystem.