Closed GoogleCodeExporter closed 9 years ago
I must admit that I hate URI shorteners in general and also I don't trust them.
How do I know that they (or an attacker) don't silently change their shortened
URLs? For Bitcoin address shorteners, this is even more of an issue.
I'm still waiting for the shortener whose output (shortened) URI is a
cryptohash of the input URI. This would allow a client to detect tampering. On
the other hand, a secure hash would not be any shorter than the Bitcoin address
to start with.
What do other people think?
Original comment by andreas....@gmail.com
on 7 Aug 2011 at 11:00
I'm pretty sure btc.to is from the people from MtGox and is used in the
official MTGox App. It is also used and supported in #bitcoin-otc, the largest
OTC bitcoin market.
Original comment by jjj...@gmail.com
on 7 Aug 2011 at 6:07
They also have built in QR support. But I'm not sure if that'll help.
So address 1J6973u4SGRCZxAEywz5XUMHrqG9XXqieR becomes https://btc.to/19e/ and
the QR link is https://btc.to/19e/qr
Original comment by jjj...@gmail.com
on 9 Aug 2011 at 2:40
Another option would be support for the firstbits algorithm, which is grounded
in the blockchain - see http://firstbits.com and
http://forum.bitcoin.org/index.php?topic=16217.0
Original comment by neal...@gmail.com
on 21 Aug 2011 at 3:02
Issue 73 has been merged into this issue.
Original comment by andreas....@gmail.com
on 19 Jan 2012 at 4:39
I don't think this will be implemented anytime soon. As soon as HD wallets are
implemented, addresses will be used only once anyway. At present, I suggest
using QR codes and NFC for transmitting addresses.
Original comment by andreas....@gmail.com
on 12 Apr 2013 at 11:00
Original issue reported on code.google.com by
jjj...@gmail.com
on 7 Aug 2011 at 8:08