BITC: a new thin/SPV client for linux/mac

[fnsa1]

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.

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

[1714102493]

1714102493

[1714102493]

1714102493

[1714102493]

1714102493

[1714102493]

1714102493

[spndr7]

It. would be help if you compile and provide its windows binary link

[empoweoqwj]

Do you have any plans to compile it  for linux/mac? You would get so many more users that way .....

[fnsa1]

It. would be help if you compile and provide its windows binary link

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

[fnsa1]

Do you have any plans to compile it  for linux/mac? You would get so many more users that way .....

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.

[empoweoqwj]

Do you have any plans to compile it  for linux/mac? You would get so many more users that way .....

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.

Totally understand. Most people, even on this forum, don't know how to compile code / include libraries etc. My guess is 10% max. I know its a "hardcore' wallet but I hope you will consider packaging it for widespread adoption. Peace.

[hivewallet]

Hey, nice work!

[fronti]

Nice Work..

first try to compile on my raspberry PI i got messages like:
 CC    src/base58.c
/tmp/base58-Djd7vs.s: Assembler messages:
/tmp/base58-Djd7vs.s:866: rdhi, rdlo and rm must all be different

I guess this is because of the different architecture

anybody already worked on this?

[fnsa1]

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.

[fnsa1]

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!

[SnowLeopard]

first try to compile on my raspberry PI i got messages like:
 CC    src/base58.c
/tmp/base58-Djd7vs.s: Assembler messages:
/tmp/base58-Djd7vs.s:866: rdhi, rdlo and rm must all be different

I guess this is because of the different architecture

anybody already worked on this?

I have compiled it cleanly on my Pi and as far as I can tell so far, it's running great.
The changes needed are pretty minor and listed in issue #14 on github, but I'm not sure what is the proper way to include the changes without breaking other platforms, so haven't submitted an official pull request.

[fnsa1]

[..]
I have compiled it cleanly on my Pi and as far as I can tell so far, it's running great.
The changes needed are pretty minor and listed in issue #14 on github, but I'm not sure what is the proper way to include the changes without breaking other platforms, so haven't submitted an official pull request.

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

[SnowLeopard]

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

Native on the pi.

Code:

$ clang -v
Debian clang version 3.0-6.2 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: arm-unknown-linux-gnueabihf
Thread model: posix

I read something about changes in the arm processors which is why the CFLAGS with explicit CPU version are needed.