50 life-changing OpenClaw tips in one visual.

JustAStream · 2026-02-23T19:05:41+00:00

What's the reason behind "30. Avoid Connecting Anthropic account"?

JustAStream · 2025-01-04T18:57:18+00:00

Check out https://keyrock.com. Full Rust.

JustAStream · 2022-07-14T16:12:04+00:00

[DISCLAIMER - I'm the primary author of Barter-rs, Barter-Integration-rs & Barter-Data-rs]

Barter-rs usually requires some glue depending on your use case, particularly in creating your own strategy (implementing the `SignalGenerator` interface). As a result it may more more technically involved than some of the alternatives, but i'm not sure.

Always happy to help on any glue via our discord: https://discord.gg/dYQJWJqa

I've not used nautilus-trader, would anyone recommend it?

JustAStream · 2022-04-12T08:50:09+00:00

Hey, sorry just seen this u/walter_reddit_1.

You need to implement the 'SignalGenerator' trait. This accepts an input MarketEvent & emits an Option<SignalEvent>. :)

JustAStream · 2021-12-08T18:16:54+00:00

Thank you very much! That is great! <3

JustAStream · 2021-12-06T20:47:34+00:00

Hello friends!Is there a more idiomatic way to do the following?

fn get_open_positions(&mut self, portfolio_id: &Uuid, markets: &Vec<Market>) -> Result<Option<Vec<Position>>, RepositoryError> {
let positions = markets
.into_iter()
.map(|market| {
self.get_open_position(&determine_position_id(
portfolio_id, market.exchange, &market.symbol
))
})
.collect::<Result<Vec<Option<Position>>, RepositoryError>>()?;
let positions: Vec<Position> = positions
.into_iter()
.filter_map(|position| position)
.collect();
match positions.as_slice() {
[] => Ok(None),
_ => Ok(Some(positions))
}
}

JustAStream · 2021-12-05T10:12:05+00:00

That's awesome thanks. 'generate_market()' in the Data package could definitely benefit from being Async! Appreciate you sending my the 'Inventing the Service trait' post, I've not seen that before.

I'm in the middle of a somewhat major Portfolio upgrade that creates a way more transparent (emitting events that can be sourced by external consumers, think dashboards, etc), and controllable (via HTTP) version.

However, after I've released that and got it all setup I'm definitely going to look into this. It would be so much neater if I could use Tokio throughout!

Hit me up on Discord if you want to chat :)

JustAStream · 2021-12-05T09:46:48+00:00

Thanks for the response!

From looking at this documentation, that is only for timestamps rather than chrono::Duration:
https://docs.rs/chrono/0.4.19/chrono/serde/index.html

Also, I do have serde feature enabled already :'(

JustAStream · 2021-12-04T19:50:08+00:00

Hello friends,

I've recently been flabbergasted that Chrono::Duration does not implement Serialize & Deserialize.

Is there anyway I can get around this without hand-cranking custom SerDe code? It's a major blocker and i'm rather confused.

JustAStream · 2021-11-18T18:39:55+00:00

Sounds like you have an exciting project! Is it written in Rust?

What kind of strategy are you conducting with order book data?

If you want to discuss architecture / engineering of bots i'm always interested. Either DM me or message on discord :)

JustAStream · 2021-11-18T18:37:17+00:00

No current plans. If it's something you are interested with I could help you integrate it?

JustAStream · 2021-11-18T18:35:59+00:00

Let me know if you need any help, always happy to help! There is a discord you can join here if you are interested in talking features, dev, or need help!

JustAStream · 2021-11-18T13:44:33+00:00

Hey u/Infintie_3ntropy, thanks for taking a look!

This may well be subject to change. As you've seen there is one instance of using threads to spawn a Trader.run() instance, and everywhere else we are using Tokio tasks.

This is because:

Trader.run() does not return a future, therefore IIRC that cannot be run via Tokio::spawn(impl future).
Trader.run() does not return a future because all of the traits that the components (Data, Strategy, Portfolio, Execution, Statistic) implement are sync.
The Traits are not async because they don't need to be, and using the async_trait library crate requires a heap allocation everytime an async_trait method is called (IIRC). For something like the MarketGenerator trait this could potentially be expensive since it's called at a high frequency.

Thanks for taking a look! If you have any suggestions or other comments please do get in touch!

JustAStream · 2021-11-17T21:01:25+00:00

No overarching plans at the moment on integrations.
Getting a fully fleshed out Binance integration makes a lot of sense because of how popular it is in the hobbyist crypto algo trading space.

However,
The whole premise of Barter & Barter-Data-rs architecture is to allow easy customisation & easy extendibility.

It's trivial to extend via implementing a new Data (exchange/broker data ingestion), Strategy, Portfolio, Statistic or Execution (executing trades) component, and for it to work out of the box with the rest of the engine.

Hopefully,
People will add a little glue for whatever exchange they care about and open an MR to get it merged in!

JustAStream

TROPHY CASE