►
Description
This week the EOSIO Coalition discusses Rebranding efforts, Voting progress, Faster Finality / IBC milestones, and P2P/ Wallet SDK RFP approvals.
00:00:00 Rebranding update by Kersten, Douglas, Zack
00:08:32 Voting and Progress update by Jeff, Douglas, Brandon
00:13:22 Bi-Weekly reports and Organization by Brandon, Kersten
00:16:55 Faster Finality and IBC Milestones by Brandon, Kersten, Gnome
00:29:09 P2P RFP update by Stephen, Ted, Douglas, Kersten
00:32:15 Wallet SDK RFP update by Aaron, Gnome, Douglas
00:35:31 FF/IBC RFP update by Kersten, Ted, Jesse, Douglas
00:46:58 Wrapping it up with open discussion by Kersten, Douglas
00:53:38 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://www.eosnetework.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #EOSIO #ENF
A
B
C
So
we
have
the
domain
which
I've
shared
my
amazing
first
revision
of
the
the
I
worked
with
ted,
I
think
yesterday
or
tuesday
we
did
dns.
So
maybe
you
can
give
us
an
update
on
that.
Like
the
other
stuff,
we
maybe
we
could
talk
about
the
the
socials.
I
I
think
two
weeks
ago
I
was
just
poking
around
on
telegram
and
I
noticed
that
the
closest
to
the
thing
to
the
brand
wasn't
available
on
telegram
and
I
think
I
told
justin
hey.
I
thought
we
had
this.
C
I
grabbed
it
because
it
was
available
and
justin
said
we
were
just
planning
to
rename
the
eosio
channel,
which
is
which
is
fine,
but
I
wanted
to
have
it
and
secure
it
anyway.
So
I
have
it
now
good
and
then
I
guess
the
other
ones,
I
think
brandon
you
were
gonna,
do
some
of
the
twitter
and
the
discord
ones.
I
also
I'm
not
sure
what
the
plan
is
with
github,
because
I
know
we
wanted
to
rename
the
one
we
have
now
to
the
new
brand.
C
But
then
again
should
we
secure
the
old?
Should
we
secure
it,
and
then
I
mean
I
imagine
like
with
the
telegram
or
with
the
github,
if
we
secure
the
new
one,
we
would
just
have
to
like
delete
it
and
then
rename
the
old
one
quickly,
so
that
there's
you
know,
I
don't
know
if
there's
a
way
in
any
of
those
systems
to
say
hey,
I
re
I
rescind
this
and
I
give
it
to
this
other.
You
know
account
that
wants
to
rename
so.
B
I
I
think
in
in,
in
the
absence
of
any
very
high
costs
like
for
premium
urls,
if
it
seems
reasonable
that
that's
something
that
someone
would
use
and
we'd
want
to
grab
it,
then
I
think
we
should
err
on
the
side
of
just
grabbing
more.
You
know
of
squatting
on
more
ip,
because
it's
only
going
to
cause
problems
in
the
future.
If
you
know,
if
somebody
has
some
kind
of
lookalike.
A
Yeah,
I
just
wanted
to
check
if
anybody
take
took
responsibility
to
look
at
whatever
tick
tock
facebook,
instagram
snapchat,
whatever
we
want
to
have
and
and
try
to
secure
those
those
name
versions
that
that
might
be
available
to
be
used.
So
I
just
wanted
to
check
if
somebody
took
that
that
task,
maybe
brandon,
I.
E
I
started
realistically
going
to
use
snapchat
here
I
mean
I'm
good.
I
I
did
some
background
like
looking
into
like
substrate
and
cosmos
and
other
similar
like
like
technologies
like
I'm,
not
I
mean
it
doesn't
hurt
to
squat
it.
So
don't
get
me
wrong
there.
We
find
squatting,
I'm
just
here
wondering
what
everyone's
opinions
are
on.
Where
we
go
with
this,
I
envision
we'll
use
twitter.
C
Don't
think
it's
anything
that
we
wanted.
I
think
that
the
name
like
grabbing
them
all
so
people
don't
imposter
or
scam
with
them,
would
be
like
the
only
reason
and
then
the
only
presence
we
would
have
on
most
of
them
probably
would
be.
This
is
the
official
you
know
channel
or
account
of
law
right.
I
think
we're
trying
to
avoid
the
name
right
now,
but
yeah,
but
go
over
here
to
this
place.
This
is
where
yeah
check
twitter,
or
you
know
these
are
the
two
main
places
where
we
have
a
presence
yeah.
C
A
Yeah
yeah,
so
the
question
is
brandon.
As
you
said
you
you
were
working
on
a
on
a
file.
Maybe
you
want
to
share
that
file
and
on
telegram
and
then
then
we
have
a
telegram
decision
chat
on
whether
we
want
to
pursue
those
or
not.
I
mean
the
name
is
generic
enough,
so
it's
probably
taken
anyway.
So
so,
but
we
still
could
try
to
kind
of
say
foundation
or
whatever
it's
going
to
be
as
a
legal
entity
at
some
point
of
time,
and
then
we've
secured
those
so
yeah.
E
D
B
B
Could
you
maybe
make
a
matrix
document
that
that
just
says
you
know
what
the
platform
name
is
what
the
yeah
the
asset
list
like
like
brandon,
says
and
who
and
who
is
basically
the
owner
of
those,
so
we
so
we
know
we've
got
it
covered
and
again
so
much
better
to
air
on
the
side
of
of
just
having
it
so
that
we
can't
be
imposters
or,
and
who
knows
what
platform
is
going
to
become
big?
This
is
we
should
look
at
this.
The
way
apple
looks
at
or
alphabet.
B
E
So
a
while
back
cc32
is
trying
to
talk
to
the
owner
of
the
eos
io
developers
group
to
pass
over
ownership
to
enf.
This
is
like
when
we
first
started
and
he
never
really
responded.
I
don't
even
know
who
the
owner
is
and
when
I
scroll
through
the
group
info,
all
I
see
are
a
bunch
of
admins.
It
seems
like
a
bunch
of
people
that
we're
close
with,
if
not
in
this
group
are
admins,
and
I
was
just
curious.
E
C
A
E
B
E
A
A
F
F
You
know
it
so
brainstorm
about
that.
Maybe
we
can
talk
about
that
in
another
meeting
on
you
know
what
other
than
just
saying,
yeah,
we'll
all
just
commit
to
do
better,
which
is
kind
of
like
saying
we're,
gonna
punt
this.
We
need
to
think
about
ways
that
we
can
add
a
little
bit
of
governance
or
accountability
to
this.
If,
if
the
coalition
is
not
happy
with
the
fact
that
it's
taking
us
four
months
to
even
get
like
the
first
contract
written.
B
Yeah,
well,
I'm
I'm
sure
it'll,
surprise,
no
one
that
I
I
think
that
we
should
be
moving
as
swiftly
as
possible
on
this
in
the
in
that
earlier
sort
of
pre-coalition
phase.
I
I
took
on
a
lot
of
that,
and-
and
so
I
think
you
know,
it
does
not
have
to
be
me,
but
I
think
probably
somebody
has
to
have
that
major
domo
role
of
saying
hey.
B
B
We
need
somebody
to
be
sort
of
in
charge
of
this
group
and
not
probably
not
any
of
us,
because
we
all
have
our
ample
responsibilities
elsewhere,
but
our
first
hire
so
to
speak
should
be
somebody
who
can
you
know
hopefully
become
the
the
ceo
of
this
in
time
or
whatever
we
nomenclature
we
use,
but
but
for
now
just
tries
to
keep
everything
on
on
track
and
moving
forward.
I
think
I
think
pr
in
a
practical
terms.
B
You
know
that
we'd
laid
out
in
those
in
those
documents
could
take
over.
But
I
think
that's
what
we
need
to
do.
Some
kind
of
interim
interim
whip
cracker
at
the
very
least,
but
hopefully
that's
somebody
who
that's
a
role
that
that
evolves
into
evolves
into
you
know
an
ongoing
thing
and
again.
Another
reason
why
none
of
us
should
really
be
doing
it.
You
know,
least
of
all
me
is
that
is
that
it
has
to
be
somebody.
B
D
So
I
kind
of
want
to
get
the
language
right
around
that
or
maybe,
if
we
shouldn't
mention
it
yet
because
it's
not
a
done
deal,
get
some
feedback
on
that
and
then
the
status
of
the
rfp
with
the
wallet
sdks
that
aaron
is
working
on
again,
I
have
all
the
documents,
but
I'm
just
wondering
if
you
could
characterize
for
me
where
these
two
things
are
at
in.
Like
a
general
summary.
B
We
shouldn't
be,
we
shouldn't
be
putting
anything
out
until
we
have
a
brand
that
we
can
put
out
at
the
same
time,
so
we
kind
of
buy
a
little
time
while
we
don't
have
that,
but
at
the
same
time
that
hopefully
is
approaching,
and
as
soon
as
we
do
have
it,
we
should
we
should
be
coming
out
with
you
know,
with
a
backlog
of
big
announcements.
I
think
to
show
the
work
we've
done,
so
I
think
those
things
need
to
be
aligned
so
you'd.
Rather
we.
D
E
E
We've
done
an
update,
we
still
need
to
do
an
update
like
I
am
starting
off.
It's
been
too
long.
We've
made
a
lot
of
progress
when
it
was
originally
on
our
content
calendar.
We
assumed
that
the
brand
would
have
been
like,
like
doug
suggested.
We
thought
it
would
coincide
with
it,
but
it's
been
a
month
and
we
haven't
done
one
since
we've
had
all
of
these
ibc
discussions
since
we've
had
the
faster
finality
discussions
so
yeah,
it's
already.
B
On
our
to
me,
updates
and
announcements
are
different
things
just
to
just
to
clarify.
I
think
we
as
as
we
talked
about
before
I
need
we.
I
think
we
need
to
it's
imperative
that
we
set
up
a
regular,
predictable
schedule
for
up.
You
know
four
updates,
but
so
I
think
for
announcements.
We
need
the
brand
okay.
D
Well,
yeah,
so
writing
this
coalition
report.
We
were
doing
once
every
two
weeks
as
zach
said
it's
been
a
month
on
this
last
one,
partly
because
it's
just
nothing
breaking
you
know
and
exciting
that
you
can
only
write
so
much
about
this
they're
still
deliberating
on
the
same
things.
Kind
of
you
know
as
an
update.
So
but
now
I
think
this
particular
these
two
items
are
pretty
big
deal
and
then
you
know
I
can
add
something
with
the
branding
I'm
still
ongoing.
Just
so
people
know
it's
still
happening
but
yeah.
D
How
would
you
like
to
characterize
where
we're
at
with
the
the
wall,
both
the
wall
sdk
and
the
the
larger
ibc
faster
finality
issue?
Like
it's
a
proposal
at
this
point,
I
I
presume
it's
proposal
that
the
the
team,
the
different
chains
have
yet
to
finalize
voting
on,
but
but
this
is
the
general
idea,
I
guess
maybe
yes.
A
Well,
I
I
second
that
the
the
point
is
that
we
have
a
lot
of
work
that
that
went
into
those
projects,
and
we
do
have
figures
now
right,
so
so
we
are
aaron
is
wanted
to
kind
of
introduce
us
to
the
to
the
entire
rfp
document,
and
he
already
showed
some
figures
last
week
with
working
packages.
So
so
I
think
we
could
take
some
of
that.
As
as
like
an
update
and
say
there,
it
is.
A
D
A
A
What
will
this
deliver?
What
is
the
estimate
cost
for
the
for
the
for
the
coalition
and
what
are
the
benefits
that
we
are
expecting
to
get
out
of
this
for
our
user
bases?
I
think
if
we,
if
we
do
this,
this
would
be
like
a
cool
update
that
shows
that
we're
not
being
being
silently
doing
nothing.
It's
a
lot
of
work
being
done,
and
these
kind
of
documents
clearly
outline
that
we
have
a
plan.
A
The
only
thing
missing
is
the
final
decision
and
the
votes
to
really
stop
working
on
that.
I
think
that's
that's
the
point
that
I
would
make
here
because
we
haven't,
we
haven't.
We
have
made
progress
and
we
should
talk
about
that.
Not
talking
about
that
because
we
wait
for
a
new
branding,
I
think
would
be,
would
be
a
mistake,
even
if
we
don't
have
the
branding
right
and
we
we
finally
vote
on
one
of
those
things
and
see.
Okay,
we
do
this
ibc
thing
with
with
having
a
pool
of
tokens.
A
I
don't
know
if
we
want
to
publicize
this
a
tool
of
tokens
of
each
chain
that
it's
that
is
used
as
collateral
against
the
for
the
payments.
I
mean
this
is
kind
of
a
cool
thing,
isn't
it
and
we
we,
I
think,
if
we
we
all
approve,
we
could
talk
about
this
and
say
this
is
not
just
ibc
technology.
It's
actually
being
used
to
to
manage
some
of
the
payments
immediately.
D
Yeah
and
that's
a
little
oh
yeah
guillaume,
if
you
want
to
weigh
in
but
to
that
point
like
that's,
that's
a
little
bit
of
the
area
that
I
was
kind
of
curious
like
how
much
we
wanted
to
get
into
is
the
this
arrangement,
this
financial
arrangement
of
the
different
tokens
being
laid
out
and
your
document
expresses
it
perfectly.
I
just
need
to
do
it
in
words,.
G
Right
so
yeah
I
did.
I
did
talk
to
eve
yesterday.
I
was
essentially,
as
I
finished
a
document.
I
discussed
it
with
him
and
I
guess,
like
it's
exactly
what
the
christina
was
saying
and
very
similar
to
what
the
status
for
the
sdk
for
ibc
and
fast
finality
were
essentially,
as
of
yesterday,
we're
pretty
much
ready
for
the
coalition
members
to
review
and
eventually
cast
their
vote
on
the
proposal
as
it
stands.
G
There's
as
as
a
what
I
was
discussing
with
evie
yesterday's,
I
think,
there's
also
opportunities
to
kind
of
start
talking
about
it
and
to
start
like
getting
people
excited
essentially
like
creating
some
momentum
leading
up
to
the
release
of
of
the
solution.
Also
considering
that
there's
some
of
these
early
deliverables
are
pretty
much
done,
like
there's
a
few
few
things
to
adjust
to
reflect
the
requirements
of
the
of
the
enf
and
of
the
coalition
members,
but
these
are
kind
of
short-term
wins.
G
So
I
think
I
think
it's
it's
a
bit
unfortunate,
that
eve
is
not
here
today
and
that
lucas
trump,
but
I
think
we're
we're
actually
doing
pretty
well
now,
it's
just
a
matter
of
yeah
like
taking
the
time
to
go
over
the
proposal,
scheduling
a
vote.
The
on
my
end,
I'm
ready
to
to
our
general
counsel
draft
the
contract
with
the
member
of
the
coalitions
and
get
this
out
the
door
asap.
A
I
personally
do
not
agree
with
that,
because
we're
not
announcing
the
announcement
of
the
announcement
we're
just
announcing
that
we
make
progress
and
I'm
not
called
justin
and
nobody's
called
sun
here.
So
we
we
are
virtually
just
reporting
progress,
and
while
we
do
this,
obviously
once
the
the
work
packages
are
being
being
ordered
and
the
contracts
are
signed
and
the
first
deliverables
are
are
being
deployed,
this
is
the
point
where
we
pick
this
up
again
and
say:
hey.
A
B
B
I
think
that
that
we
can
where-
and
we
can
talk
about
these
things
and
just
say,
hey
our
policy-
is
that
we're
not
going
to
officially
release
anything
as
a
full
announcement
until
until
this
branding
is
out,
for
you
know
such
reasons,
but
we
can
continue
talking
about
things
in
updates,
but
the
official
announcements,
I
think,
should
wait
until
the
break
until
the
branding
is
complete
and
live.
That's
that
was
my
my
point,
not
that
we
should
hold
any
news.
B
A
Okay,
so
does
does
this
help
you
already
brandon,
I
mean
they
you,
you
could
get
like
two
three
sentences
from
aaron
and
gilliam
about
the
general
status
and
we
have
those
documents
and
we
can
kind
of
condense
three
to
four
technical
information
pieces.
Out
of
that
that
you
could
add
to
the
report
and
probably
if
we
want
some
budget
numbers
and
probably
if
you
want
this
ibc
deal
details
that
include
tokens
of
the
chain.
That
would
also
even
more
show
how
closely
we're
working
together
now.
D
Yeah,
I
think
I
was
trying
to
get
to
this
yesterday
actually,
but
then
I
was
kind
of
hoping
that
today's
meeting
would
shed
like
bring
some
more
clarity
and
have
a
little
bit
more
to
announce
or
announce
or
update
whatever.
But
I
would
say
tonight
I'll
just
wrap
up
a
general
update.
That
kind
of
gives
a
like
a
broad
overview
of
the
situation
and
then
when
we
actually
have
a
more
concrete
agreement
in
place,
we
can
go
into
the
specific
details
and
kirsten
if
you
wanted
to
help
with
that
at
all.
D
That'd
be
wonderful
because
I
think
you'd
probably
have
a
better
mind
for
the
details
and
how
to
arrange
all
those
different
data
points
together,
yeah
happy
to
help
but
yeah.
I
can
just
write
a
general
overview
kind
of
where
we're
at
which
is
essentially
what
I've
been
doing.
This
whole
time
going
into
details
a
little
bit
here
and
there,
but
nothing
too
exhausted.
I
guess
so
yeah,
okay,
so.
A
I'm
good
excellent,
so
we
we
still
have
like
the
introduction
from
aaron.
We
wanted
to
talk
about
the
p2p
rfp
from
stefan.
We
wanted
to
talk
about
the
ibc
fast
finality
update
from
glyom.
So
what's
the
this
sentiment
within
the
group?
Obviously
it's
been
recorded,
but
having
the
comments
of
eve
and
lucas
would
obviously
be
very
valuable
at
this
point,
so
basically
giving
it
back.
Aaron
steve,
stefan
and
gilliam
these
you.
A
C
I'll
chime
in
and
just
go
ahead
and
quickly
say
regarding
the
p2p
rfp,
I
am
comfortable
talking
about
it
today.
I
am
also
aware
that
eve
kind
of
gave
it
his
blessing
in
the
last
meeting
and
has
since
delegated
his
vote
to
ted.
So
I
I
think
that
we're
equipped
to
to
make
moves
on
it.
If
we
can
come
to
a
vote
today,
at
least
reviewing
I'm
happy
to
do.
H
B
A
B
I
haven't
heard
from
you
kirsten,
and
I
haven't
heard
from
jesse,
I'm
just
saying
that
of
of
the
you
know
the
three
of
us
that
it
would
take
to
officially
do
this.
For
for
the
telescore
devs
I
justin
I
hadn't
direct.
We
hadn't
directly
disguised
that
so
I'm
just
saying
it's
a
yes
for
me.
If
it
is
for
him.
A
C
H
A
Wax
is
basically
abstain
for
now,
but
I
will
check
and
chat
with
the
with
lucas
and
then,
but
this
is
a
pass
anyway.
So
wonderful,
so
we
we
can
move
forward
with
this
excellent
aaron.
You
want
to
give
some
more
outline
on
on
your
on
the
wallet
sdk.
Do
we
also
have
an
information
state
already
achieved
with
the
chains
available
here?
That
would
enable
us
for
a
vote
on
this
one
or
we
need
some
further
discussion.
Obviously,
the
the
amounts
are
significantly
higher.
G
No,
I
think
we
went.
We
went
over
it
last
week
and
my
my
questions
were
answered.
So
as
far
as
I'm
concerned
all
good
with
the
proposal
we
said
we
would
discuss
the
basically
like
between
the
the
coalition
members
for
the
rates.
So
I
think
I
think
probably
next
week
would
be
a
good
time
to
do
so
if
everyone
is
available
other
than
that,
I
think
everything
is
fun.
A
C
A
D
Yeah
absolutely
yeah.
That
was
my
understanding
as
well.
We
last
time
we
talked
about
it.
We
were
going
to
do
kind
of
an
introduction
about
it,
just
again
kind
of
share
the
vision
of
everything
and
answer
questions,
but
then
you
guys
were
going
to
take
it
offline,
like
you
did
with
ibc
in
a
separate,
call,
discuss
the
details
and
then
come
back
with
it.
So
exactly.
B
A
Okay,
well
that's
great,
because
this
is
one
of
the
proposals
that
jeff
and
I
have
also
been
talking
about
saying.
Well,
it's
been
discussed
for
a
long
long
time,
everybody's,
basically
in
agreement
that
we
should
do
that
and
it's
it's
one
of
those
where
we
should
say
well,
yeah
generally,
we
want
to
do
this
and
we
know
that
we
want
to
do
this
with
aaron.
So
so,
let's
let's
go
on
okay,
but
that's
great!
A
H
B
Well,
it's
no.
We
can't
pass
anything
without
on
this.
I
don't
think
without
with,
if
eos
is
going
to
abstain
and
wax
is
in
here,
so
I
don't
know
if
there's
a
point
in
any
kind
of
vote.
If
you
want
a
straw
poll,
I
generally
I
I
strongly
support
it
in
in
general
terms,
but
I
haven't
reviewed.
What's
the
the
most
recent
modifications,
but
I
don't
think
it
could
necessarily,
but
I
would
say
it
shouldn't
necessarily
take
us
a
week
on.
B
G
Of
that
is
in
is
in
the
spreadsheet
that
I
shared
yesterday,
so
maybe
I
I
can
give
a
quick
kind
of
explanation
about
the
whole
thing
I
did.
I
did
so
yesterday
for
eve,
and
he
felt
like
that
was
very
representative
of
what
he
was
he
said
in
his
words,
he
said
it
was
exactly
what
he
had
in
mind.
So
essentially,
what
I
did
is
I
took
the
original
fast
finality
milestones
and
I
interpolated
the
ibc
milestones,
so
they
have
a
slightly
different
color.
G
The
idea
is
that,
as
as
the
agreement
with
regards
to
the
funding
was
presented,
eos
would
end
up
paying
the
first
milestones
and
wax
and
telos
would
end
up
paying
the
last
milestones,
or
rather
the
funds
would
be
unlocked
like
after
a
certain
time
for
wax
and
delos.
So
and
as
we
discussed,
it
would
also
be.
G
These
funds
would
be
made
available
to
to
serve
as
liquidity
in
to
the
amn
on
ux
network
so
and
the
the
lp
tokens
that
represent
ownership
of
these
funds
would
be
the
ones
to
be
locked.
So
essentially,
this
is
to
prevent
the
selling
of
the
wax
and
the
telus
token
before
before
vesting,
and
if
you
look
at
the
the
the
milestones.
That
means
essentially
that
none
of
these
funds
will
be
available
until
nine
months
and
nine
months
is
a
very
small
milestone.
G
B
Thanks
young,
I
would
say
that
this
is.
This
is
a
situation
where
you've
definitely
done
your
work
and
came
back
with
the
answers
that
that
we
asked
for
and
the
specifics,
and
I
think
we
just
need
everybody
else
to
everybody
else
here
to
to
you
know,
respond
in
kind
and
actually
drill
down
and
review
this
and
with
what
you've
done
and
the
few
answering
all
the
few
open
questions.
B
We
don't
all
have
to
get
on,
as
we
could
just
vote
with
with
the
voter
for
each
chain
could
just
propose
it
could
just
submit
a
self
video.
You
know
we
don't
have
to
get
on
a
whole
big
thing
again,
so
we
have
that
transparency,
but
I
think
we
could
do
this
in
24
hours,
because
there's
really
not
outstanding.
G
G
Tabs
is
possibly
to
have
arag,
have
a
look
at
it
and
see
if
you'd
like
to
change
the
wording,
or
we
already
like
agreed
on
the
on
the
items
themselves,
but
essentially
like
for
him
to
do
what
he
did
for
fast
finality
requirements
and
really
like,
but
have
a
very
kind
of.
I
guess
like
very
well
articulated
definition.
For
all
these
points,
that's
the
only
thing
that's
required,
but
in
principle
the
information
is
already
there.
H
Yeah,
so
just
all
that
eve
needs
to
know
is
that
that's
there
and
talk
to
our
egg,
so
he
might
not
be
ready
in
24
hours
is
my
point
he's
away
from
the
keyboard
today.
He's
unfortunately
has
some
personal
items
he
has
to
attend
to,
so
he
probably
he
may
not
be
able
to
be
ready
by
tomorrow.
That's
what
I'm
trying
to
tell
you
and
you
know
feel
free
to
telegram
him.
H
B
A
Do
we
have
some
more
technical
questions
to
the
requirements
from
the
chains
or,
if
that
all
is
in
you
know,
is
that
all
in
alignment
with
what
the
expectations
are?
I
mean
fast
fundamentality
has
been
discussed
extensively
over
a
long
time
already.
Ibc
is
probably
while
more
common
common
knowledge.
I
would
think
hasn't
been
discussed
in
more
detail.
Well,
this
is
not
too
detailed
too.
Are
they?
Are
there
technical
questions
or
any
any
other
requirements
and
additions
that
the
change
would
would
ask
for
in
this
kind
of
document.
G
I
reg
added
a
few
requirements
which
we
we
discussed
over
the
last
two
weeks
in
the
scalability
plus
calls,
and
as
of
the
call
that
was
on
this
tuesday,
we
have
a
we've
completed
the
research
that
was
required
to
address
these
requirements
that
eric
outlined.
So
at
this
point,
where
we
don't,
we
don't
need
anything
else
from
from
from
hiring
to
to
implement
these
requirements.
G
B
A
Cool
ted
anything
from
from
enf
that
you
would
think
you
would
add
here
or
have
more
technical
questions
or
amendments.
No
okay.
So
that's
we
can't
ask
lucas,
but
I
would
tend
to
say
that
he'd
most
likely
agree
so,
but
that
means
that
it's
more
like
the
financial
agreement
that
needs
to
be
covered
and
decided
on
which,
to
my
personal
perspective,
looks
fair
and
in
favor
of
the
smaller
chains
once
more,
which
I
I
highly
highly
appreciate.
A
A
F
I'm
not
sure
for
today
that,
as
we
move
to
operationalizing
the
new
branding,
probably
a
sub
team
or
part
of
this
agenda
for
how
you
know
to
move
beyond
just
the
launch.
The
continued
evaluation
of
you
know
how
well
we're
gonna
extend
that
out.
What
that
word
plan
looks
like
so
I
it
could
be
something
we
put
in
the
backlog
and
then
try
to
address
that
in
upcoming
meetings
or
with
a
sub
team
of
sorts.
B
B
B
H
A
B
B
H
If
I
could
go
back
to
the
ibc
thing
again
and
I'm
I'm
just
trying
to
relay
information
here,
as
he
has
a
minute
here
or
there
I
he
said
we
need
the
general
in
quotes.
It
still
looks
good
from
the
folks
that
to
whom
gnome
presented
so
that
we
can
get
illegal
to
draft
the
actual
agreement,
in
other
words,
eve,
is
wanting
to
see
an
actual
legal
agreement.
G
Yesterday
was
our
legal
counsel
would
draft
it,
but
I
was
just
I
was
just
waiting
for
a
kind
of
like
I
guess,
like
an
agreement
from
the
parties
with
regards
to
the
milestones.
If,
if,
if
telos
and
wax
and
and
eos
agree
with
the
milestone
I
presented,
then
we
can
definitely
start
the
process
and
have
the
the
contract.
H
Drafted
yeah,
I
just
don't
know
you
had
you
noticed
that
you,
you
noted
that
you
added
that
additional
tab
in
the
spreadsheet
and
I
can't
be
sure
eve-
has
seen
that
tab
or
or
agrees
to
it.
So
I
mean,
unfortunately,
this
is
one
item
where
it's
complex
enough
and
I'm
fine
with
you
guys.
You
know
telegraming
in
the
background
and
sorting
that
out.
G
If
there's
any
questions
with
regards
to
the
milestones
and
the
payment
schedule,
if
there's
anything,
that's
not
clear
feel
free
to
reach
to
reach
out
to
me
and
then,
as
soon
as
all
the
chains
give
me
their
thumbs
up,
we'll
get
started
with
the
drafting
of
the
contract,
and
then
we
can
take
a
vote
on
the
on
the
content.
The
contract
itself.
Whenever.
G
Essentially
like
this,
this
document
that
I
presented
yesterday
will
serve
as
the
annex
of
the
of
the
contract.
So
essentially
it's
going
to
be
a
more
or
less
like
standard
service
agreement
with
a
with
dnx
that
defines
the
work
and
the
milestones
that
are
expected.
So
so
that's
why
that's
why?
If
I
get
a
thumbs
up,
then
I've
got
everything
I
need.