►
From YouTube: Core Unit Launch Pod Sessions | Session #18: MakerLabs
Description
For the 18th episode of CULPS, Tim Schuppener (@ultraschuppi) will be presenting the MakerLabs Core Unit, whose purpose is to provide pathways for revolutionary product ideas. Subproposals can be found here:
MIP39c2-SP21: Adding MakerLabs Core Unit: https://forum.makerdao.com/t/mip39c2-sp21-adding-makerlabs-core-unit/9425
MIP40c2-SP32: Adding MakerLabs Core Unit Budget: https://forum.makerdao.com/t/mip40c3-sp32-adding-makerlabs-core-unit-budget/10108
MIP41c2-SP22: Facilitator Onboarding (MakerLabs): https://forum.makerdao.com/t/mip41c4-sp22-facilitator-onboarding-makerlabs/10109
A
Hi,
everyone
welcome
to
another
code
unit
core
unit
launchpad
sessions
to
word
number
18..
My
name
is
juan.
I'm
the
facilitator
from
the
sustainable
ecosystem
skating
core
units
here
at
maker,
I'm
joined
by
a
bunch
of
people
interested
in
everything,
coordinate
related.
Apparently,
today
we
are
with
the
team
or
the
to
be
team
from
from
maker
labs.
It's
a
very,
very
interesting
core
unit.
B
Okay,
so
yeah
hi
everybody,
and
thanks
for
joining
today's
session
about
mikkellet,
my
name
is
tim
or
I'm
also
running
under
the
call
sign
of
ultra
should
be
in
the
forum
and
I'm
going
to
be
the
core
unit
facilitator
of
this
core
unit.
If
everything
wins
well,
I
have
no
idea
if
this
is
going
to
happen.
It's
probably
up
to
planet
x.
B
B
Yeah
yeah
so
basically
build
something
that
is
viable
enough
to
find
out
if
it
actually
has
product
marketed
or
not,
and
we
are
going
to
cover
the
full
technology
stack
engineering-wise
from
smart
contracts
to
basically
the
user-facing
front-end
that
I
need.
This
is
yeah
in
a
nutshell.
What
we
want
to
do
here,
yeah,
so
this
is
the
team.
I'm
I'm
the
guy
on
the
left,
with
the
bad
hair.
Colin
is
the
one
with
the
beard
and
yeah
the
lefty
on
the
right
side
of
the
picture.
That's
adam.
B
You
can
already
see
that
yeah.
We
are
already
pretty
pretty
committed
about
the
whole
mission,
but
I
I
give
a
brief
intro
about
us
and
the
history
we
had
so
far,
so
we
met
first
in
in
2001
when
I
basically
had
the
chance
to
bootstrap
my
my
own
first
team,
which
was
kind
of
a
spin-off
from
from
the
last
team.
I
I
was
leading
and
adam
and
colin
were
one
of
the
first
hires
I
had,
and
it
was
really
a
really
fun
ride
and
yeah.
B
It
was
pretty
sad
that
after
a
year
or
so
colin
left
to
to
build
up
his
own
startup,
but
nevertheless,
some
years
later,
we
never.
We
never
lost
contact,
and
some
years
later,
colin
introduced
adam
and
me
to
the
ethereum
world
and
even
tried
to
alert
us
into
buying
some,
if
which
we
did
a
year
later,
which
was
probably
a
bad
idea.
We
should
have
done
it
basically
by
the
time
colin
pitches
pitch
it
to
us.
B
But
around
that
time
we
found
out
that
it's
the
right
time
to
team
up
again
and
basically
start
working
as
a
group.
Again
we
found
out
that
it's
really
hard
to
get
hired
as
a
team,
but
eventually
we
we
made
it
to
sick,
which
is
a
very
traditional
german
hardware,
engineering
company
to
basically
build
up
their
the
cloud
or
I
just
iot
branch
that
was
really
fun
because
yeah
we
did
again
this
bootstrapping
thing
and
we
found
out
well.
This
is
really
cool.
We
do.
We
are
doing
it
a
second
time
now.
B
That's
that's
really
great
and
yeah.
During
this
time,
when
we
all
went
into
ethereum,
we,
we
also
had
the
idea
of
building
something
like
dropbox
but
decentralized.
We
call
it
shahru,
which
is
which
had
the
slogan.
Finally,
your
data
is
safu.
It
was
running
on
ipfs
and
ethereum
and
yeah
it.
It
didn't
work.
We
ran
into
major
difficulties
with
ipfs,
basically
destroying
our
routers
at
home,
so
we
ditched
the
project,
but
nevertheless
we
we
had
our
first
exposure
to
ethereum
as
a
programmable
blockchain
and
writing
solidity.
B
B
We
basically
we're
asked
if
we
wanted
to
do
the
same
thing
so
basically
building
up
the
the
cloud
product,
our
bootstrap
cloud,
product
and
cloud
team
which
we
are
doing,
or
we
basically
finished-
that
we
went
live
a
couple
of
months
before
and
the
mission
of
bringing
this
to
product
market
fit
and
finding
out.
If
this
is
actually
working
or
not
yeah,
it's
done
so
our
mission
of
bootstrapping.
B
Something
is
done
here,
yeah.
So
myself,
I
started
as
a
software
engineer
in
2001,
basically
as
a
yeah
as
a
small
software
engineer
in
the
in
the
company
that
later
bought
by
101,
I
think
I'm
a
good
case
of
the
peter
principle.
I
doubled
up
the
career
ladder
a
couple
of
times
until
I
was
just
not
having
any
fun
anymore
and
I
at
some
point.
I
just
realized
that
I
want
to
do
both
things
not
only
talking
but
also
yeah,
providing
value,
building,
something
and
yeah
around
this
time.
B
I
I
had
the
good
luck
that
both
colin
and
adam
had
the
same
feeling
and
we
decided
to
just
yeah
go
early
in
on
bootstrapping
yeah.
By
the
time
I
I
joined,
sick
and
yeah
got
exposure
to
ethereum.
I
was
getting
in
contact
with
with
the
maker
ecosystem
and
found
it
very
interesting.
So
I
minted
some
diet,
basically
some
psy
by
the
time
I
think,
in
the
beginning
of
2018,
I
bought
some
first
npr
tokens.
I
even
did
some
liquidations.
B
C
Yeah
hi,
my
name
is
colin,
so
my
gateway
rock
to
programming
was
basically
20
years
ago.
Modding
for
half-life
and
quake
equate
figurine
yeah.
I
learned
quite
a
lot,
but
eventually
this
stepping
stone
into
professional
software
engineering
was
after
I
did
university
and
my
master's
and
yeah
then
basically
the
story
that
tim
told
he
hired
me
and
yeah.
Since
then,
a
software
engineer
by
heart
and
yeah,
I
love
what
I'm
doing
after
I
left
one
one.
C
C
So
yeah.
We
built
like
products
to
allow
people
to
buy
bitcoins
the
easy
way
and
had
like
bitcoin
atms
and
so
on,
but
we
ultimately
failed
with
our
goal
to
to
bring
this
to
brigham
water
stores,
yeah
and
then
at
the
time
I
was
at
pay.
I
got
into
ethereum
because
we
were
looking
for
other
routes
how
to
get
away
from
this
bitcoin.
The
speculative
bitcoin
thingy-
and
I
remember
there-
was
this
counterparty
thing
that
didn't
quite
work
that
well
and
then
I
got
into
east
but
yeah.
C
In
the
end,
we
ran
out
of
money,
but
at
the
same
time
I
I
got
pretty
heavy
into
ethereum
and
started
mining
with
my
own
computer
sitting
in
the
basement,
blowing
out
all
the
heat
and
yeah
and
then
basically,
the
story
picks
up
again
where
what
tim
already
told
so
we
reconnected
and
decide.
We
need
to
do
something
together
again.
C
D
D
D
After
two
years
it
was
became
a
bit
boring,
got
back
to
university
started
my
phd
cancelled
it
over
some
months,
because
it
was
totally
theoretically,
at
least
for
me,
it's
nothing
what
you
can
deliver
to
to
an
audience
or
something
like
that,
and
then
one
of
my
best
decisions
in
my
life
came
in
so
I
started.
One
one
and
met
should
be
the
first
time
as
one
of
the
first
members
of
the
new
team
and
then.
E
D
I
was
totally
hooked
by
by
a
team
spirit
and
how
you
can
implement
software
in
a
good
style,
and
some
months
later
I
met
also
colin,
which
was
also
part
of
the
first
team
there.
Unfortunately,
he
left
one-on-one,
which
was
really
sad
for
us,
but
nevertheless
some
some.
Some
years
later,
we
chatted
together
and
just
wanted
to
know
about
new
job
opportunities
and
we
met
in
the
bar
and
wanted
to
talk
about.
Maybe
the
next
steps,
what
we
can
do
or
what
he
could
have
could
do.
D
D
I
also
love
everything
about
art,
also
doing
some
generative
art,
maybe
because
I'm
I'm
left-handed,
but
I
don't
know
if
that's
the
reason,
but
basically
I
love
everything.
What
is
really
beautiful?
I
started
from
from
user
experience
or
ending
at
just
painting
some
some
nice
arts
and
so
on.
Maybe
that's
also
the
reason
why
some
people
also
call
me
a
minister
of
propaganda.
D
I
think
the
the
term
was
coined
at
one
and
one
when
I
was
just
doing
a
lot
of
some
kind
of
marketing
stuff,
it's
the
company
to
promote
our
team
and
our
stuff.
We
are
building
there
yeah
and
I
have
really
much
fun
with
implementing
lots
of
side
projects
or
pet
projects
in
the
end,
starting
or
doing
just
research
testing
our
new
frameworks,
technology
yeah,
we
had.
I
had
my
first
experience
with
solidity
by
implementing
this
sharo
thingy
end
of
last
year.
D
I
also
wanted
to
get
back
to
the
to
the
stuff,
so
I
implement
some
kind
of
gum,
road
clone
based
on
ethereum
contracts
and
so
on,
and
that's
also
a
good
thing
about
maker
delegates.
So
this
is
maybe
you
have
read
already
the
the
forum
posts
I've
written
there.
There
was
this
maker
delegates
initiative
that
started
some
some
weeks
ago,
and
so
we
pushed
the
idea
to
us
and
we
just
started
to
to
think
about
it-
how
we
can
implement
it.
D
It
was
a
totally
on
the
side
because
we
have
a
full-time
job,
but
in
our
free
time
we
could
just
think
about
it.
Learn
about
the
data
sources,
just
learn
about
achieve
contracts
and
so
on
how
we
can
get
our
information
and
data
to
collect
everything
to
present
it
to
an
audience
that
could
be
interesting
for
you
and
the
much
the
most
fun
is
about
to
quickly
develop
and
deploy
those
products
to
an
audience
to
get
quickly
feedback
and
have
really
small
iterations
about
it.
D
B
Yeah,
so
it's
probably
not
a
big
surprise
that
it's
euro
diet
that
this
is
the
first
product
we
would
like
to
work
on.
I
mean
we
are
all
from
from
europe
and
we
love
the
idea
of
having
non-volatile
asset,
something
like
die,
but
not
based
on
the
usd,
but
instead
on
euro
sebastian
me
have
been
thinking
about
eurodive,
for
I
don't
know
a
couple
of
months
already
and
he
burst
it.
Basically
lured
me
into
hey:
why
do
you
just
try
to
to
pitch
it
and
do
it
and
yeah?
B
B
Basically
hire
us
ourselves
into
this
company
so
effectively
would
start
working
and
being
on
the
pa
payroll
as
well.
In
january,
kicking
off
euro
die
and
well.
The
first
two
obvious
building
blocks
for
udai
would
be
to
basically
take
the
vanilla
contracts
that
protocol
engineering
already
has
on
the
main
net
for
for
the
usd
based
die,
bring
them
to
gurley,
try
not
to
modify
them
as
much,
because
I
mean
they
are
audited,
they
are
diamond
hardened.
B
B
Is
it
really
necessary
to
have
something
like
this,
but
it
would
give
us
the
additional
benefit
of
starting
from
scratch,
and
also
would
it
help
us
to
to
also
learn
about
the
whole
contract
ecosystem,
which
we
do
have
a
theoretical
background
on?
It's,
not
that
we
haven't
do
some
research,
but
it's
not
the
same
as
it
really
is
starting
from
scratch.
B
So
that
would
be
basically
the
timeline
for
for
the
next
months
and
as
soon
as
as
we
have
the
two
building
blocks,
we
basically
quickly
iterate
on
it
yeah
in
a
in
a
probably
different
manner
that
you
would
expect
from
somebody
who
is
doing
like
the
protocol
engineering
team.
We
are
totally
we
are
totally
different
in
this
perspective,
but
as
long
as
we're
not
a
mainnet,
I
think
we
we
can
do
whatever
we
want
to
basically
yeah
and
we
would
quickly.
E
B
That's
that's
our
plan
and
yeah.
Basically,
as
soon
as
everybody
is
or
us,
including
the
maker
community,
is,
is
thinking
that
it's
good
enough
to
to
release
a
domain
net.
Then
we
would
just
do
it
yeah.
So
that's
the
well
laid
out
plan
german
style
or
not
german
style
that
we
that
we
have
so
far
yeah
and
that's
pretty
much
it
so
yeah.
I
mean
there
wasn't
that
much
of
discussion
in
the
forum
about
the
mips
until
we
proposed
a
couple
of
weeks
ago.
B
F
Yeah
hi
from
a
really
pragmatic
perspective.
I
just
heard
from
you
and
three
team
members
that
you
intend
to
quit
your
current
job
to
become
this
mvp
unit
for
for
maker.
The
concern
is
that
I
don't
see
a
road
map
beyond
three
months
and
and
the
demonstrable
value
of
the
unit
is
still
not
not
demonstrated
right,
and
so
I
I
would
have
concern
in
that
you
would
come
in
quit.
B
C
To
this,
so
I
mean
we're
not
a
eurodictor
unit,
so
we
we
specifically
thought
about
it
to
build
like
a
euro
dicorio,
but
then
we
were
in
the
position.
What
comes
after
euro
day,
and
we
thought
long
and
hard
about
it,
and
we
we
said
to
us.
The
one
thing
we
want
to
do
is
is
basically
building
new
products
and
validating
them,
and
so
the
the
the
whole
promise
of
this
coin
is
not
to
build
like
uridine
but
to
build
products
and
build
mvps
and
test
them
to
market.
C
So
the
end
of
euro
die
is
not
not
the
end
of
make
a
lapse,
so
we
so
so.
If
we,
if
we
see
like
an
end
coming
to
eurodi,
either
way
it
succeeds
or,
and
some
other
team
is
taking
it
over
to
bring
it
to
production
or
to
maintain
it
or
whatever,
or
we
find
out
that
nobody
wants
eurodi
yeah,
then
we
go
to
the
to
the
community
and
ask
what
what
are
the
next
yeah
big
pictures
you
think
about,
but
never
actually
test
it.
C
So
if
the
community
decides
to
do
some
other
product
or
some
people
say
they
they
want
some
other
product,
then
I
guess
with
a
core
unit
that
that
tests
out
this
stuff,
if
the
market
is
actually
wanting
this
and
yeah
putting
putting
their
money
where
their
mouth
is
or
if
it's
not
needed.
So
it's
it's
not
about.
C
F
Yeah,
it
definitely
does
a
little
bit
so
so
what
is
what
is
the
life
cycle
of
bureau
die?
You
know,
I'm
not
fully
aware
of
it,
so
we
would,
you
would
take
it,
you
you'd
run
it
you'd,
get
it
operational
and
then,
where
does
it
go?
Who
maintains
it
right?
Pe
is
already
you
know,
quite
quite
backlogged,
so
I'm
just
I
just
want
to
understand.
F
With
maker
is
that
the
core
unit
is
the
only
structure
and
what
I
heard
from
you
is
in
some
ways:
it's
almost
like.
You
know
it
would
be
analogous
to
having
being
a
third-party
service
provider
and
then
basically
putting
a
proposal
or
statement
of
work
for
each
product
forward
and
then
letting
maker.
Basically,
you
know
sign
off
on
the
projects
and
fund
them,
but
we
don't
have
that
structure
right.
F
So
the
core
unit
is,
is
the
only
the
most
effective
structure
right
now,
and
so
so
it's
the
question
is
two
parts
right:
what
happens
the
products
after
who's
going
to
maintain
them,
because
we
don't
have
that
technical
talent?
So
let's
say
at
month,
four
nobody's
willing
to
take
it
on.
Are
you
going
to
still
operate
euro
die
right?
Are
you
willing
to
do
that
and
to
commit
to
that?
And
then
you
know
again.
F
B
Yeah,
so
maybe
it's
naive,
but
I
guess
that
well,
let's,
let's
assume
that
euro
diet
works
out
and
it
gets
product
market
fit
approved,
and
we
see
that
it
works
good
that
we
have.
I
don't
know
whatever
number
of
of
your
die
minted
within.
I
don't
know
half
inch
or
something
like
this
either
there's
somebody
saying
I
want
to
participate
in
this
and
I'm
even
taking
the
lead
on
this
or
we
have
other
core
units
like
I
don't
know
growth
or
we
were
assets
who
basically
start
contributing
to
the
euro
die
mission.
B
B
B
A
A
E
E
This
is
something
that
someone
like
pe
is
gonna
have
to
take
over
correct
me
if
I'm
wrong,
but
also
would
it
be
possible
for
you
guys,
and
I
don't
know
what
kind
of
experience
you
have
to
also
work
with
someone
like
starknet,
which
is
a
core
unit.
That's
coming
up,
and
how
do
you
see
the
role
of
america
labs
in
something,
and
you
know
when
it
comes
to
the
development
of
ck
roll-ups
things
of
that
nature
layer
twos.
E
B
So
this
is
a
couple,
a
couple
of
questions,
so,
first
of
all
we
are
able
to
maintain
stuff.
I
mean
we
have
been
doing
this
for
quite
a
while
and,
to
be
honest,
most
of
the
stuff
we
have
been
doing
is
is
done
on
the
mvp
on
the
mbv
level,
for
I
don't
know
a
year
already,
so
we
are
already
in
maintenance
mode.
It's
not
that
we
cannot
do
maintenance,
it's
just
not
what
we
want
to
do
and
what
we
are
excellent
at.
B
We
are
excellent
at
prototyping
stuff
and
bringing
this
to
the
market
and
finding
out
if
it
works.
So
probably
you
need
a
bunch
of
different
people
to
help
us
doing
the
maintenance
stuff,
but
we
can
totally
do
that.
It's
not
that
we
cannot
do
it.
We
just
we
just
love
to
bootstrap
stuff
and
we
would
like
to
keep
boots
wrapping
and
if
it's,
if
it's
needed,
that
it
needs
to
be
transferred
to
someone
else
and
for
sure
it's
not
going
to
be
protocol
engineer
my
I'm
absolutely
sure.
B
Protocol
engineering
is
totally
not
interested
in
taking
the
burden
of
maintaining
a
second
stack,
and
I
think
it
would
be
a
waste
of
energy
as
well
with
all
those
brilliant
people
over
there.
But
it's
we
are.
We
are
thinking
or
we
are
right
now,
a
bunch
of
people
like
I
don't
know
less
than
100
people
participating.
This
is
not
where
naked
hour
is
going
to
be
in
a
year.
I
hope
this
is
not
why
I'm
here
it's
we
are,
we
are
going
to
grow.
We
are
going
to
decentralize
a
lot
more
than
we
are.
B
We
are
right
now
this
at
least
my
bet
on
this
topic.
Yeah
when
it
comes
to
collaboration,
I
mean,
of
course,
at
some
point.
We
need
to
think
about
how
we
deal
with
oracle's,
for
example,
but
we
are
not
going
to
request
from
from
the
co
from
the
oracle's
core
unit
that
they
built
some
kind
of
euro-based
oracle
set
that
we
are
going
to
use.
B
B
C
Yeah,
maybe
not
to
see
case
knocks,
but
maybe
I
can
add
to
this
so
first
of
the
maintenance
of
euro
die
for
me,
it's
always
like,
like
a
certain
threshold,
it
needs
to
be
met.
To
actually
say
we
have
broad
market
fit.
So
if
we,
if
we're
in
a
region
where,
like
some
people,
are
using
it
and
other
people's
are
not
using
it,
I
always
feel
that
we
then
feel
that
we
then
need
the
the
courage
to
tear
it
down.
Anyway,
I
mean
it's
with
all
the
startups.
C
So
if
we,
if
we
have
like
a
pretty
huge
potential
there
and
a
lot
of
people
using
it
and
a
lot
of
money
in
the
in
the
euro
die
contract,
I
I
can't
see
that
there
won't
be
an
opportunity
for
like
a
dedicated
operations
team
for
uruguay,
because
then
makers,
basically
making
money
with
this
and
from
at
least
from
a
traditional
company
perspective.
Then
then
you
basically
have
the
money
to
to
invest
in
the
operations.
C
Second
to
to
the
collaboration
about
ck,
snarks
and
all
stuff
I
mean
from
from
output.
From
my
perspective,
I
think
a
biggest
benefit
is
that
we
can
own
stuff
full
stack
and
that
that
has
a
big
potential,
that
we
can
basically
move
by
our
own
timeline
and
we
can
test
all
aspects.
So
if
we
ask
us
if
we
could
do
some
ck
snark,
smart
secant,
smart
contracts
or
so
on
that,
that's
not
really.
C
I
mean
that's,
that's
not
on
the
on
the
mission
side,
at
least
for
me,
for
maker
labs,
because
it's
not
like
the
full
stack
product
that
we
can
implement
and
ultimately
test
to
the
market
and
we're
just
contributing
to
something.
But
it's
not
like
in
our
hands
to
move
timeline,
go
to
market
and
and
test
the
stuff
we
want
to
test.
G
G
C
What
you
said,
something
that
only
devs
can
use
for
me.
That's
that
more
proof
of
concept.
So
so
you
prove
like
it's
technic
possible,
but
at
least
for
me
an
mvp
is
actually
something
that
the
end
users
use,
because
it
should
be
the
minimal
viable
product
for
the
end
user
and
not
for
some
devs
and
so
on,
because
we
can't
really
test
like
product
market
fit
with
developers,
but
because
developers
they
yeah.
C
They
can
handle
a
lot
of
issues
with
usability
and
so
on,
but
it
that's
the
whole
thing
so
so
the
whole
technical
step
below
the
user
interface,
it's
nice
to
have-
and
it's
nice
to
approve
this
with
with
a
proof
of
concept.
But
ultimately,
where
you
see
users
leave
your
product
or
not
use
your
product
is
basically
the
ui
and
the
user
experience.
C
So
I've
seen,
I
see
an
fmp
not
like
shallow
on
the
or
broad
on
the
on
the
deep
level
on
a
technical
level,
but
like
a
really
yeah,
really
sharp
tower.
That
goes
from
the
from
the
technical
basis
up
to
the
ui,
and
this
should
be
as
polished
as
possible.
But
it
should
only
support
like
a
minimal
viable
use
case,
and
then
we
can
test
this
one.
D
Well,
for
me,
it's
also,
depending
totally
on
the
only
audience
we
are
targeting,
because
if
we
are
talking,
if
a
product
targets
just
developers,
maybe
they
are
totally
fine
with
just
in
the
cli
and
that's
totally
fine
for
them.
But
if
we're
talking,
for
example,
like
a
wallet
that
end
users
should
use,
there
should
be
a
polished
ui
that
you
have
to
use
there,
and
this
is
also
part.
G
G
B
C
So
regarding
to
this,
maybe
maybe
that's
something
we
wrote
in
the
in
the
proposal
or
I
think
in
the
in
the
forum,
so
we
I
think
we
should
define
like
an
like
maximum
exposure
that
we're
willing
to
take
on
on
the
on
the
production
net
on
the
mainnet.
So
we
can
say
at
most.
So
if
everything
fails,
people
are
losing
only
this
amount
of
money.
C
G
C
B
I
mean
the
longest
project
I've
been
involved
was,
I
think,
two
or
three
years
at
101,
but
it's
still
running
so
I'm
just
not
be
part
of
it
anymore,
because
yeah
the
the
heart
problems
were
solved.
So
I
made
a
move
and
moved
somewhere
else
going
for
bootstrapping
again,
so
I
don't
know
I
I.
I
hope
that
we
don't
need
years
for
euro
diet
to
get
to
fdp.
To
be
honest,
I
don't
have
that
attention
span.
A
No,
I
don't
regarding
the
euro
die.
Actually
I
think
you
mentioned
something
about
doing
like
a
legal
research
to
see
if
it
was
feasible
and
and
what
not
so
my
question
would
be:
let's
say
that
it's
not
for
any
given
reason
or
that
there
will
be
too
much
risk
involved
for
for
for
u3,
for
example,
or
for
or
for
the
dow
in
general.
A
B
B
C
C
B
E
G
B
B
E
B
Of
having
nothing
to
work
on,
that's
not
on
the
list
of
problems
I'm
having,
but
I
mean
it's,
it's
it's
the
same
way
as
well.
We
had
this
question.
What
is
what
is
the
roadmap
beyond
three
months
and
my
answer
was
be
be
transparent
about
what
you
do
and
what
your
progress
is,
and
you
can
apply
exactly
the
same
mechanism
to
also
get
feedback
from
the
community
about
what
should
be
the
next
thing
to
work
on.
So
I
think
that's
that's
actually
not
hard.
B
H
Is
that
correct,
yeah,
okay
and
and
then,
as
you,
move
along
you're,
going
to
assess
whether
or
not
that's
a
viable
product
based
upon
a
variety
of
factors
that
that
you
know
obviously,
inputs
from
the
community,
your
team
and
others,
and
if
you
decide
that
that's
not
a
project
that
you
want
to
move
forward
is
what
I'm
hearing
is
that
you're
then
willing
to
take
direct
input
and
feedback
from
the
community
to
be
able
to
work
on
whatever?
The
next
thing
is
the
community
deems
necessary
for
the
protocols?
Is
that
correct.
B
B
A
H
It's
it
seems
like
a
lot
of
organizations.
I've
been
involved
with
there's
been
like
a
labs
like
you
propose,
or
some
sort
of
incubator
or
skunk
works,
that
happens
inside
of
the
organization
and
the
projects
that
they
work
on
a
lot
of
times,
that's
dictated
by
other
factors.
Besides
a
community,
and
I
just
wanted
to
to
ensure
that
there
could
be
work
that
rolls
your
way
that
that
the
community
deems
is
very
important
that
you
guys
go
well.
H
I
I
don't
really
feel
that.
That's
something
that
I
want
to
do,
and
so
because,
because
I
heard
there
was
a
there
was
a
number
of
comments
about
like
hey
how
you
guys
like
to
bootstrap
stuff,
and
I
really
appreciate
that,
because
I
think
the
innovation's
really
needed
in
the
protocol.
At
the
same
time,
sometimes
there's
work
that
you
do
that
you
don't
really
like
to
do,
but
it's
also
necessary
to
do
so
yeah.
H
B
I
mean
in
this
case
we
would
just
quit
right,
so
we
would
tear
down
and
say
no
and
we're
not
going
to
do
that.
I
think
well,
the
main
point
I
think
colin
already
made
it
it's
the
the
pattern
of
engineers
coming
up
with
things
and
then
just
build
it
without
this
thing
really
being
something
needed.
This
is
something
that
we
totally
avoid
and
that
we
hate
and
that
we
already
experienced
in
the
last
20
years
a
couple
of
times.
B
C
So
so,
coming
back
to
the
mission
of
maker
labs
is
so
we
we
want
to
bootstrap
like
new
products
and
test
mvps,
and
I
mean
me
personally:
I
I
get
the
enjoyment
to
to
test
out
products.
I
don't
really
care
about
what
kind
of
product
yeah
it
should
be
ethical,
but
I'm
I
mean
I
really
want
to
build
like
and
test
out
new
news
new
stuff
for
users,
and
I
really
want
to
want
to
see
the
users
holding
the
new
products
in
their
hands
and
then
testing
testing
all
the
stuff.
C
A
G
I
I
was
gonna
have
a
question,
but
it
was
more
or
less
the
same
as
zero's
just
sort
of
like
you
know.
If
the
community
decides
that
or
thinks
that
we
should
be
working
on
some
other
cool
new
awesome
project
rather
than
like
euro
die,
would
you
guys
consider
moving
to
that?
I
guess
at
least
not
obviously
saying
you
definitely
would
or
definitely
wouldn't.
C
C
G
Should
clarify
a
little
bit
so
I'm
imagining
a
hypothetical
scenario
where
the
dial
decides
suddenly
that
we're
going
in
a
whole
new
direction
and
if
euro
die
does
not
fit
into
that
direction.
For
whatever
reason,
I
guess
even
before
blake
product
market
has
been
approved
for
euro
die
like
would
you
consider
moving
to
something
else?
If
it
was
something
you
agree,
you
were
aligned
with
right.
I
guess.
B
B
Only
to
have
something
used
based
I
mean
I,
I
think
it's
it's,
it's
totally
reasonable
that
we
don't
have
it
yet
and
we
have
tons
of
other
problems
to
solve
all
fine
yada
yada.
But
I
would
like
to
do
that.
I
would
like
to
do
euro
die
and
I
would
rather
cross
the
bridge
when
once
we
get
there,
if
the
community
really
wants
to
either
shut
us
down
or
give
us
something
else,
then
I'm
going
to
make
up
my
mind,
but
I'm
not
saying
yes,
I'm
I'm
ready
to
ditch
it
next
week.
E
Yes,
I
guess
what
would
you
say
to
how
would
you
answer
an
opponent,
not
proponent
of
someone
that
would
say
you
know,
maker
dow
is
more
in
need
of
maintenance
and
quality
products
versus
prototypes,
and
I'm
coming
back
to
prototypes
again
sorry
about
that
and
the
reason
why
is
because
you
know
we
need
teams
core
units
that
can
make
things
from
the
start
to
to
go,
live
right
and
to
be
able
to
pivot.
So
what
would
you
answer
be
to
someone
who's,
an
opponent
to
that.
B
So,
first
of
all,
I
think
we
are.
We
are
proposing
to
do
exactly
this
building
and
basically
an
mvp
core
unit,
and
if
people
think
we
shouldn't
have
that,
then
please
don't
vote
in
favor
of
us,
but
instead
just
don't
accept
it.
That
would
make
a
lot
of
things
easier.
I
I
wouldn't
have
to
think
about
how
would
be
my
life
next
year
without
being
in
an
un
uncanceled
job
that
I
can
have
for
the
next.
B
I
don't
know
how
much
30
years,
no
not
30,
20
years
until
I
retire,
so
that
would
help
me
a
lot.
So
if
people
just
don't
like
the
idea,
please,
let's
just
not
make
this
happen,
but
on
the
other
hand,
I
think
we
have
a
lot
of
people
out
there
that
can
do
whatever
we
need
to
do
so.
It's
it's
not
that
we
are
bound
to.
B
We
can
only
hire
10
people
this
year,
so
we
have
to
be
very
selective
about
what
kind
of
people
we
hire
for
what
kind
of
jobs
we
we
want
to
have
we
we
are
limited
by
by
the
number
of
people
applying
right
now,
not
by
the
the
amount
of
money
we
can
spend.
So
I
wouldn't
say
that
I,
I
would
just
say
sorry,
but
this
is
not
a
problem.
It's
not
a
problem
that
we
should
go
for
quality
because
we
can
go
for
quality.
E
Roger
that
and
when
it
comes
to
product
market,
fit
right,
how
does
your
team
plan
on
besides
the
community,
giving
you
feedback?
And
you
know
I
might
say
something-
crazy,
like
hey:
how
about
a
die
sports
betting
app,
because
I
love
sports,
but
how
do
you
get
product
market
fit
for
different
regions
of
the
world
right,
like
I'm
thinking
like
south
america,
has
a
different
view
on
financial
freedom
versus
germany
and
nothing
against
you
guys.
But
so
I
think
you
get
my
idea
of
my
question
here.
B
I
don't
have
a
clearance
on
that,
yet
I
think
that's
something
we
need
to
find
out
together
with
the
community.
What
are
the
thresholds
colin?
I
think
mentioned
already.
What
are
the
thresholds?
What
what
are
the
metrics
we
want
to
observe
and
what
is
what
is
basically
the
goal
we
want
to
achieve
and
if
we
met
it,
that's
great
and
if
we
don't
well,
then
maybe
it's
just
not
a
good
idea,
and
I
I
doubt
that
euro
die
is
appealing
for
somebody
in
I
don't
know
brazil,
for
example.
B
They
don't
care
if
it's
usd
based
or
euro-based.
I
do
care
and
the
euro
market
is
substantial.
It's
not
that
we
are
asking
for.
I
don't
know,
let's
get
the
new
zealand
dollar
on
chain.
That's
that's,
probably
something
that
doesn't
sound
sound
right
now,
maybe
in
five
years,
that's
different,
but
right
now
I
I
guess
my
guess
is
that
the
euro
euro-based
stable
coin
on
the
assuming
blockchain,
would
be
a
big
game
changer
for
people
in
the
eurozone.
B
E
B
C
Back
to
this
growth
thing
frank,
you
had,
I
mean
how
to
measure
success.
Basically
I
mean
you
said
something
we're
getting
feedback
from
the
community
and
so
on.
I
mean
for
me
ultimately
is
basically
usage,
so
we
we
should
find
out
how
many
people
are
using
our
product,
and
I
mean
we
have
to
benefit
we're
working
with
a
product
where
people
put
money
in.
C
So
it's
not
like
we're
offering
a
free
product,
but
we
can
actually
measure
how
much
money
people
are
putting
in
our
product,
and
I
think
that
should
be
like
the
key
metric,
so
how
many
home?
How
much
money
is
in
our
product
and
then
it's
up
to
the
community
to
decide
on
a
threshold
to
say.
If
we,
if
we
reach
this
amount
of
money,
then
we
consider
this
a
success
or
else
we
consider
it
a
failure,
but
I
guess
so
so
the
metric
could
be
pretty
simple.