►
From YouTube: The Baseline Protocol: March 2023 General Assembly
Description
Code review & explanation of BRI-3 Milestone 3 - [38:28]
We are excited to announce that our March 2023 General Assembly will be live-streamed on Wednesday, 3/15, at 12 PM EST, 6 PM CET and 10.30 PM IST!
This is an excellent opportunity for the larger Baseline community to stay updated on Baseline Protocol's progress across various working groups and engage with the core team.
We invite you to tune in and participate in the Q&A session at the end of the meeting. See you there!
A
B
Me
an
email
and
say
Hey
I
want
a
shirt.
How
do
I
get
a
shirt?
What
I
was
saying
is
I
appreciate
the
the
comments
and
the
requests
for
the
shirts
and,
like
I,
said
it's,
it's
definitely
an
asking
coming
off
of
East
Denver.
We
just
have
to
figure
out
we
as
the
eea.
You
know
what
do
we
do
and
how
are
we
doing
it
so
yeah?
We
definitely
want
to
do
that.
A
All
right:
well,
we
are
live.
Thank
you.
Everyone
for
joining
our
March
General
Assembly,
whether
you're
in
the
studio,
live
with
us
here
or
watching
from
YouTube
I
think
we
will
also
have
some
additional
members
hopping
on
shortly,
but
our
agenda
today
will
include
going
through
some
Outreach
updates
and
East.
Denver
recap
see
what
our
research
working
group
is
up
to
hear
more
about
the
completion
of
Milestone
3
for
Bri
3.
A
and
then
also
some
TSC
updates
and
then
we'll
have
an
open
discussion.
I
know:
there's
been
lots
of
crazy,
exciting,
maybe
not
exciting,
but
crazy
news
in
the
tech,
business
and
other
spaces.
So
we'll
see
if
we
can
have
some
open
discussions
there
and
with
that
Mark
hadle
I'll
hand
over
to
you
first,
if
you'd
want
to
tell
us
what's
going
on
in
the
Outreach
team,
we've.
E
Been
on
the
Outreach
team?
Well,
we've
been
hard
at
work
at
you
know,
setting
up
the
RFP
process
that
we're
going
to
have
for
a
road
show
series
and
then
also
interoperability
event.
A
lot
of
those
probably
might
be
combined
because
we
want
to
tell
everybody
about.
You
know
hey.
This
is
what
Baseline
is
and
let
us
show
you
about
what
it
can
do,
and
ideally
we
want
to
have
a
live
demo
environment
between
two
or
more
unrelated
parties.
E
That
basically
will
demonstrate
the
Baseline
pattern
in
action
we
had
that
going
on.
We
also
have
another
blog
coming
out,
be
ready
to
be
published
next
week.
I
think
the
21st
that
we
have.
This
is
one
that
I
did
in
it's
basically
kind
of
a
departure
from
the
tech,
heavy
type
content
that
we've
been
putting
out.
This
is
really
kind
of
plain
language.
Speaking
to
the
non-technical,
the
business
audience
to
say
this
is
what
you
know
Baseline
can
do.
E
This
is
what
how
it
compares
to
other
methods
of
integration
such
as
EDI,
Vans,
public
and
private
blockchains,
as
well
as
some
of
the
emerging
offerings
that
are
coming
out.
I
don't
know
if
anybody
is
there's
a
company
called
vindaya,
that's
really
kind
of
new
on
the
scene,
and
they
are.
This
was
incubated
by
a
couple
of
people
from
Amazon
and
it's
getting
a
lot
more
attention.
E
As
far
as
how
do
you
share
data
in
environments
to
where
the
data
that
you
have
is
sensitive-
and
you
know
really
has
a
lot
of
restriction
on
it,
how
can
you
still
maintain
your
collaboration?
So
hopefully
this
blog
will
really
kind
of
tear
out
tear
through
a
lot
of
the
fog.
That's
kind
of
persists
a
little
bit
when
it
comes
to
what
does
Baseline
mean
to
be
non-technical
to
the
business
world,
so
that
is
what
we
got.
A
So,
for
example,
we
have
some
Gartner
conferences
that
there
are
that
need
papers
to
be
written
for
them.
There's
lend
at
fintech
that
has
a
speaker
slot
open.
That's
in
New
York,
there's
crypto
2023,
which
is
like
a
oh
I,
can
share
all
these
links
in
the
chat,
but
they
call
this
a.
This
is
hosted
by
the
International
Association
for
cryptologic
research,
so
just
a
few
potential
opportunities
for
anyone
out
there
who
is
interested
in
writing
papers
or
speaking
on
these
topics.
A
All
right,
like
I,
said
I
will
share
those
links
in
chat
shortly
and
over
to
our
eth
Denver
recap,
I
suppose
so
a
few
of
us
were
there
in
person.
I
think
it'd
be
fun
to
talk
about
what
cool
Trends
we
witnessed
things
we
learned
about
whether
it's
a
different
project
or
advancement
in
Technologies,
the
overall
Vibe
I
love
to
open
the
floor.
To
that.
F
Well,
a
big
thing
that
I
noticed
was
account
abstraction.
There
are
a
lot
of
projects
that
are
actually
implementing
or
337.
There
are
some
wallet
companies.
Unfortunately,
I
can't
remember
the
specific
one
I
was
talking
to
offhand,
which
is
too
bad,
but
account
abstraction
is
a
big
thing.
A
lot
of
people
are
talking
about
it.
F
Zk
sync
launched
their
new
zkevm
to
mainnet,
maybe
not
a
new
ZK
AVM,
but
they
they
launched
their
ZK
evm
to
mainnet
and
they're
they're.
Doing
some
account
abstraction
as
well,
so
account
abstraction,
and
then
the
the
ZK
evm
Wars
are
really
I.
Think
the
two
big
things
from
East
Denver
that
I
noticed
one
thing
that's
pretty
entertaining
if
you,
if
you
ever
go
on
Twitter,
is
watching
polygon
and
scroll
debate
about
who
has
the
actual
ethereum
compliant
or
ethereum,
equivalent
zkevm,
so
yeah.
F
G
F
F
G
G
G
G
That
would
result
in
you,
stealing
100
million
dollars,
and
instead
of
like
this
really
weird
negotiation,
where
there's
like
and
there's
still
like
kind
of
not
a
lot
of
trust,
but
you
can
demonstrate
provably
to
a
protocol
that
you've
exploited
them
and
you
know
how
to
exploit
them.
You
can
start
kind
of
talks
for
a
completely
white
hat
thing
without
ever
like
it's,
not
a
ransom
by
any
means,
it's
like
a
an
actual
way
to
notify
them
of
vulnerability.
So
I.
F
Yeah,
that's
interesting,
I
think
I
think.
Maybe
you
and
I
were
talking
about
that,
or
definitely
some
other
people
as
well
about
how
the
incentives
for
for
white
hat
hacking
have
shifted.
Some
people
aren't
paying
out
the
bounties
and
an
actual
proof
of
exploit
is
a
really
nice
thing
moving
forward,
because
you
can
prove
that
you
can
exploit
their
stuff
and
then,
if
they
don't
want
to
pay
you,
you
can
put
a
cone
of
shame
on
them
and
take
their
funds
anyways
or
maybe
other
people
can
because
they
know
it's
possible.
B
F
B
B
Novez
is
a
recent
Joiner
of
the
eea,
open
Zeppelin,
quick,
node,
Quant
stamp
polygon,
web3
Labs
bit
wave
and
cartesi.
Those
are
a
few
I,
just
kind
of
have
listed.
So
you
know
when
we
go
to
these
events,
certainly
we're
out.
There
kind
of
you
know
listening
learning
what
what
are
people
looking
for,
at
least
from
a
non-tech
perspective,
I
heard
a
lot
of
the
the
marketing
needs
and
requests.
F
B
B
Okay,
so
here
was
probably
the
highlight
of
of
my
presentation,
so
Keith
can
talk
more
about
that
so
and
actually
it
was
my
first
event
to
go
to
so
you'll
like
he
was
so
it
was
a
loud
environment
and
I
do
have
to
tell
you
Keith
I
have
heard-
and
this
is
honest-
sincere
I've
heard
a
lot
of
feedback
not
only
from
this,
but
your
presentation
at
the
mesh
event
that
your
speaking
skills
and
are
definitely
attractive.
So
that
is
sincere
I'm,
not
picking
on
you
at
all
any
comments.
Keith.
C
Yeah
actually
I
was
gonna,
bring
this
up,
oh
that'd,
be
into
it
yeah.
You
beat
me
to
it:
yeah
everybody's,
like
what's
going
on
at
East,
Denver
and
I'm
like
well.
There
was
this
great.
You
know
gaming
speech
a
little
little
known
entity
called
APN,
but
I'm
glad
that
you
did
so.
It
makes
me
seem
yeah,
I,
guess,
I
already
revealed
my
intention
so
never
mind.
E
B
Was
a
nice
event
that
solo
had
mentioned
too
so
our
good
friend
shadman
Hussein
of
CGI
Federal
and
MPA
minority
programmers
Association
put
on
a
nice
event
where
Mark
spoke,
so
that
was
also
it's
the
top
of
my
highlight
Mark,
your
part,
but
this
was
a
good
time
informal,
but
just
really
cool,
and
actually
it
was
quite
intimate.
So
it
was
kind
of
you
know,
just
a
neat
atmosphere
where
you
had
your
hackers
there.
B
B
We
go
yeah
yeah,
so
did
a
great
job.
There.
I
won't
bore
you
with
anything
else,
popping
out
so
just
just
a
good
event,
Puja
Raj
on
if
we
know
her
from
ethereum
cat
herder,
so
it
was
first
time
got
to
meet
her
in
person.
So
that
was
great.
So
just
a
few
photos
just
to
kind
of
see
some
of
the
great
parties-
oh
hacking,
so
there's
Jessica,
so
Charles
and
Jessica
of
C4
spoke
at
a
hacking
event
across
town
Keith.
You
were
there
for
that.
B
C
A
C
Ahead
yeah,
so
I
ran
into
a
lot
of
booths,
just
like
maybe
like
Matisse
or
fundraising
that
we're
just
like
hey.
You
know
we
want,
we
have
grants
to
give
out,
or
you
know
we
want
to
help
fundraise
and
I
was
like
for
what
and
they're
like
really
for
anything
in
web3
space.
So
there
was
like
a
big
difference,
at
least
my
personal
experience
from
past
events
that
people
were
just
kind
of
looking
to
give
out
money
right.
On
top
of
that,
the
one
thing
I'll
mention
I
thought
was
really
cool.
C
A
Awesome
yeah
thanks
for
walking
us
through
those
pictures,
James
it's
cooler
to
see
it
than
to
explain
it,
and
it
is
really
cool
to
have
the
eea
as
a
group
that
kind
of
brings
people
together
with
similar
interests,
they're
pretty
professional
projects
in
the
space
and
all
looking
to
collaborate
with
each
other.
So
it's
always
a
really
nice
presence
to
have
at
these
conferences
and
also
our
mesh
R
D
team
had
an
event
our
first
mesh
r
d
event
where
our
Enterprise
ZK
team
represented
and
spoke
all
about
Baseline
to
different
attendees.
A
That
probably
haven't
even
heard
about
baseline
or
may
have
heard
of
it
and
don't
actually
know
where
the
project
is
at
at
this
point.
But
anyone
who
is
at
that
event,
how
were
those
conversations
like
Mark?
If
you
want
to
kick
us
off
I
know
you
were
Manning
that
area
I.
Guess
what
were
the
conversations
like
where
you
were
explaining
the
Baseline
protocol?
F
Yeah,
so
we
had
a
lot
of
good
I
had
a
lot
of
good
conversations,
at
least
as
far
as
I
know,
and
it
was
good
because
it's
it's
hard
for
a
lot
of
people
to
connect
the
dots
between
zero
trust,
multi-party
coordination
under
zero
knowledge.
It's
a
big
mouthful.
The
Baseline
protocol
standard
is
filled
with
requirements
that
can
be
put
together
to
achieve
it.
F
But
it's
it's
flexible,
there's
a
lot
of
different
ways
that
you
can
accomplish
it
and
really
what
people
need
is
like
a
good,
visualization
or
sort
of
story
that
they
can
visually
visualize
to
allow
them
to
see
what
it
actually
looks
like
so
I
had
a
lot
of
good
good
conversations
with
people
that
were
Enterprise
focused.
A
handful
of
people
were
specifically
Enterprise
focused
and
the
the
regulatory
pressures
of
sharing
data
compliantly
and
increasing
the
security
of
your
system.
It
isn't
necessarily
something
that
is
at
the
Forefront
of
Enterprises
Minds.
F
It
certainly
could
be,
but
it
isn't
always
at
the
very
top
of
the
list
right,
maybe
they're,
thinking
about
making
their
organizations
more
lean
or
they're
thinking
about
just
purely
producing
value
in
their
business
units
or
the
software
projects
that
they're
working
on
and
really
overhaul.
This
Baseline
protocol
kind
of
overhauls
the
way
that
a
lot
of
these
systems
interact
with
each
other.
F
So
yeah
I,
don't
know
who's
sharing
this,
but
this
is
sort
of
the
general
deck
that
we
came
up
with
for
the
event
that
explains
a
lot
of
the
different
technologies
that
our
team
is
researching
and
working
with
and
then
sort
of
weaves,
together
with
the
Baseline
protocol.
That
represents
this
new
mental
model
and
shift
in
how
these
systems
can
interact
with
each
other
in
a
secure
way
and
do
it
and
do
it
under
zero
knowledge.
F
So
it
was.
It
was
very
fruitful,
there's
a
lot
of
people
that
are
interested
in
the
in
the
concept
of
zero
trust
under
zero
knowledge,
I
connected
with
a
handful
of
people
that
are
connected
with
a
lot
of
other
Enterprise
players
that
could
that
could
be
interested
in
this
approach
and
overall
made
a
lot
of
great
connections.
People
who
are
familiar
with
ZK,
very
interested
in
the
underlying
cryptography
of
ZK
and
how
these
General
zero
trust
patterns
work.
F
And
Keith
Keith
was
at
the
event
too.
He
was
Manning
the
gaming
station
because
he
gave
that
gaming
talk,
but
usually
when
people
would
ask
questions
that
were
very,
very
deep
into
the
the
heavy
mathematics
of
zero
knowledge.
I
would
just
push
them
over
in
his
Direction.
So
Keith.
Maybe
you
have
some
some
insight
on
the
event
too,
from
the
Baseline
perspective,.
C
Yeah
there
was
a
lot
more
people
there
than
I
expected.
There
was,
and
oh
I
will
say
great
food
as
well
yeah
you
had.
This
is
just
an
aside,
but
on
the
one
like
buffet
table,
you
had
like
breakfast
lunch
and
dinner,
all
together,
which
I've
never
seen
before,
and
that
was
great,
but
yeah.
It
was
I,
wasn't
expecting
to
talk
straight
for
like
a
solid
I.
Don't
know
it
was
like
two
or
three
hours.
C
We
were
there,
but
I'd
have
people
come
over
and
they
were
interested
in
in
APN
and
we'd
be
talking
about
APN,
and
then
people
would
be
coming
over
from
the
Enterprise
EK
Baseline
side
and
then
ask
questions
about
that.
So
then,
as
I'm
answering
like
maybe
ZK
questions,
and
then
another
person
would
come
up,
you
know
wanting
to
hear
about
APN,
but
in
the
middle
of
conversation,
so
they
don't
interrupt
and
they
start
listening
and
they're
like
oh
abn's
got
CK
and
I
was
like
no.
C
No,
no
I
have
to
keep
like
clarifying
the
other
I'm
talking
like
discussing
like
two
different
subjects,
but
it
was
really
great.
Just
like
you
said,
Mark,
there's
a
ton
of
people
interested
and
and
you're
looking
just
to
connect.
You
know
whether
they
they
be
devs.
You
know
investors,
a
lot
of
investors
were
reaching
out
just
saying.
Like
hey,
you
know
we
have
funds,
we
want
to
throw
at
like
APN
or
other
things,
so
it
was
pretty
crazy.
C
It's
hard
to
tell
you
know
exactly
how
much
and
you
know
people
are
really
trying
to
like
actually
develop
or
actually
invest
or
whatever
it
is.
But
it's
just
great
to
to
see
that
interest
and
see
that
they're.
You
know
at
least
willing
to
have
those
follow-up.
You
know,
let's,
let's
talk
about
it.
Let's,
let's
cooperate
a
lot
of
companies
that
were
also
doing
something
similar
to
AP
and
I.
C
G
F
F
F
A
lot
of
people
saw
that
diagram
and
were
able
to
form
a
very
good
mental
connection
of
what
baselining
actually
actually
means
and
how
it
can
keep
systems
secure,
synchronized
and
especially
for
some
of
the
Enterprise
folks.
I
was
talking
to
that
really
sparked
their
imagination
and
started
making
them
think
about
what's
actually
possible.
With
with
this
zero
trust
and
zero
knowledge
approach,.
C
Yeah
apian
is
really
nice
because
you
can
kind
of
with
one
diagram
at
least
communicate.
The
underlying
kind
of
like
core
principles
and
ideas
versus
Baseline
is
a
little.
It
seem
seemingly
more
complex
right
and
there's
not
this.
This
I,
it
looks
like
a
good
diagram,
but
it
was
I
think
it's
a
little
harder
to
explain
with
a
single
diagram.
You
need
like
at
least
two
or
three
to
be
like
right.
C
Now,
you've
seen
it
from
there
and
now
we
need
to
look
at
it
from
a
different
aspect,
but
I
think
most
the
people
that
that
came
through
especially
questions
about
zika
or
even
apien,
but
especially
with
ZK.
They
were
either
just
beginning
their
journey
and
had
yet
to
kind
of
wrap
their
mind
around.
C
You
know
what
ZK
is
or
anything
about
it
really
or
you,
or
we
had
people
on
The,
Other
Extreme,
who
were
kind
of
you,
know
self-identified
and
taught
cryptographers,
who
are
very,
you
know,
aware
of
the
scene
of
ZK
and
and
had
in-depth
questions
that
were
usually
connecting
Baseline
Enterprise
ZK
with
other
mesh
teams.
You
know
wondering
about
different
elliptical,
curves
and
all
kinds
of
you
know.
Questions
like
that
right,
I
think
that
was
my
general
experience
was
either.
C
G
G
I
yeah
everyone
was
was
kind
of
like
focused
on
it
compared
to
all
the
other
ones,
even
but
yeah
beyond
that
there
there
was
a
lot
of
really
cool
stuff.
Going
on
and
again,
like
you
kind
of
mentioned
that,
like
interoperability
between
these
different
mesh
projects,
I
think
there
there
was
a
little
bit
of
conversation
around
that
that
I
found
super
interesting.
G
I.
Think
I've
talked
about
it
a
couple
of
times
before,
but
we're
kind
of
interested
in
CK
State
channels
for
Baseline.
So
it
was
really
cool
to
have
Baseline
at
one
table
and
then
15
feet
away.
Was
the
state
Channel
theme
and
that's
again
there
was
the
Appian
thing
as
well,
which
there's
a
ton
of
possibilities
for
so
it
was
just
really
cool
to
have
it
all
in
in
one
area
and
kind
see
how
it
all
kind
of
coagulates
into
something.
G
A
couple
times
yeah,
especially
so
we
we
spent
a
lot
of
time
with
Aztec
recently
Aztec
Noir
is
super
interesting
and
I
know
that
circum
is
kind
of
like
the
lingua
Franca
for
for
Baseline
that
and
maybe
dark
but
and
there's
actually
even
an
art
back
end
in
Noir
now,
but
yeah
kind
of
like
as
as
we
get
into
all
right.
Why
are
you
using
Noir
there's.
G
Avenues
you
can
go
so
it
kind
of
depends
on
like
who
you're
talking
to
whether
or
not
they're,
like
you
know,
interested
in,
like
I,
know
completely
privacy,
preserving
things
that
have
nothing
to
do
with
synchronizing,
Enterprise
databases
and
there's
that
entire
realm
of
web3,
that's
all
like
entirely
new
and
then
there's
also
kind
of
how
do
we
onboard
the
existing
Legacy,
what
to
type
infrastructure?
And
that's
generally,
where
Baseline
comes
into
the
conversation.
So
you
know
kind
of
when
when
people
are
wondering
how?
G
How
does
this
actually
like
fit
into
anything
like
real
and
again
I?
Don't
want
to
Discount
all
of
the
like
really
cool
Solutions
like
summer
fours
and
TLS
notary,
but
for
things
that,
like
normal
people,
are
gonna
tangibly
understand,
I
I
think
that
it
it
it's
not
like.
They
totally
understood
it,
but
there
was
definitely
something
compelling
about
not
like
having
to
put
everything
on
a
blockchain.
G
A
H
F
So
I
could
speak
to
question.
One
I
was
actually
at
the
polygon
event,
and
that
was
where
they
announced
their
on
chain.
Zk
querying
of
VCS,
so
I
haven't
seen
any
material
about
people
actually
integrating
with
it
or
incorporating
it
because
they
announced
it
there
and
I.
Don't
know
if
I
heard
anything
specific
about
Regulatory,
Compliance,
I,
checked
out
a
lot
of
booths
and
didn't
really
see
much
I,
don't
know
if
Keith
you
or
Jack
saw
anything
about
that
point.
C
C
Oh
this
is
you
know
these
are
the
the
regulations
and
you
must
comply,
but
that
that
generally
that's
where
they
were
heading
towards
right.
I
talked
about
earlier
paradise
and
there's
just
this.
This
kind
of,
like,
like
uproar
of
all
these,
you
know
security,
auditing
tools,
specifically
for
ZK.
That
I
think
is
like
a
natural
lead-in,
possibly
to
that
to
that
area
of
what
you're
talking
about,
but
not
quite
at
that
level
progression
yet
on
drives.
So
my
experience,
though
interesting.
G
It
it
seems
like
a
topic
that
not
a
lot
of
people
really
wanna
like
roach,
really
it
definitely
was
kind
of
muted
in,
in
my
experience,
I
would
say
this
wasn't
explicitly
at
Eve
Denver,
but
with
respect
to
Regulatory
Compliance,
the
most
interesting
thing
around
CK.
That
happened
would
be
the
Privacy
polls
release
that
did
happen
at
eastender
I
think
like
at
the
same
time.
G
Maybe
it
was
actually
presented
at
East
Denver.
So
that's
like
tornado
cash
with
proof
of
Innocence.
So
and
that's
it
took
me
a
while
to
kind
of
figure
out
what
the
difference
between
proof
of
innocence
and
proof
of
compliances,
but
it
seems
like
most
of
the
public
chatter
around.
It
is
not
necessarily
around
compliance
but
around
just
not
being
guilty
per
se.
H
H
H
You
need
to
prove
where,
where
your,
where
your,
where
your
funds
are
coming
from
right,
it's
like
and-
and
there
is
it's
it's
there's
like-
and
the
hammer
is
coming
down-
and
not
only
in
the
US-
it's
like
Europe,
just
enacted
in
October
new
digital
asset,
a
new
digital
at
the
regulatory
framework
right
the
sweats
are
coming
down.
I
think
the
only
one
that
is
not
like
tightening
up
is
is
funny
enough.
Hong
Kong,
you
know,
but
otherwise
Singapore
is
like
tightening
Korea.
H
G
Yeah
and
just
really
quickly,
I
think
the
the
difference
between
innocence
in
compliance,
like
you
said,
there's
kyc,
AML
and
then
the
provenance
of
the
funds
and
his
proof
of
Innocence
makes
no
attempt
to
kyca
AML.
It's
just
these
funds
are
not
like
you
use
exclusion
lists,
essentially
to
say
that
certain
addresses
can't
join
my
privacy
pool.
So
you
can
like
make
sure
that
you
don't
have
North
Korean
funds
pooled
with
your
funds,
but
so
it's
innocent
in
the
sense
that
you
didn't
like
and
it
also
it's
reactive.
G
H
Oh,
is
that
you're,
so
you're
you're,
proving
that
you're,
not
a
hacker.
The
funds
don't
come
from
a
hack
from
from
a
from
a
hacker
address
right,
it's
like
so
I
I.
You
know
it's
like
so
I
I
push
it
into
into
ZK
sync
and
then
or
not
CK,
sync
at
stack
and
then
in
and
out
and
I'm
done,
right
or
I,
I
or
I
Bridge
the
over
to
Monero
and
then
Bridge
it
back.
It's
like
oops
like
like
what
what
you
know.
It's
like
it's
like
that.
H
That's
a
that's
the
there's
like
that's
what
what
totally
gets
me!
It's
like!
It's
like!
No,
it's,
it's
and
and
and
no
one
is
going
to
going
to
say.
Oh,
it's
not
coming
from
an
address.
It's
like
yeah
prove
it.
Where
did
where?
Where
did?
Where
did
that
balance
come
from
where
the,
where
the
balance
before
that
come
from
right?
C
Well
and
I
know
we're
in
general
assembly,
but
yeah
Jack
I
mean
did
they
did
in
what
you
experience.
Did
they
address
this
at
all?
Were
they
just?
Was
it
just
like?
Oh
here's,
a
blacklist
whitelist
situation,
or
do
they
even
talk
about
plans
to
address
like
how
they
accomplishing
this
proof
of
Innocence,
with
these
obvious
faults
and
flaws,
or
what.
G
G
It's
being
done
to
do
like
the
bare
minimum
of
what
the
current
like
issues
with
tornado
cash
was
I
would
say,
like
it
seems
like
most
of
the
people
who
are
like
actively
working
on
like
full-blown
kyc
kind
of
seems
like
it's
happening
in
the
dark,
because
I
have
kind
of
like
looked
around
for
it.
A
little
bit.
I've
really
struggled
to
kind
of
see
those
conversations,
but
it's
obviously
happening.
G
A
Thanks
for
the
conversation,
I
think
what
we'll
do
for
the
final
segment
and
then
we'll
see
if
there's
time
for
an
open
floor
is
shift
into
the
Bri
3.
The
Baseline
reference
implementation,
number
three
Milestone
number
three
completion
and
walk
through
so
I'll
hand
over
to
that
work.
Group,
Keith,
I,
think
you're
leading
us
here.
F
C
C
If
you
kind
of
take
a
gander
through
the
description
here,
we
can
see
that
the
descript
it
describes
that
pr3
should
support
BPS
subjects.
Subject:
accounts
BPI
accounts,
of
course,
as
described
to
the
standard,
and
then
these
identities
can
perform
actions
like
joining
work
groups.
They
can
be
properly
authenticated
with
proof.
C
So
just
to
kind
of
go
over
a
couple
of
them
really
quick
I
guess
we
can
really
start
at
the
top
and
work
our
way
backwards.
We
have
a
you
know
the
the
addition
of
a
doc
describing
current
encryption.
This
is
for
messaging
encryption,
which,
if
we
have
time
we'll
get
to
a
little
bit
in
the
code
review
right
now.
The
messages
are
just
encrypted
at
rest
for
Milestone
three
and
that
will
be
expanded
upon
later.
C
We
also
have
another.
You
know
archive
work
group.
This
is
edition
of
archiving
The,
workgroup
functionally
added
to
the
current
work
group.
You
know
set
of
functionalities
message
encryption,
so
this
is
goes
along.
The
functionality,
along
with
the
dock
for
describing
how
encryption
is
accomplished,
Nats,
is
being
used
as
in
the
messaging
mechanism
within
the
BPI.
Currently,
here
we
have
auth
and
authorization
and
that's
often
authorization
which
takes
us
to
kind
of
the
large
part
of
authorization.
Author
was
implemented
by
Stefan.
C
We
have
a
castle,
Prisma
call
here
or
a
PR
here
as
well.
As
you
know,
implementation
of
you
know
obviously
ability
decorators,
so
we
can
kind
of
see
here.
You
know
when,
when
you
take
these
lists
of
peers
and
put
them
together,
you
can
tell
that
we're
breaking
down.
You
know
by
various
specific
functionality
right
trying
to
make
these
PRS
more
succinct,
concise,
easier
for
everybody
to
kind
of
review
and
not
have
to
spend
your
whole
life
trying
to
understand.
C
You
know
everything
that's
going
on
in
multiple
parts
of
the
code
because,
as
the
code
base
gets
bigger,
this
this
becomes
more
difficult.
So,
for
example,
if
we
dive
into
something
like
the
abilities
decorator,
we
have
a
very
small
amount
of
commits
files
changed
and-
and
we
can
see
you
know
pretty
easily
where
those
changes
were
made
in
the
nest.js,
adding
in
to
the
authorization
module.
You
know,
adding
in
the
actual
authorization
decorator
itself,
but
adding
into
the
authorization.
C
You
know
guard
how
this
is
kind
of
accomplished,
authorization
through
a
decorator
on
a
route
and
so
on
and
so
forth.
So
of
course,
you're
encouraged.
If
you
want
to
get
involved,
go
on
and
and
read
through
this,
especially
if
you
are
a
developer
engineer
code
oriented
it's
a
nice
intro
to
see
how
you
would
build
out,
for
example,
a
a
BPI
as
well
as
other.
You
know,
large
complex
systems
that
desire
authentication
authorization
messaging.
So
on.
A
C
C
C
C
Let
me
stop
share
and
reshare
them
appreciate
that
how
about
now?
What
do
you
see?
Yeah,
you're,
good
you're,
a
vs
code?
Okay,
so
we
have
under
our.
We
do
have
a
front
end
that
is
added
in
for
a
simple
authentication
purposes
right
that
as
long
as
you,
you
know,
if
you
were
to
spin
this
up
and
set
up
the
database
and
run
the
Prisma
seed
commands
for
the
database
and
the
migration
and
everything
that
are
all
in
the
readme.
C
You
know
where
we
have
the
identity
say:
identity,
for
example,
includes
BPI
accounts,
BPI,
subject,
accounts,
BPI
subjects,
we've
seen
things
like
that
and
work
group
as
well,
which
will
have
a
folder
for
workflows,
work
groups,
work
steps
primarily
at
the
end
of
Milestone
3.
We
worked
on
communication,
which
is
set
up
a
lot
like
the
other
modules
and
as
well
as
authorization
which
is
a
little
bit
different
than
the
other
modules,
but
closer
to
Authentication
communication.
C
C
We
have
the
injectable
BPI
messaging
agent,
which
of
course
has
access
to
the
storage
agent,
the
message
storage
agent,
as
well
as
the
subject,
storage,
agent
and,
of
course,
logging
in
this
case,
and
as
you
would
expect,
if
you
followed
some
of
the
previous
videos
in
the
message
agent,
we
have
all
these
kind
of
validation.
That's
that's
being
done.
If
you
look
at
some
of
the
function
names
here,
throw
it
BPI
message:
ID
exists,
so
these
you
can
imagine
as
if
you
are
going.
C
The
storage
agent
is
going
to
take
the
message
ID
and
we're
gonna
we're
going
to
try
to
retrieve
from
the
storage
that
ID
or
that
message
by
its
ID,
which
really
means
to
say
well.
If
I
can
retrieve
that
thing,
if
I
get
something
back,
then
that
message
ID
already
exists
right.
A
message
is
this
already
with
that
ID.
So
something
is
wrong
because
I'm
trying
to
create
another
message
with
the
same
ID
right.
So
we
have
a
lot
of
validation
on
this
level
and
you
can
see
okay.
C
Well,
if
that
message,
ID
does
exist,
meaning
something
is
wrong.
Right
run
order
exists,
I'm,
trying
to
create
a
new
one
with
the
same
ID.
We
need
to
throw
some
kind
of
you
know
exception
here
right
so
to
throw
an
exception
to
say
like
oh,
we
need
to
tell
the
system
or
whoever's
running
system
that
this
is
bad.
Something
has.
F
C
And
those
kind
of
go
on
with
you
know
just
depending
on
our
needs
with
the
messaging
system:
storage
agent-
we've
already
seen
it
a
little
bit
of,
but
this
is
just
to
be
able
to
access
where
the
messages
are
being
stored.
So,
as
we
saw
in
the
message
agent
where
it
was
telling
the
storage
system
hey,
you
know,
pull
back
that
message
by
ID
to
check
if
it
exists.
This
is
the
logic
it's
using
to
pull
that
message
back.
C
This
is
kind
of
the
bridge
between
you
know
where
things
exist,
running
kind
of
in
an
ephemeral
manner
in
the
in
the
BPI
and
in
the
system
and
the
database.
Let's
say,
for
example,
we
were
using
postgres
right
now
in
a
first
version,
but
whatever
database
you're,
using
if
you're
making
your
own-
and
this
is
the
connection
using
Prisma-
just
an
object-
relational
mapper
right.
C
So
if
we
go
to
search
by
get
message
ID,
this
is
obvious.
We're
going
to
find
you
know.
Let's
await
this
message.
Fine
unique-
and
this
is
kind
of
handled
by
Prisma
itself-
translates
this
into
a
query
into
the
database,
saying
where,
where
ID
you
know,
the
ID
is
the
ID
that
we
pass
it
and
it
includes
we.
F
C
To
include
these
topics
from
whatever
query
is
returned
right.
We
of
course
have
this
effect.
This
is
just
the
kind
of
the
unit
test
for
the
agent
itself
to
make
sure
that
the
agents
functions
are
working
properly
and
then
so
this
this
differs
from
the
actual
messaging
agent
right.
These,
these
BPI
message
agents
are
kind
of
what
you're
used
to
seeing
in
the
other
modules
here
right.
This
is
how
you
know
we
deal
with
a
work
group.
C
C
C
So
the
the
way
that
is
set
up
now
and
anybody
can
feel
free
to
interrupt
in
case
I,
get
this
wrong
I
believe
we
agreed
that
everything
will
be
like
a
publication.
And
subscribe.
You
know
type
interface
within
the
BPI
that,
if
somebody's
publishing
a
message
that
anybody
with
a
particular
type
of
authorization
should
be
able
to
subscribe
and
receive
those
messages
and
I
think
I
think
that's
a
good
kind
of
First
Step
introduction
to
how
the
the
the
messaging
agent,
aside
from
the
BPI
messages,
work
right.
C
C
You
know,
message
that
are
being
published
and
and
then
receiving
those
messages
by
subscribing
to
that
kind
of
Topic
in
publication
right
and
then
we
have,
of
course,
the
mock
BPI
message:
storage
agent.
This
is
for
testing
purposes
whenever
we
run
from
these
larger
tests
that
require
reaching
out
to
the
database.
C
In
this
case,
when
the
test
is
run,
it
doesn't
require
of
the
database
and
everything
to
be
spun
up.
It
can
just
simply
focus
on
what
are
we
trying
to
test
and,
and
what
that
requires
is
that
we
set
up
kind
of
like
a
mock
storage,
that's
again
in
like
ephemeral
memory.
So
whenever
the
test
runs,
this
will
spin
up
and
say:
okay.
C
Well,
what
are
all
the
things
I
need
in
this,
like
ephemeral
database,
to
run
these
tests
for
now,
so
that
we
don't
have
to
spend
the
database
every
single
time
and
run
it
and
make
sure
all
the
data
is
in
there
currently
and
then
all
the
other
things
you
would
expect
inside
of
this
module,
the
the
dtos
for
the
request
and
response
for
creating
a
message.
You
know
this
is
the
information
you
need
to
create
a
message:
ID
from
to
content
signature
type,
to
update
a
message.
C
F
C
The
outside
and
you
need
to
interact
with
this
thing.
These
are
the
routes
that
I'm
going
to
send
a
request,
because
I
need
to
create
a
BPI
message.
Right,
I
need
to
just
retrieve
a
VPN
message,
this
controller
kind
of
tells
us
what
to
do
whenever,
let's
say
if
you
want
to
create
a
BPI
message,
it's
going
to
you
know,
do
a
couple
decorator
things
up
top
that
are
a
little
fancy,
but
in
essence,
it's
going
to
execute
a
command.
C
It's
going
to
await
and
execute
of
a
create
BPI
message
command,
and
if
we
go
into
that
command,
you
know
we
will
be
able
to
see.
You
know
how
is
that
done
right?
This
is
the
command
Handler,
so
the
command
itself
is
just
another
structure.
Well,
the
command
is
composed
again
of
ID
from
to
content
signature
type,
and
this
is
how
that
is
handled.
Whenever
we
decide
to
create
one
well,
first,
we're
going
to
fetch
the
BPI
subject,
make
sure
it
exists.
C
If
not,
you
know,
throw
some
kind
of
error
and
then
do
the
same
thing,
but
in
this
case
we're
going
to
do
for
the
two
subject.
You
know
we're
going
to
authorize.
You
know
we're
going
to
actually
create
the
message
that
now
that
these
three
things
are
true
and
they
have
passed
and
then
we'll
store
the
message
so
on
and
so
forth
and
feel
free
to
go
in
here
and
you
know,
look
through
it's
open
source.
C
Look
through
all
the
different
things
aside
from
create
I'm
not
going
to
go
through
each
one
delete
get
so
on
and
so
forth.
You
know
process
an
inbound
message,
as
some
of
these
are
more
related
to
how
Nats
deals
with
things
and
update
VPN
message
with
a
couple
minutes
left
I'll
show
a
little
bit
of
the
authorization
that
scos
or
Stefan
has
implemented.
C
So
you
know
in
attention,
in
addition
to
authentication
which
is
guarding
all
routes
and
say
you
need
to
have
that
particular
JWT
that
corresponds
to
like
a
public
key
inside
of
the
database.
We
have
authorization.
So
now
we
have
these
different
types
of
kind
of
groups
that
you
can
belong
to
that
say
are.
Are
you
authorized
to
do
something
or
not
right?
C
In
addition
to
it,
you've
been
authenticated,
you
are
able
to
act
in
the
system.
You
now
it's
beyond
that.
Are
you
authorized?
What
are
you
authorized
to
do
in
the
system?
Right?
Are
you
an
admin
of
a
work
group?
Are
you
part
of
a
workflow,
you
know.
Are
you
acting
in
a
work
step?
Are
you
the
the
owner
of
a
BPA?
Subject
account
so
all
this
granularity
to
say:
if
you
have
this
role,
then
you
are
allowed
to
do
this
particular
thing
within
this
particular
module.
C
You're
allowed
to
take
this
action
that,
before
all
the
routes
were
open
you
could
everybody
could
do
this
to
the
work
group
right,
that's
how
it
starts,
and
now
that
we
add
this,
only
certain
people
are
allowed
to
do
certain
things
in
the
system
which,
as
you
can
imagine,
is
extremely
necessary
right
and
and
that's
it.
That's
all
folks.
C
C
C
A
If
you
had
more,
you
wanted
to
show
us
then
join
us
on
the
show
next
week
and
take
us
through
whatever
else,
but
since
we
are
at
the
end
of
the
hour,
I'll
wrap
up
our
general
assembly
for
this
month
and
we'll
carry
on
with
our
Baseline
show
next
week,
but
that's
a
huge
milestone.
Thank
you
for
walking
us
through
that
and,
as
you
mentioned,
join
our
chats
to
ask
more
questions
or
learn
more
about
the
work.
Thank
you
everyone.