►
From YouTube: Baseline Protocol Steering Committee 11 9 2020
Description
November 9th meeting of the Baseline Protocol Steering Committee. For more information, go to: https://baseline-protocol.org
A
Hi
everybody,
it's
great
to
see
you
all
boy,
there's
a
lot
of
people
on
the
call
today
lots
to
talk
about,
and
I
apologize
the
the
minutes
which
share
my
screen.
A
There,
it
is
the
minutes
I
I
don't
have.
I
did
not
update
the
minutes,
or
rather
my
I
have
succumbed
to
yet
again
thinking
that
I've
updated
something
and
then
not
hitting
the
button
and
it
not
updating
so
I'll
I'll
go
through
the
the
agenda
this
morning.
It's
not
complicated
and
I
see
that
there
are
no.
There
are
no
suggestions
for
agenda
additions
other
than
bill.
I
think
you're
ready
this
week.
Yes
or
did
you
want
to,
or
did
I
see
a
that
you
wanted
to
push.
B
We
have
a
conflict
this
week.
The
soonest
we
can
do
is
two
weeks
from
now.
We
have
a
conference
presentation
at
the
moment.
A
Understood
and
apologies
again
for
last
time,
not
getting
you
on
that
on
there
properly,
but
hopefully.
C
A
Maybe
you
can
bill
if
there's
any
information
that
you
can
link
people
to
if
there
is
anything,
then
that'd
be
interesting
for
folks.
A
I
see
no
worries,
okay,
any
so
kyle.
I
think.
Actually
I
see
brian
on
brian.
Do
the
maintainers
have
have
news.
I
know
you
have
one
piece
of
news
about
a
new
maintainer.
C
Sorry
yeah,
we
have,
I
think,
wasn't
it
announced.
D
A
That
is
the
news:
okay,
everyone
please
golf
club
for
anais,
frank,
the
newest
maintainer,
on
the
maintainer.
A
Team,
I
see,
I
see
the
hands
going
up.
Awesome
we're
really
we're
really
excited
about
that.
Anais
has
been
an
amazing
contributor
and
has
a
pretty
good
story
about
how
how
she
became
one
so
pull
her
aside
and
ask
her
about
that.
Sometime
kyle.
I
know
we
talked
about
this
about
an
hour
ago.
Do
you
have
any
other
issues
to
bring
up
for
maintainers
or
brain.
C
A
Okay,
I
think
we're
batting
a
thousand.
You
guys
are
far
too
well
organized
and
nice
to
each
other
you're,
giving
us
nothing
to
do
as
a
technical
steering
committee
we're
supposed
to
be
resolving
disputes
and
you
have
no
disputes
so
shameless.
A
Okay,
yes
and
I'll
echo
this
for
all
all
you
folks
out
there,
especially
those
who
are
in
leadership
positions
in
large
companies.
This
is
definitely
a
time.
There
are
some
big
companies
that
have
now
done
this
they've
made
it
safe
for
their
employees
to
participate
they've
signed
eclas.
A
They
have
communicated
to
their
engineering
and
architecture
teams
that
they
can
contribute
in
this,
and
it
would
be
very
good
to
let
your
engineering
communities
and
your
companies
know
about
the
baseline
protocol.
We're
happy
to
do
events.
We've
already
done
several
and
there's
a
whole
bunch
of
people
that
can
do
those
events
now
too.
A
So
it's
not
a
small
group
and
and
get
people
educated
and
up
to
speed
and
contributing
so
be
great
to
see
more
contributors
from
those
companies
anything
else
from
the
maintainers
before
we
move
on.
A
Okay,
so
the
agenda
today
is
going
to
be
largely
dominated
then
by
the
summit.
A
Hopefully,
everybody
here
has
heard
about
and
is
anticipating
the
thursday
summit
and
hopefully
has
registered
for
it,
or
at
least
has
told
their
community
to
register
for
it
any
questions
about
it.
So
far
we
have
we're
going
to
tee
up
several
people
who
are
running
tracks,
we're
going
to
show
you
the
the
the
the
conference
floor
as
it
were,
and
we're
going
to
go
into
some
other
things
like
that.
A
Okay,
mark
haddle,
would
you
like
to
give
us
a
quick
overview
and
I'll
I'll
take
the
liberty
of
sharing
screen
and
showing
people
what
they're?
What
they're
looking
forward.
A
Oh
looks
like
mark
when
I
might
not
be
in
yet
I'm
sorry
about
that.
Everybody
nick
had
a
last-minute
thing,
and
so
he
was
not
able
to
do
it.
I'd
also
like
to
point
out
for
the
record.
Nick
kritikos
and
a
team
of
people
have
been,
as
you
may
know,
showing
up
every
morning
at
10
a.m.
Seven
o'clock
his
time
and
he
chose
the
time
to
to
to
prepare
for
this
summit.
A
It
is
an
astounding
show
of
commitment
to
the
work
and
I
think
again
just
a
lot
of
gratitude
to
nick
and
everyone
else
I
mean
andreas
has
been
there
mark
hall's
been
there
nearly
every
single
day,
stefan's
been
there.
A
Evan
mcmullen
has
been
there
ever
since
she
got
involved.
Anais
has
been
there
just
ton
of
people
and
I'm
missing
several.
So
I
sorry
if
I
missed
you,
gina's
been
there
just
getting
ready
for
this
thing
and
in
fact
we
worked
all
weekend
to
to
set
up
the
ability-
and
this
is
cool
for
all
eight
tracks-
of
the
of
the
event
which
you
can
get
to
here-
the
baseline
protocol
summit
registration,
which,
by
the
way,
went
over
300
registrants.
A
A
So
I
did
a
straw
poll
on
that
and
found
that
about
at
least
20
to
40
percent
of
the
registrants
are
in
fact
in
that
category
and
others
are
interested
in
learning.
So
that's
that's
really
good!
There's!
You
know
people.
I
think
understand
that
this
is
not
a
webinar.
It's
not
gonna,
be
a
bunch
of
speeches
and
fireside
chats.
A
It's
gonna,
be
people
identifying,
arguing
about
specifying
and
architecting
the
next
set
of
features
and
non-functional
requirements
for
the
roadmap
and
ultimately
to
at
least
in
some
cases
create
submissions
for
the
baseline
protocol,
hackathon
2020,
which
will
begin
in
december
questions
on.
A
That,
okay,
so
the
just
to
show
the
I'm
gonna
bring
up
the
yeah
there.
It
is.
This
is
the
breakout
session.
This
is
the
event
show
floor.
Can
everybody
see
this.
F
A
Thanks
anis
so
I'll
go
to
the
rsvp
page
you'll
see
right
here,
67
rsvp's!
Now
this
isn't
signups,
there's
been
300
signups,
but
67
people
have
actually
gotten
into
the
plus
nine,
so
yeah
76
people
have
gotten
in
and
oh
actually,
no,
it's
probably
67..
It
looks
like
it's
attitude.
The
have
actually
gone
in
and
lit
up
the
page,
so
you're
all
here
and
you'll
see
yeah
it's
it's
pretty
simple.
You'll
go
into
participate.
Now
you
can
read
up
on
on
everything.
Here.
Are
some
rules
how
to
participate?
A
And
when
you,
you
jump
in
you're
you're
right
into
here's,
the
schedule
and
I'll
go
into
that
in
a
little
bit.
Nick
has
been
doing
a
lot.
Nick
and
anais
did
some
analytics
on
who
was
signing
up
and
what
they
were
saying
they
when,
when
they
could
show
up
for
different
sessions,
and
so
these
I'll
go
into
in
a
second,
you
have
we're.
Gonna,
have
eight
separate,
live
streamed,
zoom
environments
up
for
30
hours
from
10
a.m,
on
friday
morning
to
4
p.m
or
5.
A
I
guess
on
on
on
or
thursday
morning
and
then
4
4
4
5
p.m.
On
friday
afternoon,
that
is
to
make
sure
that
we
have
sort
of
around
the
planet
run.
There
are
people
in
india,
india.
There
are
people
in
singapore,
there
are
people
all
over
the
place
and
we
don't
even
know
where
some
of
the
the
others
are
coming
from.
It
is
a
you
know:
I
don't
wanna.
A
We
we've
tried
to
manage
the
fact
that
yeah,
that's
ruben.
Those
are
all
east
u.s
eastern
time
zone
times
right
so
10
10
am
us.
Eastern
did
some
research
on
on
what
times
to
to
run
the
initial
plenary
and
yeah
10
a.m
on
on
thursday
seemed
to
be
the
the
least
awful
for
the
least
amount
of
people
yeah
the
other
way
around
so
yeah.
This
is
the
opening
plenary
which
will
start
on
at
10
a.m.
A
It'll
just
be
an
hour
or
so
just
to
go
over
checkpoints,
how
things
work,
setting
expectations
and
and
taking
people
through
the
different
breakouts
and
making
sure
that
everybody's
really
dialed
into
the
idea
of
making
every
one
of
these
breakouts
an
activity-based
sort
of
thing
right
where
they
each
breakout,
is
going
through.
Let's
build
this
or
let's,
let's
generate
this
output.
This
content,
this
this
specification
or
this
or
this
issue
that
we'll
put
that
we
will
enter
into
a
git
coin,
hackathon
any
questions
so.
A
A
Okay,
so
yeah,
so
this
is
this
is
what
it
looks
like
and
you'll
see
that
dan
norken
dan.
Would
you
like
to
to
talk
about
your
track
for
the
education
session.
D
Yeah
sure
thanks
john
yeah,
so
I
guess,
if
you,
if
you
click
into
the
breakout,
one
content
is
still
still
being
crafted
everyone.
But
again,
just
like
john
said:
it's
a
working
session,
slash
education,
type
of
session,
we've
all
heard
and
seen
the
radish
34.
D
First
reference
implementation
outside
of
the
bri
1
and
1.1
up
as
well,
and
we
thought
that
it
would
be
interesting
to
have
it
in
a
hands-on
type
of
a
fashion
where
we're
provisioning
the
environment,
having
folks
be
able
to
log
in
through
kind
of
like
a
guided,
hands-on
tour
as
to
what
a
application
that
is,
baselining
would
look
like
from
start
to
finish,
leveraging
the
radish
34
through
that.
What
we're
going
to
be
able
to
do
is
really.
You
know
showcase
certain.
D
I
guess,
if
you
will
checkpoints
along
along
the
along
the
happy
path,
if
you
will
of
of
the
procurement
type
of
use
case,
thereby
giving
a
little
bit
more
context
into
the
core
interface
work
group
or
the
global
phone
book
working
group
or
the
product
cookbook
et
cetera.
So
as
as
you
go
through
this
workshop
you're
going
to
be
able
to
see
that
you
know
this
is
how
it's
presented.
We
are
definitely
looking
to
keep
this
in
a
workshop
type
of
fashion.
D
So
any
any
comments,
suggestions
on
how
we
should
be
able
to
explain
the
baseline
protocol
introduce
the
baseline
protocol,
graphics,
words
messaging,
so
on
and
so
forth.
You
know
this
is,
is
a
place
for
us
to
work
together
on
that
and,
as
you
start
to
go
through
this
kind
of
hands-on
lab-
and
you
know
there
is
going
to
be
certain
ideas
that
you
that
you
have
we're
gonna,
send
you
to
the
right
working
sessions
so
that
you
can
further
that
idea
and
then
come
come,
come
and
jump
back
into.
D
You
know
experiencing
baseline
protocol
to
kind
of
get
kind
of
like
a
high
level
holistic.
A
A
Thanks
dan,
so
that's
that's
the
the
the
education
track
and
I'll
be
running
the
entire
time
right.
D
A
And
and
probably
a
good
moment
to
say
one
of
the
coolest
things
is
that,
because
we're
going
to
have
effectively
kind
of
a
robo
host
running
all
of
the
all
of
these
zooms,
we
will
be
able
to
run
we're
going
to
be
live.
Casting
those
as
long
as
the
macbooks
that
we've
set
up
for
this,
don't
catch
fire
after
some
number
of
hours
of
continuous
youtube.
A
A
Potentially
I
mean,
maybe
not,
maybe
maybe
people
are
active
the
whole
way
through
and
people
that
you
know
break
for
dinner
and
go
away.
Maybe
you
know,
go
to
bed
other
people
come
in
and
who
knows
we?
Don't
you
know
it's
pretty
early
in
any
organization
like
this
to
be
seeing
well,
certainly
as
many
registrations
as
we
already
have
for
standards
operation,
but
also
just
in
general.
A
I
mean,
I
think,
imagine
what
this
is
going
to
be
like
next
year,
so
it
might,
it
still
might
be
a
little
sparse
and
that's
okay,
because
we're
live
streaming
these
all,
so
there
might
be
like
two
or
three
or
four
people
in
a
particular
session.
Talking
about
something
and
people
can
that
come
in
hours
later,
can
scrub
back
and
find
those
conversations,
those
those
live
points,
and
we
can
also
put
those
live
points
in
the
breakout
notes
right
up
top.
A
So
if
you've,
if
you've,
if
you've
been
talking
about
something
important
interesting,
that
people
that
come
in
later
want
to
know
about
or
should
know
about,
and
that
they
can
maybe
play
through
a
2x
speed
on
on
zoom
or
on
youtube,
we
can
put
the
link
right
there
and
at
the
time
frame
of
that
live
stream.
That
would
correspond
to
that
time.
To
that
conversation.
A
C
We
can,
I
mean,
actually,
can
you
can
you
come
come
back
to
me.
I'm
actually
let
me
do
something
like
that.
A
G
Absolutely
thank
you
so
much
guys,
so
we
don't
have
too
much
visual
aid
here,
fortunately
or
unfortunately,
a
lot
of
our
our
work
in
progress.
Content
is
just
that
work
in
progress,
but
I'm
happy
to
speak
about
the
global
phone
book
project,
which
is
a
really
exciting
collaborative
team,
representing
folks
from
consensus
from
microsoft
from
you
know,
every
every
corner
of
the
planet
and
we're
certainly
welcoming
more
and
the
intent
of
this
conversation
is
for
us
to
discuss.
You
know
how
we
want
to
approach
the
registry
problem.
G
So
how
do
we
want
to
think
about
the
act
of
finding
other
organizations
with
which
to
baseline
about
establishing
those
relationships?
G
And
then
beyond
you
know
that
sort
of
search
and
secure,
then
thinking
about
you
know
what
does
an
ecosystem
of
these
existing
relationships
mean
what
additional
information
interfaces
interactions
can
we
enable
to
make
the
baseline
process
even
simpler?
So
if
you
are
interested
in
exploring
this
global
phone
book
or
the
the
premise
of
how
to
find
baselining
partners
and
and
secure
those
relationships,
we
absolutely
welcome
everyone
to
join.
I
would
also
take
this
moment
to
pitch
the
global
phone
book.
G
Slack
channel,
I
would
invite
a
number
of,
or
a
number
of
folks
have
already
shared
some
great
ideas,
some
awesome
questions,
requirements
and
suggestions.
So
if
you
have
any
thoughts
that
you'd
like
to
see
discussed,
please
feel
free
to
drop
them
in
that
slack
channel
and
I'll
I'll.
Put
a
note
in
here
as
well,
but
yeah
we're
very
much
looking
forward
to
this
being
a
working
session.
G
Our
intent
is
to
frame
up
the
challenge
that
we're
facing
together
to
discuss
it
in
a
little
greater
detail
and
then
to
start
exploring
what
kinds
of
initial
solutions
could
be
possible
and
could
be
meaningful
to
this
community.
So
understanding
that
we
are,
you
know,
I
certainly
personally
feel
like
I'm
almost
a
bit
of
a
newcomer
to
the
excitement
around
baseline,
and
so
we've
been
really
fortunate
to
to
feed
off
of
the
pre-existing
conversations
around
the
phone
book
to
this
point
and
yeah
just
very
excited
to
build
it
moving
forward.
A
Thanks
thanks
so
much
johan,
so
that's
the
phone
book
project
we'll
come
back
to
core
interfaces.
There
is
another
session
and
by
the
way,
this
this
session
is
being
looked
at,
but
there
are
some
folks
who
seem
to
be
pretty
passionate
about
this.
The
baseline
protocol
product
cookbook
this
session
is
there
anybody
from
that
session
on
that
would
like
to
take
up
take
this
comment.
H
Yeah
I'm
on,
I
can
give
a
brief
overview
of
kind
of
what
we're
going
for
here.
So
you
know
this
session
is
still
very
much
under
discussion.
We
just
had
a
meeting
last
week
and
we've
made
some
progress
on
it.
Basically,
a
summary
of
what
we're
doing
we're,
trying
to
help
product
teams
add
baseline,
enabled
features
to
their
products.
So
the
goal
is
to
make
adoption
easier
and
we
can
work
toward
that.
H
You
know
with
documentation
and
also
with
reference
code,
so
people
in
applications
they
need
to
understand
how
to
interact
with
is
baselined
attributes.
So
you
know
we
want
to
consider
user
experience.
We
want
to
consider
like
practicality,
and
so
we
we're
having
a
session
that
at
this
point,
is
kind
of
split
into
two
general
segments.
H
One
is
business
use
cases
and
the
next
is
developer
use
cases
and
so
we're
trying
to
kind
of
delineate
between
what
business
focused
individuals
who
kind
of
want
to
understand
this
better,
but
are
still
technical
need
and
also
just
what
developers
themselves
are
looking
for.
First,
so
we've
already
got
a
deck
up
and
coming
and
some
new
people
have
just
joined.
So
this
week
will
be
our
big
week
for
progress.
A
Hey
obvious,
that's
terrific
and
I
I
just
noticed
that
yeah
glenn
scott
from
intuits
on
I
mean
that's
the
kind
of
company.
I
won't
speak
for
them,
but
that's
the
kind
of
company
and
by
the
way
into
it,
welcome
yeah,
hey
there.
You
are
yeah
glenn.
You
might
want
to
reach
out
to
avia.
A
You
know
and
and
look
into
this
particular
session,
because
you
know
I
can
imagine
how
cool
would
it
be
in
some
future
point,
for
you
know
something
like
quickbooks
to
you
know,
have
user
experience,
components
that
are
lit
up
right
out
right
there
in
front
of
their
eyes
that
they'll
allow.
A
C
Registered
for
the
for
the
several
sessions
that
may
be
a
bit
overbooked,
it's
a
bit
like
in
the
candy
store
at
this
point,
so
we'll
see.
A
It's
in
a
way
even
better
than
showing
up
in
moscone,
for
you
know
the
developer
event
or
something
because
you
know
you
can
literally
see
in
real
time
who's
in
what
rooms
you
can
jump
into
a
private
room
or
a
semi-private
room
and
that
isn't
being
recorded
and
talk
about
stuff
with
just
two
people
for
as
long
as
you
like,
and
so
it
should
be.
We're
really
hoping
we're
taking
big
risks
here.
I
don't
know
that
anybody's
tried
things,
something
just
the
exactly
the
way
we're
doing
this.
A
There
could
be
lots
of
dead
air
all
over
the
place.
We
we
kind
of
expect
it,
but
we
hope
that
there's
enough,
you
know
activity
that
30
hours
later,
we
have
real
time
spent
doing
art.
You
know
real
architecture,
and
you
know,
having
those
you
know,
those
arguments
and
discussions
about
which
way
to
go.
So
you
know
the
real
question
is:
will
be.
A
Will
people
at
this
point
in
our
maturity,
be
at
a
point
where
this
is
close
enough
to
and
near
and
dear
enough
to
their
day
jobs
to
their
livelihoods
to
their
interests
to
their
needs
that
it's
worth
their
time
and
they
you
know
they're
coming
in
you
know
respectfully,
but
with
guns
blazing
saying
hey,
you
know
this
is
what
I
think
this
is
what
I'd
like
to
see
happen
here
and
if
that
happens,
we're
gonna
be
in
great
shape.
A
E
Sure,
thank
you.
Thank
you,
john.
So
this
track
is
about
enabling
or
getting
baseline
ready
for
mass
adoption,
and
one
of
the
key
things
here
is
to
drive
down.
No,
that's
not
the
notes.
John
sorry.
Oh.
E
No,
actually,
I
I
think
we're
no,
the
notes,
as
I
think
the
is
right.
Thank
you.
Sorry.
I
was
confused
there
for
it
for,
for
a
second
and
the
the
the
key
thing
here
is
to
drive
down
transaction
cost,
primarily
because
you
know
five
bucks,
a
transaction-
if
you,
if
you
have
you
know
100
000
of
them
is
is,
is
is
not
a
good
value
prop.
E
So
the
the
key
here
is
to
to
to
ensure
that
we
can
drive
down
transaction
costs
and
make
sure
that
we
can
have.
You
know:
100
000,
a
million
two
million
businesses
transact
via
the
baseline
baseline
protocol,
because
it
is
the
least
invasive
invasive.
With
regard
to
internal
I.t
infrastructure,
the
least
invasive
methods
to
use
distributed,
ledger
technology.
So
what
we
are
focusing
on
is
a
set
of
in
order
to
do
that.
E
We're
focusing
on
on
like
three
key
questions
that
we
need
to
answer
and
they
are
they're
outlined
in
the
notes.
John.
If
you
want
to
scroll
down
a
little
bit.
A
E
E
A
E
E
Yes,
yes,
yes,
yes,
those
are
the
those
are
the
instructions.
Actually.
Thank
you.
That's
that's
the
right
one
I
was.
I
was
like
I
updated
that
so
this
is.
This
is
what
what
people
will
we'll
we'll
see
if
you
actually
can
scroll
up
a
little
bit?
Sorry
about
that,
if
you
can
scroll
up
further?
Yes,
yes,
yes,
yes,
so
you
can
you
you,
you
see
the
the
you
can
see
the
timeline
and
then
scroll
down
a
little
bit.
Sorry,
when
we're
gonna
gonna
tackle
those
those
those
questions.
E
They're
gonna
be
a
follow-up
session
on
on
on
friday,
if
we,
if
we
run
into
in
if
we
need
more
time-
and
there
are
stop,
thank
you
that
we
have
a
clear
goals,
no
goals
and
deliverables.
If
you
can.
A
E
Back
up
that
we
that
we
want
to
want
to
achieve.
No,
that's
a
stretch
goal.
Thank
you.
So
we
want
to.
We
want
to
clearly
get
a
scaling
approach,
selection,
evaluation
criteria,
so
we
don't
want
to
say
this
is
the
this
is
the
right
solution.
What
we
want
to
give
people
and
implementers
on
hand
is
these
are
the
criteria
you
should.
E
You
should
consider
when
you're,
when
you
are
either
developing
a
solution
or
when
you're
selecting
a
solution,
and
that
is
also
what
is
the
type
of
of
stack
architecture
and
then
what's
the
smart
contract
architecture
that
supports
a
scaling
solution,
and
out
of
that,
we
want
to
create
a
a
hackathon
use
case
description,
utilizing
the
frameworks
and
and
extensions
and
update
and
as
a
stretch
goal.
E
If
we
get
if
we
get,
there
is
to
talk
about
fully
private
transaction
approach
and
and
and
architecture
which
fully
private
means
fully
private
plus
audit
backdoor.
A
Andreas
can
I
can
I
cut
you
off
there
just
to
just
to
be
mindful
of
time.
This
is
obviously
going
to
be
a
a
major
track.
It's
got
a
lot
of
packed
into
it
from
zero
knowledge
to
batching,
to
l2s
and
all
such
related
things,
and
let
me
can
I
can
I
add
if,
if
you
reached
a
stopping
point
or
would
you
like
to
finish.
E
No,
this
is
this
is
really
this
is
really
so
so
anybody
who's
who's
who's
interested
go
through
the
instructions.
Everything
everything's
there
by
tomorrow,
there'll
also
be
sort
of
like
the
the
actual
operating
starting
point
in
there,
where
we,
where
we
start
from
a
from
a
from
a
high-level
architecture,
point
of
view,
as
well
as
from
from
from
a
mind,
mapping
point
of
view
to
address
those
three
questions.
A
So
I'd
like
to
again,
as
evan
pointed
out
earlier,
there's
a
slack
channel
on
this.
All
of
the
slack
channels
are
the
are
predicated
on.
A
E
Yes,
so
the
the
the
the
if
you're,
if
you're
in,
if
you're
in
the
the
baseline
slack
it's
there
are
public
channels.
They
all
start
with
the
same
mnemonic.
It's
bps,
2020.
E
so
and
you'll
find
all
the
tracks
there
from.
I
did
from
the
phone
book
to
scaling
to
the
product
cookbook
to
the
core
interfaces,
et
cetera.
So
if
you're,
if
you're,
if
you
just
click
on
on
on
on
channels
and
search,
they
will,
if
you
put
in
bps2020,.
A
Also,
here's
the
hashtag
for
just
as
I'm
thinking
about
it,
2020.
A
Yes,
so
if
you
want,
if
folks
want
to
be
tweeting
about
this,
please
do
and
the
other
thing
I'd
like
to
bring
up
right
here
is
tomorrow
morning
at
10,
all
the
hopefully
all
of
the
sort
of
ringleaders
of
these
different
tracks
will
be
reporting
out
on
kind
of
head
counts,
who's
showing
up
who
are
their
core
maven
groups.
I'll
give
a
good
example.
Kirk
here
andreas
brought
up
a
pretty
interesting
point
about
l2s.
A
We
don't
have
time
to
discuss
it
on
this
call,
which
is
exactly
the
point
of
the
summit
and
the
summit.
We
have
time
for
you
guys
to
argue
about
that,
for
as
many
hours
as
you
like
and
and
we'll
have
fun
watching
that
happen
so
sounds
like
kirk
is
somebody
you
would
want
to
reach
out
to
to
see.
If
they
can,
you
know
if
they're
going
to
be
sort
of
in
the
core
maven
group
of
that
particular
subject,
join.
E
The
any
anybody
who's
interested
should
join
the
the
the
the
the
slack
channel.
I
will
put
a
call
for
help
out
with
with
a
social
media
tweet
that
actually
went
out
yesterday
to
the
98
people
who
had
expressed
interest
in
the
in
the
scaling
workshop.
E
Whoever
will
show
up
is
is
welcome.
They
will
be
awesome
if
they
can,
because
then
we
can
dig
into
into
fully
private
transactions.
They
have
a
great
new
framework
called
noir
for
for
for
general
approver
prover
services
that
allow
scaling,
so
all
good
stuff
will
all
dig
in,
and
this
is
gonna
be
fun.
It's
gonna,
be
it's
gonna,
be
very,
very
interesting,
very
technical
just
to
to
to
let
everybody
know.
E
A
Yeah,
a
a
10
billion
looks
like
the
possibly
a
number
did,
some
scratch.
Math
10
billion
a
day
would
be
effectively
some
within
a
zero
or
so
of
all
of
the
b2b
events
that
might
need
to
be
made
verifiably
consistent
in
the
world.
A
So
unless
I,
unless
my
math
is
really
really
wrong,
I'm
going
to
wait
for
andreas
to
do
to
check
that
map.
A
C
Yeah
yeah
yeah
sure,
yes
for
the
court.
The
core
interfaces
track
is
going
to
give
sort
of
an
introduction,
a
deeper
introduction
around
where
the
api
contracts,
messaging
persistence,
privacy
and
types
packages
live
in
the
core
under
the
core
top
level
core
protocol
repo
in
the
repo.
It's
also
going
to
show
sort
of
the
app
the
implementation.
The
initial
implementation
in
bri.
I
C
Each
one
of
those
packages,
and
so
they'll
be
like
sort
of
the
ability
to
see
how
it's,
how
they're
actually
used
and
how
you
could
implement
them
yourself.
You
know
in
the
real
world
application.
A
If
anybody
missed
that,
I
just
demonstrated
going
from
the
environment
to
the
repo
entry,
there
will
be
a
repo
entry.
A
master
epic
was
what
we
call
these
for
every
every
issue
or
for
every
breakout
and
the
notes
pad
by
the
way
people
should
think
of
as
a
scratch
pad
for
ideas.
You
know
you
should
people
should
be
very
comfortable
coming
in
there
and
getting
it
messy.
A
It's
fine,
because
really,
the
the
document
of
record
is
the
issue
in
the
github
repo,
by
the
way,
anybody
that
doesn't
have
and
needs
to
have
or
wants
to
have
the
ability
to
control,
or
you
know,
to
create
and
edit
and
or
assign
epics
and
issues
in
the
baseline
roadmap.
Repo.
A
Here,
please
reach
out
to
me
on
dm
jaywalpert
on
slackdm
dm
me
to
with
your
github
id,
and
I
will
add
you
to
the
ssc
list
that
allows
you
to
have
right
access
to
this.
You
can
still
go
in
and
make
comments.
You
just
can't
do
a
lot
more.
You
can't
assign
anything
you
can't
create
new
ones.
A
If
you
don't,
please
reach
out
to
me
so
yes,
and
by
the
way
kyle
can
I
know
that
you
guys
have
got
a
bunch
of
stuff
offline
for
these
major
topics
which
are
just
listed
in
here
message
formats
permit
persistent
ck
and
some
new
features.
A
A
So
there's
time
what
we've
done
here
in
the
in
this,
in
this
view,
nick
did
and
and
anais,
is
to
sort
of
heat
map
where
act,
action
might
be
occurring
and
what
we
will
do
by
the
time
of
the
summit
is
identify
real
kind
of
kickoff
times
where
people
really
are.
You
know
especially
going
to
be
on
alert
to
be
in
there.
So
you
see
this
green
item.
That
means
that
the
the
persistence
layer
for
core
interfaces
will
be
discussed
at
9
am
on
friday.
A
A
We
did
not
have
people
indicate
their
their
interest
in
attending
sessions
or
tracks
in
this
set
of
time,
basically
middle
of
the
night
us
or
europe,
and
so
that
was
mistake,
and
we
regret
that
mistake.
But
that's
why
we
don't
have
a
lot
in
here,
but
I
expect
that
there's
several
people
already
that
are
are
planning
on
lighting
up
that
time
frame
in
the
in
you
know
in
india
and
singapore
elsewhere,
so
apologies
again,
so
the
I
hope
that
makes
sense
pl.
This
would
be
a
good
time
for
a
question.
A
Right
so
so
yeah
kyle,
if
you
guys,
could
put
more
into
the
core
interface
docs
and
and
into
that
epic
by
tomorrow,
that'd
be
super
good.
C
Do
that
and
there's
some
slides
on
the
on
the
bri
one
tab
within
that?
That's
that
on
the
top
there.
C
So
there's
gonna,
be
some
there'll,
be
some
good
content
in
here
tomorrow,
as
well
for
each
one
of
the
topics
and
just
to
give
some
context
around
where
to
find
each
of
those
things
in
the
bri
one
example.
So
that'll
be
good
too.
A
Oh,
that's
sweet,
that's
perfect,
and
also,
if
I
can
suggest
you
guys
this
is.
This
is
a
great
example
of
an
opportunity
for
the
maintainer
team,
in
particular
to
start
linking
up
this
master
epic
right
with
additional
issues
that
may
come
from
the
from
the
baseline
repo,
and
so
you
could
be
creating
those
issues.
A
Yeah
and
I'll
so
that
that'd
be
a
great
thing
for
you
guys
to
make
as
an
activity
as
yeah,
effectively
yeah
issue
grooming
and
getting
that
together,
and
I'm
going
to
use
that
moment
to
this
moment
to
pivot,
to
a
different
car
point,
which
is
the
baseline
hackathon
december
2020..
A
We
have
funded
it.
I
think,
as
people
know,
I'm
officially
asking
now,
if
any
company
or
per
individual
wishes
to
sponsor
or
not
sponsor
but
fund
a
a
a
challenge
in
in
the
form
of
a
bounty.
A
So
we
have
funded
quite
a
large
number
already
so
that
nobody
has
to
worry
about
the
the
hackathon
not
being
funded
with
the
overheads
required
and
with
a
certainly
a
minimum
number
of
of
bounties
in
december,
but
so
so,
for
example,
the
the
project
or
the
the
core.
You
could
create
an
issue
add
it
here
which
is
fairly
straightforward
and
then
people
as
they
join.
I
see
I'm
not
logged
in,
so
I
probably
don't
have
much
more
access
than
this
right
now.
A
I
won't
waste
your
time,
but
you
can
then
go
in
and
create
a
connect
that
issue
and
bounty
it
and
we
will
be
selecting
you
know
at
least
six
seven,
eight
bounties,
the
that
we've
got
covered
and
then
you
you're
welcome
to
do
more.
So
any
of
the
companies
here
you
could
say,
hey.
You
know
I'll
bounty,
this
issue
on
my
platform.
A
That
would
be
a
perfectly
legitimate
thing
to
do
now.
Let's
see
what
we
can
run
up,
but
it
will
be
well
funded
regardless.
So
there's
no
pressure
here,
but
if
you've,
if
you
guys
have-
and
anybody
has
budget
for
that-
terrific,
hey
connor
thanks
for
the
time
we'll
see
con
connor,
you've
already
dropped,
haven't.
A
A
Looking
at
comments
seeing
if
there's
any
there
dominic,
let
me
pivot
back
to
you
on
this.
So
if
we
can
go
back
to
the
product,
cookbook
I'd
I'd
like
to
to
point
out,
if
anybody
didn't
know
that
dominic
style
and
and
his
team
released
a
pretty
awesome
demo
and
release
dominique
are
you?
Are
you
there.
A
I
I
Excellent,
so
yeah.
What
we
wanted
to
talk
about
during
the
session
is
some
of
the
ways
that
we're
thinking
about
baselining
at
the
system
of
engagement
layer-
and
I
think
one
of
the
things
that
we
wanted
to
do
was
during
the
session
at
least
highlight
some
of
the
ways
we
did
that
on
top
of
salesforce
through
the
release
that
we
did,
and
these
include
kind
of
more
no
code
process,
builder
ways
of
doing
things
so
kind
of
declaratively,
saying
like
if
this
record
meets
these
conditions,
whether
it's
a
checkbox
or
a
certain
value.
I
You
know
we
would
like
to
then
have
this
record
call
out
to
the
main
net
and
baseline,
and
so
I
think
what
we
like
to
do
in
the
in
the
cookbook
is
essentially
talk
to
some
of
the
ways
that
we
did
this
on
the
salesforce
platform.
But
in
addition
to
that,
how
you
can
do
this
kind
of
repeatable
repeatable
ways
to
essentially
baseline
at
the
system
of
engagement
layer,
different
application
uis?
So
that's
what
you
know.
What
we'll
add
our
part
in
this
session
as
well.
H
Hey
dom
that
sounds
really
awesome
thanks
so
much
for
talking
about
it.
I
think
you're
in
our
channel
now
so
I'll
just
message
you
yeah,
but
we
would
love
to
have
that.
I
H
A
Right
on
I'm
gonna
we'll
we'll
break
our
regularly
scheduled
programming
here,
real
quick
to
make
sure
we
get
time
for
anais
to
talk
about
standards.
We've
made
some
great
strides,
there's
and
also
on
ace.
I
think
you're
going
to
bring
up
the
question
of
the
of
the
tokenization
session,
so
yeah
I'll
we'll
skip
to
that.
One.
F
So
in
the
tokenization
and
digital
assets
track
we'll
be
mostly
working
on
how
to
convert
a
baseline
option
record
into
a
on-chain
asset
and
the
interactions
between
the
option
record
and
that
asset.
So
the
key
objective
of
the
track
is
really
to
discuss
the
requirements
for
the
option
record,
the
on-chain
asset
and
the
tokenization
project
process
itself.
F
So
for
the
option
record
requirement
in
the
context
of
baseline,
we
will
ask
and
explore
if
we
can
generalize
and
specify
a
set
of
required
field
needed
for
the
tokenization
process.
So
really
our
first
expected
outcome
here
is
a
data
model
or,
I
should
say
part
of
the
data
model
for
generic
baseline
record
ready
for
tokenization,
but
we
will
also
address
metadata
authorization
permission
on
that
record
as
well.
F
For
instance,
if
there
are
any
parameters
to
provide
access
to
the
option,
asset
or
option
record
to
the
token
owner.
So
those
are
the
questions
that
we
will
explore
on
the
ancient
asset
requirements
side.
We
will
really
focus
on
what
are
the
appropriate
token
standards
that
we
could
look
at
for
possible
implementation
and
what
are
the
privacy
requirements
in
terms
of
token
ownership?
Privacy
asset
attribute
privacy,
etc.
F
On
the
token
process,
it's
a
tokenization
process
itself.
We
will
really
focus
mostly
on
token
deployment.
So
what
are
the
steps?
The
technical
options
for
implementations
so
how
to
really
ensure
secure
tokenization
of
baselines
record,
so
the
expected
output
for
the
track
are
the
data
model,
the
methods
and
really
implementation
level,
architecture
diagram
for
example?
F
A
Thanks
honeys,
and
would
you
like
to
talk
about
the
standards
as
well.
F
Yes
sure
so,
two
weeks
ago,
I
don't
know
if
you
remember,
but
we
had
reached
a
milestone
by
completing
the
review
of
the
component
and
the
high
level
requirement
of
the
protocol.
And
last
week
we
actually
started
the
work
on
the
api
and
data
model
specification.
F
F
So
now
I
would
say
that
we
are
in
a
very
good
position
to
start
formulating
detailed
requirement
for
both
core
and
api
specifications,
and
I
think,
during
the
summit,
there
will
probably
be
very
good
input
into
what
we
should
include
or
what
we
should
explore
or
review
at
the
on
the
standard
and
specification
site.
So
I'm
really
looking
forward
to
it.
So
some
detail
requirement
will
be
more
straightforward
than
others
so
next
week
I
think
we
will
probably
start
addressing
those.
F
However,
I'm
aware
that
there
is
a
lot
of
work
happening
on
bigger
items
in
parallel,
so
if
you
are
interested
in
the
standard
and
specification
works
and
joining
us,
it's
twice
well
once
every
two
weeks,
two
weeks,
sorry
and
so
feel
free
to
reach
out
to
me
on
on
slack,
and
we
can
take
it
from
there,
because
there
are
a
lot
of
people
on
the
course
that
are
not
part
of
the
standard
and
specification
call.
So
I'm
making
a
call
here
if
you
are
interested,
please
don't
hesitate.
A
Yes-
and
you
should
be
any
anyone-
that's
interested.
It
should
be
aware
that
this
is
the
one
thing
that
we
do
restrict
access
to,
and
so,
if
anyone
can
be
involved
in
standards
of
specifications
work
and
be
in
the
meetings
that
that
go
over,
that
every
two
weeks,
that
anais
organizes,
which
we're
very
grateful
for,
but
it
to
get
an
invite
to
that.
You
have
to
have
sign
the
icla
or
the
ecla.
A
The
ecla
is
the
company
wide
cla.
Then
you
also,
it
was
an
individual
icla
or,
if
you're,
just
an
individual,
just
an
icla
and
those
are
all
yeah.
You
actually
automatically
do
that
when
you
try
to
submit
a
pull
request
to
the
master
branch
or
the
main
branch
of
of
the
repo
github
repo.
So
if
you
do
that,
then
you
can
get
into
that
team
and
and
work
on
standards
and
specifications.
A
You
can
also
sign
the
icla
manually
without
doing
a
pull
request.
Just
so
you
know.
A
Terrific-
and
I
will
say
that
in
case
we
didn't
mention
it
before
the
we
have.
Finally,
at
long
last
solved
the
documentation
system
problem
that
we
were
having.
A
I
won't
go
into
the
details
of
that,
but
now,
if
you
want
to
work
on
the
documentation
which
I'm
showing
here
on
the
screen,
you
can
do
this
and
all
you
need
to
do
is
go
into
the
specification
or
the
docs
folder
which,
by
the
way
the
specifications
folder
is
in-
and
you
can
change
any
dock
in
here
and
submit
it
to
submit
a
pull
request
to
to
the
main
branch
when
that
pull
request
is
accepted
by
three
maintainers
on
a
yeast
being
one
of
them
now
and
and
maintainers
for
specifications
are
allowed
in
the
maintainers
group,
not
just
code
maintainers,
but
also
specifications
maintainers
same
group.
A
Three
people
will
approve
it
and,
and
then
that
will
show
up
here,
the
change
will
show
up
on
the
website
automatically.
A
A
C
A
So
you
can,
you
know,
literally,
can
create
a
new
specifications
header
here
on
the
left,
and
these
and
the
dot
md
files
will
show
up
on
the
right,
as
you
specify
them.
So
just
a
quick
primer
on
that
any.
A
All
right
we're
getting
close
to
the
end
here
we
didn't
get
through
all
of
the.
A
Sessions,
let's
see
what
what's
left
here,
got
tokenization
got
blockchain
client
support,
so
I'll
just
read
off
what
what
connor
brought
up?
If
you,
if
you
look
in
the
notes
in
the
chat,
you'll
see
the
the
roadmap
number
roadmap.
Epic
number
143
is
where
you'll
find
details
about
about
the
client
support
effectively
how
ethereum
clients
like
like
excuse
me
excuse
me
like
nethermine
like
quorum
like
besu
and
others
can
be
improved
or
added
to
or
add
things
onto
to
support,
baselining.
A
A
You
should
have
credentials
for
kiko
chat
for
the
for
the
summit
already
and
if
you
don't
reach
out
to
nick
kritikos
and
we
are
always
putting
out
more
credentials
as
people
sign
up
the
you
know,
if
you're
a
company-
and
I
see
splunks
on
here-
I
see
accenture's
on
here-
I
see
so
many
companies
that
are
that
are
that
have
services
and
and
technology
and
and
other
things
to
feature
in
the
baseline
community
for
their
to
achieve
their
objectives
and
their
commercial
objectives.
A
There's
nothing
wrong
with
getting
in
here
and
creating
another
breakout
on
the
fly
during
the
summit
and
saying
oh
well,
how
would
you
know,
let's,
let's
create
a
an
issue
that
we
can
bounty
about,
how
you'd
use
yeah
intuit
in
something
or
google
in
something
or
chain
link
in
something
or
unibride
in
something?
Or
how
would
you
know
solutions
providers
like
accenture,
you
know
you
could
create
a
bounty
on
that
say.
You
know,
create
a
new
solution
idea
that
would
involve
accenture.
A
A
I
think
that
is
it
I'll
I'll
just
pause
for
a
few
seconds
to
or
a
minute
to
see
if
there's
anything
left
sam
bacha
did
you
want
to
talk
very
briefly
about
about?
What's
coming
for
edi.
B
Yeah
I
appreciate
it
john,
so
we
now
are
actually
able
to
generate
the
specific
data
types
required
for
for
contracts
to
accept
edi
transactions.
B
Also,
I
have
compiled
a
library
of
every
edi
transaction
set,
I
think
available,
so
that
that
includes,
like
medical
images
x,
400
transaction
sets
for
like
governmental
edi
transactions.
It's
it's
pretty
exhaustive.
B
So
if
anyone
has
any
questions
on
a
transaction
set
that
they
don't
see
or
is
not
available,
let
me
know,
and
then
we
should
have
actually
some
some
actual
interfaces
for
like
the
most
basic
edi
transactions,
which
are
like
acknowledgments.
B
That
will
definitely
be
like
a
first-class
priority
for
for
for
usage
and
then
also
we
we're
working
on
integrating
the
registry
contracts
that
are
in
the
baseline
repo
to
to
actually
interface
with
the
with
trading
channels
for
for
edi
transaction
sets,
so
hopefully
we'll
be
able
to
leverage
the
phone
book
for
the
registry
for
communicating
with
edi
partners.
So
that's
that's
a
that's
a
goal
for
like
the
first,
like
actual
use
case
for
for
baselining,
so.
A
Really
excited
to
just
to
to
be
seeing
the
the
drop
of
that
code
been
looking
forward
to
edi
work.
I
think,
like
oracle's
edi
is
going
to
be
extremely
extremely
relevant
and
important
to
baselining
writ
large
going
forward.
So
it's
it's
really
great
to
see
that
you
guys
are
pioneering
that
work
and
generalizing
it.
So
that's
not
just
about
one
platform
or
another,
but
for
everybody.
A
So
looking
forward
to
seeing
that
work
drop
in
the
coming
weeks,.
B
I'll
put
a
a
message
in
the
edi
channel
with
all
the
the
work
that's
published
right
now,
some
of
it's
not
exactly
production
ready,
but
it's
a
good
first
cut.
So
so
yeah.
A
A
All
right
we
got
through
it
all
see
everybody
at
the
summit
and
thanks
for
the
time
today,
it's
gonna
be
a
big
week
and
a
big
couple
of
months
for
baseline
and
for
ethereum
in
general,
of
course,
and
for
all
sorts
of
blockchain
stuff
see
you
soon.
Bye-Bye.