* Defunct abe.fcgi processes not letting abe.py exit.

* Bitcoin 140176 failed to catch up: str(exception) == "1".  Should
  probably limit the kinds of exceptions that catch_up converts to
  warnings.

* Test for a portable "begin transaction" and use it.

* Consider retesting SQL flavour every time on startup.

* Start a test suite, especially for out-of-order blocks and reorgs.

* Add search by date/time within chain.

* Show auxiliary proof-of-work data.

* Consider porting to libbitcoin.

* Use explicit constraint names.

* Speed up initial load by disabling unneeded constraints temporarily.

* Perhaps rewrite adopt_orphans iteratively to avoid Python's
  recursion limit.

* Separate HTML from data access.

* Factor the coin-days destroyed feature as an optional add-on.

* Use SEQUENCEs where available for synthetic identifiers.

* Slight variation in CoinDD et al. among sites indicates a bug.

* Clean up and document limits on search result size.

* Admin interface to reset blkfile_offset, delete chains, etc.

* Configurable logging.

* Add a tool to upload transactions if bitcoind supports it.

* Perhaps write a validation module to check db data.  Begun as verify.py.

* Abstract SQL into the DataStore class.

* Highlight any objects that are not in the main chain as such.

* Store and report block size, address type, raw objects, etc.

* Report the Merkle branch of a particular transaction to support SPV.

* Test as multithreaded or forking server.

* Perhaps support searching by hash/address non-initial substring.

* /q functions:
  getdifficulty       latesthash          hextarget
  decimaltarget       probability         hashestowin
  nextretarget        estimate
  avgtxsize           avgtxvalue          avgblocksize
  interval            eta                 avgtxnumber
  addressbalance      addressfirstseen    mytransactions
  reorglog

* BTC-specific /q functions:
  bcperblock          changeparams
  totalbc(future block numbers)

* Perhaps create a BlockExplorer.com compatibility mode.

* Perhaps show nethash interval statistics on the chain summary page.

* Perhaps create an "SQL script" DataStore subclass that outputs flat
  SQL INSERTs.

* Perhaps provide a postgresql-bytea binary type.

* Perhaps compress scriptPubKey by representing as a pubkey_id and
  address type.

* Context-sensitive help as on http://blockexplorer.com.

* Simplify the process of adding new chains.

* Present Namecoin name operations as an optional add-on.

* Extract info from MultiCoin config files.

* Support new currencies.

* Import transactions from the pool.

* Perhaps add coin tracking features: allow the administrator to
  specify "interesting" (e.g., suspected fraudulent) transactions and
  addresses, then add a hyperlink from objects linked to them.

* Perhaps track and report coin difficulty as proposed by casascius:
  http://forum.bitcoin.org/index.php?topic=10755.0

* Perhaps track and report collectible transaction bytes: size of
  transactions whose outputs are all spent, minus Merkle shrubbery
  needed to verify the rest.

* Perhaps support email notification about address activity.
