►
Description
The µRaiden network allows unidirectional off-chain (and thus cheap and fast) transactions. Demo included.
Slides: https://docs.google.com/presentation/d/1oY-WHOOWFSmGOkr1oyAYziJFrEoV9FYTsa35PcP3gfo
Recording and editing by https://twitter.com/alexboerger
A
A
I'm
have
to
run
full
okay
out
I'll,
try
to
speak
louder,
so
I
had
I
have
to
run
a
full
chain
for
the
demos
to
work.
So
that's
why
I'm
not
sure
that
I
can
I'm
I
will
be
able
to
actually
show
you
something
so
I
am
Loredana.
I
have
been
working
with
brain
bot,
developing
micro
rating,
so
I
am
one
of
the
developers
now
how
many
of
you
have
heard
about
rating
network
or
a
micro
Radin?
A
Okay,
that's
good!
How
many
of
you
have
heard
about
state
channels
or
payment
channels?
Okay,
so
both
Radio
Network
and
micro
Radin
use
payment
channels
as
a
scaling
solution.
The
difference
between
them
is
that
micro
Radin
is
a
framework
for
off
chain
payment
channels,
but
unidirectional
from
many
to
one,
as
opposed
to
rate
and
network,
which
is
many
to
many.
So
reading
network
is
more
complex
in
the
sense
that
it
has.
It
needs
routing.
A
It
needs
fees
to
incentivize
nodes
in
the
system,
so
they
can
route
payments
without
having
to
always
open
channels
between
the
sender
and
receiver.
So
that's
why
micro
Radin
is
actually
free
offers
free
off
chain
transactions
because
you
open
a
channel
and
it's
only
you
and
the
receiver.
Are
you
sending
tokens
to
the
receiver
so
that
doesn't
cost
anything.
A
Micro
readin
is
available
now
on
the
main
net
and
the
test
nuts
robson
ring
B
and
kovin.
The
version
is
zero
point
two
and
it's
a
another
bug
bounty
release.
So
after
we
see
what
happens
now,
please,
if
you
want
to
look
at
the
contracts-
and
we
actually
had
a
very
successful
bug,
bounty
release
version
0.1
and
we
actually
changed
some
of
the
code.
That
was,
we
didn't.
We
didn't
find
any
important
bugs,
but
if
there
were
some
some
advices
that
we
took
into
consideration,
so
please
have
a
look
as
use
cases.
A
A
Okay,
so
I
have
my
micro,
raid
and
server
working
here,
and
this
is
the
option
chain
syncing
and
we
have
a
paywall
here
that
wants
us
to
open
a
channel.
We
have
metamath
connected
and
we
already
have
39
tokens
as
a
deposit.
Here
we
can
deposit
nine
tokens.
This
will
take
a
bit
because
this
is
an
on
chain
transaction.
So
opening
the
channel
happens
on
chain
and
we
can
follow
the
transaction.
A
A
A
A
So
opening
a
channel
topping
it
up
with
tokens
closing
the
channel
and
we
have
also
added
a
withdrawal
function.
So
now
the
receivers
can
withdraw
their
tokens
from
the
open
channels.
So
that's
why
these
channels
will
will
be
long-lived
because
the
service
providers
can
actually
withdraw
tokens.
Yes,.
A
A
Yes,
for
example,
even
at
this
point,
if
we
store
the
temporary
channel
data
in
the
local
storage
of
the
browser,
but
we
can
also
retrieve
the
channels
from
the
blockchain,
because
opening
that
opening
the
channel
topping
up
has
events
on
chain.
So
we
can
look
at
those
events
and
retrieve
that
channel
data,
and
we
can
query
I'll
get
this
later
bit
when
I
actually
explain
how
how
it
works.
A
A
A
Api
is
for
whatever
you,
you
would
think.
For
example,
we
have
a
video
demo
online
and
we
have
an
example
of
querying
the
ether
price
and
US
dollars,
and
we
do
this
constantly
and
we
can
see
that
we're
sending
payments
these
sending
new
balance
proof
is
the
actual
payment.
And,
yes,
you
can
look
at
look
at
that.
I
also
prepared.
A
A
A
A
Okay,
if
this
time
it
doesn't
work
so
just
so
the
the
idea
is
that
we
already
have
an
open
channel
with
the
drone,
and
now
these
commands
just
are
done.
I
mean
you,
you
actually
pay
a
fee
for
for
each
command
and
then
you
can
fly
the
drone.
However,
you
want
hopefully
next
time,
I'll
actually
have
a
nice
interface
interface.
For
this.
A
A
So
we
can
also
make
it
I
mean
we
can.
We
can
also
pay
for
for
for
each
picture.
A
A
This
is
the
micro
raid
and
server
that
was
used,
so
we
import
some
some
helper
classes
from
the
server
and
then
this
is
the
resource
for
which
we
we
pay
and
I
just
put
in
the
all
the
commands
here.
So
it
would
have
been
nicer
to
separate
the
commands
and
do
separate
api's
for
them.
But
I
just
wanted
you
to
see
how
easy
it
is
to
actually
set
up
a
machine
to
machine
a
server
and
client
for
for
this
type
of
use
and
then
the
client.
A
A
So
we
have,
we
have
the
repository.
It's
open
source
at
Raiden,
Network
micro,
Raiden
I,
told
you
about
the
off
chain
payments,
so
the
channel
data
is
contains
the
receiver
address
and
the
sender's
address
the
block
number
at
which
the
channel
has
been
opened
and
the
last
balance,
because
the
balance
is
always
increasing.
So
we
we
keep
the
last
glass
value
and
the
sender
also
and
the
receiver
keep
the
channel
data.
The
receiver
also
has
the
last
balance
proof
received
from
the
sender.
A
This
data
is
signed
by
the
sender,
and
this
is
the
actual
balance
proof
we
use
now
sign
type
data
as
a
standard
which
is
still
in
work.
So
that's
why
we
are
not
able
to
actually
have
a
stable
release,
because
we
are
also
waiting
a
bit
now
for
the
standard
to
be
implemented
and
the
nice
thing
about
it
is,
and
you
saw
when
we
are
actually
signing
the
balance,
proof
that
we
actually
see
text.
So
we
can
see
how
much
how
many
tokens
we
are
paying
to
whom
what's
the
contract
address
and
so
on.
A
Until
now,
this
wasn't
really
that
nice,
when,
when
signing
transmit
when
signing
messages,
so
the
sender
sends
all
of
this
data
to
the
receiver
and
then
he
gets
the
resource.
We
also
support.
We
support
the
ERC
20
NERC
223
tokens
up
until
this
point.
I
know
there
are
some
more
standards
coming
out
why
we
decided
for
year,
C
223,
mainly
because
of
lower
gas
cost,
because
we
only
do
one
transaction
for
opening
and
topping
up
channels
instead
of
two
transactions.
A
So
we
only
do
a
transfer,
and
this
actually
the
same
transaction
opens
the
channel,
the
ERC
20.
You
have
to
approve
the
tokens
first
and
then
you
can
create
the
channel,
and
this
is
it's
the
same
for
topping
up
about
closing
the
channels.
So
what
what
happens?
The
best-case
scenario
is
when
the
sender
and
the
receiver
actually
agree
about
what
amount
of
tokens
are
owed.
So
the
sender
queries
the
receiver
and
sends
him
his
his
balance.
Proof
and
then
the
receiver
signs
the
same
balance.
A
There
are
two
two
more
cases
when
the
receiver,
let's
say
he's
not
online
or
for
whatever
reason
he
doesn't
want
to
sign.
The
sender
can
close
the
channel
and
then
there's
a
challenge
period
in
which
the
receiver,
with
the
last
balance,
proof
that
he
has
stored.
He
can
close
the
channel
himself
or
after
the
challenge
period
has
finished.
Then
the
sender
can
settle
the
channel
himself
and
that
transaction
is
also
instant.