►
From YouTube: The Baseline Protocol: June 2023 General Assembly
Description
The Baseline Protocol June 2023 General Assembly will take place on Wednesday, 6/28, at 12 PM EST, 6 PM CET and 10.30 PM IST!
The Baseline Protocol community members will cover updates from the Core Devs, Outreach Team, Technical Steering Committee, and other work groups!
We invite you to tune in, join the live audience, and share your own updates.
B
Yeah
thanks
all
for
joining
these
weeks
fly
by
in
between
these
sessions.
Thanks
for
joining
us
live
or
tuning.
In
later,
we
will
go
through
our
usual
monthly
General
Assembly,
where
we
will
talk
through
Outreach
updates,
core
devs,
the
interop
work
group
standards,
the
TSC
and
roadmap
items,
and
then
we
will
also
have
an
open
floor.
B
I'll
get
us
started
on
one
Outreach
update
and
then
I'll
hand
over
to
Mark
cattle,
the
TSC
member
and
Outreach
chair,
but
one
of
our
last
blogs
that
came
out
published
by
the
TSC
member
Stefan
kostik
was
called
proving
secrets
that
proof,
without
exposing
them,
and
it's
a
nice,
concise,
read
about
privacy,
how
zero
knowledge
proofs
can
be
applied
to
current
privacy
problems,
how
the
attributes
of
completeness
soundness
and
zero
knowledge
fit
together.
B
C
Interesting
time
I'm
just
in
the
world
as
it
is
just
so
much
going
on,
and
particularly
within
the
technology
world
I'm,
seeing
a
lot
of
innovation
that
is
coming
to
the
Forefront.
It's
not
just
vaporware,
and
it's
not
just
ideas
and
dreams.
You're
actually
seeing
people
build
something
that
is
going
to
actually
have
an
impact,
and
a
lot
of
this
has
been
going
on.
C
In
the
background
for
the
past
couple
of
years,
kind
of,
like
senator
of
AI
chat,
GPT
and
everybody
is
now
saying
this
is
a
really
cool
thing.
But
how
can
we
keep
it?
Not
that
quickly
set
it
to
where
it
doesn't
get
us
in
trouble?
Because,
again,
how
do
you
Source
the
data
that
you
can
make
the
decisions
where's
it
all
coming
from,
and
is
it
yours
and
do
you
have
a?
C
Are
you
allowed
to
use
it
and
the
answer
to
all
those
questions
is:
maybe
I
don't
know,
and
so
that's
one
of
the
big
things
they
need
to
start
drilling
down
on
the
big
thing
that
I'm
starting
to
see
with
zero
knowledge
almost
addresses
that
to
where
you
can
prove
Secrets
without
exposing
them,
and
that
happens
in
a
lot
of
Highly
regulated
Industries,
to
where
I
need
to
have
certainty
that
my
counterparty
is
looking
at
the
same
data
set
that
I
am
but
I
cannot
show
or
even
take
custody
of
the
data
object
just
to
make
sure
that
it
is
correct
or
that
it
is
concurrent
with
my
counterparties
and
then
scale
that
out
across
if
you
had
a
thousand
people
to
sit
there
and
actually
look
and
take
a
possession
of
or
custody
of,
you
know
a
data
object
that
is
unique
to
are
specific
to
your
relationship,
and
you
don't
want
anybody
else
to
see
it.
C
Let
it
stay
in
its
existing
system
and
you
have
a
proof,
not
just
an
assurance
and
not
just
a
a
promise
that,
yes,
it
is
matches
a
proof.
So
you
again
certainty-
and
this
is
really
getting
a
lot
more
traction
there
and
I'm
starting
to
see
kind
of
the
people
start
to
look
at
yeah
I.
Don't
quite
understand
the
concept
A
little
bit.
How
can
you
prove
something
without
showing
it
to
me,
and
you
know,
you'll
have
a
lot
of
exercises,
the
the
most
simple
one
that
I've
actually
come
across.
C
That
has
a
lot
of
that
people
get
is
you
can
say
you
know
I've
got
my
phone
I
want
to
prove
to
you
that
I
know
my
phone
number
and
I
could
say
you
know
subtle.
I
know
your
phone
number
and
you're
like
no
prove
it,
and
so,
if
I
I'll
take
out
my
phone
I'll
call
you
and
if
your
phone
rings
identifies
me
as
the
sender,
I
have
proven
to
you
that
I
know
your
phone
number
without
exposing
it
and
that's
something
that
people
now
kind
of
understand.
C
I
mean
I
I
run
into
so
many
problems
where
you
start
to
use
the
example
of
the
two
red
balls
or
alibaba's
cave.
That
just
requires
a
lot
of
mental
gymnastics
that
a
lot
of
people
don't
really
want
to
have
to
under
undertake.
So
that's
really
what
we're
seeing
right
now,
especially
in
these
highly
regulated,
regulated
Industries,
where
you
don't
necessarily
have
to
share
data
objects
because
you're
not
allowed
to
because
of
privacy,
compliance
or
just
competitive
position.
So
this
is
a
way
that
you
can
actually
do
it.
C
So
a
lot
of
people
are
getting
a
lot
more,
paying
a
lot
more
attention
about
it
and
we
want
to
get
them
more
excited
about
it.
And
so
that's
why
we're
kicking
off
a
a
a
demo
environment
where
we
want
to
show
you
what
are
the
capabilities
of
Baseline
protocol
and
what
it
can
do
for
what
impact
it
can
make
within
your
business,
your
process,
environment,
multi-party
and
and
so
forth.
So
that's
really
where
we
are
right
now.
As
far
as
Outreach.
B
Awesome
so
I
know
the
Outreach
team
has
had
some
meetings
get
canceled
in
the
last
few
weeks
due
to
holidays
and
things
like
that.
But
aside
from
some
of
the
larger
picture
things
you
mentioned,
are
there
some
plans
or
I
mean
what
are
like
the
actionable
things
that
we
want
to
accomplish
in
the
Outreach
team
this
year?
Well,.
C
C
It's
a
baseline
reference
implementation,
three,
which
is
going
to
show
you
how
you
can
have
the
interoperability
between
two
or
more
parties
and
how
you
can
actually
maintain
that
product
and
demonstrate
how
that
process
environment
happens.
So
how
was
the
General
how's,
the
zero
knowledge
proof
generated?
How
is
it
shared
and
in
what
format?
And
how
can
you
then,
on
your
counterparty
side,
have
that
function
as
an
acceptance
of
the
I
guess,
data
concurrency,
so
I'm
proving
something
to
you.
You
have
to
accept
it
and
so
we're
looking
at.
C
How
can
we
go
ahead
and
show
how
that
mechanism
Works
within
an
environment?
Now
we
want
to
get
a
little
bit
more
and
get
a
little
bit
a
little
bit
more
fine-grained
as
far
as
where
does
this
fit
within
the
current
it
architecture
and.
C
There
is
where
it's
going
to
you
know
kind
of
sit
in
there
to
where
it
doesn't
disrupt
the
furniture
but
still
maintains
all
of
its
functionality.
A
Yeah
can
do
all
right,
so
I
guess
I
will
start
off
just
kind
of
showing
a
little
bit
about
bri3,
giving
some
updates,
as
well
as
just
some
general
kind
of
information
on
the
planning
of
it
and
how
it's
going
and
what
what
considerations
are
being
made
in
order
to
kind
of
achieve
this
goal
of
creating
this
a
simple
reference:
implementation
that
I'm
sure
everybody's
heard.
You
know
the
definition
of
a
hundred
times,
but
I
will
share
my
screen
and
we
can
kind
of
look
at
some
stuff
together.
A
So
here
sharing
this
is
the
SRI
use
case,
walkthrough
dock.
So
this
was
kind
of
I.
A
Think
I
talked
about
this
on
the
last
show
as
well,
but
the
core
purpose
of
this
document
is
to
kind
of
create
an
outline
of
what
the
architecture
would
look
like
for
a
use
case
to
sort
of
synchronize
all
of
the
devs
working
on
the
work
group,
so
that
we're
all
kind
of
on
the
same
page
of
what
what
the
implementation
will
be
sort
of
architecturally,
so
that,
when
a
full
use
case
is
decided,
everybody
will
be
able
to
kind
of
easily
begin
working
on
it
because
we'll
we'll
have
already
synced
on
what
that
would
look
like.
A
So
this
stock
has
been
shown
before
they're
still,
some
action
items
and
discussion
items
being
sort
of
reviewed
and
looked
at
just
to
kind
of
scroll
through.
You
can
see
that
there's
quite
a
healthy
amount
back
and
forth
between
the
work
group.
A
So
this
is
still
a
work
in
progress.
However,
it
does
seem
that
it's
sort
of
moving
along
nicely.
A
So
taking
a
look
out
of
this
we'll
check
out
some
PRS
that
have
been
closed
since
the
last
call
that
we
had
the
last
GA
I
should
say
so.
There
are
kind
of
four
I
believe
three
or
four
major
PRS
that
are
SRI
related
that
have
been
merged
into
mate,
so
fully
kind
of
discussed,
reviewed,
updated
and
committed
to
the
main
branch.
So
this
one
here
we
have
to
remove
the
remaining
storage
box
and
we
can
first
look
at
the
issue
that
this
sort
of
solves.
A
So
here's
the
issue
in
GitHub
and
that's
kind
of
the
format
that
we
run
is
there
are
issues
in
GitHub
that
are
then
picked
up
by
a
developer
or
group
of
Developers
worked
on,
and
then
a
PR
will
link
to
that
issue
so
that
anybody
now
or
in
the
future
can
sort
of
follow
along
as
to
why
that
code
was
implemented
and
what
sort
of
problem
or
feature
it's
introducing
or
solving.
A
So
this
one
is
intended
to
create
a
way
to
mock
the
database.
That
way,
all
of
the
different
storage
agents
for
each
individual
function
isn't
needed
to
be
written
sort
of
one
by
one
which
is
just
tedious
and
because,
like
you
said
here,
the
augment
said
here,
it's
a
boilerplate
code.
It's
sort
of
an
unnecessary
function,
if
possible,
to
sort
of
implement
a
way.
So
scos
has
his
PR
here,
which
implements
a
couple.
A
If
you
don't
want
to
kind
of
read
through
every
every
line
committed
here
line
by
line,
we
can
look
also
at
the
conversation
to
see
all
of
the
discussion
and
the
back
and
forth,
and
the
suggestions
that
are
being
made
by
the
by
the
core
Dev
team,
the
maintainers
in
order
to
kind
of
get
Synergy
and
to
be
all
aligned
with
what
everybody
wants,
the
kind
of
repo
to
to
look
like
in
a
way
that
is
structured
and
consistent.
A
Her
third
part
is
now
I
believe
currently
open
in
a
PR,
so
this
is
generating
the
circuit
proving
and
verification
keys
and
adds
a
placeholder
circuit,
and
this
PR
was
opened
I
believe
two
weeks
ago
or
so,
and
since
then
there
are
some
comments
being
left
as
well.
A
Just
like
all
the
other
PRS
that
we've
looked
at
being
reviewed
in
case
people
have
in
case
some
of
the
code
owners
have
any
updates
to
be
made
or
requested
changes,
she'll
go
ahead
and
discuss
those
and
then
Implement
what
what
is
agreed.
Otherwise
it
looks
like
there's
one
approval
here,
and
one
comment
by
Andreas
says
looks
good,
so
this
should
likely
be
merged
pretty
soon.
He
just
has
one
kind
of
pending
question.
It
seems,
and
then
that
will
be
the
part
three
of
the
component
of
the
ZK
component
implementation.
A
We
have
also
looks
like
this
is
an
issue
part
one
or
no.
We
looked
at
this.
A
This
is
I
think
this
is
the
last
PR
that
had
been
merged
in
this
since
the
last
GA,
that's
related
to
the
SRI,
so
this
is
two
month
the
work
group
storage
agent
I'm
using
the
jest
extension
it's
pretty
similar
to
the
idea
of
it.
Anyway,
it's
pretty
similar
to
the
other
one
that
we
looked
at
and
it's
linking
to
the
same
PR.
So
it's
just
another
implementation
to
kind
of
solve
for
this
same
problem.
A
There
are
a
couple
other
er's
open
still
other
than
just
the
part.
Three
that
we
looked
at
there
is
did
off
stock,
extending
the
Handler
to
allow
for
transaction
creation
by
Ogden
and
the
mark
which
We
Cried
by
T.
This
Merkle
tree
crud,
one
I
believe,
is
just
pending,
re-review
I.
Think
all
of
the
suggestions
have
been
addressed,
at
least
for
the
most
part,
and
then
we
have
here.
A
A
You
can
see
and
track
everything
very
easily,
which
is
all
kind
of
to
fit
into
this
open
source
concept
of
making
sure
that
everything
is
very
clear
for
anyone
who
were
to
you
know
either
jump
in
in
the
middle
of
something
or
to
watch
its
progress
as
it's
going
or
even
down
the
line
in
the
future
to
be
able
to
track
all
of
the
changes
being
made.
Why
they're
being
made
and
kind
of
the
considerations
as
they're
being
implemented.
A
There
are
a
number
of
issues
still
open
related
to
the
PRS,
the
SRI
sorry,
so
once
those
PRS,
the
people
working
on
those
PRS
are
able
to
get
those
merged
in
more
of
these
will
then
sort
of
be
taken
on
and
be
put
in
progress,
however,
they're
I,
don't
think,
is
a
whole
lot
left
for
Milestone
four.
D
B
E
Okay,
sorry
about
that,
just
yeah
I'll
take
both
both
the
the
intro
and
the
standards.
At
the
same
time.
So
the
interrupt
group
has
made
great
progress.
So
we,
as
I
think
is
the
of
memories
are
as
well.
We
have
showcased
the
intra-abuse
case
of
synchronizing
banking
data
between
a
company
and
a
bank
involving
an
auditor
and
a
a
company's
customer.
E
We
have
gone
through
all
the
interrupt
requirements
and
I've
decided
how
we're
going
to
meet
them,
and
now
we
have
Advanced
to
the
how
this
is
actually
going
to
work.
We
are
have
established
the
basically
the
identification
method.
What
did
we're
going
to
use?
How
that's
going
to
work?
We
have
started
to
work
on
the
data
schemas
for
the
messaging
between
the
different
bris.
E
So
this
is
a
this
is
so
we're
making
good
progress
there.
We
are
we're
defining
the
predicates,
so
what
it
means
to
you
know,
work
step,
one
work
step,
two
work
step:
three
how's
that
expressed
how's,
that
expressed
through
through
circuits
the
inputs,
the
outputs
so
making
progress
there.
E
So
we
we
hopefully
get
to
the
point
soon
where
we
have
not
have
nailed
all
the
data
models
down
and
at
that
point
we
can
start
creating
some
some,
some
initial
sort
of
like
experiments
around
around
you
know
having
one
PRI
represented
in
another
through
through
BPI
subjects.
E
So
that's
where
we're
currently
at
obviously
we're
still
waiting
for
for
for
funding.
But
you
know,
all
the
groundwork
is
is
is
being
laid
to
be
successful
and
have
something
shovel
at
the
end
of
the
year.
Hopefully
fingers
crossed.
E
So
that's
that's.
On
the
interop
side,
any
questions
comments.
E
Well,
I
just
want
to
say
it's
like
you
know,
kudos
to
both
the
Bri
and
one
and
Bri
three
team,
they're
they're,
you
know
it's
like
it's
like
Keith
onion
go
off
Ryan,
you
know
great
job,
everyone
Shri,
so
the
on
the
standard
side.
We
have
one
two
three
four
PR
is
actually
no
five.
Now
PR
is
open,
we're
basically
at
the
stage
we're
asking
adding
testability
statements
to
the
standard
which
is
critical.
E
So
we
have
that
completed
for
for
section
two
section,
seven,
but
six
is
is
open
as
an
open
PR,
which
is
over
a
hundred
requirements.
E
We
have
section
eight,
that's
around
all
the
the
thing
about
external
data
data
Oracle.
So
that's
that's
that's
open
and
then
we
have
started
on
on
the
whole
middle
layer,
interop
requirements
and
where
we've
done,
we
have
testability
statements
for
section
five,
one,
five,
two
and
five
three
so
more
to
come.
So
that
is
that's
where
we're
diligently
working
through
that
and
that's
you
know
that's
time
consuming
those
testability
statements
are
not
trivial
and
there
are
a
lot
of
requirements.
E
E
Involved
work,
but
hopefully
it
will
put
the
standard
in
a
in
a
very
good
place
where
any
any
implementer
has
then
also
an
idea
how
to
to
to
test
their
implementations
very
effectively,
and
that
is
it
from
the
standard
side.
Any
any
questions.
E
No
all
right
back
to
you
Sono
all.
E
Sure
so
we
you
guys
already
discussed
the
blog,
so
we
we
have
another
one
coming
up
in
July.
We
have
to
get
that
get
going,
but,
most
importantly,
we
have.
We
have
we're
still
raising
funds,
that's
basically
the
core.
The
the
primary
focus.
The
TSC
right
now
is
to
raise
funds
for
the
interrupt
demo
and
for
the
roadmap
show
for
the
for
the
Road
show
for
for
for
our
our
2bri
implementations.
E
So
we
are
looking
for
sponsors
still
and
we
are
looking
into
the
right
platform
that
we
can
use
to
to
make
this
to
to
make
this
most
effective.
E
So
if
you
know
someone
who
wants
to
sponsor,
you
want
to
sponsor
yourself,
please
reach
out
to
the
TSC,
we're
more
than
happy
to
help
and
get
things
started,
we're
taking
any
amount
so
to
speak.
It
could
be
Fiat
or
crypto.
So
we're
we're
happy
to
to
to
to
do
that.
So
please
reach
out
to
Sono
myself,
on
slack
and
and
and
we'll
get
you
we'll
get
you
going.
E
We
have
like
10
plus
targets
I'm
on
our
sponsor
of
us,
but
no
luck
yet
so
we
have
one
that
is
willing
to
match,
but
not
step
forward.
So
we,
if
we
can
raise
a
certain
amount
of
money,
then
that
organization
will
match
those
those
funds.
E
Sorry,
that's
my
dog,
so
we're
we're
we're
we're
we're
working
hard
to
get
there
more
updates
in
July,
hopefully
positive
ones,
and
that's
it
I
mean
that's
really
really
all
we
that
we
have
to
say
TSC
is
right
now
raising
funds
raising
funds
raising
funds.
Thank
you.
B
Awesome
already
I
think
that's
the
end
of
our
formal
agenda
of
updates.
Is
there
anything
we
missed
on
anything
going
on
in
the
Baseline
world
or
shall
we
shift
into
the
open
floor.
B
All
right
shifting
into
the
open
floor
so
feel
free
to
unmute
and
share.
What's
going
on
in
your
world's
whether
it's
things,
you're
learning
about
working
on
pondering
questioning,
feel
free
to
give
some
updates
Ryan?
What's
going
on
with
you.
F
Hey
I'm
back
I
got
I
got
myself.
Unmuted,
hey
I
had
a
cool
cool
weekend
last
this
this
past
weekend,
I
was
out
in
Jacksonville
Florida
hanging
out
with
the
the
core
Tech
Team
at
V
chain.
Do
you
know
about
B
chain?
You
know
proof
of
authority,
evm
compatible
layer,
one
blockchain
and
very
honored
to
actually
receive
a
a
grant
from
be
changes
recently
to
to
do
some
things
that
are
pretty
baseline-ish
in
the
the
V
chain
ecosystem.
F
You
know,
along
with
Bri
one,
so
the
the
idea
to
this-
and
this
is
kind
of
follows
down
the
track
of
what
we've
been
doing
lately
with
Eco,
which
is
a
carbon
emissions,
nft
right
so
think
about.
Why
would
why
would
a
company
tokenize
their
missions
in
the
first
place?
Well,
there's.
Actually,
you
know
two
particular
reasons
where
we're
specifying
in
that
you
know
one
is.
F
F
So
when
business
ecosystems
look
to
to
cost
share
on
you
know
emissions
reductions
or
offsets,
you
know
what
is
the
instrument
for
that.
So
the
idea
to
that
is:
that's
the
carbon
emissions
nft
that
we're
seeking
to
prototype
there
thanks
to
V
chain
for
a
great
event.
They
gave
free
tickets
to
a
UFC
fight.
You
know
they
they're
marketing,
vechain
at
UFC
and
sustainability
right,
and
you
know
it's
great
to
see
that
this
involvement
and
sustainability
from
you
know
so
many
different
projects,
I'm
a
big
believer.
F
F
Clean
air,
clean
water,
clean
food,
these
these
are
things
that
matter
to
to
you
as
a
person
and
to
businesses
you
know
to
to
all
of
us,
so
it
it's
great
to
to
to
keep
building
there.
F
F
We
still
have
a
really
amazing
partnership
with
clean
middle
who
have
kind
of
rebranded
to
carbon
Mark
there
as
as
well,
but
we're
holding
an
event
July
6
with
carbon
Mark
that
it
walks
through
the
carbon
Mark
API,
so
that
uses
VR
br1
in
the
background
right,
so
we're
bringing
users
into
that
that
whole,
like
technology
stack
of
prvd-
and
you
know
using
that
for
provide
payments
which
you
know,
gives
a
user
the
option
to
get
the
benefits
of
transacting
on
chain
without
having
to
custody,
crypto
so
really
exciting.
F
Stuff
there
a
lot
of
interest
customer
interest,
you
know
growing
there
very,
very
close
to
release
overall
and
I.
Think
you
can
see
how
this
this
is
coming
together
right.
You
know,
you
know,
broadcasting,
you
know
improving
the
market
for
offsets.
You
know
B2B
wise
lowering
costs
there,
but
at
the
same
time
introducing
these
things.
You
know
around
zero
knowledge
and
emissions
and
improving
the
outcomes
there.
So
lots
of
exciting
things
going
on
with
provide
and
Eco,
especially
at
this
time
and
new
Partnerships
all
over
the
place.
B
F
Share
yet
all
of
them,
but
lots
of
cool
things.
B
Awesome
yeah
thanks
for
sharing
with
us
what
you
can
Jack
Gilchrist,
what's
going
on
with
you,
if
you
are
around
at
the
moment,.
G
Yeah,
all
right
so
yeah
I've
been
wrapping
up
integration
with
like
Halo
2,
compiling
Noir
and
Halo
2.
kind
of
killing
some
time
waiting
for
recursion
to
get
built
into
Noir,
but
that's
right
around
the
corner,
so
I'm
gonna
be
picking
back
up
with
ZK
channels
pretty
soon
and
that'll.
G
That'll
definitely
be
something
where
we
can
hit
the
ground
running
because
it'll
be
a
lot
easier
than
architecting
that
in
Halo
2,
especially
where
it's
still
very
like
each
circuit
is
kind
of
application.
Specific.
So
in
order
to
kind
of
scale
that
out
writing
stuff
in
in
Halo
2
is,
is
pretty
preventative,
so
yeah
looking
forward
to
that.
G
Obviously,
that's
that's
something
that
we've
had
a
lot
of
ideas
on
how
to
kind
of
do
like
almost
like
Roll-Ups
for
specific
parts
of
like
a
baseline
interaction.
So
looking
forward
to
coming
back
and
finally
testing
that
out
in
the
next
few
months,
and
then
also
I
wanted
to
ask-
is
they're
gonna
be
I
might
have
talked
about
this
offline,
but
is
anyone
gonna
be
at
ECC
in
the
next
few
weeks?.
G
B
Awesome
alrighty
thanks
for
sharing.
Is
there
anything
else
that
anyone
wants
to
cover
while
we're
here.
D
I
think
we
can
give
a
shout
out
to
Martin
Valenta
right
if
you're
in
I
believe
you
message
in
general
and
also
in
core
devs,
so
not
to
revealed
too
much
because
I
haven't
really
gotten
the
okay
from
Martin,
but,
as
you
can
see
from
his
messages
in
the
group
that
he's
you
know
working
on
his
own
personal
Baseline
reference
implementation,
that's
done
in
golang
with
gunarch
and
I
believe
he
will
be
joining
us.
This
Thursday
at
our
Bri
stand
up
not
necessarily
to
to
join
the
group
in
development.
D
That's
yet
to
be
seen.
But
just
to
you
know,
discuss
some
of
the
roadblocks
he's
run
into
in
going
through
the
docs.
So,
of
course
we
welcome
anybody
to
join
that
conversation.
We'll
probably
hold
it
right
after
we're
done
with
stand
up.
Anybody
is
welcome
from
you
know.
Any
reference,
implementation
or
you
know,
from
a
spectator's
not
to
come
and
join
in
the
conversation
to
see
what
you
know
what
Martin
ran
into
what
he
understood
and
what
was
more.
D
To
comprehend
and
and
then
even
so,
Implement
yeah
so
just
wanted
to
give
a
shout
out
to
him
tackling
Baseline
alone
is,
you
know,
difficult
to
say
the
least.
F
It
is-
and
you
know
this-
this
is
like
my
I'm
gonna
plug
Bri,
one
because
Bri
one's
written
in
in
in
in
golang
right.
So
that's
that's.
You
know.
If
you're
looking
to
do
Baseline
and
you're
writing
it,
the
core
services
in
golang,
that's
that's,
been
open
source
and
and
done
there
so
and
of
course,
there's
a
great
user
experience
around
that
with
with
shuttle.
So.
F
F
Great
great
question:
so
if
you
go
to
docs.provide.services
and
I'll
put
it
in
our
Zoom
chat
here,
but
I
can
also,
you
know,
share
share
my
screen
here
as
well
of
of
where
you
can
find
all
this
today
right.
So
let
me
share
my
if
I
can
share
it
very
quickly.
F
All
right,
docs.provide.services
right
so
on
this
web
page,
you
can
find
all
the
information
about
our
apis
here
recently
we
renamed
our
Baseline
service
Axiom
right.
F
So
this
will
describe
you
know
a
ton
of
information
in
depth
in
terms
of
you
know,
what's
what's
going
on
in
terms
of
the
configuration
now
as
well,
if
you're
looking
for
the
open
source
source
code,
if
we
go
to
github.com
and
go
to
provide
platform
right,
if
he's
thinking
about
writing
it
in
golang,
this
is
where
you'd
find
the
Axiom
API
middleware
all
cure,
and
you
can
see
you
know
many
different
changes
through
the
years
that
are
done
and
committed
here
in
terms
of
you
know
how
it's
meant
to
conform
to
the
Baseline
protocol
instances.
F
F
You
know
examples
in
Postman
right,
so
here's
one
I
did
you
know
recently
regarding
you
know
proving
emissions
right.
So
if
I
look
at,
let's
look
at
this
guy
here
right
if
I
send
this
protocol.
Okay,
I
got
authenticate
here.
F
F
Save
that
let's
go
there,
you
go
so
that's
how
simple
beastline
should
be
for
so
many
developers
right
is,
you
have
you
know
any
kind
of
payload
of
data.
You
know
what
kind
of
work
group,
what
kind
of
type
of
data
and
see
back
your
ZK
proof
that
comes
from
that,
so
that's
just
just
as
an
end
user,
but
again
in
terms
of
understanding
the
internals
of
it
definitely
check
out
the
provide
platform
GitHub
to
learn
about.
You
know
the
things
that
have
been
built
by
so
many
different
contributors.
F
You
know
through
the
years
there
and,
of
course
the
the
other
components
are
all
here
as
well.
So
like
ident,
so
there's
you
know
Bri
one
is
essentially
you
know
five
pieces
right
Axiom
for
the
Baseline
piece,
ident
and
chain
for
the
actual
smart
contract
middleware
both
for
Key
Management
privacy
is,
is
where
we
see
narc
integrated
there
as
well.
So
you
know
privacy
and
is
kind
of
a
sub
component
of
of
Axiom
there
as
well.
So
so
lots
of
cool
stuff
definitely
check
it
out.
F
If
you
have
questions,
you
know
feel
free
to
always
ping
me
Kyle
as
well,
but
feel
free
to
ask
questions
and
you
know
poke
around
see.
What's
there
ask
the
community
because
there's
been
like
I,
said
tons
of
work
on
this
done
over
the
years.
D
Yeah,
nice
and
as
we'll
see
you
soon
or
later
in
the
year
as
we
work
towards
interop
session
between
I,
believe
it's.
D
Be
the
goaling
implementation
and
then
on
our
side
we
have
a
typescript
implementation.
It's
an
even
more
kind
of
test
the
waters
of
can
we
have
two
kind
of
isolated
implementations.
You
know
totally
different
infrastructure
high
level
language.
Can
we
get
them
to
kind
of
connect?
So
now
we'll
see
what
happens
with
that
here?
Yeah.
F
I
think
I
think
always
taking
that
API
driven
approach
it.
You
know,
you
know
it
helps
a
lot
with
that
interop
piece
of
it.
You
know
another
thing
about
you
know
in
terms
of
like
ready
to
use
sdks,
we
have
a
typescript
based
SDK
around
Bri
one,
but
you
know
again
it's
the
same
idea.
It
was
actually
cool
is
like
hey
if
you
implement
the
standard
in
a
certain
way
and
you
like
follow
naming
conventions.
F
Actually
a
lot
of
the
apis
should
be
pretty
similarly
laid
out
and
almost
should
be
interchangeable
right
between
Bureau
and
Bri
3.
In
terms
of
just
point
to
a
different.
You
know:
API
collection,
right
overall,
so
cool
stuff.
Thank
you
for
letting
me
share
more
about
that
and
I
I
hope
and
I
hope.
Our
viewers
enjoy
it.
So.
D
F
D
Yeah
actually
I
think
we
should
get
Martin
on
if
we
can
on
a
future
show
if
it's
a
general
assembly
or
not,
then
you
can
explain
what
he's
gone
through
and
we
can
kind
of
give
real-time
advice.
D
You
know
based
on
you
know
the
issues
that
he's
he's
writing
to
I
think
that
would
be
nice,
especially
as
you
know,
we
get
newcomers
and
who
who
want
to
implement
or
join
a
Dev
team.
We've
always
struggled
with
having
that
kind
of
ramp
up
documentation,
so
go
ahead.
Yeah.
F
It's
it's
always
challenging
because,
like
every
developer
is
different
right,
especially
when
we're
trying
to
be
in
this
intersection
of
like
blockchain
and
Enterprise
things,
because
it's
very
rare
to
find
people
who
are
camped
in
both
right,
so
you
know
think
about,
but
generally
like
a
few
things
always
stand
out
right.
Most
people
have
a
background
in
JavaScript
right.
They
can
always
read
and
write
that
and
like
that's
really
what
I
enjoyed
but
but
seeing
about
fear
I3
is
like
this
implementation,
typescript
very
simple,
to
understand.
F
What's
going
on
in
the
internals
there,
but
otherwise
some
people
have
you
know
more
specialization
than
other
language
or
have
preferences
to
see
certain
things
in
the
execution,
production,
execution,
environment.
So.
D
But
yeah
yeah,
and
on
top
of
that,
the
gun,
Arc
Library
same
thing
right.
If
you
go
for
a
growling
implementation.
D
So
one
of
the
things
that
I
talked
about
with
Martin
he
kind
of
struggled
in
connecting
the
documentation
with
how
do
you
work
in
the
kind
of
the
application
specific
information
between?
Let's
say
the
two
parties?
If
we're
talking
about
in
our
use
term
out
of
purchase
order,
he
felt
like
it
wasn't
exactly
clear
on
how
to
integrate
that
into
you
know
which
layer
within
the
BPI
or
even
within,
like
a
connector
to
the
BPI
and
I,
think
that's
something
that
we
should
address
like
in
the
show.
D
F
Yeah,
there's
there's
a
there's
a
there's
two
parts
of
this
there's
a
technical
like
setup
and
then
there's
the
actual
orientation
of
what
is
the
business
process?
What's
the
what's,
the
kind
of
data
involved
there
right
so
assuming
like
just
the
technicals
are
in
right,
which
means
like
hey
you
onboard
some
credentials
between
systems.
You
have
the
work
group
set
up
now.
The
the
pseudo
technical
business
business
thing
is,
you
know,
definition
of
this
workflow
right.
F
So
that's
a
you
know
agreed
upon
schema
for
this
for
for
different
steps
of
the
workflow
and
then
simply
marshaling
that
data
you
know
into
that
structure
in
into
the
the
into
into
the
bris
to
you
know,
you
know
trigger
the
Creations,
you
get
moves
trigger
the
workflow
right,
but
it's
a
lot
of
steps
to
get
through
right.
It's
it's
and
then-
and
it
takes
a
lot
of
flexibility
to
say,
like
I'm,
going
to
take
any
kind
of
data
type
right,
yeah.
F
You
have
to
you
have
to
do
you're,
making
it
very
generic
right,
because
even
at
companies
like,
let's
say
an
essay
like
different
sap
customers
right,
they
have
there's
a
like
there's
a
core
structure
of
the
purchase
order,
but
then
there's
different
industry,
specific
extensions
to
certain
things
right
that
sometimes
come
in,
which
kind
of
make
you
know
the
compatibility
of
certain
data.
You
know
more
difficult
overall,
still
the
same
core
I
idea,
but
like
how
do
you?
How
do
you
reconcile
these,
like
small,
even
schema
differences
between
partners,
yeah.
D
And
and
not
sorry,
you
know
to
waste
more
time.
I
know
it's
GA
not,
but
we're
on
open
floor.
So
in
the
next
show
you
should
come
in
and
discuss
how
does
Bri
one
tackle
generifying
that
process
right,
but
overall,
that's
probably
the
most
difficult
technical
aspect
right
is
taking
all
these
Concepts
and
generifying
them.
It.
F
It
is
like,
because
you
know
this,
you
know
something
we
did
very
early
on
when
I
was,
you
know,
working
more
directly
with
integrating
to
bro
and
myself
was.
We
were
looking
at
idocs
right,
which
were
these
like
huge
multi-structured
like
payloads,
like
not
simple,
payloads,
but
huge
ones
right.
How
do
how?
How?
How
does
this
the
stack
absorb
such
a
large?
F
And
and
even
insert
when
you
think
about
cardinality,
sometimes
you
know
it's
different
instances
of
like
a
purchase
order.
Data
doesn't
have
everything
mapped,
so
it
could.
You
know,
change
up
from
time
to
time
in
terms
of
like
what
data
elements
are
actually
required
or
optional
descent
right,
because
that
can
change
from
you
know
one
one
transaction
to
another
right,
so
so
definitely
cool
thing
to
to
to
Deep
dive
into
always
happy
to
to
get
another
show
out
there.
F
We
should
just
do
another
show
about
you,
know,
shuttle
and
provide
and
another
time
if,
if
we
can
arrange
it,
so
would
be
glad
to
do
that
anytime.
D
Yeah,
it
would
be
nice,
br3
is
not
as
advanced
at
least
it's
to
the
point
where
we
can
contrast
and
compare
and
see
like
you
know
what
are
the
the
pros
and
cons
of
of
the
certain
approaches
and
and
and
paths
kind
of
untraveled,
and
you
know
the
the
path
that
you
have
chosen
right,
but
yeah
yeah.
F
There's
yeah
definitely
open
for
feedback
too,
because,
like
it's,
it's
like
this,
we
want
to
have.
We
all
collectively
all
want
to
learn
and
share
like
how
do
we
make
the
user
experience
developer
experience
business
user
experience
better
around
this
right
because
I
think
that's
that's
what
actually
connects
it
to
focus
the
most
when
they
like
see
it
work
in
a
business
process.
They
see
it
work.
You
know
relative
to
their
role.
F
They're
like
oh
I
can
go
Implement
that
right,
otherwise
folks
feel
like
they
have
to
like
Build
It
Up
from
the
inside
out,
and
they
don't
have
to
like
it's
it's.
This
is
this
is
why
we're
here
is
like
this
is
why
we're
building
this
open
source
project
is
just
to
help
people
along.
B
Great
yeah,
thanks
for
that
conversation,
and
we
should
definitely
invite
Martin
on
the
next
one
Keith
when
he
joins
the
call
tomorrow.
Maybe
we
could
see
if
he
wants
to
hop
on
next
week.
Wednesday
we
don't
have
a
guest
lined
up.
We
do
have
one
the
following
week,
but
it'll
be
low
pressure.
B
What
was
super
confusing
and
things
like
that,
because
he
seems
to
have
figured
it
out,
which
hopefully
means
that
we
do
have
enough
content
package
together,
but
I'm
sure
it
was
a
uphill
battle
of
some
sort,
so
that
feedback
would
be
great
and
to
also
learn
what
he's
doing
and,
like
you
said,
doing
like
a
live
session,
to
talk
him
through
these
things,
because
if
there's
someone
like
him
out
there,
who
was
able
to
get
this
far-
and
you
know
still
has
interest
and
sees
the
value
which
we
all,
of
course
do.
B
Then
there
may
be
others
out
there
too.
So
we
should
do
it
live.
Let
me
know
if
he's
willing
to
join
a
future
show,
preferably
next
week
and
otherwise
we'll
get
him
on
in
another
session
alrighty.
So
anything
else
before
we
wrap
up.
D
D
About
like
up
where
you're
Jumping,
Up
and
Up
and
Up
In
the
game
up
only
only
yeah
and
the
cool
thing
about
it
is
that
it
displays
the
what
an
nft
collection
right.
What
are
they
called
the
goblin,
some
Goblin
culture
or
something
like
that,
and
they
don't
sell
them,
though
It's
Only
just
displays
it
in
game.
Supposedly
and
but
I
guess.
The
nfts
have
risen
by
something
like
51
in
terms
of
their
value,
just
by
being
displayed
in
game,
so
anyways
I
thought
it
just
mentioned.
D
F
Very
cool
I
didn't
know
that
about
that
game
at
all,
that's
and-
and
it
it's
almost
like
this,
what
are
what?
What's
the
actual
boundary
for
the
game?
Publisher,
to
advertise
things
right,
because
typically
game
Publishers,
only
let
ads
happen
of
things
that
they
can
monetize
right.
This
is
very
different
actually
because
it's
outside
the
conventional
ecosystem
of
monetization,
it's
not
even
Direct
monetization
in
the
game
at
all
right.
It's
just
artwork
right.
B
D
A
A
F
The
publisher
really
I
think
if,
if
it's
a
storefront
like
steam
or
something
else
like
that,
like
they
might
get
a
little
concerned
about
the
monetization
features
in
the
game
right,
but
I
think
there's
still
openness
around
this
idea
of
tokenizing
like
game
assets
right
because
it's
like
you
can
buy
and
sell
things
you
know
directly
to
other
players
or
or
even
take
the
loot
from
a
single
game,
and
you
know
recompose
it
into
a
different
game
right.
That's
that's
that!
F
D
D
F
It's
like
this
right
there
you
know
the
CIA
and,
like
other
intelligence
agencies,
they
they
want
to
Snoop
on
gaming
activity,
because
that's
actually,
where
there's
a
lot
of
you
know.
There
are
criminal
activities
like
that,
take
place
in
Discord
and
those
are
the
places
they
look
out
for
so
they
they
would
be
concerned
about
like
money
laundering
and
those
types
of
things.
How
do
you
prove
it's
compliant?
That's
just
you
playing
a
game.
B
F
Without
you
know
having
to
give
up
your
identity
every
single
time
right,
while
that's
going
on
so
keep
it
safe,
Keep,
It,
Fun,
right
all
those
good
things.
B
All
right,
if
not,
that
will
be
the
end
of
our
June
General
Assembly.
Thank
you
so
much
for
the
great
conversations
in
our
live
Studio
here
and
thanks
to
those
watching,
feel
free
to
comment
with
questions
and
chat
and
we'll
get
back
to
you
in
the
future
and
see
you
all
next
week
on
the
Baseline
show.
Thank
you.
Thank.