►
From YouTube: Baseline Protocol Office Hours #1
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
I'll
put
this
in
the
chat.
This
is
where
this
the
YouTube
stream
is
running
and
I
will
minimize
that
so
I'm,
not
looking
at
myself
over
lag
yeah
now,
so
we
we
have
the
ability
to
stream
sign
people
up
and
I'm
just
gonna
see.
Does
anybody
have
put
in
chat
if
you
can't
unmute
yourself
we're
really
debugging?
This
is
the
very
first
time
we've
used
our
webinars
capability.
A
A
B
A
Then
my
I
set
the
settings
up
correctly,
so
this
is
a
Q&A
session
and
so
I'm
here
with
Sam
Sam
Stokes
is
one
of
the
people.
One
of
the
engineers
who
made
the
baseline
protocol
happen
worked
on
raddish
34
since
the
beginning,
with
Ernst,
&,
Young
and
Microsoft,
and
all
the
others
so
Sam's
a
say:
hi,
hey
and
I'm
John
walpert
I
was
also
on
the
team.
Since
the
beginning,
and-
and
this
is
our
first
weekly
QA
things
we
can
talk
about-
are
how
to
get
involved
with
the
baseline
community
generally.
A
Are
you
having
any
trouble
getting
into
any
of
the
community
stuff?
Are
you
having
trouble
knowing
what
to
do
in
there?
Are
you?
Would
you
like
to
do
more,
but
you're
unclear
how
so
those
are
the
kinds
of
things
we
can
talk
about
with
regard
to
sort
of
the
meta
level
of
this,
but
we
can
also
talk
about
technical
questions.
That's
why
Sam
is
here
and
I
can
like
I
can
I
can
I
can
go
to
a
certain
depth
myself,
so
we
can
talk
about
technical
issues.
We
can
talk
about
deployment.
A
C
And
so
I'm
currently
leading
the
sales
engineering
practice
for
Marco
Polo
Network
anemia,
so
that
you
know
very
well
that
is
based
on
cordon,
so
I
was
just
interested
in
knowing,
of
course,
I
applaud.
All
the
initiative
around
baseline-
and
it
looks
to
me
like
it-
makes
a
lot
of
sense
and
I
was
wondering
aside
from
the
technical
progress
around
the
the
protocol
itself.
Do
you
guys
have
any
roadmap
in
terms
of
like
the
supporting
business
applications
that
will
eventually
use
the
baseline
protocol
from
from
a
vertical
perspective
industry
vertical
perspective?
Yes,.
A
That's
a
great
question:
thanks
Artie,
ona,
correct,
right
and
and
yeah
say
hi
to
our
friends
over
in
kurta.
We're
all
we're
all
in
this
together
right,
so
we're
all
trying
to
make
stuff
better.
I
have
great
respect
for
the
to
myself
and
I.
Think
you
know
Richard,
L,
Brown
and
I
go.
You
know,
kind
of
knock
each
other
about
on
Twitter.
C
A
D
A
Corta
yeah,
so
in
terms
of
the
road
map,
if
you
go
into
the
baseline
protocol,
github
repo
and
it's
in
particular,
if
you
have
Zen
hub
extension
and
enabled-
or
if
you
go
to
the
Zen
hub
web
app
you'll
see
the
the
road
map
which
is
getting
situated
pretty
well
I.
Think
by
next
week
we
will
have
all
the
key
initiatives
and
then
anybody
that
wants
to
join
the
SSE
and
add
an
initiative
can
do
so.
A
C
Am
more
interested
in
like
and
I'm,
not
I,
don't
think
it's
your
time
for
interoperability
and
between
Korda
related
applications
and
those
that
will
thrive
on
baseline,
so
I'm,
just
interested
in
knowing
and
any
full-fledged
business
applications
that
you
guys
are
developing
on
top
on
off
baseline,
of
course,
with
close
feedback
that
you
might
receiving
from
industry
partners.
I
just
want
to
know
like
what
is
the
you
know
the
meet
around.
You
know
the
backbone
that
you
were
developing
and
are
you
planning
to
first
finish?
C
A
A
Is
it
it's
just
a
well-chosen
name
by
the
way
Sam
and
I
worked
on
the
Sam
came
up
with
a
design
pattern
for
doing
this
that
early
on
and
we're
like
what
we
call
this
thing,
what
we
call
doing
a
entanglement,
you
know
blah
blah
blah
and
we
and
one
day
it
kind
of
to
two
or
three
weeks
later
paceline
baselining.
We
should
call
this
baselining.
A
A
Random,
so
so
baseline
is
not
a
something
that
like
corta
corta
is
a
platform
baseline
is
not
so
when
we
talk
about
integration,
baseline
is
entirely
a
cookbook
for
integrations.
That's
what
it
is
right
Sam,
you
want
to
say
anything
about
them,
so
SAT,
Oracle
quart
of
fabric,
any
state
machine
that
needs
to
have
a
verifiable
consistency
between
it
and
another
state
machine
can
use
the
baseline
approach
as
a
way
to
do
it.
C
Sorry
John
there
was
a
little
bit
of
confusion
also
with
what
Paul
Brody
and
the
ey
blockchain
summit.
Actually
so
I
think
the
confusion
came
because
by
now,
I
think
most
of
the
people
that
have
been
following
the
happenings
around
baseline
and
also
associated
with
the
capability
to
perform
in
a
way
transactions
which
are
private
from
enterprise
to
enterprise
leveraging
the
domain
I,
but
I
I
understand
the
idea
around
the
common
frame
of
reference
at
baseline
rings.
C
C
B
I
think
the
goal
of
building
the
protocol
right
now
is
to
make
it
generalize
such
that
it
it's
applicable
to
a
bunch
of
different
use
cases.
So
I
guess
we're
trying
to
build
that
foundation
and
then
make
it
modular
enough
where
people
can
plug
in
their
own
specific
modifications.
As
they'd
like,
for
example,
the
the
Socrates
circuits
would
be
one
thing
that
that
would
probably
be
well-suited
to
being
I.
Guess
people
creating
their
own
building
their
own
circuits
that
specifically
applied
to
their
use
case
and
enforce
their
business
logic.
B
B
Basically,
the
the
different
states
you
go
through
in
a
supply
chain,
where
a
buyer
sends
out
a
request
for
a
proposal,
and
then
the
next
state
would
be
a
supplier
responding
with
a
proposal
and
then
them
agreeing
to
master
service
agreement.
And
at
that
point
you
know,
the
Socrates
circuit
enforces
that
we
get
signatures
from
both
parties
and
that
that
commitment
is
pushed
on
chain.
B
So
we're
trying
to
build
the
foundation
that
would
support
any
sort
of
Socrates
circuit
and
kind
of
build,
the
very
fundamental
states
that
could
fit
to
most
use
cases
and
then
kind
of
leave
it
open
for
people
to
to
plug
in
their
own
specific
circuits.
Or
you
know
that
that
applied
to
their
use
case.
A
Sam
and
I
see
there's
more
participants,
so
I
should
probably
unmute
some
of
them
and
I
will
before
I.
Do
that
I'll
put
this
in
chat
before
I
forget
Chat
Chat
there.
It
is,
there's
the
Zen
hub
roadmap,
the
web
app
version,
and
anybody
can
get
right
access
to
that
by
joining
the
SSC.
So
anybody
that
wants
to
take
accountability
for
a
piece
of
work
and
yeah
in
the
next
week
or
so
you'll
see
that
this
roadmap
will
be
filling
up
with
quite
a
bit
of
stuff
and
I'll,
promote
more
folks
to
panelists.
A
There
you
go
hey
everybody,
I
see,
there's
one
question
in
the
Q&A,
so
basically
I
just
hardens
the
data
integrity
around
a
set
and
central
source
of
truth
like
an
ERP.
How
does
it
differ
from
writing
to
any
other
DLT?
Well,
I
think
you
know
as
I
understand
it.
There's
already
a
couple
of
folks
and
it's
turning
get
hard
to
track
everything.
That's
going
on
around
baselining
we're
tracking
an
s
AP
and
dynamics,
we're
using
the
baseline
pattern
to
show
how
to
connect
s
AP
and
dynamics
in
a
baseline
sort
of
way.
A
I
would
say
that
you
know
the
pattern
itself,
because
again
it's
a
cookbook.
It
doesn't
care
if
it's
using
the
main
net
that
you
know.
I
talked
about
the
main
that
the
capital,
M
maintenance
and
yeah
I'm,
a
partisan
of
thinking
that
the
etherium
is
a
pretty
good
candidate
for
that
maintenance,
if
I
say
main
net
and
I.
A
Just
like
you,
don't
want
more
than
one
tcp/ip,
so
the
main
that
is
lower
level
than
say,
corta
or
fabric
or
any
of
these
other
technologies,
and
which
main
that
we
use
well
I
like
aetherium
I
like
youth
too,
but
you
don't
have
to
and
that
the
future
is
not
written
on
that.
Yet
any
common
frame
of
reference
can
do.
You
can
set
up
a
traditional
database
in
the
baseline
pattern
and
it
would
work
you
can
use
any
blockchain
and
it
would
work.
B
E
E
E
So
that's
why
my
question
was:
how
should
we
be
thinking
about
it
as
a
place
to
output
data
to
from
let's
say
a
plugin
that
we
built
that
poles
from
dynamics
some
sort
of
data
that
we
want
to
harden
the
integrity
of
and
that
we
were
going
to
stamp
it
in
our
mind
to
private
etherium
hyper
ledger
like
sometimes
we
do
with
trade
lens
or
something
of
that
nature.
But
now
we
have
baseline
to
mix
and
obviously
be
why
Microsoft
they're
all
part
of
our
ecosystem,
so
so
curious
about
that.
So.
A
E
A
Yeah,
oh
yeah,
very
much
respect
or
CEOs,
been
friend
for
a
while
I
think
that
you
know
so.
The
difference
here
is
that
there's
integrity,
there's
maintaining
the
integrity
I
mean
you
can
you
could
have
stayed
hash
and
put
that
in
the
New
York
Times
classified
section,
which
actually
has
been
done
right.
This
is
proof
of
entanglement
or
proof
of
consistency
right.
So
you
have
your
record
in
dynamics.
A
We
are
now
I
say:
I
I,
you
and
I
are
doing
a
P,
oh
right,
yeah,
yeah
and
I'm
on
sa
P
and
my
so
my
procurement
system
is
on
sa
P.
Yours
is
on
dynamics
by
the
way
we're
just
talking
about
the
dynamics
team.
Yesterday
it
was
a
fantastic
call.
They
were
incredibly
supportive
and
they're
helping
out
in
in
really
great
ways
to
to
make
a
particular
demo
happen
and
we're
very
grateful
to
them
for
that,
as
is
si
P
and
you
know
bright
and
and
other
than
other
companies.
A
So
with
with
this
again
there's
no
new
product
or
platform
in
the
middle
there's
just
a
design
pattern.
That
said
that
we
call
baselining.
That
says,
you
have
a
record
in
dynamics
you're
going
to
serialize
it
and
send
it
to
me
an
S
AP
normal.
You
know
messaging
protocol,
peer-to-peer
point-to-point
and
then
we're
defining
the
specification
for
what
that
needs
to
be.
So
you
can't
just
use
any
you
know
to
be
baseline
compliant.
You
might
say
you
wouldn't
use
just
any
messaging
protocol.
It's
got
to
be
gtp
are
compliant,
etc,
etc.
A
We've
been
talking
a
lot
to
the
Nats
people
about
that.
So
that's
one
potential
way
of
going
about
that.
We
implemented
the
first
demo
in
whisper,
which
is
exactly
not
right
right.
So,
in
fact
we
did
it
that
way
to
say
yeah.
This
is
what
you
could
do,
but
it's
not.
We
just
need
messaging
here
so
you're
going
to
get
that
message
to
the
si
PE
system.
Asap
system
is
going
to
sign
it,
and
then
we
go
through
a
process
whereby
that
baseline
proof
is
rendered
under
zero
knowledge
into
onto
the
main
net
and
yeah.
A
E
A
Then
you
have
to
ask
why
wouldn't
I
just
use
the
thing?
That's
always
on
and
running
a
camp
and
can't
lock
me
out
for
that
right.
It's
just
middleware.
It's
not
like
I'm
putting
data
there
I'm
not
putting
business
data
there
and
then
that's
the
job.
The
specification
will
be
heavily
around
making
sure
that
we
don't
mistakenly
create
any
kind
of
specification.
We're
sensitive
business.
A
Information
coming
from
the
company
running
dynamics
is
exposed
in
any
way,
including
things
like
Poisson
distribution,
analysis
of
event,
tracking
rain
saying
you
know,
I,
don't
know
who
you
are
I
don't
know
what's
going
on,
but
I
can
I
can
see
the
pattern
here.
I'm
gonna
make
you
and
with
you
know,
a
year
of
AI
analysis
on
this
data
right.
You
know
the
job
of
baselining
is
to
say
no
we're
using
the
maintenance
in
such
a
way
that
you
don't
have
to
worry
about
it
as
a
C.
B
Yeah
that
that
sounds
great,
so
yeah
that
to
John's
point
just
to
emphasize
one
of
the
things
he
said
was
you
know
why
would
you
use
aetherium
over
other
distributed
Ledger's
yeah?
Our
reasoning
was
etherium
and
it
doesn't
have
to
be
a
theorem.
It
can
be
others,
but
that's
one
of
the
most
readily
available
Boudreau.
E
We'd
use
a
theorem,
we'd
use
a
mix
right.
We
use
a
bunch
of
asymmetric
networks,
so
we'd
use
public
etherium
private
etherium
hyper
like
we're,
because
we're
writing
to
a
bunch
of
different
places
for
a
bunch
of
different
reasons,
right
and
depending
on
the
frequency
of
those
rights
and
transactions,
and
reads
that
you
know
certain
things:
don't
make
sense,
where
other
things
make
sense
because
of
cost
of
things
like
that
right.
B
C
C
Let's
say
that
IPO
was
created
out
of
an
ERP
system
that
is
intercepted
for
the
baseline
protocol.
Oh,
that
creates
so
to
say
Sam
even
listener
on
the
receiving
s
AP
system,
so
that
it
kind
of
accepts
that
P,
oh
and
automatically
creates
like
an
invoice
I'm
just
creating
a
very
simplified
version
here,
but
so
the
supplier
would
first
need
to
approve
the
P,
oh
and
then
they
would
create.
They
would
have
like
an
invoice
on
their
respective
ERP
system.
C
So
is
this
now
done
and
achieved
through
this
middleware
so
that
essentially
it
kind
of
listens
from
it?
It
listens
like
events
happening
in
the
European,
then
it
on
a
bilateral
basis.
It
then
instructs
the
receiving
party
to
create
the
object
on
the
other
side,
and
then
it
goes
and
not
arises.
What
happened
on
the
May
night?
Is
this
more
or
less
like
a
good
summary
of
what
you
guys
are
doing?
Yeah.
A
You've
got
a
Sam,
you
worked
on
the
messaging
part,
but
the
only
thing
is
it's
not
that
there's
a
baseline
middleware,
it's
just
that
the
pattern
says
yeah
use
messaging
and
what
you
just
described
is
messaging
and
EDD
si
done
in
a
certain
order
right.
So
the
protocol
is
saying
this
is
the
order,
and
these
are
the
rules.
You
should
follow
to
make
sure
that
you're
doing
this
securely.
A
But
you
know
if
you
use
messaging
protocol
a
or
B
you
know
that's
up
to
your
implementation
right
as
long
it
and
when
we're
where
we
would
suggest
that
the
main
that
is
important
is
to
say:
well,
you
want
to
have
one
common
frame
of
reference
and
you
wouldn't
be
nice
as
long
as
you're,
not
getting
you're,
not
revealing
anything
about
your
business
activities
wouldn't
be
nice.
If
that
was
something
that
is
no
longer
a
silo,
everybody
is
just
using
it.
It's
always
there.
It's
always
on
you
pay
as
you
go.
E
E
A
An
ESB
for
state
machines,
and
so
the
real
competitor-
maybe
it's
that
really
competitor,
but
the
better
more
apt
competitor
to
this
idea
or
to
the
main
map,
is
not
corta
or
fabric.
It's
embrace.
Even
then,
you're
gonna
still
want
to
use
mq
series
right.
You
know,
but
this
would
allow
you
to
to
have
an
ESB
where
you
you're,
not
where
you're,
where
your
dynamic
system
isn't
just
telling
you
what
you
know,
but
it's
also
on
a
record
by
record
basis.
A
We
atomic
compartmentalization,
so
that
counterparties
only
know
that
one
record
of
activity
or
that
one
bit
of
a
workflow
so
think
about
supply
chain
where
you
might
have
a
party
in
the
workflow
that
shouldn't
know
about
step.
Two
at
all
shouldn't
even
know
it
exists.
Right,
say:
your
shipper
is
also
a
competitor,
not
like
that
ever
happens
in
the
world
today,
right,
you
know
you
guys
ever
used
to
be
able
to
grab
their
their
delivery
date
for
your
invoice
process
without
them.
A
More,
the
more
the
worlds
about
coopertition
and
the
more
BPM
is
about
cross
company
and
multi
company
business
process.
Automation
and
our
enterprise
service
systems
of
record
need
to
be
more
about
what
all
of
us
know,
not
just
what
one
of
us
not
what
we
know
the
more
a
baseline
protocol
becomes
important
unless
you
are
okay,
with
putting
all
of
your
internal
data
on
a
new
threat,
surface
called
a
blockchain
right,
private
or
public
and
I.
Don't
think
anybody
any
CI
said
any
C.
So
that's
that
I
know
is
not
thinking.
A
A
Yeah
I
think
I
had
a
hand
in
this
I'm,
sorry
to
say,
but
that
was
there
in
2015
when
we
all
got
excited
about
private
blockchains
and
you
know
built
one
of
the
bigger
ones,
but
at
the
time
we
were
thinking
that
we
would
be
able
to
create
these
consortium
more
quickly
and
easily.
If
we
could
say
hey,
all
of
us
have
control,
but
none
of
us
is
in
control
of
the
system
through
which
we're
doing
business.
A
I
wrote
that
line
and
I
think
I
was
a
little
bit
wrong
because
it
turns
out
it
takes
just
as
long
to
forge
these
damn
things
and
they're
still
just
as
hard.
These
alliances
I've
been
doing
alliances
for
30
years.
It
takes
18
to
24
months.
It
still
takes
18
to
24
months,
and
now
we
have
to
teach
people
blockchain
right
and
what
we
basically
said
to
them
was
and
quarter
by
the
way
I
have
to
give
props
is
the
best
at
this
particular
problem,
because
it's
so
finely
grained.
A
A
A
What
we
want
is
a
common
frame
of
reference
so
that
we
know
that
all
of
our
respective
databases
are
in
a
state
of
consistency
on
an
atomic
basis,
but
we
didn't
need
and
don't
need
and
don't
want
when
you
think
it
through
is
a
single
source
of
truth,
where
everybody
in
a
in
a
business
line,
has
admin
access
to
the
root
repository
of
the
information,
because
that
means
your
stupidest
admin
is
going
to
make
you
all
when
they
get
hacked
by
mr.
robot.
Is
that
what
you
do?
What
does
any
of
them?
Do
it?
A
Do
any
of
us
really
want
that
I?
Don't
think
so
right
so
don't
put
anything
on
a
common
framework
on
a
single
source
of
truth
that
is
maintained
by
hundreds
or
tens
or
even
20s,
get
those
smaller
large
number
of
companies
unless
you're
really
confident
in
every
single
admins
ability
not
to
get
hacked.
So
so
we
said:
let's
not,
let's
make
that
problem
irrelevant.
Let's
not
use
it
for
that.
Let's
use
it
as
middleware
so
that
we're
really
tolerant
of
it
getting
hacked
because
we
don't
really
care
there's
nothing
on
it.
A
A
Actually,
we
actually
have
hit
the
bottom
of
the
hour
and
you
know
we're
gonna
keep
these
short,
but
we're
gonna
do
them
often
so
we'll
do
them
every
two
week
is
there
which
I'll
leave
this
open
for
a
couple
of
minutes
for
any
last
questions,
any
comments
about
things
you'd
like
to
discuss
in
the
future,
and
obviously
you
know
you
know
it's
pretty
easy
to
to
get
into
the
slack
and
make
suggestions
about
what
we
should
be
talking
about
on
these.
Does
anybody
have
any
last
questions.
D
Yes,
this
is
Boris
I
think
this
was
very
helpful.
I
mean
and
I'm
a
technical
business
analyst
and
spent
like
what
con
quite
a
few
projects
would
Ian
why,
in
the
past
regulatory
specific
in
the
finance
industry,
so
I
have
been
kind
of
like
getting
into
helium
for
about
a
year
and
and
because
this
is
I
think
baseline
from
what
I've
seen
like
the
webinar
we
had
there
I
couldn't
join
it,
but
I
was
listening
to.
You
looks
to
me
like
something
at
I
guess
at
a
conceptual
level.
D
At
this
point,
I
don't
fully
understand
the
details,
but
the
conceptual
level
sounds
really
great.
I
mean
it's
something
that
could
be
very
beneficial
since
blockchain
is.
Is
it
as
we
all
know,
it's
pretty
complicated
beast
from
a
technical
and
and
business
perspective
also,
but
so
I
would
like
to
definitely
I
I
do
have
questions
to
just
kind
of
in
the
middle
of
my
workday
so
in,
but
it
is
very
helpful
and
I
hope
you
can
continue
this
in
the
next
in
the
future.
Yeah
Thank.
A
You
Boris,
and
if
you
are
you,
if
you
go
to
baseline
protocol,
org
you'll,
see
the
inviter,
the
slack
and
yeah.