►
From YouTube: Hummingbot Community Call #6 | July 2022
Description
On this July Community Call, Mike and Hummingbot Foundation team members discussed on Epoch 1 Review, Gateway v2 Status, Hummingbot Botcamp, & with an engaging AMA session with the community.
Time Stamps
0:00 Introduction
1:25 Epoch 1 Review - HBOT Allocations
3:55 Epoch 1 Review - Gateway v2 Connectors
5:00 Epoch 1 Review - ETH Portland Hackathon
5:50 Epoch 1 Review - Tech Review DAO
7:00 Epoch 1 Review - External Integrations
8:00 Epoch 1 Review - ONE Liquidity DAO Campaign
8:30 Epoch 1 Review - Staging Bug Hunt
10:30 Epoch 1 Review - Recap
11:00 Epoch 1 Issue - Pull Request & Bug Fix Processes
11:15 Epoch 1 Issue - Connector Maintainer
13:45 Epoch 2 HBOT Allocations
15:45 AMA - Bittrex Connector Known Issues
16:50 AMA - Create New HIP at Next Epoch
18:05 AMA - Development Period
19:50 AMA - Quick Swap
20:08 AMA - Cosmos Integration
25:18 AMA - Stacks co
27:05 Community Reminder - Open Source Project
28:08 Feedback - Gateway Archt'l Decisions & Commonwealth Platform
31:45 AMA - Design Artifacts on Hummingbot
35:05 Hummingbot Botcamp
41:05 Hummingbot Prework
A
A
I
think
we'll
have
allocated
about
31
million
hbo
tokens,
but
I'll
also
kind
of
discuss
how
governance
went
overall
for
that
process
and
then
next,
we'll
kind
of
discuss
the
status
of
gateway
v2,
which
is
our
new
connector
module
that
was
released
in
master
in
the
april
release
and
and
then
and
now.
I
think
it's
just
gone
through
the
second
iteration
in
the
recent
1.5
release
and
then
third
we'll
do
an
ama
about
the
upcoming
bot
camp.
A
A
We'll
open
up
to
a
general
ama
as
well,
so,
let's
get
started
so
overall
in
epoch,
we
allocated
30
million
hbo
tokens
across
three
different
categories.
They
are
liquidity,
distributions,
dev
grants
and
initiative
budgets
so
for
liquidity
distributions.
We
allocated
15
million
hr
tokens.
We
had
two
approved
proposals,
number
one.
We
distributed
five
million
hbot
tokens
via
h-bot
miner
and
then
number
two.
A
We
allocated
10
million
tokens
to
create
a
liquidity
pool
on
the
avalanche
blockchain
on
the
trader,
joe
trader
joe
platform,
and
we
should
be
able
to
create
in
the
pool
sometime
later
on
this
week.
So
the
miner
platform
is
still
distributing.
H5
rewards
11
million
tokens
that
were
the
result
of
unclaimed
tokens
from
the
initial
air
drop,
and
so
those
tokens
will
be
going
out.
I
think
later
on
the
coin.
A
A
That's
why
we,
you
know,
wanted
to
get
the
trader
joe
liquidity
pool
set
up,
so
that
users
who
received
each
spot
on
the
avalanche
blockchain
could
actually
do
something
with
those
tokens
and
sell
them
on
the
decks.
Next,
we
had
the
dev
grand
budget.
We
allocated
10
million
tokens.
We
had
three
proposals
approved
number
one
was
the
creation
of
humboldt
client
strategies,
of
which
I
think,
we've
only.
We
had
one
million
budget
for
that.
A
A
In
my
view,
I
think
this
was
a
pretty
successful
initial
epoch,
because
we
we
saw
the
the
release
of
one
new
strategy,
the
fixed
grid
strategy
that
just
made
it
into
the
code
base
in
the
recent
june
release.
In
addition,
the
solana,
the
connected
team,
has
been
hard
at
work.
They
have
almost
finished
the
serum
connector
as
well
as
the
integration
into
the
combat
client.
A
I
think
there's
a
draft
request
right
now
that
they've
submitted
into
the
repository
that
we
will
be
reviewing
shortly
for
the
gateway
v2
connectors,
I
think,
was
also
pretty
successful
there
from
that
initiative.
It's
all
requests
for
polygon,
quick,
swap
curve,
perpetual
protocol
and
a
number
of
other
connectors,
as
well
as
the
harmony
blockchain.
You
know,
I
think
the
the
harmony
one
liquidity
dow
has
also
been
working
on
the
integrations
to
the
harmony
blockchain,
as
well
as
the
phyrra
and
d5
kingdoms
on
on
harmony.
A
So
overall,
this
debt
grant
category,
I
think,
is
something
that
we
want
to
expand
on
and
really
focus
more
hbot
tokens
toward
initiatives
that
actually
reward
developers
for
submitting
new
connectors,
especially
to
dexes
and
new
strategies
that
benefit
the
overall
community.
Thirdly,
we
had
a
initiative
budget
category.
We
allocated
only
five
million
tokens
for
this,
but
we
actually
ended
up
allocating
those
nine
million
tokens,
not
counting
the
developer
boot
camp
proposal.
That's
currently
pending
some
of
the
proposals
we
we
outlined,
I'm
just
going
to
list
them
number
one.
A
We
allocated
one
million
h-bot
to
the
eth
portland
hackathon
that
resulted
in
there
was
an
arbitrage
scout
script
that
was
created
as
a
result
of
that,
but
unfortunately,
none
of
the
the
hackathon
entries
actually
ended
up
being
submitted
into
the
code
base
as
pull
requests.
I
think
this
is
in
part
because
of
lack
of
guidance
from
our
part
in
what
type
of
person
should
be
doing
afterwards
with
those
with
submissions,
but
I
think
also
from
a
quality
standpoint.
A
I
would
say
the
submissions
probably
needed
more
work
in
order
to
make
it
to
a
a
true
merchable
code
standpoint.
So
so
I
think
it
was
a
good
experiment
in
doing
hackathon,
but
I
think
doing
it
over
again.
We
probably
would
either
allocate
less
budget
to
that
or
try
to
ensure
that
the
quality
bar
is
higher
for
the
winning
entries.
A
We
also
allocated
2.5
million
for
the
tech
review
dao,
and
I
think
this
was
in
my
opinion
was
pretty
well
spent
because
the
tech
review
dao
has
been
doing
a
lot
of
work
on
on
all
the
proquests
that
are
coming
into
the
code
base.
They've
been
reviewing
almost
every
single
pretty
much.
Every
single
pull
request,
adding
comments
to
it
and
then
also
working
with
developers
to
merge
those
requests
in.
So
I
think,
because
that
is
one
of
the
foundational
you
know,
work
items
performed
by
hummingbird
foundation.
A
A
Next,
we
also,
we
passed
two
million
hbo
budget
to
integrate
for
external
integrations
with
the
hvac
clients.
This
actually,
in
my
opinion,
should
probably
have
been
a
developer
grant
budget,
but
we
we
pass
it
as
an
initiative
budget
that
one,
I
think
I
think
we
did
see
a
few
tools.
I
think
there's
one
visualization
tool
that
made
it
into
the
code
base.
A
In
addition,
I
think
there's
also
there's
a
trading
view
integration
that
our
long
time,
community
member
police,
roger
has
put
forth
overall
external
integrations,
I
think,
is
something
we
definitely
want
to
encourage
as
we're
seeing
there's
lots
of
other
tools
out
there.
You
know
that
versus
with
trading
view
of
the
trading
platforms
and
overall,
we
think
that
human
bot,
you
know,
adds
ads
things
like
indicators
and
external
data
feeds
it's
more
powerful
if
it
can
leverage
external
data
sources.
A
A
Last
three,
in
this
category,
we
we
matched.
We
allocated
a
small
amount
of
hbot
225
000
to
match
the
reward
from
the
one
liquidity
liquidity
campaign,
so
this
was
one
of
the
partner
dows
set
up
by
the
harmony
blockchain
to
distribute
tokens
to
people
using
healing
bots
to
provide
liquidity
to
harmony
based
pairs.
A
A
And
lastly,
we
did
see
a
number
of
developers
claim
the
developer
airdrop.
I
think
we
probably
had
at
least
15
to
20
developers
claim
that,
so
there
is
a
good
amount
of
the
budget
remaining.
Another
thing
we
want
to
revisit
in
the
second
epoch,
because
some
of
the
feedback
we
got
from
tech
review
dao
was
that
developers
were
submitting
fairly
trivial
requests
in
order
to
you
know
kind
of
basically
claim
be
able
to
show
that
they
had
committed
to
the
development
branch
and
in
order
to
claim
this,
this
airdrop.
A
So
I
think
that
we
want
to
make
sure
that
you
know
we
have
the
right
incentives
in
place
and,
if
we're
just
creating
more
work
for
tech
review
data,
reviewing
you
know
trivial,
pull,
requests
or
documentation
or
things
that
kind
of
don't
actually
impact
the
user
base.
I'm
not
sure
that
this
type
of
airdrop
is
something
we
want
to
encourage.
A
So
I
think
I
think
one
of
the
roles
we
had
was
reduce
the
air
drop
for
for
this
from
100
from
10
000
to
something
like
100,
which
gives
developers
enough
to
you
know,
submit
pull
request
proposals.
Obviously
they
would
need
more
to
submit
the
improvement
proposals,
but
it's
something
that
may,
if
it
results
in
less
work
for
tech
review
dao.
That
might
be
a
good
thing.
A
So,
overall,
I
would
say
I
think
that
the
initial
epoch,
just
as
a
recap
we
allocated
about
30
million
hvac
tokens.
You
know
some
of
that
was
for
liquidity
distributions
and
I
think
of
the
30
million,
where
this
was
best
spent
was
on
places
like
the
dev
grants
that
incentivize
developers
to
submit
code
that
benefited
everyone
in
the
community,
as
well
as
on
things
like
the
tech
review,
dao,
which
compensated
community
members
for
doing
work
and
putting
in
the
time
that
helped.
A
You
know
the
community
get
their
requests
in
and
expanded
kind
of,
like
the
the
number
of
developers
who
were
able
to
contribute
to
codebase.
So
some
of
the
things
that
I
think
we
can
improve
on
our
proquest
process
and
the
improvement
proposal
process
were
still
fairly
opaque
and
also
fairly
cumbersome,
especially
when
it
came
time
to
actually
getting
bugs
fixed
in
the
code
base.
A
I
think
that's
definitely.
One
issue
we
want
to
address,
and
the
second
issue
that
we
want
to
address
is
the
fact
that
we've
had
certain
issues
with
connectors
that
went
unfixed
for
a
long
time,
because
there
was
an
official
maintainer
for
that.
Connector
and
bitmark
was
one
example
where
the
the
connector
really
didn't
work
for
a
while.
We
had
a
community
developer
who
built
that
connector
and
unfortunately
the
individual.
They
didn't
actually
fix
the
connector.
You
know,
even
though
they
were
supposed
to
do
so
in
the
role
as
official
maintainer.
A
So
what
happened
with
the
bitmark
connector
was
that
it
wouldn't
unfix
for
a
long
time
and
then
eventually
the
folks
at
coin
alpha
our
parent
company
fixed
it
resolved
issues
and-
and
I
believe
that
it
was
resolved
in
the
last
release.
So
I
think
it's
a
good
example
of
where
you
know
on
one
hand,
I
think,
having
an
official
maintainer
if
it
goes
well
does
result
in
kind
of
like
work
being
done
on
the
code
base
and
maintenance
being
performed,
but
in
cases
where
the
community
maintainer
doesn't
act.
A
It's
a
lot
of
overhead
for
the
foundation
to
to
check
in
with
that
person,
make
sure
if
there
are
or
aren't
doing
the
work
and
then
to
remove
that
mantle
and
give
that
to
another
developer.
If
that
person
doesn't
do
their
job
so,
overall,
we're
revisiting
this
concept
of
having
dedicated
maintainers
for
different
components
of
the
codebase,
we'll
publish
a
proposal
in
the
next
few
days.
A
A
So
that's
a
just
a
quick
recap
of
epoch
1
in
terms
of
the
hvac
distribution.
Overall,
I
would
say
I
think
we
learned
a
lot
the
foundation.
We
learned
a
lot
in
terms
of
what
works
and
what
doesn't
during
epoch,
1,
and
I
think,
we'll
be
able
to
make
a
lot
of
improvements
in
epoch
2..
One
of
the
things
I
think
one
last
thing
is,
I
think,
we'll
be
less
focused
on
allocating
and
distributing
a
certain
number
of
hbot
tokens.
I
think,
even
though
the
the
price
of
the
token
is
kind
of
trivial
good
liquidity.
A
For
the
token,
what
we
found
was
that
developers
in
our
community
the
motivated
they
seem
to
be
motivated
less
by
just
receiving
tokens
by
the
ability
to
contribute
into
the
code
base
and
earn
something
that
might
represent
the
long-term
potential
of
having
this
open
source
community
around
a
single
code
base.
It
just
helps
traders
everywhere,
so
I
think
that
initially
allocated
60
million
hbo
target
distribution
for
epoch
too.
However,
I
think
we'll,
probably
you
know
kind
of
like
instead
of
having
a
fixed
target,
I
think
we'll
just
have
certain
categories.
A
So
the
bot
cam
proposal,
that's
currently
being
voted
on,
there's
only
a
two
million
hbot
budget.
For
that,
because
you
know,
we
believe
that
a
lot
of
the
work
that
people
want
to
put
in
is
because
they
want
to
learn
how
to
write
quant
trading
scripts
and
getting
some
hbot
you
know.
Reward
for
completing
course
is
a
small
carrot,
but
the
real
reason
they
want
to
participate
in
the
bot
camp
is
to
basically
learn
and
to
acquire
skills
that
they
didn't
have
before.
A
So
that's
what
it
for
this
first
part
the
epoch.
One
review.
Does
anyone
have
questions
you
can
put
them
either
in
the
general
channel
or
raise
your
hand
and
request
to
speak?
I
see
one
question
from
joseph
savage:
are
there
any
known
issues
with
the
bittrex
connector,
so
probably
more
of
a
general
inmate
question,
but
I'm
not
going
to
take
it
now.
I
think
there
might
be
bittrex
is
not,
I
would
say,
one
of
the
connectors.
A
We
see
a
lot
of
usage
on
currently
so
that
it's
a
combination
of
probably
lack
of
you
know
demand
from
the
community,
but
also
it
could
be
potentially
issues
with
bittrex.
So
what
I
would
recommend
joseph
is,
if
you
look
at
on
the
open
issues,
I'll
put
I'll
post
a
link
on
the
general
channel,
but
basically
you
can
actually
you
can
search
for
bit
tracks
in
terms
of
open
issues
in
terms
of
code
base,
basically
just
search.
A
The
just
add
a
filter
bittrex,
just
looking
at
open
issues
right
now,
it
does
seem
like
there
are
some
issues
with
bittrex
but
yeah.
So
so
it's
something
that
I
think
we
we
yeah
it
looks
like.
There
are
some
issues
with
the
tricks,
so
so
overall,
I
think
this
is
where
we
should
be
able
to
fix
these
issues,
and
I
think
the
new
kind
of
bounty
based
model
should
allow
users
to
submit
kind
of
vote
for
certain
connectors
to
be
fixed
and
even
assign
bounties
to
them
so
diffid.
C
Thank
you,
michael
yeah.
I
have
two
questions.
Originally
we
proposed
2
million
hummingbits
to
be
distributed
for
solana,
development
work
and
we
have
now
in
total,
I
think,
claimed.
1.1
million
in
100
improvement,
improvement
proposals
and
the
question
would
be
now:
is
it
possible
to
still
create
hips
in
the
next
epoch,
for
this
development
grant
from
the
last
epoch,
or
should
we
have
to
create
a
new
proposal
for
the
next
epoch.
A
I
think
we
said
originally
that
you
know
one
of
the
rules
was
we
had
to
kind
of
claim
all
that
in
one
single
epoch,
but
I
would
say
the
reality
is,
as
we
all
know,
development
takes
time.
We
want
to
do
what
we
can
to
make
things
easy
for
the
community.
So
no,
I
don't
think
you
should
create
a
new
proposal
and
we'll
just
roll
that
hep
over
to
the
second
epoch.
C
Okay,
the
second
thing
is
what
about
like.
We
had,
I
would
say,
unexpected
troubles
when
trying
to
integrate
solana
wallets
with
the
hummingbird
client,
when
integrating
the
new
kind
of
interface,
which
is
for
central
limit
order
books
on
gateway,
the
original
amount
of
800
000
planned
for
the
serum
decks.
If
we
think
it's
not
like
it's
not
enough,
and
we
had
more
days
than
we
originally
planned,
is
there
any
way
to
also
propose
for
a
certain
additional
payment
in
case?
We
think
it
would
be
justified.
A
Yes,
definitely
actually,
so
I
think
that
would
probably
need
to
be
a
new
governance
proposal
allocating
more
tokens,
but
I
think
this
is
definitely
something
we
should
allocate.
We
should
be
flexible
on
because
you
know
again,
it
wouldn't
need
to
be
voted
on
by
the
community.
In
my
opinion,
I
think
kind
of
like
developers
doing
work-
and
you
know
doing
work
for
the
code
base-
is
something
that
that's
what
hr
tokens
are
designed
to
to
promote
and,
of
course,
as
a
lot
of
us
developers
on
the
call.
A
We
recognize
that
the
initial
scope
of
something
doesn't
always
kind
of
match
the
reality
of
developing
something
unknown
and,
like
I
think,
as
long
as
you
can
explain
what
happened
and
what
the
issues
are.
I
think
that
a
lot
of
people,
the
community
would
support
that
if
they
believe
that
extending
coming
back
to
solana
is
something
that
we
want
to.
It's.
A
B
A
A
Yeah,
that's
a
great
question.
Actually,
yes,
actually
there's
a
team
working
on
a
connector
to
sift
chain,
which
is
a
cosmos
connector
sift
chain
allocated
a
budget
to
build
a
homeowner
connector,
so
they
set
up
dao
called
petunia
that
is
currently
working
on
it
right
now.
We
should
actually
check
in
to
see
how
they're
going
because
when
they
first
started
back
in
may,
the
documentation
around
gateway
was
pretty
decent,
but
in
the
last
kind
of
a
couple
couple
months
the
gateway
dots
improved
a
lot.
A
A
Could
you
share
some
context?
We
can
add
you
to
the
telegram
group
that
we
have
with
zipchain.
I
think
there's
also
a
partners
channel.
We
have
with
them.
I'm
actually
not
sure
what
their
status
is.
We
we
last
talked
them,
I
think
about
about
a
month
and
a
half
ago,
actually
fauzi
may
have
some
more
color.
I
think
he's
gonna
yeah,
because
he's
our
engineering
lead,
who
focuses
on
gateway
so
and
he's
been
in
contact
with
all
the
developers.
B
A
Yeah
thanks
rousey.
We
want
to
make
this
a
community-based
effort,
so
you
know
with
gateway.
The
goal
of
the
gateway
is
really
community-owned
stand-alone,
middleware.
That
makes
it
easy
for
developers
from
various
chains
and
from
various
dexes
and
just
the
ecosystem
generally
to
add
their
own
connectors.
So
we
recently
published
a
lot
of
documentation
around
gateway,
so
in
the
last
release
we
now
have
a
list
of
all
the
devs
and
all
the
projects
that
are
adding
different
types
of
connectors
to
gateway,
as
well
as
improved
developer
docs.
A
So
one
note
is
that
gateway
is
still
somewhat
in
flux.
Right
now,
it's
on
the
master
branch,
but
we're
looking
at
how
to
improve
the
experience
for
both
normal
users,
who
are
just
using
coming
bot
and
who
don't
need
to
know
any
technical
skills
we
can
just
use
gateway
as
a
standalone
or
as
well
as
for
developers
that
really
want
to
use
it.
A
However,
overall,
we're
really
excited
about
gateway,
because
what
we've
seen
is
that
there's
an
you
know
ever
since
we
announced
that
there's
been
a
surge
of
people
from
various
blockchain
projects
that
want
to
work
on
it.
Obviously,
the
solana
dex
is
one
great
example,
harmony,
you
know
cosmos,
but
we've
also
had
teams
from
the
near
ecosystem
or
interested
in
connecting
to
gateway
and
building
connectors
to
near
based
amm
dexes,
as
well
as
order
book
indexes
on
year.
A
So,
overall,
I
would
say
that
the
interest
is
definitely
there
and
I
view
our
job
with
foundation
to
help
coordinate
those
efforts,
ensure
that
there's
sufficient
documentation
for
both
developers
and
users
and
try
to
make
sure
that
teams
working
on
gateway
are
talking
to
each
other,
trying
to
standardize
interfaces
for
different
exchange,
types
for
and
kind
of,
creating
reusable
classes
and
modules
in
gateway.
So
people
are
not
reinventing
the
wheel
with
every
single
dex
integration.
A
In
addition,
one
thing
that
we're
working
on
now
is
introducing
more
examples
of
ways
that
people
can
use
gateway
by
not
just
building
connectors
but
actually
creating
strategies
and
scripts
that
leverage
gateway.
One
example
is
coin.
Alpha
is
currently
modifying
they're,
proposing
a
change
to
the
cross
exchange
market
making
strategy
so
that
users
can
can
basically
hedge
on
a
decks
instead
of
just
on
central
exchanges,
so
the
cross-exchange
market
making
strategy-
you
know,
after
probably
one
or
two
releases,
should
be
usable
with
all
the
dex
connectors
in
gateway.
A
In
addition,
fauzi
our
engineer
at
foundation
is
working
on
some
examples
of
scripts
that
also
leverage
gateway.
So
overall
we're
we're
looking
to
really
integrate
the
gateway
dex
connectors
into
the
rest
of
human
body
and
truly
try
to
create
strategies
and
scripts
that
allow
people
to
you
know
trade
and
do
whatever
they
want
on
on
dex
connectives
with
gateway
is
still
a
very
still
pretty
new
project,
and
we
do
see
a
lot
of
demand
from
from
both
individual
users
and
from
professional
market
making.
A
Firms
on
trading
firms
use
gateway,
so
we'll
be
improving
it
a
lot
in
the
next
few
months,
but
overall
it's
something
that
we're
really
excited
about.
Does
anyone
have
questions
about
gateway
that
we
can
answer?
One
question
from
on
the
general
channel
from
bcf
and
the
question
is:
will
humminbot
work
with
dexes
built
on
stacks
dot?
Co.
I
assume,
depending
on
how
many
slash
how
much
liquidity
is
provided.
I
assume
stacks
is
at
the
block
stack.
Is
that
the
stacks
foundation,
the
stack
foundation?
A
We
actually
spoke
with
them
at
consensus
in
austin,
I
would
say
it
probably
depends
on
the
dex
infrastructure
on
stacks.
Apparently
there
is
one
there
is.
They
did
mention
one
or
two
dexes
that
they're
the
people
are
launching
on
stacks.
So
initially
we
set
up
a
telegram
group
with
them.
So
I
think
we
have
one
already.
So
I
would
say
if
you're
interested
in
joining
a
telegram
group,
we're
happy
to
add
you
to
it
from
a
team
working
on
a
dex
at
at
stacks
or
at
the
blockchain
itself.
Yeah.
A
A
E
You
mike
this
is
gonna,
be
pretty
fast,
but
I
have
been
hearing
a
lot
that
the
way
the
questions
are
being
raised
is
a.
Are
you
from
the
foundation
planning
on?
Are
you
going
to?
I
just
wanted
to
quickly
remind
that
everyone
that
this
is
an
open
source
project
right
and
it's
driven
by
the
community.
So
we
we
shouldn't
like
be
in
a
passive
position
here
say:
are
you
planning
on?
We
should
make
it
be
making
the
changes.
Really.
E
A
That's
a
great
point,
thank
you
about
yeah
and
I
think
I
think
some
of
the
changes
we're
going
to
propose
to
the
the
government
system
and
the
poor
court
systems
should
hopefully
be
aligned
with
that.
By
giving
you
know,
people
in
the
community
more
direction
in
terms
of
how
they
can
propose
bounties
pick
up
bounties
and
can
get
there.
You
can
also
get
rewarded
in
each
spot
for
doing
them.
C
Like
part
of
the
coin,
alpha
team
part
of
the
hummingbird
team,
and
that
I
think
I
think
we
should
somehow
or
that
we
need
somehow
a
platform
or
some
way
of
really
I
mean
okay,
we
have
the
commonwealth
forum,
but
it's
I
don't
know
it
just.
I
experienced
it
as
difficult
to
talk
about
these
complicated
architectural
decisions
and
I'm
not
sure
how
to
really
solve
it
or
how
to
do
it
better.
Maybe
you
have
ideas,
michael.
A
I
actually
do
so.
I'm
glad
you
raised
this
point
because
I
think
I
think
to
address
your
first
point,
which
is
about
kind
of
like
kind
of
centralization.
So
I
would
say
this
is
not
definitely
not
the
goal,
especially
with
gateway,
which
is
definitely
the
idea
of
gateway.
Is
that
every
single
chain,
every
single
ecosystem
has
their
own
unique
qualities,
and
so
we're
trying
to
create
a
piece
of
middleware
that
people
can
connect
it.
A
You
know
every
single
ecosystem,
so
obviously
you
know,
I
think,
bringing
in
input
from
everyone
is
something
we
want
to
encourage
because
coin
alpha
kind
of,
like
originally
designed
gateway
and
overall,
is
in
the
process
of
like
handing
off
hummingbi
to
the
community.
I
think
a
lot
of
the
architectural
decisions
were
to
be
honest,
somewhat
centralized
in
the
past.
I
think
we're
trying
to
change
that
now,
which
is
why
we're
trying
to
publish
more
documentation
but
but
to
your
latin.
A
Your
second
point:
I
definitely
agree
that
commonwealth,
while
the
integration
with
some
of
the
web
3
native
stuff
was
nice.
The
actual
kind
of
features
of
the
forum
itself
were
lacking,
especially
in
terms
of
you
know,
writing
about
code
and
architectural
changes,
and
the
experience
isn't
a
great
experience.
A
So
we
recently
did
a
poll
on
on
discord
where
we
asked
people
if
we
should
stick
with
commonwealth
or
move
to
discourse,
which
is
you
know,
kind
of
like
the
standard
form
that
most
open
source
projects
use
and
the
community
actually
selected
discourse
by
a
pretty
overwhelming
majority.
I
think
it
was
like
80
percent
of
the
voters
wanted
us
to
move
to
discourse,
so
we
actually
just
set
up
a
test
forum
yesterday
and
we're
in
the
process
of
moving
over
some
of
the
posts
from
commonwealth
over
to
discourse.
A
But
I
do
think
discourse
will
be
the
main
kind
of
a
community
forum
that
we'll
use
going
forward
and
we're
hoping
that
forum
is
a
place
where
we
can.
You
know
a
publish,
more
documentation
and
and
it's
our
thoughts
around
architecturally,
where
you
know
certain
athletes
having
about
are
headed
but
also
encourage.
A
I
would
say
there
probably
are
more
artifacts,
I
think
yeah,
I
would
say
I'll
speak
to
a
bell
and
some
of
the
corn
alpha
folks.
I
think
we've
recently
we've
added
a
bunch
of
gateway
documentation,
so
I
think
most
of
the
gateway
artifacts
are
there
and
there
actually
might
be
some
some
other
artifacts
from
our
other
notion
pages
in
the
past
that
we
haven't
brought
online.
A
We
can-
probably
you
know,
you
know,
create
a
you
know,
basically
ask
the
question:
cto,
martin
or
some
of
the
other
developers
who
are
from
corn
alpha
who've
worked
on
it
for
a
long
time
to
kind
of
chime
in
and
add
you
know
more
documentation
around
aspects
of
code
which
are
not
well
documented.
Today,.
A
A
That's
still
internal
right
now
of
like
just
some
of
the
things
that
you
know,
we
think
might
be
a
good
idea,
so
I
think
we
should
actually
try
to
bring
that
online
and
and
publish
some
of
the
things
that
you
know
we
think
would
benefit
overall
codebase,
for
example.
One
thing
we
discussed
is
adding
an
rpc
layer
in
hummingbot
and
which
will
allow
kind
of
developers
to
control
it
more
easily
and
to
potentially
even
build
an
interface
around
homingbot
or
to
run
homebot
in
headless
mode,
not
using
current
ui.
A
That's
a
pretty
big
change
and
I
think
that's
actually
one
of
the
reasons
why
coin
alpha
submitted
the
pedantic
config
management
request
that
was
recently
merged
in
so
I
would
say
that's
something
that
I
think
we're
still
the
foundation's
still
considering,
but
that's
an
example
of
I
think,
a
change
that
would
really
benefit
a
lot
of
folks
in
the
code
base,
but
it
is
a
big
change.
So
it's
something
that
I
think.
A
To
be
honest,
I
think
both
we
and
coin
alpha
need
a
better
job
of
involving
the
community
in
those
efforts,
instead
of
just
having
that
be
something
that
you
know
an
idea
that
we
have
that
that
we're
working
on
so
yeah.
This
is
something
that
I
would
say
getting.
The
architectural
improvements,
doc
invisible
to
the
community
either
on
the
forum
or
the
docs
is
something
that
we
should
try
to
prioritize.
A
D
Everyone
this
initiative
is
currently
we
have
a
rotation
in
snapshot.
We
are,
we
have
only
two
days
left,
but
we
have
the
maturity
right
now.
So
the
idea
is
that
we
are
going
to
teach
in
at
the
first
time,
three
modules.
The
first
module
will
be
how
to
code
scripts
and
when
I'm
talking
about
scripts
is
the
new
scripts
and
note
the
peer
market
making
scripts.
D
The
second
module
will
be
high
frequency
trading
fundamentals.
The
mic
is
going
to
teach
how
to
run
market
making
strategies
how
to
hedge
your
position,
how
to
be
like
a
professional
market
maker
and
the
third
module
will
be
how
to
use
the
scripts
with
the
gateway.
So
this
is
like
the
first
proposal
for
this
year.
D
Hopefully,
the
next
year
will
have
much
more
courses
we
have.
We
have
like
an
experience
in
inspiration
of
the
near
the
near
blockchain
is
doing
something
similar.
They
have
like
a
university
and
they
have
a
lot
of
courses
like
analyst
instructor
developer.
They
have
a
lot
of
of
topics
that
the
people
who
could
learn
and
the
idea
will
be
like
the
every
course
will
have
like
a
pre-work.
D
In
this
case,
we
are
going
to
code
a
b
whap,
a
b
b.
What
is
used
is
used
by,
I
don't
know
a
hedge
fund
that
wants
to
buy
a
large
amount
of
tokens
and
if
he,
if
they
use
a
market
order,
or
maybe
they
they
will
buy,
buy
all
the
other
book
and
the
price
will
be
not
good
for
for
the
that
amount
of
of
tokens
that
you
want
to
buy.
So
this
strategy
buys
a
little
bit
every
a
quantity
of
seconds
that
you
define
your
strategy
and
also
uses
your
other
books.
D
D
There
is
a
form
that
anyone
could
submit
a
strategy
with
a
description
I
will,
which
will
be
the
requirements
to
have
this
strategy
like
approach
for
us.
We
are
going
to
select
top
the
top
10
strategies
from
that
list,
and
that
will
be
like
the
assignments
that
you
have
to
do
once
to
get
35
in
the
in
the
bootcamp.
You
have
to
only
do
one
of
one
strategy
of
all
the
lists
submit
a
pull
request.
D
That
is
that
we
consider
that
is
appropriate
for
the
solution
will
be
rewarded
with
with
these
hbots.
So
in
the
in
the
proposal,
there
is
a
an
estimation
of
how
many
hbos
we
are
going
to
to
give
with
this
initiative
and
everything
that
you
want
to
ask
I'm
here
to
to
answer
all
the
questions.
Another
thing
that
I
don't
that
I
don't
tell
you
is
that
we
are
working
in.
We
are
trying
to
create
some
kind
of
certification
for
for
this
bot
camp
or
of
all
the
modules.
D
I
think
that
it
will
be
much
more
easy
to
hire
one
that
already
knows
how
to
call
a
high
frequency
trading
strategy
or
is
familiar
with
some
cool
framework
like
hummingbirds
to
do
it.
So
that's
one
of
the
initiatives
that
we
have
also
obviously
sabell
told
today.
This
is
like
an
an
open
source
project
and
obviously
all
the
ideas
that
you
have
will
be
will
be
considered
and
if
you
have
any
suggestion
in
the
process
in
the
in
the
bottom,
the
content
and
anything
that
you
want
to
contribute,
we
we
are.
B
Basically,
the
overall
curriculum
fede
already
described
pretty
much
in
detail,
and
our
goal
is
to
have
a
great
ecosystem
of
developers
that
can
help
different
partners
that
one
another
to
it
has
our
current
hummingbird
coat
base.
The
pre-work
is
optional.
So
if
you
have
already
been
diving
into
the
hummingbird
code
base,
then
that
is
totally
optional,
but
if
it's
for
people
who
are
very
new
to
hummingbot,
that
will
be
some
of
the
ways
that
they
can
get
on
board
easily.
So
yeah,
are
there
any
questions
specifically
for
the
hummingbot
bot
camp?
B
We
will
basically
launch
the
first
flagship
course.
The
scripps
developer,
one
course
first
and
then
the
question
about
the
sign
up.
We
are
currently
creating
a
website
for
users
to
sign
up
to
the
bot
camp
and
it
will
be
done
within
this
week
and
we
can
send
it
over
for
people
to
enroll
and
the
bot
camp
will
be
a
live
session.
B
D
A
Yeah
and
one
one
final
thing
about
the
bot
camp:
we
also
are
looking
for
experienced
developers
who
want
to
act
as
reviewers
for
the
submissions
that
some
of
the
students
submit.
So
I'm
sure
some
of
the
folks
from
coin
alpha
might
be
interested
as
well
as
some
of
the
other
experienced
developers
in
the
community.
So
if
you're
interested
in
that,
please
reach
out
to
bayday
or
michelle.
A
Thank
you
very
much.
I
think
this
is
a
good
first
test
of
the
of
the
audio
only
system.
If
you
have
any
feedback
about
a
format
of
this
call,
audio
versus
video,
etc.
Please
ask
foundation
staff
carlito,
jeremy
or
david
no
and
we'll
get
that
feedback
incorporated
into
future
calls.
This
call
has
been
recorded.