►
From YouTube: Hummingbot Weekly Developer Call 007 | 31 August 2022
Description
The Hummingbot Weekly Developer Call is a technical and general discussion intended to gather active community developers who contribute to making the Hummingbot codebase better through Hummingbot Improvement Proposals (HIPs) and Bug Fixes.
Meeting Info:
- Schedule: August 31, 2022 : 10:00 AM EST / 2:00 PM UTC / 10:00 PM HKT
- Duration: 60 minutes
- Location: Hummingbot Discord https://discord.gg/hummingbot, in the community-call-chat at https://discord.com/channels/530578568154054663/996769563054186536
Agenda:
- Proposal to Integrate with Celo
- HIP - Revamp Hedge Strategy
- Request for All Strategies to work on both spot and futures markets
- Bounties Board's Items
- Botcamp, & its Mentorship
- Community QA
#hummingbot #developer #algotrading #cryptotrading #liquiditymining #marketmaker #trading #bottrade
A
Then
we
are
going
to
develop
the
trade
streamer
a
module.
This
will
need
to
subscribe
to
the
channel
to
the
trace
channel
of
the
support,
the
exchanges
via
websocket,
and
once
it
is
streaming
the
trades
it
has
to
transform
them
to
the
same
standardized
way
like
trading
pair
time,
some
side
amount
and
volume
and
deliver
the
messages
to
the
ohlc
manager,
because
this
new
streamer
will
only
we
start
consuming
information
via
websocket
and
deliver
the
messages
to
the
the
manager.
Then
we
will
have
the
object
that
will
be
ohlcv.
A
This
object
can
be
volume
or
time,
as
I
mentioned
your
day,
is
very
good
that
we
can
have
the
two
ohlcs.
The
volume
on
time
based
bars,
for
example,
and
also
this
object
will
have
a
threshold.
This
threshold
is,
for
example,
if
we
are
creating
a
original
time,
ohlcs
with
candles
or
every
five
minutes.
The
threshold
will
be
5
minutes
is
a
volume
of
hlc
will
have
a
candle
solve
measures,
every
100
base
asset
buys
or
sells
or
trades
sorry,
the
threshold
will
be
100..
A
So,
for
example,
if
I
am
working
in
BGC,
UCT
and
I
would
like
to
create
volume
bars,
every
50
Bitcoin
is
traded,
the
threshold
will
be
50.,
so
that's
the
threshold.
What
this
object
has
to
do.
It
has
to
receive
the
trades
and
base
it
on
the
threshold.
It
will
assign
the
open,
low,
high,
close
and
volume
of
that
candle,
and
when
the
threshold
is
met,
it
will
close
the
candle.
A
If
it's
a
Time
ohlc
the
threshold
will
be
closing
the
candle
using
the
timestamp
of
the
of
the
of
the
trade,
and
if
this
volume
it
will
use
the
accumulated
volume
of
that
candle
object
will
have
all
the
rows
of
the
hlc
that
you
are
working
on
in
that
in
the
in
your
script
and
then
the
the
last
module
will
be
the
original
CB
manager.
This
will
receive
the
input
of
the
users
like
hey.
How
many
oh
see
do
you
want
to
create?
A
For
example,
I
would
like
to
have
I,
don't
know
for
binance
ethereum
usdt,
100
ohlc
of
time
base
bars
of
five
minutes
on
volume.
Every
I
don't
know
100
ethereum.
So
with
that
information
it
will
create
the
object
of
the
oh
hlc.
It
will
initialize
the
train
streamer
and
then
it
will
check
how
many
data
it
needs
to
collect
to
start
the
bot,
for
example,
if
you
need
a
if
one
of
the
metrics
that
you
want
are,
for
example,
I,
don't
know
the
RSI
of.
A
It
will
be
like
available
to
merge,
like
the
historical
traits,
with
the
real-time
trades,
that
you
are
streaming
and
create
the
ohlc,
and
then
only
a
train
streamer
will
be
adding
more
candles
to
the
ohlc
objects,
and
the
last
thing
is
that
the
user
will
be
able
to
Define
for
each
exchange
trading
pair
the
following
like
the
following
nomenclature.
It
will
be
like
binance
paper.
Trade
is
usct
time
and
the
times
that
you
want
to
have
the
hlcs
and
volume
and
the
volume
that
you
want
to
for
or
each
ohlc.
A
A
Yeah
Mike,
the
trade
collector,
will
be
using
the
historical
trades
API
endpoints,
so
it
will
be
a
module
that
use
all
the
endpoints
of
the
historical,
the
API
of
historical
trades
and
collects
all
historical
traits
to
a
to
have
this
information
and
then
be
used
by
the
by
to
the
of
the
to
the
construction
of
the
ohc.
So
this
we
have
to
implement
in
this
change.
A
The
ability
to
collect
the
the
trades
or
probably
another
idea
could
be
use
tcxt,
for
example,
to
get
the
trades
I
think
that
is
implemented
in
the
most
of
the
of
those
changes.
This
functionality
of
request
historical
traits,
I
used
it
before
so
I,
don't
know
if
it's
for
every
exchange,
but
it
can
be
for
every
Exchange.
A
B
B
So
yes,
I,
I,
think
I
see
the
the
need
for
the
the
trade
collector
and
the
streamer
in
order
to
you
know,
can
I
get
historical
data
and
also
make
sure
that
data
is
updated
by
the
oh
CD
manager,
so
maybe
maybe
to
clarify.
How
do
you
envision
the
kind
of
like
the
user
experience
here?
For
instance,
like
does
the
user
like
initialize
this
using
a
config
file
or
from
the
hummingbot,
client
and
and
I
guess
like
if
the
person
exits
something
bot
like?
Does
this
stop
running?
B
A
Yes,
there
are,
there
are
like
two
things,
because
the
trade
streamer
will
also
start
like
collecting
the
trades
and
storing
them
in
the
in
a
CSV.
So
when
they
use
is,
if
we
make
this
microservice,
we
can
have
this
running
all
the
time
on
collecting
trades.
You
can
stop
it
when
you
want,
but
if
we
make
this
module
like
on
a
hummable
module
to
use
directly
hummingbot,
we
can
make
like
an
definition
as
we
Define
the
markets
in
the
in
the
scripts.
A
We
can
also
Define
the
markets
and
in
the
same
way,
Define
the
ohlcs
and
that
module,
and
when
you
start
the
bot,
all
in
the
background
will
start
like
the
ohlc
manager
will
start
and
will
check
in
the
for
in
the
data
collection
folder.
If
it
has
a
trades
or
not,
if
not,
it
will
start
collecting
the
traders
that
are
missing
and
streaming
the
new
trades
and
when
it's
ready
the
bot
will
start.
A
So
that's
the
the
only
the
the
other
solution.
If
we
make
it
like
on
a
microservice,
it
can
run
forever
and
start
creating
the
ohlcs
all
the
time.
And
then,
when
you
start
a
bot,
you
will
have
like
the
information
available,
because
that
service
will
be
running
all
the
time,
but
if
you
run
it
with
the
bot
once
the
bot
stops,
that
service
will
stop.
It.
B
So
so
yeah,
so
so
yeah
yeah.
So
even
though
I
wasn't
able
to
hear
Freddie's
answer,
I
hope
the
community
was.
But
if
you,
if
you
have
any
more
questions
about
kind
of
like
this,
this
PRD,
please
put
it
in
the
community
called
chat.
I
think
that
the
the
I
think
the
orchestration
project
is
a
little
bit
further
along
because
we've
already
identified
two
community
members
who
work
on
it,
I
think
the
next
stage
there
is
to
basically
create
the
proposal.
B
One
there's
still
probably
a
good
number
that
we're
still
working
with
a
developer
to
you
know,
merge
in
the
proquests
and
to
then
distribute
the
h-bot
bounties
to
them.
So
that's
one
reason
why
we're
kind
of
slowing
down
on
these,
like
you
know,
hips,
but
we
still
want
to
make
sure
that
we
collect
feedback
from
the
community
in
terms
of
what's
going
to
benefit
them
the
most
and
then
and
then
create
Improvement
proposals
only
the
ones
that
can
really
benefit.
B
A
Perfect
Mike
well
I
think
that
the
process
of
building
these
the
bounties
is
very
clear,
but
for
me
it's
very
clear
how
we
should
proceed
well.
Obviously,
if
you
have
any
feedback
about
how
we
can
improve
this
process,
let
us
know
well
now
it's
time
for
some
q
a
if
you
have
some
q
a
about
a
hummingbot.
You
can
do
it
now
on
the
chat
on
the
community
called
chat
or
if
you
have
any
suggestion
about
the
the
process
or
the
the
things
that
we
reviewed
today.
A
A
So
the
thing
is
that
first,
we
have
to
focus
on
the
issues
that
we
have
on
the
code
base
on
the
most
important
connectors
that
we
have
and
the
most
important
strategies,
improving
the
user
experience.
And
then,
when
we
have
a
better
process
and
that
is
working
properly,
then
we
can
continue
with
creating
more
hips.
When
we
finish
the
hips
that
we
have
right
now,
I
don't
know
Mike.
If
you
want
to
add
something
else,.
B
You
know
basic
hips,
so
bounties
page
spot
bounties
for
outstanding
work
that
were
still
you
know,
working
to
close
out
somewhere
because
it's
been
the
code's
been
merged
in
we
haven't
processed
distributions.
Yet
others
developer
is,
you
know,
still
working
with
us
to
review
the
code
and
get
it
in
you
know
by,
for
instance,
the
case
is
Solana
and
the
serum
project,
in
other
cases,
we've
probably
so
in
the
process
of
reviewing
the
pr
or
we're
still
waiting
for
the
developer
to
submit
CR.
B
So
so,
and
so
each
of
those
are,
you
know
like
initiatives
that
do
take
time
and
effort
to
manage.
That's
why
I
would
say
you
know
we
we,
you
know
we're
not
discouraging
people
from
creating
hips,
but
but
I
think
you
know,
there's
kind
of
like
there's
a
list,
what
kind
of
show
the
community
in
terms
of
how
many
words
right
now.
So
that's.
Why
I
think
that
the,
whether
it's
what
we
do,
encourage
a
community
to
submit
fixes
for
bugs
General?
B
So
so
I
think
that
if,
if
that's
why
for
bug
fixes
the
processes
were
not,
we
don't
even
have
to
kind
of
vote
on
them.
You
know
if
it's
anything,
that's
with
a
fix
per
class.
The
community
will
review.
It
was
the
real
buttons,
because
those
are
you
know,
those
are
bug
fixes
are
ones
that
we're
making
all
the
time
anyway,
the
code
base
for
releases
to
do
what
they've
done.
So
we
want
to
encourage
Community
to
help
us.
B
A
A
But
well,
let's
focus
on
the
bug
basic
fixes
so
for
the
ones
that
are
entering
now
in
the
in
the
Co
in
the
call,
and
if
you
can
watch
on
YouTube
the
video
where
I
show
you
the
the
bounties,
the
Bounty
the
board
of
bugs
there,
you
can
select
the
bug
that
you
want
to
work
on.
There
are
at
least
on
the
open
box
with
that
you
can
start
working
within
to
solve
some
bugs.
A
B
B
Oh
yeah
yeah,
it's
worth
thinking
buying
well
so
I'll
leave
the
question
whether
it's
worth
buying
or
not
up
to
up
to
you
know
each
individual,
a
user
as
a
as
a
reminder.
Anything
we
say
here
is
not
investment
or
financial,
but
but
I
would
say
in
terms
of
the
question
of
whether
to
reissue
or
not,
I
would
say
right
now
the
foundation
isn't
planning
to
do
any
type
of
reissuance.
B
B
B
There's
no
plans
to
reach
you
I
mean
if
there's
a
lot
of
people
in
the
community
that
want
us
reissue
we
we
can
definitely
consider
it,
but
it
seems
like
I
would
say
just
from
the
feedback
we've
seen
on
the
H5,
Channel
I,
think
one
one
user,
you
know
was
I
thought
we
should.
But
another
two
said
we
you
know
they
didn't,
they
did
not
teach
it.
So
currently,
I
would
say
you
know
without
a
strong
push.
Community
Foundation
is
you
know.
Foundation's
default
position
is
not.
B
A
B
Yeah
yeah
exactly
so
we're
still
working
on
this,
but
we'll
have
a
process
for
how
the
foundation
came,
like
you
know,
raise
a
priority
of
bugs.
If
you
know
users
are,
you
know,
are
heavily
interested.
That's
why
and
I
think
the
longer
a
bug
is
on
the
board.
You
know
and
Suspects,
just
so
considerable
and
we'll
try
to
you
know,
find
a
way
to
raise
down
incentivize.
B
So
there's
some
processes
with
the
kind
of
build
support
that,
but
it
seems
like
just
you
know
already:
we've
already
had
like
three
or
four
developers.
You
know
you
know
be
assigned
to
fix
the
bugs.
So
there's
clearly
I
think
you
know
some
interest
in
the
community.
It
fixed
bugs
and
I.
Think
for
us.
We
feel,
like
you
know,
it's
a
good
way
to
start
building
a
a
you
know
in
training,
a
stable
developers
Community,
who
are
earning
regular
income.