►
From YouTube: Hummingbot Foundation - Community Call #4 | May 2022
Description
Learn about the latest updates in Hummingbot Foundation.
Be part of a growing community of developers, traders, & project managers who strive to build reliable liquidity solutions in the crypto market making space with Hummingbot.
0:07 Welcome
0:38 Important Notice | NO TOKEN SALE
1:20 April Approved Proposal
2:27 April Created Proposal
2:54 Epoch 1 HBOT Allocation
3:58 HBOT Reward Schedule Page
4:50 Coming up in Hummingbot Foundation
11:40 Technical Review DAO
15:07 Technical Review DAO Report
19:58 AMA
A
Right,
okay,
everything,
fine
welcome
everyone
to
another
community
call
we,
as
always
on
this
one
we're
going
to
go
through
what
happened
on
the
humbot
project
and
what
we
are
planning
to
do
for
the
next
weeks.
So
and
as
usual
at
the
end
of
the
presentation,
the
mic
is
open
to
anyone
from
the
community
to
just
join
and
ask
questions.
Add
any
comments.
Anything
you
guys
want
to
talk
about
as
usual,
a
quick
warning
that
humboldt
foundation
haven't
done
and
will
never
do
a
token
sale.
A
So
all
the
tokens
will
be
is
about
to
be
held
by
the
community
and
we
are
hold
on
okay
and
all
tokens
will
be
distributed
to
the
community
and
through
the
governance,
proposals
and
participation
on
it.
So
if
something
appears
that
saying
that
we
are
selling
tokens
talking
say
so
it's
probably
scam,
so
don't
don't
join
any
of
these.
A
So
a
quick
go
through
the
governance
proposals.
What
was
the
state
in
what
happened
on
the
last
month?
So
last
month
we
had
an
approved
proposal
that
is
the
air
drop
of
hbo
tokens
to
community
developers.
So
we
have
two
million
allocated
with
days
being
allocated
until
the
end
of
the
year,
and
the
whole
goal
here
is
that
we
want
to
incentivize
developers
to
participate
on
the
on
the
dev
grants
proposal.
A
Any
other
initiatives
that
we
have
and
since
the
minimal
amount
to
create
a
proposal,
an
improvement
proposal
that
would
allow
to
participate
in
that
grant
is
10k.
So
we
are
distributing
the
the
10k
for
each
developer
that
have
created
at
least
one
pull
request
to
the
humminbot
repository.
So
we
do
have
a
fix,
a
topic
on
commonwealth,
if
you
guys
want
to
learn
a
bit
more
about
it,
how
to
how
to
request
the
tokens.
A
So
last
time
I
checked,
there
was
no
ongoing
proposal,
at
least
not
governance
proposal.
There's
a
few
other
ones,
the
related
to
dev
grants
and
pull
requests,
but
yeah.
Well,
it
will
take
too
much
time
to
go
through
all
of
them.
A
So,
but
if
there
is
any
specific
ones
that
anyone
for
the
community
want
to
discuss
feel
free
to
bring
it
up
at
the
end
of
the
the
meeting
right
so
recap
of
what's
the
current
allocation
of
the
tokens
for
these
epochs,
so
we
do
have
30
million
allocated
to
be
distributed
to
the
end
of
june,
and
we
have
19
million
already
approved
for
budget
allocated
already
into
across
initiatives,
budget
and
dev
grants,
and
there
is
still
10
million
open
for
proposals.
So
anyone
from
the
community
can
create
ravenous
proposals.
A
So
if
anyone
have
an
idea
check
back
to
the
to
the
rules
that
we
have
established
on
the
homepage
on
the
humbot.org
and
if
you
want,
if
you
want
to
see
the
details,
how
each
allocation,
how
each
how
each
proposal?
What's
the
budget
for
each
proposal
check?
Also
the
humbot.org
is
inside
governance.
We
have
a
detailed
approved
list
of
the
approved
proposals
for
by
epoch
right.
A
So
a
few
updates
is
that
we
now
we
created
last
month
reward
schedule
page
where
we
are
listing
all
the
approved
proposals
and
all
the
the
the
rewards
that
foundation
will
be
sending
to
the
community
across
the
whole,
the
whole
epoch
and
then
the
holidays.
A
And
so,
if
you,
anyone
from
you,
guys,
see
this
riot
schedule
and
we
are
expecting
to
receive
some
reward.
But
it's
not
on
that
list,
reach
us
out
and
we
can
check
it
and
add
the
reward
payment
to
that
list
right
and
if
you
want
to
wonder
where
you
want,
you
want
to
find
out,
there
is
a
fixed
match
message
on
the
announcements
channel
on
discord
with
the
the
proper
link
to
the
rewards
schedule
page
right.
A
So
let's
talk
a
bit
about
what
the
foundation
is
working
on
and
what
can
be
expected
for
the
for
the
this
month.
So
we
can
start
with
one
that
probably
a
lot
of
people
have
been
asking
is:
when
are
the
rewards
going
to
be
sent?
A
So
we
work
it
on
a
process
that
we
want
to
streamline
the
payment
process
of
the
rewards
right.
So
currently
we
all
the
rewards
started
on
the
main
treasure
wallet
with
three
out
of
five
modsig
safe
and
we
are
moving
into
a
less
restricted
mood.
Sig,
that's
going
to
be
sent
to
that's
going
to
be
used
to
create
the
transactions
to
send
the
rewards
to
each
one
of
you
that
are
expecting
them.
So
the
idea
is
that
this
reward
payment
payment
wallet.
A
We
only
contain
the
funds
that
have
been
approved
via
via
a
governance
proposal,
so
the
moment
that
the
government's
proposal
with
a
budget
allocated
to
it
is
approved.
We
move
it
to
the
reward
payment
wallet
where
it's
easier
and
and
faster
for
the
foundation
to
to
create
the
proper
transaction
to
the
final
wallets
that
we
have
on
the
rewards
schedule
right.
A
Another
thing
that
we
are
working
on
is
to
restructure
the
way
that
we
are
working
with
projects
and
ideas
that
are
more.
How
do
I
say,
increase
a
bit
of
the
flexibility
of
the
projects
and
idea.
A
So
one
point
that
was
we
are
working
is
to
create
a
structure
where,
instead
of
having
governance,
proposals,
allocating
budgets
to
projects
with
a
very
tight
description,
we
want
to
create
a
structure
that
basically,
we
set
up
two
types
of
standardized
dials,
one
that
we
are
calling
maintenance
dials
that
are
dials
that
will
be
will
exist
for
a
longer
period
of
time
and
will
deal
with
cyclical
tasks
and
is
going
to
be
the
participants
of
this
dow.
A
The
initiative
is
to
have
them
elected
for
periodically,
so
every
epoch
we
would
have
a
dow
election
and
then
anyone
for
the
community
could
join,
and
the
prime
example
of
that
is
is
what
is
happening
with
the
tech
review.
A
Dao
right,
where
we
have
the
objective
of
tech
review
dao,
is
to
help
the
rest
of
the
community
with
the
pull
requests
and
proposals
that
are
being
created
to
review
the
code
that
been
sent
and
add,
suggestions
of
improvement
and
changes,
and
the
idea
is
that
this
dao
will
keep
existing
every
epoch
and
and
through
each
epoch,
they
they
will
be
elected
by
community.
Who
is
going
to
be
part
of
it
and
and
that's
kind
of
the
base
idea
of
have
this
concept
now?
A
The
other
idea
is
that
we
want
to
create
the
standard
to
project
based
dials
right.
So
it
is
that
we,
if
we
have
an
idea
both
from
the
foundation
or
other
community,
that
have
a
specific
end
goal,
have
a
specific
deliverable
at
the
end
of
that,
we
want
to
have
this
structure
where
we
want
to
have
this
project
dials
that
we
will
exist
only
during
the
time
until
the
the
defined
objective
is
finished.
A
So
this
is
that
we
have
one
initial
election
for
the
members
and
and
from
there
the
until
the
end
of
that
project,
the
project
is
closed
and
then
the
the
those
that
are
elected
for
this
project
that
is
going
to
be
the
one
responsible
to
to
delivering
that
what
was
proposed.
So,
as
I
mentioned,
the
idea
is
that
the
the
objective
that
the
dow
is
pretty
specific
and
it's
temporary.
A
So
once
the
objective
is
achieved,
the
dow
is
closed
and
we
do
whatever
is,
is
proposed
on
the
to,
for
that
doubt
to
exist
an
example.
That
is
something
that
we
started
to
discuss
would
be
options
model
down
right.
So
with
the
cl,
it
have
a
clear
objective
to
create
a
model
inside
the
humbot
clients
that
allows
users
to
create
strategies
related
to
options
trading
and
then
so
the
objective
is
this
and
then,
once
that
model
is
created,
the
dow
will
be
closed
up
and,
as
the
objective
was
achieved
right.
A
So
there's
two
details.
We
are
working
on
this,
but
you
guys
can
expect
that
on
the
following
days,
we
will
create
some
commonwealth
threads,
take
describing
what's
our
initial
idea
and
bring
to
the
rest
of
the
community
to
discuss
what
would
be
the
better
way
to
implement
this,
this
type
of
dials
right.
A
So
we
also
working
on
a
foundation
roadmap.
So
we
want.
The
idea
is
that
we
want
to
establish
a
more
clear
direction.
What
the
foundation
is
thinking
about
the
humbot
project
as
a
whole,
and
also
open
up
the
opportunity
to
the
community
to
have
a
more
direct
and
more
straightforward
discussion
about
what's
on
that
foundation
and
how
we
can
make
it
better
and
improve
from
the
from
our
initial
the
foundation
issue
idea
so
also
partnership.
A
We
are
always
constantly
working
with
both
exchanges
and
and
all
types
of
projects,
both
centralized
and
decentralized,
trying
to
to
close
up
some
partnerships
where
the
community
itself
can
can
be
can
how
they
describe
it.
Participation
in
general,
like,
for
example,
like
we
already
have
with
some
centralized
exchanges
and
some
of
the
other
decentralized
that
we
are
talking
to
implement
some
taxes
into
the
humbot
and
also
the
documentation
improvements.
That's
something
that
we
have
been
discussing
a
lot
internally.
A
We
know
that
our
documentation
still
need
a
lot
of
improvement
and
we
are
organizing
ourselves
and
trying
to
figure
out
a
better
way
to
to
to
improve
and
including
the
participation
of
the
community,
to
to
make
the
documentation
better
for
both
users
and
developers.
Right
now,
let's
talk
a
bit
about
the
tech
review
now
because
they
it
started
to
work
a
few
months
ago.
A
So
a
quick
explanation
why
it
exists
and
what's
the
structure,
so
we
do
have
a
2.5
million
h
bot
allocated
to
it.
The
idea
of
this
now
is
that
the
it
is
self-directed
independent
right
from
the
foundation.
A
What
the
foundation
did
with
the
proposal
that
was
created
was
to
establish
what
is
the
the
goals
that
technical,
revo
dao
must
achieve,
and
the
five
members
that
currently
is
part
of
the
technical
review
dial
have
been
elected
through
improvement
proposal.
I
think
it
was
two
months
ago.
I
don't
remember
the
date
exactly,
but
that's
kind
of
the
the
point,
so
the
just
a
quick
review
of
what
is
the
responsibilities
of
the
technical
review
of
the
dao
right.
A
So
it's
to
review
all
the
incoming
pull
requests,
preferably
before
there
is
a
pull
request
proposal
created
to
it
right
so
before
the
pull
request
proposal
is
created.
The
idea
is
that
the
technical
review
now
go
through
the
code.
Talk
to
the
the
developer
that
submitted
suggests
improvements
to
the
code
and
add
a
comment
to
the
pull
request
to
help
those
that
just
don't
have
the
technical,
the
technical
knowledge
to
go
through
the
code
to
understand.
A
What's
inside
that
pull
request.
So
it's
both
to
help
the
developer
that
created
it
to
send
and
and
improve
the
code
contribution,
and
also
to
the
other
other
users
for
the
community
to
have
a
better
understanding
what
the
progress
is
about
and
make
a
better
decision
to
vote
if
the
that
pull
request
should
merge
or
not
into
the
code
base
right
and
also
another
responsibility
that
we'll
go
through
on
the
next
slide
is
that
they
will
always
to
be
reporting
to
the
rest
of
the
community.
A
What's
the
state,
what
they're
doing,
because
it
is
important
that
everyone
all
the
whole
ecosystem
understand
what
the
why
the
what
they
are
doing
and
how
is
the
the
the
tokens
that
are
being
used
if
they
are
actually
doing
what
they
are
supposed
to
do
right
and
right,
like
a
mission
helping
developers
with
technical
information?
B
A
Request
guys,
could
you
guys,
please
just
silence
your
mic
before
until
the
end
of
the
presentation?
Thank
you
all
right.
So
we
do
have
the
tech
review
down.
So
if
anyone
from
the
tech
review
wants
to
talk
a
bit
about
it,
the
report,
what
have
been
done
feel
free
to
to
join
and
talk
a
bit
about
it.
B
Hello,
paulo,
I
I
would
like
to
do
that,
but
currently
it's
very
difficult,
because
I
cannot
even
listen
myself.
Is
there
a
way
to
mute
everyone
in
the
in
the
meeting
there
we
go.
Thank
you.
A
B
It's
okay,
it's
working
out,
yeah!
Thank
you
for
the
presentation,
hello,
everyone.
My
name
is
abel.
I
am
part
of
the
technical
review
now
and
we
wanted
to
share
with
the
community
and
what
has
been
our
our
first
month
of
working
and
in
general,
we
have
here
the
numbers
we
have
been
working
on,
63
pianos
in
total,
many
of
them
were
pre-existent
they
they
did
not
all
arrive
during
this
month.
B
So
we
took
a
bunch
of
pr's
that
were
already
present
in
in
coins
repository
in
the
coming
repository
and
when
we
we
started
working
and
the
distribution
is
that
we
have
a
approved
a
18
years
during
the
month,
and
we
we
discarded,
12
and
many
of
them,
because
they
they
didn't,
have
a
information
enough
information
or
there
was
a
prp
missing
or
we
were
missing.
We
were
not
receiving
any
response
from
the
from
the
user
from
the
developer
in
a
long
time
after
the
initial
requests.
B
B
Only
three
and
most
of
them
were
rejected,
mainly
because
either
they
were
doing
some
repeated,
a
functionality
that
was
also
including
another
pr
or
because
they,
the
apr,
was
my
form
a
point
into
the
master
branch.
Instead
of
the
development
branch
we
have
still
26
pending
appears
pending
painting
review
at
the
end
of
the
month.
So
that's
our
initial
backlog
for
the
for
the
next
month,
from
the
approved
years,
the
the
18
approved
brs
10
have
been
already
merged
into
the
development
branch.
B
So
that's
that's
a
we
have
a
50
merch,
a
pr
status
right
now
and
also
before
we
finish.
We
wanted
to
share
a
as
a
with
everyone,
some
considerations
that
are
important
when
you
are
sending
pr's
for
the
for
the
to
to
be
to
be
considered
for
mercy,
please
remember
to
use
development
as
the
base
branch
for
any
any
contribution.
Pr
also,
please
provide
full
description
of
the
changes
being
done,
so
it
should
be
enough
information
for
anyone
in
the
community
understanding.
B
What's
the
the
pr
intention-
and
also
please
include
in
information
for
for
qa
team,
to
be
able
to
to
test
the
pr
and
currently
check
it's
working.
Please
include
the
link
to
the
prp
in
the
pr
we,
it's
not
a
requirement
for
the
technical
to
start
reviewing
it,
but
at
some
point
to
approve
it.
We
we
need
to
see
that
the
prp
is
is,
is
already
created
and
it
has
been
linked
and
also
remember
that
all
pr
should
pass
the
validation,
workflow,
the
automatic
workflow
that
runs
so
that's
important.
B
It
will
mainly
check
a
unit
test.
All
the
units
are
running
in
green
and
also
it
will
check.
The
minimum
coverage
requirement
has
been
fulfilled
in
the
pm,
so
that's
also
something
important
to
to
keep
an
eye
on
and
if
you
are
working
on
connectors
or
you
are
interested
on
on
providing
any
new
connector
to
the
community
version
of
the
open
source
solution.
B
Please
remember
that
you
should
be
following
the
standards
specified
by
the
golden
templates
that
are
binance
for
the
spot,
connectors
and
binance
one
for
the
perpetual
connectors.
If
you
send
the
any
any
pr
for
a
connector.
That
does
not
follow
those
standards
it,
it
will
be,
it
will
be
a
either
either
rejected
or
changes
are
gonna
be
requested
to
bring
bring
the
new
connector
to
the
to
the
latest
status
and
that's
everything
from
the
technical
review
for
for
the
for
april
thanks.
Everyone.
A
Thank
you
abel
for
the
presentation
and
that
pretty
much
closed
our
community
call
presentation
for
today,
and
so,
if
feel
free,
everyone
feel
free
to
mute
yourself.
Ask
questions
that
comments
and
anything
you
want
to
talk
about.
A
One
last
thing
I
forgot
to
mention
when
I
was
talking
about
the
the
process
of
reward
payments
is
that
we
are
already
working
on
start
sending
the
approved
rewards
that
we
have
on
the
reward
schedule.
A
So
by
the
end
of
the
week,
we'll
probably
have
already
start
to
to
you,
whoever
whoever
is
eligible
to
receive
some.
Some
tokens
will
start
to
to
see
them
reaching
up
their
wallets
right.
So
yeah
the
mic
is
open,
so
anyone
feel
free
to
jump
in
and
and
talk.
A
Come
on
no
question,
nothing,
nothing!
So
all
right:
okay,
okay,.
B
A
B
B
A
A
A
Here:
okay,
let
me
check
if
it's
working,
yeah,
okay
right
so,
like
I
said
we
do
have
inside
a
commonwealth
forum,
a
thread
that's
fixed
here
on
the
top.
So
here
inside
the
thread,
we
do
have
the
link
to
the
proposal
itself
right.
So
if
you
want
to
guys
want
to
take
a
look
at
it
with
more
details-
and
here
we
have
the
eligibility,
so
we
do.
You
need
to
have
sorry
for
the
misspelling,
a
github
account
a
discord
account
at
least
one
pull
request
targeting
the
humbot
client
repository
right.
A
So
the
pull
request
could
be
a
node
pull
request
or
it
can
be
a
new
one.
It
doesn't
matter.
What
we
want
to
do
is
to
anyone
that
contributed
both
in
the
past
or
will
contribute
in
the
future
to
be
allowed
to
get
this
token,
so
they
can
have
10kh
bot
tokens,
so
they
can
also
create
proposal
related
to
the
dev
grants
and
initiatives,
and
here
you'll
see
a
link
to
the
to
the
form
that
you
need
to
to
fill
with
your
information.
A
Yes,
nice,
so
here
we
just
enter
your
information
and
including
the
the
address
where
you
want
to
receive
that
sagebot
tokens,
and
then,
with
that
we
are
building
another
list
with
the
all
these
information.
So
we
will
start
to
also
send
the
the
10k
tokens
to
anyone
that
have
contributed
the
to
the
token
so
yeah,
it's
kinda,
it's
pretty
simple,
just
fill
out
the
form
and
we
you
will
be
sent
the
the
tokens
so
to
create
proposals
enough
to
create
the
proposals.
A
Right,
I
guess
that's
it,
then
anyone
else
last
last
chance
to
to
say
a
word.
A
Hey
hello,
hi:
this
is
this:
is
you
so
I'm
actually
the
developer
and
founder
of
the
setabus,
so
so.
B
I
noticed
that
the
hi.
A
Okay
hold
on,
I
think
we
have
some
delay
between
guys.
So
freddie,
you
is
talking,
so
you
just
you
talk
about
after
him
right.
A
Sorry
fedex
I
had
to
mutu,
I
think,
there's
some
delay
happening
here,
but
yeah
go
on
you.
They
know
omu
I'll.
Let
feder
talk
later
sorry.
A
A
I'm
is
talking,
but
I
think
I'm
sorry
you
we
are
lost,
we're
losing
you.
A
Fate
you
are,
I
mean,
like
he's,
meaning
I
mean
it's
because
my
my
id
is
you
so
he's
not
talking
to
you
he's
talking
to
me.
A
B
Oh,
that's
yeah.
B
A
Yeah
you're
free
to
talk
okay,
so
I
just
wondering
that
when
will
the
humminbot
support
the
polygon
network
for
the
liquidium
mining
and
the
other
stuff
like.
A
Right
one
one
thing
about
the
liquidity
mining
part:
I
can't
answer
for
that
because
that's
part
of
coin
alpha
we
are,
we
are
separate
entities
right
now,
so
anything
related
to
the
liquidity
mining
itself.
You
need
to
reach
out
to
the
queen
alpha
guys,
support
to
ask
them
how
how
they're
going
to
work
on
that.
B
B
And
that's
binance
coin
get
there
on
the
centex.
We
are
working
on
an
amm
kind
of
product
which
we
hope
to
launch
in
the
next
like
one
to
two
months,
so
we
so
we're
initially
supporting
avalanche.
But
as
for
future
plans,
we
have
to.
We
have.
A
In
the
future,
right
awesome
and
about
the
connector,
maybe
federico
fawzi
can
give
an
update
with
that
of
the
polygon
connector.
Well,
I
know
we
do.
We
did
have
merged
the
gateway
v2
code
into
the
main
code
base.
So
if
one
of
you
guys
could
give
an
update
of
the
polygon,
if
you
have
any
any
status
of
that.
B
A
A
B
A
A
Yeah
we
got
lost
from
the
from
fawzi.
I
think
he
had
a
bad
connection,
but
what
he
said
basically,
is
that
there
is
some
apparent
there
is
someone
from
the
community
already
working
on
a
polygon
connector.
I
have
to
check
later.
Who
is
going
to
to
be
on
that
one
but
they're?
Probably
since
we
did
the
the
gateway
v2
merge,
my
bet
would
be
that
they
are
probably
close
to
adding
it
to
the
to
the
code
base.
So
yeah,
I'm
not
sure.
A
I
think
the
best
way
to
reach
out
is
on
the.
We
have
the
dev
channel
on
the
on
our
on
our
discord,
and
maybe
we
can
ask
around
to
see
who
is
developing
that
one
yeah.
This
is
a
community
initiative,
the
polygon
connector,
so
yeah.
We
need
to
check
with
the
rest
of
the
community
if
there's
anyone,
that's
working
on
that,
want
to
jump
in
and
give
an
update
of
it
so
feel
free
to
to
talk
a
bit
more
about
it.
A
Right:
okay,
let
let's:
let's
do
that:
let's
do
that
I'll!
Try
to
reach
out
to
the
community
devs
to
see
if
we
can
find
a
way
to
organize
these,
these
initiatives
that
these
developers
are
working
on
and
try
to
find
a
way
if
we
can
kind
of
have
a
list
or
something
where
we
can
show
who's
working
on
it,
and
how
is
the
state
of
these
connectors
yeah?
That's
that's
something
interesting!
A
We
we
we
could
do
yeah
once
we
we
do
that
we
can
reach
out
to
to
make
easier
to
find
this
information.
A
Okay!
Thank
you!
So
much
yeah!
That's
all
my
question
right,
okay
and
last
chance
for
anyone
to
join
so:
hey,
paul,
okay,
hey.
B
B
The
gateway
v2
has
been
merged
into
development
recently,
so
it
it
has
been
thoroughly
tested.
B
B
I
don't
think
it
should
be
used
as
a
a
as
a
production,
a
production
ready,
a
code
yet,
but
I
think
I
I
in
my
opinion
it
will
be
soon
stacy
enough
to
consider
production
ready,
so
yeah
still
still
use
it
with
a
little
bit
of
caution.
B
Please
great,
and
what
would
you
say
that
are
the
main
problems
in
the
gateway
v2
right
now
so
far
we
haven't
seen
any
problems
there
in
the
gateway
itself
and
we
are
still
working
on
on
making
interaction
between
the
amm
arbitrage
strategy
in
the
client
side
with
the
gateway,
and
here
we
a
little
bit
more
smooth.
B
We
have
seen
that
at
time
and
there
are
some
times
where
there
could
be
a
couple
of
transactions
trying
to
try
to
to
be
executed
at
the
same
time
and
maybe
the
nonce
manager
on
the
gateway
having
having
troubles
with
particular
scenarios.
But
these
are
not
the
scenarios
that
are
happening
very
very
frequently,
and
so
this
we
can.
We
can
say
that
these
are
both
our
cases
scenarios.
B
In
any
case,
we
are
still
working
on
on
solving
on
solving
those
particular
situations
in
the
code
and
we
hope
in
the
in
either
at
the
end
of
this
sprint.
That
is
ending
this.
This
a
this
friday
or
maybe
the
end
of
next
week.
We
might
be
able
to
have
all
those
a
all
those
border
cases
sold
in
the
development
branch.
B
A
A
We
have
a
section
about
gateway
with
all
the
instructions
to
set
up
and
and
run
it
and
test
it
right,
but
so
yeah
as
usual,
like
a
bell
mentioned,
it's
still
the
beta
phase
of
it.
So
make
sure
you
guys
take
your
take
precautions
to
to
test
it
and
don't
don't
don't
put
all
your
eggs
in
it
right
test
it
out
before
actually
doing
something.
That's
that
use
proper
trading
funds
that
you
guys
have.
B
I
wanted
to
make
one
quick
comment:
if
we
have
a
members
in
the
community
that
are
interested
in
seeing
a
particular
functionality
in
the
in
the
client
or
in
gateway,
but
you
are
not
developers,
please
feel
free,
and
I
encourage
you
to
also
propose
those
those
ideas
in
in
in
the
commonwealth
or
in
the
as
a
improvement
proposal,
and
because,
even
when
you
cannot
work
on
on
on
creating
them,
there
will
be
many
developers
in
the
community
that
might
find
your
ideas
interesting,
useful
or
nice
to
work
on,
and
they
will
be
happy
to
to
to
gather
them.
B
So
I
just
wanted
to
say
that
if
you
are
not
the
developer,
but
you
think
you
have
a
you
have
ideas
you
can.
You
can
propose
by
all
means,
go
ahead
and
I'm
proposing.
A
Yes,
that's
true,
that's
true
governance.
Governance
is
for
everyone
participate,
even
if
you
you
are
not
developer.
You
can
always
go
and
suggest
project
improvements
on
the
code
base
and
some
developer
can
pick
it
up
and
start
working
on
it.
B
Or
the
foundation
can
can
at
some
point
find
a
particular
idea
very
interested
or
required,
and
there
will
be
grants
for
the
developer
to
to
take
them.
So
there
are
many
possibilities
that
in
in
all
ways
in
which
an
idea
can
can
be
executed,
so
don't
refrain
yourself
from
from
from
publishing
them.
A
Thank
you,
everyone
again
for
coming,
and
as
always,
so,
even
though
we
do
this
this
presentation
only
once
every
month,
if
any
other
questions
arise,
if
anyone,
if
you
need
any
help
with
anything
related
to
both
governance,
development
or
anything
like
that,
feel
free
to
reach
out
for
the
for
the
foundation
team,
and
we
are
always
willing
to
to
send
you
on
the
right
direction
and
our
main
goal
as
to
remember
is
that
we
want
to
make
the
hanbok
client
the
best
trading
client,
open
source
and
free
that
exists
on
the
on
the
crypto
and
for
that
to
be
possible.
A
We
one
of
the
the
k,
the
key
things
to
that
is
the
the
strong
community
that
we
have
and
the
contribution
that
from
both
developers
and
both
traders
and
and
everything
involved
into
it
so
feel
free
to
reach
us
out.
We
can
help
you
with
anything
that
you
need
and
that's
it.
Thank
you
all
for
coming
great
coming
to
call
for
this
month,
and
I
see
you
officially
next
week,
but
I'm
always
around
discord
so
feel
free
to
reach
me
out
also
bye.
All.