►
Description
The EOSIO Coalition is an organization composed of multiple EOSIO blockchains united to advance and sustain development of the open source EOSIO protocol.
Currently composed of representatives from #EOS, #WAX, #TELOS, and #UX blockchains, the coalition meets each week to discuss and advance initiatives for the mutual benefit of all member blockchains and the open-source EOSIO codebase.
A variety of topics are covered each week including development, governance, operations, and communications.
Timestamps & Topics:
00:00:00 Intro
00:00:02 Telos RFP system update - Kersten
00:00:41 Funding for worker proposal system - Adam Zientarski
00:01:17 Building the RFP system -Adam Zientarski
00:01:42 RFP Public testnet - Adam Zientarski
00:02:56 Admin account creation - Adam Zientarski
00:04:00 Community voting period - Adam Zientarski
00:04:40 Build Committee - Adam Zientarski
00:06:30 RFP Github repository - Adam Zientarski
00:07:20 Submitting proposals - Adam Zientarski
00:16:46 Submitting bid amounts - Adam Zientarski
00:18:04 Administrative process - Yves La Rose, Adam
00:22:10 RFP Scalability - Jeff Werner
00:23:48 Control mechanisms - Jeff Werner, Adam
00:25:09 Production ready timeline - Kersten, Yves, Adam
00:27:06 What is left to do? (RFP system) - Yves La Rose, Adam, Kersten
00:28:09 RFP Treasury account - Yves La Rose, Adam
00:31:01 Feedback - Adam Zientarski, Yves La Rose
00:34:57 Brand Initiative - Justin Giudici
00:36:45 Domain names - Yves La Rose, Justin Giudici, Kersten
00:40:23 Community strategy updates - Brandon Lovejoy
00:42:58 Faster Finality RFP Document - Ted Cahall
00:44:23 Scalability+ update - Yves La Rose
00:51:06 Ultra Contribution to Faster Finality - Yves La Rose
00:51:51 “Honor” original contributors to bluepapers - Yves La Rose, Jeff Werner
01:00:18 EOSIO full audit + RFP in progress (Ted) - Yves La Rose
01:01:01 Create RFPs for top 20 - Jeff Werener
01:05:58 Identification of feature delta - Kersten
01:07:44 Add coalition members to ENF repository - Ted Cahall
01:09:00 Top 20 Item list - Yves La Rose
01:18:50 Create Wallet + SDK RFP Document draft - Jeff Werner, Ted Gahall
01:20:48 Clarity of Top 20 Items - Kersten, Ted Cahall
01:23:10 Contributing Administrative Resources - Team discussion
01:39:30 Outro
01:39:46 END
Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF
A
Starting
the
meeting
for
today
restarting
a
little
adam
great,
to
have
you
here
thanks
for
joining
the
call
today,
so
we're
going
to
look
at
the
rfp
system
that
just
passed
the
telos
worker
proposal
system
last
week.
So
it's
it's
being
funded,
it's
actually
already
being
built
by
deja
detroit
ledger
technology.
So
so
we
be
able
to
see
something.
A
B
Sure
yeah,
so
the
primary
reason
why
we
built
this
is
because
we
were
kind
of
having
discussions
with
one
of
the
telus
foundation
board
members
about
how
they
thought
that
the
worker
proposal
system
on
telos
the
funds
weren't
being
utilized
in
an
efficient
manner,
mostly
being
distributed
to
for
for-profit
projects.
And
not
you
know,
network
tools
or
or
things
that
can
benefit.
Everybody
right,
there's
also
not
a
whole
lot
of
oversight
on
it.
B
B
And
so
this
is
that
this
is
on
public
testnet.
So
you
can
visit
this
link
and
check
out
things
on
your
own.
If
you'd
like
to
what
I'm
going
to
run
through
here
is
just
the
process
of
actually,
you
know
creating
a
project
or
a
request
for
proposal
and
then
on
the
actual
user
side,
submitting
a
proposal
as
well
there's
a
couple
of
things
that
we
want
to
add
to
this
in
the
future.
But
we
figured
we
kind
of
get
out
a
minimum
viable
product
first
and
the
two
major
things
being.
B
B
And
then
we'll
go
back
to
the
projects
here.
These
are
all
just
the
projects
in
the
system
and
the
ones
at
the
top
are
are
really
ones
that
are
are
managed
by
that
admin
or
program
manager.
Rather,
you
can
swap
through
between
ones
that
need
to
be
started
started
for
the
voting
period,
so
this
is
broken
down.
B
Actually,
when
you
create
an
rfp,
there's,
there's
two
periods:
there's
a
community
voting
period
which
everybody
can
come
on
and
and
vote
stake,
weighted
voting
which
one
that
they
think
is
best
and
that
all
that
does
the
winner
of
that
or
the
multiple
winners
of
that
get
rewarded
kind
of
like
a
little
bit
of
a
bonus.
So
it's
gamified
and
that's
usually
something
around
like
a
thousand
dollars
usd
it
of
course
gets
paid
in
telos,
but
it's
pegged
to
usd
so
that
we
don't
run
into
volatility
issues
as
these
projects
get
completed.
B
The
second
part
of
it
is
then,
after
the
community
vote
is
done.
The
build
committee
which
is
composed
of
people
in
the
tcd,
the
court
telus
corps
development
team
and
the
tf
will
essentially
vote
and
decide
which
proposal
that
they
want
to
go
with,
because
you
know
somebody
might
have
the
cheapest
proposal,
but
they
don't
have
the
best
team.
That
sort
of
thing
right.
So
there's
still
some
some
heavy
oversight
there
from
the
network
stakeholders
so
we'll
go
ahead
and
we'll
create
a
project
or
rather
a
request
for
proposal.
B
B
The
deadline
here,
so
this
is
the
number
of
days
that
there's
accepted
like
accepted
submissions
before
the
voting
period,
the
amount
of
usd
to
be
rewarded
is
that
bonus.
So,
let's
just
say
a
thousand,
you
can
set
any
number
of
proposals
that
will
get
rewarded
for
that.
So
let's
say
the
top
three
vote.
Getters
will
get
that
you
know
it
could
always
just
be
one
and
then
you
can
set
a
custom
voting
period
as
well
for
this,
so
it's
a
little
bit
different
than
how
telus
works
currently
works.
B
B
B
B
B
So
there
there
is
some
templating,
it's
pretty
basic
when
it
gets
to
the
timeline,
there's
actually
a
csv
template
and
I'll
show
you
that,
in
a
second
that
you
fill
out,
essentially
the
sprints
that
you're
doing
and
what
generally
what
you're
doing
there.
So
if
we
go
here,
this
is
actually
now
like
a
user.
B
And
let's
see
here
other
projects
accepting
proposals
so
we'll
go
ahead
and
go
to
this
one
right
here
and
actually
send
a
proposal
in
so
you
can
title
it.
It's
mostly
uploading
a
pdf
at
this
point
right,
so
it
is
a
little
bit
more
free
form,
but
it
does
ask
for
like
essentially
mock-ups.
So
if
you
have
a
figma,
you
can
put
that
in
there
the
kanban
board,
where
you
know
essentially
people,
can
go,
look
in
real
time
and
see
that
tickets
are
are
being
done
by
that
project
team.
B
A
B
B
G
B
B
B
Well,
that's
one
thing
that
we
should
probably
build
in
here
before
we
release
it
is
having
the
ability
to
end
this
early
but
anyways.
I
do
have
a
video
that
I
can
send
you
guys
to
that
finishes
out
the
rest
of
this
process,
since
I
can't
apparently
move
this
forward
manually,
but
essentially
after
after
that,
you
close
the
period
or
the
period
the
period
ends
for
submitting
proposals
and
then
community
members
can
go
on
and
vote
and
then
eventually
they
can.
B
B
H
B
I
I
And
right
now,
I'm
I'm
guessing
because
it's
for
tell
us
the
side
right
now,
it's
the
token
holders,
but
in
our
case,
for
example,
we
have
only
four
voting
accounts,
essentially
to
what
we
do,
I'm
guessing
that
those
parameters
could
be
changed
to
only
white
list.
Those
accounts
as
having
x
amount
of
weight
right
to
determine
what
does
go
through.
B
I
B
B
Yeah,
so
it
does
follow
along
right
here
on
the
the
milestone
section
they're
supposed
to
upload
either
a
document
or
like
a
video.
The
idea
is
that
the
program
manager
is
going
to
regularly
meet
with
the
team
just
to
do
check-ins
to
make
sure
things
are
moving
along
as
they
should.
But
it's
more
about
this
part
of
it,
I
guess,
is
like
reporting
right,
just
making
sure
that
things
are
getting
done
and
there
being
a
paper
trail.
I
I
I
And
likewise,
in
our
case,
the
current
treasury
is
in
is
in
usdt,
so
there
is
no
volatility,
I'm
also
assuming
that,
should
the
determination
be
that
the
milestone
gets
paid
at
the
onset,
that's
also
possible
to
make
that
switch
within
the
the
platform,
for,
let's
say
customization
of
our
specific
needs,
or
is
the
idea
that
this
platform
will
be
as
is,
and
should
people
want
to
adapt
it
to
their
needs?
It's
up
to
them
to
make
those
customizations,
and
I
guess
the
question
is:
is
it
open
source.
K
B
B
B
A
Yeah
it
virtually
just
passed
the
the
worker
proposal
system
and
we're
we're
starting
to
discuss
further
how
to
utilize
it.
I
think
the
the
component
I
personally
like
is
that
it
has
this
kind
of
control
mechanisms
in
into
integrated.
So
so
it's
not
like
the
traditional
wps,
it's
like.
If
it
passes,
then
it
passes,
then
you
virtually
have
to
pay
this.
One
here
is
also
like
a
quality
assurance
mechanism
for
the
program
manager
to
actually
slash
a
project
if
they,
if
they
don't
hit
the
the
actual
milestones
in
delivering.
A
A
So
I
think
that's
what
what
I
like
about
it,
and
it
is
a
process
that
that
allows
us
to
manage
those
rfps,
but
it
is,
as
as
said,
it's
just
being
being
progressed
and
and
we
we
need
to
discuss
all
those
things
and
and
test
it
with
the
first
projects
to
see
how
it
really
works
out.
But
I
think,
as
a
as
a
first
mvp
I
do
already.
I
B
Already
yeah,
so
I
just
put
in
the
name
bid
a
couple
days
ago,
but
got
outbid
for
the
actual
account
that's
going
to
manage
like
the
treasury,
and
things
like
that.
I
did
correct
me
if
I'm
wrong
person,
but
I
would
imagine
in
the
next
like
two
to
four
weeks.
We
can
have
this
deployed
and
have
all
the
funding,
because
we're
applying
for
the
initial
funds
that
are
going
into
the
treasury
from
telos
works
as
well.
I
B
A
Yeah
I
could
envision
that.
Obviously
the
voting
process
is
kind
of
it
needs
to
be
kind
of
close
to
to
the
accounts
that
may
vote
in
our
in
in
our
construct,
so
so
that
it's
not
like
set
out
into
the
side
voter
into
an
official
group
and
everybody
votes
on
it.
So
obviously
we
need
to
kind
of
take
care
of
that,
and
then
we
need
to
care
about
the
currencies.
A
B
I
So,
on
the
other
end,
the
telos
treasury
actually
whitelisted
for
added
this
account
as
a
permissioned
account
to
be
able
to
transfer
out
and
how?
So,
how
does
the
telos
account
threshold
get
mass?
I
guess
what
I'm
getting
at
with
this
is:
is
there
a
potential
vulnerability
that
this
requests
funds
and
because
it's
being
whitelisted,
the
funds
can
get
approved
regardless?
B
On
the
other
end,
so
the
funding
aspect
of
it
now
is
done
manually.
So
it's
it's
not
connected
to
this
system.
That
was
one
of
the
things
that
I
mentioned
in
the
the
beginning
that
we
want
to
build
that
in
in
the
next
phase.
It
was
just
like:
let's
get,
this
done,
see
how
it
works,
and
then
we
can
add
those
improvements.
I
I
B
K
L
I
think
it
looks
like
it's
going
in
the
right
direction.
I'm
also
quite
curious
to
see
it
in
a
few
weeks
see
what
it
looks
like
once.
It's
populated
and
whatnot-
I
am,
I
don't
know
if
you're
planning,
to
support
any
sort
of,
I
guess
like
a
markup,
markdown
language
or
something
like
that
to
write
the
proposal.
I
think
that's
probably
a
good
idea
as
well.
I
L
Exactly
no,
I
think
I
think
in
general,
like
when
you,
when
you
build
things
like
that,
like
I
guess
I
guess.
That's.
That's,
probably
a
a
good
feature
to
have,
because
now
that
you
can
format
the
whole
thing
the
way
you
see
fit
and
you
can
you
can
easily
have
like
collaborators,
also
working
on
the
same
document
and
things
of
the
sort.
I
think
it's
a
so
it's
a
good
idea
as
well
like
edit
as
you
go
type.
Oh
yeah,
that's
a
question:
can
you
edit.
A
F
I
A
Yeah,
because
that's
that's
kind
of
what
I
reorganized
usually
before
the
meeting-
I
haven't
done
this
today
too,
because
I
switch
back
and
forth
between
agenda
and
in
progress
so
that
that's
in
fact
a
little
confusing,
but
usually
we
start
with
in
progress
and
then
move
to
the
agenda
items.
But
it's
kind
of
a
it's
obviously
kind
of
a
secret.
I
I'm
telling
nobody.
A
Oh
yeah,
again
so
great:
let's
go
to
the
in
progress
items
then
then
justin
just
joined,
which
is
perfect
timing.
Justin.
You
want
to
kind
of
give
a
very
short
update
on
on
this
progress
of
the
brand
development,
because,
obviously
it's
timing
is
up
for
next
week.
So
I'm
curious.
Everybody
is
curious
to
hear
what
the
status
of
the
brand
initiative
is.
K
Yeah,
I
think,
we're
still
at
least
two
weeks
away
at
this
point.
The
things
are
progressing
pretty
well
we're
at
the
point
where
we're
looking
at
some
names
and
name
directions,
but
it's
all
dependent
on
how
fast
we
can
get
together
and
meet.
So
I
would
just
like
flag
that
I
know
we've
got
our
next
meeting.
I
think
it's
scheduled
for
tomorrow,
but
yeah
I
would
just
flag-
and
I
guess
check-
is
there
any
specific
deadlines
that
we
have
any?
I
I
think
we're
like
two
or
three
weeks
ago.
I
K
I
I
The
idea
was
to
have
the
the
final
three,
but
we
did
go
over
names
earlier
this
week
and
we're
meeting
tomorrow,
and
I
think
tomorrow
we
might
actually,
if
not
have
three
but
at
least
have
a
you
know
few
less
than
what
we
did.
So
it
is
possible
that
we're
still
on
track
for
that
may
12th
being
able
to
present
three
names
to
the
group.
A
M
I
That's
kind
of
part
of
it
that's
part
of
the
exercise.
So
if
we
do
finalize
the
names
within
the
group
of
like
the
top
three
or
something
like
that,
they
may,
depending
on
the
cost
of
the
domains,
we
might
actually
have
those
secured
prior
to
bringing
up
to
the
group
depending
on
the
cost.
Obviously,.
E
N
I
K
A
O
No
we're
still
on
track,
I
think
we'll
publish
next
thursday.
Largely
it's
just
the
bullet
points.
I've
got
outlined
there
with
any
additions
that
come
up
in
today's
meeting
and
then
we're
still
kind
of
hanging
on
for
I'll,
just
wrap
up
all
the
comms
stuff
in
one
pill
swoop.
Here
we're
just
kind
of
waiting
for
the
name
and
for
some
other
the
priorities.
If
once
the
priorities
are
finalized
and
ready
to
be
publicized,
that'll
be
huge.
O
N
A
A
C
A
A
A
I
A
L
L
L
So
all
of
the
proposals
that
are,
I
don't
have
to
do
with
scalability
plus
we've
been
writing
these
overviews
for
them
and
that's
going
to
be
the
first
basis
for
the
scalability
paper
in
terms
of
content.
What's
been
discussed
in
the
in
the
discussion
also
was
to
possibly
model
it
after
the
structure
of
the
yield
plus
paper
that
is
not
yet
released
officially,
just
because
that
was
that
was
kind
of
following
our
our
latest
discussion
eve
on
the
matter.
L
L
I
guess
like
a
a
bit
of
a
inspiration
from
that
one
to
put
together
the
the
scalability
plus
paper,
but
since
it's
I
mean
I
I've
seen
it
enough,
has
seen
it
because
they're
also
part
of
the
yelp
group,
but
until
it
is
like
released
to
the
public,
we
were
not
comfortable
sharing
it
just
yet
with
the
scalability
plus
group.
So
if
that
makes
sense
so,
but
that's
kind
of
where
it
stands
and
the
the
paper
that
we're
writing
about
fast
finality.
L
L
I
It
I
would
have
no
issues
young
if
you
ask
the
others
in
the
plus
working
group,
if,
if
they,
if
they
were
okay
with
sharing,
I
would
have
no
issues
as
long
as
it
would
be
out
yet
because
that
would
kind
of
suck,
but
as
long
as
they
kept
it
to
themselves.
That'd
be
okay,
yeah,
I
think
so
and
yeah
it's.
L
L
I
I
A
L
It's
a
good
question.
I'm
not
sure,
I'm
not
sure
how
that
group
will
evolve
after
I
guess
like
after
the
the
the
next
couple
weeks,
the
the
last
couple
weeks
I
mean
like
we
we
had
from
the
administrative
standpoint
like
for
kind
of
structuring
and
set
up
standpoint.
I
think
we're
good.
We
basically
identified
which
items
were
essentially
falling
upon.
Scalability
plus,
I
guess
responsibility,
and
then
we
came
up
with.
L
I
guess,
like
people
have
been
designed
like
been
assigned
to
work
on
each
of
these
points
and
flesh
them
out,
and
that's
going
to
converge
into
that
that
blue
paper,
we
we're
gonna
release
at
some
point,
probably
relatively
soon
and
there's
there's
I'm
not
sure
after
that,
like
if
we
even
need
to
keep
the
group
going
unless
it's
for
actually
like
discussing
these.
These
topics
that
we're
gonna
be
working
on.
L
Like
so
I
mean,
there's,
there's
basically
like
three
kind
of
like
large
topics
that
we're
gonna
be
addressing
as
part
of
scalability,
and
we
probably
probably
have
enough
done
on
the
fashionality.
There's
gonna
be
probably
another
one
for
the
ram
improvements,
which
is
what
we
have
on
the
agenda
for
next
tuesday,
but
after
that,
I'm
I'm
not
sure
if
we're
gonna
have
anything
else
in
that
list,
because
that
the
other
points
were
fairly
down
in
the
the
list
of
priorities.
L
So,
as
we
were
kind
of
probably
like
aiming
for
in
one
year,
let's
tackle
like
five
to
eight
of
them.
I
don't
think
there's
I
think
ibc
is
ninth,
so
I
don't
even
think
it's
on
the
radar
just
now,
so
so
yeah,
that's
but
open
suggestions.
Of
course,
like
it's
a
it's
a
convenient
time
time
slot
we
managed
to
get
like
a
bunch
of
developers
in
there
as
well.
So
you
can
certainly
use
it
for
for
any
purpose
that
we
see,
but
it's
just
I
don't.
A
Yeah,
okay,
so
I
I
just
removed
that
I
just
wanted
to
follow
up
so
if
there,
if
you
imagine
at
some
point
that
you
need
some
assistance,
just
just
let
me
know
it's
just
that
the
time
slot
doesn't
fit
mike
my
into
my
calendar
at
the
moment,
but
I'll
be
happy
to
join.
If
you,
if
you
can
adjust
that
cool.
Okay,
that's
great
then
yeah.
This
one
is
the
probably
the
item
ultra.
A
I
So
we
sent
out
it's
been
a
few
weeks.
Now
we
sent
them
the
invitations,
I
believe
they
did
not
join
and
so
the
ball's
in
the
airport.
At
this
point
and
they're
not
on
this
call
today,
either
I
invited
as
well
yesterday
randomly
during
our
fireside
chat
nathan
james
from
ultra,
was
on
our
fireside
chat
and
I
invited
him
to
join
these
calls
as
well
and
so
the
invitation's
there
it's
it's,
it's
the
falls
in
the
airport.
I
A
I
Yeah
so
we're,
I
guess,
for
this:
we're
waiting
to
complete
the
rfps
for
all
of
the
items
that
stem
from
the
original
blue
papers,
but,
and
so
they
need
to
be
populated,
essentially
in
the
rfp
shell
and
then
once
that's.
There
it'll
be
sent
out
to
the
teams,
I'd
already
reached
out
to
the
teams,
so
they're
waiting
on
that
so
they've,
the
teams
have
all
raised
their
hand
to
say
yes
we'd
like
to
tackle
these
items
they're.
I
So
the
one
issue
I
see
here-
the
one
potential
roadblock
I
see
here
is
we've
got
a
lot
of
rfps
to
fill
out
and
we
don't
have
many
people
working
on
this.
So
if
there's
anybody
else
that
would
be
able
to
come
and
help
contribute
to
that
initiative.
We'd
be
able
to
ideally
get
the
rfps
out
to
the
you
know.
I
think
it's
like
12
or
of
the
20
items
or
so
out
sooner
rather
than
later.
I
H
I'll
tell
you,
I
will
tell
you
one
of
the
key
challenges
there
is,
of
course
we
can
get
it
to
a
good
first
draft,
but
we
really
need
people
to
take
a
little
bit
of
time
to
review
that
make
sure
that
we've
broken
the
translated,
the
blue
paper
into
the
rfp
requirements
correctly,
and
it's
just
kind
of
that
little
step,
and
maybe,
if
we
term
it
that
way,
because
we
don't
need
people
to
write
up
the
rest
of
the
structure
of
the
document.
That
would
be.
You
know
not
a
good
use
of
their
time.
H
E
H
So
I
I
think
we
could
do
that.
The
one
one
potential
gap
is
that
this
call
doesn't
necessarily
have
all
of
the
contributors
from
the
working
group
in
it
who
might
have
that
deep
dive
level.
I'm
not
saying
that's
a
critical
problem,
I'm
just
pointing
it
out
to
make
sure,
and
we
could
get
around
that
if
I
say,
for
example,
next
week,
let's
review
these
two
or
three
rfps
so
that
you
guys
can
go
and
get
the
appropriate
people
into
this
meeting
just
for
that
one
week.
H
H
I
Of
scenario
right
so
instead
of
waiting
for
a
week
and
inviting
them
here,
if
there's
documentation
to
send
them,
we
can
send
it
to
them
at
any
time.
We
can
send
it
today
tomorrow
they
could
review,
provide
their
feedback
as
to
what
the
rfp
in
its
current
form,
looks
like,
and
then
we
could
review
the
final
before
essentially
posting
out
and
sending
the
rfp
as
actual
rfp,
not
draft
rfp,
for
their
review
to
be
right,
this
end
of
the
rfb.
H
Something
that
would
help
for
kind
of
the
leaders
of
the
chain
is
to
communicate
like
a
date
as
like.
This
is
a
priority,
so
we
need
this
to
be
reviewed
by
a
certain
date
because
a
lot
of
times
you
know,
I
have
sent
out
stuff
to
different
authors,
and
you
know
people
are
super
busy
and
they
don't
know
where
this
falls
in
their
priority
list.
So
you've
sent
that
to
the
original
author
so
far,
you've
sent
out
drafts
for
their
comment,
a
handful
right
just
a
handful.
M
I
I
can
I
can
re-explain
again
the
ideas
that
we
would
so
eos,
regardless
of
this
group
prior
to
this
group
existing
prior
to
the
coalition
existing
when
eos
put
out
the
mandate
to
create
the
blue
papers.
We
had
also
given
given
the
it's,
not
the
promise,
but
I
don't
know
how
you
would
call
that
said
that
once
they
submit
the
blue
papers,
the
part
of
it
was
that
they
would
have
the
first
right
of
refusal.
I
A
I
So
we've
done
that,
so
I
think
it
was
two
weeks
ago.
I
think
it's
maybe
one
of
the
meetings
that
weren't
there
we
I
went
out
to
just
ask.
That
was
the
first
task.
Do
you
even
want
to
bid
on
this
if
it
were
to
become
available?
The
coalition
has
highlighted
as
this
as
one
of
the
priorities
in
the
top
20
and
essentially
all
of
the
items
were
said
yes,
but
not
by
all
of
the
groups.
I
So
a
good
example
is
an
audit
plus
there's
sentinel
and
there's
slaumis
sloan
has
turned
down
to
bid
on
any
item,
but
sentinel
said
they
would
be
interested
in
bidding
on
the
I
believe,
two
items
that
were
highlighted.
So,
yes,
all
of
the
items
have
been
said
yes
to,
but
by
different
groups.
Okay,
fine,
awesome,
good.
I
A
There
it
is
yep,
okay,
so
yeah,
and
that
was
ted
that
wanted
to
write
that
at
the
moment
that
that
we're
ready
to
go
for
it.
Okay,
so
here,
is
still
the
ted
and
jeff
to
create
rsps
for
top
20..
I
think
we
covered
this
waiting
for
the
first
one
and
and
we
we
haven't
started
really
to
do
the
other
ones.
I
assume
so
or
do
or
do
you
have
like
48
hours
a
day,
and
I
already
started
to
to
create
some
of
the
rfp
bare
bones.
L
I
believe
on
on
tuesday,
during
the
fast
the
scalability
plus
call,
we
said
that
we
would
leave
24
hours
a
review
period
for
anyone
who
wanted
to
go
over
the
faster
finality
and
see
if
they
had
anything
to
add.
I
I
I'm
guessing
nobody,
everybody
raised
their
hand
and
nobody
had
anything
to
bring
up,
so
I
would
say
at
least
for
that
one
like.
Maybe
I
I'm
happy
to
do
another
round
on
it.
I
do
intend
place
a
bid
on
it
as
well,
so
just
full
disclosure.
L
H
It
did
have
the
open
question
to
think
about
nobody
put
any
security
requirements
around
that
which
might
be
okay,
but
usually
that's
kind
of
a
yellow
flag
that
goes
up
in
my
head
for
technical
projects,
but
if,
if
you
guys
don't
believe
there
are
additional
security
requirements
for
that,
then
that's
okay.
That's
just
me.
L
L
Like
I
said
I
mean
I
I
was
hoping
because
I
mean
this
rfp
was
built
of
my
overview,
the
one
that
I
drafted
myself
a
while
back-
and
I
was
hoping
we'd-
get
other
people
to
review
that
as
well.
But
but
unfortunately
I
don't
think
it
happened.
So
so
it's
it's
fine,
but
yeah
I'll
I'll
I'll.
Just
do
one
last
pass
to
finish
it
the
way.
I
K
L
I
L
I
A
L
We're
still
waiting
on
wax,
but
I
mean
I,
I
had
a
discussion
with
lucas
on
kinda
this
topic,
not
just
that,
but
that
that
was
kind
of
part
of
it
and
he
said
that
really
like
the
only
thing
significant
that
they
have
is
that
that
rsa
implementation
that
that's
kind
of
quite
easy
for
them
to
port
over
to
a
new
build
later
on,
or
something
like
that.
So
I
I
don't
think
it's
a.
L
L
A
C
One
of
them
still
is
pending,
like
all
I
can
do,
is
send
the
invite
and
they
have
to
go
to
the
repo
and
accept
the
invite-
and
I
think
lucas
has
still
not
done
that.
I
think
I
have
a
window
open,
but
I
was
looking
at
that,
but
he
had
not
yet
I
can
just
one
second
I'll
pull
up
the
right
thing.
Just
maybe
and.
C
A
Yes,
so
it's
probably
sitting
in
in
thousands
of
mails
waiting
for
him
to
to
find
the
mail.
So
that's
fine!
Okay,
then
we
you
did
go
to
the
top
top
20
priority
list
and
and
discuss
that
so
the
the
ones
that
were
open
as
far
as
I
could
understand
from
from
the
call
was
19
and
20.-
I
don't
know,
have
you
been
able
to
work
on
those
probably.
I
The
research
items
number
10
and
number
five
so
that
the
bolded
right
below
is
are
the
notes
for
the
meeting,
so
I
didn't
fill
up.
I
tried
to
do
the
notes
like
you
do
them,
so
I
unbolded
the
previous
ones.
I
bolded,
basically
the
latest
ones,
so
the
text
there
should
be
accurate
this
one
here.
Yes,
well,
the
three.
Basically
everything!
That's
bold
right
there.
Yes,.
A
L
I
A
L
A
L
Out
of
these
those
that
matter,
the
most
are
probably
number
one
through
five,
because
these
are
the
higher
priorities,
I
believe
for
fashionability
sdk
we're
in
good
shape.
Secure
smart
contract
is
being
also
tackled
because
it's
it
was
part
of
the
audit
plus
blue
paper
synchronous
calls.
I
think
I
think
you
are
already
doing
that
to
the
the
enf.
I'm
not
mistaken
eve.
No.
I
And
actually,
my
question
on
that
was
when
fractally
or
I
guess
dan
and
frankly
did
on
or
had
indicated
that
they
were
bidding
that
they
may
be
on
faster
finale.
Synchronous
calls
was
part
of
that,
so
I
guess
my
question
to
you
is:
do
you
see
synchronous
calls
being
part
of
the
faster
finality
work
and
I'm
really
asking
simply
because
they
were
both
put
together
when
they
were
pitched.
L
I
H
I
Than
that,
I
think
there
is
one
then
that
we
would
actually
go
to
open
tender
with.
If
that's
the
case.
Well,
you
know,
faster
finale
is
another
one,
but
we
guillaume
has
just
highlighted
that
he'll
bid
on
it,
which
is
still
an
open
tender,
the
other
one.
I
guess,
then,
if
I'm
understanding
correctly,
you
wouldn't
bid
on
that
necessarily
guillaume
or
you
or
it's
not
part
of
the
faster
finality
bit.
So
because.
L
L
It
didn't
get
picked
up
for
the
scalability
plus
group,
so
we
decided
it
was
not
a
scalability,
I
guess
feature
so
as
it
stands,
it
probably
should
fall
under
core
plus
or
or
I
mean
if
we
ever
want
to
assign
something
else
to
to
one
of
these
existing
groups
or
for
planning
to
resuscitate
that
yeah.
That's
not
gonna
happen.
I
I
don't
envision
envision
that
happening,
okay,
so
so
yeah.
L
L
I
Do
have
a
question
about
item
number,
nine,
which
is
the
or
what
I
believe
was
item
number
nine.
It
moved
a
little
bit
too
fast.
The
trussless
ibc
is
so
I
saw
that
you
or
that
ux
prioritized
that
as
zero.
I
I
would
imagine
correct
me
if
I'm
wrong
that
you
prioritize
that
as
zero,
because
you
have
a
solution.
Correct.
Yes,
exactly
so
my
question.
I
I
I'm
not
sure
we
talked
about
this,
but
we
kind
of
did
when
we
were
talking
about.
I
believe
it
was
last
week
about
some
of
the
products
or
functions
that
some
chains
have
already
built,
essentially
that
the
others
have
not,
or
they
don't
have,
and
this
would
be
a
good
example
or
the
telos
rfp
solution.
I
The
dlt
solution
that
we
saw
earlier
is
kind
of
another
example
of
that
I
would
be
very
much
supportive
of
whenever
there's
a
chain
that
has
developed
a
particular
product
or
a
function
that
the
others
do
not
have,
that
a
priority
go
to
that
chain
or
that
team
just
seems
to
implement
as
long
as
it
met
the
requirements
of
everybody
else
and
that
we
actually
compensate
retroactively
for
whatever.
That
is
so
that
that
team.
I
In
this
example,
let's
say
ux
would
say
we,
you
know
we're
willing
to
bid
on
this
item
for
x
amount
of
dollars
and
then,
if
they
win
the
bid.
Well,
the
actual
implementation
of
is
much
much
much
quicker
because
the
solution
is
already
there.
So
there's
the
maintenance
and
then
there's
documentation
everything.
But
then
we
would
be
in
a
way
rewarding
the
coalition
members
that
have
already
worked
on
solutions
that
the
others
have
not
rewarding
them.
Financially
is
a
big
component,
but
also
then
for
everybody
else.
I
So
I
put
that
caveat
in
because
I
didn't
want
it
to
sound
like
let's
say
we
would
implement
trustless
ibc
in
this
case
at
no
cost,
because
it
is
an
ip
or
it
is
something
that
you've
developed.
Likewise,
with
the
the
dlt
solution
that
we
just
looked
at
before,
if
we
did
something
like
that,
then
yeah
the
chains
have
borne
costs
in
order
to
bring
it
to
this
level.
That
should
be
reflective
in
in
the
process.
I
I
would
fully
support
that.
L
The
only
reason
I
didn't
really
bring
it
up
until
now
is
because
yeah
it
felt
it
felt
it
were
because
of
the
way
we
voted
for
it.
We
didn't
give
it
exactly
zero,
but
I
think
we
gave
it
like
15
rank
15
or
something
like
that,
so
that
pushed
it
to
global
rank
nine.
I
think,
but
it's
it's
yeah
like.
Obviously.
Obviously
we
we're
very
happy
to
entertain
some
sort
of
agreement
here.
I
H
A
So
do
we
have
because
this,
obviously
these
top
20
items
and
everything
are
we
clear
on
when
we
expect
all
the
things
to
be
ready
and
because
I
I
have
to
admit
I-
I
lost
a
little
bit
track
of
who's
now,
caring
for
what
which
items
and
and
which
status
they
have.
Probably,
it
does
make
sense
to
kind
of
split
this
top
20
ticket
into
actually
20
tickets
to
to
have
like
each
and
every
in
a
different
in
a
different
ticket
format.
A
L
Before-
and
I
thought
we
agreed
upon
was
that
this
only
applied
to
the
haddocks
items,
because
the
other
one
we
would
just
take
the
content
of
the
blue
papers
and
of
the
adducts
that
we
have
in
there.
I
think
those
that
have
that
are
high
priority
all
have
their
definition,
those
that
don't
we
abandoned
them.
So
it's
kind
of,
I
think
I
think
the
that
part
is
more
or
less
done.
As
far
as
my
understanding.
I
So
I
don't
know
if
there's
any
chains
that
have
kind
of
the
the
more
project
managers,
business,
analysts,
writers
or
anything
like
that.
That
would
be
very,
very
much
appreciated,
because
once
these
rfps
are
out,
then
it
goes
to
the
developers.
But
then
that's
not
necessarily
in-house.
We
can
then
go
out
to
the
greater
public,
whereas
for
the
administrative
components
be
very
difficult
to
go
out
to
the
greater
public
to
come
and
volunteer
their
time
to
do
this
at
this
stage,
so
we
probably
have
to
farm
in-house.
I
So
just
keep
that
in
mind.
Wax,
I
guess
is
not
a
call
be
great.
If,
if,
if
wax
were
able
to
contribute
some
people,
I'm
sure
you
have
some
people
that
will
be
able
to
help
out
right
now,
it's
it's
pretty
much
jeff
and
ted
that
are
doing
the.
I
guess
that's
not
true,
there's
guillaume
as
well,
but
if
there
were
other
people,
that'd
be
awesome
all
right
and
I
apologize
like
as
jesse
you've
helped
as
well.
I
L
I
I
K
E
At
the
same
time,
but
I
also
thinking
through
it
if
we
hired
somebody,
I
think
all
the
people
that
are
currently
doing
the
work
would
spend
a
similar
amount
of
time
helping
that
person
come
up
to
speed
on.
You
know
yes
trying
to
do
and
then,
by
the
time
that
time
spent,
they
could
have
just
done
it
themselves
and
then
to
your
point,
then
we'd
have
nothing
for
them
to
do
for
some
cycle
and
yeah.
I
And
we'd
have
a
big
bill
and
we
need
to
figure
out
how
to
hire
those
people
anyways
right,
essentially
the
one
in
in
one
of
our
chains
likely
because
we
have
the
processes
to
be
able
to
do
so.
So
we
we
are
also
increasing
staff
within
bnf,
but
I'm
just
thinking
for
this
week
or
for
next
week,
like
immediate
needs.
Essentially,
if
there's
anybody
on
your
chains
that
you
can
think
of
that,
you
could
volunteer
for
this.
That'd
be
great.
H
H
So
you
know
that's
kind
of
a
good
model.
If,
like
people
inside
the
working
group
can
kind
of
step
out,
even
if
they're,
not
a
project
manager
or
a
product
manager,
they
can
still
like
help
with
just
a
small
amount
of
time.
I
think
inside
of
like
20
minutes
or
half
an
hour,
they
can
blow
through
a
quick
review
and
turn
it
into
gold.
You
know
kind
of
the
garbage
that
I'm
throwing
at.
K
A
Yeah,
I
think
it's
getting
clearer
at
the
moment
that
we
have
a
full
document
and
then
we
could.
We
can
also
judge
what
kind
of
skill
set
we
we
need
for
the
people.
To
do
that.
I
mean
mostly
jeff
and
ted,
are
very
skilled
in
in
those
things
and
can
can
do
that
and
people
trust
them.
So
we
just
need
to
assure
that
we
have
resources
that
that
really
understand
what
they're
doing
so
well,.
I
That's
just
the
beginning
too.
So
then
we
actually
go
out
to
tender
and
then
we
need
to
make
the
decision
as
to
who
wins
the
bid.
And
then
we
need
to
follow
that
project
along
to
make
sure
we
don't
waste
our
dollars
and
end
and
then
so.
We'll
still
need
people
that
know
what
they're
doing
over
time.
I
I
A
Yeah,
I
could
imagine
that
that
this
tool
could
be
used
for
that
I
kind
of
having
keeping
track
on
the
various
roadmaps
and
timelines
and
and
the
budgets
that
are
assigned
to
them
and
well.
If
we
have
like
a
formal
approval
process
for
the
for
the
milestones.
Obviously,
somebody
needs
to
decide
has
a
milestone
been
achieved,
and
if
that's
the
case-
and
we
approve
that
milestone,
then
the
payments
could
be
automated
as
adam
outlined.
A
I
We
were
to
go
forward
with
with
some
with
with
that,
specifically,
I
think,
there's
a
few
components
that
are
missing,
I'm
thinking
just
from
the
invoicing
side
of
things
to
be
able
to
actually
generate
the
invoices,
the
contracts
et
cetera.
Otherwise,
if
that's
all
manual,
then
I
mean
most
of
the
work.
I
And
then
the
ongoing
process
as
well,
because
a
lot
from
what
I
see
right
now
is
a
lot
of
the
ongoing
monitoring
project
management
process
occurs
also
outside
of
that
project.
So
if
there's
a
better
link
to
that,
then
the
accountability
as
you
just
mentioned
would
be
in
there,
but,
as
I
saw
today,
that's
not
necessarily
the
case,
so
you
mentioned
that
we
need
to
manage
these
20
projects.
H
That
is
such
a
complicated
thing
and
there's
no
way,
there's
just
no
way
if
they
spent
the
next
three
years
focused
on
this
they're
gonna
get
something
ready,
but
if
we
take
that
out
and
let's
forget
about
portfolio
management
or
milestone
tracking,
like
you
know,
we
could
use
that
potentially
as
a
framework.
I
also
the
other
thing
I
said
earlier.
H
Because
again
we
need
that
transparency
on
the
process
and
just
saying
that
well,
telus
voted
yes
and
eos
voted
no,
and
I
mean
that
I
don't
think
that's
going
to
cut
it,
particularly
with
some
of
the
headwinds
we
already
have
with
trust
issues.
I
think
what
we
need
to
do
is
maybe
start
in
spreadsheets,
because
they're
easy
and
if
the
process
requires
us
to
pivot.
Spreadsheets
are
super
easy
for
us
to
change
and
we
don't
have
to
go
through
a
development
cycle
just
to
like
make
a
slight
process
tweak.
H
I
I
guessing
that
part
of
that
rigor
process
is
is
occurring.
Let's
say
it
would
occur
on
these
calls
one
thing
that
could
be
kind
of
simple,
but
I
take
your
point
as
well
that
basically,
the
manual
process
is
what
we're
by
default,
doing
and
that's
somewhat
relatively
easy.
While
we
define
the
processes,
one
of
the
things
we
could
do,
if
that,
if
the
application
itself
were
to
add
that
function
would
be
that
these
calls
are
recorded,
put
on
ipfs
and
then
uploaded
through
that
that
application,
then
this
is
the
recurve.
I
The
video
is
the
kind
of
the
record
of
how
we
came
to
that
decision.
Then,
in
the
application,
do
it
up
down
what
was
still
missing
for
me
is
then
the
payments
are
sent
out,
but
I
still
need
an
invoice.
We
still
need
a
contract.
We
still
need
the
kind
of
the
real
world
part,
that's
not
in
there.
So
that's
the
part
I
think
is
still
missing
before.
I
would
think
that
we
could
actually
adopt
it.
Otherwise,
I
think
it'd
be
nice.
I
It'd
be
symbolic,
but
we'd
still
need
to
recreate
the
actual
thumb
up
in
a
paper
with
a
signature,
and
so
it
would
be
it'd
be
a
nice
kind
of
to
have,
but
in
order
to
leverage
it
the
way
that
I
think
could
be
leveraged.
It
still
needs
to
work
and
that's
cool,
because
if
we're
one
of
the
first
users
or
enterprise
users,
it
might
be
an
opportunity
to
define
what
the
application
becomes
or
what
it
looks
like
and
which
features
are
being
added
to
it.
I
J
J
C
The
reason
it
needs
I
agree
with
it
should
not
have
kanban
in
it
jeff,
but
it
needs
the
milestones
because
the
milestones
are
when
payments
are
created.
So
all
the
milestone
would
go
tick.
This
milestone
should
be
up
now
and
then
a
pm
would
say,
show
me
your
demo
or
whatever
yes,
we're
approving
payment.
C
Then
it
could
actually
cause
payment
on
chain
and
telos
or
an
eos
and
create
the
invoice,
and
you
know
it
could
it
could
do
it
doesn't
do
any
of
that
today,
but
I
could
see
where,
if
we
added
those
enhancements,
it
could
kick
out
the
contract
kick
out
the
invoice
make
the
payment
automatically,
but
it's
it's
got
work
before
I
mean
for
now
we're
it's
not
really
taking
any
load
office.
It
would
actually
be
more
work.
I
Would
be
good
to
kind
of
define
that
process
early
if
we
really
wanted
to
go
down
that
route,
defining
it
early
and
then
leveraging
the
power
of
the
blockchain
that
we
have
and
our
own
tools
to
be
able
to
kind
of
create
that
transparency
that
that
record.
That
immutability
to
our
processes,
I
think,
would
be
really
good
but
agree
with
you
that
today,
it's
probably
more
work
than
just
doing
it
manually,
but
we
need
to
start
somewhere
at
some
point,
and
this
team
seems
willing
to
do
so.
A
Yeah
and
at
the
point
of
time
we
we
start
really
working
on
those
projects
we
need
to
have.
Like
you
said
jeff,
we
need
to
have
like
a
the
tool
that
enables
us
to
to
do
proper
portfolio
management
and
and
manage
those
projects
and
and
put
them
together
as
a
program.
So
so
we
we
need
to
work
on
that,
so,
but
maybe
ted
jeff
I'll
coordinate
the
meeting
for
this
template.
Maybe
we
can
think
about
that
and
and
think
about
tools.
A
I
C
J
C
I
mean
yeah
yeah,
I
mean
it
was
nice
that
it's
also
being
signed
with
the
private
key.
So
I
like
that,
like
you,
can
tell
it's
a
you
can't
fake
the
private
key.
You
know
that
the
fact
that
you
signed
it
with
your
wallet,
so
I
like
that
integration.
It's
it's
one
of
the
reasons
why
most
enterprise
applications
can
be
spoofed.
You
just
go
in
the
database.
Somehow,
if
you're
a
dba
and
you
change
someone's
salary,
they
don't,
they
can't
really
tell
who
changed
it.
C
I
Yeah
in
terms
of
general
accountability
for
this
group,
it's
also,
I
think
I
see
the
benefit
fast
forward,
six
to
eight
months,
where
we're
spar,
where
we're
managing
multiple
projects,
we're
awarding
multiple
rfps,
where
the
treasury
is
much
larger.
I
can
see
how
this
then
also
brings
accountability
to
all
of
the
groups
to
showcase.