►
From YouTube: Hummingbot.org Community Call #7 | August 2022
Description
Monthly Community Call Agenda:
- Epoch 2 Proposed Budget and Key Initiatives
- Hummingbot BotCamp
- Exchange Certification Voting
- QA Process for Certified Exchanges
- New Community Resources
Links mentioned:
Monthly Community Call 007 (August) Agenda https://github.com/hummingbot/pm/issues/4
Sign up for the upcoming Scripts Developer Botcamp https://hummingbot.thinkific.com
Epoch 2 proposal: Exchange Certification Program https://hummingbot.discourse.group/t/epoch-2-proposal-exchange-certification-program/127
Exchange Certification poll: https://snapshot.org/#/hbot.eth/proposal/0x49cfce7ebdb766506ac1e1ef5f634ff7ff383dd1fc7f9f8383e94586b906ccef
Hummingbot Project Management Repository https://github.com/hummingbot/pm
Hummingbot StreamLit Apps https://github.com/hummingbot/streamlit-apps
Awesome Hummingbot https://github.com/hummingbot/awesome-hummingbot
Hummingbot Community Tools https://github.com/hummingbot/community-tools
A
Hello,
can
everyone
hear
me
welcome
to
the
monthly
community
call
for
humminbot
I
wanted
to
so
we
have
an
agenda
that
we
we're
gonna
publish
pretty
soon.
I
think
we
have
it
on
the
event
this
time
around.
We're
also
gonna
make
some
changes
so
I'll
wait
for
more
people
to
join,
but
we're
gonna,
we're
gonna,
we're
planning
to
live,
start
record
and
live
stream.
A
These
weekly
calls
on
youtube,
in
addition
to
you,
know,
having
recording
the
audio
so
as
we
always
do
before
you
can
post
any
questions
or
or
comments
in
the
community
call
chat
channel,
and
when
we
talk
about
various
things
during
the
call.
That's
also
when
we're
going
to
be
posting
links
to
what
we
talk
about
in
the
project
in
that
channel.
A
A
So
this
today
we're
gonna
talk
about
a
few
things.
First
of
all,
we're
gonna
talk
about
what
happened
with
the
nomad
hack
that
happened
on
monday
and
I'll
explain
kind
of
like
why
you
know
why
we
chose
nomad
in
the
first
place,
what
happened
with
the
hack
and
what
we're
planning
to
do
afterwards.
Afterwards.
A
So
with
that,
let
me
kick
things
off
by
talking
about
the
the
the
the
nomad
hack
that
happened
on
monday.
Unfortunately,
this
was
pretty
big
in
the
industry.
I
think
a
total
of
about
200
million
of
crypto
was
stolen,
so
as
background
nomad
nomad
protocol
is
a
was
a
was
a
one
of
the
newer
british
protocols
that
launched
earlier
this
year.
A
We
chose
avalanche
because
coin
alpha
was
working
with
avalanche
on
a
program
to
like
distribute,
basically
minor,
can
minor
campaigns
on
avalanche
and
would
be
distributing
hbot
on
the
avalanche
blockchain.
So
we
wanted
to
find
a
bridge
provider
that
was
secure
and
that
would
support
avalanche
because
nomad
uses
a
optimistic
verification
security
approach.
So
this
is
the
same
approach
to
use
for
auburndrum
optimism
and
other
ethereum
rollups.
A
We
we
did
some
analysis
of
all
the
british
providers
and
we
felt
that
they
had
the
most
kind
of
like
the
optimistic
approach
toward
kind
of
like
verification
of
of
kind
of
any
type
of
like
crosstalk
internation
was
safer
than
the
kind
of
the
the
more
traditional
you
know
emma
and
validator,
set
brooch,
so
and
and
also
because
nomad
the
team
was
had
had
a
lot
of
experience
and
very
well
known
in
ethereum.
They
had.
A
You
know,
raised
a
lot
of
money
from
polygon
polychain
and
some
of
the
other
top
investors
in
crypto.
We
decided
to
use
that
them
as
the
bridge
provider.
So
I
think
actually
h.
Spot
was
the
first
token
that
nomad
bridge
over
to
avalanche
and
we've
been
working
closely
with
the
nomad
team
ever
since
then.
A
Unfortunately,
what
happened
on
monday
was
that
during
a
routine
upgrade
of
the
nomad
protocol,
they
inadvertently
set
one
of
the
kind
of
like
the
connected,
the
the
basically
the
approver
addresses
to
xero.
So
unfortunately,
what
this
meant
was
that
anyone
could
essentially
copy
and
paste
prior
nomad
transactions
and
just
inject
their
own
address
in
the
recipient
field.
A
You
know,
the
majority
of
the
I
think
10
to
11
million
tokens
that
was
stored
in
the
nomad
bridge
contract
were
were
basically
stolen.
So
after
that
the
the
hackers
started
liquidating,
you
know
both
our
token
and
all
the
other
tokens
they
had
stolen.
You
know.
So
our
token,
I
guess
you
know
it
was
a-
was
a
very
small
amount
of
the
overall
pie.
However,
the
you
know
the
hackers
are
still
in
the
process
of
selling
down
their
positions
in
h-bot.
A
Do
some
analysis
in
the
next
two
days
to
understand
how
much
the
hackers
have,
how
much
is
remaining
for
them
that
they
might
be
able
to
sell
what
the
impact
was
for
people
who
had
received
h5
rewards,
especially
on
avalanche,
where
now
it's
not
worth
anything
anymore
and
what
we
should
and
basically
consider
what
alternatives.
We
have
to
try
to
rectify
this
situation.
A
Just
to
address
some
concerns
out
there
that
that
were
posted
on
discord.
I
I
think
I
think
we
should,
in
my
opinion,
I
think
there
isn't
a
big
risk
of
like
governance
attacks
and
these
things
like
that,
because
the
total
amount
of
tokens
that
were
stored
in
the
bridge
was
about
one
percent
of
the
overall
supply
and
because
of
how
delegation
works.
A
A
A
Having
said
that,
I
think
that
you
know
this
is
definitely
a
wake-up
call
for
those
of
us
in
the
foundation,
and
it
was
a
it
was
a
you
know.
Well,
I
would
say
one
of
the
like.
I
think,
we'll
we'll
cover
this
in
more
detail
in
a
you
know,
post
mortem
that
we're
working
on
right
now
and
we
aim
to
publish
by
end
of
the
week.
A
However,
speaking
personally,
I
think
that
this
was
a
big
lesson
that
you
know
you
know
like
just
because
the
the
protocol,
something
is,
has
a
good
security
profile.
The
one
of
the
biggest
risks
in
blockchain
is
operational
security.
You
know,
can
you
know,
can
a
team
take
the
the
appropriate
safeguards
to
prevent
you
know
kind
of
like,
like
of
fat,
finger
errors,
and
things
like
this
from
happening,
because
what
happened
here
was
a
very
simple
kind
of
like
you
know,
simple
bug
that
you
know.
A
I
think
it
probably
pointed
more
to
the
the
fact
that
this
was
an
immature
protocol,
whereas
other
bridge
protocols,
you
know,
even
though
they
were
kind
of
using
older
technology,
they
they're
more
mature
and
they've,
more
battle
tested
so,
and
I
think
I
think
I
think
vitalik
from
ethereum
also
wrote
one
blog
post
a
few.
You
know
I
mean
one
or
two
years
ago
just
about
the
fact
that
bridges
in
general,
you
know
bridges
in
general
are
the
most
insecure
aspect
of
blockchain.
So
I
think
in
the
future.
A
I
think
we
also
are
going
to
revisit
you
know
like.
Does
it
even
make
sense
to
bridge
a
spot,
and,
and
if
we
do,
I
think
it
would
make
sense
to
limit
how
much
is
bridged
in
terms
of
how
we're
planning
to
kind
of
handle.
You
know
like
basically
this
this
process
and
how
to
you
know
like
compensate
or
or
somehow
you
know,
ensure
that
you
know
kind
of
people
still
want
to
receive
the
hbot
token,
given
that
the
price
is
dropped.
A
This
is
something
that
we
are
still
analyzing.
I
think
first
we're
going
to
conduct
the
postmortem
on
the
on
the
on
the
hack,
determine
how
much
tokens
the
the
hackers
still
have
right
now.
I
think
they're
still
in
the
process
of
liquidating
the
positions
on
on
on
a
unit
swap,
which
is
the
only
exchange
where,
where
humminbot
is
currently
well,
h5
is
currently
active.
A
But
what
was
interesting
is
that
actually
there's
actually
been
quite
a
few
purchases
in
the
past
few
days,
which
is
you
know,
probably
probably
some
people
in
this
call
and
other
community
members
who
you
know
were
able
to
pick
up
hvac
tokens
at
a
low
price.
But
overall
we
do
think
the
hackers
are
essentially
watch
looking
for
you
know,
opportunities
to
sell,
so
in
my
opinion,
any
purchases
will
likely
trigger
them
to
sell
sell
more.
A
So
I
think
that
yeah
overall,
we
are
going
to
try
to
announce
something
in
the
next
few
days.
You
know
related
to
this,
but
right
now,
please
give
us
some
time
to
actually
analyze
the
situation
and
and
understand
kind
of,
like
you
know
what
the
impact
was
and
and
and
outlines
some
steps
going
forward.
A
If
you
have
any
questions,
please
post
them
in
the
community
call
chat,
channel
and
we'll
be
happy
to
take
them
either
during
the
call
or
or
throughout
it,
in
terms
of
how
this
affects
the
proposed
budget
for
epoch
ii.
So
in
a
government
in
a
thread
that
I
published,
I
think
last
week
I
proposed
that
we
we
stick
with
the
same
budget
of
h5
tokens.
We
had
for
epoch,
one
so
30
million
as
well.
A
This
is
because
we
didn't
end
up
using
the
full
budget
for
epoch,
one,
and
I
think
you
know,
because
the
hbo
tokens
are
supposed
to
be
for
governance.
I
think
that
the
key
to
epoch,
2,
in
my
opinion,
is
ensuring
that
the
foundation
is
sustainable
from
a
revenue
perspective
from
the
exchange
feature
agreements
once
well,
once
the
foundation
is
sustainable
and
is
able
to
store
the
excess
cash
flows
that
it
earns
into
treasury,
then
the
hbot
holders
can
then
direct
how
that
treasury
is
used.
A
A
I,
I
think
that
a
lot
of
the
initiatives
for
epoch
2
are
related
to
kind
of
ensuring
sustainability
from
a
revenue
standpoint
for
the
foundation,
which
also
benefits
the
community
as
well,
because
some
of
these
exchanges
that
are
are
giving
out
fees.
You
know
some
of
these
rebates
also
go
back
to
users
as
well.
A
However,
in
light
of
the
in
light
of
the
the
nomad
hack
this
may,
this
may
cause
us
to
propose
a
higher
budget
for
epoch
2,
because
the
price
of
the
hvac
tokens
is
now
lower.
Due
to
you
know
the
additional
supply
of
the
market.
There's
also,
you
know
more
tokens
outstanding.
So
we
want
to
make
sure
that
you
know
the
the
people
who
have
hbot
feel
like
they
have
enough
to.
You
know
actually
submit
proposals
and
actually
vote
on
proposals.
A
So
in
the
meantime,
I
think
there's
enough
budget
from
the
leftover
epoch,
one
budget
to
still
proceed
with
some
of
the
key
initiatives
that
we
have
for
epoch
ii,
one
of
which
is
the
hum
about
bot
camp,
which
is
a
free
developer.
Boot
camp
that
we're
starting
in
september
in
order
to
teach
the
community
how
to
customize
and
create
their
own
humminbot
scripts.
A
So
as
background
scripts
are
a
new
module
that
we
added
recently
that
allows
anyone
to
create
python,
simple
python
strategies
and
just
a
few
lines
of
code,
they're
less
a
lot
lighter
than
the
traditional
strategies,
because
they
don't
have
a
configuration
file.
However,
they
actually
have
the
full
power
of
of
strategies
because
they
can
use
any
aspect
of
the
humanbot
connectors.
A
So
because
of
that,
we
feel,
like
you
know
the
key
to
actually
growing
the
community.
The
key
to
actually
you
know
basically
ensuring
that
we
have
more
and
more
users
sticking
with
hummingbot
and
actually
making
money
off
of
writing
their
bots
is
to
teach
them
how
to
actually
build
their
own.
You
know
trading
strategies
and
we
think
the
scripps
module
is
the
the
best
place
to
start,
because
it's
the
simplest
way
to
actually
build
an
automated
trading
bot
and-
and
we
can
teach
you
know
anyone
we
feel
like.
A
A
C
B
Well,
thank
you
mike
for
explaining
the
stage
with
the
the
alex
protocol,
the
on
the
no
no.
They
know
what
protocol
well
regarding
to
the
botcom,
we're
going
to
start
the
botcom
on
a
beta
group
this
friday,
just
to
review
the
content
and
make
the
best
experience
for
you,
the
first
batch
and
well
how
which
are
which
are
going.
We
are
going
to
explain
the
bottom.
B
Well,
that
will
be
like
the
the
second
session,
sorry,
the
first
session
that
will
be
recorded
that
you,
you
could
see
the
times
that
you
want,
and
after
that
we
will
have
our
first
live
session,
that
we
are
going
to
do
some
q.
A
regarding
to
the
question
the
regarding
to
the
content
of
the
prerequisite
session
and
also
after
the
q
a
we
are
going
to
have
a
live
coding
session
of
of
a
dimension
to
put
some
hands-on
on
the
code
and
then
how
I
designed
this.
B
And
the
view
is
like
a
strategy
that
a
big
hedge
funds
or
people
that
wants
to
move
a
lot
of
money
use
just
to
don't
move
the
price
of
the
other
book
a
lot
and
start
buying
over
the
time
a
little
amount
of
tokens.
So
that
would
be
the
strategy
that
we
are
going
to
implement
that
in
the
live
coding
session
too.
In
the
last
conversation,
one,
sorry
and
and
well-
and
with
that
we
are
going
to
finish
the
first
edition,
then
what
you
have
the
second
light
session,
the
you
can
share
your
strategies.
B
Of
contact
between
developers,
traders,
people
that
wants
to
show
their
strategy
these
people
that
wants
to
ask-
is
this
a
makes
sense
or
not?
And
well
obviously
you
can
do
some
q
and
a
there
too.
Well
after
that
session,
you
will
have
two
weeks
to
submit
a
script
strategy
based
on
a
list
of
strategies,
ideas
that
we
were
collecting
so
those
strategies,
ideas.
B
To
do
exactly
what
that
strategy
idea
says
suppose
one
strategy
idea
is
portfolio,
rebalancing
what
and
japanese
you
have
to
buy
you
how
to
maintain
the
portfolio
x
with
each
of
each
token.
Well,
you
can
create
a
new
version
of
this
portfolio
or
you
could
stick
to
the
the
that
version,
but
the
the
main
thing
is
that
you
have
to
to
say:
okay.
What
I
would
like
to
this.
B
The
purpose
is
how
it
works
and
the
explanation
how
it
works,
and
then
the
code,
the
exp,
stands
that
that
idea
after
that
we're
going
to
review
all
the
submissions
and
they
will.
We
are
going
to
select
a
top
five
solutions
in
all
the
different
from
all
the
different
submissions,
the
top
five.
We
will
receive
a
the
announcement
in
the
snapshot
proposal,
but
I
think
that
it
will
were
50k
of
facebook
exports
and
the
other
normal
submissions
that
are
approved
because
we
have
to
review.
B
Is
really
by
the
by
the
let's:
try
the
script,
so
if
that
submission
is
approved,
you're
going
to
receive,
I
think
that
was
like
10k
of
h
votes.
So
well,
that's
the
information
of
the
botcom
the
first
session.
The
first
live
session
will
start
the
first
of
september
and
well
that
I
think
that
that's
all,
if
anyone
has
a
question
regarding
to
this,
there
is
a
mic,
a
post
link
for
thing
up,
bootcamp.
A
B
C
A
Asks
in
the
chat
you
know
they
signed
up
for
the
buck
camp
and
they
asked
about
the
beta.
So
so,
unfortunately,
the
beta
is
full
already
we're
just
doing
that
with
about.
I
think
10
community
members
just
to
kind
of
verify
that
the
the
the
whole
process
is
working
but
because
the
the
actual
block
camera
is
gonna
start
in
less
than
a
month.
A
I
would
advise
anyone
to
sign
up
to
wait
for
the
actual
bot
camp,
with
a
caveat
that
I
think
we
actually
have
so
many
signups
that
we
had,
I
would
say,
yeah,
depending
on
when
you
signed
up
for
the
bot
camp,
it's
possible
that
you
won't.
You
won't
be
able
to
make
it
into
the
first
batch
even
in
september.
I
think
we've
had
over
like
something
like
70
or
80
signups
now,
so
I
think
we
have
to
we're
going
to
use
it
beta.
A
One
of
the
purposes
of
the
beta
is
to
try
to
figure
out
how
many
students
we
can
actually
support,
given
you
know
kind
of
like
because
there
is
a
need
to
review
everyone's
script
submissions
and
to
help
them
with
it.
So
we're
trying
to
gauge
like
how
many
we
can
actually
accommodate
in
a
batch
before
you
know
kind
of
kind
of
actually
starting
that
first,
one
in
september.
A
So
this
is
at
zero
cost
to
users.
You
know,
basically,
what
it
means
is.
You
know
whenever
you
use
hummingbot,
there's
a
identifier
built
into
the
code
that
identifies
your
trade,
that's
coming
from
hummingbot,
and
this
is
in
exchange.
We
have
partnerships
with
a
few
major
exchanges
that
rebate
fees
based
on
how
much
volume
users
have
been
generating
to
be
honest
in
the
past
we've.
A
You
know:
coin
alpha
for
maintaining
the
code
base,
but
instead
kind
of
like
is
building
what
we
think
is
much
more
sustainable
in
the
long
run,
which
is
a
truly
community
based
project.
So,
but
now
that
I
think
you
know
it's
clear
that
you
know
we
need
to.
We
need
to
make
sure
that
we're
doing
sustainable,
so
we
can't
rely
on
a
grant
coin
alpha.
You
know
in
the
long
run,
so
that's
why
the
focus
for
epoch
2
is
ensuring
that
you
know
we're.
A
Actually,
you
know
being
transparent
to
the
community
about
how
these
programs
work
and
getting
your
help
in
in
helping
us
pick,
which
exchanges
we
should
actually
focus
on
and
grow.
The
fee
share
volume
that
it
comes
from
because
the
right
now
I
think
the
fee
share,
I
think
it's
about
30
or
40
000
every
month.
That's
still
not
enough
to
pay
all
the.
A
I
think,
there's
a
lot
about
11
to
11
people
that
work
full-time
for
coming
up
foundation
and
those
people
are
engineers,
qa,
community
managers
and
and
we're
all
here
to
kind
of
support
the
community.
But
I
think,
in
order
for
us
to
kind
of
keep
on
doing
our
jobs
and
to
have
even
some
some
leftover
that
we're
storing
in
treasury.
I
think
that
it'll
benefit
everyone.
If
we
all
understand
you
know,
where
does
that?
Where
does
the
money
come
from
and
how
do
we?
A
You
know
ensure
that
we're
delivering
the
best
possible
experience
on
those
exchanges
and
how,
in
focusing
our
limited
bandwidth
on
supporting
those
exchanges,
so
so
the
thread
that
I
post
explains
kind
of
like
what
the
differences
are
between
certified
and
non-certified
exchanges.
This
is
actually
very
similar
to
what
other
open
source
you
know.
Trading
kind
of
like
projects
like
ccxc
are
already
doing,
and,
and
one
of
the
reasons
that
we're
pursuing
this
is
because
we
learned
recently
having
because
we're
actually
starting
to
work
with
ccxt
and
other
open
source
projects.
A
We
learned
that
some
of
the
other
open
source
projects
out
there
are
are
earning
a
lot
more
fees
than
we
are
from
from
the
exchange
feature
agreements.
I
believe
c60
is
making
someone
order
like
four
hundred
thousand
dollars
every
month
from
exchange
feature
agreements,
so
I
think
there's
a
lot
of
room
to
improve
for
having
a
foundation
if
we
all
focus
on
it.
So
the
the
same
thread
has
a
table
actually
I'll
post
a
table
here
as
a
link
as
well.
A
There's
we
actually
create
a
table
which
summarizes
all
the
feature
agreements
and
how
much
you
know
what
they
are
and
how
much,
how
much,
basically,
how
much?
How
much,
how
much
kind
of
like
you
know,
fees
we've
collected
from
them,
what
the
rebate
actually
is
and
also
what
the
rebate
to
you.
Users
are
because,
in
some
exchanges,
like
gate
and
ok
x,
the
dashboard
actually
allows
us
to
select
which
how
much
of
the
fee
share
we're
sharing
back
with
users,
and
so
I
think
so.
A
This
is
also
a
way
for
users
to
get
a.
You
know
basically
have
a
discount
on
their
trading
fees
as
well,
when
they
use
hummingbit
as
opposed
to
other
tools.
So
the
reason
we
put
we
put
this
this
information
out.
There
is
because
we
I've
we've
also
created
a
poll
that
that
basically
allows
people
to
start
voting
on
on
exchange
certification.
So
we
just
created
that
fold
today.
A
So
basically
I'll
put
that
poll
in
the
chat
as
well,
and
this
poll
will
run
for
seven
days
and
it
will
allow
anyone
with
hbots
to
vote,
for
which
of
these
eight
exchanges
with
feature
agreements
should
be
certified.
Basically,
once
once
the
vote
is
ended,
the
foundation
will
look
at
which
exchanges
have
more
than
50
percent
approval,
and
those
will
be
the
exchanges
that
are
certified
for
epoch
2..
This
doesn't
mean
we're
going
to
cut
out
any
exchanges
from
the
code
base.
A
Overall
hummingbot
is
an
open
source
code
base,
and
so
you
know
one
of
our
features
is
anyone
can
submit
a
pull
request
and
if
it
passes
governance,
you
know
and
pass
the
review
that
pull
request
gets
merchant.
So
we
will
always
have
more
and
more
exchanges
that
are
being
added
to
the
code
base,
but
because
our
bandwidth
is
limited,
we
can't
offer
the
same
level
of
support
to
all
of
them.
A
The
qa
team
will
run
kind
of
like
ongoing
test
bots
and
do
a
lot
more
qa
focused
on
the
certified
exchanges,
and
also
the
community
managers
will
will
only
kind
of
like
will
focus
their
support
on
users
on
the
certified
exchanges,
as
opposed
to
the
non-certified
exchanges.
I
I
think
for
the
this
does
mean
that
you
know
as
there's
a
trade-off
here,
which
is
that
for
the
the.
A
A
C
A
C
Yeah
thanks
mike
good
morning,
good
afternoon
and
good
evening
to
everyone.
So
here
is
this.
This
part
of
the
call
is
about
the
great
process
for
certified
and
non-certified
exchanges,
so
for
qa
testing
up
on
the
pull
request,
submission
and
review
each
connector,
we
have
to
make
sure
it
should
be
working
and
performing
as
expected,
compatible
with
the
hummingbird
strategies
and
for
the
liquidating
mining
purposes
as
well.
C
Also,
a
part
of
qa
task
for
certified
exchanges
is
that
we
continue
to
monitor
github
issues
and
add
labels
and
priority
on
how
it
impacts
our
humminbot
client.
So
we
do
have
a
checklist
which
will
be
shared
this
week,
probably
a
public
page
or
on
our
discord
discourse
forum.
So
from
the
the
checklist
we
make
sure
everything
is
all
green
before
we
approve
the
certified
connector.
C
Another
is
doing
multiple
orders
and
multiple
bots
for
multiple
bots.
What
we
on
the
qa
side,
we
do.
The
approach
here
is
we
use
docker,
build
and
run
different
instances
with
the
same
api
and
same
exchange,
yeah
moving
forward
for
the
field
events.
The
qa
process
is
we'll
make
sure
the
history
provides
the
the
number
of
the
correct
number
of
trades.
C
The
history
verbal
shows
the
trade
data
of
each
field
orders
and
it
should
be
matching
from
the
csv
file
from
the
humminbot
client
and
the
exchange
trade
history,
so
ongoing
connector
testing.
So
a
part
of
the
qa
process
for
certified
connectors
is
that
we
on
the
qa
side
have
a
dedicated
server
where
we
run
multiple
tests
and
we
are
running
different
strategies
and
different
types
of
config
for
certified
connectors
on
the
on
a
daily
basis.
C
Qa
must
check
this
test
box,
make
sure
the
log
files
I
review
the
log
files
check
whether
there
are
some
errors
or
cross
check,
whether
on
between
the
client
and
the
certified
connector
from
there.
If
there's
something
wrong,
and
then
we
conduct
an
investigation
task
where
we
create
github
issues,
and
it
usually
take
days
before
we
make
sure
this
is
a
valid
issue
for
running
test
bots.
Like
I
said
earlier,
we
do
have
multiple
test
bots
running
per
certified
connector.
C
We
have
to
make
sure
we.
There
is
like
a
test
plan
for
every
strategy
for
pre-market
making.
At
the
moment,
we
are
running
like
multiple
orders,
with
hanging
orders
enabled
with
a
value
on
the
having
hanging,
order,
percentage
and
monitoring
if
it's
properly
cancelled
or
whatnot
so
yeah.
Currently,
we
have
like
seven
bots
running
with
different
strategies
and
configs
and
moving
forward.
C
We
will
be
planning
to
at
least
change
the
approach
where
we
check
the
support
channel,
whether
there
are
some
issues
being
reported,
and
then
we
try
to
come
up
with
a
test
plan
for
it
and
then
set
up
about
and
then
see
how
it
goes.
So
that's
how
we
do
on
the
qa
side.
So
how
often
do
we
check
this
test
was
on
on
certified
connectors
so
for
qa
we,
like
I
said
earlier,
we
do
it
on
a
daily
basis.
C
We
normally
check
this
one
or
our
qa
test
server,
so
moving
on
for
non-certified,
this
is
still
being
tested
by
the
foundation
qa
team.
However,
we
have
and,
however
there
is
like
a
modified
connector
testing
checklist,
which
will
also
be
shared
later
this
week
for
the
connector
maintenance
once
the
connect
be
it's
gonna,
be
non-certified
exchange
just
pass
or
all
green
on
the
checklist
that
we
created
the
community.
It
will
be
approved
by
the
pull
request
proposal
and
then
from
there.
C
We
would
like
we
will
be
creating
some
guides
as
well
for
the
community
so
that
they
have
like
an
overview
on
how
we
test
the
the
connectors
and
how
a
week,
and
also
we
are
planning
to
create
some
projects
or
tasks
for
the
for
the
community
to
at
least
have
a
better
experience
with
checking
or
testing
certified
connectors.
So
all
of
this
will
be
shared
again
on
a
public
page
or
this
on
our
hummingbird
discourse
platform.
A
Yeah
thanks
ralph
yeah
yeah,
so
so
I
hope
that
gives
everyone
a
summary
of
kind
of,
like
all
the
work
that
the
qa
team
does
and
how
we're
planning
to
kind
of
like
really
focus
those
efforts
on
the
certified
exchanges.
As
rav
mentioned,
we
will
still
do
some
testing
for
the
non-survive
exchanges
when
someone
submits
a
pr,
but
the
level
of
testing
will
be
much
lower
and
we
will
not
run
ongoing
kind
of
test
bots
for
the
non-certified
exchanges.
A
A
A
Okay,
so,
unfortunately
I
think
carlito's
having
some
issues
with
his
mic.
So
let
me
let
me
go
and
maybe
kind
of
like
summarize
what
I
think
he's
gonna
talk
about
and
I'll
just
make
sure
that
we
at
least
post
the
resources
available
on
on
hummingbit.
So
so
what
we've
been
doing
recently
is
adding
more
github
repositories
to
the
hummingbit
one
as
well.
So
carlito
has
published
a
four
new
github
repos
that
that
we
have
now
in
hummingbot
in
the
community
called
chat
channel.
A
So
I
wanted
to
just
walk
through
each
of
these
in
particular,
so
one
of
them
is
called
streamlit
apps,
so
that
one
is
basically
a
set
of
companion,
dashboards
and
data
apps
that
that
federico,
our
engineering
lead
has
added
using
streamlit.
So
streamlight
is
a
pretty
popular
open
source
framework
for
adding,
basically
any
type
of
like
visualization
or
chart
or
dashboard,
and
it's
actually
quite
easy
to
create
these
dashboards.
And
so
we've
created
a
few
as
examples
in
that
repository.
A
One
of
them
is,
is
basically
just
helps
analyze
cross-exchange
market
making
data
across
different
different
different
tokens
exchanges.
So
you
can
plug
in
a
token
and
see
kind
of
where
the
spread
and
volume
of
that
token
is
across
exchange
landscape.
This
is
really
helpful
if
you're
running
either
cross-exchange
market
making
or
arbitrage,
because
you
can
see,
for
instance,
looks
like
the
avalanche
token.
A
You
know
what
the
spread
is
for
avalanche
and
binance
versus
all
the
other
exchanges
for
the
avalanche
token,
my
trade
and
then
it
helps
you
identify
which
exchanges
you
should
be
using
to
maximize
like
the
differential
between
between
you
know
kind
of
like
actually
between
different
between
different
exchanges.
So
you
can
capture
that
spread
more
easily,
there's
also
an
app
that
helps.
You
see
the
all
the
trades
that
have
happened
in
a
particular
homebot
instance.
A
Now-
and
it's
actually
now
that
we
have
depth
connectors
index
focused
strategies
in
humminbot.
We
think
that
this
is
probably
one
area
of
growth
for
the
industry
as
a
whole
and
for
our
user
base.
So
we
added
a
a
basically
kind
of
just
a
a
really
easy
way
for
people
to
visualize
how
much
liquidity
you
know
versus
the
market.
Cap
of
a
protocol
exists
on
different
blockchains
for
different
dexas,
and
I
think
it's
helpful
in
identifying.
A
A
You
know
videos
that,
like
that
we've
created
and
people
have
created
to
talk
about
hummingbi,
and
so
we
wanted
to
just
create
one
guitar
repository
that
puts
all
that
in
one
place
so
that
anyone
who
wants
to
you
know
kind
of
like
contribute
to
it
or
or
see
what's
available,
can
access
all
that
in
a
single
location,
the
third
one.
It's
called
community
tools.
So
recently,
we've
had
a
couple
of
of
improvements
that
people
have
submitted
that
we
have
been
approved
by
by
by
improvement
proposals.
A
So
one
of
them
was,
I
think
we
have
a
with
this
discord.
User
named
james
p.
Magic
who
created
a
visualization
tool
for
hummingbot
and
also
lojack
who's
on
call
today,
has
created
a
tool
to
help
you
manage
multiple
bots
and
to
visualize
how
they're
operating
so
those
those
kind
of
community
tools
will
be
added
to
a
new
repository
called
community
tools
where
every
folder
in
the
repository
is
a
different
tool.
A
So
we're
still,
I
think,
establishing
the
process
for
that
trying
to
make
sure
that
the
initial
contributions
are
passing
review
and
they're
working.
But
we
see
that
as
something
that
we're
going
to
keep
on
growing
over
time,
because
in
the
past,
there's
actually
a
number
of
tools
created
by
community
members
that
we
want
to
make
sure
are
available
to
everyone
else
in
the
community.
A
Finally,
last
but
not
least,
I
want
to
just
also
shout
out
the
the
pm
repo,
where
we'll
be
posting
the
agenda
for
each
of
these
weekly
calls,
as
well
as
the
the
notes
and
the
recordings
afterwards,
so
the
cadence
will
be
we're.
Gonna
do
a
call
at
the
same
time
every
week.
Basically
this
time
I
think
it's
you
know,
2
p.m,
to
3
p.m,
utc
time,
and
so
that
and
every
month,
once
a
month,
it'll
be
a
general
community.
A
Call
like
this
one
and
the
other,
the
other
three
to
four
weeks
of
the
of
the
month.
They
will
be
developer,
focused
focus
more
on
kind
of,
like
you
know,
working
with
community
contributors
to
help
them
understand
kind
of
like
the
technical
architecture
of
codebase,
how
they
can
earn
hbot
tokens
for
fixing
bugs
contributing
bounties
reviewing
code
and
doing
other
things
that
will
basically
focus
more
on
the
technical
nature
of
the
code
base.
A
So
with
that
kid,
and-
and
with
that
cadence,
we
plan
on
using
this
pm
repo
as
a
resource
that
we're
putting
on
the
agendas,
storing
the
notes
and
recordings
afterwards
and
basically
storing
a
record
of
how
hummingbi
is
is,
is
going
to
improve
in
the
future.
This
is
actually
modeled
after
how
ethereum
foundation
kind
of
manages
their
core
dev
calls.
A
So,
with
these
four
repos
that
serve
as
companions
to
the
general
humminbot
codebase
repo,
we.
We
hope
that
this
is
once
one
step
in
the
transition
to
becoming
a
fully
community
maintained
codebase.
So
in
the
past
I
think
in
in
the
first
epoch
it
was.
It
was
probably
very
unclear
how
the
community
could
contribute.
You
know
what
the
process
was
for
voting
hbot
tokens,
you
know
and
even
kind
of
what
the
what
the
direction
of
homebot
would
be.
A
This
is
something
that
we
hope
to
to
fix
in
starting
second
epoch
and
and
so
we're
trying
to
basically
be
much
more
transparent
in
how
we're
handling
things
the
community.
So
if
anyone
has
questions,
please
post
them
in
the
in
the
community
call
chat
now
and
we'll
try
to
answer
them.
I
guess
in
the
next
few
minutes.