Topic: Bounty for QR Code LTC Payment Processor (Read 3196 times)

How touching is the opinion in the posts about the bounty, Lightcoin and other crypto things seven years ago. Although the general idea does not differ from the present with respect to the development of cryptography. I want to ask participants to support this topic and write some real posts.

This site might prove interesting:

https://www.bitaddress.org/

Being able to generate addresses like this via javascript could be used to allow a user to walk around with a secure but 'temporary' wallet on their digital device.

On that note, a LTC wallet on a Smartphone etc... could have a 'send to vault' feature where the current balance could be sent to your primary LTC wallet (on your computer, etc).

Previously it was mentioned that the wallet could be hosted 'in the cloud' but I think we should consider carefully the security implications of that. Perhaps in default instances the smart-phone based wallet should be kept separate from a users primary wallet. You would fill up your mobile wallet with LTC much like how you fill up your real-world wallet with cash. Keeping the portable device's wallet copy separate from a users main wallet might be a little bit less convenient, but considering how bad the effect negative publicity can have on alt-chains (Someone crying on the forums about how all their LTC has been stolen after someone stole their smart phone) it might be a good idea to idiot proof the software.

Additionally, many smart devices now have remote-wipe abilities. You wouldn't want to have your phone stolen and have to wipe it to protect personal information while simultaneously destroying your LTC wallet. 

Looking forward to see what you come up with. :-)

Like I said earlier, I will try to work on something over Christmas.

For me such total interoperability wasn't necessary, but after reading your post it makes sense. The success of any of the cryptocurrencies is good for all cryptocurrency, and making the transition from bitcoin to Litecoin should be easy to do from a users point of view. It's a good idea the interoperability.

Any takers so far?

Look, why are we wanting to have a QR Code payment processor?
To promote Litecoin as a payment solution, and not only as a store of value / exotic alt currency.

So if we are going to develop an app that allows to read and generate LTC QR codes, let's arrange to have it as widely adopted as possible.
If it reads only Litecoin QR codes, it will cater almost exclusively to existing Litecoin users.
Now if it reads both Litecoin and Bitcoin QR codes, it will show in the search results when people search for a Bitcoin QR code processor, and will be used both by Litecoin and Bitcoin users.

The difference?
In the first case, promotional effect nil.
In the second case, many bitcoin consummers will have a little Litecoin logo on their QR code reader app, and become progressively aware of the existence of Litecoin as a payment solution.
And many bitcoin merchants will have this little Litecoin logo on their QR code generator app, and become progressively aware of the existance of Litecoin bearing potential customers.

Which do you prefer?

That being said, I'd like to precise the requirement for the 1500 BTC bounty as follow :
- The application should be able to both read and generate Bitcoin, Litecoin and Bitcoin+Litecoin QR codes.
- Bitcoin QR codes generated by the application should be readable by existing Bitcoin QR code readers (so exactly same format).
- Bitcoin QR codes generated by other generators should be readable by the application.
- The application should display both a Litecoin and Bitcoin logo in a neutral fashion.
- The application should be able to run on at least one major breed of smartphones (IPhones or Android phones).

crazy_rabbit : can you please update my requirements in post #1?

Yeah, I was just suggesting that:

Seller could display BTC, LTC, or both

Buyer scans.
If it's BTC, app defaults to BTC. LTC, it defaults to LTC. Both, the app would decide, based on balance/address, which to use. Or it could manually ask.

I'm really not sure about having one app manage both, but I'm not a fan of "catch all" apps anyway. Obv. if the bounty is there for it, it's worth looking into.

True, but the price might be different in the future, or one might be more or less stable, or the user might have only one coin and not both. Are you suggesting that the app convert based on the autodetection of the address? Or that it should just be smart enough to know what coin is being used without having to manually select it?

Really, outside of a couple things (what the address is) BTC and LTC are pretty much the same, as far as using them goes. The easiest thing would be to have the payer's app detect if it's an LTC address (starts with L) and act accordingly.

Excellent article and accompanying dicussion:
https://en.bitcoin.it/wiki/URI_Scheme
https://en.bitcoin.it/wiki/Talk:URI_Scheme

Bounty up to 4000LTC! 

That's not so critical to me, but you are probably right on the idea that it's not necessary to proliferate QR codes. Maybe we can see how the bitcoin wallet software produces the QR codes so it can be interoperable with the already existing software for the bitcoiners.

I pledge another 1500 LTC provided that the QR code encoding allows to embed a BTC address, a LTC address or both and that the application allows to pay either with Bitcoin or Litecoin at the choice of the user. That way, a merchant needs to display a single QR code to accept payment in both currencies.
I believe that Litecoin and Bitcoin are truly complementary, and Litecoin owes a lot to Bitcoin (actually, it IS another embodiment of Bitcoin). Litecoin should grow in symbiosis with Bitcoin and support its growth.
Also, the user should not get confused by the proliferation of QR codes.

I want to pledge another 1000 (one thousand) LTC to the bounty. And one more feature which I think would be valuable:

An RPC implementation which would easily run either with a locally stored blockchain (on the phone) or with a remote RPC server, with SSL support. A configuration menu (host, port, rpcuser, rpcpassword) would enable the user to select what they want.

Crazy_rabbit, you might want to update the first post every few days with the total bounty so far, and the list of features. Terry's comments above (open-source and no private keys circulating) and your recent addition (API implementation) are very important to me as well.

My GF and I might work on this over break. If you have any features you'd like to see, post them so we can get a better idea of what this'll entail.

Perhaps to expand on the idea a bit- it would be interesting if someone could bundle the QR <-> LTC client as an API or some sort of stand alone program so that others could build transferring LTC via QR codes into their application.

For example games could allow real world interaction with other people via allowing people to transfer money in-game in-real life by scanning each others QR code.

It goes against the idea of keeping it dead simple, but It's good to throw ideas out there. Anyone else interested in contributing to the bounty? We are at 1500LTC so far.

If I didn't already have an LTC related project I'd jump on this. I have some experience doing just about the same thing on Android, although it would take some work to have it function with LTC. Good to see someone jumping on the ball for this.

I've downloaded the bitcoin wallet app, and it takes less than 30-40 megabytes from what I remember.  I don't understand how it works, but I'm sure that's what the developers are working on. 

So I imagine the developer would be able to make the phone app require very minimal (50 mb?) room rather than a whole gb.

I think those are pretty good terms, I'll stick by those as well. Seems like a good starting point.

I'm adding 500, making the total 1500LTC.

I would like to add that for my part of the bounty to go to the developer, the application must be open-source and at no point may private keys be sent over the air, encrypted or not.