►
From YouTube: Core Devs Meeting #14 - Monday 11 March 2019
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
A
C
C
Andre
did
some
changes
wrong,
humbling
contract
interaction,
so
the
idea
was
to
reduce
the
transaction
being
performance.
You
you
try
to
buy
a
sticker
back
and
then
and
the
contract
was
it
front
when
we
are
still
in
the
process
of
auditing
the
contract,
but
that's
essentially
the
last
bit.
We
need
to
do
so.
That's
pretty
much
it
for
a
sticker
market.
I
can
continue
with
the
brazos
form.
C
Actually
so
Andre
implemented,
EAP
712
and
the
goal
of
this
EIP
is
to
provide
a
different
way
to
sign
data
from
within
you
adapt
so
like,
because
the
previous
weights,
who
are
signing
that
I,
was
really
a
string
based.
But
now
you
can
sign
like
more
complex,
structured
information,
so
which
is
actually
something
that
was
requested
by
a
number
of
external
DEP
developer,
also
is
starting
like
working
on
separating
gaps
in
a
separate
tab.
C
So
because,
right
now,
as
you
know,
we
have
both
chats
and
dabs
in
the
same
tab,
which
is
what
I
guess
one
like
feedback.
We
had
a
lot.
It
was
a
little
bit
confusing.
So
now
there
was
a
new
design
to
separate
this
in
three
different
apps
and
when
Andre
hijiri
started
and
he's
making
great
progress
on
that,
and
the
last
bit
we
are
working
on
is
on
creating
a
new
swarm
around
extension
and
the
idea
is
to
push
and
finally
have
extension
and
out
of
alpha.
C
D
Okay
for
the
true
to
talk.
Well,
the
trot
the
chat
swarm
in
general.
We
last
week
we
fixed
the
toolbars.
There
is
a
pending
PR
and
the
next
step
will
be
to
make
it
a
component
and
regarding
tree
to
talk,
we
are
in
the
final
touch
of
implemented
in
the
chat
UI
for
to
talk
that
the
settings
are
done,
but
there
is
a
few
things
that
we
need
to
still
figure
out
like
if
we
keep
them.
D
E
Go
on
the
deaf
store
stuff,
so
in
tandem
with
the
work
that
Julien
and
Andre
have
been
doing
on
the
various
different
browsers
changes
and
everything
that
he
just
detailed
now
we're
also
slowly
moving
ahead
with
implementing
messages
designs
for
version
1
of
the
taps.
Tour
there's
some
folks
in
Cape
Town,
who
are
going
to
help
us
do
that's.
E
The
initial
thinking
was
that
we
would
sort
of
managed
it
all
through
bouncies,
but
it's
a
fairly
large
project
and
it
seems
better
to
try
and
experiment
with
rather
sort
of
contracting
particular
organizations
to
do
the
full
load
of
work,
and
you
know
we'll
pay
and
cryptocurrency
and
all
that
kind
of
stuff
which
is
really
cool.
So
we
should
have
version
1
of
the
store
which
will
or
just
be
like
the
suggested
home
screen
icon
for
our
new
browser
tab.
E
That
should
be
done,
hopefully
in
the
next
two
weeks
and
in
the
meantime,
we'll
be
finalizing
the
contracts
and
hope
to
be
preparing
it
for
audits,
so
that
we
can.
As
soon
as
you
know,
the
navigation
PR
has
been
merged
and
we've
got
those
four
separate
tabs
at
the
bottom
of
the
app.
We
can
have
the
DEP
store
up
and
running
and
get
SMT
ranking
into
its.
Hopefully,
you
know
the
next
month
or
two
depending
on
how
the
contracts
or
let's
go,
but
that
stuff
is
moving
along
nasty.
F
So
yeah
so
for
the
Tor
network,
we're
finishing
and
adding
the
scroll
workflow
a
lot
of
other
UI
details
here
and
there
just
to
really
excite
the
apt
application.
We
created
this
data
seeding
system.
So
when
we
deployed
that
that
in
the
contracts
they
can
do
a
bunch
of
actions
automatically,
which
makes
it
much
easier
just
to
see
the
tap
in
action
and
instead
testings
more
more
easily
and
we're
going
to
be
deploying
the
tap
soon
again,
a
new
version
to
recopy
for
the
Dow
down.
F
G
I
can
go
I'm
working
on
top
democracy.
My
now
I'm
currently
researching
how
I
will
implement
the
veto
function
and
also
there
is
a
problem
with
the
allocation
of
essence,
not
a
problem,
but
a
characteristic
that
is,
there
is
some
balances
that
need
to
be
removed
from
the
total
column
because
they
are
like
not
actively
been
set
balances.
They
are
Lockette
balances.
G
So
there
is
these
two
things
that
are
working
on
top
of
democracy
and
also
I
am
researching
on
a
chair,
iam
J,
to
see
if
we
can
I
already
started
so
imparting
to
whisper
version
6
from
the
version
tree
that
is
returned
J
to
the
six
and
with
that
I
think
should
be
easy
to
build
something
for
status
in
a
TMJ.
If
someone
wants
you.
H
Because
eager
is
on
vacation,
I
can
tell
about
status.
:,
please
depart
so.
We
have
released
the
hotfix
last
week.
Mainly
it
was
about
possibility
to
cancel
the
tinned
mail
server.
So
when
you
selected
some
mail
server
as
your
preferred
one,
you
was
not
able
to
unselect
it
now
you
can
so
if,
for
some
reason,
mail
server
is
not
responding
or
whatever
behaving
in
a
wrong
way.
Now
you
can
just
cancel
and
have
the
app
to
select
any
other
mail
servers.
H
It
is
responding
and
behaving
well
and
we
also
added
some
changes
to
the
bottom
navigation
in
the
mobile
app.
So
the
tops
are
now
visible
as
a
home
and
wallet
and
profile
tabs
should
be
visible
when
you
navigate
actually
in
any
screen
as
I
know,
Pedro
you've
done
a
lot
of
say
changes
to
our
bills,
so
maybe
you
can
also
update,
beat
about
it.
A
The
end
of
this
week,
so
I
invite
everyone
to
to
give
it
a
try
and
see
if
they
find
any
kinks
or
if,
on
the
contrary,
everything
is
working
as
expected,
it
shouldn't
have
any
impact
on
the
existing
environment.
You
have
so
don't
be
afraid
to
give
it
a
test.
I
already
had
some
feedback
from
external
developers
who
reached
out
to
me
and
said
they
were
a
table,
for
instance,
to
build
Androids
and
after
trying
this
branch,
they
we
got
it
up
and
running
in
a
few
minutes,
so
that
was
good
sooo
to
see
yeah.
A
A
J
I've
got
a
few
things
on
from
the
security
perspective
this
week,
we'll
be
starting
a
retainer
with
trailer
bits.
They're
gonna
be
kind
of
watching
over
PR
suis
perdu,
watching
our
contracts,
we're
going
to
be
piloting
their
new
product
called
critic
that
basically
automatically
runs
integrates
with
github.
It
runs
all
their
tool,
sets
on
smart
contract,
pull
requests
and
then
notifies
according
to
whatever
issues
there
may
be.
J
That
should
help
with
a
lot
with
the
beginning
stages
of
all
the
the
audits
that
are
currently
being
done
on
all
the
swarms
and
if
we
need
another
third
party
audit,
a
full
audit
than
one
before
with
that,
after
the
initial
like
overview
from
them.
Also,
today
we're
launching
our
private
campaign
with
hacker
one,
so
we
can
extort
potentially
saying
bugs
come
in,
hopefully
not
too
fast
on
any
and
that's
the
scope
of
these
is
any
of
the
current
public
releases
of
the
application
and
the
infrastructure
that
serves
that
applications
of
the
website.
J
Basically
and
we'll
see
bugs
come
in
from
there
from
whatever
hackers
they
invite
and
the
private
campaign
that
will
still
to
increase
so
we're
trying
to
keep
a
cadence
of
around
five
valid
bug
reports
per
month
and
then
I'll
be
handling
those
and
dishing
them
out
to
whoever
whoever
needs
to
mitigate
whatever
whatever
comes
there,
so
expect
to
hear
that,
hopefully
not
too
much
but
regularly
over
the
next
few
months.
Coming
from
hacker
one.
D
D
We
are
also
working
on
improving
improving
the
loading
speed,
key
card
and
also
we
are
working
on
the
development
of
a
key
card
app
for
the
ledger.
Nano
X,
which
is
the
Bluetooth
version
of
the
the
nano
that's
coming
on
the
market
in
the
coming
weeks,
and
currently
we're
implementing
using
your
channel
here
and
maybe
about
what
it's
I
think
the
rain
is
not
here,
but
there's.
No
one
going
work
since
Garron
is
is
working
on
the
key
code
to
help
to
get
to
this
alpha
stage.
Equity.
A
A
C
Sorry
I
was
animated.
Somehow
yeah
I
want
you
to
restart
this
discussion
around
components
and
mostly
because
well
now
we
have
a
number
of
different
depths
that
we
are
working
on
and
in
parallel
and
looks
like
most
of
them
are
kinda
free
implementing
their
own
components,
at
least
the
basic
ones,
because
yeah
this
word
discussion,
one
component
is
quite
all
and
lots
of
people
have
been
involving
in
it
and
lots
of
different
point
of
views.
So
the
the
one
I
want
to
initiate
right
now
isn't
is
very
focused
and
and
yeah.
C
So
that
way,
I
want
to
provide
some
context
around
what
I'm
thinking
about,
but
essentially
I
feel
like
most
of
the
very
basic
component.
We
have
two
things
like
that
list
item
and
so
on.
They
are
kind
of
duplicated
in
like
at
least
once
in
status,
reacts
in
react
native
and
then
essence
she
probably
a
couple
of
times
in
various
depths.
C
So
I
guess
no.
My
idea
would
be
to
have
like
just
an
extra
repository
that
would
contain
only
those
components,
so
it
could
be
some
more
somewhat
like
extracted
from
what
we
are
right
now
like
in
statistics.
We
have
some
components,
so
they
don't
really
exactly
match
the
figma
ones,
but
still
it's
it's
something
but
yeah
I
guess
we
should
use
the
figma
list
as
a
source
of
truth
of
components.
C
I
wanted
to
discuss
now,
get
like
feedback
and
ideas
from
people
working
on
the
apps,
like
teller
or
network
or
feedback
from
design
team
just
to
see,
if
no,
that
makes
sense
and
yeah
again
I'm
trying
to
have
a
very
narrow
and
fixed
scope
so
that
actually
we
can
deliver
and
ship
something
this
time.
And
then,
once
we
have
this
basic
stuff,
we
can
always
add
other
things
or
think
about
more
I,
don't
know
more
component
or
having
something
and
more
well
3
oriented.
C
F
A
F
K
I'll
be
like
speaking
on
behalf
of
the
design
team,
we
would
be
happy
to
turn
those
thoughts
and
discussions
into
action,
so
I'm
definitely
on
board,
with
Julian,
with
narrowing
the
scope
and
creating
something
simple:
are
you
but
usable
on
the
design
side
of
things?
So,
as
you
are
now,
we
have
a
component
library
for
the
app,
but
there's
now
defined
components
for
web
based
apps
such
as
the
apps.
K
K
K
Icons
which
are
completely
the
same
on
all
platforms
app
and
the
native
app
I
mean,
and
the
the
web-based
apps,
such
as
snaps.
So
if
there's
any
need
for
assistance,
I
will
be
happy
to
help
and
if
we
move
further
and
started,
creating
components
for
web
I
was
just
creating,
for
example,
one
component
and
define
that
in
figma
in
detail,
I
have
all
the
specifications.
K
G
Think
that
interesting,
that
you
mentioned
about
the
difference
about
the
native
app
in
these
T
apps
right
now,
we
have
this
difference,
but
just
to
what
you
mention,
this
I
think
that
in
the
future
we
are
going,
everything
is
going
to
be
the
same.
Everything
would
be
at
the
app
so
like
the
chat
screen
and
the
wallet
and
the
profile
right
now
we
have
this.
K
So,
that's
that's
all
the
code
level
right,
but
on
the
UX
level
there
would
be
some
differences
because
of
the
difference,
patter,
a
difference
in
and
basically
in
user
experience
between
web
based
applications
and
native.
The
most
simple
example
would
be
the
tab
bar
so
websites.
They
don't
have
anything
that
is
sticking
to
the
bottom
in
a
mobile
website,
for
example,
because
it's
it
works
inside
of
a
browser
window,
and
that
gives
us
certain
limitations
and
most
commonly
a
web-based
app
would
be
scrollable
down.
K
There
are
more
differences,
considering
the
native,
considering
the
the
platform
with
text
temple
would
display
errors
and
text
inputs,
so
there's
a
different
level
of
control.
As
far
as
I
know
when
it,
when
we're
talking
about
websites
versus
native
apps,
I'm,
not
saying
that
they
should
be
different
but
I
guess
they
figured
out.
It's
just
providing
a
better
experience.
They
they
most
likely
would
be
different.
Just.
L
K
It's
a
really
nice
example,
because
this
is
an
example,
and
it's
the
same
on
both
web
and
native.
It's
it's
completely.
It's
gonna
be
completely
the
same
and
yeah
we'll
start
with,
and
also
do
reusable
fundamentals
such
as
typography,
color,
colors
and
icons,
which
is
also
we
are
also
gonna,
be
the
same
note.
L
Yeah,
so
totally
I'm
totally
on
board.
I
think
that
those
are
a
really
good
place
to
start
and
to
kind
of
stay
away
from
so
I
totally
understand
the
concern
about
having
components
that
might
be
different
on
web
as
they
are
all
native
I
think
we
need
to
discuss
those
case-by-case
because
it
feels
like
otherwise
we
get
into
an
endless
like.
Should
we
or
shouldn't
we
copy
or
like
implement
components
for
both
native
and
web?
K
K
I
K
Yeah,
that's
a
nice
comment
by
the
way,
and
it
brings
us
back
to
this
really
long
discussion
about
what
are
we
building
and
what
is
the
target
audience
of
what
we're
trying
to
build
so
if
which,
if
we
are
creating
a
component
library
that
we
are
going
to
use
inside
status,
to
build
to
build
our
own
decks?
It's
one
thing
but
we're
if
we
are
building
in
component
library
for
third-party
developers.
It's
another
thing
and
if
that's
true,
we
should
definitely
consider
some
customizable
elements.
C
C
And
to
the
previous
point
point
about
dabs
and
web
depths:
I
think
we
we
have
kind
of
two
different
usage
of
web
technology
in
status
and,
for
instance,
something
like
that:
Deb
Stahl.
Well,
it's
almost
not
a
Deb
in
the
sense
that
it
will
run
directly
within
statutes.
It
will
not
run
as
a
regular
Deb
in
the
browser.
So
you
don't
have
the
world
browser
declaration
and
components
and
and
UI
elements,
and
probably
it's
also
kind
of
change
the
way
those
component
they
will
behave.
C
K
K
Regarding
the
depths
or
being
basically
native
I'm,
I
would
suggest
not
to
pretend
that
it's
a
native
app
when
it's
a
web
app
and
to
be
more
transparent
and
honest
about
it
and
to
be
ready
for
it
to
be
used
outside
of
status.
So,
yes,
it's
the
most.
It's
most
likely
going
to
be
used
inside
status
in
the
sort
of
controlled
environment
of
ours,
but
we,
but
since
it
is,
adapt
and
it
it
has
the
URL
and
it
is
accessible
from
some
some
someday.
K
B
K
C
B
Part
of
the
ideas
that
we're
not
actually
offering
a
list
of
daps
and
thereby
we're
not
violating
any
App
Store
rules
by
offering
digital
goods
for
sale.
So
it's
actually
an
additional
inspirated
app
store.
But
that's
just
this
particular
example.
In
other
cases,
we
might
be
actually
animating
more
native
feeling
with
a
dad.
E
E
There's
no
death,
always
specifically
external
and
we'll,
have
you
know
eventually,
if
I
get
my
way
like
a
whole
bunch
of
features,
you
know
like
uploading
and
downloading,
with
SMT
and
interactions
with
your
wallets
and
stuff,
which
will
make
it
very
you
know,
completes
and
and
and
complex
and
worthy
of
its
own
URL
and
standing
alone
in
additions.
All
the
AppStore
guidelines
that
Rachel
just
mentioned.
B
Might
be
worth
formalizing
this
whole
component
discussion
in
a
swarm
right
up,
because
we've
identified
some
research
needs
and
terms
of
implementation,
like
definitely
different
phase
into
you
and
there's
a
lot
sitter
in
terms
of
like
actually
handle
the
implementation.
It'll
be
really
attractive.
If
we
can
manage
to
bounty
out
the
whole
thing,
and
it
seems
like
something
that
we
should
be
able
to
find
enough
external
contributors
who
would
be
interested
in
capable
of
doing
especially
for
creating
goods
in
JavaScript
I
could
take
a
start.
B
E
Work
for
us
have
been
asking
if
there's
like
any
other
work
in
between
version
1
of
the
data
store
and
like
implementing
the
smart
cut,
but
like
laughs.
So
they
would
be
keen
perhaps
to
take
on
something
like
that,
because
they
have
react
experience
if
we
decide
but
doing
it
in
JavaScript
is
okay.
Given
the
animations
and
like
input
for
there's
anybody
else.
Caveats.
B
L
No,
it
also
because
there
is
some
more
time
to
discuss
I
think
a
write
up,
see
great
ideas.
It's
a
bit
of
a
larger
effort
altogether,
just
coming
back
to
things
like
font
and
color,
palette
and
list
item
are
any
of
those
being
implemented
for
react
native
now
that
could
be
expanded.
So
we
have
like
a
start.
C
C
L
Okay,
yeah,
that
would
be
awesome.
Just
I,
wouldn't
want
to
do
seem
like
things
that
we
we
would
need,
regardless
of
whatever
future
system
we'd
come
up
with,
so
it
feels
like
the
sooner
we
can
start
on
those
two
better.
So
if
you
say
you're
working
on
list
item,
is
anyone
working
on
phones
at
the
moment
or
is
that
also
something
that's
already
happened
in
the
past.
C
K
By
the
way
regarding
the
typography
of
a
typeface,
we
used,
as
you
all
know,
it's
open
source
and
it's
being
actually
developed
and
it's
it's
being
updated
once
in
a
while.
So
just
to
consider
this,
we
never
discussed
that
before
that
this
typeface
needs
updating.
So
if
anybody
could
looks
great
like
I,
don't
know
sort
of
a
road
map
or
just
let's
just
keep
that
in
mind
that
it's
updated,
so
somebody
would
go
to
the
developers
website
download
the
latest
typeface
and
update
it
inside
the
codebase
I'm
talking
about
the
interior
UI.
C
A
L
A
C
So
maybe
just
like
one
last
shot
from
me
is
I,
see
this
as
kind
of
a
collective
effort
like
any
team,
doing
something
related
to
UI,
which
should
be
probably
all
of
us
well
at
least
the
revell.
They
should
think
component
and
try
to
know
just
extra
extract.
Whatever
behavioral
thing,
they
are
working
on
to
make
sure
that
they
can
be
reused
across
the
various
teams
and
try
to
reduce
the
duplication
and
that
type
of
thing
that
would
be
really
great.
G
Just
maybe
the
designers
they
they
can
mention
to
the
developer.
Look
this
that
this
component
here
is
probably
being
being
reused
and
and
then
also
the
designers.
They
can
follow
up
this
story
book
or
whatever
is
the
model
we
are
using
to
see
if
the
component
is
actually
implemented
as
the
designer
expected.
So
maybe
it
would
be
as
you
mention
it
is
a
team
effort,
but
I
guess
that
the
design
team
should
be
in
charge
of
taking
care
of
what
goes
to
this
to
this
package
and
to
actually
review
if
it's
correct.
K
Yeah,
that
sounds
great
would
be
happy
to
serve
to
do
it.
Let's
just
find
out
what
is
the
best
way
to
make
it
work.
As
I
said,
if
we
start
with
something
really
simple,
it
would
be
easy
to
find
out
what
is
the
best
way
to
review
components,
to
define
the
components
and
I
guess
after
we
start
with
something
simple
is
going
to
be
easier
to
scale
that
system.
A
A
H
I
do
have
two
small
announcements
if
I
can
start
first
one.
Actually
it
relates
to
anyone
who
has
mobile
application
installed
if
you
haven't
upgraded
from
33
release.
That
is
like
two
readers
in
the
post.
Please
do
upgrade
to
the
waiter
stories
the
reason
that
next
Monday,
so
in
a
week
they
will
make
changes
to
the
nightly,
build
first
and
later
to
the
next
release,
and
you
will
not
be
able
to
receive
messages
from
this
to
newer
versions
in
one
to
one
and
in
the
group
shots.
So
he
wanted
to
receive
messages.
H
Please
upgrade
to
the
latest
released
if
you
adventurous
to
the
nightly,
but
I
would,
as
a
tester
I
would
recommend
to
update
to
the
latest
through
list
mobile
version
for
the
desktop.
We
will
announce
the
stable
version
later
this
week,
so
it
was
just
announcement
in
short,
just
upgraded
to
the
latest
released
version.
That's
it.
H
Reported
issues
in
status
react
ripple
and
use
to
things
that
your
issue
is
relevant,
but
there
were
no
actions
on
this
like
last
three
months.
Then
it
will
be
all
closed
by,
but
it
will
be
marked
for
of
all
this
tale
label
and
then
it
will
be
closed
later.
So,
if
you
think
that
issue
is
still
relevant,
please
make
a
note
like
I
can
still
reproduce
all
these
features
still
needed
and
you
haven't
added
it
to
the
app.
But
I
really
would
like
to
see
it.
H
So
just
add
some
comment
to
the
issue,
so
it
it's
open,
it's
not
caused
by
the
bot.
If
you,
for
example,
got
some
update
but
like
notification
from
github
but
missed
it,
and
you
still
room
remember
about
such
issues,
please
go
to
status,
reactor
Apple
and
just
search
for
issues
and
reopen
them.
That
will
be
very
helpful
and
will
save
a
lot
of
time
for
testing
testing
who
will
review
such
issues
that
were
closed
and
see
if
they
still
relevant.
That's
it.
A
I
Okay,
so
for
Nimbus
I,
don't
know
if
you
guys
are
following
any
of
that
stuff,
but
what's
happening
with
your
into
Worlds
right
now.
Is
that
we're
going
to
be
launching
a
client,
specific
test
net
of
sorts
for
the
beacon
chain?
How
do
we
contain
doesn't
do
a
lot
of
things,
but
it
does
provide
randomness
and
security
to
it.
They're
into
I'm.
I
So
if
anybody
is
interested
in
becoming
like
playing
a
validator,
basically
playing
a
stakeholder
in
east
to
you
get
in
touch
with
me,
because
this
is
what
will
be
launching
like
in
the
next
few
weeks.
So
the
workflow
is
basically
that
in
etherion
to
you
steaks
on
East
and
then
you
become
a
value
later
and
then
validators
have
these
duties,
which
are
similar
to
what
miners
do
today,
the
hardware
and
basically
we're
looking
for
test
bunnies
that
want
to
play
validators
on
our
own
Testament.