Bitcoin Forum

I really would like to open my local client/app with a single click on a link
providing at least sum and receiver-address to the client.

so e.g.
btc://0.25@1HH5zTPQCHwZKwDf8KVADwD3XJBwC1YtXg (http://btc://0.25@1HH5zTPQCHwZKwDf8KVADwD3XJBwC1YtXg)

or
http://img687.imageshack.us/img687/3984/1hh5ztpqchwzkwdf8kvadwd.png (http://btc://0.25@1HH5zTPQCHwZKwDf8KVADwD3XJBwC1YtXg)
(unknown protocols are not parsed correctly as link by this forum)

would hand over a quarter to me :)
without any other service/website


Any suggestions what should be minded beside receiver and the amount to pay or are there better ideas?

related topics:
URI-scheme for bitcoin (https://bitcointalk.org/index.php?topic=55.0)
[RFC] Bitcoin Payment URI scheme (https://bitcointalk.org/index.php?topic=5171.0)
[PULL] URI Support (https://bitcointalk.org/index.php?topic=6205.0)

There are various bitcoin URI proposals already.

bitcoin-qt simply uses "bitcoin:<addr>?label=<label>&amount=<BTC>"  (label and amount are optional)

There is also a wiki page on http://wiki.bitcoin.it that describes a more arcane format.

There is a patch that I made for this forum to support bitcoin:// links somewhere in the Meta section. It lays there for months already because there is no consensus on how the links should look.

My personal favorite is bitcoin:/0.02/address

0.25 is a username? What context do usernames even have in Bitcoin URLs?


Unfortunately this will never happen since URL parsers can't handle it.... since it is even farther outside the URL format than the one in the top post.

Well, let's make it bitcoin://0.02/address then.

It reads very logically: "Send 0.02 to this address", from left to right in natural order.

I'd appreciate a link to the page, as I did not find it.
So youre one of the ppl with the ability to implement and distribute that feature - are there links already handled with your gui?

are you kidding? plz just read again.. no username even mentioned.And that one makes me question your technical qualification. There is no prob in parsing that url.

vv01f, you're heading straight into a shitstorm  ;D

Obviously: https://en.bitcoin.it/wiki/URI_Scheme ;)

Also, theymos et al. had this idea, but it kinda fell out of favor: https://en.bitcoin.it/wiki/X-btc


http://tools.ietf.org/html/rfc3986

Come back when you've read and understood the relevant RFCs for URIs, such as RFC 3986. Neither of these proposals is anywhere near compliant, and that's going to mean breakage out here in the real world.

Not obviously enough  ;D for some reason i overread it on search (https://en.bitcoin.it/w/index.php?title=Special%3ASearch&search=uri)  :-[ .

You mean like e.g. callto://YourSkypeName or tel://0043150123456789 ?  ::) but still parsing was never an issue - or why are there email-addresses with percent-sign as delimiter for lists?
Standards are nice, but sometimes not ultima ratio - or am I wrong?  :-\


AND

amount@address is as convenient as user@host. just project yourself being the "coins" and searching a way to go. thinking of userinfo as userid or even name is a bit crude to me.
It would have been nice to mention the RFC in first place, then I would have reason to doubt your knowledge due to that intentional(?) misunderstanding.

vv01f, I agree with you. But there are lots of people here who have an incredible, pathological need to follow "the standard" to the letter.

By the standard, of course, they mean their interpretation of it and no amount of talking will convince them otherwise.

You will just be labeled all sorts of things and scorned at because "you probably don't even know what RFC means" (actual quote from my previous encounters with these people).

The only way this issue will be resolved: every developer will implement URI's as he sees fit and the best one will eventually win.

So don't waste your breath arguing here, just use the URI scheme you think is best.

But it was my prior intention to argue about the elements of that uri and its options.

I can live with other opinions quite fine :) . At least I try to understand the ways others are thinking regardless the other party does.
Most times the tradeoff is not that far away as soon as everyone realises its an argument not a struggle on true or false.

Finally we now know there are plenty things already thought of in the wiki, as I could have known already if I wasn that blind 8) .

But good luck to you :)

Best approach is to use standards or conventions if they don't have any downsides. In this case, they don't. If they have, it's best to fix the standard. For something like URI-schemes, I think that makes sense, don't you?

one downside I thought of: Users have easily to understand it - like tel://0043155985476 - the know http:// from the web, and they know telephone-numbers, easy

plz post an example thats of the same ease for the sending of some btc to a specific address - just to focus on the topic and not just slapping each other

There are TONS of documents about URL and URI standards available.  People should really read them before they start cooking up schemes of their own so that they don't make basic simple mistakes.

eh, that smells like tripple-post  ;)
behave my friend  :D

you're assuming things that have already been refuted
it seems to be very hard to keep to the point (of the topic)

I'll reply to your point, but this has been discussed in length in these forums and I doubt that any of us will say something new. :)

I'm sure you'll find those topics easily.


That would be tel:+43-1-559-8547 or something like that depending on the context. Just like mailto:vv01f@example.com

tel:// or mailto:// wouldn't and shouldn't work. :)


bitcoin:15VjRaDX9zpbA8LVnbrCAFzrVzN7ixHNsC?amount=1&label=Faucet&message=Donation

Keep in mind that these schemes are mainly meant for parsers. That's also why standards are important.

youre very right :), especially on tel:+43-7654321 - real-world-examples: skype-link (https://support.skype.com/en/faq/FA99/What-are-Skype-buttons-and-callto-links-and-how-do-I-use-them?frompage=search&q=callto&fromSearchFirstPage=false#2), wtai:// (http://forums.devshed.com/mobile-programming-20/phone-number-links-in-wap-pages-145899.html)
so probably a parser (and if only for supporting simple-minded like me) would do better if the common known "://"-string is also accepted - no big deal so far.

now I knwo, Luke (https://bitcointalk.org/index.php?action=profile;u=3318) implemented a URI handler (acc to ~half year ago (https://bitcointalk.org/index.php?topic=6205.0)) - question: why isnt it in use (by shops) already  ??? any examples that do?

it seems I things work out well

It would make more sense for it there to be an RFC for general purpose payment links:

payment://<currency>/<amount>?url=<url>

These links could be handled by any payment provider.   A user could then set up payment providers for any currency.   This type of general purpose scheme is more likely to accrue broad based browser and W3C support, etc.... rather than a one-off for one crypto.

- Erik