►
From YouTube: Open Decentralized Voter Committee | July 12, 2022
Description
The Voter Committee Calls are designed to invite MKR stakeholders to help the community agree on an overall top-down structure of categorizing the activities and strategic initiatives of the MakerDAOs decentralized workforce to create more specialized voter committees that cover each category.
In this call, Nik from Oracles Core Unit speaks on OCU roadmap, initiatives, and thoughts toward the Endgame Plan
A
All
right,
hey,
everyone,
welcome
to
tuesday's
dvc
call.
I
was
normally
scheduled
wednesday,
but
we
just
moved
it
over
here
to
tuesday
and
thank
you
all
for
joining
us.
I'm
thomas
floyd
with
govcoms
and
today's
agenda
is
we've.
We've
got
nick
from
oracle's
who's
going
to
talk
to
us
about
their
roadmap,
and
then
we
will
open
the
floor
to
any
questions
or
comments
about
next
presentation.
B
Okay,
so
hi
everyone
for
those
of
you
who
may
not
know
me,
I'm
nick
I'm
the
facilitator
of
the
the
oracle's
core
unit
and
and
I'm
a
little
bit
unfamiliar
with
with
the
format
of
these
calls.
I
have
not
managed
to
attend
one
of
the
the
dvc
calls
yet
so
I'm
going
to
try
to
speak
as
little
as
possible
and
just
give
maybe
10
minutes
or
less
on.
B
You
know
the
ocu
and
and
what
we're
doing
and
what
our
objectives
are.
And
then
I
want
to
just
have
the
rest
of
the
time
just
be
reserved
for
for
all
of
you
for
for
asking
questions
right,
because
if
it's
just
a
one-way
communication
thing
right,
I
could
have
just
written
a
forum
post
right,
and
I
want
you
guys
to
get
something
out
of
this
call
right
that
you
wouldn't
be
able
to
get
out
of
me
just
typing
up
a
foreign
post,
so
cool
so
oracle's
core
unit.
B
C
B
Position
where
we
had
really
just
accumulated
a
bunch
of
technical
debt,
everything
was
kind
of
being
held
together
by
you,
know:
duct
tape
and
bubble
gum,
and
this
was
fine.
You
know
for
launching
a
system
that,
had
you
know,
a
circulating
supply
of
30
million.
40
million
50
million
die
right,
but
as
the
system
scaled
quite
a
bit
over
the
past
year
right,
it
really
came
down
to
professionalizing
things.
So
we've
pretty
much
rewritten
everything
from
the
ground
up.
B
B
B
It
was
not
known
whether
this
was
just
a
temporary
mania
or
whether
this
would
be
a
sustained
increase,
and
so,
in
the
early
days
of
the
core
unit,
we
had
pretty
much
like
exclusively
focused
our
resources
into
trying
to
optimize
the
oracle
cost
down,
and
so
we
kind
of
tackled
this
problem
from
a
bunch
of
different
areas.
Right,
we
looked
at
it
from
the
the
smart
contract
level.
We
looked
at
it
from
a
how
often,
how
frequently
do
you
update
the
oracle
level
right?
B
We
looked
at
it
from
okay.
You
know
these
collateral
types
are
profitable
right.
These
ones
are
not.
If
we
off-board
these
collateral
types
right,
we
can
save
50
of
our
oracle
costs,
but
only
get
rid
of
like
you
know,
or
not,
even
get
rid
of
any
profit
right
you're.
Actually,
you
know
profiting
more,
but
you
know
by
by
only
scraping
you
know,
one
percent
of
our
revenue
were
less
right,
so
we
were
looking
at
that
problem
from
from
all
of
those
different
angles,
and
I
think
that
focus
will
continue
right.
B
We
are
in
the
fortunate
situation
right
where,
through
the
bear
market,
the
gas
prices
have
decreased.
You
know
they're
exponentially
lower
compared
to
what
they
once
were
right.
So,
instead
of
you
know
high
single
digit,
millions
right,
we're
now
probably
spending
you
know
less
than
a
million
a
year
on
oracle
gas
cost,
and
I
think
that's
a
great
position
for
us
to
be
in
right
that
we
can
not
have
to
spend
that
much.
B
B
B
You
know
you
can
look
at
things
like
dye,
stats
right
and
you
can
see:
okay,
here's,
the
medianizer
and
here's
the
osm
and
here's
the
last
time
it
was
updated
and
here's
the
queued
price
and
the
current
price
right,
but
one
it's
it's
not
in
a
format,
that's
very
easy
to
consume
and
and
two
it's,
it's
almost
there's
a
lot
of
contextual
information
missing
so
making
a
like
a
front-end
dashboard.
That's
you
know
easy
to
to
navigate
easy
to
to
process
the
information
right.
B
It's
in
a
kind
of
a
user-friendly
format
and
not
in
this
raw
blockchain
type
of
format,
I
think
is,
is
a
major
kind
of
initiative
that
we
want
to
undertake
and
it
kind
of
goes
hand
in
hand
with
the
business
side
of
things
right.
So
we
want
to
build
out
this
oracle's
business,
and
you
know
when
we
were
looking
at
this
right.
It
was
what's
holding
us
back
from
this
oracle
business
right
and
one
was
okay.
The
oracles
themselves
are
really
really
expensive.
B
Okay,
so
we
need
to
invest
the
resources
into
making
oracles
cheaper,
okay,
cool
we've
done
that
or
the
initiatives
are
are
underway
right.
We,
we
know
that
we
have
a
viable
product
that
makes
sense
from
a
numbers
point
of
view,
going
forward:
okay,
cool!
What's
the
next
bit?
Well,
okay,
the
this
like
process
right
to
create
an
oracle
or
to
get
whitelisted
on
an
oracle
right
going
through
through
governance
right.
B
It's
a
most
people,
look
at
our
governance
process
and
they
have
no
idea
right
what
their,
what
they're
looking
at
or
what
they
need
to
do,
even
just
going
through
the
governance
cycle
right
to
get
whitelisted
is
just
too
much
of
a
pain
right
when
you
can
just
go
on
the
chain
link
website
and
just
say
boom.
You
know
I
I
just
want
to
read
from
from
this
thing
right
great,
so
we
want
to
retool
the
oracles
to
be
more
accessible
in
in
that
type
of
way.
B
I
would
hesitate
to
even
call
it
a
whitelist
really
from
the
legal
counsel
that
we've
talked
to
right
it's
more
about
in
terms
of
liability
right.
We
need
to
protect
ourselves
to
an
extent.
So
really
what
we
want
to
do
is
insert
some
terms
and
conditions
into
the
oracle
smart
contract,
and
then
you
know
instead
of
saying
white
list,
it's
more
just
like
here's,
a
table
of
all
the
people
who
have
agreed
to
the
terms
and
conditions
right
and
so
now.
B
Okay,
you
can
white
list
yourselves,
but
by
whitelisting
you're,
really
just
signing
the
the
tnc
okay
cool
and
then
it's
an
acceptance.
Sure
it's
not
a
white
list.
It's
it's
an
accept
list
exactly
right,
and
you
know
part
of
this.
This
dashboard
is
not
just
like
right
displaying
the
the
like
properties
of
the
oracle,
but
it's
also
just
to
get
the
flow
of
of
accepting
yourselves
on
on
one
of
these
oracles
right.
In
the
ux
form
you
know
right
now
you
have
to
go,
find
the
smart
contract
address.
B
You
have
to
go
on
either
scan
or
you
have
to
do.
You
know,
go
through
your
little
web3
library
or
something
right
and
that's.
This
is
not
the
type
of
onboarding
experience
that
people
are
used
to
right.
You
should
just
be
able
to
go
on
the
maker
oracle's.
You
know,
site
click
on
the
you
know
the
I
don't
know
the
curve,
oracle
right
and
say:
white
list
me
or
you
know,
white
list,
this
address
great
and
meta
mask
pop-up
or
your
wallet
connect.
Pop-Up
right
boom
sign
the
transaction
done
right.
B
You
should
be
able
to
do
it
in
less
than
a
minute
right.
So
getting
that
that
our
our
goal
is
to
get
out
that
type
of
of
product.
Part
of
that
will
also
involve.
I
think
I
think,
branding
and
marketing
will
be
extremely
important
right.
We
have
created
a
brand
for
the
oracle's
product.
It's
called
chronicle.
B
I'm
I'd
love
to
share
more
information
with
you
about
that
branding
initiative,
but
essentially
it's
it.
It's
a
way
that
we
can
market
the
oracles
as
a
product.
That's
immediately
recognizable,
because
when
people
look
at
the
maker
logo
right
or
the
dye
logo
right,
they
they
don't
think
of
oracles,
they
think
of
maker,
they
think
of
dye,
they
think
of
vaults
right.
So
it
makes
sense
to
to
coalesce
this
product
around
its
its
own
little
brand.
B
Sorry
paper:
do
you
have
a
question?
I
see
that
or
I
don't
know,
if
that's
a
hand,
raiser
or
something.
Let
let
me
just
finish.
I
only
have
a
few
minutes
more
and
then
we'll
we'll
do
questions
we'll
do
questions
right
after
so
we
want
to
announce
this
branding
quite
soon.
So
at
eth
warsaw
we
are
gonna,
be
co-sponsoring,
along
with
some
of
the
other
maker
core
units
right,
so
we're
gonna
have
the
the
maker
logo
alongside
right
this,
this
chronicle,
logo
and
we'll.
B
I
think
we'll
do
like
a
soft
launch
announcement
of
the
the
brand
and
the
product,
offering
probably
in
the
weeks
right
before
eath
warsaw
and
then
do
kind
of
like
the
hard
launch
at
eth
warsaw
right
and
get
and
do
kind
of
a
presentation
there
right
that
we
can
have
recorded
and
then
kind
of,
recycle
as
as
media
right
to
on
on
social
media.
Further
the
other
core
initiative,
so
besides
right,
cost
optimization
besides
this
oracle's
as
a
business
right
besides
this
front
end.
B
Research
is
one
of
those
areas
that,
in
the
very
early
days
of
maker,
we
devoted
a
huge
amount
of
our
resources,
and
when
I
mean
huge,
I
mean
like
almost
50
of
our
resources.
Just
went
to
people
doing
research,
and
I
can
tell
you
it
was
probably
some
of
the
best
money
we
ever
spent
and
it
gave
us
years
and
years
and
years
worth
of
dividends
like
and
at
some
point.
B
It
would
help
keep
us.
I
think
the
focus
of
the
research
right
would
be
on
things
like.
How
do
we
keep
the?
How
do
we
optimize
the
cost?
Further
right?
How
do
we
build
more
trustless
oracles
right
that
maybe
don't
rely
on
feeds
as
a
consensus
based
trust
mechanism
right?
How
do
we
get
more
data
compression
right?
So
you
know
maybe
in
aggregate
we
have
lower
costs
even
with
higher
update
frequency,
because
we
are
compressing
the
data
right
or
because
we
have
more.
B
You
know
instead
of
having
like
this
contract,
is
for
this
one
particular
oracle
right
we
have
this
contract
is,
for
you
know
all
the
asset
types
that
are
updated
very
frequently
right.
This
other
contract
is,
for
you
know,
asset
types
that
we
only
update
once
or
twice
a
day
right
or
this
other
one
is
for
ones
that
are
only
once
a
week
or
something
right,
and
that
way
you
can,
you
can
again
start
min
maxing.
B
You
know
the
the
frequency
of
updates,
depending
on
kind
of
the
the
tier
of
of
of
asset
right,
so
for
something
like
eth
and
rap
btc
and
wrap
btc
right.
You
want
to
update
that
extremely
frequently
right.
The
dow
has
very
large
exposure
to
those
assets
right
having
a
very
low
latency
oracle
is
really
important.
B
B
We
can
handle
a
more
an
oracle
that
has
higher
latency
right,
which
will
reduce
the
the
oracle
costs
associated
with
that
right,
and
if
we
start
batching
them
right,
then
we
we
we
can
do
it
even
more.
So,
okay,
that's
I'm
looking
at
the
time
here.
I
I
think
that's
that's
kind
of
all.
I
want
to
say
in
terms
of
me
one
way
talking
to
you
guys.
A
C
B
Sure
so
I
I
think
one
important
thing
to
note
about
this
oracle
architecture
that
we've
made
is
that
it's
quite
blockchain
agnostic
for
the
majority
of
the
architecture
right
so
in
terms
of
a
future
proofing
right
all
of
the
stuff
that
happens
from
the
price
querying
side
to
the
feeds.
You
know
signing
these
price
messages
right
and
there
being
this
peer-to-peer
network
of
price
messages
right
and
that's
where
the
consensus
happens.
B
All
of
that
is
off
chain
right.
All
of
that
data
is
json
right,
so
it
doesn't
even
need
to
be
say
a
price
right.
You,
any
data
that
you
can
encode
in
json
format
can
be.
You
know,
data
that
you
can
pump
into
an
into
a
smart
contract
so
in
in
terms
of
right.
If
you
want
to
have
start
having
okay,
we,
let's
say
real
world
assets
right,
we
need
a
we.
B
We
need
some
kind
of
number
from
some
a
tester
right
or
we
need
some
kind
of
matrix
or
we
need
some
kind
of
signature
or
we
need
some
volume
numbers
or
we
need
some
signed
price
quotes
from
a
third
party
write,
an
auditor
we
can.
We
can
handle
all
of
that
right
depending
right.
We,
depending
on
the
data
format
right
we'd,
have
to
modify
the
oracle
smart
contract
itself
right
to
accept
that
type
of
data,
but
from
the
off
chain
component,
which
is
the
majority
of
of
the
architecture
right
we
can.
B
We
can
pretty
much
handle
anything
I'll
give
you
an
example,
the
new
maker
teleport
right
that
we
have
right.
It
used
to
be
called
wormhole
right,
and
this
is
going
to
allow
right
dye
to
be
transferred
between
different
chains,
right
from
ethereum,
to
optimism,
to
arbitrarium,
to
starknet,
to
zk,
sync
right
so
on
and
so
forth.
That
is
all
being
powered
by
the
same
oracle
architecture
that
we're
using
for
the
price
oracles.
B
B
What
the
front
end
then
does
for
maker
teleport
right
is
once
enough
feeds
have
attested
to
that
event
happening
right.
Is
it
collects
all
of
those
attestations
and
now
the
user
can
go
on
optimism
and
just
say:
okay
confirm
on
optimism,
right
and
it
the
front
end
will
submit
all
of
the
oracle
signatures
attesting
that
this
is
a
valid.
You
know
teleport
right,
so
the
architecture
I
think,
is
quite
diverse
in
in
what
it
can
do
right.
B
You
could
even
use
this
for
I
I
would
imagine
it
could
be
expanded
to
like
cross
chain
communication,
because
you
know
this
burning
of
dye
right.
It's
really
just
reading
an
arbitrary
function
right
and
saying
these
are
the
parameters
of
that
function
right,
so
it
the
fact
that
it
was
a
token
is,
is
kind
of
meaningless
right.
B
You
can
confirm
okay
yeah.
The
repayment
happened
right,
you
could
and
I'm
thinking
a
little
bit
farther
into
the
future
right,
but
you
could
have
liquidations
right
where
maybe
you
don't
want
to
liquidate
on
the
chain
where
the
vault
is
right
now,
maybe
there's
more
liquidity
on
another
chain,
and
so
the
maker
protocol
itself
wants
to
transfer
those
assets
to
the
other
chain
right
to
do
the
liquidation
on
this
other
chain
right.
So
all
of
that
is
possible
using
the
oracle
architecture
that
we
have
today.
C
B
Oh,
I
I
mean
from
the
real
world
asset
side.
I
think
we're
fine
too
right.
It's.
We
query
data
from
not
just
on-chain
sources,
but
also
off-chain
sources,
right
and
so
having
you
know,
some
kind
of
third-party
auditor
or
some
kind
of
asset
originator,
post
some
data
somewhere
right.
We
can
query
that
data.
A
C
Yeah
thanks
nick
so
like
these
meetings
are
kind
of
focusing
a
little
bit
on
the
handgame
plan,
and
so
I
have
some
questions
regarding
that.
So
basically,
the
way
it's
it's
written,
how
the
way
it's
planned
is
that
oracle's
also
will
support
these
metadows,
that
kind
of
split
off
from
maker
and
then
run
their
own
businesses
and
the
way
you
describe
it.
I
think
it's
it's
fairly
simple,
but
I'm
wondering
like
when
you
sell,
for
instance,
your
services
to
other
organizations
or
you
plan
to
sell
it.
How
exactly
does
that
work?
B
Sure
so
so
I
think,
there's
still
a
little
bit
of
an
open
question
on
how
we
want
to
structure
that
so
there's
I
without
getting
too
into
the
weeds
right.
There
are
considerations
right
from
the
technical
side,
from
the
scalability
side,
from
the
legal
side
and
from
the
business
side
right
that
all
sometimes
run
counter
to
each
other
right.
So
from
the
legal
side.
B
Maybe
you
would
love
to
have
every
oracle
customer
right
sign
a
contract
right
before
before
you
offer
them
any
oracle
services
right,
but
from
a
bd
side
and
a
and
a
scalability
side
right,
you
don't
want
to
be
constrained
by
having
people.
You
know,
managing
customer
accounts
right.
You
would
rather
have
everything
just
be
on
chain
and
decentralize
right
and
just
have
people
just
white
list
themselves
on
a
smart
contract
and
maybe
load
up
some
die
in
a
in
a
credit
account
right
and
then
their
credit
account
just
gets
automatically
deducted
right.
B
So
right,
that's
that's
the
most
decentralized
approach
right.
You
know
also
from
right
the
the
legal
side
of
things
right.
It
may
not
be
you
know
a
if,
if,
if
the
oracle
core
unit
is
managing
is
kind
of
themselves
managing
access
to
the
oracles
in
some
way
right,
then
the
oracle
core
unit
is
seen
as
running
that
oracle
service
and
legally.
We
would
instead
prefer
to
position
ourselves
as
we
just
develop
the
software
and
then
the
dow
right
decides
that
it
it
wants
to
to
run
that
software
right.
B
I
think
that
that's
like
a
legal
position
that
we
we
would
like
to
maintain
right
and
there's
there's
a
couple
other
factors
as
well
right.
So
I
I
would
say
it's
an
undecided
problem
on
on
how
best
to
go
about
it,
but
it's
it's
something
that
we're
we're,
considering
all
the
pros
and
cons
of
each
approach
and
we'll
we'll
find
the
the
sweet
spot.
B
B
I
I
would
prefer
not
to
in
a
in
a
recorded
setting,
but
to
say
that
there
are
a
lot
of
regulations
making
themselves
through
the
pipeline
right
now
that
are
related
to
defy,
and
by
running
you
know,
software
that
facilitates
some
of
these
defy
activities
could
put.
Whoever
is
running
that
software
in
at
some
kind
of
legal
risk.
C
A
B
B
2018,
as
for
light
feeds
right
light
feeds
are
the
ones
with
public
operators.
These
tend
to
be,
or
actually
all
of
them
are
public.
You
know
protocols,
majority
in
in
d5,
but
a
couple
external
as
well,
so
we
have
like
dydx
zero
x,
gnosis
ether,
scan
bitcoin,
kyber,
fura
argent,
my
crypto
d5
saver
and
the
last
one
of
those
to
be
onboarded
was
may
2021.
B
The
intention
is
definitely
to
onboard
more
feats.
If
you
look
at
the
budget
that
I've
presented,
I've
based
the
it
would
be
the
feed
stipend
component
and
not
only
have
I
budgeted
to
add
more
feeds,
but
I've
actually
budgeted
to
increase
the
feed
stipend
per
feed.
So
right
now
we're
paying
about
a
thousand
die
per
month
to
each
feed
and
a
lot
of
them
are
doing
it
because
you
know
it's
just
a
cool
thing
to
do.
B
But
the
thing
is
these:
take
real
engineering
hours
to
maintain
right
and
especially
as
we
as
the
software
gets
bigger
and
more
complex,
it's
going
to
require
more
powerful
servers
to
run,
and
so
the
existing
feed
stipend,
if
you
include
the
engineering
hours
for
maintenance,
start
to
really
come
up
short
and
that's
that
that
I
think,
is
a
problem.
So
I
I
do
have
budgeted
in
the
new
proposal
right
for
a
feed
stipend
increase.
B
B
If
we
want
to
have
maker
teleport
from
optimism
to
ethereum
and
from
ethereum
to
optimism,
then
the
feeds
need
to
run
a
optimism
node
and
right,
so
they
have
visibility
of
what's
happening
on
the
optimism
network
right.
If
we
want,
you
know
to
have
a
maker
teleport
to
arbitram
right
now.
The
feeds
need
to
run
an
arbitrary
node
right,
and
you
see
there's
this
going
right
with
stark
net
right.
B
They
need
to
run
a
stark
net
node
and
these
nodes-
some
of
them,
are
pretty
heavy
duty
right
as
those
blockchains
grow,
bigger
in
size
right,
the
longer
they
are
in
operation
right,
the
the
bigger
their
state
is,
is
going
to
grow
right
and
so
running.
The
client
for
those
blockchains
will
get
more
expensive
as
well
right.
So
this
is,
I
think,
right
now.
A
D
Yeah,
hey
nick.
That
actually
leads
me
to
my
to
a
question.
I
have
a
couple
of
questions
but
circling
forward
to
the
manual
token.
The
do
you
think-
and
maybe
you
can't
comment
on
this,
which
is
fine.
Do
you
think
the
token
can
be
used
for
price
feeds
and
the
reason
why
I
asked
is
because
you're
seeing
people
like
pif
networks
who
are
signing
up
all
these
price
feeds
and
they
sign
them
up
from
every
direction
you
can
think
of
right,
the
real
world?
And
what
have
you?
D
B
D
D
B
Like
the
the
the
reason
that
people
like
jaylink
and
piff
are
able
to
get
kind
of
these
more
high
profile,
feed
signers
is
because
they're,
basically
giving
them
a
ton
of
tokens
right
and
so
we've.
Never
you
know,
ocu
has
never
had
you
know
maker
tokens
to
give
to
people
right
and
we've
never
had
an
oracle
token
where
we
can
be
like
here's.
A
hundred
thousand
oracle
tokens
be
a
feed
for
us
right.
That's
traditionally
where
those
kind
of
business,
development
and
incentives
have
for
growth
have
kind
of
come
from.
B
B
B
B
So
in
our
position
right
now,
it
actually
doesn't
make
sense
to
onboard
more
feeds
if
we
keep
the
quorum
at
13.
right.
If
we
start
raising
the
quorum
and
start
spending
more
on
oracle
gas
costs
right,
then
yeah
then
maybe
it
makes
more
sense
right
now.
Oracle
gas
costs
are
really
low
right.
We
are
spending
less
than
two
weeks
per
day,
right,
so
conceivably
yeah.
B
We
could
raise
the
quorum
significantly
and
we
could
start
onboarding
more
feeds
right
and
you
know
in
the
big
scheme
of
things
the
oracle
gas
costs
are
are
still
very
low.
But
but
that's
that's
kind
of
this
constraint
that
we
have
right
now,
and
so
one
of
the
things
that
we
have
in
r
d
is:
how
do
we
get
away
from
the
amount
of
feeds
used
for
consensus
being
linearly
proportional
with
the
cost
to
do
that?
Oracle,
update
and
so
one
of
the
areas
that
we
found
is
there's.
B
B
D
B
B
Those
were
based
off
the
simulations
that
we
made
so
yeah
and
we'll
we'll
continue
to
do
those
right.
We
we
know
what
parameters
we
can.
We
can
tune
and
we
know
how
tuning
them.
You
know
changing
the
spread
parameter.
You
know
from
two
percent
to
one
percent.
You
know
how
much
that
will
increase
our
cost
right
or
how
much
it
would
reduce
our
cost
to
change
it
from
you
know,
two
percent
to
four
percent
or
something
right
for
collateral
types
right
that
are
really.
D
D
I
could
throw
one
more
in:
how
did
you
envision
the
some,
perhaps
new,
participant
oracle
feats
coming
in?
Do
you,
I
guess,
envisioned
a
chronicle.
I
believe
that's
what
you
call
it
right,
chronicle,
oracle's
web
page,
where
you
can
go
in
and
just
do
a
google
type
form
and
kind
of
drop
in
your
details,
name
of
the
company.
What
are
you
looking?
What
price
feed?
Are
you
looking
to
provide
things
like
that?
Okay,.
B
Like
like
the
way
we
the
way
we
have,
it
now
doesn't
scale
right.
Someone
goes
to
the
forum
and
posts
this
proposal
right
and
depending
on
when
they
post
the
proposal
right
it
may
not.
You
know
it
could
be
an
extra
week
or
it
could
be
one
week
less
right,
depending
on
the
timing
of
when
the
the
polling
votes
go,
live
right
and
the
implementation
side
of
things
right.
So
it's
a
that's
a
mess.
A
B
So
I
currently
don't-
and
the
reason
is
that
I
I
thought
from
a
real
world
asset
point
of
view.
We
would
be
much
further
along
in
some
kind
of
consistent
way
that
these
look
like
and
to
me,
it
still
seems
that
there
isn't
the
cookie
cutter
recipe
yet
as
soon
as
we
have
that,
I
think
then
we
can
start
looking
at
creating
this
framework
in
terms
of
like
what
actors
would
be
involved.
I
definitely
think
you
know
from
you
know
you
and
your
core
unit
would
be
involved
right.
B
B
Okay
yeah,
so
I
I
answered
both
of
those
right.
I
I
said
we
we
haven't
come
up
with
a
solution
yet
because
right,
there's
still
at
least
to
our
knowledge,
there's
uncertainty
over
what
a
stereotypical
real
world
asset
looks
like,
but
and
then
in
terms
of
the
actors
who
are
involved,
it
would
be
will's
core
unit
and
myself,
and
I
I
I
I
think
that
would
be
it.
I
think,
that's
all.
We
would
need
to
push
things
through.
A
B
Oh
okay,
I
definitely
think
there
would
need
to
be
some
kind
of
auditor
function
right
because
we
correct
me.
Maybe
you
have
different
thoughts.
I
don't
think
it's
appropriate
that
we
would
be
taking
the
asset
originators
at
their
word
on
the
numbers
that
they're
giving
right.
So
really
we
would
have
want
to
have
some
kind
of
third
party
auditor
right
that
would
agree
to.
A
C
B
We
may
have
one
day
have
to
follow
through
on
our
threat
and
submit
a
off-boarding
proposal
for
a
feed,
and
we
would
include
evidence
of
you
know
their
performance,
and
why
is
it
why
it
was
lacking
right?
So
we
could
show
this
feed.
You
know
you
can
see
is
a
big
outlier
to
all
these
other
ones
or
this
feed.
You
know
we
believe
maliciously
tried
to,
or
this
group
of
feeds
maliciously
tried
to
manipulate
some
price
and
therefore
we
are
we're
off
boarding
this.
This
set
of
feeds.
D
And
hey
nick
just
I
want
to
follow
up
on
chronicle.
This
is
exciting
stuff,
I
hope
to
be
in
warsaw
for
the
announcement
god
willing.
So
is
the
idea
here
that
once
it's
launched,
that
maker
could
incur
some
revenue
or
not
quite
yet,
it's
just
more
of
a
marketing
thing
like
how
do
you
envision
that
part.
B
B
I
think
getting
to
the
point
where
also
starts
offsetting:
well
subsidizing
the
core
unit
costs
for
sure,
but
when
it
starts
supplanting
the
like,
you
know,
being
above
the
coordinate
costs,
I
don't
really
have
those
projections.
Yet
until
we
start
seeing
you
know
at
what
rate
we
can
start
onboarding
people
right.
D
Got
it
and
just
to
make
sure
the
delegates
that
are
present
or
watch
this
later
on
understand
because
delegates
we
like
to
debate
a
lot
about
the
budgets
and
stuff
the
r
d
component
that
you
want
to
introduce
and
implement
that's
something:
that's
going
to
increase,
cost
keep
costs
about
the
same
like.
What's
what
are
you
thinking
there?
I.
B
So
I
didn't
want
to
hire
an
engineer,
pay
him
a
ridiculous
salary
and
then,
when
the
bull
market
was
over,
not
be
able
to
afford
paying
that
engineer
anymore
and
having
to
fire
him
right
that
that
didn't
make
any
sense
to
me.
So
we
basically,
I
just
said:
okay,
we
are
going
to
try
to
make
do
with
the
team
that
we
have
right
now,
but
we
won't
really
make
progress
on
any
initiatives,
we're
just
kind
of
treading
water,
so
to
speak
right.
B
So
that's
why
the
majority
of
our
past
year
right
was
dealing
with
the
technical
debt
right
was
doing
just
keeping
up
with
the
collateral
that
you
know.
Governance
wanted
to
to
onboard
right,
making
doing
some
of
those
low-hanging
fruit
cost
optimizations
when
it
came
to
the
oracle's
infrastructure.
D
Got
it
and
as
someone
that
is
part
of
the
maker
community,
you
know
you're
an
og
mkr
token
owner.
Do
you
mind
if,
if
we
get
some
commentary
on
you
or
what
your,
what
you
think
is
the
best
path,
fuller
for
maker
dow
as
a
doubt,
as
far
as
budgets
are
concerned
for
core
units,
because
that's
as
you
mentioned
a
second
ago,
you
guys
are
cutting.
I
believe
it's
about
10,
which
is
super
cool
right,
you're,
one
of
the
first
ones
to
do
that
as
a
core
unit.
D
What
are
your
thoughts
on
that
because
I
always
like
your
opinions,
man
and,
and
I
value
them
again-
you're
an
og
and
if
you
don't
mind
speaking
out
and
how
you
feel
about
what
other
core
units
should
do.
Obviously
all
of
us
delegates
have
different
opinions
and
care
token
owners,
but
yeah
like.
I
would
like
to
hear
what
you
think,
if
possible,.
B
Okay,
sure
I
I
do
have
a
hard
stop
at
the
in
in
a
minute
or
two
but
yeah.
I
I
think
that
I
I
would
love
to
to
give
a
quick
comment
on
that.
I
think
what
from
the
core
unit
side,
what
people
just
want
is
certainty
right,
it's
hard
to
do
any
kind
of
forward
planning
when
you
don't
know
how
much
money
you
will
have.
B
You
know
three
months
from
now
six
months
from
now
eight
months
from
now
12
months
from
now
right,
so
there's
core
units
right,
you
have
a
certain
budget
and
they
see
all
these
cost-cutting
initiatives
coming
through
right
through
different
initial
right
from
different
areas.
Right,
I
think
strategic
finance
is
doing
something
right.
I
think
the
delegates
right,
you
guys,
are-
are
kind
of
doing
your
own
initiatives
and.
B
It
it's
hard
it's
hard
to
it's
hard
to
plan
right.
I
don't
want
to
hire
someone
if
I
know
if
I
don't
know
that
three
months
from
now
my
budget
won't
get
cut
and
I
have
to
fire
them
again
right.
So
it
makes
forward
planning
really
difficult
and
right
the
longer
that
this
you
have,
this
uncertainty,
you're,
really
just
kind
of
crippling
the
the
core
units
and
the
longer
you
have
this
budget.
You
know
reduction
process
ongoing
in
governance
right.
It
worries
the
core
unit
contributors.
B
So
it's
hard
for
me
to
give
reinforcement
to
you
know
my
team
to
you
know,
make
them
feel
like
they
have
job
security
right
so
and
I
end
up
having
to
spend
you
know,
I
I
get
a
very
generous
salary
right
from
the
dow
you
want.
You
want
me
not
wasting
my
time,
you
know
doing
participating
in
budget
discussions
say
in
a
two
or
three
month
process
right.
You
want
me
focusing
on
you
know,
research
and
developments
on
you
know
optimizing.
B
The
oracle
costs
on
you
know,
building
out
that
oracle
business
right
on
hiring
the
talent
that
I
need
right.
So
at
some
point
right,
the
longer
you
drag
this
out,
the
more
you
know
of
of
the
money
that
you're
spending
on
core
units
right
now,
you're
really
wasting
right,
because
it's
just
these
wasted
bandwidth
cycles.
So
my
advice
is
just
whatever
you're
gonna.
Do.
D
A
All
time-
and
I
know
we
had
a
couple
more
questions
in
the
chat-
and
I
know
that
we
will
have
this
recording
posted
afterwards,
so
we
could
jump
on
the
discord
and
I'm
sure
nick
will
entertain
additional
questions.
But
we
thank
him
for
joining
us
today.
That
was
that
was
very
informative,
and
so
now
we've
got
about
30
minutes
left
I'd
like
to
open
the
floor
to
any
other
discussions.
D
E
Yeah,
I
kind
of
want
to
actually
echo
one
of
the
questions
that
came
from
chat
regarding
what
he
brought
up
surrounding
uncertainty
and
what
happens
with
this
budget
process,
because
I
think
we'd
be
more
cognizant
of
the
effect
this
has
on
the
protocol
and
not
drag
this
whole
thing
out,
so
we
so.
So.
I
really
liked
the
proposal
that
that
oracles
have
put
forward
with
this
grace
period
of
12
months,
and
I
think
we
might.
E
E
C
B
D
Yeah,
but
I
also
you
know,
I
I
think
about
the
end,
game
and
metadows
right
and
obviously
all
the
delegates
that
are
here
hope
we're
all
looking
to
support
the
end
game
and
get
the
metadows
m0
at
least
rolling,
and
I
know
that
right
now
we
have
some
proposals
coming
up.
We
already
kind
of
saw
a
preview
of
that
budget
from
chaos,
labs,
there's
other
budgets
that
are
coming
up.
So
I
guess
I
guess
what
I'm
thinking
is.
D
D
I
think
we
even
phrased
it
as
oas,
so
I'm
super
excited
for
that
to
finally
be
a
realistic
thing
right,
that's
going
to
happen
in
september,
but
I
guess
what
I'm
saying
is
like
do
any
of
you
guys
here
see
the
metadows
as
like
similar
to
what
google
did
back.
You
know
in
the
early
days
when
they
spun
off
just
as
a
search
engine
and
then
they
created
gmail
and
then
after
gmail
they
created.
I
don't
know
what
came
next,
but
maybe
google
cloud.
D
Do
you
guys
envision
the
same
thing
here
happening
and
if
that's
the
case,
do
we
want
to
support
new
initiatives
like
chaos
labs?
Do
we
want
to
support
r
d
for
our
core
units
who
want
to
expand
into
other
areas?
I
guess
that's.
That's
kind
of
like
the
question
I
have
for
the
other
delegates
or
any
of
the
core
unit
members
or
even
mkr
token
holders
here
who
are
here
today.
A
E
Yeah,
it's
a
direct
answer.
Okay,
I
think
there's
a
couple
of
things
to
consider
here
with
the
metadatas.
I
think
we're
going
to
be
in
a
transition
period
right
so
for
some
time
we're
going
to
actually
have
to
run
two
systems
in
parallel,
we're
going
to
have
to
start
the
the
slow
onboarding
of
the
metadose.
At
the
same
time,
we're
going
to
have
to
run
everything
else
more
or
less
the
way
we
had
already
have
it,
so
we
kind
of
have
to
keep
two
thoughts
in
our
head.
E
At
the
same
time
when
it
comes
to
onboarding
new
initiatives.
At
this
point,
I
think
I
think
we
should
be
extremely
reluctant
to
do
so.
I
mean
I
have
branded
myself
as
a
hawk
in
this,
but
being
that
means
being
fiscal
conservative,
and
that
means
also
being
more
restrictive
with
new
initiatives.
I
would
much
rather
stop
unit
initiatives
and
onboardings
than
having
to
go
through
the
off-boardings,
which
we
are
now,
because
I
think
the
off-boardings
are
very
damaging
to
the
organization,
and
I
don't
like
onboarding
people
for
them
to
fail.
A
C
That's
exactly
what
we
should
we
should
be
focusing
on
like
I.
I
support
the
engine
plan
because
I'm
not
sure
about
this,
this
alphabet
and
all
analogy.
But
for
me
this
kind
of
clarity
of
structure
that
you
have
this
immutable
kind
of
car
and
then
these
experiments
that
can
run
and
fail
or
run
and
succeed.
A
C
At
maker,
and
personally,
I
feel
like
we-
we
just
need
to
decide
as
an
org
like
I've
also
signed
up
as
a
hawk,
so
I
kind
of
tend
to
say
another
budget
for
chaos-
labs.
I
don't
know,
maybe
not
now,
and
let's
figure
out
like,
I
think
we
have.
We
have
other
stuff
to
get
through
first
in
a
way,
but
that's
my
opinion
and
that
love.
I
love
this
discussion
because
I
think
we
need
to
come
come
to
a
common
understanding
of
what
that
future
looks
like
like
the
immediate
future.
F
Yeah
I'll
just
come
in
and
sort
of
second,
what
everyone
is
for
saying,
but
tie
it
together.
It's
basically.
I
think
that
frank's
question
is
something
that's
more
appropriate.
I
think
for
office
hours,
especially
considering
we
came
in
here
to
talk
about
like
oracles
as
they
relate
to
dbc
calls
and
the
metadow
plan.
F
I
just
sort
of
want
to
echo
something
nick
said
to
sort
of
bring
it
back,
which
is
the
uncertainty
is
troubling.
So
I
hear
your
guys's
point.
I
think
that's
something
we
should
definitely
try
to
resolve
at
least
as
much
as
we
can.
But,
more
importantly,
I
think
the
metadata
thing
lacks
the
like.
We
can't
implement
that
just
yet.
F
I
think
right
now,
there's
a
lot
of
those
pieces
are
missing,
and
so,
if
we're
really
going
to
be
signing
up
for
that,
we
need
to
really
be
thinking
of
that
wedge
between
the
current
time
and
then
what
we
want
to
see
in
the
future
and
just
be
a
little
patient
like
don't
just
immediately
assume
that
it's
like
going
to
be
these
nodes
that
run
perfectly
or
whatever
it's
like.
There's
steps
to
take
until
we
actually
get
to
that
transition
point.
If
that
makes
sense,.
F
F
The
floor
yeah,
I
think
thanks
yeah.
I
wanted
to
actually
to
get
a
bit
of
a
view
from
from
from
the
delegate
group
on
kind
of
like
a
possibly
future
revenue
sharing
type
of
agreements,
because,
like
I
think
the
the
oracle
discussion
was
actually
quite
interesting
from
that
point
of
view
that
right
now,
we
kind
of
like
we're
really
kind
of
like
we're
running
that
it's
like,
I
guess,
a
costly
exercise,
but
it's
actually
one
that
it's
very
important
for
the
protocol.
F
But
at
some
point
you
could
have
you
know,
accidents
that
are
generated
when
actually
that
oracle
services
provided
as
as
a
services
as
people
were
saying
that
might
be.
You
know,
used
by
different
protocols
across
chain
and
that
produces
some
sort
of
accident.
So
so
how
are
you
guys
thinking
about
like
how
the
dow
should
approach
those
types
of
accidents?
E
E
Some
are
kind
of
independent
company
that
is
partially
funded
by
maker
now
and
there's
also
this
question
of
who's
actually
benefiting
from
this,
and
I
think
we
should
stratify
that
a
little
bit
because
right
now
there's
a
bit
of
a
hodgepodge
and
there's
kind
of
different
rules
for
the
different
core
units,
and
I
think
that's
unfortunate
going
forward.
So
I
think
once
we
start
implementing
the
metadata
at
least
we
should
stratify
this
and
I,
in
my
view,
there's
just
two
basic
ways
to
look
at
this.
E
As
a
so
and
my
interpretation
of
how
the
metadatas
are
supposed
to
work,
I
think
they
are
much
more
going
to
be
independent
entities,
which
means
that
they're
getting
some
form
of
seeding
capital
and
then
we
send
them
on
their
way
and
and
if
they
manage
to
turn
the
profit
and
then
go
back
to
the
metadown,
if
they
don't,
then
they
fail
and
they
died
and
better
the
obstacle
goes
away.
That's
my
interpretation!
So
far.
F
F
Actually,
even
though
the
the
the
software
itself
is
is
free,
I
would
say
like
red
hat,
for
example,
software
itself
is
actually
free,
but
the
the
the
supporting
service
that
is
provided
is
the
one
that
is
kind
of
like
is
charged
by
different
providers,
and
I
think,
like
oracle's
was
one.
Of
course
you
got
like
have
like
sort
of
like
product
associated
with
it,
and
that's
why
my
discussions
on
product
lines
are
important,
but
but
yeah
I
was
thinking.
D
F
I
think
I
I
suppose
actually
deco
is
one
example
that
is
the
first
one,
that's
kind
of
like
coming
coming
up
in
the
dow,
because
they
yeah,
of
course,
they're
providing
they're
building
a
service,
and
they
are
thinking
about.
Like
part
of
that
services.
Kind
of
is
charged
to
the
dow
part
of
the
expense
and
part
of
it
is
kind
of
like
they
are.
They
are
obtaining
from
from
actually
selling
that
service
to
different
clients,
so
yeah,
exactly
yeah
supporting
different
products.
D
Yeah,
almost
almost
personally,
a
3f
delegate
is
a
supporter
of
that
model.
A
revenue
share.
You
know
it
yeah.
This
is
the
first
time
the
dow
has
tried
it,
and
I
think
that,
with
the
release
of
the
end
game
and
m
m0,
it's
going
to
be
interesting.
To
finally
see
it.
Go
live
right,
it'll
come
into
fruition,
whatever
you
want
to
say,
but
I
do
think
that
you
know
mkr
token
owners
and
delegates
do
need
to
be
careful
and
make
sure
it's
structured
properly.
D
D
Oracles
could
also
be
something
that
and
the
reason
why
I
say
this
by
the
way-
and
I
want
to
make
sure
I'm
being
clear-
is
that
it
it
has
an
incentive
portion
to
it,
and
I
think
that
incentive
itself
allows
a
team
like
deco
to
be
inspired,
keep
inspired
and
also
it's
kind
of.
Like
you
know,
I
told
one
of
the
delegates.
This
is
kind
of
like
back
in
my
days
when
I
was
on
wall
street
right.
I
always
had
a
quota
and
my
quota
as
an
example
could
have
been
like.
D
I
need
to
do
20
000
of
revenue
per
week
or
per
month,
and
if
I
don't
make
20
000
per
revenue
per
week
or
per
month,
what
have
you?
I
don't
make
a
single
dollar.
All
I
get
is
a
basic
flat
salary,
so
in
other
words
the
first
20
000
needed
to
go
to
the
investment
firm
that
I
was
working
for
back
then,
so
I'm
a
big
fan
of
it.
It
could
be
because,
yes,
you
know
my
experience,
my
background
does
go
back
to
that
to
sales,
so
to
speak.
D
A
F
Whether
you
see
also
like
an
evolution
of
the
the
business
model,
essentially
from
a
from
a
revenue
generation,
point
of
view
as
well,
whether
you
actually
have
those
considerations,
especially
because
of
the
talk
about
oracle's,
which
is
kind
of
you,
know
really
evolving
in
a
product
type
of
like
roadmap.
And
it's
thinking
about
all
those
things.
I
think
it's
actually
a
good
opportunity
to
have
the
discussion.
A
A
C
D
I
mean
I
can
take
a
shot
out
of
it.
I
mean
there's
a
lot
of
a
lot
of
of
this.
Of
this
stuff
has
been
written
right,
there's
a
lot
of
tokenomics
behind
it.
So
to
retro
I
would
say
you
know,
take
a
look
at
there
and
dig
dig
in
a
little
bit
right,
like
there's
already
the
they're
thinking
of
minting
mkr
right
to
reward
the
metadows.
D
I
believe
roone
was
talking
something
in
the
number
of
forty
thousand.
I
think
today,
in
the
governor's
channel
he
was
asking
how
much
of
mkr
is
already
accounted
for
pretty
much
from
core
units
things
of
that
nature,
so
I
think
a
lot
of
that
as
far
as
how
much
the
concept
is
prepared
to
spend
on
enabling
the
strategy
that
yeah,
I
agree,
you
know
raphael,
you
know
we
we
don't
know
yet.
D
D
Look
I'm
not
gonna
lie,
there's
probably
some
core
units
that
I
voted
for
that
probably
shouldn't
have
never
been
on
board.
It
probably
should
have
been
bundled
together
into
one
core
unit.
So
you
know
a
lot
of
these
core
units.
Probably
in
my
opinion
might
not
be
around
shoot.
Even
some
of
us
delegates
might
not
even
be
around
right,
so
a
lot
is
going
to
change
over
the
next
10
years.
D
In
my
opinion-
and
I
think
what
I
believe
in
is
that
this
is
the
best
path
forward
for
maker
thou
and
I
like
to
see
everybody
just
buy
in
little
by
little,
and
I
think
the
best
way
to
do
that
is
either
by
attending
these
meetings
or
just
kind
of
putting
your
head
down
and
reading
up
on
some
of
this
stuff.
So
yeah
that
doesn't
answer
your
question
retro,
but
it's
the
best.
I
have
right
now.
C
A
F
F
I'm
sad
that
I'm
one
of
my
biggest
concerns
with
this
plan
is
that
we're
effectively
launching
a
bunch
of
icos
and
tying
them
into
makers
to
economics,
and
if
it's
not
done
100
buy,
the
book
is
going
to
be
significant
regulatory
risk
and
I
think
the
dow
is
going
to
have
to
decide
whether
metadata
is
going
to
fund
that
risk
themselves
or,
if
maker's,
going
to
pay
for
it
maker's
going
to
pay
for
it.
Every
time
a
metadata
is
gonna,
be
launched,
it's
gonna
be
really
expensive,
yeah.
C
Yeah,
I'm
not
so
sure
if,
if
like
I
mean,
for
instance
like
the
the
stuff
that
dydx
put
out
about
their
like
currency's
currency
purpose
trust
fund
for
their
grants.
Now
I
mean,
if
a
tower
successfully
launches-
and
there
are
some
legal
considerations
there-
then
they
should
be
published,
especially
if
maker
is
paying
for
them
and
that
might
serve
as
a
blueprint
for
others.
A
D
No,
I
just
want
to
say,
like
the
beauty
of
this
metaverse
workforce
right
that
has
been
envisioned
by
the
co-founder
maker
dao.
Is
that
you
guys
think
about
it
like
we're,
not
we're
not
setting
up
offices
in
warsaw,
berlin,
lisbon,
sao
paulo,
buenos
aires
and
san
francisco
right,
we're
we're
a
remote
workforce
and
that's
a
huge
cost
savings
by
that
to
begin
with,
and
and
if
one
metadata
cannot
function
right,
you
can
spin
up
another
metadow
down
in
kenya
on
narobi
right
for
all
this
work,
for
whatever
that's
worth
so.
D
My
point
is,
I
think,
there's
a
beautiful
thing
happening
here
and
I
think
we
all
just
kind
of
like
need
to
expand
our
minds
and
kind
of
like
realize,
like
the
opportunity
that
we're
creating
here
so
there's
definitely
a
lot
of
risk
involved
in
this.
But
I
think
that
all
of
us
are
here
because
we're
willing
to
take
that
risk
right.