►
From YouTube: Core Devs Meeting
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
Hello
and
welcome
everyone
to
the
tenth
stutter
steps
meeting
the
first
one
for
this
year,
we'll
start
with
some
swarm,
updates
or
1530
minutes
and
then
go
through
some
hot
topics.
So
first
there
is
say
the
sine
of
U
that
s
is
going
to
go
through
and
then
also
talking
about
a
security
security,
vulnerability
in
react,
native
desktop
and
then
at
the
end
we
can
have
if
there
are
any
specific,
quick
announcements
and
thank
you
eager
for
hosting
this,
and
thank
you
Rachel
for
taking
notes
so
start
with
the
swarms.
B
C
B
B
Something
that
I
found
really
interesting
about
our
brainstorming
was
that
we
kind
of
created
a
create
an
idea
of
how
onboarding
users
that
don't
have
any
crypto
for
using
the
the
status
and
even
the
teller
network,
and
this
would
be
like
for
you.
You
basically
asks
for
someone
to
be
your
lawyer
or
not
not,
especially
especially
a
lawyer,
I,
think
that's
not
like
a
warrant
er
subsidiary.
B
B
B
If
we
want
to
support
issue
restriction
limits
like
some,
for
example,
for
United
States
people,
we
want
to
support
KEYC
about
the.
If
we
want
to
have
the,
how
do
you
want
wait?
We
want
to
deal
with
the
privacy
of
the
transactions
if
we
want
to
list
prices
in
died
or
if
we
want
to
support
died
as
it's
the
base
and
yeah
I.
Think
that's
enough,
and
also
about
we
discussed
a
lot
of
the
user
flows,
how
they
about
the
designs,
how
they
should
be.
C
Two
fronts,
one
is
the
is
the
more
long-term
and
kind
of
really
more
complex
front,
which
we
discussed
all
our
wish
list
and
all
the
stuff
we
want
to
do
and
how
we
want
to
do
it
sooner.
Another
one
is
more
than
more
immediate
NPP,
so
the
more
immediate
MVP
we
don't
have.
Never,
we
have
a
basic
working
app
that
what
move
our
desktop?
C
The
user
can
buy
a
license
to
sell,
there's
an
escrow
mechanism
dispute
resolution.
There
is
a
there's
also,
you
might
require
prices
for
whatever
what
the
escrow
exchange
will
be
support
for
multiple
ERC
20
tokens.
We
can.
We
can
already
rate
also
the
transactions
and
get
overall
rating
for
the
seller.
C
I
mean
there's
stuff
that
is
more
cold,
wise,
lucky,
like
story
book
and
stuff,
like
that,
multiple
tasks,
good
test
coverage
and
we
we
call
star
functionality,
list
the
available
sellers
and
what
else-
and
we
just
did
also
two
yet
for
users
to
allow
users
to
open
arbitrage
case
and
I've
and
we're
working
now
on
the
arbitration
UI
for
that
arbitration.
So
that's
what
we
have
now
with
a
VP.
B
D
A
E
Can
you
hear
me
yeah,
okay,
so
for
tribute
to
talk,
we
are
starting
to
work
on
the
screens
and
we
are
doing
a
specification
of
the
contracts.
So
we
start
with
the
father
MVP,
with
a
simple
tribute
to
talk
where
you
pay
the
tribute
with
the
regular
transaction.
So
the
contract
is
a
very
simple
contract
that
just
managed
the
tributes
and
allows
want
to
check
what
the
tribute
is
for
a
particular
address
and
that's
it
for
now.
F
F
We
agree
that
this
is
the
right
direction.
The
andrey
spent
some
time
implementing
the
smoke
apps
and
this
week
I
will
try
to
to
glue
the
mock-up
with
contracts
and
actually,
by
the
way,
ricardo
did
some
some
work
on
this
contract
to
the
one,
eventual
open
question
that
I
would
like
to
raise
it
that
for
the
MVP
we
probably
will
not
consider
esc
721,
but
it's
still
open
to
disk.
So
if
someone
has
an
opinion
around
that,
that
would
be
appreciated
and
that's
it.
A
G
G
You
know
I
put
forward
a
proposal
about
using
some
simple
bonded
curves,
but
that
obviously
still
needs
to
be
validated
by
others
and,
like
I
say,
we've
got
a
little
bit
of
a
lack
of
resources
on
the
swamp,
so
hopefully
we
can
experiment
with
more
bounties
and
sort
of
external
contributions.
While
the
p0
work
that
everybody
else
is
doing,
it
goes
ahead.
Full
steam.
H
Okay,
so
yeah
we
are
continuing.
Our
research,
like
I'm
Dre
I,
did
like
one
of
the
ideas
of
incentive
civilization,
our
current
infrastructure,
meaning
like
whisper
and
mail
servers,
but
for
the
next
week
we
wanna
also
take
a
look
like
taken
into
account.
That's
there
is
also
a
protocol
research
happening,
so
we
want
something
like
more
broad
and
more
applicable
and
future
proof.
So
next
people
want
to
have
some
research
around
this
people
want
to
have
some
research
on
something
like
differend.
H
H
For
the
improvements
there's
a
different
situation
there
we
just
there
is
no
much
research
there
to
just
that-
we're
implementing
things.
So
what
we
actually
did
is
we
wrap
up
the
quicker
login,
so
it's
very
very
fast
on
at
least
my
phone
and
on
even
on
the
small
palms,
it's
very
quick
and
it
should
be
released
in
the
internal
release
that
we'll
have
this
week.
Hopefully
the
second
thing
that
we
also
added
a
second
password
for
Android
as
well.
H
So
it's
right
now
have
this
feature
as
well
as
iris,
but
there
is
some
more
things
to
do
there,
so
I
don't
consider
it
implemented
completely,
because
we
also
need
to
like
improve
how
it's
two
stores
passwords
in
both
places.
So
it's
around
like
30%
in
and
also
like
half
done
with
a
reliable
messages.
So
pruning
was
I.
Guess
it's
already
in
status
go,
but
it
needs
to
be
deployed
to
work
properly,
and
there
are
a
few
things
to
regarding
questions,
email,
server,
confirmations
and
mail
server
management
in
general.
H
H
Just
use
some
master
or
some
current
version
of
two
sets
and
the
last
one
is
that
there
is
some
more
was
done
with
BFS
and
device.
Think
I
think
we
will
actually
work
on
it
like
this
week,
probably
because
it's
also
might
clash
with
tribute
attack,
so
they
need
some
coordination
there.
So
that's
so
for
us.
A
Cool,
thank
you.
I'll.
Do
the
vertical
update,
so
mainly
two
things
have
been
done,
so
one
is
workshop
preparation,
so
we're
gonna
meet
just
before
Fossum
in
Brussels.
End
of
January
will
be
five
to
seven
people
from
sellers,
so
working
of
agenda
and
making
it
as
useful
to
as
many
people
as
possible.
The
other
thing
is
proof
of
concept
for
a
sort
of
data.
A
You
can
sort
of
swap
whisper
out
and
so
on,
while
still
being
able
to
sync
data
appear
to
be
away,
and-
and
in
this
proof
concept
there
is
a
proto
buff
specification-
that's
wrong
in
some
places,
but
it
gets
the
gist
of
it
across
as
well
as
a
sort
of
basic
simulation
in
in
in
Python.
That
has
some
unreliability
assumptions
and
also
deals
with
mobile
notes.
A
Having
slightly
different
characteristics,
then
something
like
a
desktop
note
where
a
mobile
node
does
this,
maybe
almost
you're
flying,
but
sometimes
it
goes
online
and
then
sort
of
for
a
one-to-one
chat
and
so
seeing
how
how
the
system
behaves
so
I
did
a
short,
write-up
and
all
force
to
make
them
links
to
it
in
the
notes.
If
you
want
to
have
a
look
and
yeah,
please
ask
questions
or
just
specific
things
that
you
want
to
go.
You
wanna!
You
want
me
to
try
to
answer
with
this
answer.
Further
proof
of
concept,
and
so
on.
A
D
But
the
UI
itself
is
essentially
the
feature
complete
for
them,
which
means
you
can
create
a
giving
profile,
a
delegate
profile
or
except
offer
a
project,
and
ever
can
create
a
pledge
that
fun
can
fund
the
pledge
and
elected
delegate
and
a
dog
it
could
fund
projects
and
they
give
rican
veto
or
and
projects
can
ultimately
withdraw
those
funds
after
the
commit
period.
So
from
that
perspective,
it's
feature
complete.
D
But
we
were
just
thinking
about
sort
of
what
what
still
needs
to
be
done
to
these
contracts
from
their
perspective
and
from
ours,
where
there's
mutual
overlap,
and
also
to
see
the
differences
to
understand.
Maybe
there
needs
to
be
like
a
broader
use
case
to
to
generalize
them
more
to
accommodate
these
sort
of
broader
use
cases,
but
that's
where
it
currently
stands.
D
I
D
D
J
Basically,
we've
been
meeting
regularly,
we
had
to
design
reviews
last
week,
and
so
we
were
I
think
it
it
was.
The
process
was
pretty
good.
We
just
want
to
make
sure
that
we
have
engineers
attending
each
design
review
to
make
sure
that
everything
that's
being
proposed
is
feasible
and
it's
good
to
further
engineers
to
be
able
to
give
input
and
have
a
heads
up
on
on
what's
coming
along
other
than
that
I
think
progress
is,
is
it's
going
well?
J
For
the
most
part,
the
one
thing
that
I'd,
like
to
kind
of
request
from
everyone,
is
for
all
the
swirlies
to
make
sure
to
put
in
the
number
of
hours
that
is
happening
on
the
swarm
into
the
spreadsheet.
That's
been
sent
on
by
email
just
so
that
we
can
keep
track
of
budget,
and
so
when
we
give
updates
at
the
town
moles
we,
you
know
the
budgets.
This
needs
to
be
to
the
to
the
dot
but
say
plus
or
minus.
J
In
terms
of
actual
engineering
progress
where
everyone's
using
pivotal
tracker
and
I
some
teams,
using
it
more
than
others
and
people,
are
some
teams
just
getting
used
to
using
it
the
board
that
we
use
that
the
better
it
becomes
in
the
more
effective
it
is
and
Yuri
can
probably
give
a
good
spiel
on
on
how
great
it's
been,
especially
for
for
his
team.
So
yeah,
those
two
things,
one
make
sure
the
hourly
rates
for
the
families
are
coming
in
and
just
get
them
at
the
team
meeting.
J
It
shouldn't
take
more
than
like
30
seconds
and
then
yeah
continuing
to
use,
pivotal
tracker
and
making
sure
the
granularities
at
around
the
right
right
level
so
that
it's
not
just
one
issue,
that's
being
worked
on
for
multiple
weeks,
but
you
know
we
can
like.
If
the
issue
is
too
big
break
it
down
into
smaller
issues.
A
If
you
want
to
do
that,
I
think
it
would
be
great
because
it
gives
sort
of
other
people
are
very
good
for
ways
of
seeing
what's
what's
happening
and
so
on.
It's
also
a
way
to
clarify
your
your
thoughts.
So
so,
maybe
if
you
right
after
beforehand-
and
you
just
put
it
there
and
then
you
just
say
it
and
it
just
it-
makes
you
think
about
like
what's
what's
actually
changed
so
this
an
idea
would
be
great
if
we
can
keep
them
updated,
so
the
states
care
if
it's.
A
E
Real
cool
free
course
on
that
is
to
review
digital
tracker
and
also
update
it
so
either
way
we'll
be
mindful
of
that.
It's
also
worth
noting
that
we
are
also
there
in
their
research
phase.
So
if
you've
got
any
feedback
on
how
things
are
going,
if
there's
anything
that's
on
like
Moodle
any
way
we
can
improve
our
processes.
A
F
Can
give
some
update
on
Ambrose,
oh
yeah,
if
you
want
yeah?
Yes,
mostly,
we
try
to
to
take
her
the
number
of
flow
and
getting
fruits
related
to
what
we
consider
it's
unsure.
So
things
like
fixing
Universal
inks
in
Brazil,
or
making
sure
that
you
can
resolve
well
II
theorem
production
URL.
Well,
whatever
something
technical
or
so
we
worked
on
some
AI
peace.
F
No,
because
we
are
browser,
so
we
try
to
work
with
all
the
other
browser
making
sure
that
we
we
only
implement
the
same
set
of
AI
piece,
and
we
have
the
number
of
rings
and
and
chats
to
discuss
that.
So
we
currently
like
two
different
AI
piece
that
different
teams
are
pushing
and
mostly
metal
mask,
but
we
are
also
every
industry
in
that.
F
So
Andre
did
a
lot
of
work
around
that
last
week
and
finally,
in
parallel,
I'm
trying
to
to
finish
the
cable
extension
and
making
sure
that
all
the
relevant
extension
changes
are
being
implemented
and
I'm
pretty
happy
that
last
week,
I
was
able
to
do
like
my
first
exchange
with
the
cable
extension
so
hopefully
like
very
soon.
We
should
be
able
to
even
make
this
like,
maybe
a
little
bit
more
public
and
maybe
writes
a
blog
post
or
something.
K
K
G
I
have
one
update
and
that's
that
wall
is
really
designed.
Specifically,
the
wallets
and
flow
poor
request
is
almost
ready
to
be
reviewed
and
tested.
So
that's
that's
something
new.
It
should
be
ready
during
this
week.
Probably
so
yeah,
that's
that's.
It
will
probably
prioritize
the
next.
The
next
task
on
our
like
on
our
next
calling
on
Thursday.
So
if
anyone
wants
to
be
in
the
loop
or
you
know,
did
either
pinned
us
or
or
join
the
call.
I
I
could
take
that
that
topic
I
put
up
earlier
and
the
process
of
going
through
the
dependency
for
rat
native,
desktop
I
found
I've
submitted
a
bunch
of
PRS
to
fix
some
of
the
issues
that
snake
had
with
the
dependencies
there.
But
one
of
them
that
didn't
have
an
automatic
fix
in
terms
of
just
upgrading
a
dependency
is
a
high
severity
bug
in
the
yeoman
generator,
which
allows
arbitrary
command.
I
Injection
I
have
submitted
an
issue
and
reacted
of
desktop
and
I,
and
it
hasn't
gotten
much
attention,
but
that
we
really
need
to
look
into
also
made
a
big
mitigations
for
this
and
that
they
involved,
like
all
input,
validation,
to
make
sure
that
people
can't
take
advantage
of
this,
and
it
probably
seems
to
react
native
as
well.
So
if
I
can
get
more
people
looking
at
this
particular
issue
to
find
out
how
we
can
mitigate
it,
because
it's
not
one
of
those
things
where
you
just
upgrade
the
dependency
and
it's
fixed.
So
it
says
that.
A
I
K
I
K
K
Unfortunately,
shell
jeaious
library
itself
does
it
doesn't
have
the
fix
for
this
I
checked
and
they
are
not
going
to
fix
exactly
that
API
in
methods
that
is
vulnerable
to
have
a
backward
compatibility,
but
they
are
going
to
introduce
a
new
like
more
safe
method
instead
of
this
one,
and
if
this
is
iam
and
generators,
it
depends
of
this
shell
jsn.
This
call
to
the
function.
I
hope
they
also
take
advantage
of
a
new
method
when
it's
released.
Shell
Jas
can.
A
H
Yeah,
so
the
main
work
happen
right
now
is
on
especially
looking
down
on
the
versions
of
software
use,
so
some
of
that
is
being
done
by
Pedro,
he's
right
now
kind
of
changing
how
we
build
our
the
both
linux
and
windows.
So
we
love
that
pretty
much
everything
in
terms
of
versions
and
I'm
finishing
work
on
the
same
same
thing
for
Android
and
once
both
of
the
roles
are
done,
we
can
promote
report,
also
development
locally
into
docker.
H
L
Last
week,
Friday,
we
added
two
pivotal
tracker:
our
projects,
okay,
called
testing
and
most
of
the
tasks
like
last
week,
like
common
tasks
for
testers,
were
release.
Testing,
like
we
had
I
believe
four
or
five
bills
to
test
now.
It's
still
in
progress
because
we
are
waiting
for
status,
go
updates
to
test
with
this.
As
soon
as
it's
done,
we
will
also
test
battery
consumptions
there
and
probably
performance
testing
just
to
make
sure
that
that
we
can
measure
it
automatically.
Also
for
test
automation.
We
have
tasks
to
automate
upgrade
on
Android.
L
For
the
beginning,
it
will
be
upgrading
this
like
empty
account,
but
the
next
step
would
be
also
to
create
more
charts
and
see
how
it
goes.
These
upgrades
with
real
data
and,
as
usual,
writing
test
cases,
updating
them
for
the
new
features
or
modified
features
and
testing
nightly
builds.
So
there
are
like
more
or
less
repetitive,
tasks
for
like
nightly
release,
testing,
updating
their
cases
plus
for
test
automation.
You'll
have
like
some
focus
like
upgrade
battery
consumption,
the
foreman
stations
in
different
scenarios.
That
also
will
be
described.
That's
it.
C
Yeah
I
could
I
mean
we
I
mean
a
lot
actually
stock,
we're
doing
any
work,
it's
related
to
the
talent,
Network
and
the
Dow,
in
the
sense
that
we
we
sound
tongue.
While
during
the
channel
network
we
see
bugs
that
we
find
bugs
a
bit
fixing
or
for
a
feature
ideas
and
so
on
and
that's
been
quite
been
quite
useful.
C
A
M
M
M
Hope,
that's
feasible,
it's
pretty
basic,
but
none
of
it.
We've
scoped
it
as
I
work
for
at
least
most
of
the
swarms
I
thought
it
would
be
useful
to
give
you
a
quick
snapshot
of
the
current
allocation
by
team.
Looking
at
court
on
the
eye
is
the
key
context
for
core
under
core.
There
are
two
swarms:
currently
polish,
there's
onboarding
/
patient
zero,
which
Alma
is
also
working
on
and
network
in
sensitization,
which
culminates
also
working
on
then
similar
story
for
chats.
M
Where
much
is
the
context
for
the
team
yeah,
roughly
three
swarms
connected
to
that,
even
though
sticker
market
is
also
dab,
so
it's
not
necessarily
one-on-one,
but
the
swarms
that
much
a
is
responsible
for
it.
A
moment.
A
sticker
marquetry
to
talk
an
anti-spam
them
for
adapts
and
browser
story
changes
slightly
as
the
team
contact
is
and
will
remain,
to
be.
M
Dennis
who's
been
working
on
browser,
and
that's
a
lot
up
until
now,
specifically
for
the
DAP
store,
swarm
and
going
into
telling
Network
later
on
the
day
will
be
to
context
for
now
then
under
embark,
because
it's
a
little
bit
difficult
to
connect
the
swarms
to
all
individual
teams.
But,
let's
say
teller
network
for
telling
network
that
key
context
is
Dennis.
There
are
some
other
activities
going
on
always
that
demand
the
designers
attention,
but
for
now
the
ones
that
you
see
on
the
right
are
a
little
bit.