Thanks, glad you're finding it useful! Regarding extensions, we've it pretty easy to add stuff to the source and rebuild so you can customize that to your needs and then share the changes so we can work that back into the main version if it makes sense.

We're also working on a new version to come out soon that merges some community driven features such as paper wallet support and printing.

I'm not sure I understand your question. RFC = Request For Comments. I originally opened this thread to get feedback from the community on BitKey and how to improve it.

It's good for that too, but I own a Trezor and still prefer to use BitKey in ultra paranoid mode for my highest risk transactions:

https://www.turnkeylinux.org/blog/secure-bitcoin-transactions

A new version of BitKey is out - 14.1

BitKey is a self-contained Live CD/USB key with everything you need to perform highly secure air-gapped Bitcoin transactions. Offline cold storage made (slightly more) practical.

https://bitkey.io/

Changes:

* Refreshed component versions and base OS to Debian Jessie, thanks to
   Yannick Heneault.
* Fixed Electrum issues.
* Manually verified & signed integrity of upstream components
* New Bitcoin apps: warpwallet, coinbin & libbitcoin-explorer (bx)
* New packages: secure-delete, dosfstools (mkfs.vfat)
* Added background color labels to boot modes
* Desktop UX: cut and paste, improved keybindings

I tried that out yesterday. I didn't really see an option to print out my private key (QR-Codes) or scan them and just create the  transaction to execute it in another online OS, which is my whole point of using an offline OS.
I also think, the Electrum Wallet way of generating adresses is way to complicated. I just want to generate a bunch of adresses to print out.
[/quote]

We released a new version and updated the documentation with step by step instructions for doing offline airgapped transactions, which is what we're using BitKey for ourselves. We've also included a few additional tools other than Electrum such as WarpWallet and coinbin.

Printer support is tricky to get right on a non-persistent OS (e.g., automatic configuration), so we haven't gotten to that yet. Not a feature we use personally. Also, sending to a printer is potentially quite dangerous. It's not always easy to tell what your printer is storing, where.

FWIW, we released a new version of BitKey today. Changes: fixes Electrum issues, added warpwallet, coinbin & libbitcoin-explorer.

It's not necessarily a good idea to aggressively update software you intend to use to maintain an offline wallet. For that kind of use case, what you want is extreme conservatism. More of a "if it works don't fix it" mentality than a "latest and greatest".

FWIW, we just released a new version of BitKey and made some improvements to the documentation. It's a fun side-project for TurnKey GNU/Linux, something we developed & use for our personal needs. Hope people find it useful.

We just released a new version of BitKey. I fixed the download link. The 64-bit (AMD64) image will not work on a 32 bit only machine.

Not really but try to use common sense. I had to block this one IP today from Sweden that pounding on the site harder than everyone else put together (over 50% of requests). No user agent. I put up with it for a week or so but he just kept it up. Relentless. If you're doing hundreds of requests a second on an ongoing basis, better to run your own copy of Insight.

I can't reproduce this so that probably means I am misunderstanding you. Could you give me a specific example of what you are seeing for a given address vs what you expected to see?

User:Liraz

Not an evil robot as far as I know.

Brain miswired. Thanks for catching that. I edited the post.

If that happens, you can contact me personally:http://liraz.org/?ContactLiraz

FWIW, I'll probably already be on top of it as I've implemented robust Nagios monitoring that triggers SMS notifications to my phone when anything goes wrong. If the site goes down for 5 minutes or the blockchain stops updating for more than 2 hours my phone will be lighting up.

Also, I've put in quite a bit of effort to make sure the next downtime we have will be due to hardware failure rather than a software or operating system issue. All the site's key services are monitored by systemd and set to restart automatically if they leak too much memory or go down.

Thanks! People did inquire politely what was up, and whether I had lost interest in maintaining the site. Thankfully there are other options so worst case scenario you just use something else. Which is exactly the way it should be. Decentralization FTW.

Still, I admit it is a big relief to have the site back up and finally in good health.

I thought this was a bug with the old code and assumed blockchain.info was in the right but strangely enough after migrating blockexplorer.com to Insight there is still a difference in the balance.

I can't speak for what blockchain.info is doing, but since the site is open source you can take a look yourself and figure out where the difference is coming from. This time I'm betting blockexplorer.com is right.

At the time of the survey Blockexplorer.com was busy choking on spam attacks on the blockchain so  I wouldn't have included it in any respectable list of block explorers either. The old code had far outlived it's usefulness.

FWIW, all of the problems with the old site are now resolved. I finished migrating the site to Insight last week:

https://bitcointalk.org/index.php?topic=1167528.new#new

It was a long time coming but better late than never I guess.

Insight is the best standalone Bitcoin blockexplorer out there but there are a few things you should be aware of.

Some of the things I learned while migrating blockexplorer.com to Insight:

- You'll need to turn on txindex in bitcoind and reindex the blockchain database. With txindex turned on the blockchain will weigh in at around 70GB. You can't turn on pruning to save space.

- Insight filesync doesn't work with bitcoind versions 0.10 and beyond so if you're running the latest version of bitcoind you'll have to use the slower RPC sync.

- You can only sync Insight with bitcoind after bitcoind blockchain has been reindexed with txindex and fully caught up with the blockchain.

- After syncing the Insight LevelDB database will weigh in about 15% more than the bitcoind database. Currently that's about 80GB.

- Insight's testnet breaks with any reorg deeper than 6 blocks, which does occasionally happen on testnet. The only way I've found around this so far is to delete the testnet database and resync.

- If bitcoind goes down for any reason Insight does not re-establish a connection with it after it comes back up. You'll need to do that by hand.

FWIW, I'm planning on open sourcing the blockexplorer.com server configuration to make it a bit easier to roll your own.

Sorry for the late response. If nobody was using the site the last 2 couple of weeks would have been less stressful. I could have just shut the site down and sent blockexplorer to a quiet peaceful death, instead of migrating to Insight:

https://bitcointalk.org/index.php?topic=1167528.new#new

Anyhow, the Internet is a big place and old sites die hard. Especially when they have an API and hundreds of thousands of links. According to CloudFlare BlockExplorer.com received 871 million hits in the last month and is scheduled to receive 2 billion hits next month:

The old PHP code is retired, Blockexplorer.com is now powered by a lightly modified version of BitPay Insight:

https://bitcointalk.org/index.php?topic=1167528.new#new