►
Description
This week the Antelope Coalition updates the community on progress on the Scalability+ Blue paper, IBC governance, Developer onboarding, Wallet SDK, Ledger maintenance and more!
Antelope Coalition Summary Notes 10_20_22
00:00:00 Start
00:00:10 Reprioritization of top development items
00:23:00 Scalability+ Blue Paper
00:23:27 RFP Secure smart contract library
00:25:40 IBC Governance
00:26:28 Developer onboarding / development workshops
00:28:10 Instant Finality / IBC approvers / champions
00:34:40 Wallet SDK approvers / champions
00:40:20 Adding new chains to the coalition
00:44:23 Ledger app maintenance
00:52:30 End
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.eosnetwork.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
All
right,
everyone
we've
got
the
board
up,
we'll
just
start.
The
first
item
today
is
the
re-prioritization
of
the
top
development
items
for
the
coalition,
so
I'm
going
to
switch
over
and
share
the
voting
that
was
done
by
the
chains
and
you
you
can
see
on
the
screen
now,
there's
a
number
that
were
selected.
The
points
were
distributed.
There
were
16
points
for
the
16
items,
but
this
shows
the
waiting.
A
A
B
Four
of
them,
which
are
higher
in
point
and
of
those
there's
peer-to-peer
board,
read
write
which
we've
already
done
on
RFP.
So
we
could
either
do
three
rfps,
which
would
be
the
smart
contractor,
willing,
abolition,
the
ram
limitation
fixes,
provable
State
domains,
or
we
could
add
a
fourth
one,
which
would
also
be
adding
reference
thoughts,
but
either
way,
I
only
see
three
or
four
rfps
being
written.
B
C
B
We
we
currently
are
starting
to
work
on
this
okay.
If
it's
not
us,
then
somebody
else.
We
believe
it's
important.
We
have
a
general
idea
of
what
we
would
be
doing
if
this
went
out
as
RFP
we'd
bid.
Just
like
everybody
else,
we've
got
our
proposed
solution
to
this.
This
was
still
highlighted
in
the
core
plus
blue
papers.
Just
that
there's
somebody
in
the
team
that
is
particularly
good
at
this
and
wants
to
work
on
this,
and
so
we
would
be
assigning
resources
to
it.
B
C
Yeah
speaking
for
for
ourselves,
essentially
like
there's
a
I
guess
like
so
far,
people
are
still
using
the
the
block
one
documentation
as
the
I
guess,
like
main
point
of
reference
and
it's
starting
to
deviate
from
the
code
base
quite
a
bit.
So
there's
a
few
things
that
are
mentioned
there
that
are
no
longer
applicable
and
I
guess.
With
the
new
software,
the
leap
3.1
3.2,
we're
kind
of
moving
away
from
like
yeah.
It's
basically
a.
C
D
C
E
Think
it's
pretty
complete.
What
we're
still
planning
on
doing
and
we've
just
been
resource
constrained,
is
pushing
a
version
out
to
docs.antelope.io
and
then
we're
going
to
start
we're
going
to
start
diverging
so
that
they're
not
going
to
look
almost
similar
and
so
like.
But
but
at
that
point
our
documentation
team
is
not
going
to
work
on
docs.antelope.io.
E
There
will
be
the
the
stuff
that
is
living
inside
the
leap
repo,
obviously,
and
whenever
we
change
any
documentation
there
it'll
be
changed,
but
there
needs
the
generator
has
to
run
and
and
push
it
out
to
docs.enelope.io
and
again
until
we,
we
figure
out
some
way
to
pay
for
that
Etc
or
have
some
people
do
that.
We,
our
Engineers,
will
update
the
the
document,
part
that
lives
inside
the
leap
repo,
but
they
won't
necessarily
run
the
generator
and
push
it
out
there.
E
We
will
open
source
the
generator
and
make
that
available
to
you
know
to
Antelope
as
well,
but
this
is
where
we'll
have
to
decide
how
funding
Works,
who
does
it?
But
you
know
we'll
give
the
part
pieces
and
all
that
and
we'll
make
we're
going
to
make
an
initial
push
to
it.
So
it
exists
and
snap
the
chalk
line
and
then
say
it's
up
to
the
Coalition,
then
to
figure
out
how
to
fund
and
pay
for
any
of
that.
Moving
forward.
C
D
I
think
my
I
guess
I'm
going
to
leave
too
I
mean
probably
that
can
make
a
difference,
but
it
sounds
like
there
does
need
to
be
some
effort.
Funding
put
into
the
either
maintenance
of
docs.antelope.io
I
mean
that
would
be.
My
instinct
is
to
support
the
needs
required
so
that
docs
at
antelope.o
gets
the
generator
ran
regularly,
and
you
know
wire
up
whatever
CI
CD
pipeline
stuck
needs
to
be
done.
So
that's
not
gonna
Fall
by
the
way.
So
right.
E
E
Today
we
haven't
even
like
put
the
hardware
out
there
for
Antelope
yet
and
everything,
and
it's
just
a
matter
of
Nathan's
team,
allocating
Cycles.
They
have
a
major
launch
that
they're
doing
towards
the
end
of
October.
So
it's
it's
just
not
been
a
priority
yet,
but
you
know
they
will
get
that
I.
Don't
know
if
they'll
also
hand
over
the
CI
CD
and
that
way
when
the
developers
update
the
headers
and
stuff
or
or
even
the
the
headers
and
C
plus
code
or
the
stuff.
That's
in
the
docs
subdirectory
of
leap.
D
E
E
We
have
a
DNS
setup
in
there
that
that
you
helped
with
so
once
it
gets
to
be
of
reasonable
cost,
we'll
probably
build
it
back
into
the
Coalition,
maybe
once
a
quarter
once
every
six
months,
something
like
that
and
because
it's
not
going
to
be
that
expensive,
for
you
know,
basically
one
or
maybe
two
hosts
in
a
load
balancer
just
doing
sure
that
it's
you
know,
got
higher
reliability.
This.
E
D
D
D
E
C
D
E
I
mean
if,
if
Guillaume,
if
you
had
some
people
that
were
willing
to
do
a
little
bit
of
work
on
it,
it
would
be
great
right
because
then
you
guys
could
just
donate
that
time
into
your.
You
know:
fees
for
the
Coalition
and
just
maintain
it,
because
there's
just
going
to
be
a
CI
CD
pipeline
that
runs
a
generator
every
time,
there's
a
push
to
either
the
the
docs
subdirectory
or
you
know,
anytime.
A
header
changes.
You
gotta
re-scrape
it,
because
that
means
that
you
know
where
we're
at
yeah.
You
get
it
yeah.
F
C
D
F
D
D
A
E
Well,
I
mean
we
kind
of
have
that
what
we
we
owe
meaning
we,
the
enf,
oh
a
deliverable-
that
Nathan
is
just
you
know
a
little
bit
resource
constrained
to
do
and
then,
from
there
it'll
be
more
this
discussion.
You
hear
Guillaume
and
Jesse
and
Lucas
talking
about
of
okay.
How
do
we
maintain
it
going
forward,
but
we
haven't
delivered
the
Baseline
yet
of
right
here
it
is,
and
you
know,
look
it
works.
So
how
do
you
you
know
that
that's
the
next
step
is
then,
okay?
E
How
do
we,
you
know
be
on
the
CI
CD
pipeline?
There
might
be
a
desire
like
hey
we'd,
like
to
make
this
look
better,
oh
and
it
won't
be
designed
by
the
way
it'll
be
kind
of
just
there,
and
so
someone
with
a
design
aisle
say.
Oh,
my
God
put
some
Chrome
around
that
that
looks
like
the
rest
of
the
antelope
site
and
so
someone
you
know
one
of
the
Coalition
members
might
say
we'll
step
up
to
that.
E
Like
we
one
of
the
questions
that
came
to
me
was
hey.
Can
we
just
move?
You
know
the
docs
directory
out
from
under
leap
and
I'm
like
no,
because
it
has
to
stay
in
the
Coalition.
They
were
going
to
just
bring
it
over
to
enf
I'm
like
then,
what
would
the
Coalition
use?
So
you
know
that
I
told
them.
Look
you
as
long
as
you
leave
stuff,
so
it'll
work
for
the
Coalition.
If
you
want
to
put
translators
and
filters
on
it
for
post-processing,
that's
great,
but
the
you
know.
A
F
E
I
have
some
feedback,
so
the
last
one
was
coming
in
so
expensive
and
the
duration
was
rather
long.
So
what
we've
been
working
is
to
cut
it
in
half,
so
it
used
to
have
a
network
discovery
portion
and
a
swarm,
download
portion,
and
so
what
we've
said
is
why
don't
we
do
the
network
network
discovery
portion?
First,
it's
pretty
brittle
code
and
and
a
lot
of
the
the
ogs
inside
enf.
The
developers
are
kind
of
saying
that
that
stuff
needs
to
be
fixed.
E
You
know
whether
they
just
take
it
on
themselves
or
it.
You
know
if
we
do
an
RFP,
so
that's
what
the
new
RFP
that's
coming
out
is
that
should
cause
the
bill
to
be
at
least
cut
in
half
we
had
a
previous
bid,
which
we
all
looked
at
and
said
was
too
high,
but
in
addition
there's
now
a
Chinese
University
that
is
also
willing
to
bid
and
obviously,
while
their
experience
with
the
project
is
a
lot
less,
the
pricing
will
be
better
and
I've
I've.
E
D
A
E
They
possibly
could
have
used
three
Engineers
instead
of
two,
but
you
know
I
think
that
if
we
get
that
change
in
with
you
know
requiring
the
transparency
of
how
the
bid
was
arrived,
you
know
how
the
numbers
were
created
along
with
it
just
being
the
discovery
portion.
So
we
we
are
working
to
get
that
text
reworked
so
that
it
is
just
the
discovery
portion
of
the
new
RFP.
Along
with
that,
the
new
requirement
of
hours
rates,
Etc.
E
E
A
E
C
A
C
A
A
A
And
then
we
did
go
over
the
items
this
week.
They
gave
us
a
great
overview
of
the
breakdown
I
published
that
into
the
Coalition
channel.
So
at
this
point
we
have
a
fairly
thorough
breakdown
where
it's
by
hours
by
roll
and
then
also
they
gave
us
the
hourly
rate
for
the
roles
themselves.
So
like
I,
don't
think
Douglas
warned
us
that
he
would
be
traveling,
so
he
was
not
able
to
join
the
Monday
meeting.
Ted.
A
E
A
A
C
So
for
that
part,
I
apologize,
I,
didn't
I
I
do
have
a
homework
on
that
providing
a
list
of
various
questions
to
be
answered
by
everyone
kind
of
come
up
with
the
final
I
guess
like
game
plan.
For
that
part
I
did
it
I
I
started
on
this,
but
I
didn't
finish
it.
So,
let's
just
put
that
up
for
next
week.
If
you
don't
mind.
A
C
C
C
We
do
have
the
audit
scheduled
pretty
pretty
shortly
I
think
originally
they
were
saying
the
the
team
was
saying
end
of
month
or
early
next
month,
so
that
should
be
should
be
happening
very
shortly
as
well.
I'll
follow
up
with
them
this
week
and
see
what
their
timeline
is,
but
I'm,
not
I'm,
I'm,
not
too
much
in
a
rush
because
essentially
like
The
Way,
We
Were.
C
Basically
looking
at
this
was
enf
review
would
come
first
and
then
we
would
have
the
audit
by
an
external
auditor.
So
if
we
don't
have
the
internal
review,
then
I
would
rather
delay
that
external
audit
a
bit
more.
We
are
still
progressing
on
the
on
the
Milestones
there.
We
have
basically
the
the
I
guess,
like
the
proof,
server,
pretty
much
ready
to
start
what
I
would
call
the
closed
beta.
So
we
will
be
essentially
discussing
with
a
few
teams.
C
I
already
showed
interest
in
helping
testing
it
out,
so
we
will
start
deploying.
We
actually
started
deploying
it
on
the
main
nets
for
for
now,
and
we
will
basically
like
be
onboarding
some
of
these
other
teams
to
test
it,
give
their
feedback
try
to
break
it,
find
issues
with
it.
So
that's
our
Milestone
that
is
scheduled
for
November,
22nd
I,
believe
so
so
we're
ahead
of
schedule
on
that.
C
One,
in
my
opinion,
so
we'll
see
we'll
see
how
that
goes,
but
so
far
so
good,
then
for
IBC
yeah,
like
that's,
that's
pretty
much
it
we're
waiting
for
the
the
review
from
and
like
after
that
point.
Once
we
released
this,
the
the
the
the
proof
server,
then
we're
transitioning
everything
pretty
much
to
instant
finality,
which
we
already
started
as
well.
C
Like
we're
already
working
on
the
institutionality
stuff
in
the
meanwhile,
so
for
the
instant
finality
stuff,
essentially
we
we
do
have
a
milestone
coming
up
next
week,
which
is
the
mathematical
proofs.
So
we
did
have
a
chat
with
the
enf
engineers
earlier
this
week.
So
that's
that's
pretty
much
covered
where
we
should
be
able
to
to
deliver
this
at
the
date
that
we
were
supposed
to.
C
But
we
do
have
the
same
kind
of
issue
where
this
is
subject
to
review
and
approval
by
the
AF
engineers
and
they
already
have
quite
a
big
backlog.
So
it
might
not
be
approved
or
reviewed
I
I,
my
estimate
would
be.
It
will
take
probably
another
three
weeks
to
a
month
minimum
before
they
get
to
that,
because
they
already
have
a
few
other
things
to
to
review
on
our
end,
plus
they
had
their
own
their
own
work
as
well.
C
Later
on
so
after
discussing
with
Eric
and
on
the
topic,
we
decided
to
also
throw
that
in
so
essentially
like
we're
broadening
the
scope
a
little
bit,
but
we
were
ahead
of
schedule,
so
it
doesn't
really
impact
much
and
it
will
allow
us
for
more
interesting
constructs
down
the
road
things
like
ZK,
snarks
and
other
zero
knowledge
proof
schemes
that
will
be
now
made
possible
with
this.
So
that's
going
very
well.
C
We
are
also
in
the
process
of
essentially
finalizing
some
decisions
with
regards
to
the
the
consensus
of
great,
like
the
consensus
model
upgrade,
so
we
call
it
instant
finality
between
us,
but
the
way
things
are
shaping
up.
It
will
be
a
variant
of
Hut
stuff,
which
is
the
consensus
algorithm
that
was
I,
think
planned
for
the
Libra
blockchain
and
that's
that's
pretty
much
Cutting
Edge.
C
That's
that's
pretty
much
like
the
the
most
the
most
interesting
consensus
model
that
exists
right
now,
so
it
will.
It
will
definitely
like
we
will
do
this
instant
finality,
but
we
will
also
have
other
benefits
deriving
from
that.
So
at
some
point
at
some
point,
we'll
write
them
down
and
we'll
discuss
them
with
the
with
everyone,
but
yeah,
it's
quite
exciting
stuff.
So
so
this
is
progressing
very
well,
it's
it
is
challenging.
This
is
not.
C
This
is
not
easy
stuff,
but
we're
doing
very
good
so
far,
so
quite
excited,
probably
in
a
few
weeks
we'll
be
able
to
discuss
it
a
bit
more
and
maybe
make
us
some
sort
of
presentation
where
this
is
going,
but
I
think
I
think
you
guys
will
find
it
very
interesting
as
well
and
I
think
I
think
that's
it
for,
for
instance,
finality
yeah
I
think
that
that
covers
it.
We
I
I
did
update
Adam
earlier
this
week
as
well.
B
Yeah
sure
we
had
our
first
meeting
this
week,
they're
going
to
be
reoccurring,
meetings,
the
time
slot
may
change
just
because
I
know
we
pushed
this
one
quickly
and
not
even
everyone
even
had
the
chance
to
respond
to
their
availability.
So,
but
in
this
initial
meeting
we
went
over
the
first
revision
of
the
architecture
document,
which
we
said
we
would
be
delivering
this
week.
It's
available
in
the
SDK
Channel.
B
It
is
going
to
be
a
living
document.
We
expect
multiple
revisions
throughout
the
course
of
this
project,
but
it
is
going
to
be
a
component
that
lives
in
kind
of
the
core
GitHub
repository
that
is
effectively
for
developers
to
get
kind
of
an
overview
of
the
architecture
of
this
project.
You
know
somebody
may
have
an
idea
for
the
ecosystem
they're
like
where
does
this
idea
fit,
and
this
document
should
help
them
navigate
where
it
should
fit
in
the
architecture.
B
So
there
is
a
bit
of
a
question
on
the
architecture
document,
because
this
was
a
milestone
as
to
when
it
is
complete
and
since
it's
a
living
document,
I,
don't
I,
don't
know
if
revision
one
means
complete
or
how
we
want
to
handle
that
I.
Think
that
that
is
going
to
be
a
topic
for
next
week's
call,
if
not
a
call
like
this,
but
some
sort
of
decision
needs
to
be
made
as
to
when
we
will.
A
The
three
Champions
on
this
are
Eve,
Guillaume
and
Jesse,
and
so,
if
the
three
of
you
determined
that
you
feel
it's
complete
enough
right
doesn't
have
to
be
perfect.
But
as
long
as
the
three
of
you
are
satisfied,
we'll
mark
this
as
complete
to
that
end.
Aaron,
you
might
want
to.
If
you
haven't
already
post
the
link
to
the
architecture
document
into
either
the
work,
the
working
group
Channel
or
perhaps
in
this
case
the
Coalition
channel.
It's
it's
really
up
to
you,
because
all
three
are
in
both
yeah.
B
B
B
B
I,
don't
know
what
the
the
others
were
on
that
call,
or
the
other
two
Champions
what
you
feel
because
it's
going
to
be
ongoing,
then,
like
Aaron
mentioned,
it's
never
really
gonna
be
complete,
but
based
on
what
I
saw
it's
complete
enough
that
and
there
was
no
significant
pushback
so
there's.
Basically
the
call
was
very
technical,
very
deep.
B
C
I
would
support
that
as
well
on
a
call.
We
also
had
Shaq
who's,
our
lead
developer
for
anything
front,
end
back
end
and
I
also
our
lead
Susan
men
for
all
the
infrastructure.
So
basically
he
does
everything
except
smart
contracts,
and
he
was
he
was
very
impressed
with
with
everything.
So
so
we're
we're
good
for
that.
B
Awesome
and
I'm
hopeful
that
this
is
the
only
kind
of
odd
Milestone
out
of
these
Milestones
and
I
guess.
My
last
thought
on
that
is
I.
Think
it's
complete
enough
to
proceed
forward
with
the
future
milestones
and
the
only
reason
we
want
to
kind
of
stress
that
it
is
a
living
document.
Is
that
as
we
move
through
this
process,
we're
probably
going
to
discover
things
that
have
to
go
back
and
modify
it,
and
that
will
be
a
part
of
those
future.
Milestones
is
kind
of
modifying
this
first
one.
A
B
Right
anything
else,
we
are
beginning
on
the
next
couple
milestones.
We
may
want
to
rearrange
a
couple
of
the
Milestones
due
to
discoveries
during
the
architecture
process.
We
are
kind
of
thinking
about
shuffling
things
around
that
doesn't
mean
that
any
Milestones
are
significantly
changing.
It
just
might
be
beneficial
for
us
to
start
on
one
of
the
further
Milestones
before
we
get
into
what
we
had
designated
in
this
current
timeline.
So
we
will
provide
some
updates
on
that
relatively
soon.
A
All
right,
we'll
set
down
and
I,
will
make
sure.
Adam
is
aware
that
that
milestone's
completed,
and
so
he
will
work
through
the
rest
of
that
process.
All
right.
One
thing
on
the
agenda
that
I
would
like
to
try
to
get
is
scheduling
the
the
Ford
chain
heads
it's
very
difficult
to
do
of
since
you're
all
here.
This
is
a
separate
meeting
on
discussing
the
process
when
a
new
chain
wants
to
join
the
coalition
and
Guillaume
you
wanted
in.
A
B
I
was
gonna,
say
today
we
met
the
four
chain
heads
actually
for
the
first
time,
just
four
chain
heads
and
we
met
at
a
right
before
this
call
so
one
to
two
that
time
slots.
If
we
wanted
to
do
that
again
works
on
land,
I,
don't
know
if
that
was
it
worked
on
everybody
else's
end
or
if
that
was
just
exceptional
today,.
C
B
C
It
might
make
sense
to
try
to
get
the
entire
time
slot
on
a
different
day,
just
just
like
a
kind
of
an
optional
one.
That
is
not
necessarily
gonna
take
place
every
week.
But
if
there's
at
a
items
that
we
need
to
discuss,
that
would
give
us
maybe
a
bit
more
responsiveness
because
having
the
two
of
them,
like
the
same
same
day
like
just
back
to
back
it's
a
bit.
It's
a
bit
slow
for
addressing.
F
D
B
B
B
A
B
B
F
B
B
Account
was
on
a
ledger:
it
was
stuck
there
forever
and
The
Ledger
team
after
enough
prodding,
that's
a
kind
of
not
the
right
word,
but
after
I
raised
the
issue
enough
times,
eventually
dedicated
their
own
resources
to
fixing
this
issue
and
I,
don't
think
they
want
to
repeat
that,
so
they
want
to
make
sure
that
we
as
a
community,
are
maintaining
this
application
and
have
some
form
sort
of
formal
contact
with
The
Ledger
team.
So
that
way,
this
is
an
app
moving
forward.
I
think
their
concern
is.
B
F
B
Support
volume
decreases,
so
it's
it's
kind
of
a
reboot
of
the
relationship
with
Ledger
I
feel
at
this
point
in
time,
and
they
would
not
release
the
issues
to
me
as
just
kind
of
a
wallet
developer
in
the
space
there
may
need
to
be
agreements
that
are
signed
so
that
way,
like
this
sort
of
confidential
user
information
that
they
have.
You
know
their
users,
reporting
vulnerabilities
and
issues,
isn't
getting
into
the
wrong
hands.
So.
F
B
None
of
them
are
supported
in
Ledger,
live
with
Ledger
live
being
their
wallet
interface,
but
all
of
the
chains
do
work
with
a
ledger
device
through
anchor
and
through
the
web
interfaces
like
blocks
gotcha,
so
so
this
would
be
an
antelope
thing,
but
I
guess
by
default
the
enf,
if,
if
it
deemed
that
it
doesn't
want
to
lose
that
vnf
would
just
pick
this
up.
Potentially
I
mean
that's
up
to
you.
B
B
Do
you
know
if
or
actually
anybody
else
on
the
call
do
you
guys
potentially
have
engineered
resources
that
we
could
put
in
touch
and
that
we
label
them
as
official
Antelope,
Engineers
or
whatever
it
is,
and
then
that
way
as
a
unit,
we're
kind
of
moving
forward
on
this
because
I'm
based
on
what
I'm
hearing
it
they
need
people,
it's
not
money.
They
money
may
also
be
the
thing.
B
I'll
just
add
this
as
a
resources,
they
have
a
list
of
recommended
vendors
that
they
work
with
that
they
could
put
us
in
contact
with
to
manage
the
app
Theo.
For
example.
Right
now
is
actually
working
with
one
of
the
ledgers
external
Partners
to
build
a
fio
app
that
goes
on
the
ledger,
so
I'm
in
that
discussion,
I've
been
watching
that
app
been
built
over
the
past
like
six
months
or
so,
and
that
is
a
potential
point
of
contact
that
could
manage
a
new
Antelope
app.
B
F
B
Can
it
be
awesome,
I
can
put
whoever
in
contacts
that
may
seem
more
official
than
me.
I
I
came
to
them
as
a
wallet
developer,
so
I
think
when
they
view
me.
They
see
me
as
just
kind
of
a
third
party
in
this
ecosystem,
so
they're
looking
for
I,
don't
know
some
better
point
of
contact,
I
guess:
Can
You,
Reach,
Out
Aaron
to
Eric
Passmore
about
this,
and
maybe
we
can
so
Eric
is
not
here.
B
So
I
can't
ask
him,
but
maybe
Eric
can
represent
the
enf
for
this
and
then
just
start
that
discussion,
just
he
has.
He
has
experience
with
yeah
and
I
I
think
that
would
be
a
good
contact
to
put.
Ultimately,
if
anything
needs
to
be
signed,
it's
going
to
need
to
be
me
anyways
sure,
but
that
way
we
we
don't
let
it
linger.
Yeah
I
can
send
Eric
a
message
and
see,
if
he's
willing
to
take
that
on
or
just
inform
him
of
the
situation.
Thank
you.
B
Yeah
that
sounds
good
and
the
reason
I
wanted
to
raise
it
today
was
I.
Wasn't
sure
if
you
guys
wanted
to
handle
this
as
an
RFP
or
just
as
a
kind
of
a
side
item,
it
is
probably
going
to
be
a
smaller
item.
I
don't
know,
though,
but
as
the
decisions
were
being
made,
I
figured,
it
was
probably
good
to
be
talking
about
it
or
at
least
raise
awareness
yeah.
Thank
you.
B
B
B
And
I
guess
just
to
add
to
that
conversation
that
I
had
with
them.
We
did
briefly
talk
about
future
Integrations
and
opening
up
Partnerships
and
being
able
to
do
more
with
Ledger,
but
in
this
initial
call
we
primarily
talked
about
just
getting
the
current
state
of
affairs
in
order.
So,
as
I
said,
this
is
probably
a
good
way
to
establish
that
relationship.
So
that
way
we
have
better
Hardware
support,
moving
forward
foreign
I'm.