I've begun working again on my block explorer. I have a prototype running in #whaacked that is synced up to block ~260,000 as of writing. It's running on a local machine, located near near a beach in Costa Rica in a beautiful-albeit-not-well-infrastructured town, so please pardon the downtime. It has a few commands you can see via:
!e help
If the arguments to a function are too long to paste into a single line of irc, you can instead paste the arguments to paste.deedbot.org and then feed trbexplorer the link to the resulting paste i.e.
!e balance http://paste.deedbot.org/?id=y484
The only time I see this send-arguments-via-paste feature being useful is for the command push,1 where one will paste a potentially long hex string representing a raw txn.
The ircbot currently returns a link to a paste of the result of the command. I was tempted to return the results of certain commands, such as !e balance [ADDRESS], directly via an irc message. However this would require operators of ircbot to have to write different logic for handling the responses of different commands, so I decided to return all results via paste.deedbot.org.
There are three main items on my TODO list, not including code revision and testing.
I. Speed up syncing/scan.
It looks like it's going to take 30-45 days to sync up on my machine. It's already a nightmare to get trb itself sync'd, so any shaving off of this time will be appreciated by someone wanting to run the explorer locally.
II. Decide on data return format.
I think returning the results to queries as an sexpr, and/or something that interfaces well with Gale's Bitcoin Wallet is the way to go.
III. Implement an interface with the mempool.
As I see it, the mempool is a secondary layer above the main protocol. So it may be best to ignore the rpc commands to trb and create an ad-hoc mempool. Essentially, trbexplorer may be the only interface into the trbexplorer mempool.
- ATM push is not a tested feature [↩]







