►
From YouTube: ECDC - DAY 1: Swarm POC3 by @acud
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
My
name
is
a
lot.
The
latest
addition
to
the
swarm
team
I
joined
the
about
three
months
ago:
I've
been
involved
in
various
projects
in
the
past,
from
stuff
in
media
and
to
real-time
homeland
security
systems,
embedded
systems
and,
in
the
last
couple
of
years,
also
bit
of
bread
and
other
corporate
back-end
web
systems.
A
A
Okay,
it's
pretty
good!
How
many
of
you
tested
it
managed
to
get
through
the
setup
stage?
Okay,
not
so
many,
and
how
many
of
you
are
building
applications
on
top
of
it
all
right,
okay,
cool!
So
let's
get
started
so
I'd
like
to
start
with
something
that
Victor
portrayed
as
something
very
clearly
as
a
but
I.
Think
for
those
of
you
which
are
not
familiar
with
swarm.
So
I
wrote
this
really
short
paragraph
about
what
it
is
or
what
it
is
for
me
and
what
it
means
for
me.
A
So
basically,
what
is
it
typically
content
addressed
storage
and
delivery
network,
and
it
is
part
of
an
integral
part
of
the
third
web's
vision
of
the
etherium
foundation.
It's
it
handles
archival
and
retrieval
of
data
with
a
bounded
incentivization
model,
which
is,
of
course,
material
and
it
serves
built
to
serve
web
applications
or
devs
with
real-time
messaging.
A
But
most
of
all,
it's
a
silly
world
of
acronyms
riddles
and
mnemonics.
So
soir
basically
defines
three
crucial
notions.
We
have
chunks,
hashes
and
manifests
so
chunks
are
our
most
basic
data
type.
They
are
limited
to
four
kilobytes
hold
the
arbitrary
data,
as
well
as
other
swarm
primitives,
which
we
will
get
to
and
they
are
redundant
over
the
network
right
now,
as
each
chunk
is
towards
three
times
on
the
network,
basically,
and
they
reside
or
being
actually
stored
on
the
in
the
closest
proximity
to
the
participating
nodes,
IDs
or
addresses
in
swarm.
A
The
notion
of
proximity
is
not
of
geographical
proximity,
but
of
basically
the
proximity
between
addresses,
which
we
do
using
an
ex
source
and
so
yeah
next.
So
basically,
what
are
chunks.
So
we
have
four
kilobytes
sharks,
which
are
split
into
128
32
byte
seconds.
These
are
being
hatched
with
a
binary
miracle.
B
A
And
then
we
get
the
binary
micro
free.
So
each
chunk
has
a
VM,
T
hash
and
swarm
hashes.
They
basically
represent
this
swarm.
Trees
of
hashes
with
a
single
contact
address,
shot
three
hash
of
the
content,
so
it's
basically
used
for
a
miracle
tree
representation
of
arbitrary
data
and
theoretically
collision-free.
A
So
we
said
that
chunks
are
four
kilobytes
in
size.
So,
basically,
once
we
have
basically
100
2828
chunks,
we
pack
them
into
intermediate
chunks
that
hold
up
to
128
hashes,
which
in
turn
are
used
to
get
one
root
hash
of
the
file,
so
files
are
retrievable
using
a
single
32,
byte
half
and
they
have
built-in
interpreted
protection,
as
I've
said,
using
the
Merkle
tree
and
support
hierarchical
encryption
and,
of
course,
due
to
the
fact
that
random
access
is
supported
on
the
lowest
level.
So
we
preserve
integrity,
protection
and
encryption.
A
A
A
Presentation
so
so
about
a
year
ago,
so
I'm
team
started
a
big
project
which
was
called
the
notorious
swarm
network,
rewrite
project
in
which
they
rewrote
basically
all
of
the
network
layer.
So
we
so
after
one
year
and
the
feature
branch
which
were
diverse
almost
about
thousand
commits
on
a
tiered
master.
On
the
longest
day
of
the
year,
we
released
swampy
oc3.
A
A
So
encryption
we
support
encryption
now
out
of
the
talks
using
counter
mode
encryption
which
enables
us
for
a
selective
disclosure
of
data,
meaning
you
don't
have
to
disclose
the
entire
content
of
the
data
that
you
stored
to
a
specific
hash.
But
you
could
store
a
whole
chunk
of
that,
like
the
whole
chunk
of
data
encrypted,
but
you
could
disclose
just
a
part
of
it.
A
Without
revealing
the
encryption
keys
for
the
entire
content,
it
will
be
user,
complete
with
the
cooperation
of
access
control,
trees,
which
we
hope
to
start
hacking
through
next
month,
and
you
could
distinct
encrypted
content
from
uploaded
content,
since
it
has
a
double
length
right
now.
It
is
not
deterministic
or
let's
say
it's
not
deterministic,
and
not
it
impotent.
Due
to
the
fact
that
we
generate
random
encryption
keys
on
the
fly
when
you
upload
something.
However,
this
will
be
addressed
in
the
future,
with
introduction
of
user
provide
encryption
keys.
A
A
A
A
And
so
it's
basically
know
to
note
messaging
service.
Oprah's
warm
important
to
mention
is
that
the
mail
there
is
no
mailbox
in
or
persistence
in
any
way.
At
this
point,
although
we're
trying
kind
of
take
a
crack
on
how
to
do
male
boxing,
but
it's
not
that
straightforward,
it
is
encapsulated
using
whisper
hands
and
it
is
exposed
right
now
only
to
json-rpc.
So
you
have
to
use
basically
a
flag
that
we
introduced,
which
is
minus
minus
WS,
which
introduces
a
WebSocket
server
that
you
can
connect
to
and
use
JSON
RPC
calls
so
yeah.
A
Other
interesting
point
is
that
you
we
have
a
DC
Hellman
handshakes,
provided
when
you
use
our
handshake
modules
and
basically
PSS
offers
a
sliding
scale
of
anonymity
in
trade
of
performance.
So
you
could
basically
send
a
message
to
someone
using
PSS
without
revealing
the
address
of
the
receiver,
and
so
in
PSS.
The
receiver
is
the
node
that
can
decrypt
a
message.
A
A
So,
basically,
what
we
have
created
is
a
system
of
deterministically
issuing
updates
to
resources
on
swarm
through
a
fixed
entry
point.
So
you
have
a
hash
of
a
certain
beautiful
resource
chunk
which
swarmed
and
follows,
and
basically
brings
you
to
the
latest
updates
right
now,
it's
undergoing
pretty
extreme
refactorings
and
redesign,
but
it's
almost
merged
actually.
A
Yeah
and
the
big
change
which
we
which
was
introduced
now,
is
that
resource
updates
signatures
are
being
done
by
clients
and
in
the
past.
Basically,
the
nodes
had
to
verify
the
ownership
of
the
DNS
name
that
you're
updating
with
DNS.
But
now,
basically,
you
could
create
an
arbitrary
miracle
immutable
resource
which
has
basically
no
connection
to
the
NS
name.
B
A
We
had
to
write
a
network
simulation
framework
in
order
to
actually
simulate
how
the
network
behaves
and
to
actually
simulate
very
complex
behavior
of
nodes,
joining
and
leaving
a
network,
and
so
this
was
finally
merged.
This
was
used
during
this
war
network
rewrite
but
wasn't
much
on
master,
but
you
could
small
I
can
be
actually
that
visualizes.
A
A
B
A
This
is
just
just
the
overlay
of
this,
like
you
can't
really
it's
just
you
just
visualize
the
topology
here,
but
so
underneath
all
of
this
there
was
the
bill.
Please,
this
incredible
simulation
framework
which
they
had
to
really
grind
it
to
to
work
properly
and
be
able
to
actually
simulate
networks
which
drain
resources
pretty
quickly
to
run
on
a
single
machine
but
yeah.
So
this
is
another
big
milestone.
A
A
So
since
we
changed
a
lot
of
these
a
lot
of
these
easy
schemes,
so
we
have
to
reintegrate
into
mist
and
so,
as
I
said,
before,
we're
going
to
try
to
get
access,
control,
trees
implemented
in
the
near
future.
There's
a
few
evangelist
light,
client
developers
that
are
popping
up
and
trying
to
help
us
to
implement
actual
light
clients
for
for
mobile
and
the
racial
coding
is
coming
at
some
point
also,
but
we
have
been
given
the
directive
to
not
give
any.
A
Specific
dates
or
I
hope
you
can
understand
yeah,
so
I'm
enjoying
the
fun.
We
have
open,
Gator
room
that
you
can
come
and
gauge
with
us
source
code.
You
know
where
it
is.
Probably
this
link
is
for
the
swarm
gateways
and
we're
hiring
wants
to
join
the
team.
So
thank
you
and
if
you
have
any
questions.
B
Thank
you
so
much.
You
know
it's
really
exciting
to
see
small
cargo,
so
the
mutable
resources
stuff
is
what
interests
me
most.
It
seems
like
you
guys
have
made
some
really
really
good
progress.
There
simple
question
around
the
faulty
sink
because,
obviously
like
if
I
lose,
my
keys
and
I
can't
update
my
sites
or
whatever
content
I'm
serving
anymore
yeah.
What
specifically
is
blocking
you
there
do
you
have
any
sense
of
how
easy
it
would
be
to
fix.
Well.
A
I
think
they
just
didn't
get
to
that
yet
right
now,
it's
more
about
finalizing
the
implementation,
because
we
we
had
a
dependency
on
EMS,
basically
to
to
issue
updates
on
the
network.
So,
basically
now
we
actually
decoupled
from
DNS
in
that
manner,
for
for
the
verification,
and
also
for
the
verification
that
notes
do
when
they
pass
along
chunks.
So
to
see
that
these
chunks
are
not
basically
updates
issued
by
somebody
that
just
wants
to
hijack
your
content
so
yeah
that
was
pretty
much
redesigned.
A
Also,
we
don't
use
block
Heights
for
for
issuing
updates,
but
rather
now
just
UNIX
epoch
times
instead
and
yeah,
but
the
multi-sig
updates
I
have
to
check
with
Louis
about
I,
can't
give
you
an
informed
answer
about
this,
but
I
know
that
they
have
it
in
view.
So
this
is
definitely
something
we
are
talking
about.