I'm in the Bay Area on business to the central office for my "day job" and was hoping to find some like-minded individuals and have a meetup.

My local area is pretty dry when it comes to public tech meetups and the like, so I like to try to do whatever I can when I travel.

If there's any interest, we can see about ironing out the details.

I also have a GPG key and am working towards CACert assurance (I'm a general security geek), so if anyone is interested, we can have a key signing / assurance event as well or independently. Security, pseudonymity, and identity "can" be put together, so long as you're careful about it and don't mix pseudonymity with identity.

Just now I uncovered the official API (http://blockchain.info/api/blockchain_api) on what is supposed to be returned for the info call for transactions and am working on figuring out how to get my electrum / abe server returning this info... then once that's done I can provide the tools to do the offline transaction management.

... most likely it'll be a Python tool that hooks up to the Litecoin-flavored Electrum APIs and talks to my Litecoin-electrum server.

Thanks

As an aside - you mentioned "Electrum style server" ... I have one I'm working on testing out right now in fact - your little fund will give me a chance to make sure transactions flow from an Electrum server to a slightly hacked electrum client - for which the server would be required for Litecoin support in my Bitcoinstarter - a little busy w/ side projects toward a common goal

Will let you know as soon as I get status on building proper input for the transaction system... in the mean time.. I suppose I can enable it for anybody wanting to play around.

Heh, was poking around the transaction management and had a transaction signed, but litecoind rejected (so will have to check out what's going on there)

Sure, here's the site for all to try http://www.eharning.us/brainwallet-ltc

Currently the "Transaction" tab is removed since the behavior is quite hosed. Will be poking around litecoind commands to see about generating proper transaction data to sign. Looks like listunspent might be the right RPC / litecoind command... though it looks to only work w/ addresses w/ full private key... Will let you know of updates.

Got the blockchain.info usage fixed.. but transaction building is a no-go due to no existing web services for Litecoin getting transaction details... on the other hand, transaction signing w/ pre-created data will work just perfectly.

Funny discovery w/ this - nobody has paid into the "correct horse battery staple" wallets for Litecoin

Let me know if this bounty is still present.

I have put together a slightly modified version of bitcoinjs-lib (had to figure out how to compile the many many scripts together) to allow a default address-type to be configured... then I had to apply minor tweaks to brainwallet.org's code to use the new locations of things in bitcoinjs-lib + fix the default public address filled in the signing page.

NOTE: The transaction construction currently does not work due to it interacting w/ blockchain.info ... and clicking on addresses right now in the signature verification window points you to blockchain.info ... with a litecoin address... with no indication from them that all is wrong.

I'll take it on. Taking brainwallet and making it do Litecoin addresses. Should be done, at worst, by Monday night. Anticipate tonight

Thanks Fun hacking Electrum src code.
Confirming receipt for benefit of others.

Awesome - decided to hack it out to test.

I added a new button "Import transaction CSV" underneath the "Import raw transaction". Hooked it up to a function that:

 * Opened up CSV file dialog
 * Open file, reading CSV taking 1st column as address, 2nd column as BTC value - converting to satoshi as mktx outputs array needs
 * Save off wallet seed to variable to prevent unwanted signing
 * Called wallet mktx to generate unsigned transaction object
 * Restored wallet seed
 * Prompted create_process_transaction_window which allowed raw viewing of the transaction to be sent and signing it

... odd thing I noticed, though... the coin outputs for spending were there, but no associated address, in fact is showed None .. (guessing something lost in translation w/ raw transaction processing)

For CSV, would you want to ignore 1st row since it is typically a header w/ descriptions or treat it raw?

I can fork and submit a pull request if needed.

Happy to accept coins (for this - 16Ad3kT79J4bUtpKACKTBbwDwJgykwGf5h - either directly to me or the Bitcoinstarter project I have... on whatever conditions you like. Can fork tomorrow and push if you like.

What sort of behavior would you like?

CSV w/ 1st column of addresses and 2nd column of amounts?

UI:

 Import Transaction Queue
  -> Open File Open Dialog for CSV
  -> Upon 'Open' show confirmation with total amount to send
  -> On confirm, send

Good?

Norton classifies many many Bitcoin things as malicious... now heaven forbid a Bitcoin CLIENT infect a user.

Miners... I can understand... but clients... that's just bad.

I'll give this a try

From Fort Wayne here.

Wish I saw this message before (I decided to start investing time in Bitcoin in April, just right before the boom).

ABANDONED

Biased input here, but, my Electrum for Android - Native Edition wallet will offer support for multiple wallets. To support what you want, I could implement a wallet-flavor where it is temporary / in memory only and can store the configuration that all change must go to the source address.

Example flow:

 * Tap wallet drop-down
 * Select temporary wallet (would need to come up w/ naming)
 * Wallet gets selected
 * Select option to scan key
 * Hold phone/device over paper key
 * Gets added
 * Electrum servers lookup transactions associated w/ the address and populate temporary wallet data
 * Use option to send coin, select address you want to send to either by scanning using camera, address-book, or manual entry (where you could paste if off web page)... input amount.. send

Then you can watch for the transaction to complete or immediately clear the temporary wallet.

.. another option for use-case could be to have that address as a watch-only address, then when you need to send from it, it would ask you to provide the private key source (ex: paper wallet)

Let me know if this sounds sane to you...

Will need to eventually document all the support flows / use-cases so that I know what kind of UI to design and develop...

Any change of a withdrawal / deposit API being released?

Don't expect it for government-issued currency, since that's a tricky issue... but virtual currency seems natural to convert automatically.

One request I've seen is a Bitcoin / Litecoin client that can "automatically" convert between the two. The only way I can think of this reasonably done w/o taking risk and being a hold of large amounts of Bitcoin / Litecoin to self-manage the conversion is to take an exchange and use it to perform market purchases.

Ex:
User wants to convert BTC -> LTC w/ market rate
Client looks up rates and calculates estimated LTC for a given BTC amount

Client requests a deposit address from backend
Client sends amount to backend
Client waits for backend to accept payment (another API call)

Client performs trade using standard API

Client requests a withdrawal to a given address

Boom, instant transfer.

Note: You could make this userless by doing the following API...

Client sends:
 * limit rate or simply allows market value
 * currency X type
 * currency Y type
 * amount of currency X
 * target address for currency Y

Server sends:
 * address of currency type X
 * estimated return value in currency Y given the estimated amount of currency X
 * expected fee to be taken out (either this could have already been applied to expected return value, or defined as a value to subtract to determine your real estimated return value)
 * ID of some sort for future tracking APIs


Server does not have to expect the exact amount going in, it can take all that is going in to the address in a reasonably close period of time (ex: within 2 blocks starting time)... then it performs a purchase of currency Y using parameters passed in... then sends Y back to the user

BTC-e could stand to gain a bundle from this w/o having to deal with users... just an API needs to be designed and appropriate automation fees applied (though... last I saw... standard LTC withdrawal fee was quite huge relative to the USD value... newer clients, IIRR use a lower value)

105

Answered the question on IRC, but for posterity and anybody else who has the question: check out the scripts directory in the Electrum source code and you'll see a merchant.py script that you can model off of to perform what you may want to do. Electrum's scripting in python makes for relatively easy custom integration scripts.

Doing further investigation in the BTC/LTC trading via BTC-e yields the problem that they have no withdrawal / deposit API. I'll raise this with them.

ABANDONED