I just got the message processor complete and we have had our first fully automated StealthText transaction, which is a big step.
1c6f16b92097d3beb4a5b64ff14eb83470f69367e95808952bf280599a5e55ac
Now that I have that done, I'm going to work on instructions and simplifying the process, and I'll also work on finishing the whitepaper, which is still in "rough draft" form.
A number of people have been curious about why StealthText uses email to transmit the encrypted transaction to the wallet. This necessity boils down to the fact that two fundamentally different communication protocols are involved.
On one end (the phone), you have SMS, and on the other end (the wallet) you have TCP/IP. Somehow you need a service that intercepts the SMS and turns it into TCP/IP. One such service (of many) is google voice. If you have a google voice account, your SMS messages can be turned into TCP/IP messages, which take the form of email. I boldface and underline "One" because there are plenty of other ways to skin this particular cat. I chose google voice and email because it is free and convenient. In other words, email is chosen for its convenience and not out of necessity.
However, email is an excellent way to encapsulate information. It is a perfect metaphor for regular mail. In regular mail, you have a message on a piece of paper. You put the message in an envelope and put it in a mail box to be carried away by the postman. The nature of the message (and even the medium on which the message is printed) does not change in this process.
The same is true for email. The encrypted transaction gets packaged into a message with To: and From: headers and other information. However, the encrypted transaction does not change during this process. The email is then sent through TCP/IP, where it is routed to its recipient.
This email message, with the unchanged encrypted transaction, comes over a protocol called IMAP. IMAP is not understood by the wallet (it's a protocol for mail not cryptocurrencies!), so the transaction (unchanged) needs to be unpackaged from it's email envelop and repackaged into RPC (remote procedure call), which is understood by the wallet. And, just like when you unpackage and repackage physical objects, they don't change during the process. They are simply moved from one package to another.
That's the function of the simple message processor I wrote over the last couple of nights. As you can imagine, this conversion from mail format to wallet format is not common, so I had to write the message processor specifically for this task.
-- Hondo
Read the posts of Hondo's hard work bitches and judge by your self if he is the main programmer and the lead dev.
Hondo and other dev parting ways! 
