►
Description
For the 20th episode of CULPS, Daniel Kremerov (@danik) will be presenting the Sidestream Auction Services Core Unit, whose purpose is to improve security and transparency of the Maker Protocol by providing auction service through open-source development.
Sidestream Auction Services Core Unit - https://forum.makerdao.com/t/mip39c2-sp25-adding-sidestream-auction-services-core-unit-sas-001/10796
Sidestream Auction Services Core Unit Budget - https://forum.makerdao.com/t/mip40c3-sp44-adding-sidestream-auction-services-core-unit-mkr-budget-sas-001/10802
Discussion thread from the call:
https://forum.makerdao.com/t/core-unit-launch-pod-sessions-session-20-sidestream-auction-services/10959
A
Hello,
everyone
welcome
to
another
co-unit
launchpad
session.
My
name
is
juan.
I'm
the
facilitator
at
the
scs
coordinates
sustainable,
consistent
scaling
and,
as
you
probably
know,
one
of
our
initiatives
is
to
run
an
incubation
program
where
we
make
sure
that
teams
get
what
they
need
to
be
an
independent
core
unit,
and
today
I'm
joined
by
the
team
of
sidestream,
which
is
part
of
the
incubation
program.
So
I'm
I'm
a
little
bit
biased
on
this
one.
B
All
right,
let's
go
yeah,
I'm
daniel,
I'm
one
of
I'm
the
facilitator
of
the
sidestream
auction
services
group
yeah.
As
one
said,
we
are
an
sas
incubation
team
that
started
in
june
and
today
we're
just
gonna
introduce
like
ourselves
and
also
what
we
have
done
so
fine.
What
we're
hopefully
gonna
do
in
the
future.
B
B
B
Some
of
our
reference
projects
are
like
propriet,
which
is
a
portal
for
real
estate
pricing,
sp
iot,
which
is
a
platform
for
sensor
data
visualization,
and
we
have
also
done
like
various
projects
in
financial
services
and
the
centralized
world
like
kyc
vc
and
a
bunch
of
other
things
and
like
for
the
for
working
with
maker.
Daw.
We
imagine
our
like
core
unit
to
become
a
separate
business
unit
of
side
stream
and
we
hope
to
leverage
like
our
software
agency
know
how,
by
when
building
auction
services.
B
The
team
that
is
going
to
be
the
core
unit
of
five
people,
some
of
us
who
are
gonna
work,
half
time
and
some
full
time,
so
I'm
as
that's
a
co-unit
facilitator
lucas,
who
is
sitting
next
to
me
as
a
product
manager,
valentin
and
ben,
are
full
stack
developers
and
nieuws
is
a
devops
engineer
and
also
a
full
stack
developer
and
yeah.
We
have
already
worked
together
on
a
bunch
of
other
projects
before
that.
B
So
now,
let's
talk
briefly
about
the
motivation
for
having
a
dedicated
core
unit
for
auction
services.
For
that
a
quick
recap
on
liquidations
and
auctions
and
then
general.
So
if
we
have
a
collateral
such
as
ease
that
falls
below
a
certain
collateralization
ratio,
the
vault
has
to
be
liquidated
to
protect
the
protocol
to
pay
back
the
outstanding
debt.
B
C
C
C
So,
let's
directly
dive
into
the
vision
that
we
came
up
and
our
vision
is
to
provide
and
maintain
systems
on
top
of
the
auction
mechanism
that
contribute
to
security
and
growth
of
the
maker
protocol.
Now,
these
systems
that
we
are
going
to
provide
and
maintain
will
increase
the
transparency
and
also
generate
insights
by
visualizing
auction
data.
B
Yeah
next,
let's
talk
about
our
strategy,
so
how
we
gonna
execute
on
this
vision,
yeah,
we,
we
came
up
with
a
strategy
that
is
centered
around
challenges
that
we
anticipate
along
the
way.
So
we
have
five
challenges
and
we
also
have
five
solutions
and
they
have
actually
a
many-to-many
relationship
to
each
other.
So
one
challenge
is
solved
by
several
solutions,
and
one
solution
also
caters
to
solving
like
several
challenges.
B
Second
challenge
is
about
informed
decision
making.
So
in
general
we
want
to
know
if
auction
participation
is
healthy
and
then
also
measure
and
make
decisions
on
things
like
okay,
how
well
the
ui
is
used.
How
is
user
changing
over
time,
but
also?
How
are
people
integrate
interacting
with
options
use
scripts
and
how
healthy
is
this
whole
keeper
ecosystem
search
challenge
is
prioritization,
so
building
the
right
things
in
the
right
order.
B
B
So
the
quality
of
everything
we
do
need
needs
to
be
very
high,
and
we
also
need
to
ensure
that
these
things,
actually
yes,
stay
safe,
like
even
if
the
protocol
in
the
infrastructure
scales
and
the
last
challenge
is
that
we
think
there's
a
quite
heterogeneous
user
base.
So
it's
important
that
auction
mechanism
actually
also
accessible
for
new
users
and
not
just
for
expert
users,
and
but
on
the
other
hand,
it
should
also
be
rest
relevant
like
for
existing
users
and,
most
importantly,
what
is
that
like?
C
Right
then,
now,
let's
have
a
closer
look
on
the
different
solution
approaches
we
see
to
tackle
the
just
mentioned
challenges
first
of
the
simulation
of
failure
modes.
So
we
want
to
model
the
different
risks
and
conduct
regular
fire
drills
so
that,
in
case
of
an
actual
emergency
event,
we
are
prepared.
C
C
We
want
to
have
very
short
time
to
market
through
automation
and
standardization,
for
example,
with
an
automated
ci
cd
pipeline
everything
we
build.
We
want
to
build
modular
and
in
a
reusable
way,
and
we
will
deploy
sops
guides
and
checklists
again
to
provide
transparency
and
comprehensibility
in
everything
we
do.
C
C
So
what
we
have
here
is
basically
a
table
with
all
of
the
active
auctions.
Of
course,
right
now
we
are
here
on
the
kovan
testnet,
since
there
are
no
active
auctions
on
the
mainnet,
if
there
haven't
hasn't
been
a
liquidation
event
in
the
last
couple
of
minutes
yeah.
So,
as
I
already
said,
you
can
see
the
different
active
auctions
in
this
table
with
the
current
auction
price.
C
We
provide
different
kpis
on
the
auction,
that
is
so
to
say
the
one
market
and
then
the
other
kpis
that
we
provide
is
basically
the
second
market
side.
In
this
case,
we
for
now
focus
on
uni,
swap
where
there
is
then
the
arbitrage
opportunity,
and
we
also
want
to
give
insights
already
to
the
user
on
the
potential
profit
he
can
make
in
participation
in
this
auction,
but
also
give
a
disclaimer
already
on
the
transaction
fees
that
will
be
insured
by
auction
participation.
C
Now
this
is
a
lot
of
information
that
one
has
to
process
when
navigating
through
this
ui
and
since
we
want
to
build
very
accessible,
uis
and
also
cater
for
unexperienced
users.
We
have
implemented
this
switch
over
here
that
provides
a
lot
of
context
and
allows
an
unexperienced
user
to
get
insights
on
what
this
whole
is
about.
C
There
is
a
direct
connection
to
the
metamask
integration,
so
when
the
user,
for
example,
switches
the
network
from
the
metamask
integration,
that
is,
this
is
directly
reflected
in
our
ui
or,
for
example,
when
the
user
tries
to
connect
with
a
network
that
is
not
supported
by
the
ui.
This
is
also
shown.
C
C
So
you
should
hopefully
see
it
now
all
right,
then,
to
give
a
glimpse
on
the
current
road
map
that
we
have
in
front
of
us.
So
we
want
to
launch
our
mvp
by
the
beginning
of
november
and
then
the
next
feature
that
we're
planning
to
build
is
a
twitter
notification
bot
that
allows
to
draw
attention
within
the
community,
but
also
outside
the
community
and
bring
actual
users
to
the
ui
that
we
are
building.
C
C
B
Last
slide,
so
let's
look
at
the
budget
so,
as
said
before,
so
this
is
a
permanent
team,
3.5
full-time
equivalents.
I
think
the
main
position
here
is
just
a
contributor
compensation,
which
also
includes,
as
usual,
all
the
social
insurance
fees
and
everything
else.
And
then
there
are
a
few
kind
of
normal
positions.
B
We
have
reserved
some
budget
for,
like
traveling
events,
office
space
and
some
like
audits,
and
all
these
things
that
might
come
up
a
few
things
that
I
I
can
share
a
few
words
more
on
on
the
one
and
18
subscriptions.
So
this
is
mostly
infrastructure
costs
that
we
expect
so
right
now
we
just
have
a
few
aws
servers,
but
this
might
increase
over
time
and
then
there's
a
budget
reserved
for
that
gas
costs
as
we
expect
to
have
to
test
quite
a
lot
of
things
on
mainnet,
professional
and
legal
services.
B
A
B
Ensure
that,
like
yeah,
the
core
unit
is
not
liable
for
for
any
mistakes
that
a
user
might
encounter
and
the
last
position
that
is
worth
talking
about
is
engineering
contractors.
So,
as
said
before,
we
are
also
software
development
agency
on
and
already
throughout
the
incubation
program.
From
time
to
time.
B
We
have
also
yeah
worked
together
with
some
other
people
from
our
company
that
supported
with
some
less
critical
work,
like
ui
components,
for
instance,
to
just
have
more
speed
when
it's
possible,
and
we
might
continue
to
to
do
that
from
time
to
time
when
it
makes
sense,
and
it
might
also
have
the
advantage
that
in
case
the
co
unit
needs
to
scale
further
in
terms
of
head
count.
We
already
have
people
that
are
more
or
less
familiar
with
the
code
that
has
been
built
by
the
core
unit
and
next
to
the
die
budgets.
A
Oh
yeah,
sorry,
I
didn't
see
that
okay
good,
are
there
any
questions,
or
I
mean
I
can
start
see
if
there's
no,
no
pressing
matter
from
david
or
pros
or
anyone
else
yeah.
I
was
curious.
Obviously
this
makes
a
lot
of
sense
for
the
crypto
collaterals.
Do
you
have
plans
to
do
these
type
of
services
for
any
of
the
real
world
assets
integrations
as
well.
B
A
Think
that's
much
harder
right
bros
because
you
need
to
go
through.
I
think
there's
like
legal
things
to
do
and
I
need
to
liquidate
the
assets
in
the
real
world
and-
and
it
can
take
weeks
or
months
so
I
think
that'll
be.
I
can
imagine
it
could
be
at
least
a
lower
priority
in
the
for
the
moment
being
yeah.
A
It
seems
that
it's
right
now,
it's
heavily
focused
on
on
users
and
accessibility,
which
is
great,
and
I'm
happy
to
see
that
have
you
guys
also
considered
any
type
of
integrations
with,
for
example,
exchanges
or
or
with
any
other
type
of
automatic,
bots
or
keepers.
That
would
run
these
auctions
as
well.
Can
you
comment
on
that?
A
bit.
B
A
B
A
C
B
A
A
B
Already
worked
a
lot
on
this,
like
rfc,
with
scs
team,
with
incubation
program
and
also
talked
in
this
process
already
with
a
lot
of
different
call
units,
but
here
now
we're
in
the
next
weeks
we
yeah
hope
to
campaign
a
bit
more.
We
also
be
in
this
one
next
week
hope
to
meet
many
members
in
person
and
then
yeah
by
the
end
of
the
month.
We
want
to
launch
the
mvp
and
then
also
the
map
will
be
up
for
voting.
A
A
B
B
B
A
B
Yeah,
I
think
it
was
somewhere
in
the
strategies
that
we're
also
gonna
work
with
a
public
roadmap.
So
where
you
can
everyone
sees
what
we're
gonna
so,
basically
the
roadmap
we
just
shared,
but
in
more
detail,
then
you
can
either
comment
on
these
things,
but
also
propose
like
new
new
issues,
for
the
backlog.