it is in there already.
i just see that the forum software resizing the code makes it less readable. generally works, but not perfect. will change this soon.

the generator output images scan fine though.

I have no idea how much information you can include in a 3D codebar, but, if possible, it would be interesting to being able to include the address and a quantity in the 3D bar, so with one scan you can get the address and the amount of bitcoins, so you just have to confirm the transfer in the screen (f.e.).

we have at least two competing uri schemes. the generator supports both.

but you are right, i will add a "send amount" feature.

@hugo: they are 2d barcodes, not 3d. you can store A LOT in there. QR supports up to 4,296 characters. The codes become bigger, though.

Nice!

It would also be cool if we could add a short description text to it, where the merchant could identify himself and maybe describe the transaction. This could be useful for controlling how you spend your coins.

so the amount-bit is live. enter the amount you want to be sent to the adress and it is encoded to qr.

also the codes can now be used as your forum profile picture without resizing, that is IF you adhere to either RAW or bitcoin:URI. Unfortunately codes in xbtc get larger than the 80x80 size the forum supports. And resizing is a really bad idea, as it hurts readability.

description (as per the two specifications) is next on my agenda.

@hugo: the whole idea of this URI scheme is that this is possible. but that is up to the reader software. this is doing the text->qr part, the reader software needs to do qr->text. and sorry to correct you again, but it is not bitcoin://xxxxxxxxxxxxxxxx. It is bitcoin:xxxxxxxxxxxxxxxxxxx as this is a URI, not a hierarchical URL.

@slush: yes, i am basing my work on this. but as had been said there, we can discuss all month, somebody needs to implement it.

for your reference, the x-btc specification is here: http://pastebin.com/VsBbmXQx

lets say it that way, as we are the only two people at the moment USING the URI-scheme in publicly available software (as far as i know) we can de facto determine which standard is used. if that is a good idea remains to be seen.

personally, i'd really like another shot. and better do it now, then after widespread adoption. right?

edit: Post moved to https://en.bitcoin.it/wiki/Bitcoin-scheme

I love the error correction parts which enables you to put a bitcoin in the middle. xD

Actions are optional in x-btc, and you can use public key hashes instead of addresses in the current version. Addresses can be losslessly converted to and from public key hashes.

x-btc:addr=17Dk1cugCynTaNdmQihF7tproJgyKyWiwr;store
becomes
x-btc:hash=RDmmVdBt99QUY87vTlxY4K4aX1c;
which is even smaller than
bitcoin:17Dk1cugCynTaNdmQihF7tproJgyKyWiwr


This sort of size issue is exactly the reason why a short name was chosen. QR codes also have a relatively small maximum size.

Ehhh, you shouldn't hotlink the qrcode you get. Current script wipes the generated codes after 48hrs. That is why the image is saved in a directory called "temp"!!

Perhaps I'll change this later, but at the moment I strongly advise AGAINST this. You'll spend btc to redirect to a nonexisting picture.

Sorry if s/1 already did this, but I clearly marked the URL as temporary.

[edit]i changed the script to not wipe pictures anymore. however, the current script was never intended for hotlinking. this is a TEMPORARY solution, and this may change as soon as i find time to implement hotlinking in a permanent way. so i still advise against hotlinking, but it is possible now.