►
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).
B
A
So
yeah
I
guess,
let's
get
started
then
yeah.
Thank
you
for
joining
its
meeting
number
17.
It's
the
one
that
been
postponed
from
the
last
time
and
yeah
and
then
yep.
Basically
today
there
are
not
that
many
topics
to
discuss,
but
we
can
start
with
a
swarm
updates
as
as
usual.
So
just
give
me
a
few
seconds
to
open
an
active
swarms
list,
yeah
so
I
guess
we
can
start
with
the
sea
care
market
and
yeah
Lucy
can.
C
Can
do
that
not
a
lot
of
news
from
sticker
market
no
from
development
sign
way.
We
we've
done
pretty
much
anything
that
is
required,
so
not
a
lot
to
expect
and
we
are
still
in
the
process
of
doing
the
audits,
which
I
believe
started
well,
I'm,
not
very
sure,
because
the
it's
kind
of
complex
to
to
follow
the
the
contractor
deeds
so
I'm,
not
quite
sure
about
that.
But
yeah
not
a
lot
own
on
sticker
market
front.
C
B
A
D
D
Just
you
know
to
see
what
were
the
issues
on
what
to
improve
and
so
on
and
I
guess:
I
can
go
next
to
the
down
stuff
and
Billy
doll.
We
I
mean
we
asked
we
are
this
feature
to
support
listening
projects
and
it
fetches
the
produce
for
my
PFS
and
all
that
we
also
did
like
a
more
intensive
test
and
from
the
a
bunch
of
issues
that
were
currently
working
on
unfixing
and
I.
Think
I
said:
cool.
A
Sub-Sectors
known
again,
the
next
is
core
improvements
that
so
for
the
last
few
weeks,
we
did
release
a
new
version
and
we
are
playing
series
a
follow-up
to
this.
With
one
more
bug
fix.
That's
we
feel,
like
it's
important
status,
go
side
as
well.
We
are
currently
like
working
on
error
reporting
in
a
more
private
way,
so
people
can
actually
send
blogs
and
they
will
be
offered
to
send
blogs
to
status,
on
exceptions
and-
and
things
like
that,
so
that's
very
important
for
us
to
actually
debug
the
application.
And
after
that,
we'll
do
the
like.
A
E
That's
where
we've
got
to
build
materials,
I'm
working
on
the
initial
like
introduction,
blog
posts,
as
well
as
we're
playing
around
with
a
few
different
ways
to
visualize
the
ENS
usernames
contract
and
people's
interaction
with
it,
so
that
it
can
be
explained
easier
to
the
general
public,
while
also
showing
like
how
it
captures
value
and
that'll
be
well
I.
Hope
to
have
that
at
least
like
major
draft
being
revised
by
the
end
of
the
way
and
then
from
there
won't
go
into
each
of
the
individual
use
cases
and
notebooks.
E
F
Sir,
so
let's
see
so
last,
we
ish
so
we've
been
sort
of
implementing
this
minimal
Viable
did
sink
proof
concept
and
go,
and
this
been
working
at
it's
sort
of
working
interactively,
but
as
I'm
cleaning
up,
we
have
to
do
to
get
it
running
in
this
or
console
client.
And
so
we
can
go
still
looking
into
every
bit.
F
Do
protocol
negation
negotiation
and
these
types
of
things
adding
that
we
have
this
ongoing
bi-weekly
calls
and
trying
to
cooperate
a
bit
with
this
one
team.
It's
gonna
be
a
summit
and
a
few
weeks
that
a
few
of
us
are
going
to
yeah
and
I.
Think
that's
mostly.
It
I
forgot
exactly
what
to
be
updated
last
time,
but
something
like
this.
G
Go
ahead,
I
was
gonna,
give
an
update
that
we
made
some
progress
on
the
critical
path
that
is
in
Reich,
so
I
believe
most
people
do
have
a
bank
account
if
you
go
to
the
top
top
folder.
Let's
say
projects
you'll
see
eight
projects
that
is
called
critical
path
or
has
some
something
referring
to
critical
path.
If
you
go
into
that
task,
you
can
see
all
the
dependencies
that
we
defined
so
far
as
being
being
critical.
I
would
say:
that's
the
main,
update,
husker,
anything
to
add
I.
F
A
B
I'm
doing
so
more
research
on
because
I
have
two
types
of
quorum,
that
is
the
simple
quorum
in
the
majority
quorum
and
for
the
wicked
democracy
it.
It
seems
that
it
doesn't
make
sense
to
have
these
delegates,
or
at
least
default
to
delegate
for
these
simple
columns
because
they
don't
require
the
majority.
So
it's
just
the
how
you
would
say
they
online
my
majority,
just
the
people
who
voted
that
counts,
and
so
I
would
I'm
removing
this
part
of
topic.
B
Democracy
to
a
later
on,
iteration
and
I
will
focus
only
on
the
majority
quorums,
because
that's
the
I
think
the
most
important
ones
and
and
then
later
on,
I
would
derive
from
from
that
to
make
a
simple
quorum.
I'm,
also
trying
still
trying
to
talk
with
Oregon
but
but
seems
like
there
is
not
not
many
interests
at
their
parts
or
I'm,
not
really
sure.
B
So,
like
a
lot
like
many
answers
about
my
questions
but
yeah
in
about
today,
they
react
components
that
that's
really
being
slow
and
that's
so
I
expect
to
get
in
the
rhythm
again
back
to
make
the
components
this
week.
But
I
was
mostly
on
this
research.
A
F
A
G
A
H
H
So
we've
had
two
or
three
calls
now
about
to
kick
off
the
material
count
work.
We
are
definition
Faye's
we've
defined
the
scope
of
what
we
want.
What
we
want
to
do,
what
you
to
what?
What
you're
not
currently
doing
is
a
writing
the
user
stories,
so
that
design
can
work
on
that
and
also
listing
the
development
tasks
with
regard
to
the
scope
very
quickly,
so
that
everyone
knows
what
we
have
in
mind
that
what
we're
trying
to
do
for
q2.
H
So
the
impact
is
on
the
wet
side,
only
we
wouldn't
release
only
later
or
the
matters
about
secretary
policy,
/
key
bear
and
all
the
specific
use
case
of
key
pairs
for
dabs
and
chats
like
unique
at
his
fault,
apps
and
and
chat
groups.
So
basically
those
copies
in
the
on
the
wallet.
We
want
a
user
to
be
able
to
create
several
while
at
accounts
either
on
the
Status
hd3
so
and
either
automatically
or
by
manually,
entering
the
path
they
want
to
use
on
these
three.
H
H
Also,
and
of
course,
we
want
the
user
to
be
able
to
browse
and
explore
through
these
different
accounts,
meaning
being
able
to
have
another
view
of
all
these
accounts,
get
into
the
details
of
a
specific
account
and
and
and
and
choose
from
which
account
so
they
send
the
transaction
from.
So
that's
the
scope
we
have
in
mind
and
what?
What
friends
via
writing
user
stories
for
yeah?
That's
it.
A
B
Think
that
some
interesting
topics
that
we
could
discuss
is
about
the
gas
abstraction
in
the
gas
relayer,
because
keycard
also
implemented
that
in
Hakata
as
Julian
is
asking
me
about
that
so
to
implement.
This
is
not
not
exactly
a
gas
abstraction,
but
to
pay
the
gas
for
the
users
in
a
way
to
first
to
make
easier
the
onboarding
of
new
users
and
also
the
discussion
about
identity
that
is
connected
to
these
points
and
also
the
discussion
about
separating
the
a
wallet
from
the
shed
identities.
B
So
I
think
this.
This
topics
they
are
important
to
be
disgusted
together
with
to
be
implemented
for
for
this
change
or
near
changes,
especially
because
of
keycard,
and
how
keycard
mentions
it.
I
think
that
separating
the
the
the
wallet,
the
Schottky
would
make
things
better
for
keycard,
and
also
this
would
make
things
easier
to
implement
as
an
identity
contract
to
make
the
Gazoo
layer
possible.
So
I
think
this
these
topics
they
are
kind
of
connected
and
for
do
for
that.
B
I
think
that
a
good
step
would
be
to
start
thinking
in
how
we
can
separated
a
density.
Sorry,
if
they
shat
in
the
world
I
think
that
would
be
the
first
thing
when
we
need
you
I
know
that
this
is
an
ongoing
topic
for
a
long
time,
so
I
think
the
first
fit
question
would
be.
How
is
this
stages
of
this?
It's
been
working
on
and
there
is
pool
requests
about
this.
H
Obviously,
since
status
needs
to
work
with
keycard,
what
we
will
need
is
that
the
main
chat
key
is
not
is
going
to
get
said
different
from
the
main
way
that
key,
so
this
will
be
implemented,
meaning
in
particular
that
on
onboarding
or
when
the
user
starts
using
status.
We
need
to
be
made
aware
that
these
chats
are
made
with
a
different
key
pair
and
is
worried
so
that
when
he
gets
some
funds
on
his
wallet,
keep
air
through
kudos
or
anything
else.
You
get
them
in
another
way,
lads.
H
So,
yes,
I'm
saying
he
needs
to
be
aware.
It
needs
to
be
discussed.
Maybe
all
this
can
be
done
automatically
in
the
background
for
him.
But
basically,
yes,
we're
gonna
have
a
different
chat
keeper,
but
the
other
thing
we
said
is
that
we,
we
have
not
prioritized
the
fact
to
use
one
unique
key
pair
twelve
chat
context
at
this
at
this
stage,
just
for
planning
reasons,
that's
what
we
discussed
in
terms
of
specific
of
usage,
of
a
chat,
key
pairs.
A
B
B
Another
question:
so
there
is
a
difference
from
the
shot
key
to
the
wallet
kid,
because
the
wallet
key
is
not
saved
inside
of
the
device,
but
the
schottky.
Please
save
it
in
the
device
right
because
you
don't
want
to
be
hot
holding
the
card.
So
how
that
changes?
May
sorry
how
that
that
is
the
very
differentiated
the.
H
The
the
thing
with
implemented
is
the
ability
for
the
key
card
I
mean
so
here
we're
talking
about
when
the
user
is
using
the
key
card.
Of
course,
when
the
user
is
changing,
the
key
card
is
seed
is
on
the
key
card
only
and
we've
implemented
on
the
key
code
API
the
ability
to
export
from
the
key
card
to
the
App
one
range
of
paths
and
we've
actually
defined
the
IP
for
that
and
the
chat
key
is
on
these
range
of
paths.
Of
course,
does
that
answer
your
question.
B
Yes,
so
so
you
can,
you
can
have
like
this
save
it,
but
then
I
have
another
question
that
is
regarding
another
discussion
that
is
kind
of
similar,
because
that
we
have
this
shot
keys.
That
is
something
far
stages
like
it's
not
like
some
or
something
like
a
any
deck
can
can
request
the
type
this
type
of
key,
because
I
see
that
this
is
kind
of
useful
for
some
depths.
B
So
maybe
I
did
that
attack
once
you
use
whisper
and
then
they
could
request
this
kid
and
then,
when
you
want
to
kind
of
login
and
then
indeed
the
app
only
on
the
first
time
you
you
put
the
card
and
then
it
kind
of
says
this
guy
I'm
not
really
sure.
But
but
the
question
is
that
that's
this
put,
this
feature
is
for
stages
only
or
any
death
can
use
this
type
of
key
that's
raised.
I
I
mean
once
we've
done,
the
multi
account
stuff
we'll
be
able
to
correct.
We
will
be
able
to
look
at
how
to
use
treated
in
whisper
and
in
deaths,
so
so
my
personal
take
as
I
would
like
to
generate
a
new
keeper
for
every
death
based
on,
like
the
hash,
would
suppose
for
something
and
I
I.
Definitely
think
at
that
point.
We
can
definitely
request
the
data
themselves
to
to
request
to
keep
it
full
whisper
if
it
only
generate
them
of
themselves.
G
Have
a
question
Dehradun
Ricardo
as
well,
because
we've
had
some
back
and
forth
on
this.
If,
if
we
would
enable
any
DAP
to
request
a
key
part,
key
Parenthood
it
like
hyung,
would
you
see
the
process
for
the
ENS
DAP
to
request
a
let's
say,
a
one-time
key
pair?
That
then
also
offers
guests
abstraction
so
what
it
like?
B
So
all
these
surrounds
in
this
the
solution
about
this
I
think
solar
surrounds
the
identity
contracts.
Because
then
you
can
have
this
single
single
place
that
you
can
start
this
DNS
name
and
these
different
keys,
for
example
the
ENS
usernames
that
it
can
have
its
own
key
for
accessing,
but
it
registers
the
name
for
that
identity
contract
and
in
that,
so
you
can
associate
new
keys
for
that
identity,
contract
and,
of
course,
remove
the
keys.
B
If
you
want
so,
but
of
course
this
this
kind
of
QD
the
privacy
feature
of
separation
of
the
keys,
but
it
would
only
kill
the
prior
privacy
for
the
selected
apps
that
you
want.
So
it's
not
a
default
behavior
for
exposing
the
the
app
so,
for
example,
maybe
you
want
to
use
at
the
app
with
a
new
key
for
bit,
because
it's
only
whispering
yes.
B
So
if
you
want
you
can
link
to
your
identity,
then
you
could.
For
example,
let's
say
that
status
chat
uses
a
separate
key
for
shed,
but
then
we
have
this
identity
contract
that
maybe
have
badges
and
have
the
ENS
name,
maybe
have
reputation.
And
then
we
can
link
this
shet
key
to
this
identity.
By
listing
this
kidding,
indeed
see
and
and
then
the
the
other
users
could
could
lease
this
information
from
that
user
to
see
the
profile.
B
I
So,
basically,
your
ENS
username
would
be
pointing
to
a
smart
contract
which
would
be
like
your
your
on,
like
go
on
chain
identity
of
this
owner.
How
I
personally
view
viewed
this
in
the
future
would
be
that
every
Chad
has
it's
automatically
generated
keeper
and
the
actual
say,
identity
keep.
There
would
be
a
parent
of
those
ones
that
generate
so.
You
generate
these
child
keepers
off
this
identity,
public
key,
so
so
that
public
key
would
not
actually
ever
be
exposed.
Extent
for
to
to
basically
sign
messages
to
to
authenticate
these.
I
Try
who
that
person
is
on
the
child
keys,
so
I
would
be
an
unknown
contact
to
you
in
a
particular
chat.
But
if
I
like,
if
I
join
a
public
chat-
and
you
join
a
public
chat,
neither
of
us
would
know
each
other
who
we
are,
but
if
we
would
like
to
reveal
ourselves
to
each
other,
we
could,
if
it's
a
private
chat.
Of
course,
each
private
chat
with
have
its
own
key
and
you
would
automatically
reveal
itself.
I
G
In
that
sense,
it's
it
seems
like
if
every
chat
would
have
its
own
key
I'm
struggling
to
understand
like
how
it
fits
together
with
E&S.
So
my
line
of
thinking
was:
is
there
a
way
to
use
the
address?
To?
Can
that
you
use
to
connect
ENS
to
your
let's
say
public
address?
Could
we
use
that
same
address
to
also
by
the
ENS
name
with
gas
obstruction,
yeah.
I
B
Yes,
exactly
so,
but
there
is
another
another
feature
that
about
these
guys:
abstraction
that
I
want
to
mention.
That
is
about
the
create
to
opcode
from
recent
hard
part,
because
once
we
create
a
key
pair,
we
can
also
create
this
new
identity
without
deploying
it
in
it
can
no,
it
can
be
deployed
on
demand
only
if
it's
actually
use
it.
B
So,
for
example,
you
can
deposit
University
20
tokens
in
the
in
like
SNT
only
as
the
team
in
this
identity
contract
that
was
not
even
created
yet
and
once
you
need
to
use
it,
for
example,
to
buy
an
e
NS
name.
Then
you
you
can
use
the
gas
abstraction
to
deploy
it
in
register
your
name
and
then
everything
is
paid
in
st,
including,
of
course,
the
registration
price
or
take
advantage
is
10s
the
t
more
like
something
1
as
the
T
for
paying
the
gas.
So
so
you
can.
B
B
Maybe
it
could
be
just
a
hash
or
or
maybe
you
haven't
a
specific
key
that
you
make
a
signature
to
prove
that
another
key
is
part
of
that
identity.
So
you
can
you
don't
need
to
go
to
in
chain,
so
you
don't
lose
the
privacy
and
but
the
main
concern
in
all
of
this
is
having
your
public
profile
mix
it
up
with
your
bank
profile,
maybe
like
where
you
start
your
phone's.
B
So
we
should
educate
users
to
have
multiple
profiles,
so
maybe
we
would
have
some
do
something
in
the
UX
that
the
user
could
enable
the
like
a
public
profile,
the
family
profile,
and
maybe
they
work
profile.
We
can
research
on
that
and
then
the
user
select,
but
for
the
the
public
shares
I
just
mentioned
that
each
chat
would
have
one
key
I
think
that
that's
really
good
as
well,
and
if
we
allow
the
idea
to
request
a
key,
a
new
key
I
think
that's.
B
A
Actually,
for
multi-account
and
privacy
ever
question,
or
one
concern
rather
so
I
want.
Maybe
someone
knows
the
good
answer
this,
so
we
are
trying
to
make
as
I
understand
it.
We
are
trying
to
make
this
multi
account
seemed
to
be
able
to
so
that
the
apps
don't
share
the
same
identity.
So
we
are
protecting
ourselves
from
being
tracked
or
something
like
that.
But
if
we
don't
have
a
private
transactions
in
the
theorem,
it
still
will
be
as
soon
as
you
spend
some
money
somewhere.
A
B
To
solving
that
I
see
that
we
can
have
a
mixer,
so
maybe
we
could
have
a
function
inside
of
status
or
at
the
app.
That
does
that
that
could
allow
you
to
transfer
phones
in
a
private
manner,
using
a
chair
in
the
app
that
uses
that
guys
narcs
technology
just
like
G
cash
deposit,
the
phones
and
this
is
saves
my
contract
and
it
kinds
of
you
don't
know
who
who
ever
came
that
money
from
that
would
be
a
solution
but
not
ideal.
B
F
F
Fellow
soon,
if
we
make
it
I
think
it's
probably
not
number
one
priority
for
the
wallet
considering
other
low-hanging
fruit,
but
it's
something
we
can
probably
get
to
it
like
two
three
or
so,
and
this
was
something
that
key
Cod
is
looking
at
as
well.
So
it's
definitely
like
a
medium-term
path
to
it.
Was
it.
B
Just
conclude
this:
this
is
what
I
brought
here.
I
brought
this
here,
because
I
wanted
to
start
start
no
or
not,
or
integrate
these
concepts
of
ID
contract
in
and
Gaza
abstraction
into
these
updates
directly.
There
are
coming
in,
like
we
have
the
gas
abstraction
in
a
proof
of
concept
working,
so
we
could
implement
that
in
stages
already
or
maybe
just
in
in
a
test
net,
or
something
like
that.
B
So
it's
just
a
matter
of
maybe
we
are
really
taking
ourselves
in
in
making
this
happen
because,
like
everyone
else
is
already
doing
this,
and
we
should
also
do
that
not
only
this,
but
also
Universal
looking
so
many
of
other
wallets
are
implementing
just
gas
abstraction.
What
what
I
envisioned
here
is
the
universal
logins,
just
like
I'll
explain
this
in
the
proposed
it
that's.
That
is
basically
the
the
new
single
sign-on
for
the
web.
3
and
you're
near
on
this
I
think
would
be
very
googled
for
States
I.
F
F
B
I
think
that
this
is
a
continuation
of
this
keycard
updates,
or
maybe
we
first
have.
This
key
card
is
to
make
it
launch
it
in
working
and
then
we've
progress
to
the
universal
logins
that
would
bring
all
these
features
that
we
talked
it.
That
would
be
the
separation
from
from
keys.
You
know
maybe
perfect
way
in
gas
abstraction
in
everything
that
makes
the
us
better
or
users
yeah.
I
A
B
A
I
A
A
B
But
this
is
like
not
really
good,
because
if
there
is
a
lot
of
things,
I
don't
want
to
see
there.
So
maybe
we
should
have
some
kind
of
future
in
common
or
something
like
that.
You
show
just
the
app
specific
because
I
also
like
when
I
develop,
the
app
I
want
to
see
the
errors
in
it,
but
I
then
I
have
to
keep
scrolling
that
that
screen.
But
maybe
someone
have
a
solution.
A
I
We
have
the
console
bot,
you
I'm,
pretty
sure.
Console.Log
was
hooked
to
sending
messages,
so
you
could
like
typing,
commands
and
get
some
feedback.
I
could
be
remembered,
miss
remembering
that,
but
if
we
auto
generating
chats
like,
maybe
we
can
order
generate
one
for
like
local
host,
doesn't
know
that
and
don't
come
so
loads
into
chat
that
way
as
well.
I
don't
know
about
you,
but
yeah.
A
C
Accessible,
we
are
certain
documentation,
so
what
you
can
do
is
remote
debugging.
So
it's
specific
to
adapts,
because
what
you
are
referring
to
before
the
a
DB
stuff-
it's
it's
every
lug
and
probably
not
that
long.
Actually,
I'm,
not
sure
you
can
do
like
regular
web
remote
debugging
using
Chrome
or
Safari,
and
it
should
work
out
of
the
box.
You
just
you
have
to
make
sure
that
your
phone
is
on
the
same
Wi-Fi
as
your
laptop
and
then
look
for
your
mobile
as
a
remote
device
or
something
like
that.
But
we.