ping

witness wackou is now also up and running

Code: [Select]

get_witness wackou
{
  "id": "1.6.24",
  "witness_account": "1.2.778",
  "last_aslot": 0,
  "signing_key": "MUSE7ZRFMaAfDH4pMK7BQkr8ey1LDZ5Gt1r9xAsECTaXQyBSWdGFoG",
  "vote_id": "1:34",
  "total_votes": 0,
  "url": "http://digitalgaia.io",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

...and waiting for some votes 

The screenshots are outdated.  The dates are in 2014 and the terms used are for BTS1.  Could you please put up screenshots for BTS2?

I haven't gotten around to making new screenshots yet, was planning to do it after fixing everything. Currently the screenshots I could take don't show everything or some wrong fields, and I prefer to leave old screenshots for now than put broken ones. They would be very similar in spirit, though, as the UI hasn't changed much since bts1.

For those that don't know the bts_tools package, the best description can probably be given with screenshots (a picture is worth a thousand words!): http://bts-tools.readthedocs.org/en/latest/monitor.html#screenshots

-------------------------------------

A bit later than what I originally hoped for, here comes the bts_tools package ported to support graphene clients, in this case BitShares 2.0.

Given the new asynchronous model of communication via websockets, I had to refactor more than originally planned, but the bulk of it is now done, and I learnt quite a great deal in the process (wanted to look into async programming in python for some time now, and this was the perfect occasion!). Thanks go to Xeroc for writing his python-graphenelib module, that was extremely helpful in getting me bootstrapped and understanding how it all worked.

Please bear in mind that there are probably still a few things not working, or not working properly. The basic functionality is there, though:
 - cpu/ram/network connections graph
 - feeds publishing, using either a time interval (as before) or a time slot (as currently setup in the telegram chat)
 - some other plugins: wallet_state, voted_in, online, network_connections

notably missing:
 - detection of blocks missed

So for the non-faint of heart that don't mind a few quirks, you can install the tools as usual with:

$ pip3 install bts_tools
and you should get version >= 0.3. The documentation, although not updated yet, should still mostly apply to everything: http://bts-tools.readthedocs.org/

What you can do then:
 - bts2 build [tag]: builds the latest version, or a given version
 - bts2 run: runs the witness client
 - bts2 run_cli: runs the cli wallet
 - bts2 monitor: launch the monitoring tools

Things to watch out for in this release:
 - the config file is still sensitive, ie: you need to configure everything properly, there is very little checking. The default config.yaml file comes with the minimum required fields you need to configure to get something working, edit at will. If you had a previous config.yaml file, it is highly recommended to delete it beforehand.
 - in particular, you need to setup correctly an api_access.json file (as described here: https://github.com/BitShares/bitshares-2#accessing-restricted-apis - the saltpass.py script can be found here: https://github.com/BitShares/bitshares-2/blob/bitshares/programs%2Fwitness_node%2Fsaltpass.py) and configure your config.ini file to use it. This is needed to get access to restricted APIs of the client such as the network one.

What I plan to do next is to iron out the support, port the remaining monitoring plugins and stabilize the code base. Support for Muse clients should also come very soon

Let me know what you think!

witness wackou is now also up and running

get_witness wackou
{
  "id": "1.6.24",
  "witness_account": "1.2.778",
  "last_aslot": 0,
  "signing_key": "MUSE7ZRFMaAfDH4pMK7BQkr8ey1LDZ5Gt1r9xAsECTaXQyBSWdGFoG",
  "vote_id": "1:34",
  "total_votes": 0,
  "url": "http://digitalgaia.io",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

list of current seed nodes and whether they are included as dns name or ip address can be seen here:

https://github.com/BitShares/bitshares-2/blob/bitshares/libraries%2Fapp%2Fapplication.cpp#L151

I will now turn off my seed nodes as they have still not been included in the default list of seed nodes.

I still would like to offer this service to the bitshares community, so once they will be included in the bitshares client, I will bring them back up (I need about 20 minutes to do that).

well I had been thinking about those too (still need to fix my script first) but now that we can have markets with any pair of assets, probably now is the time to consider whether we want to keep those with BTS as core asset (as in BTS1), or if we want to move those market to NYSE/USD, SHANGHAI/CNY, etc.

I would say the latter, but I'm not expert in that field, so... thoughts?