►
From YouTube: The Baseline Protocol: April 2023 General Assembly
Description
The Baseline Protocol April 2023 General Assembly will take place on Wednesday, 4/19, 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, join the live audience, and share your own updates.
A
C
Well,
yeah
so
we'll
go
through
our
usual
monthly
General
Assembly
updates,
where
all
of
our
different
teams
will
give
updates
on
the
work
going
on
and
what's
to
come,
we'll
get
updates
from
Outreach
research,
core
devs,
the
TSC,
we'll
talk
about
the
roadmap
items,
the
interop
events
and
use
case,
and
then
we'll
have
an
open
floor
and
see
if
there
are
any
other
updates
or
conversation
points
from
anyone
in
the
call.
So
to
kick
us
off
Mark
haddle.
Can
you
tell
us
what's
going
on
in
the
Outreach
team.
D
D
The
biggest
thing
that
we,
the
blog
really
worked
on
was
you
know
all
the
different
approaches
to
multi-party
data
sharing,
because
there's
so
many
manual
processes
and
ad
hoc
solutions
that
are
really
kind
of
cobbled
together
in
various
different
ways.
There's
not
really
a
unified
solution
that
can
deal
with
the
problems
when
it
comes
to
pardon
me
for
a
second
I
get
my
cat
down.
D
But
you
still
have
a
lot
of
the
limitations
that
you
know
what
happens
if
you
have
people
that
don't
have
the
constant
updating
of
the
data
sets
and
it
isn't
put
through
the
EDI.
That's
why
yeah
blockchain
really
emerged
and
the
two
flavors
of
blockchain
that
I
talk
about
in
the
article
public
blockchains,
as
well
as
private
permission
blockchains.
D
We,
you
know,
talk
about
the
advantages
and,
of
course,
the
trade-offs
and
the
limitations
when
it
comes
to
each
one
of
those.
There
isn't
really
one
that
is
emerging
out
front
right
now,
just
depending
on
a
use
case,
there's
many
different
approaches
and
still
just
really
trying
to
figure
out
how
the
technology
is
going
to
really
kind
of
mature.
D
So
we
also
looked
at
there's
a
couple,
other
solutions
that
are
working
out
that
are
managed
Services,
where
you
are
cloning
and
moving
your
data
to
a
common
repository
that
has
encryption
and
the
permissioned
aspect
of
it
entirely.
Cloud-Based
and
generally,
this
involves,
you
know
forcing
your
data
into
a
shared
architecture,
you're,
giving
up
custody
and
control,
and
you
know
I've
got
governance
questions
when
it
comes
to
these
new
approaches
that
are
coming
out.
As
far
as
who
owns
the
network,
what
happens
with
dispute
resolution?
D
And
you
know
looking
at
all
of
those
shortcomings,
we
talked
about
how
Baseline
really
does
not
suffer
from
the
same
design
problems
that
a
lot
of
these
other
Solutions
have,
where
you're,
not
cloning
and
moving
data,
giving
up
custody
and
control
it
stays
in
your
data
stays
in
each
system
of
record.
It's
a
lot
easier
to
secure
that
at
rest
than
data
in
motion,
and
this
is
what
we
wanted
to
have.
D
D
You're
coordinating
this
internally,
but
also
across
your
corporate
borders.
So
that's
what
we
really
showcase
within
the
within
this
month's
blog
post.
So
coming
up
next,
we've
got
another
one.
I
believe
yov
has
this
one
and
it's
all
about
how
you
know
being
a
core
Dev
within
the
Baseline
protocol
and
it's
really
exciting
a
lot
of
this
stuff.
I
didn't
know
a
lot
of
the
stuff,
but
you
guys
actually
did
sometimes
and
and
I
pay
attention.
C
Well,
yeah,
thanks
for
that
and
looking
forward
to
that
blog
I
think
we'll
plan
to
publish
that
today
or
tomorrow,
and
that
was
a
great
next
topic.
You'll
love
just
because,
like
Mark
said,
you
have
to
be
in
the
community
to
know
how
things
work,
just
because
there's
a
lot
of
moving
Parts,
but
it
isn't
too
hard.
So
if
we
just
have
resources
that
exist
that
make
it
a
little
easier
for
onboarding
that'll
help
us
continuously
grow.
C
C
We
don't
have
a
baseline,
focused
event
or
none
of
our
major
involved
organizations
are
doing
anything
because
we
we
did
some
stuff
at
eth,
Austin,
sorry,
East,
Denver,
but
I
think
we
will
be
on
ground.
Our
mesh
R
D
team
will
be
there,
I
think
some
other
community
members
from
UI
and
the
others
will
be
around
as
well
as
the
eea.
C
So
we
will
meet
in
person,
try
to
get
some
stuff
done
where
we
can
and
then
our
mesh
R
D
team
is
going
to
be
presenting
at
the
hyper
Ledger
booth
on
next
Wednesday.
We
have
the
last
slot
where
we'll
be
talking
about
the
ZK
VM
and
also
there
will
definitely
be
mentions
of
Baseline,
so
that
will
be
a
little
unique
opportunity
for
us
to
share
with
those
in
the
Linux
Foundation
ecosystem,
as
well
as
those
interested
in
learning
about
Baseline,
so
also
from
the
Outreach
team.
C
We
do
have
our
Outreach
rfps
that
are
at
the
final
stage.
We
just
need
to
wrap
them
up
and
get
them
posted
I.
Think
that's
on
the
the
list
for
the
next
day
or
two
so
Mark
is
our
Outreach
chair
mapped
out
the
roadmap
items
on
that
are
relevant
to
outreach,
so
what
the
large
events
for
the
year
will
look
like
and
what
types
of
resources
are
needed
to
support
that
so
we'll
share
more
on
that
next
time,
all
right!
So
Mark.
B
All
right,
yes,
thank
you,
so
core
Dev
updates
are
mainly
going
to
Encompass
the
SRI
Bri
3
work
group
and
kind
of
where
that's
progressed
since
the
last
time
we've
given
an
update
So.
Currently,
the
SRI
is
on
Milestone
four.
The
team
has
kind
of
gone
through
and
discussed
all
of
the
necessary
components
that
Milestone
4
would
Encompass
and
have
opened
relevant
issues
in
the
GitHub
repo
that
kind
of
cover
those
different
components.
B
So
there
are
several
open
issues
like
I
just
mentioned
that
are
kind
of
relevant
to
the
milestone
for
things
like
Merkel
proof
in
the
ZK
circuit,
a
state
object,
cruds,
happy
case
end-to-end
testing,
mocking
Prisma
Merkle
tree
crud.
Things
like
this
things
that
kind
of
involve
the
the
overall,
the
overall
objective
of
Milestone.
Four.
B
B
B
It
has
been
decided
on
to
be
something
incredibly
simple
and
straightforward
kind
of
without
any,
without
going
into
too
much
complexity,
which
is
kind
of
the
overall
design
architecture
of
the
SRI,
to
kind
of
be
as
simple
and
easy
to
understand
as
possible
to
to
become
sort
of
the
starting
point.
The
base
layer
of
an
implementation
to
be
able
to
just
take
this
and
then
add,
on
top
of
it,
you
know
a
new
custom
implementation,
something
more
novel.
B
B
B
B
A
The
implemented
use
case
will
actually
be
within
the
BPI,
but
more
of
a
way
for
the
team
to
align
on
the
the
concepts
and
the
largely
the
the
path
that
would
be
traveled
in
whatever
use
case
is
finally
decided
decided
in
synchronizing
their
states
and
so
on
and
so
forth.
So
it's
good
to
keep
that
in
mind.
If
you
look
at
that
document,
it's
aimed
at
bringing
an
understanding
to
you
know
the
underlying
functionality.
That's
going
to
be
implemented,
Mouse
to
point
not
necessarily
the
use
case.
Exactly
that's
it.
G
Absolutely
so,
we
are
aware
in
an
interesting
situation,
because
the
the
a
communities
projects
requirements
for
a
standard
listed
that
a
must
requirement
about
including
testability
statements
without
defining
testability
note.
W3C
has
spent
the
better
part
of
part
of
three
decades
trying
to
Define
testability
that
everybody
can
accept.
Needless
to
say
that
their
efforts
to
Define
this
in
a
unanimous
manner
have
been
utterly
unsuccessful.
B
G
G
We
are
currently
at
the
stage
of
finalizing
a
general
structure.
How
we
should
write
these
I
think
this
in
the
end
will
be
also
really
helpful
for
or
implementers
because
they
can
basically
just
put
some
meat
on
the
logical
test
Bones
by
adding
their
then
very
specific
tests.
Again,
those
are
non-normative
statements,
so
it
it
really
doesn't
doesn't
require.
The
test
has
to
be
exactly
like
this
right.
G
This
is
just
a
guide,
though
I
think
we're
we're
close
to
that
and
I
think
there's
there
are
there
are
we
will
be
able
to.
You
know
now
that
we
have
this
Clarity
be
able
to
not
in
short
order,
but
in
a
reasonable
order.
Aka
time
frame
I'll
be
able
to
to
complete
the
complete
this.
This
task
we'll
have
to
rewrite
some
of
the
some
of
the
the
testability
statements
that
we
already
have,
but
it's
not
going
to
be.
Thank
you,
Chad
GPT.
G
G
G
G
G
Yes
right,
TSC
updates
well
so
Mark
already
talked
about
the
blog
that
was
published,
so
we
have.
If,
if
you
don't
know,
every
TSD
member
have
the
responsibility
of
producing
a
Blog
during
their
tenure
of
the
one
year
10
years,
so
that
the
work
we're
we're
filling
up
those
those
slots
with
different
points
of
view,
which
is
because
we
have
a
decent
variety
on
the
of
backgrounds
on
the
TSC
we
are
actually
getting
in.
G
You
know
very
interesting
views
on
like
Baseline
and
how
it's
useful
for
different
types
of
roles,
entities,
people
I,
think
that's
Autumn,
Mark
great
job
we're
job
is
is
is
up
next,
talking
about
being
a
court
F
or
becoming
a
a
chord
F,
which
I
think
is
is
is
is
great.
So
all
very
much
thank
thanks
to
Mark
appreciation
and
you
know
high
five,
two
two
Joe
off
to
taking
on
this
this
work.
G
We
obviously
need
then
also
grant
funding.
So
if
any
of
you
are
eager
and
Keen
to
either
contribute
in
kind
with
your
with
your
time
and
brain
cells
or
any
software,
you
want
to
showcase
or
if
you
open
up
your
purse
strings
and
are
willing
to
to
support
any
particular
RFP
with
a
grant.
Please
do
so
all
the
instructions
are
actually
in
the
or
in
the
RFP,
and
we
can
help
you.
G
Speaking
of
the
interop
we
are
have
started
and
launched,
and
interoperability
working
group
which
meets
Friday
at
7,
AM
Pacific
10
a.m,
Eastern
4,
P.M,
Central,
European,
Time,
so
the
the
goal
there
is,
we,
you
know
everybody
interested
in
the
interoperability
subjects
and
potentially
wanting
to
to
to
reply
to
the
RFP
we're
working
together
to
Define
the
the
actual
use
case.
That
is,
and
then
also
then
write
down
hey.
G
There
are
a
whole
bunch
of
these
annoying
interoperability
requirements
in
the
Baseline
standard,
like
how
the
heck
are
we
gonna
gonna
Implement,
those
which
is
actually
a
great
test
to
figure
out
whether
they
are
actually
really
implementable,
whether
they
are
they
make
sense
or
not,
and
so,
with
great
discussions
going
on
there,
we
have
an
open
Slack
group
on
the
Baseline
slack
called
the
interop
working
group.
So
please
join
if
you're.
C
E
E
Taking
is
two
sleepless
nights
in
Portugal
and
we
got
them
built
with
plancky
two,
which
was
super
exciting
to
get
done,
but
we
realized
when
we
were
there,
that
not
a
lot
of
people
were
using
plancky,
2
right
now
and
there's
a
lot
of
Halo
2,
which
we
kind
of
dove
into
before,
but
there's
a
lot
to
digest
there.
So
we're
taking
a
look
at
that
again,
more
so
at
accumulation
and
the
kcg
implementation,
which
we
didn't
really
dive
into.
E
So
I
think
we
mentioned
before
on
a
call
the
way
Noir
works
is
they
have
an
abstract
representation
called
Acer,
so
you
can
take
different
proving
systems
and
plug
them
into
the
back
end.
I
think
most
people
here
are
familiar
with
dinaric
or
narc.
However,
you
pronounce
it
so
it
sounds
like
that
might
be
a
go,
but
we're
still
talking
to
them
right
now,
but
yeah
I
know
that's
kind
of
a
short
summary
of
what's
been
going
on.
C
H
There's
a
there's
this
exciting
time:
oh
I,
I
gotta,
grow
up
a
little
bit
here
got
a
little
short
there.
My
my
camera
keeps
getting
knocked
around
by
this
chord
over
here,
but
you
know
tons
of
exciting
things
going
on
around
provide.
You
know
folks
may
be
familiar
with
Eco,
that's
been
catching
on
really.
Well,
you
know.
Sustainability
is
a
really
great
way
to
engage
with
companies
about.
H
You
know
their
business
transformation,
because
what
I
always
encourage
folks
to
think
about
relative
to
Baseline
relative
to
to
blockchain
in
general,
is
you
know
think
about
these
Enterprise
customers?
Think
about
you
know
what
their
business
transformation
goals
are
because
they
are
getting
buyer
hosts
with
not
only
blockchain
or
Baseline
things,
but
AI
things
and
just
running
their
Core
Business.
H
So
when
you
think
about
how
to
communicate,
you
know
what
their
priorities
are.
Sustainability
is
actually
top
so
lots
of
exciting
things
you
know
still
to
announce
or
or
share
in
the
future,
but
we're
active
with
the
interop
discussion
here
as
well.
You
know
the
bank
Master
data
synchronization,
that's
something
that
we've
prototypes.
You
know
with
with
shuttle
successfully
and
submitted
to
hackathons
and
other
events
and
circumstances,
so
we're
excited
to
to
see
that
Advance
through
interop,
and
you
have
more
discussions
as
well
about
you
know.
H
How
does
that
fit
in
into
more
on-chain
Finance
right?
Because
you
know
once
you
have
like
these
cryptographic
assurances
around
correct
payment
address,
to
send
to
a
customer
or
or
or
vendor
right
now,
now,
you've
really
taken
a
step
towards
like
like
true
on-chain
settlements,
which
I
think
should
interest
everyone
here
on
this
call
in
this,
this
space
is
like
Hey.
H
How
do
we
move
from
an
EDI
Centric
payment
rails
to
a
more
digital
one
right,
and
you
know,
speaking
of
EDI,
that's
you
know
we're
we're
harping
on
this
message
of
like
ZK
EDI
right,
where
it's
not
necessarily
a
rip
and
replace
of
of
EDI
or
idocs,
but
rather
like
how
do
you
get
that
Assurance
outside
the
black
box
right?
So
once
you
send
the
CDI
document-
and
you
know
doing
more
than
just
confirmations,
but
getting
those
assurances
up?
H
You
know
really
tremendous
potential
there
overall,
so
more
news
to
come,
we're
going
to
do
another
provide
webinar
here
in
May,
we'll
also
be
doing
an
event.
You
know
in
partnership
with
xenerjex,
which
is
a
partner
of
ours,
that's
based
in
the
Australian
New
Zealand
region,
so
they're
very
excited
about
Baseline
as
well,
and
you
know
getting
getting
that
into
the
hands
of
more
sap
users
across
the
ANZ
region.
So
that's
that's
all
from
me
and
thanks
yeah
thanks
for
like.
Let
me
have
an
update
here.
A
C
D
G
Oh
they've
been
doing
that
for
years
already
and
that's
that's
wildly
wildly
widely
used.
I
mean
I
mean
Watson
was
the
first
one,
and
then
they,
you
know,
turned
out
that
that
that
did
not
work
so
well,
but
for
certain
things
it
is
significantly
more
advanced.
In
fact,
there
was
there
was
a
there.
Are
a
couple
of
research
papers
out
that
large
language
models
actually
can
detect
certain
types
of
cancer
significantly
earlier,
based
on
based
on
blood
tests
than
than
doctors.
G
Can
it's
just
simply
because
they,
because
because
of
you
know
you
you
just
can't
compare
a
much
larger
data
set
much
more
quickly,
so
it's
it's!
It's
not
like
super
magic.
It's
just
that.
You
know
it's
like
human
being.
Just
has
a
limited
amount
of
data
that
it
can
a
process
and
be
retained
at
any
point
in
time.
That
includes
patterns.
So
it's
it's.
It's
not!
It's
not
surprising.
However,
every
every
diagnosis
budget
by
these
type
of
large
language
models,
not
change
apt
in
particular,
any
large
language
models
needs
to
be.
G
G
To
very
quickly
simply
because,
because
this
type
of
like
pattern,
recognition,
these
models
are
much
more
suitable
for
than
human
beings,
at
least
basic
based
on
based
on
you
know,
if
you
need
a
lot
of
data
in
order
to
be
able
to
to
to
make
accurate
predictions,
especially
when
it
comes
it's
a
great
tool
for
for
especially
younger
healthcare
providers
that
haven't
had
Decades
of
experience
and
have
seen
basically
build
up
that
that
pattern
matching
most
pattern.
Matching
capabilities.
Well,.
D
And
I
think
they
miss
a
lot
of
the
tiny
details
and
stuff,
because
there
are
so
many
different
sources
of
data
that
they're
relied
upon
within
the
clinical
setting.
I
mean
you
know,
forget
the
research
for
a
second,
but
you
know
and
just
to
submit
a
claim.
You
know
just
whoever
is
within
the
revenue
cycle
of
the
provider's
office
staff.
D
G
D
G
G
Claims
that
are
that
are
that
are
that
are
that
are
reviewed
by
Machine
learning.
Every
single
claim
is
reviewed
by
a
machine
learning,
algorithms
and
I.
Think
over
80
are
fully
automatically
adjudicated,
including
a
lot
of
very
questionable
ones
that
are
then.
You
know
that
are
that
they're
basically
saying.
E
G
A
G
G
Which
is
which
is
which
is
much
more
effective
way
of
deterrence
for
employing
these
type
of
schemes
anyway,
just
saying
that
that
AI
models
are
also
utilized
in
in
fraud
detection
for
taxes,
you
can
you
can.
You
can
easily
tell,
for
example,
based
on
the
structure
of
numbers,
not
like
literally,
you
can
tell
whether
books
are
cooked,
based
on
based
on
what
the
what
what
the
number,
what
the
individual
numbers
are.
G
No,
you
you
can
you
you,
don't
even
need
that
that
much
sophistication
you
you
can.
You
can
just
tell
if,
if,
if
numbers
are
too
round
and
they're
this
and
that
there
there
are
there's
there
there's
a
book
that
has
been
written
about
that.
So
it's
like
it's
like
that
is
relatively
easy
to
to
spot
and
and
based
on
you
know,
forensic
accounting
practices
anyway.
Irrespective
of
of
that
yeah,
the
the
the
problematic
thing
is
that
there
is
a
lack
of
regulatory
framework
for
applying
AI
models.
D
D
G
Yeah,
it's
machine
learning
is
typically
one
algorithm
large
language
models
employ
on
the
order
of
a
dozen
different
algorithms
right,
where
you
know
you,
you
machine
learning,
you
you'll
often
do
like
just
one
like
random
forest
or
something
like
that,
but
in
with
large
language
models,
you
in
fact
have
yeah
like
about
a
dozen
models
that
are
that
are
that
are
that
are
layered
on
top
of
each
other.
Well,.
G
D
Well,
and
the
big
thing
is:
is
you
the
output
that
you're
going
to
get
from
AIML
whether
either
one
is
only
as
good
as
the
input
that
you
have?
And
you
know
the
big
problem
that
I
see
exists
everywhere?
Is
you've
got
you
know?
You
know
data
science
teams
within
even
a
large
company
saying
we
don't
have
the
entire
data
set.
We
don't
have
all
the
pieces
of
the
puzzle.
G
Right
and
you
can't,
you
can't-
share
the
data
right,
so
that's
where,
where
ZK
ml
comes
in
again,
it
becomes
it's
a
it's
a
it's,
a
multi-party
coordination,
which
means
there
are
trust
under
Azure
knowledge
that
that
becomes
becomes
necessary.
So
now
we're
talking
ckml
dkvm.
Those
are
those
are
those
are
that
becomes
that's
an
active
area
of
of
research
and
development,
because
it
it
it
it
is.
H
A
H
And
like
the
whole
hook
of
the
show,
was
like
at
the
beginning
of
every
show,
all
they
got
was
just
like
a
name
right.
They
didn't
get
any
other
context
about
this
person.
It
was
just
like
okay,
you
gotta
figure
out.
What's
going
on
with
this
person
right,
like
didn't,
didn't
talk
about
everything
else
going
on
with
this
person,
but
the
but
the
machine.
This
AI
was
nudging
them
towards.
Okay,
you've
got
to
figure
out.
What's
going
on
with
this
person
at
a
given
time
and
I.
H
Think
that
show
was
like
weirdly
prophetic
because
it
like
it,
it
kind
of
tied
into
like,
like
all
these
crazy
things
that
could
be
like
kind
of
guard
rails
for
AI
or
or
like
things
AI
could
do
for
itself
like
towards
the
end
of
the
show,
is
like
moving
its
own
data
center,
like
that
was
crazy.
Stuff
fun
show
highly
recommended
by
everyone
on
on
Baseline.
A
H
G
I
G
That
you,
you
you're,
you're
you're,
you
will
be
interacting
with
ages,
so
the
the
the
the
the
the
key
information
is
right
as
you
are
starting
to
interact
with
different
AI
agents
right.
What
what
do
the
AI
agents
have
to
prove
about
themselves?
Right?
It's
like
it's
like
you
know.
We
we
can.
We,
you
know
it's
gonna,
be
because
they're
gonna
interact.
G
G
G
H
H
Like
it,
it
has
to
have
a
way
of
parsing
to
what's
just
garbage
data
or
like
training
model
data.
It's
that's
meant
to
throw
it
off
right
because
you
you
see
this
you
discuss
discussed
often
is
like.
If
you
give
chat
GPT
a
bunch
of
you
know
garbage.
You
know
fake
news,
it's
gonna
spew
that
right
back
to
you
right,
so
it's
it's
not
necessarily
that
AI
is
always
correct.
It's
only
as
good
as
the
the
training
data.
That's
there
right!
H
So
if,
if
you
can
have,
you
know,
verified
like
axiomatic
level
data
and
like
reporting
that
goes
with
the
information
that's
cryptic
cryptographically
signed
by
certain
parties,
then
then
you're
on
to
something
better
right.
You're,
it's
not
going
to
be
just
kind
of
a
garbage
and
garbage
out
type
of
scenario
with
what
information
they
give
you
yeah.
G
You
you,
you
need
a
you
need
a
provenance
of
your
data
supply
chain
right,
as
as
with
with
with
pretty
much
everything
and
what
that
comes
back
to
multi-party
multi-party
automation.
You
know
under
zero
truck
in
zero
trust
and
under
zero
knowledge
right.
So
again
you
can't
know,
but
you
need
to
prove-
and
there
is
no
trust
right.
Trust
needs
to
be
re-established
every
single
time
right
because
you
could
have
been
compromised
since
the
last
time
we
interacted
wait.
That
was
just
100
milliseconds
ago.
I,
don't
know
it's
like!
So
what
it's?
A
G
G
It
started
things
that
have
literally
legal
implications,
significant
legal
implication
because
the
you
know
the
standard
in
a
lot
of
court
systems
is
just
you
know
you
get
off
if
there's
Reasonable
Doubt
so
and
and
and
if
you
can,
through
fake
information,
big
proofs
generate
Reasonable
Doubt.
No
one
can
verify
anything
really.
Then
your
entire
legal
system
is
in
de
facto
imploding
because
because
there
there's
there's
no
way
that
you
can
establish
not.
G
H
Well,
I
think
a
a
really
cool
thing
that
I
I
read
this
week.
Actually
there
was
a
stablecoin
proposal
that
that
way
quickly
into
Congress
for
for
the
financial
services
and
interops,
actually
one
of
their
one
of
their
requirements,
actually
right
to
say,
like
hey,
we
know,
there's
going
to
be
all
of
these
different
networks
and
some
some
manner,
but
we
need
to
have
some
level
of
interoperability
to
have
assurances
across
each
one
if
you're
going
to
use
different
different
things
all
over
the
place
right,
so
you
know
I
think
about
interop.
H
We
we
think
about
interrupting
the
context
of
just
BPI
instances
right.
But
what
is
a
BPI
instance?
It
could
be
two
runtimes
of
like
API
API
Frameworks,
but
could
also
be
different
chains
right
it
could.
It
could
be
so
so
we
think
of
BPI
interrupt
between
like
bri
one,
be
it
like
bri
three,
but
reality
it's
not
only
just
that,
but
anywhere
there's.
You
know
zero
knowledge
applied
right
because
we
we
discussed
that
in
depth
of
like
hey.
H
You
know
a
zero
knowledge.
Proof
should
always
be
verifiable
in
any
context
where
you
have
the
the
same
work
group,
the
same
information.
The
same
could
like
credentials
involved
right,
so
I
I
may
have
butchered
some
of
that
on
the
standards
there,
but
the
I
think
the
idea
stays.
The
same
is
like
hey
look.
Interop
is
actually
an
important
thing
across
systems.
G
I
Right,
not
only
are
the
you
know,
the
validators
that
are
facilitating
that
Exchange
need
a
money
transmitter
license
right,
but
you
know
you
need
to
apply,
for
example,
the
travel
rule
right.
You
need
to
apply
all
factless
right,
it's
like
you,
you
just
can't
just
like,
and
this
must
be
done
in
in
zero
knowledge,
because
you
are
operating
on
public
networks,
even
if
they're
permission
they're
going
to
be
public
right.
I
You
know
on
each
Network
because
the
trust
assumption
again
vary
between
those
networks.
So
every
time
you
interact,
you
need
to
again
establish
truck.
So
again,
there
are
Trot
under
zero
knowledge
right
again
between
multiple
parties
right
because
you
need
to
because
we're
the
multiple
parties,
even
if
you
send
yourself
money,
there's
going
to
be
the
regulator
and.
H
Well,
I
mean,
on
the
other
side
too,
like
a
practical
business
operations,
level
I
like
and
my
sap
level
view
I.
Think
of
of
you
know
clearing
payments.
You
know
you
want
to
know
if
you're
the
actual
status
of
your
payment
or
ones
that
you're
receiving
you
know
typically
work
that
you
know
through
EDI.
You
work
that
through
Swift
there's
a
really
compelling
way
to
apply
Baseline.
You
know
in
the
context
of
you
know,
Swift
and
invoicing
and
payments.
You
know
B2B
wise.
H
H
Yeah
ccip
but
I
think
there's
a
missing
piece
of
the
puzzle
there
of
like
you
actually
have
to
do
some
other
assurances
with
payments
of
regarding
you
know
what
what
purchase
order
or
invoices
related
to
that
that's
not
captured
by
ccip
or
something
else
so
that
we
need
they.
They
call
me
call
me
Sergey,
I,
I
I,
have
ideas.
H
Yeah,
like
that's,
that's
the
deep
dark
secret
behind
B2B
payments
and
because
it's
it's
not
like
as
nice
as
striper
cash
app,
you
know
what
happens.
Is
you
know,
businesses,
you
know,
produce
a
file
on
a
daily
basis
of
of
all
the
vendors
they
pay
and
they
put
it
into
one
file
that
has
the
business
name.
H
Their
bank
account
numbers
what
amounts
they're
being
paid
and
there's
a
lot
of
of
Legacy
access
controls
on
that
right
to
make
sure
that
never
falls
in
the
right
hands,
but
it's
still
there
and
it's
it's
and
it's
subject
to
being
manipulated
because
like
when
we
sell
this
business
case
for
interrupt
working
group
around
bankmaster
data.
We're
talking
about
the
scenario
where
accounts
payable
departments
get
phone,
calls
or
emails.
Saying
hey!
You
should
change.
This
bank
account
number
from
one
to
three
XYZ
to
this
other
thing.
H
I
C
We
are,
but
thank
you
for
the
very
great
conversation.
This
was
a
good
General
Assembly.
We
will
see
everyone
next
month,
but
we
will
also
see
you
next
week
where
we
will
host
ZK
pass
that
focuses
on
two
topics
that
are
relevant
to
Baseline
of
ZK
and
identity,
so
do
a
little
reading
up
on
them
and
they'll
walk
us
through
what
they
do
and
we'll
identify
any
relevance
for
the
Baseline
protocol
next
week.
Thank
you
all.