mauritso

The data is coming from steemd with the debug_node plugin.

Certainly can be done. Filtering newly created accounts, define new? 1 day/1 week?

Made a static graph a few months ago displaying when the most SP is used on a day:

The screenshot was made at the beginning of syncing the blockchain data with my database, I think it might be a test category, but I could be wrong. Updated the image.

It's a little bit behind at the moment, but it looks right to me.

Thanks, fixed.

X-axis label says "Time of the day (UTC)" UTC is the time standard, same as Steem uses in the blokchain.

If you vote less than 20 times a day your STEEM power gets divided by 20. So if you vote 10 times a day each vote will still be worth 1/20 * STEEM power. For 21 or more it will be 1 / amount of votes made

Thanks for the advice, I made a thread linking to this post:

Red/yellow -> a lot of connections Blue -> not many connections. Node size is transaction volume (money going in + money going out)

It's a strategy that uses @xeroc 's bot infrastructure combined with deployment/automatic registration scripts. In StakeMachine the strategy is updated to work without cli_wallet, those changes (and more)

change: witness_url: "wss://bitshares.openledger.info/ws" to a testnet witness ("ws://testnet.bitshares.eu/ws" for example), "BTS" to "TEST" "markets:"

Thanks for the pointers. If the market is massive, the price used by the bot could be determined by the weighted (by volume/time) average price of the orders in the last 10 minutes or something like that.

Good idea. The bot uses the feed price, the STEEM:SBD market has a price feed and is based on graphene, so I think the bot already is compatible with that trading pair (might need some small adjustments

Currently it does not. Comparing markets on the DEX with markets outside of bitshares shows that there can be quite a gap between the price of other exchanges and the price on the DEX. The big problem

target_price_offset_percentage: +-percentage offset from target_price This config option is available for that (hidden in the config.py that came with liqbot, will add that)

Change the folder name, if the folder has the same name it won't work because the created containers get a name based on the folder docker-compose.yml is in.

I downvoted this post accidentally -.- The total value can go up and down depending on price swings of the assets your bot account has. The loss probably stems from that. I see no trades on and 3 trades

The loss in BTS has to do with the price movement and not with the bot, right?

As OPEN.BTC and OPEN.DGD are not smartcoins and the bot currently depends on the feed price, I can't set up a bot like that at the moment. I"ll try to figure out a way to generate a reliable price,