Topic: bitcoind-ncurses: Terminal front-end for bitcoind - page 4. (Read 11314 times)

A few updates:

Lots of speed improvements and eliminating needless queries.
Better error handling if commands fail or connection fails.
Various bug fixes.
The block viewer now supports browsing through older blocks and arbitrary block height or hash.
The genesis transaction would fail as bitcoind does not index it.
Formatting changes to monitor mode (age of transactions).
Difficulty, nethash and mempool transactions added to monitor mode.
A peer viewer has been added - currently listed is sync node status, incoming/outgoing status, node IP (if available), received and sent data.

I wanted to thank users again for making suggestions and testing so far.

Thank you both.
virtualx, it may work with older Python versions, 2.7 is all I've tested.

Pushed a few updates since the original post.
A lot more is event driven now.
The transaction and block browsers have scrolling support (tested with 200KB transactions with hundreds of inputs/outputs) and should be _much_ smoother.
Only remaining obstacle is the main updating view (called every second or so).
I intend to set up and test over SSH at some point to see if there are issues with redrawing.

If anyone has feature requests I will be glad to look into them as time allows.
Next is to add support for querying an arbitrary block, prev/next block and so on.

Looks very cool, I will look into this today.

Edit: good to see it needs Python 2.7

Actually, the 'received ... ago' display is time since last received block (including verification time).
This is because at present it constantly (every 2 seconds or so) polls with getinfo.

If blockheight changes then it goes ahead and pushes a getblockhash/getblock combo to find timestamp and size.
My understanding is that there is no need to check getbestblockhash because the height should never reduce.

This fails for the first block on startup and just displays the time of first contact with bitcoind.

Very neat.  Perhaps to go with the bandwidth stats some mempool stats and a time since last received block?— for the latter we might need to adds something to the rpc, I don't think we expose what time we received a block.

Here are some screenshots of the various modes.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Greetings,

I've been working on a Python front-end for bitcoind for the past few days.
The principal motivation was to give myself a reasonable way of monitoring my node without using CLI.

I thought it might be useful to others so I've made it available on GitHub: https://github.com/azeteki/bitcoind-ncurses

As it's been hacked together rapidly it is fairly limited on features and 'just about works' at present.
Best to treat it as a proof of concept for now, though it is perfectly usable for watching only.

As always, make sure you audit before running (I've tried to seperate out potentially vulnerable stuff like RPC calls as much as possible).

Regards,
Atelopus Zeteki
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJTrfn2AAoJEOK9FOwsfUWPCykQAK2yBLXlg3iJ6D1OSGjKeh1r
YrsXHwODQ9vx92ucIdQEQ085+E3qKqVBOTv0hQHmKC7BSo7XoDfSvuCxYjzQEtWX
8Kpn+scIzi2GQXL+wRCVKVo72lLdzjr3r/nPNm36n63LmDqBE14HTe1rgnfsw6oH
CRe8Czdx6q12dicBaARvBxs07s8lARr/rIxxvB2SPyGLTkdNbg5jzhf28FiB8XyI
MrxdCt0OHYLPlArHDswJlUVwgu6/Us8aL3e3nxYvlEJPqM/dX/4rlMembl3eNTmJ
3JiKkNFIITcKvy3p8Z0jHHo5l8YwOjN4H4M70lhL4JAuJJCTYb+oqKuUoxcWObDG
XiXrWfx8/TRfBYDFmqys3hWz7gGm3ssTsobb5cdvywC00DrSfTUKGnNvzLDWID5A
yTek73cs6scgDOrdRZQr7sGUI+rKd80B2v/AxA2zGfgq7WQ7WKJbAwkJVnp6HhOG
XbQk91geG07XE/nQbxa2hfEUvNMQL3wfPWyvEc4oBMnJqheeptb5tpw30mq8+tpQ
gz7vUgBkJLiGi0P/zyi0YLDWCJxIFaCBj4BoFFFmpbMF1tO+XTSTlMhX81pO4vrw
2agjnMd/bI1S2MXH3LNgu9K1blio47rrPTsvDJX/MFkeAky7da2rj/POWeCE4j81
y8JclVhdbEHfO/DdoGFv
=84Pj
-----END PGP SIGNATURE-----