►
From YouTube: Hummingbot Foundation Community Call #1
Description
This is the first community call by the Hummingbot Foundation.
Topic covered
- State of Hummingbot Community
- Governance Process Walkthrough
- Community Channels
0:00 Welcome
1:08 Community Call
4:44 Hummingbot User Advantage
5:30 Incentivizing Community Contribution
6:20 Fork-Friendly Software
6:45 Community Count
8:50 Volume of Liquidity provided
9:30 Self-Sustainability
11:30 Hummingbot Foundation as a DAO
16:30 HBOT Distribution through Rewards
19:26 Community Call Schedule
20:50 Governance System
42:15 Epoch
49:25 Community Tools
55:06 Questions
1:16:00 Wrap Up
A
All
right,
hello,
everyone
welcome
to
the
first
comment,
call
we'll
be
starting
it
soon.
So
just
a
quick
talk
about
welcome
everyone
that
join.
So
the
goal
here
of
the
community
call
is
to
do
an
update
of
what's
happening
on
the
governance
of
the
humboldt
foundation
project
and
at
the
end
of
the
call
we
will
open
up
for
anyone
who
wants
to
ask
questions
or
add
any
other
comments
that
you
think
it's
relevant
for
the
for
the
project
so
for
now
I'll
pass
through
to
mike.
A
B
Okay,
awesome,
hey
everyone
just
wanted
to
thank
everyone
for
joining
this
is
our
first
community
call,
but
going
forward.
We
wanna
do
this
every
month
to
basically
walk
through
the
what's
happened
in
every
release
and
discuss
the
proposals
that
happened.
You
know
in
them
because
the
the
financials
they
have
a
monthly
cadence
every
month.
We're
gonna
have
a
lot
of
proposals
that
the
community
approves
via
pro
quest
proposals,
governance
proposals
and
improvement
proposals,
and
so
every
month
we'll
be
doing
this,
but
the
first
one.
B
We
wanted
to
explain
how
the
foundation
works,
and
I'm
really
use
this
one
as
an
informational
session
for
everyone
who
wants
to
get
involved
and
contribute
to
humminbot
our
vision
of
an
open
source
liquidity
ecosystem.
So
first
just
explain
how
this
works,
as
you
guys.
May
you
guys
probably
know
coin
alpha.
The
company
that
originally
built
having
bought
has
spun
hummingbird
off
essentially
open
source
foundation.
B
B
So
what
that
means
is
foundation
is
going
to
partner
with
exchanges
to
build
connectors
and
those
connectors
are
maintained
by
individual
users
and
communities.
In
addition,
we're
also
going
to
try
to
incentivize
people
to
create
strategies
as
well,
and
we
believe
that
that
will
increase
the
number
of
users.
B
Meanwhile,
as
those
users
as
those
users,
you
know
like
higher
level
need,
for
example,
let's
say
they
want
to
run
boss
arms.
Let's
say
they
want
a
back
testing
engine
that
they
need
to
use
it
to
help
them
do
what
they
do.
That's
where
the
coin
out
then
so
coin.
Alpha
will
continue
to
be
a
for-profit
company
that
operates
the
minor
platform,
there's
also
a
hummingbike
pro
practicing
engine
that
they
have
out
and
and
overall
there's
other
businesses
and
networks
that
serves
the
needs
of
both
individuals
and
individualizations.
B
B
Similarly
in
the
blockchain
world,
we
have
ethereum
as
a
source
kind
of
you
know
core.
You
know
behind
behind
ethereum
the
foundation
anyway
and
then,
but
you
have
a
network
of
of
companies
around
projects
around
ethereum
that
are
kind
of
providing
research,
and
so
this
is,
I
think,
quite
awful
won't
be
the
only
company
in
this
ecosystem,
but
I
think
we'll
be
one
supporting
the
foundation.
B
Okay
next
slide,
please
follow
so
so
coming
back
today.
This
is
just
a
quick
recap
of
where
we
are
today,
so
it's
the
leading
open
source
framework
in
the
industry
for
building
crypto
cuts,
and
I
think
that
the
really
the
value
process
really
comes
from
the
fact
that
it's
integrated
to
as
many
exchanges
as
possible
in
industry.
So
we
really
started
with
centralized
exchanges,
binance
nifty.
B
We
now
have
a
number
perpetual
swap
exchanges
like
futures
dx,
and
currently
we
are
working
on
standardized
for
amm
indexes,
as
well
as
order
indexes
on
different
blockchains,
and
that's
that's
really.
The
gateway
project
we're
working
on
now
in
conjunction
with
the
community,
and
we
expect
that
to
launch
in
about
about
two
months.
B
So
so,
essentially,
what
we're
really
trying
to
do
is
build
interfaces
for
these
different
exchanges
to
allow
developers
to
add
connectors
to
any
exchange
they
want
and
have
that
fit
into
a
standardized
training
interface
that
can
work
any
of
the
home
and
on
the
strategy
side.
You
know
we've
added
a
bunch
of
strategies
and
I
think
the
focus
this
year
is
really
trying
to
incentivize
the
community
to
build
or
customize,
which
is
why
I
think
one
of
the
the
the
key
thing.
C
B
B
B
So
three
jane
I've
done
a
bunch
of
interviews
with
with
the
founder
eugene
on
youtube
and
I
think,
they're
a
great
example
because
they're
very
active
right
now
across
some
larger
exchanges
and
I
think
they've
actually
graduated
behind
hummingbi
they're
kind
of
you're
running
their
own
customers
off
right
now.
But
they
start
with
us
and
they're
still
contributing
back.
B
So
so,
obviously,
I
think
that
this
is
actually
showing
up
in
the
volume.
So
this
is
this
is
the
heartbeat
feature
with
the
hummingbot
that
sends
data
with
this
anonymized
and
aggregated
x
into
into
our
servers.
So
we
track
we
track
basically,
so
this
is
actually
only
about
a
thousand
bucks
because
you
know
per
day
or
so,
because
a
lot
of
people
are
turning
that
feature
off,
but
we
do
find
that,
like
a
tracking
perspective,
it's
good.
B
We've
really
seen
a
big
since
we
and
we
think
that's
because
the
the
binance
connectors
have
been
upgraded
in
that
release,
and
so
I
think
that
the
higher
speed
and
the
higher
quality
of
those
connectors
are
probably
you
know
causing
that.
And
so
that's
why
we
want
to
try
to
get
maintainers
for
all
the
exchanges,
because
we
believe
that
you
know
if
there's
dedicated
personnel
looking
after
naturally
volume
and
we
want
to
make
sure
containers
share
in
some
of
that
upset.
B
Next
one,
so
so,
as
I
mentioned,
it's
really
the
user,
creativity
behind
hummingbot
that
allows
it
to
be
sustainable.
You
know
both,
and
so
the
model
really
is
that
we
try
to
enter
into
partnerships
with
different
exchanges
and
rebate
a
share
of
fees
based
on
user
trading
activity.
This
is
tracked
at
the
connector
level,
using
a
custom
api
header.
B
B
B
So
so,
actually
about
foundation.
We
really
view
this
as
a
dow,
because,
because
of
the
fact
that
the
maintenance,
you
know
the
the
exchange
feature
agreements
coming
in
support
the
ongoing
operations
of
the
foundation,
it
means
that
this
token,
you
know
we
want
to
just
give
it
away.
You
know
give
away
as
much
as
possible
to
come
out
users
so
that
they
can
essentially
vote
and
steer
the
homeowner
foundation.
B
However,
they
want
so
you
know
we
when
we
achieve
the
token
we
decided
to
give
the
allocations
to.
You
know
both
past
stakeholders,
the
investors
from
one
alpha
who
had
basically
funded
the
build
out
of
playing
bot
for
the
past
four
years,
the
coin
alpha
nation
team
and
then
but
we're
essentially
giving
40.
B
B
Thank
you,
oh,
so
so
yeah
because
of
the
sustainable
nature
foundation.
We
believe
that
you
know
that's
why
the
the
this!
This
token
distribution
is
really
intended
to
increase
municipality.
It's
not
needed
for
we,
the
foundation,
never
plans
to
sell
the
token
for
operational
purposes
or
issue
more
because
the
feature
agreements
that
that
support
the
foundation
today,
you
know,
if
we
continue,
I
don't
change
it
that
that
should
actually
become
that
is
added
to
the
charge
of
having
to
use
the
treasury.
So
that's
why?
For
the
distribution?
B
Are
to
control
which
of
the
open
requests
you
know
should
be
approved
so
currently
there's
probably
about
30
or
40
space.
Some
of
these
are
from
a
lot
for
community
developer.
You
want
to
contribute
to
the
code
base
or
change
certain
features,
or
those
kind
of
things
so
so,
and-
and
I
think
a
lot
of
that
is-
is
really
you
know,
though,
now
that
we're
ill
personalization.
B
So
the
the
very
first
thing
that
I
think
the
main
job
for
for
token
holders
is
to
be
able
to
vote
on
requests
and
to
warn
it.
How
do
we
get?
How
do
we
involve
the
community
and
helping
discuss
that
some
more,
but
the
the
main
thing
we
want
to
do
to
actually
help
basically
help
get
something,
because.
B
So
so
that's
why?
Because
of
the
the
hummingbird
distribution,
we're
basically
giving
out
nine
percent
of
the
supply
every
year
for
the
next
four
years,
so
we
believe
that
that
distribution
will
allow
the
foundation
to
be
completely
sustainable,
but
also
incentivize
the
community
to
do
a
variety
of
things
that
basically
support
the
foundation.
One
is
liquidity,
so
you
know
we
want
to
make
sure
that
people
are
actually
using
the
software,
especially
when
we
connect
to
an
exchange,
and
we
want
to
incentivize
people
to
do
it
for
market
making
purposes.
B
B
Full-Time
people
working
at
the
dow
level
and
to
increase
the
ability
for
the
community
to
contribute
in
a
variety
of
ways,
so
we're
planning
to
set
up
a
dow
to
help,
but
also
there's
also
really
interesting,
that
we
want
to
try
to
basically
get
teams
created
in
the
community
to
do
research
on
areas
like
energy
domain,
specific
languages
and
getting
with
each
other
and
to
compete.
You
know.
A
A
So
that
way,
we're
looking
to
platforms
like
humbot
miner,
so
that
we
know
that
have
a
lot
of
humbot
users
and
we
also
going
to
do
dev
grants
where
the
goal
is
to
improve
the
code
base
of
the
humbot
itself
right
so
like
connectors
strategies,
any
third-party
integrations
and
things
like
that,
and
also
the
third
area
that
we
want
to
to
distribute
the
the
tokens
to
incentivize.
The
community
is
to
have
different
projects
right
that
are
self-organized
by
the
community.
A
Some
of
these
examples
are
a
dial
for
technical
review,
to
review
the
the
pull
request,
proposals
of
the
codes
and
some
research
on
how
we
can
integrate
some
some
some
ideas
into
the
into
the
humbot
like
providing
liquid
to
nfts
domain
specific
language
for
creating
strategies
and
bought
coordination
between
different
clients.
So
these
are
the
main
areas
that
are:
is
the
goal
of
the
foundation
to
reward
the
community
for
for
their
participation
right?
A
So
just
a
quick
talk
about
community
calls
right
so
why
we
are
doing
this
and
what's
the
plan
for
community
calls.
So
the
goal
is
that
we
want
to
hear
from
the
community
what
everyone
thinks,
how
the
project's
moving
any
ideas
and
any
discussions
that
are
relevant
to
the
improvement
of
not
only
the
bot
itself
but
for
the
community
as
a
whole
and
also
for
to
allow
the
foundation
to
provide
a
a
time
to
go
through
all
the
the
updates
of
what's
happening
on
the
project
as
a
role
as
a
whole
right.
A
So
the
plan
is
to
have
these
common
calls
once
every
month
at
the
beginning
of
the
month.
So
as
we
did
the
voting,
we
will
do
it
the
first
thursday,
tuesday
or
today
is
yeah
tuesday
off
every
month.
So
we
can
kind
of
have
this
cadence
of
updates
right.
So
at
the
end
of
the
call
after
we
go
through
the
presentation,
we
will
also
open
up
to
everyone
who
wants
to
to
ask
questions
or
emit
any
opinion
about
the
project
itself.
A
A
The
other
level,
on
the
other
extreme,
we'll
have
the
pull
request
proposal
that
is
essentially
the
approval
of
which
pull
request
is
going
to
be
added
into
the
code
base
right.
So
if
you
check
it
last
january,
we
had
some
pull
request.
Proposals
created,
so
that's
what's
happened
to
and
send
and
okay,
so
we
did
some
votings
for
testing
and
the
proven
proposal
is
going
to
be
merged
into
the
next
version.
I'll
get
a
bit
more
details
on
each
one
and
the
third
type
that's
going
to
be
the
improvement
proposal.
A
So
why
three
types
of
proposal
right
because
from
what
we
discussed
it
is
that
we
need
to
have
different
levels
of
sorry.
We
have
different
need
different
levels
of
requirements
for
each
type
of
proposal,
because
what
they're
going
to
cover
so
on
the
the
one
that
require
less
less
resources
to
create
proposals
and
approval.
A
We
have
the
governance
proposals
right
where
the
governance
we're
going
to
handle
and
needs
to
have
a
higher
requirement,
because
in
this
sense
we
are
going
to
talk
and
handle
about
changes
on
the
governance
process
and
use
of
treasury.
So
that's
why
it's
the
type
of
proposal
that
we
need
more
a
bigger
part
of
the
community
participating
into
the
discussion
and
into
the
voting
right.
So
on
the
middle,
where
we
have
the
improvement
proposals,
it's
on
the
middle
ground.
A
So
we
are
talking
about
any
other
type
proposal
not
covered
by
the
other
two.
So
this
is
kind
of
the
middle
ground.
Where
we
have
different
type
of
proposal
that
it
will
make
a
bit
more
sense
when
I
go
through
them
right,
so
a
bit
more
details
about
pull
requests,
how
it
works
so
yeah
before
I
continue
everything
that
I'm
saying
here
is
also
on
the
on
the
official
page
right,
so
humminbot.org
so
everything's
already
there.
A
The
basic
idea
here
is
that
a
developer
creates
a
pull
request,
targeting
development
branch
right,
because
the
the
thing
is
that
development
branch
is
going
to
be
the
one
that's
going
to
be
added
later
into
the
master
branch
right.
So
all
the
requests
that
are
targeting
development
branch,
they
want
to
be
on
the
main
version
of
the
bot.
A
So
what
happened
is
that,
after
creating
the
pull
requests,
the
developer
or
not
necessarily
the
developer,
but
anyone
from
the
community
that
sees
a
pull
request
into
the
github
pages
can
create
a
pull
request.
Proposal
right
so
ended
up,
creating
the
request,
so
the
foundation,
the
dev
itself
or
anyone
else
from
the
community
can
go
into
the
the
snapshot
page
and
I
create
the
the
proposal
all
right.
So
what
happens
is
when
a
pull
request
is
created?
A
It
will
have
a
seven
day
period
that
will
be
open,
so
the
first
four
days
it
will
be
pending
so
and
if
we,
the
community,
won't
be
able
to
vote
it.
The
plan
here
the
idea
is
that
it
gives
time
to
everyone
into
the
community
to
look
into
the
pull
requests
understand
what
the
pull
request
is
about
and
comment
and
discuss
and
talk
with
the
developer
that
created
the
pull
quest
to
point
out
any
any
errors,
any
fixes
that
the
pull
requests
need.
A
Then,
after
these
four
days
the
voting
will
be
open
for
three
days.
So
at
that
point,
our
request.
Our
suggestion
is
that
the
developer
do
not
change
the
request
anymore.
So
we
can
have
a
final
version
of
it,
so
the
community
can
properly
evaluate
if
they
want
to
to
have
it
added
to
the
to
the
main
code
base,
and
then
we
have
two
outcomes.
A
So
if
to
keep
track
of
how
what's
the
state
of
all
the
pull
requests
inside
the
github
page,
will
you
inside
the
the
project
tab
you
see
that
this
project
called
pull
request
proposal
status
inside
of
it,
where
we
have
some
columns
that
that
shows?
What's
the
state
of
the
pull
request
right,
if
there
is
a
proposal
created
if
the
proposal
was
approved,
it
was
and
it's
under
review
if
it
has
already
been
merged,
it's
mostly
to
track.
A
What's
the
the
current
state
of
each
pull
request
related
to
the
status
right,
so
the
pull
request
also
gets
into
the
development
cycle.
The
the
client
release
development
cycle
that
we're
going
to
follow.
This
is
a
quick
scheme
of
how
the
the
request,
the
process
of
having
a
pull
request,
is
going
to
to
happen.
So
we
have
the
developer,
create
the
pull
request.
Then,
if
it's
approved
foundation
team
is
going
to
merge
it
in
the
development
branch
after
the
proposal
is
approved
and
after
the
we
have
a
cut-off
date.
A
So
at
the
end
of
the
month,
let's
say
all
proposals
that
were
approved
until
the
end
of
january
they're
going
to
the
february
release
right,
and
so
that's
basically
the
process
we
go
into
the
development.
Then
after
development
we
run,
we
merge
into
the
stage
branch
to
run
some
final
tests
see
if
everything
is
working
properly
and
then
after
these
tasks
everything
passes.
Qa
is,
is
good
enough
and
sign
off
to
the
to
the
release,
and
then
it's
added
to
the
master,
master
branch
and
added,
as
so.
A
The
the
cycle
that
I
mentioned.
That
I
was
talking
about
is
that
at
the
end
of
the
month,
we'll
have
a
cut-off
date
for
proposals.
So,
as
I
was
saying,
everything
that
was
approved
at
the
end
of
january
will
go
ins
into
the
release
of
february.
Everything
that's
approved
until
the
end
of
february
will
go
into
the
march
release.
So
that's
the
cadence
that
we're
going
to
to
work
with
the
the
future
releases
from
now
on
right
now,
so
that's
all
I
had
for
the
request
proposals
and
for
improvement
proposals.
A
So,
like
I
mentioned,
is
anything
that's
not
covered
by
pull
request,
proposals
or
governance
right.
So
there
is
a
few
special
cases
here
that
is
tied
to
mostly
governance
proposal.
So
we
have
three
types
of
improvements,
proposals
that
needs
to
be
tied
to
governance
once
the
not
the
fixed
request,
sorry,
but
the
we
have
the
fix
request
where
the
community
create
improvement
proposal
to
ask
for
the
maintainers
to
prioritize
bug
fixes
right.
A
Is
the
dev
grant
grant
request
yeah
I'll
talk
a
bit
more
about
them
a
bit
in
a
few
minutes,
but
basically,
once
we
have
a
dev
grant
approved
by
the
community
developers
will
create
an
improvement
proposal
requesting
a
participation,
appro,
sorry,
a
participation
into
that
deaf
grant
explaining
and
showing
what
he
will
be
into
humboldt
right
and
we
have
initiative.
Elections
like
we
mentioned.
One
of
the
goals
is
to
incentivize
community
teams
to
create
different
projects
and
initiatives
that
probably
need
research
or
need
more
more.
A
The
major
one,
the
governance
proposals
right.
So
what
happens
with
governance
proposals?
Is
that
we
divided
into
four
main
categories
that
if
any
proposal
that
wants
be
it
the
foundation
or
anyone,
anyone
from
the
community
wants
to
create?
Okay,
sorry
about
that,
once
you
create
false
into
one
of
these
four
categories,
it
must
be
created
as
a
governance
proposal
right.
A
The
first
one
is
about
liquidity
distribution,
so
anything
related
to
just
distributing
new
age
about
tokens
among
the
community.
So
any
new
distribution
needs
to
be
to
go
through
a
governance
proposal.
So
the
goal-
and
the
point
of
this
proposal
is
to
try
to
maximize
the
probability
of
the
anyone,
that's
holding
a
hbot
token,
to
be
a
humbot
user
and
be
part
of
the
community
and
also
help
with
must
also,
if
possible,
try
to
help
with
the
liquidity
of
the
markets
and
incentivize
the
the
new
community
participants
joining
our
community
right.
A
A
You
can
see
the
details
about
it
on
our
snapshot
page,
but
basically,
our
proposal
is
that
we
distribute
this
amount
of
tokens
through
the
liquidity
mining
that
happens
into
the
humbot
miner
right.
So
using
the
same
system
that
already
exists
in
place
right,
there's
more
details
to
it
into
the
proposal,
so
this
is
going
to.
This
is
what
our
main
example
for
this
type
this
category.
A
The
second
category
is
about
the
dev
grant
budget
right.
So
I'll
take
some
time
here,
because
this
is
one
is
going
to
be
one
of
the
key
process
that
we
are
going
to
to
run
so
a
death
grant
budget.
Basically,
what
happened
is
that
is
a
proposal
where
it's
going
to
allocate
an
amount
of
from
the
treasury
to
incentivize
the
community
to
create
new
solutions
to
to
create
improvements
into
the
the
main
code
base
of
the
bot
right.
A
A
So
what
happened
is
that
it
all
starts
with
the
governance
proposal
right.
So
the
governance
proposal
established
the
budget
of
the
divergent
and
what
is
the
type
of
work?
What's
the
type
of
improvement
that
can
request
participation
into
the
dev
grants.
After
that
proposal
is
approved,
the
developers
any
developers
can
create
an
improvement
proposal
requesting
a
share
of
that
that
grant
right.
So,
let's
say
the
example,
I'm
going
to
show
you
the
first
one
we
created
is
a
dev
grant
to
create
new
strategies
right.
A
So
once
this
divers
is
approved,
any
developer
can
create
an
improvement
proposal
explaining
okay.
So
I
want
to
receive
x
amount
of
hbot
tokens
from
this
dive
grant
that
was
approved,
and
for
that
I'm
going
to
build
the
strategy
x,
y
and
z
right
and
then
this
going
to
into
community
voting,
and
if
the
community
likes
the
the
idea
they
will
vote
yes
or
rejected.
A
If
the
developer
proposal
is
approved
by
the
community,
he
then
will
go
into
creating
his
pull
requests
and
and
effectively
his
pull
request
proposal,
and
that
also
needs
to
go
to
governance,
because
at
this
point
we're
talking
about
looking
into
the
code
reviewing
the
code
the
whole
coming
to
check.
If
the
code
matches
what
was
proposed
initially-
and
once
this
is
approved,
the
developer
will
get
his
share
of
the
dev
grant
and
the
code
he
submitted
is
going
to
be
added
into
the
main
code
base.
A
So
the
example,
as
I
mentioned
we
just
created
this
morning
my
morning-
I'm
not
sure
what
your
times
is
for
everyone
else,
but
it's
the
creation,
improvement
of
humboldt
client
strategies.
So
we
are
allocating
one
million
hbot
tokens
to
new
strategies
or
improvement
of
new
ones,
so
in
developers
that
want
to
contribute
and
request
a
share.
A
After
the
approval
of
this
governance
proposal
can
go
on
and
and
request
the
participation
process
and
again
it
might
be
a
lot
of
information.
So
if
to
to
make
sure
that
everyone
gets
all
the
details
go
into
the
humbot.org
page,
we
have
a
section
about
governance
where
all
these
details
that
I'm
I'm
talking
here
is
a
bit
more
explained
there.
So
take
a
time
to
look
into
it
too.
A
But
the
idea
of
this
initiative
budget,
for
example,
is
that
we
allocate
an
amount
of
tokens
for
the
community
who
wants
to
be
to
who
wants
to
be
actively
reviewing
the
pull
requests
that
have
been
created
to
the
to
to
the
code
base
right.
So
in
this
example,
this
team
that
will
perform,
probably
five
community
members
would
go,
would
take
the
time
to
go
through
the
submissions.
The
pull
requests
review.
A
So
another
example
is
here
we're
talking
about
hackathons,
so
we
could
have
initiative
budget
to
fund
the
hackton
content
creation,
that's
going
to
be
community,
created
blog
posts,
videos
or
anything
related
to
humbot
and
team
projects,
like
the
one
I
mentioned
about
review,
review,
community
review,
team
or
development
of
domain
specific
language
right.
So
the
the
difference
here
is
that
we
are
talking
about
projects
that
not
necessarily
have
a
direct
creation
in
direct
creation
of
a
request
to
change
the
code
base
right.
A
So
it's
a
bit
more
ample
win
and
covers
a
bit
more
possibilities
right
so
and
the
fourth
type
is
governance.
Changes
right,
so
anything.
Any
proposal
that
the
community
wants
to
to
to
discuss
to
to
propose
to
make
changes
into
the
governance
system
itself
needs
also
to
be
a
governance
proposal
right.
A
So
that's
why
that's
the
main
reason
that
this
type
for
these
four
types
of
proposals
needs
to
have
a
higher
requirement
to
to
to
be
approved
because
they
need
our
view
is
that
they
they
need
a
bigger
discussion
among
the
community
and
that's
why
we
added
them
as
a
higher
requirement.
So,
as
example,
for
this
type
of
proposal,
we
are,
we
created
one.
That's
going
to
change
the
minimum
quorum
for
the
approval
to
this
percentage
of
circulating
supply.
Currently,
our
our
supply.
A
Sorry,
currently,
the
minimum
quorum
needed
to
approve
the
the
governance
proposal,
is
a
percentage
of
the
total
supply.
So
what
we
discussed
is
that
this
might
cause
some
issues
with
the,
as
we
still
have
a
a
pre-considerable
amount
of
tokens
to
be
distributed
among
the
community.
So
our
proposal
for
now
is
that
we
change
this
instead
of
using
the
total
supply,
the
minimum
quarter
to
be
a
percentage
of
the
circulating
supply
right.
A
So,
once
every
month
we
will
update
the
snapshots
to
match
the
circulating
supply
and
that
will
make
it
more
sense,
at
least
in
of
you
to
to
to
have
as
a
minimum
amount
of
votes
prior
to
the
pro
right.
So
yeah,
that's
the
the
walkthrough
of
the
how
the
governance
proposal
itself.
It
will
work
again
check
the
humbot.org
page
for
more
details
and
also
any
questions
that
anyone
have
be
it.
It
could
be
right
now
or
maybe
in
the
future,
feel
free
to
reach
us
out
into
discord.
A
Ask
a
question
about
one
proposal
or
another
of
how
something
works.
So
we
are.
We
are
around
the
community
always
to
try
to
to
answer
all
the
questions
as
much
as
possible
right.
So
next
part
we're
going
to
talk
a
bit
about
epochs
I'll
handle
up
to
to
mike
too,
and
so
he
can
explain
this
a
bit
better.
How
watch
the
idea
of
the
epochs
and
how
they're
going
to
right.
A
B
B
B
You
know
ask
community
how
everything
went
and
try
to
take
your
feedback
and
try
to
improve
the
process
for
the
next,
and
so
hopefully
that
allows
ensure
that
we're
maximizing
the
impact
of
the
h-spot
distributions
onto
the
and
they're
achieving.
I
think,
the
end
goal,
which
is
creating
a
truly
bizarre
style.
You
know
open
source
code
base
that
allows
everyone.
B
You
know
to
really
get
the
most
out
of
it
in
different
ways,
but
also
allows
the
developers
community
developers
to
basically
earn
a
lift
by
supporting
the
code
base
distributing
from
all
that,
never
using
so
for
the
first
epoch.
I
think
if
you
go
ahead
next
slide
paulo,
let
me
explain
how
the
first
epoch
run
so
the
first
one.
Essentially,
this
is
really
our
kind
of
like
our
starter
epoch.
B
So
so
overall,
I
would
say
because
there's
some
time
to
actually
get
get
the
pro
requests
approved
and
get
the
improvement
proposal
and
the
progress
before.
Basically
the
the
hiv
cut
off
for
dev
grants.
Budgets
related
will
be
31st.
So
that
means
that,
if
you
wanted
to,
you
know
basically
say
I
want
to
do
this
work
and
get
get
a
get
a
share
of
this
epoch.
One
contribution
submit
that
improvement
proposal
by
the
end
of,
and
then
your
pro
cross
proposal.
B
B
So
in
terms
of
allocation,
so
we
kind
of
divided
the
the
hbo
distribution.
Three
general
categories:
one
is
liquidity
distributions,
basically
to
incentivize
users
who
use
the
software
and
you
get
a
get
the
users.
So
we
want
to
try
to
distribute
15
million
tokens
across
a
variety
of
platforms,
so
one
of
them
is
the
minor
platform
that
this
proposal
out
standing
for,
but
there's
also
other
exchanges
as
well.
B
That
hummingbird
is
connected
to
so
we're
going
to
try
to
work
with
those
exchanges,
but
also
some
of
the
newer
ones
that
I
think
also
want
to
work
with
in
order
to
get
tokens
into.
You
know
people
using
those
both
existing
exchange
connectors
in
addition
for
dev
grants.
This
is
a
big
part
of
it.
I
I
think
that
we're
gonna
try
to
use
it
to
really
grow
the
number
of
community
developers
involved
with
the
project
and
and
try
to
find
some
things
that
can.
B
B
Oh
actually,
actually
yeah.
So
actually
one
thing
I
forgot
to
mention
about
the
epoch
is
so
so
one
aspect
of
the
epoch
I
think
you'll
see
on
the
page,
is
some
guidance
in
terms
of
how
much
hbot
to
request
when
you're
distribution,
so
currently
the
hbo
token
is
not
very
liquid
and
and
this
one
because
you
know
we,
we
we're
going
to
work
with
to
work
with
all
the
exchange
partners,
most
likely
to
get
an
hr
listing.
B
You
know
kind
of
like
query
distribution,
the
connector,
so
it's
kind
of
why
we
haven't
really
kind
of
really
focused
on
all.
You
know
hbo
liquidity
yet,
but
we
are
aware,
there's
one
pool
that
is
created
in
uni
swap
with
which
the
currently
the
token
is
trading
yeah,
a
pretty
you
know
just
low
price.
So
that's
what
right
now
for
epoch,
one!
Our
guidance
is,
I
think
you
know
we
believe
the
developers
should
ask
for
something
like
twenty
thousand
h
spot
per
day.
B
A
C
D
D
So
everyone
knows
how
this
works,
but
we
have.
We
do
have
these
major
channels
that
we
can
use
to
further
make
conversations
with
one
another.
So
in
the
we
have
the
hashtag
general
channel
in
which
there
are
discussions
with
other
community
members
like,
like.
I
hear
some
people
here
asking
help
from
other
people,
so
I
think
that's
that's
where
that
conversation
should
should
be
so
in
the
support
channel.
Any
concern
with
regards
to
hummingbird
expo
token
so
stuff,
like
that
anything
under
like
dumbbell.org
umbrella.
D
We
can
cover
it
and
we
will
answer
the
questions
for
you.
Then
we
have
a
twitter
chat
in
which
this
is
a
space
for
traders
to
talk
with
each
other
like
give
some
advices.
So
if
you
have
any
questions
with
regard
to
trading,
this
is
the
place
to
go,
and
we
do
have
some
traders
who
do
answer
questions
for
other
traders
as
well.
So
I
think
the
trader
chat
is
the
most
appropriate
channel
to
ask
for
any
trader
related
questions.
D
Then
we
have
the
governance
chat
in
which
you
guys
can
discuss
some
improvements
enhancements
you
want
to
go
in
and
what
are
the
the
prs
that
we
have
from
the
community?
And-
and
I
I
guess
this
is
the
perfect
place
for
you
to
to
ask
what
enhancement
or
what
are
the
pr's
that
are
going
into
the
code
base.
D
Good,
so
we
do
have
the
minor
support
channels
and
the
market
announcement
and
liquidity
mining
in
which
you
these
are
owned
by
coin
alpha
and
with
and
are
in
which
you
can
ask
the
minor
supports
for
for
support,
in
which
you
have
failed
issues.
Stuff
like
that.
So
this
board
is
generally
a
shared
space
between
coin
alpha
and
the
hummingbird
foundation,
but,
like
some
partners
can
also
have
their
own
space
in
in
the
community.
Discord
as
well,
so
yeah
yep.
D
D
We
can
easily
contain
and
search
for
related
topics.
We
are
interested
in
as
usual,
any
user
of
the
community
can
create
any
related
topic
and
for
developers
to
encourage
them
to
create
topic
before
submitting
proposals.
In
this
way,
our
community
will
be
well
aware
of
these
proposals
and
be
able
to
decide
and
vote
intelligently.
D
D
A
Yeah
one
final
note,
two
final
notes:
actually
one
is
that
community
calls
every
month
we'll
be
uploading
them
to
to
the
youtube
channel.
So
you
can
tell
anyone
that
missed
it
to
go
check
what
happened
and
the
the
third
one
is
just
a
recommendation
that
be
careful.
As
we
know,
all
discord
community,
especially
those
related
to
cryptocurrency
in
some
way,
is
full
of
people
trying
to
scam
others.
A
So
we
as
foundation
and
queen
alpha,
we
will
never
ask
you
to,
for
your
crypto
keys
your
api
keys
or
anything
like
that.
Right,
so
be
sure
that
if
someone
tries
to
impersonate
anyone
both
from
the
foundation
or
coin
alpha,
so
make
sure
that
you
don't
send
any
sensitive
information
rights
and
also
give
a
heads
up
to
our
support
so
or
anyone
else
from
the
photician.
A
C
Perfect,
yes,
yes,
well,
my
question
is:
is,
are
these
figures
absolutely
set
in
stone,
or
is
there
a
possibility
to
give
more
or
less
hummingbird
tokens
until
the
end
of
the
epoch
like,
for
example,
the
first
death
grants
have
been
sized?
I
don't
know,
maybe
too
too
small
or
too
big
and
there's
some
stuff
happening.
C
D
B
Entire
budget
during
the
next
five
months,
and
but
overall,
I
think
this
is
sort
of
like
that,
because
we
also
want
to
make
sure
that
the
the
the
like
the
because
tokens
are
not
really
like
like
something
that
the
value
we
expect
to
change
right.
So
so
it's
kind
of
like
if
we
give
out
all
the
tokens
that
we
have
available.
B
You
know
too
fast,
then
kind
of
like
also
not
really
maximizing
value
once
you
will
get
a
later
one,
because
those
by
more
point.
So
that's
why
that's
really
why
we
process
is,
to
kind
of,
like
you
know,
have
a
fixed
target
over
a
certain
format
decision
and
then
reassess
and
then
kind
of
readjust
for
the
next
epoch.
So
I
do
think
that
you
know
what
we,
I
would
say
the
reason
we.
B
Versus
45
and
45
is
because
we
actually
foresee
you
know
getting
to
30
million
challenge
finding
enough
developers.
My
incentivized
grants,
because
this
10
million
is
not
just
for
a
few
dirt,
expect
this
to
cover
a
number,
and
you
know,
lots
of
different
people.
So
so
overall
I
mean,
I
would
say
yes,
could
people
do
more
absolutely,
but
I
think
we
also
want
to
make
sure
that
yeah
for
the
second
epoch
we
in
in
future
epochs.
We
have
enough.
So
that's
why.
A
Yeah
complement,
complement
of
what
mike
said
is
that
in
a
sort
of
way,
we
are
still
understanding
the
best
way
to
run
this
process
right.
So
that's
why,
on
the
beginning,
we
start
a
bit
slow,
but
as
everything
all
the
whole
governance
process
gets
more
clear
and
everyone
else
from
the
community
also
get
used
to
it.
We
we
we
can
kind
of
adjust
any
numbers,
also
another
another
question.
For
example,
like
you
mentioned
a
bigger
amount
of
work
for
a
project,
for
example.
A
What
could
happen
also
is
that
studying
or
looking
to,
if
there
is
a
dev
grant
created
for
that
type
of
project,
the
community
member
or
you
or
you
could
create
a
governance
proposal
as
a
initiative
with
what's
the
amount
of
budget
and
explaining
what
were
the
mechanics
of
that
project?
That
initiative
and
put
up
for
for
government.
B
Yeah
yeah
also,
this
is
one
final
thing,
so
30
million
tokens
what
this
represents
overall
supply
because
of
the
dynamics
of
the
the
there
won't
be
any
more
than
the
the
initial
supply
tokens
and,
and
so
the
reason
we
did
it.
This
way
is
because
we
think
coming
by
will
be
around
as
a
project
in
10
years.
B
You
know
20
years-
hopefully
you
know
you
know
100
years
hopefully,
but
but
the
idea
is
that
you
know
this
this,
this
ability
to
govern
the
project
you
know
on
to
infinity,
and
so
you
know
so
right
now.
I
think,
like
the
the
token
is
probably
trading
at
a
price,
probably
not
where
my
if
the
future
does
actually
happen.
So
so
that's
why
I
think
right
now
we
want
to
make
sure
we
actually
leave
f
tokens
for
posterity
so
that
the
people
who
are
contributing
you
know
in
2024,
2005
2026.
B
They
have
enough
tokens
to
reward
them
for
their
time.
So
you
know,
I
actually
think
giving
out
three
percent
of
the
overall
supply
over
the
next
five
months.
You
know
the
first
five
months
of
the
foundation
you
know
is
actually
quite
a
lot
other,
and
so
that's
why
I
think
you
know
I
I
would
look.
I
would
consider
for
every
developer
looking
to
look
at
what
the
future
value
might
be
in
the
future.
You
know
if
you
know
it
assume
that
there
will
be
never
any
more
tokens
issued
this.
C
Okay,
so
there
I
think
two
points
that
I
want
to
maybe
ask
one
is:
does
the
hummingbird
tao
intend
to
own
any
stables
in
the
treasury
at
any
point
in
the
future?
In
case
of
I
don't
know,
maybe
some
like
a
kind
of
insurance
fund
if
something
goes
wrong
and
what
about
and
if
the
daw
also
intends
to
increase
the
available
liquidity
on
the
hummingbird
top.
So
maybe
that
the
price
can
be
a
more
I
say,
a
reliable.
B
B
C
Would
necessitate
yeah
yeah?
Well,
that's
something
that
is
mostly
for
d5
protocols.
I
think
a
problem,
but
let's
say
for
some
reason:
there
is
a
bug
in
the
open
source
code
introduced
by
a
pull
request,
proposal
which
hasn't
been
detected,
or
maybe
even
a
malicious
actor
induced
some
kind
of
code
which
could
somehow
extract
funds
by
the
users
of
hummingbirds.
C
B
So
essentially
I
was.
I
would
not
look
at
any
protocol
when
looking
at,
like
comparables,
for
on
how
it
should
be
designed.
What
I
would
look
at
is
more
other
open
source
networks
that
are
like
creating
network
between
almost
like
workers
and
other
other
kind
of
projects
that
benefit
in
a
more
coordinated
way,
so
so
more
more
of
the
dow's
out
there,
as
opposed
to
like
the
pure
dowels,
rather
than
you
know
that
the
so,
of
course,
the
index
co-op
is
probably
one
example.
B
B
Yeah
make
sense
except
yeah,
yeah
but
yeah,
but
also
to
answer
the
second
question
on
liquidity.
So
so,
overall,
the
main
thing
the
foundation
will
do
be
doing
is
expanding
partnerships.
So,
since
we've
launched,
there's
probably
been
about
30
to
40
exchanges
who
have
the
foundation
about.
You
know
arranging
partnerships
to
build
connectors
and,
to
you
know
basically
incentivize
the
use
of
those.
B
So
so
that's
why
I
would
say
because
of
the
nature
while
yeah,
because
so
the
liquidity
is
really
the
government's
tokens,
but
but
I
think
it's
really
an
incentive
for
people
to
use
hummingbot,
and
you
know
coming
up
tokens
on
various
platforms,
and
so
it's
kind
of
it's
almost
like
you
know.
There's
by
design
hummingbird
should
be
a
very
liquid
yeah.
D
Okay,
hi:
hey
guys,
can
you
hi?
Can
you
guys
hear
me
yeah?
Okay,
so
I
have
questions
about
so
this
looks
like
our
community
has
to
like
develop
into
like
a
foundation.
So
my
question
is
about
something
like
the
the
ego
club.
So
do
we
have
any
plan
to
like
to
because
now
we
have
something
like
distributing
the
h-bot
tokens
into
some
some
categories
here,
like
liquidity,
distribution,
death
or
initiative.
So
what
about
like
the
older
ego
group
members,
something
like
that?
A
Yeah,
I
would
say,
eagle
club
is
related
to
the
humbot
miner
right
so
the
foundation.
So
that's
that's
more
a
question
for
coin.
Alpha
itself:
do
we
do
have
a
proposal?
The
proposal
we
have
about
the
liquidity
mining
distribution?
That's
up
for
voting
right
now
is
to
that
we
our
proposes
to
give
this
amount
of
tokens.
A
B
Yeah,
yeah,
and
and
and
just
adding
up
to
that,
so
the
yeah,
the
eagle
club,
is
really
for
like
it's
like
the
minor
vip
program.
But
I
would
say
the
lesson
we
learned
from
eagle
club
is
really
that,
like
because
those
of
you
aren't
eagle
club
there's
actually
a
lot
of
discussions
that
happen
channel.
You
know
on
discord
and
it's
almost
like
the
the
people
there,
because
it's
you
know
like
an
exclusive
community.
They
tend
to
work
each
other
more
help
each
other
kind
of
strategies.
B
You
know,
for
instance,
there's
been
discussion
about
the
story.
Okay
micro
price
indicator
on
the
eagle
club
channel
say:
if
eagle
club
members
want
to
form
you
know
a
team
to
go
and
build
something
related
to
that
they
can
ask
for
a
budget
for
their
team.
But
the
overall
idea
here
is
that
I
think
the
community
I
think
is,
is
a
real
part
of
everything
that
has
made
hummingbird
where
it
is
today,
and
we
want
to
essentially
create
a
structured
process
to
incentivize
users
to
form
to
to
basically
organize.
D
A
A
A
D
B
A
A
Okay,
there,
it
is
right
back
to
commonwealth,
like
we
mentioned
on
the
on
the
on
the
meeting
earlier.
The
idea
is
that
every
time
there
is
some
something
that
anyone
from
the
community
wants
to
go
to
a
bit
more
long-term
discussion.
Please
try
to
use
commonwealth
because
the
thing
with
discord
it's
great
to
chat,
but
it's
pretty
easy
to
lose
track
of
any
discussions
that
happen
there.
So
if
things
are
happening
pretty
fast,
so.
B
Yeah
yeah,
yes,
so
just
just
explain
a
bit
more,
so
the
reason
we
use
commonwealth
is
because
we,
I
think
now
that
especially
now
that
we're
much
more
an
open
source
foundation,
truly
community
owned
having
a
forum
is
an
important,
really
aspect
of
every
open
source
project.
In
the
past,
we've
actually
experimented
with
having
a
separate
discourse
forum.
This
is
something
that
many
crypto
projects
have,
but
because
discourse
involves
a
separate
login,
every
every
basic
person
has
to
create
a
separate
log
for
it.
B
I
believe
that
com
is
going
to
be
you
know,
and
basically,
web
3
native
type
form
that,
where
you
log
in
with
the
wallet
is
going
to
be
the
future
of
of
how
discussions
happen
in
the
future,
because
you
know
everything's
moved
to
web3
and
given
that
they
have
a
snapshot.
Integration,
I
think
commonwealth
is
a
is
a
good
contender,
for
you
know,
for
kind
of,
like
the
form
software
that
becomes.
B
You
know
just
something
that
it
becomes
a
native
to
crypto
and
we've
heard
really
good
things
about
it
from
our
partners
at
uidx
who
use
this
for
the
forum.
So
so
I
know
that
right
now,
it's
it's
pretty
new
and
people
are
still
used
to
have
conversation,
but
I
really
encourage
you
to
come
in
here
and
just
comment
or
you
know,
hit
like
on
some
of
the
topics
here.
This
really
helped
just
as
a
soft.
You
know
it's
a
soft
pulling
system
to
see
which
of
the
topics
we
should.
B
You
know
dive
more
deeper
into
try
to
try
to
form
governance
proposals
around
and
try
to
form
research
to
so
there's
a
lot
of
you
know,
votes
for
the
kill
switch.
I
think
we'll
definitely
look
at
that
yeah
and
some
of
the
other
kind
of
features
here,
but
I
would
say
overall,
the
trend
definitely
seems
to
be
that
the
community
wants
easier
and
more
size
and
create
strategies
and
basically
to
control
how
humminbot
is
is
doing
in
multiple
ways.
B
This
is
actually
something
we're
actually
researching
right
now,
and
I
would
say
you
know
just
allowing
people
to
customize.
You
know
humminbot
in
various
ways,
whether
it's
through
strategies
or
scripts.
It's
definitely
a
big
focal
area
for
the
foundation
in
terms
of
roadmap
this
year,
so
so
yeah.
Overall,
I
just
want
to
highlight
this
because
I
I
think
that
obviously
is
new,
but
we
think
a
big
part
of
how
the
foundation
feature.