►
Description
The Baseline Protocol team takes you through the code of the v0.1 update.
Previous video: https://youtu.be/ZgaAcQvoD_8
Next video: https://youtu.be/l3BDBNMnR_Q
Go to https://baseline-protocol.org for more information.
B
B
Group
method
essentially
will
be
responsible
for
persisting
anything
on
a
local
level
like
in,
like
a
local
postgres
database,
for
example,
and
then
doing
operations
just
for
in
terms
of
the
a
local,
a
local
copy
of
the
data
and
also
being
is
also
responsible
for
for
deploying
the
org
registry
contract
for
the
work
group
and
reg.
And
then
you
know,
that's
sort
of
the
that's
sort
of
the
life
cycle
for
create
work.
Group.
B
B
For
each
new
work
group,
this
will
deploy
the
org
registry
contract
so
like
what
this
does
is,
if
bob
or,
if
alice,
is
the
initiator
of
this
work.
Group
alice
calls
this
method
on
her
side
and
it
does
the
stuff
that
you
know
it
deploys
the
work
group
right
of
the
the
org
registry
contract,
but
that
contract
is
not
does
not
make
alice
the
all
like.
It's
just
basically
out
there
right,
yeah.
A
A
B
And
that's-
and
that
makes
this
that
makes
this
exact.
You
know
interface
and
and
functionality
flexible
to
work
not
only
on
the
public
ethereum
blockchain,
but
on
a
private.
You
know
test
net
or
the
robson
test
net
with
your
own
little
work
group
or
you
know
really
any
any
any
test
or
production.
Word
registry
contract.
B
B
So
the
create
workgroup
method
doesn't
actually
doesn't
add
to
companies.
You
still
have
to
actually
register
you
have
to
register
yeah
so
after
alice
deploys
the
the
work
group.
So
so
what
does
that
there's?
Also?
Not
only
does
this
update
the
blockchain,
but
good
implementations
are
going
to
have
a
local
copy
of
the
work
group
and
like
stuff,
you
know
locally
as
well,
probably,
and
so
that
that's
also
respon.
B
B
I
mean
I
guess
it
could
be
like
internally
at
a
big
company.
Like
I
don't
know
microsoft,
you
could
maybe
invite
some
other.
You
know
business
unit
by
active
directory
potentially,
but
I
could
see
that
just
becoming
an
email
address.
You
know
really
at
the
end
of
the
day,
and
so
you
know,
I
think,
the
user.
You
know
you're
basically
say
giving
someone
permission
to
represent
the
organization.
B
You
know
in
that
org
registry
contract
because
you're,
you
know
you're
giving
the
work
group
you're,
providing
that
work
group
id
that
was
basically
returned
from
create
work
group,
so
they're
gonna
have
to
then
get
an
email.
You
know
you're
gonna,
you're
you're
likely
going
to
know
them.
You
know
if
you
send
an
email
to
someone,
that's
telling
them
to
sign
up
for
an
organization
that
they're
not
a
part
of
it's
not
going.
A
To
make
much
sense
and
that's
kyle,
that's
yeah,
so
the
current
state
of
things
we're
setting
up
these
little
work
groups
again.
You
know
in
the
future.
We
if
we
have
a
global,
so
identity
issues
are
abstract
from
this
from
this
right.
You
know
here,
you're,
stepping
around
the
identity
issues,
saying
hey
we're
just
carrying
a
little
work
group
between
us
kind
of.
B
A
B
You
go
into
that
yeah.
So
when
you,
when
you
create
a
work
group
organization
or
end
update
a
work
group
organization,
that's
where
the
messaging
endpoint
is
actually
set,
so
each
organ
each
worker,
each
each
organization,
has
the
opportunity
to
to
provide
their
their
messaging
endpoint
to
to
the
to
the
registry
contract.
B
And
you
know
it's
it's
not.
It's
just
assumed
that,
like
you
know,
well-behaved
a
well-behaved
implementation
would
verify
the
reachability
of
the
endpoint,
but
it's
just
assumed
that
that
endpoint
will
be
maintained
and
kept
available
by
the
organization.
I
think
that's
a
cool
integration
point
for
something
like
ens
in
the
future.
A
What
is
assumed
here
is
that
there
is
a
baseline,
compliant
system
of
record
on
on
the
part
of
companies,
a
b
and
c
in
this
case
right,
and
that
part
of
that
baseline
compliance
is
being
able
to
have
an
emp.
You
know
that
you
have
a
messaging
protocol
implemented,
you
have
an
endpoint,
and
you
have
your
system
rigged
to
to
be
part
of
this
work
group
right.
B
B
A
B
C
B
Yeah,
I
think
it's
more
asynchronously
checked.
I
don't
think
it
actually
emits
any
events
right
now
that
we
care
about,
but
I
think
you
yeah,
I
don't.
I
don't
think
it's
necessarily
needed.
I
think
you
would
just
you
would
look
it
up,
because
you
know
when
you
want
to
get
a
list
of
the
organizations
in
the
work
group.
You
know
you
can
just
do
that.
A
Okay,
that's
cool!
So
you
see
your
your
you're
look,
you're
you're
kind
of
thinking
ahead
to
when
there's
so.
The
original
design
had
a
work
group
or
an
org
registry
for
every
work
group
and
what
you're
saying
is
yeah.
We
still
have
that,
but
we
can
also
start
to
contemplate
the
idea
of
a
global
phone
book
yeah,
where
you
can
still
keep
sort
of
the
convenient
subset,
yeah
yeah.
B
Right,
yeah
right
now,
it's
it's
a
super
like
it's.
Your
your
your
org
registry
is
just
the
the
set
of
your.
Is
your
work
group
in
the
under
this.
You
know
this
pattern,
but
like
the
when,
when
the
org
registry
is,
the
org
registry
can
be
flexibly
a
superset
of
your
work
group
depending
on
the
implementation.