Bitcoin Forum

This is a simple project to have a bit.ly style URL shortener for your bitcoin address....  all it needs to provide the full address in plane text.  On account of this usernames reputation.

Longer-term: an API so that the shortened address may be used directly with the bitcoin application.
(Implementation for a private hash for security)   e.g. bitcoinaddress.com/A4IN (Z5 35 Up)  the Z5 part is private and applications can use it to check if the returned address is correct.  Because desired addresses are hard to generate, Prob a six digit base 58 will suffice.

Even Longer-term: a implementation of a Bitcoin DNS style system. (with security)

Any Ideas/Comments??

question, is there a check hash built into the bitcoin address?

[Edit 1] - changed the hash check part... was very vulnerable to an rainbow address table.  38 billion seems like a good balance, have in the API an optional 8, 10, and so on charter checks.

[Edit 2] - changed the bounty... 200 BTC was way more BTC than I have spare.

I'd say only the DNS-like system seems interesting. The addresses are already kind of short, they don't pollute a text like huge URLs...

The main rational that I have for this, is that at the moment it is inconvenient to write a bitcoin address by hand... or even type a 32 character address by hand is annoying... It would be much easier, say by SMS to just message say a 5 charter one.

you can always use copy/paste  ;) or as it was already proposed on this forum use 2D-barcode encoded bitcoinaddress for mobile phones

I own bitcoin.me and a url shortener was one of the things I was thinking of for the domain.Also @bitcoin.me email addresses. This would mean you would also be promoting bitcoin whenever you shortened a url or sent an email from that address.  :)

Personally, a 2D barcode is easier than anything, but its use is mostly limited to smartphones.

An address shortening service would be pretty neat, but I don't think it would catch on unless automatic address resolution was built into the bitcoin client.

I think that there would be many times that a short address would become much in handy...  Say print media, or business cards. - But the main thing is that it gets the ball rolling for a bitcoin DNS system, where we can have addresses like donation.bitcoin.org as a address...

atm you can use any url shorter: say http://goo.gl/oVa2 (http://goo.gl/oVa2) that is my bitcoin address*... down to 4 character... (if you remember goo.gl).

However the site could have instructions, a link to download the bitcoin app... a link to send with an online bitcoin wallet, a link to auto-buy and send mtgox etc...

In the long term, auto generated addresses with DNS could work heaps like the paypal payment system...

There is a whole host of different ways to make this idea profitable.

but that is just my 2cents (well really 200BTC) lol

EDIT: *well except that goo.gl makes it all lowercase...

i had a similar idea for a short url service, where the user creating links could earn btc for views to their created links.

if you add qr on the end of any shortened google link it also creates a qr code  ;D

I'm working on a prototype for a system like this...expect a beta within a week or two.  :)

  Hi all, I just registered to reply to this.  I think this is a great idea, but I'm not sure if I'd trust a 3rd party for something like this.  Instead I'm picturing using the existing DNS infrastructure with a simple TXT record, similar to how SPF et al. work.  The format could be simple, just "BTC=<address>" (or maybe "BTCv1=<address>" to cover our rears for future expansion).

  You could publish your own records for your domains, you can publish dynamic or fast updating records using something like MyDNS.  It really makes it easy for anyone already doing business on the web (To complete your order, send the amount above to Order12345.MyStore.com), and you could still see 3rd party shorteners pop up.

  It would also have the advantage that no new servers would be needed, but when noagenda or someone else does implement an HTTP based service, it would play nice since they'd have a / and probably a protocol, so we could mostly differentiate without even needing an extra lookup.  In the case that we couldn't guess which protocol it was neither the extra DNS query or the HTTP request are huge performance hits.

  As a future enhancement, you could allow conversion of, say, email addresses into subdomains.  So you could send to person1@example.com, and it would lookup a TXT record for person1.example.com, or maybe something like person1.bitcoin.example.com for safety.

  I think this would be a minimal impact change, to try to resolve an address through DNS if it isn't a valid bitcoin address, but I don't know if I'm up to it, since I haven't delved into BT's code at all yet.  I'm sure I could offer a bulletproof implementation on the Linux command line version, using libresolv which (afaik) should be available everywhere without dependency issues... but I'm not sure off the top of my head what the windows equivalent is, and haven't touched wxWidgets before so that would add some time.

  If there's interest in this and nobody else takes it up, I'll see what I can put together at the beginning of November when I have a slot in my side projects list.

p.s. I just put up a TXT record in the above format on one of my email domains (perlstorm.net) for kicks.  If you're not familiar with DNS, either 'dig perlstorm.net txt' on a *nix or 'nslookup -type=txt perlstorm.net' on windows should get the address (as well as my SPF record).

Bitcoin can already pay to an IP address. It wouldn't be a big deal to add DNS support. Maybe an address in a TXT record could be used as a fallback if the IP address isn't accepting payments.

DNS and IP transactions aren't secure, though. (DNS will be perfect for this once DNSSEC is available everywhere.)

I guess the cat's outta the bag now, isn't it!

Couple of things:

We are utilizing TXT records, just like domainkeys, and spf, sshfp, et. al. We will be releasing an RFC with the format soon. (But it's very simple) We personally are using a custom developed authoritative name server written in Erlang - for various reasons including scalability, high availability, and because no nameserver available can handle the dynamic nature of our service. (And I just like flexing my Erlang muscles =) We can service thousands of concurrent requests per second currently on extremely limited hardware.

Using an IP address is just as obtuse as a bitcoin address (which is a huge barrier to adoption), and really isn't the point of this service. You lose the address labeling/generation aspect - which is essential to running a business that accepts bitcoin. In other words, I'm not going to tell a new client I met at a tradeshow and sold something to to send payment to xxx.xxx.xxx.xxx, and nobody is going to remember an IP address off the top of their head - that's exactly why we have DNS.

DNSSEC is a long way off for the com and net TLDs. It's also a pain in the ass to implement and adminstration is non-trivial. We're using GPG signing - it's more robust, far easier to implement, and available today. Signing responses prevents any possibility of falling victim to all currently practical DNS attack vectors. (Along with the standard means to address spoofing...random ports and IDs, etc...)

Unfortuantely, libresolv is not available on Win32 platforms (without Cygwin), so we are using a boost library for DNS resolution. This will be implemented as a seperate application that bitcoin/bitcoind will call out to, or you can use by hand. Also there is a fallback mechanism in place: every DNS record also gets an A record that points to our webserver, so if you put the address into a web browser, you will be shown a (pretty) page with the BTC address and a QR representation of the address. Perfect for the eventual advent of mobile payment clients. (That we also plan on offering!)

IMO, there would be little reason not to trust a well-known 3rd party - as the responses are easily verifiable (in real time, you'll know very quickly if you've missed a payment). You can trust a third party with hosting your address records just as much as you can trust Paypal, LibertyReserves, myBitcoin, mtGox, your bank, or anyone really...but if you're that worried, in the future we plan on releasing our entire system as FOSS - so you can host your own after an apt-get and a bit of configuration.

As noagendamarket mentioned, we are finishing completion of this in the very near term and we will be having a public beta very shortly. We will be releasing an "RFC" and client specifications for our system in tandem so that people writing their own clients, e.g. mybitcoin.com, mtgox and everyone else can interop with our service (and any others) - hopefully the community can standardise on some format. ( Ours is very similar to existing RFCs like it so there should be no problems with using what we have )

Of course hosting your own records on your domain is simple and easy, and we encourage people who are able to do so. However, in addition to our basic hosting services, we will be offering full merchant systems with all the bells and whistles that go along with that; dynamic address generation, redundant, highly available, distributed servers (we're talking 5+ nines here), SLAs, APIs, backend portals to manage your orders and invoicing, and everything else you'd expect from an enterprise level SaaS - some time shortly after our public beta period. Currently we are working on a very, very custom (e)bitcoind that will enable even more functionality.

In other words - we got this covered. Stay tuned. =)

 :o

thrashaholic, that sounds very good!
Well I think that once you have released it... you have earn't a 200BTC reward!

Looking forward to the system... Make my other bitcoins worth more! :D

Thrash, I'm speachless! This is wonderful news! The mobile clients-  will there be one for Android?

I am guessing Android will be the first client available considering it is more open. 
(not that im a google fanboy or anything)  :D

I am an owner of a G1 and own no Apple hardware, so yes - Android will be first, of course. =)

 I have an iphone :P

*fires up angry birds...

Google supports bitcoins, apple doesn't! Na na  :P

LOL 

Apple isnt perfect....

Looks like a domain squatter: http://bit.co.in/

holy shit! 200 BTC is lots of money now...  will restructure this prize!

Thanks for the bump. This might tie into a side project I'm already working on, and I would never have seen it otherwise.

GRrrrrrrr.

I'm working hard on this, and the payment gets cut by 97.5% just before I publish?
That is extremely frustrating!
Rats.

200BTC is worth the same in BTC as it was back then.  I think changing the bounty is quite unfair.

I agree. If the bounty was originally 200 BTC, then surely that meant the OP had 200 BTC physically available, no? (Already earned or bought at a low price?)

Perhaps people should pledge "X USD worth of Bitcoins" if they want the pledge to reflect USD value for example.

Is the original request of a simple shortener for addresses still worth 5 BTC?

I'm really sorry... I would have put a catch all phrase in earlier, however I had forgotten about it.

However 200 BTC is like 10x the market price for such a site.

If I wanted to get it done I could 'pay' almost any of the web-developers for hire 20 BTC and get it done... and own the result.

I don't' think anyone can claim that I don't put lots of money into community projects.
However I just cannot afford the opportunity cost of paying out this pledge. (the full 200 BTC)

Don't worry, I wouldn't pay out 200 BTC for this pledge either. My main point is that people should either:

a) Think solely in terms of BTC without regard for the exchange rates,
OR
b) Include provisions for exchange rates in any pledges, or at least attach a deadline.

Lesson learnt I'm sure ;) I've learnt from it anyway; Will think about this next time I put up a bounty or post in the market section.

Is this helpful in any way: http://radicalmojo.appspot.com/3 (http://radicalmojo.appspot.com/3) ?

You put your address in the first box, and get the minimum unique address (depending on the addresses already in the database). Alternatively, you put some initial letters in the second box, and the system outputs the whole address.

See http://forum.bitcoin.org/index.php?topic=11303.0 for my attempt to claim this 200 5 BTC bounty.

Nice... :)  I'll send you the payment... I really feel bad about not updating this post earlier. :(

I'm a little late and I didn't know about the bounty, but check out http://forum.bitcoin.org/index.php?topic=11838.0 for a much simpler version of this.