►
From YouTube: BLIP BOUNTY: Baselined Background Check
Description
This is a clip taken from a Baseline Protocol Core Devs call which took place Monday, April 4 2022, where the following BLIP (baseline improvement proposal) was discussed- https://github.com/eea-oasis/baseline-blips/issues/25
A
Okay,
so
the
idea
of
this
one
is
essentially,
you
have
an
apartment,
complex
that
that
has
an
applicant
right,
say
bob
and
bob
wants
them
to
so
they
require
a
background
check
right
and
bob
wants
them
to
know
whether
or
not
he's
a
safe
person
to
rent
to
without
them,
actually
seeing
the
full
scope
of
his
background
checks.
So
he
doesn't
want
them
to
see
like
listed
criminal
record
credit
score
income
statements,
all
of
the
different
things
that
would
come
back
to
the
to
the
bureau.
A
That's
actually
running
this
check,
so
the
the
baseline
implementation
here
is
to
have
some
sort
of
algorithm
that
would
show
to
the
complex
just
a
yes
or
no
of
yes,
you
can
rent
to
him.
No,
you
shouldn't
rent
to
him
based
on
some
sort
of
msa,
that's
kind
of
agreed
by
the
the
apartment,
as
well
as
anyone
who
is
applying
to
lease
with
this
department,
and
that
way
they
can
be
sure
that
you
are
getting
kind
of
enough
of
a
result
of
whether
or
not
they
should
be
rented
to
without
them.
B
A
C
Yeah,
so
it
is
so
so
how
how
how
it
currently
works
is
that
you
basically
have
a
centralized
entity
that
that
that
collects
all
the
information
from
the
different
other
entities
right,
so
they
they
know
everything
right.
If
you
want
to
do
it
in
it
in
a
decentralized
way
right,
you
you,
you
send
the
you
send
the
request
to
all
the
agencies.
You
yourself,
because
right
someone
wants
a
background
check
from
you
and
says
these
are
my
requirements
right
and
I
need
these
from
these
agencies
right,
so
the
the
the!
C
So
what
you
do
is
you
you.
You
actually
send
a
request
to
each
agency
and
they
need
to
add
and
then
tell
them,
hey
once
you're
done.
Add
it
to
the
other.
One
add
it
to
the
other.
One
add
it
to
the
other
one
right,
so
you're
they're,
basically
updating,
basically
updating
the
proof
every
single
time
and
then
the
final
proof.
It
proves
everything.
C
Right,
so
it's
it's,
so
you
can
do
you
can
do
one
to
n
where
you're
the
central
entity,
because
you
need
it
and
then
you
you,
you
just
present
whatever
three
four
five
proofs
together
or
you're,
you're
or
you're
you're
you're
doing
that
and
then
you're
handing
out
the
the
the
you're
doing
a
recursive
proof
for
each
one
proves.
It
proves
a
different,
different,
different,
different
aspect.
C
No,
they
don't
get,
they
don't
get
to
see
anything.
They
just
get
a
proof.
They're
just
get
they're
just
getting
a
proof
that
they
that
they
that
they,
that
all
of
the
organizations
that
you
requested
the
information
from
provided
that
information
and
that
it
fulfills
your
requirement
that
the
apartment
complex.
A
C
C
Is
that
right,
yeah,
so
that
that
would
be
there
will
be,
there
will
be.
There
will
be
one
solution.
Yes,
so
you're
doing
your
five
requirements
and
then
you
get
five
different
proofs
right
or
you
get
or
you.
You
have
five
different
requirements
and
in
the
end
you
get
one
proof
that
proves
everything
right.
D
B
B
Thank
you
and
yeah.
This
is
good
to
maybe
on
the
on
these
blips.
Let's
make
sure
we
make
that
indication
about
the
proposed
scope
being
just
an
example,
because
and
then
we
can
add
comments
like
from
this
call
on
ways
to
actually
do
the
work
to
propose
more
or
less
money
based
on
what
they
want
to
do.
C
They
just
have
to
send
the
proof,
because
their
signature
is
already
embedded
in
in
in
the
proof
itself,
so
that
that's
a
that's
a
that's,
also
an
interesting
way
to
to
to
avoid
having
to
expose
any
nunces
and
signatures,
and
things
like
that,
so
it
to
the
to
the
to
the
outside
world
which
make
you
know
keys,
you
know
or
may
make
signatures
attackable
anyway.
Okay,.