Topic: coinsplit: generate, split, rejoin and import bitcoin addresses and keys offline (Read 2207 times)

Thanks very much for creating this program! I've been needing something very much like this, and was even considering writing something myself, although that would require a lot of research on my part since I haven't done any public/private key encryption programming before. That, and I'm not too great a programmer to begin with.

I was able to compile coinsplit on a Mac OS X 10.5 machine with GCC 4.2 (4.0 didn't work). I had to download and build the latest versions of GMP, Berkeley DB, and OpenSSL, which went mostly fine. OpenSSL needed some special love to build and work correctly on the Mac, but I was able to follow a simple guide and got it to work.

Unfortunately, the open_memstream() and fmemopen() functions aren't natively available on Macs, so I had to do some digging and was able to locate implementations of each using the available funopen() function. The app compiled fine and runs on both 10.5 and 10.6, however I couldn't create a working binary under 10.6; the resulting program segfaults when trying to generate an address. I tracked the fault to the base58_encode() function and its references to result_stream.

Just as a note, I noticed that the bitcoin source code includes its own base58 and bignum header files. Might these be easier and/or more portable to use? I realize they're C++ (not C).

Anyway, I have a few requests for the next version of coinsplit:

• Easier build process / compatibility on Macs (see above)
• Ability to specify bitcoin vs testnet address as a command line option
• And most importantly: output of base58 encoded private key

If you're able to make these changes, I'd be happy to send you a donation in either BTC or USD.

Take care, and thanks again.

Well, I wrote it so someone could possibly do a semi-distributed exchange, with an escrow address along the lines of ClearCoin, but without storing any keys on the server.

I kind of imagine it going like this:

1. Seller lists a price on the exchange.
2. Buyer places an order.
3. Exchange gives each person the address and half of the key (deleting the original key and keeping only the buyer's half.)
4. Seller sends the BTC to the address.
5. Buyer sends the money to the seller using whatever the seller accepts.
6. Seller sends the other half of the key to the buyer.

If the money isn't claimed in like six months, then the seller gets it back.

I personally don't want to write an entire exchange, but I like the idea of having an exchange that keeps no funds and no keys for itself. It's not the completely distributed exchange that we all fantasize about, but it's better than what we have now.

So, the main purpose of this is for security for a savings wallet?

- Create an offline address/key.
- Split key into several parts.  Store each part in a different location.
- Send BTC to address.
- If need to access account, bring all key parts together and join them to the wallet file.

Definitely. It only works on the test net right now anyway, so please don't use it with a real wallet file.

From the help menu, this looks exactly like what I've been looking for. Maybe there's a better name, such as coinmanager - it looks like it splits AND merges (and generates). I'm reading coinsplit.c now. I've gotten paranoid in my old coin age!

This is a simple commandline tool for playing with addresses and keys and wallets. I've been working on it for fun, just using ideas seen in other tools.

http://github.com/cecilw/coinsplit

This isn't for split-device generation of keys, as is discussed elsewhere in this forum, but simply a way of doing it with a one-time pad for now. I tried to keep it UNIXy, so you can append lists of keys together and pipe back and forth between the wallet and key backups.

Here's "coinsplit --help", just to give an idea.


This is probably worthless and overlaps other tools, but I had fun making it. Take care.