Excellent, thanks for the report. Btw, were you compiling natively on the pi or were you using a crosscompiler? Thanks!

bitc now supports connecting to Tor via Socks5. You just need to add
   network.useSocks5="TRUE"
.. in your ~/.bitc/main.cfg. It will automatically use localhost:9050 on linux or localhost:9150 on a mac.

If the proxy is not local or on a different port, you'll need to tweak the config options:
  socks5.hostname="localhost"
  socks5.port="9050"
.. in your ~/.bitc/main.cfg.

Note that the geoip requests now go over https, and also go over the socks5 proxy.

Finally, I would appreciate if someone could give me access to a raspberry pi or any other exotic device. I do have informal reports that it works quite well on Pis if only for something fishy with the way getopt_long works, so I'd like to fix this. Thanks!

Thanks for trying to compile it on this platform.

It sounds like your toolchain is not properly setup. I'd love to make this code compile properly on raspberry pis, as they're a good fit there. Please PM me and I can try to fix this up. In the mean time and if you have gcc installed, you can try editing the file 'Makefile' and change the first instance of 'clang' with 'gcc', then comment out lines #12 and #13. Cheers.

I guess that eventually, yes. But I've never done that, so there's going to be a learning curve.
For now, checking the code out and building as described in the README.md should be doable for most people.

He, it might be possible to build a cygwin port, but it's not on my agenda. A patch is welcome though.

Thanks for the kind feedback, Jonas.

Yeah, I'm aware of picocoin, and like I mentioned to Jeff privately I was initially interested in learning how the underlying protocol worked, so I developed my own stack from scratch (almost actually, I already had a few building blocks available). Cheers.

-M

I announced it on the dev forum an hour ago, but I guess that most interested parties hang out around here:
 
https://github.com/bit-c/bitc
https://bitcointalk.org/index.php?topic=436899.0

Note that this uses an entirely new bitcoin stack, it's multi-threaded and all i/o's are issued asynchronously. It supports encrypted wallets.

http://i.imgur.com/IJJU14s.png

Folks,

I announced the creation of bitc recently:
    https://bitcointalk.org/index.php?topic=428765.msg4686381

The code is now on github:
    https://github.com/bit-c/bitc

From the README.md:

bitc is a thin SPV bitcoin client.

• 100% lean 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,
• supports encrypted wallets,
• multi-threaded,
• valgrind/AddressSanitizer clean.

Please let me know if you have any questions. Cheers.

-M

---

That would be me -- he, I'm not quite done and I prefer not to quantify the time I spent on this I tried to not cut too many corners for the most part and I wasted time (i.e. had fun) re-implementing a poll loop, an async network i/o stack and various generic libraries. But assuming you re-use existing building blocks, have copious spare time and are proficient in C#, you could get there in a few weeks.

You'll soon be able to look at/re-use bitc code.  In any case, feel free to ping me if you have any question.  Cheers.

Thanks for the interest. It should be out sometime in the next 2 weeks if all goes well.

-M

That's a great suggestion. I'll think about it.

-M

The code is ready, I for some reasons am not. Send me a PM and I'll ping you once I'm there. Cheers.

Ah, that's what I figured. If they get their act together and decide to implement some form of SPV support server-side, the client side shouldn't be that much work (but like I said, I don't know much about altcoins, so I may well be missing a big chunk of work).

-M

I see. Note that if I ever do something for this platform (very unlikely at this point), it's likely to be a full blown UI for the newer Windows flavors. Your best bet might well be to use a linux VM =)

By 'coin control', you mean the ability to select the coins used when initiating a tx? If so, having a generic UI for this is going to be kind of tough, but implementing policies (randomize, oldest first, etc.) is doable. Being able to broadcast a raw transaction is an hour of my time; setting an arbitrary fee is one line change.

Windows? Most of the low-level APIs have already been abstracted away, but the biggy will be the UI/ncurses. Maybe cygwin has a port for it? Not sure, I would have to investigate.

-M

Thanks for the feedback. Interesting. I don't know much about altcoins, but if they support SPV clients it shouldn't be much work to build say the litecoin peer of this app. Now having a single client be able to support several flavors of digital coins would be quite a bit more work.

-M

Folks,

I've been working on & off on a lightweight bitcoin client. It's all command line for now and it supports linux & mac platforms. It doesn't re-use any existing bitcoin library, my original intention was to write a dummy client to better understand the underlying protocol, so I wrote my own.

From the README:

bitc is a thin SPV bitcoin client.

• 100% lean 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,
• supports encrypted wallets,
• multi-threaded,
• valgrind/AddressSanitizer clean.

There is still a fairly lengthy TODO list but the client is somewhat complete at this point and certainly usable, so I plan to put it on github sometime in the next few weeks.
Before I do so I was wondering: what would you like to see in an SPV bitcoin client for well.. geeks?
Cheers.

-M

---

Thanks for adding the possibility to hide the MACD, having as little clutter as possible is essential in technical analysis (but then what everyone finds useful varies greatly).

Now it's unfortunate that we can't increase the density, there just aren't enough bars per charts... any move in that direction will be welcome.

Cheers.

Thanks, I like the UI.

2 big sticking points though
 - the only indicator useful to me is the volume. I don't need SMAs/EMAs/MACD/RSI, etc. I didn't find any way to hit this pane. Is there?
 - is there any way to print more bars per chart? I want to say 4 days worth of charts using 15min bars and I can't seem to do that.

Cheers.