►
From YouTube: What's next for the Berty Protocol - Manfred Touron
Description
Most people aware of Berty won't know that we've made an underlying protocol that could power many other projects. We want to change that and help more builders to create powerful dApps. Let's look at what problems we're addressing and how.
A
So
today
we'll
talk
about
dirty
protocol,
which
is
a
protocol
behind
yes,
after
brt,
we
made
multiple
presentation
about
the
virtual
Messenger
application
and
today
we'll
talk
about
the
protocol,
so
the
part
that
no
one
actually
knows
or
any
details,
so
I
meant
Freddie,
the
founder
of
brt
in
the
peer2pi
ipfs
lipid2p
ecosystem
and
a
core
team
member
of
blockchain
and
Noland
a
bit
of
context
about
BRC
messenger.
A
So
that's
messenger
is
a
mobile
first
application,
which
means
we
want
to
make
peer-to-peer
on
mobile,
which
is
clearly
not
something
easy,
even
in
2022,
with
privacy
with
a
privacy
Focus,
which
means
that
we
don't
want
to
leak
unnecessary
metadata,
which
is
also
another
challenge
in
the
P2P
ecosystem
and
ipfs
ecosystem.
A
It
is
local
local
first,
so
you
can
run
pertin
network
even
in
the
desert
or
in
the
in
the
in
in
a
very
isolated
region
of
the
world,
and
the
goal
is
to
make
something
that
can
work
in
good
condition
when
you
are
in
a
good
country
with
no
censorship,
but
also
some
things
that
will
resist
and
allow
you
to
make
extreme
Communications
in
extreme
cases.
A
The
battery
protocol
is
the
part
of
birds,
messenger
that
manage
basically
everything
related
to
peer-to-peer
encryption
everything
and
we
try
to
to
Define
where
it
should
be
compared
in
a
web
2
to
rep3
metrics.
So
if
you
consider
blockchain
to
be
the
equivalent
of
Visa
or
something
to
too
much
control,
ipfs
more
like
a
competitor
of
Amazon
S3,
we
are
more
competitor
of
Amazon
sqs,
so
for
everything
related
to
cues
and
history
of
queues,.
A
The
SDK
and
the
peer-to-peer,
the
SDK
sorry,
is
directly
used
by
the
battery
messenger.
So
on
mobile
you
have
one
application
running
a
full
apfs
node
and
we
have
some
kind
of
application,
oriented
rules
for
everything
related
to
messaging,
to
messenger,
sending
messages
and
attachment
Etc.
But
the
protocol
is
something
more
agnostic
that
you
can
use
to
basically
send
messages
on
metadata
or
binary
stuff
between
nodes,
and
always
we
are
doing
it
in
a
way
to
allow
to
remove
more
and
more
servers
from
your
decentralized
applications.
A
We
make
everything
to
make
unchecks
with
contacts
and
groups
as
and
then
you
will
just
follow
topics
and
participate
in
the
topic
and
sorry
and
you
are
using
rbdb
for
the
crdt
part
for
the
local
first
part
and
to
allow
people
to
have
no
consensus
but
still
have
real-time
application
and
to
make
everything
working
in
the
in
the
same
way
as
soon
as
you
have
all
the
same
data.
A
So
here's
a
probably
the
most
important
part
I
think
battery
protocol
could
be
something
very
useful
for
you.
If
you
want
to
make
real-time
application,
but
not
not
just
the
application,
because
you
can
use
ipfsp
or
not
just
something
mostly
right
right,
first
and
with
a
different
amount
of
people.
Reading
the
data
like
with
rbdb
by
default.
A
But
if
you
want
to
have
something
more
private,
more
content,
content,
oriented
and
topic
oriented,
we
will
you
will
have
by
default
identity
and
IC
and
ACLS
so
that
everyone
in
the
group
can,
in
a
trustless
mode,
participate
in
the
communication
with
full
privacy
of
the
communication
and
offline
communication.
First,
because
rpdb
is
pretty
good
to
support
network
splits.
A
But
if
you
are
on
the
mobile
ecosystem,
you
want
to
have
additional
Network
configurations
like
Bluetooth
Bluetooth,
first
Networks,
so
we
address
the
mobile
ecosystem
with
different
kind
of
networks,
whether
it's
device
management,
so
you
can
add
a
contact
and
then
the
contact
will
be
able
to
add
new
devices.
So
another
challenge
of
the
of
the
peer-to-peer
and
privacy
in
a
various
synchronous.
World.
Actually
you
can
add
a
contact
in
a
place.
You
can
split
your
network,
add
new
devices,
add
new
contact
and
everyone
will
be
able
to
follow
the
same
topics.
A
We
we
have
kind
of
identities
so
that
you
can
have
a
dedicated
topic
for
yourself
between
all
your
devices,
dedicated
topic
for
each
contact.
You
added
in
a
safe
way
and
dedicated
topic
and
sorry
and
dedicated
topic
for
each
groups
that
will
actually
that
won't
be
device
around
it,
but
contact
oriented
with
many
devices.
A
So,
even
when
one
communication
is
always
a
Multi-Device
communication
and
we
consider
that
we
have
some
kind
of
I
think
mesh
Network,
because
you
can
have
the
maybe
a
synchronous
mesh
network
with
ble
if
you
have
good
conditions,
but
you
will
mostly
have
in
synchronous
mesh
network
if
you
receive
a
message
from
someone
else
and
distribute
it
to
another
peer,
especially
with
Bluetooth,
and
we
have
many
optimization
in
the
app
life
cycle,
because
actually
ipfs
runs
very
well
on
big
servers
with
big
bandwidth
Etc,
but
on
mobile.
Your
application
is
going
foreground
background.
A
A
We
have
a
blockchain
which
wants
to
create
a
universal
interface
for
web3,
so
you
have
one
node
and
you
can
access
your
wallet,
your
content,
your
message
Etc.
So
something
very
communities
on
trick
as
it
wants
to
rely
on
the
probability
protocol
and
we
have
the
French
army,
which
is
working
on
Extreme
communication
experiments
because
they
want
to
explore
what
can
be
done
in
standard
internet
or
very,
very
local
internet.
A
Today,
the
battery
protocol
is
still
in
the
big
monolith,
so
like
ipfs
was
embedding
lip2p
for
many
years
and
then
it
was
splitted
out.
We
are,
we
are
doing
the
same.
So
today
we
have
a
big
monolith
and
we
are
extracting
the
protocol,
so
it
can
be
used
by
anyone
from
a
new
for
any
applications,
and
today
it's
not
ready,
but
we
are.
We
are
looking
for
people
that
wants
to
experiment
and
give
a
try,
so
we
can
make
the
SDK
the
API
contract,
etc,
etc.
Having
some
sense
for
the
end,
builders.
A
To
make
it
with
this
ID
to
change
the
name
to
because
battery
protocol
can
look
like
a
protocol.
Just
for
me
said
messenger
applications.
Actually
we
don't
know
me,
we
don't
want
to
meet
West
Network,
so
like
mesh
network
with
a
reverse
m,
to
actually
show
you
that
you
can
build
other
applications
and
not
only
Messengers.
A
We
also
have
other
libraries
that
we
developed
for
four
years.
We
are
we
developed
properties
on
your
Google
Mobile
apfs
in
the
epfs
ipfs
CPR,
the
organization
on
GitHub,
which
allows
you
to
embed
on
a
full
apfs
node
on
mobile.
We
developed
group
DB.