Well, locking helped the non-SSL code. I can no longer crash it. Not sure I care enough to figure out the SSL problem.

What if the connection threads grabbed a lock, and the "real" multithreading only occurs when the RPC function itself releases that lock?

Well, care to help? I basically "need" this functionality to setup my pool how I want it-- a 'getwork' request depends on being able to make sub-RPC calls.

Here's a new version, that mostly works fine without -DUSE_SSL... Though I can still crash it if I keep a constant load of 100+ RPC calls at once, it's probably "stable enough" for my pool to just restart it when it dies.

http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/commitdiff/0071352b3347f92faa266dfd1db18aea88b45c54

I wrote a patch to give JSON-RPC connections their own threads. However, it still has some issues that I can't seem to figure out. If anyone can advise on how to fix it, this would be a nice feature.

• Occasional crashes (SIGABRT)
• Segfault if -DUSE_SSL
• Timed out connections aren't closed

http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/commitdiff/355e162fba35810978742f6f1e6f2e413cdc78e9

It doesn't eliminate divisibility problems. Obviously the solution is a varint fraction. First, you have the numerator, made up of a variable number of 7-bit sequences (using the high-bit for "more bits to follow"). Then, the same encoding for the denominator. That way you can have exactly 1⁄7 of a bitcoin...

I would hope so. The only C-level runtime dependencies are Python and PySide. PySide has a supported ARM port.
No. It is a GUI, not a Wallet.
I would recommend running a 24/7 bitcoind at home (or perhaps use xf2.org's hosting service) and run Spesmilo on your Pandora to control it remotely.
Why not?

Or just connect to the free transaction relay network which will relay "weird" (really taboo) transactions between connected nodes.

No, it isn't. It's bitcoin:somestupidlyunreadableaddress?amount=50 if you want decimal, or the same, but x50 if you want hexadecimal. You can do WHICHEVER YOU WANT.

(Also, it would be fairly silly to type a URN into a browser)

Oh great. That means lots of someones were idiots and reported bitcoind as malware to Norton. Either that or Norton is stupid and treated some other reports as a problem with the NSIS installer framework itself... sigh

GPLv3... read the COPYING file (included in source and on Start Menu for Windows)...

I disagree.
You would export your keys from the old Wallet software (using the Wallet protocol), and then import them to the new Wallet software (again, using the Wallet protocol).
A standard for communicating keys is needed for various purposes, including export/import, anyway. This can work just fine for the example you gave. Requiring a standard storage format can prove to prevent innovation in key storage.

No, because keys can be reused.

Access to keys is inherently insecure.

Of course. Any Bitcoin-enabled ATM is going to need a standard protocol and drivers implementing it. While some people might be crazy enough to allow random ATMs unrestricted access to their keys, that isn't something that should be enabled.

Your USB device would itself be running the software for your Bitcoin wallet. Anything else would be a security hazard.

You can (optionally) connect it to a remote (or local) 24/7 bitcoind. That's probably the biggest feature right now. Unless you prefer the Tonal number system, or one of the languages it supports.

Would appreciate beta-testing of Spesmilo, the next generation Bitcoin client that welcomes diversity. Additional translations and patches welcome! Live support available on FreeNode #bitcoin-dev.

• Windows installer -- Requires Administrator to install or you will get an error
• Source code
• Gitorious project (including git repository)

Gentoo install:

• layman -o https://gitorious.org/bitcoin/gentoo/blobs/raw/master/overlay.xml -f -a bitcoin
• emerge -a spesmilo #(you may need to keyword some packages)

Quick start (from source):

• # Dependencies: PySide, ImageMagick
  
• make local
• make
• ./spesmilo

To install:

• make install

To install with bitcoin: URI support for KDE:

• make install KDESERVICEDIR="/usr/share/kde4/services"

Not really, that assumes we know all possible units in advance, as it can't easily be added onto later. It also means software would need to hard-code every possible unit.

You don't need to understand the URI. Only software does that. The point is for humans to be able to write URIs-- however they feel is convenient. Also, it's not "wrong", nor is it a negative exponent. All real bitcoin amounts are integers.

Not that thread, see https://www.bitcoin.org/smf/index.php?topic=5171.msg89908#msg89908