Termcoin – A Bitcoin wallet for your terminal(github.com)
github.com
Termcoin – A Bitcoin wallet for your terminal
https://github.com/chjj/termcoin
19 comments
It's a bit tough to deal with this since javascript doesn't offer any real way to zero a string's memory. The way to do this would be to read from stdin directly into a Buffer object (which is malloc'd separately from the v8 allocator) and to buff.fill(0)/memset(buff, 0) once we're done. I'll definitely work on implementing this. Thanks for pointing this out.
Assuming you trust your hosting company (maybe that's another discussion?) I don't think it's possible to leak memory contents VPS-to-VPS but I could be wrong.
In any case, if I had a pile of Bitcoin (unfortunately I do not) I wouldn't put it all in one wallet on one server. From what I've heard, paper wallets are the safest.
That said, maybe "zero out" your wallet before switching VPS providers, changing plans, etc.
This is from 2012 but probably still relevant as we saw with the recent Digital Ocean outrage. http://www.contextis.com/research/blog/dirty-disks-raise-new...
"It is worth noting that the data was not live, in that it was not due to sharing of disk contents between running instances of virtual servers. It is understood that the data is due to disk and swap data not being zeroed after use."
In any case, if I had a pile of Bitcoin (unfortunately I do not) I wouldn't put it all in one wallet on one server. From what I've heard, paper wallets are the safest.
That said, maybe "zero out" your wallet before switching VPS providers, changing plans, etc.
This is from 2012 but probably still relevant as we saw with the recent Digital Ocean outrage. http://www.contextis.com/research/blog/dirty-disks-raise-new...
"It is worth noting that the data was not live, in that it was not due to sharing of disk contents between running instances of virtual servers. It is understood that the data is due to disk and swap data not being zeroed after use."
The underlying terminal parser is friggin' hawt: https://github.com/chjj/blessed
that really is sexy...quite possibly the best UI I have ever seen. brooding dark background and no nonsense colors.
Heck yes, I've been looking for something exactly like this. I hate the Qt client, and the others I've played with aren't much better, but this is perfect :)
EDIT: Dumb question, running Mint 16 here, installed the nodejs package through apt, but termcoin looks for "node", not "nodejs". I copied the symlink as "node" and am just installing the npm modules now, but whats up with that?
EDIT: Dumb question, running Mint 16 here, installed the nodejs package through apt, but termcoin looks for "node", not "nodejs". I copied the symlink as "node" and am just installing the npm modules now, but whats up with that?
the commandline binary for nodejs is just 'node'
It looks amazing, and I do dislike the current bitcoin-qt that most of us use.
However, I'll be damned if I install it on my machine for at least a year or two after it's been released and fully verified by everybody in the community who matters.
However, I'll be damned if I install it on my machine for at least a year or two after it's been released and fully verified by everybody in the community who matters.
If you're worried about the security then just verify it yourself, don't wait for others to do it for you. It's not like the source isn't available for auditing.
We're not all skilled pen testers.
I do not possess the time to do that, unfortunately.
The only way that I can be sure that it's not going to steal from me is if it has been around for a few years, used extensively, and nobody has cried fowl.
That, or if they paid for a public auditing by respectable cryptographers.
The only way that I can be sure that it's not going to steal from me is if it has been around for a few years, used extensively, and nobody has cried fowl.
That, or if they paid for a public auditing by respectable cryptographers.
Interesting, I've also developed a bitcoin client :) However, mine is completely independent of bitcoin-qt and is meant to be lightweight and snappy. It uses SPV. Here's a screenshot:
https://i.imgur.com/pRLs1ps
Let me know if anyone is interested in taking a look.
From my README file:
bitc is a thin SPV bitcoin client.
https://i.imgur.com/pRLs1ps
Let me know if anyone is interested in taking a look.
From my README file:
bitc is a thin SPV bitcoin client.
- 100% C code,
- support for linux and mac platforms,
- console based: uses ncurses,
- home grown async network i/o stack,
- home grown poll loop,
- home grown bitcoin engine,
- multi-threaded,
- valgrind clean.
If you have some kind of email list, please add me "pj at pjbrunet.com"
Finally something to replace the awful bitcoin-qt. Get the best of both worlds with a "gui" that is in the terminal.
Notably, there is as an alternative to this node terminal btc client.
It's actively used in ecommerce [2], and we've even heard on #electrum freenode of at least one Bitcoin exchange using it on the backend.
Electrum uses a deterministic mnemonic address generation system (soon to be BIP0032 compatible) and the Stratum protocol, which involves running a gateway daemon [3] and bitcoind on the backend, to tackle the large size of the blockchain and rather unwieldy individualized address generation scheme in use by Bitcoin-QT.
[1] https://gist.github.com/atweiden/7272732
[2] http://acceptbit.com/
[2] https://wordpress.org/plugins/bitcoin-payments-for-woocommer...
[3] https://github.com/spesmilo/electrum-server
electrum -g [text | stdio]
It's actively used in ecommerce [2], and we've even heard on #electrum freenode of at least one Bitcoin exchange using it on the backend.
Electrum uses a deterministic mnemonic address generation system (soon to be BIP0032 compatible) and the Stratum protocol, which involves running a gateway daemon [3] and bitcoind on the backend, to tackle the large size of the blockchain and rather unwieldy individualized address generation scheme in use by Bitcoin-QT.
[1] https://gist.github.com/atweiden/7272732
[2] http://acceptbit.com/
[2] https://wordpress.org/plugins/bitcoin-payments-for-woocommer...
[3] https://github.com/spesmilo/electrum-server
Security sensitive software written in js huh?
I've been ready to ditch bitcoin-qt . . . this is fantastic.
After seeing the screenshot (https://raw.github.com/chjj/blessed/master/img/screenshot.pn...) I'll be switching to "Welcome to my program" from now on instead of "Hello world!" which is getting really tired. I don't know why I never thought of it. Facepalm.
I see e-ink readers, such as the Kindle, being used as a POS system for merchants. Linux installed with this running.
It's awesome because it's super lightweight and can be installed on virtually any device without even having to run an X ui server.
That also means that you don't have to install anything but this bitcoin client on the system, which dramatically lowers the possibility for attacks.
It's awesome because it's super lightweight and can be installed on virtually any device without even having to run an X ui server.
That also means that you don't have to install anything but this bitcoin client on the system, which dramatically lowers the possibility for attacks.
Wish this was elaborated: "Ideally I wanted this to have all the capabilities of a full wallet, but that would require, for example, linking to to berkeley db to parse the wallet.dat. I wanted to write this entirely in node."
So it still makes a wallet.dat file but different wallet encryption? I'm a little confused.
So it still makes a wallet.dat file but different wallet encryption? I'm a little confused.
termcoin uses the bitcoind json-rpc api[1] for (nearly) everything (which means the same wallet.dat file, the same encryption (aes256-cbc), etc.). What I mean to say is, the bitcoind api is a bit limited with regards to how it can manage a wallet.
For example, there is no way to retrieve the "send" addresses from the wallet via the api. The only way to do this is by using bdb to open the file and reading it as a berkeley database. Send address retrieval is the only thing termcoin does not use bitcoind for: termcoin has a "dumb" parser built-in which reads the wallet.dat and searches it for bitcoin addresses, when it finds them, it checks to see that they're valid and also checks them against "receive" addresses.
The bitcoind api is also incapable of re-labeling or deleting addresses (bitcoin-qt itself cannot delete "receive" addresses). A lot of people end up using a tool like pywallet (which links to bdb) to get around this. These are the only two limitations in termcoin's functionality that keep it from being a fully-fledged wallet.
[1] https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls...
For example, there is no way to retrieve the "send" addresses from the wallet via the api. The only way to do this is by using bdb to open the file and reading it as a berkeley database. Send address retrieval is the only thing termcoin does not use bitcoind for: termcoin has a "dumb" parser built-in which reads the wallet.dat and searches it for bitcoin addresses, when it finds them, it checks to see that they're valid and also checks them against "receive" addresses.
The bitcoind api is also incapable of re-labeling or deleting addresses (bitcoin-qt itself cannot delete "receive" addresses). A lot of people end up using a tool like pywallet (which links to bdb) to get around this. These are the only two limitations in termcoin's functionality that keep it from being a fully-fledged wallet.
[1] https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls...
Great job, this looks really neat.
This is better than having to read the docs every time I want to send a few coins...
Please report if you lose any coins ;)
Javascript was a bad design decision.
Looks cool.
Finally.
esneyder(1)
For instance, you're getting the user's wallet passphrase at line 1361. Does the passphrase just sit around in memory somewhere, long after the wallet encryption has been kicked off?
https://github.com/chjj/termcoin/blob/master/bin/termcoin#L1...