►
From YouTube: Baseline TSC Meeting 30March 2020
Description
Baseline-Protocol.org
The Baseline Protocol is an open source initiative that combines advances in cryptography, messaging, and blockchain to deliver secure and private business processes at low cost via the public Ethereum Mainnet. The protocol will enable confidential and complex collaboration between enterprises without leaving any sensitive data on-chain.
Official Press Release https://consensys.net/blog/press-release/ey-and-consensys-announce-formation-of-baseline-protocol-initiative-to-make-ethereum-mainnet-safe-and-effective-for-enterprises/
Twitter https://twitter.com/baselineproto
Baseline Protocol Documentation https://docs.baseline-protocol.org/
Github https://github.com/ethereum-oasis/baseline
A
According
to
this
cloud,
now
everybody
welcome
to
the
second
TSC
me
for
the
baseline
protocol
community.
It
looks
like
we
have
a
couple
of
one
guests:
one
guest
who's,
an
L,
Nate
right,
a
mate.
We
got
in
the
crÃticos
as
a
guest
and
we
shall
proceed
so
I.
We
did
introductions
last
week
and,
as
you
probably
have
seen,
we
have
posted
the
TFC
and
the
SSC
meeting
to
zoom
we're
grace
by
the
grace
of
God.
We
can
hit
2x
speed
and
zip
through
it.
A
Thank,
You,
Tube,
Ryan,
Chamberlain
and
Karthik
solo
program,
who
are
both
on
the
call
for
in
advance
for
having
worked
so
hard
on
getting
our
maintainer
rules
and
practices
started.
We
have
a
ways
to
go
still,
but
they
should
be
thanked
for
the
work
that
they
did
on
that
I'm
going
to
share
my
screen
and
get
all
over
to.
A
If
people
make
good
work
good
time
on
it,
where
we
will,
where
we
can
use
chat
to
to
chunk
out
some
some
brainstorming
without
blocking
each
other
on
conversation,
and
we
have
an
incentive
program,
conversation
to
work
out
and
then
we
needed
to
decide
the
next
meeting.
Does
anybody
else
have
a
an
agenda
item
that
we
should
add.
C
A
D
A
C
D
What
for
infrastructure
related
to
the
project
and
specifically
the
next
kind
of
big
chunk
of
work?
We
want
to
get
to
help
important
stability
of
baseline
as
a
continuous
integration
server.
So
we
couldn't
run
that
for
every
pull
request
that
is
going
against
manner
to
make
sure
we're
running
all
the
tests
and
all
that
fun
stuff
in
the
walls
open
and
potentially
it's
an
automatic
style,
limping
kind
of
thing.
D
She
was
a
little
bit
of
two
primary
check
check
points
that
are
required
for
every
PR,
in
addition
to
the
standard
like
three
approvals
from
donors
list.
So
the
question
is
around
the
CI
system.
If
any
Maggiore
about
the
process
for
getting
something
like
that,
meaning
is
a
the
TSC.
Would
we
all
should
or
pick
or
approve
what
type
of
system
we
use
like?
This
is
a
hosted
system,
so
we
don't
have
to
do
it
ourselves,
so
something
like
Travis
or
circle
CI
and
there's
one
to
flow
to
the
TSE.
D
B
B
A
D
D
B
A
D
I
guess
from
the
TFC:
is
there
anything?
Procedurally
we
need.
My
understanding
was
I.
Think
if
we're
gonna
use
a
hosted
service
that
requires
resources,
then
we
get
them
donated
or
somehow,
because
you
know
we
do
have
very
pretty
extensive
test
suite.
It
requires
quite
a
bit
of
resources
which
cost
money.
So
you
know
that's
kind
of
good
once
we
set
it
up
like
was
gonna
pay
for
it,
so
we're
looking
at
services
that
could
provide
free
or
some
amount
of
free
to
open
source
projects.
D
D
E
D
A
A
Right,
good
I'll
leave
this
to
you,
guys
that
and
and
we'll
move
on,
shall
we
let's
put
put
this
as
seeing
where
I
put
that
yeah
put
this
as
a
say
nominally
vine
by
this
time
next
week.
Do
you
think,
is
that
a
good
time
frame
for
a
gang
CIO
or
do
you
do
you
think
we
can
what's
it's
a
critical
path
for
that.
D
D
A
I'll
say
that
again
it's
a
delight
to
work
with
Oasis.
They
have
the
ability
to
get
some
stuff.
They've
never
had
a
problem
getting
this
stuff,
they
get
it
for
free
when
it's
possible
and
they
they
do
have
some
kind
of
a
budget
for
something
I
think,
but
bottom
line
is
I.
Think
you're
working
with
Jory
will
make
short
work
of
that
and
and
you're
correct
about
the
issue
right
until
we
do
some
fundraising,
which
won't
happen
until
a
little
bit
later.
Certainly
you
know
the
April
May
time
May
June
July
timeframe.
A
I
should
say
that
we
will.
We
don't
have
any
real
funds
in
community
to
to
manage.
I
will
say
that
this
was
a
topic
for
a
little
bit
later.
We
will
want
to
start
Tim.
Tim
cupping
for
I
will
start
I
will
putting
together
a
presentation
on
what
sponsorship
would
look
like
past
May
31st,
and
it
does
turn
out
that
Oasis
has
a
wonderful
facility
for
as
a
nonprofit
handling,
basically
community
funds
that
are
designated
for
community
things.
So
we
have
a
facility
for
doing
that.
A
We
don't
have
like
to
set
up
a
trust
fund
or
something
to
handle
it
and
deal
with
governance.
Oasis
handles
all
that,
so
we
can
create
dues
and
membership,
and
you
know
the
spot.
Yeah
there's
a
correspond,
sir
ship
for
Oasis
projects
that
we're
gonna
want
to
consider
after
May
31st,
when
the
money
for
the
current
project
runs
out,
we're
talking
to
Microsoft
or
Lubin,
and
some
other
folks
about
that.
A
Joe,
eea
and
EF
currently
fund
the
project
that
is
housing
us
until
the
end
of
May
they
may
or
may
not
read,
even
if
they
do
REO
yeah
by
May
31st
we
may
want
to.
In
fact
we
certainly
do
want
to
once
we
determine
this
is
mission
critical
for
lots
of
companies
to
say,
hey
lots
of
companies.
You
should
be
so
you
know
card
you
should
be
in
here.
It's
not
a
lot
of
money.
A
It's
like
15k!
If
you've
got
2,000
people
its
25k
for
anything
above
that
and
it's
it
goes
down
to
pretty
low
numbers
and
then,
of
course,
you
don't
have
to
pay
anything
at
all
to
still
be
a
contributor
and
to
be
involved.
So
it's
pretty
pretty
nice,
but
we
can
also
pay
more
than
that
we
can.
We
can.
We
can
raise
more
money
than
the
Corps
dues
and
and
have
Oasis
manage
it
for
specific
things
like
hackathons
and
I'm,
getting
ahead
of
myself.
That
was
not
the
next
thing
on
the
agenda.
C
C
A
Fact,
Hudson
I
will
fix
that.
Okay,
cool
you've
got
lots
of
other
things
and
I
know
you
want
to
do
and
I've
been
I
seem
to
have
the
easiest
time.
Changing
docks
right
now.
Brian
and
I
are
working
in
karthika
and
I
are
working
on
merging
docks
the
docks
branch
into
McMaster
flipping
the
docks
system
over
to
master,
and
once
we
do
that,
then
anybody
can
merge
them
or
it
can
just
change
an
MD
and
it
will
get
into
docks
once
it's
approved,
but
until
until
we
do
that
it's
a
bit
hinky.
So
right.
D
A
A
A
And
hub
I
thought
I
I.
Think
I
was
walled
into
a
false
sense
of
confidence
on
that
I
thought
that
I
saw
I
thought
I'd
tested
this
with
a
browser
that
didn't
have
Zen
hub,
installed
and
and
and
I
still
saw
it
and
I
was
like
aha,
oh
great,
it's
it's
in
there
for
everybody,
but
apparently
not
yeah.
You
can.
A
D
A
A
B
D
A
Yep
agreed
so
so
then
we
have.
What
do
maintain
errs?
Do
I
thought
was
good.
Who
are
the
current
maintain
errs?
I
am
a
maintainer
in
just
functional
capability,
only
I
won't
be
doing
any
code
merges,
but
I
think
I
do
have
the
ability
to
do
it.
So
that's
why
I'm
there
and
I
and
I
will
do
docks,
merges
how
to
become
a
maintainer
I.
Think,
that's
a
that's
a
really
interesting
question
for
everyone.
A
I've
been
wanting
to
come
up
with
some
kind
of
a
forgive
the
anachronism,
but
you
know
some
kind
of
a
merit
badge
system.
You
know
for
the
whole
community
to
say:
hey,
you
know
this
is
the
you
know.
Do
this
and
you
know
you
get
this
merit
badge
and
the
community
will
trust
you
with
this
sort
of
thing.
A
G
I
mean
I
think
for
us
anyway,
when
it
comes
to
maintain,
as
the
I
think.
One
of
the
most
important
things
is
to
see
persistence
over
time,
because
always
the
risk.
You
know
to
a
lot
of
the
time
with
with
the
open
source.
Anyway,
what
you
see
is
you
know,
people
come
involved,
come
on
to
the
project.
I'll
start
scratching
around.
You
know
they
might
submit
some
really
good.
Pull
requests
make
some
great
contributions,
but
then
you
know
over
time
they
kind
of
vanish
and
and
no
longer
sort
of
in
the
picture.
G
So
I
think
that
that
would
be
one
of
the
key
thing.
You
know
you
want
people
who
are
actually
going
to
be
committed.
It's
not
that
it's
like
a
passing
phase,
because
you
know
they're
they're
having
their
interest
in
finding
out
about
baseline
they're,
trying
to
run
the
example,
found
scenarios
to
make
improvements,
and
then
you
know,
then
they
go
on
to
the
next
thing.
G
So
that
would
be
the
biggest
one
to
me
in
terms
of
actually
having
some
sort
of
you
know,
metrics
that
you
can
track
I
mean
you
know,
I
find
with
open
source.
Like
you
know,
it's
it's
pretty
easy
to
spot
the
people
who
are
having
an
impact
because
you'll
see
you
know
the
names
will
pop
up
again
and
again
or
they'll.
Be
you
know,
multiple
pull,
requests
against
for
the
names
or
multiple
comments,
and
so.
A
A
One
of
one
of
the
things
that
we
were,
we
we
didn't
get
done
in
a
consensus,
but
I
really
wanted
to
do
is.
Was
this
notion
of
I
think
we
wrote
about?
It
called
something
called
a
pie
where
we
had
a
kind
of
a
slack
tool
that
allowed
people
to
you
know
basically
award
each
other
points,
and
the
crazy
idea
was
that
the
points
would
be
actually
a
share,
a
non-transferable
interest
in
a
trust.
So
you
know
you
could
you
could
fund
a
trust
fund?
A
And
if
you
had
ten
points-
and
there
were
a
hundred
points,
then
you
had
1/10-
you
had
a
you
know,
basically
a
bear
right
to
1/10
of
the
trust,
but
you
know
you
could
you
could
it
could
be
other
kind
of
goodness?
So
you
could
say
you
know
on
a
sprint.
I
did
this
work
and
I
deserve
10
points,
and
somebody
could
say
you
know
you
only
deserve
to
another
et
cetera
you,
whatever
you,
whatever
the
average.
A
Is
you
get
those
points
you
could
also
do
that
for
for
kind
of
a
Net,
Promoter
Score
for
people,
you
say:
hey
I'm,
dealing
with
this
guy
and
he's
not
responsive
I'm
gonna
bring
his
rating
down,
but
I
only
say
that
as
a
as
a
directional
thing,
obviously
I
don't
think
we
should.
We
have
that
we
don't
have
the
bandwidth
to
build
that,
but
if
it,
if
it
inspires
anybody
to
think
of
ways
to
create
a
kind
of
data-driven
regime
for
some
of
these
things
that
be.
C
I
thought
of
one
more
maintainer
thing
self-motivated
and
then,
in
response
to
what
you
just
said,
I
think
it'd
be
really
cool
if
we
built
something
that
was
based
that
was
built
on
baseline.
That
was
for
contributors
of
this
repository,
like
you
said,
that's
like
an
incentive
point
system
so
that
it
hooks
into
the
name
net
and
whenever
a
pull
request
is
merged
using
an
Oracle,
the
stats
are
updated
on
main
net
and
point
values
are
assigned
based
on
discussion
with
the
TSC.
C
We're
not
going
to
do
that
any
time
soon,
but
I
thought
that
was
a
that'd,
be
a
cool
thing
to
do,
because
I
think
that'd
be
like
using
baseline
and
showing
off
the
chain,
link,
Oracle
solution
within
baseline
and
then
a
couple
about
the
other
tools
that
would
be
needed
to
make.
That
kind
of
point
system.
A
Right
on
right,
yeah,
it's
it's
a
it's
a
forever
dream
of
mine
that
we
get
to
something
like
that.
One
of
these
days,
I'll
start
an
organization
that
actually
does
it.
Okay.
Moving
on
to
where's
my
and
always
it's
it's
I,
don't
know
about
you
guys,
but
I
have
an
endless
battle
with
chrome,
tabs
and
windows
and
ok.
So
the
agenda
review
prospective
maintainer
candidates.
Okay,
so
Brian
do
you
have
any
other
anything?
A
D
Sort
of
talking
about
some
of
the
areas
that
are
challenging
its
how
to
pick
a
maintainer
out
of
the
group
of
people
who
contribute
and
what
it
means
to
be
a
good
maintainer
over
time,
and
then
you
know
the
other
aspect
of
it
is:
what
happens
if
someone
is
the
maintainer
and
they're
not
responding,
and
they
don't.
You
know,
I
pull
requests
and
they
kind
of
ghost.
How
long
do
we
go
before
we
remove
them
from
the
list
and
what's
the
process
for
that
harder
discussion
to
have
it
could.
A
D
We
I
wonder
if
we
have.
We
want
to
remove
any
kind
of
human
discussion.
It's
like
you
know,
just
a
good
idea,
but
some
kind
of
time-based
real
thing
where
it's
like
you
can
be
a
maintainer
for
six
months
or
a
year
or
whatever
your
your
term
is
and
then,
as
long
as
you're
continuing
to
have
pull
requests
and
be
active,
you
can
going
to
re-up
your
status,
but
if
you
don't,
then
just
get
removed
automatically
something
like
that
fail-safe
mechanism-
I
guess
it
also
implies.
The
idea
of
a
tenure
makes
sense,
remain
Tanner's
brand.
A
A
D
D
A
On
yeah
and
and
obviously
yes
for
the
the
next
to
at
least
the
next
to
maintain,
we
got
to
get
more
maintainer,
Zoar,
Brian
and
Karthik
in
the
team.
We're
gonna
go
crazy,
trying
to
deal
with
all
the
poor
requests
and
and
I
mean
we're
pretty
active
by
early
standards,
but
even
by
any
standard
we're
seeing
a
lot
of
stuff
come
in
Brian
Karthik
are
you?
Are
you
kind
of
treading
water?
Now
I
mean?
How
are
you
guys
handling
the
load.
D
It's
it's
a
good
amount,
I
think
at
this
point,
I
guess
going
back
to
the
CI
discussion,
that's
kind
of
why
I
have
some
issue
with
getting
that
or
wonderful
a
priority
in
the
near
terms,
because
Naruto
requests
as
technical
requires,
checking
out
the
branch
into
the
test
so
run.
These
are
things
that
a
computer
can
do
without
me
babysitting
the
process.
D
A
A
A
Of
the
people
that
we
are
that
we
currently
have
approve
that's
a
lot.
So
would
anyone
like
to
move
to
bring
it
down
to
two,
and
what
are
the
counter
arguments
to
that?
I
would
I'm
offering
that
as
a
prompting
for
that,
if
anybody
thinks
that
we
ought
to
bring
it
down
to
two
for
the
short
term,
they.
B
A
A
D
A
E
I
think
three
does
make
sense.
I
think
the
main
thing
we
were
looking
for
at
his
diversity
in
terms
of
maintenance,
aside
from
the
grimy
Sam
and
Patrick,
were
a
little
cold.
What
right
now
as
part
of
the
maintenance,
I
think
generally
in
terms
of
pull
requests?
I
do
agree
with
having
three,
but
one
of
the
more
things.
I
would
one
things
out
that
compasses
is
probably
having
more
number
of
maintenance
when
there
is
no
diversity
in
terms
of
being
the
code
as
well,
then
who's
able
to
merge
the
code
to
master.
A
You
know,
obviously,
if
you
start
getting
behind
on
on
those
merges,
and
let
us
know
it
is
you
know.
Definitely
the
chatter
is
good,
so
I
mean
don't
don't
just
grin
and
bear
it.
Let
people
know
if
you're
getting
behind
okay.
So
if
that's
I
think
that's
the
maintainer
some
conversation
for
this
week,
we
have
some
actions
we're
going
to
deal
with
the
CI
by
next
week,
we're
gonna.
A
We
are
going
to
have
two
more
maintain
areas
and
that's
that's
the
next
thing
to
come
to
talk
about
with
who
are
those
two
other
maintainer
z--
by
the
way,
Johan
yeah
I'd
love
to
hear
I.
Think
we
all
love
to
hear
more
from
chain-linked.
You've
done
a
lot
of
this
stuff
and
you
have
a
community.
So
if
there
are
some
best
practices
from
chain-linked
that'd
be
great
to
hear.
A
A
A
A
Right
I
think
we
discussed
on
the
last
call
that
you
know
one
does
not
need
to
be
a
master
at
one
particular
subject,
but
it
is
nice
to
have
maintain
errs
who
are
masters
at
some
subject,
and
then
you
can
also
check
in
things
that
are
you
know
and
approve
things
that
are
not
in
your
set
set.
If
you,
if
you
you,
if
you
want
to
go
to
the
masters
of
that
subject,
right
well,
yeah,
it's
working
really
poorly
said
by
made
by
me
just
now,
but
I
think
yes,
yeah.
C
I
want
to
nominate
myself
as
a
like
a
Prentice
maintainer,
so
I
don't
want
to
be
a
full
maintainer
just
because
I've
not
I've
been
so
ingrained
in
non-text
for
a
number
of
years.
Since
I
worked
in
a
bank
doing
mainframe
without
github,
using
some
crappy
IBM
tool
that
yeah
I
I
need
to
get
more
acclimated
to
this.
A
A
B
B
A
A
F
Basically,
for
me,
it's
about
sorting
out
how
my
how
my
and
our
commitment
would
be
sorted
out
best
and
I.
Think
I
just
need
perhaps
until
the
next
DNC
meeting,
because
we
also
have
these
hackathons
going
on
and
we
try
to
contribute
at
the
same
time.
So
please
have
understanding
that
I
need
some
days
to
work
out
the
best
that
the
role
where
I
could
be
the
best
for
them
for
the
project.
I
wanted.
A
B
B
A
A
A
Right,
I
think
that's
eight,
so
we
have
three
new
maintain
errs
Karthik,
you
wanna!
You
want
to
take.
Do
the
honors
of
getting
these
guys
in
yep
I
could
do
it.
You'll
probably
want
to
reach
out,
given
that
this
is
a
public
meeting,
I
won't
put
I
guess:
I
already
did
put
github
identities
already
up
on
screen
there
yeah
so
Zach
husband,
Kyle.
A
Alright,
welcome
to
maintainer
group
guys
I'm
gonna,
move
on
I
think
we're
gonna
be
running
out
of
time
for
the
activity
I
was
hoping
to
do,
but
that's
that
will
be
okay.
We
can
do
it
another
time
and
I'm
trying
to
find
the
turn
screen
again.
Okay,
there
we
go
respective
maintainer
candidates
working
session,
we'll
skip
over
that
to
the
incentive
programs,
methods
and
practices.
There
is
a
hackathon
by
get
coin
and
at
the
beginning
of
June,
and
there
is
also
I
think
I
mentioned
earlier.
A
You
know
we
will
have
to
start
thinking
about
funding
stuff.
If
we
want
to
do
that,
I
mean
the
community.
Doesn't,
strictly
speaking,
doesn't
need
that,
but
it's
usually
good
to
have
a
you
know.
Some
kind
of
reasonable
warchest
for
things
and
a
way
of
distributing
incentive
opportunities,
get
coin
seems
to
be
the
way
to
do
it
nowadays.
A
B
Yeah
I
think
it
would
actually
make
quite
a
lot
of
sense
to
do
something
like
this
I
think,
with
the
current
market
conditions
to
like
being
able
to
participate
in
stuff
like
econ
grants-
and
you
know
hackathons
like
this
one-
it
makes
complete
sense
and
it
fits
well
with
the
current
conditions.
You
know,
I
think
it
would
be
very
well
perceived,
and
usually
a
lot
of
great
stuff
can
come
up
from
it.
So
that's
something
I
would
definitely
encourage
it.
A
Those
were
the
three
suggestions
they
had
I'm,
not
I'm,
not
gonna,
go
beyond
this
I.
Just
wanted
to.
This
was
a
kind
of
a
PSA
this
week.
I,
don't
think,
there's
anything.
We
have
to
decide
upon
right
now,
but
I'm
soliciting
input
regarding
that
over
the
next
week
and
we'll
we
can
decide
things
later
so
I'm
good.
B
A
Sponsorship
becomes
a
real
thing
that
we
can
do
and
we
might
be
able
to
build
a
pretty
good
war
chest
for
incentive
programs
and
other
things,
but
that's
for
another
day,
I'm
just
kind
of
getting
everybody
ready
for
that
conversation
when
it
becomes
a
relevant
thing
which
is
not
today
decide
next
meeting
in
time.
Let's
do
that.
Do
we
want
to
go
next
week
same
time
same
place,
or
do
we
want
to
go
to
two
weeks
at
this
point.
C
B
D
A
Awesome
all
right
we'll
do
that
now:
we've
got
nine
minutes
left,
let's
call
it
seven
minutes
or
five
and
we'll
give
ourselves
a
few
minutes
early
and
let's
talk
about
the
projects,
shall
we
is
there?
Yeah
I
think
we've
got
all
the
other
agenda
items
done,
rather
than
do
the
brainstorm
that
I
was
gonna,
propose
I'm
gonna,
just
take
you
guys
through
what
I
did
here
this
needs
a
day
and
over
the
weekend
to
see.
A
If,
if
you
have
some
comments
about
it,
this
is
heavily
to
do
with
the
SSC
and
in
fact,
but
also
here
for
the
TSC.
So
we've
got
the
cross
industry
use
case.
So
I've
just
created
a
bunch
of
projects
here
in
Zen
hub.
This
is
a
relative,
relatively
new
feature
in
Zen
hub
I
kind
of
like
it,
because
it
doesn't
clutter
up
the
the
actual
issues
and
you
know
they
get
the
github
set.
A
A
I
created
some
projects
and
for
all
of
them,
most
of
them
I
just
put
it.
You
know
from
now
till
June,
1
and
I,
just
I,
just
flipped
them
out
pretty
quickly.
So
there's
a
system
of
record
integration
tools.
You
know
Oracle
services,
you
know
so
I
think
that
there
some
spikes,
some
spike
epics
that
can
go
through
here.
A
A
D
A
F
John,
what
is
the
desired
level
if
I
may
ask
of
detail
that
you
want
to
achieve
here?
Is
it
more
about
the
scheduling
and
time
planning,
or
is
it
also
about
detailed
tasks?
For
example,
I
would
like
a
clear
to
distinguish
clearly
between
what,
for
example,
unit
bride
has
to
do
on
their
end,
because
it's
it's,
of
course
more
product
and
and
what's
in
it,
for
the
open
source
part
of
the
protocol.
So
what
is
the
level
of
detail?
You
would
like
to
see
you
well.
A
I'm
betting,
that
most
of
us
here
are
object-oriented.
You
know
kind
of
cut
our
teeth
on
object-oriented
stuff
right
so
and
what
was
what's
the
basic
lesson
of
object-oriented
yeah
is
that
you
come
out
of
the
gate.
You
know
learning
object,
oriented
programming
and
you
everything
is
abstracted
like
17
layers
right
and
you
know
it
becomes
a
mess
that
way.
But
if
you
didn't
have
any
object-oriented
station,
you
know
you
write
everything
in
one
function,
so
you
know
somewhere
between
those
two
things.
So
there's
a
lot
of
layer
or
epochs
can
go
infinitely.
A
F
Knight,
then,
for
just
for
an
example,
I
would
understand
that,
within
the
system
of
record
integration,
we
would
need
a
more
generic
epoch
like
providing
the
right
api's
for
any
integrator.
And
then
the
unit
services
could
be
another
epic
within
that
project.
But
on
top
level
there
would
be
some
some
more
architectural
epics
to
work
on.
A
Yes,
I
think,
look
I,
think
that
you
got
you
and
in
Johan
and
Kyle
and
a
few
other
folks
are
really
the
experts
in
the
system
of
record
integration.
I
think
Eric's
got
some
chops
in
there
as
well
so
yeah,
let's
yeah
I
think
this
is
the
week
to
start
really
budding
up
and
getting
some
work
done
on
the
out.
You
know
in
terms
of
structuring
this
so
that
through
the
week
and
then
next
week
in
particular,
we
can
really
release
the
Kraken
as
it
were,
and
get
in
state
and
start
to
publicize
to
people.
A
Hey,
here's,
a
project,
here's
a
project-
you
can
add
a
project,
but
here's
a
bunch
of
them
already
to
get
your
creative
juices
flowing
understand
and
they
it
can
be
well
articulated.
So
just
yeah
go
right
in
here
feel
free
to
structure
this
the
SOR
integration
tools,
project
the
way
you
guys
want
and
I
figure.
You
know
it'll
it'll
norm
out
right,
so
you
can
make
a
change.
Other
people
can
make
a
change,
eccentric,
Center!
You
can
get
together
and
say:
hey
we're
running
amok.
A
E
E
It's
issue
number
19
on
the
issue
list
that
was
intended
to
capture
somewhat
similar
process
of
having
better
more
more,
more
robust
way
of
managing
smart
contracts
and
using
them.
You
know
as
baseline
components
for
importable
importable
contract
library,
so
in
portable
contract
components
I
can
I
can
look
further
into
it
as
I've
been
getting
a
lot
of
things
from
others
as
well
in
the
community,
especially
from
people
from
ether
line,
who
have
expressed
a
lot
of
interest
and
also
direction
in
the
in
terms
of
the
architecture
of
management
of
smart
contracts.
E
D
A
Very
much
like
to
see
somebody
step
up
to
do
that
and
I
think
we'll
grow
into
it.
I'm,
I'm,
I,
guess
I'm
working
that
job
for
now.
No
but
I
I
really
do
believe
in
a
buddy
system,
so
I
mean
you
and
Karthik
or
buddy.
You've
got
another
buddy
with
Kyle,
stephania
I
think
our
buddies,
so
yeah
buddy
system,
so
I'd
love
to
I'd
love
to
have
a
buddy
I'm,
a
project
management
side.
A
Unfortunately,
our
project
manager
for
Ernst
and
Young
the
the
is
from
arson.
Young
cannot
be
the
project
of
the
official
project
manager
of
this
for
independence
reasons
because
they're
not
sure,
as
you
know
so,
and
just
officially
that's
so
he
can't
provide
that
role,
although
he
is
very
much
engaged
in
supporting
the
program,
otherwise
so
yeah
I
can't.
We
can't
use
our
good
friend
Brian
for
that.
E
A
Well,
we
are
out
of
time
I
we
will
publish
this
and
I'm
and
encourage
everybody
to
walk
through
these
these
projects
and
and
go
hey
you're
missing
one
and
and
write
it
in
there
and
ping
me
if
you
have
any
trouble
with
them
without
further
anything
else.
Last
words
he's
gone,
I'll,
see
everybody
next
week,
Cheers.