Bitcoin Forum
July 21, 2017, 08:50:49 PM *
News: Are you prepared for Aug 1 / BIP148?
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Idea for alternative bitcoin address format for vendors  (Read 1765 times)
realnowhereman
Hero Member
*****
Offline Offline

Activity: 504



View Profile
June 03, 2011, 08:35:42 AM
 #1

Bitcoin vendors (should) generate a new address for each transaction.

They will say something like
Quote
Please send 2.57BTC to 1AAZ4xBHbiCr96nsZJ8jtPkSzsg1CqhwDa

Now... very sensibly, Bitcoin addresses are self consistent, making it very hard to mistype one and send the money to someone other than you intended.

But... the amount can still be mistyped.

How about this then?  A new address format which includes the amount and the address, both checksummed?

Quote
Please cut and paste this address zdfga1AAZ4xBHbiCr96nsZJ8jtPkSzsg1CqhwDa

It would be an extra few bytes at the end of the address, and it would be entirely UI-based, never getting anywhere near the block chain.  But it would mean that a customer could cut and paste the address given by the vendor into the Bitcoin client (or any of the online wallets if it became standardised) and the amount field would be automatically filled in, along with the "true" bitcoin address.  Obviously it would still need confirmation from the user, but it would make accidents like "Ooops I just sent 100 BTC when I meant to send 10 BTC to a vendor" much less likely; and much easier for Grandmas to use.

It could be easily handled by making a new bitcoin address version byte; which would trigger the special handling in the client(s).

1AAZ4xBHbiCr96nsZJ8jtPkSzsg1CqhwDa
1500670249
Hero Member
*
Offline Offline

Posts: 1500670249

View Profile Personal Message (Offline)

Ignore
1500670249
Reply with quote  #2

1500670249
Report to moderator
1500670249
Hero Member
*
Offline Offline

Posts: 1500670249

View Profile Personal Message (Offline)

Ignore
1500670249
Reply with quote  #2

1500670249
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1500670249
Hero Member
*
Offline Offline

Posts: 1500670249

View Profile Personal Message (Offline)

Ignore
1500670249
Reply with quote  #2

1500670249
Report to moderator
Meni Rosenfeld
Donator
Legendary
*
expert
Offline Offline

Activity: 1988



View Profile WWW
June 03, 2011, 08:44:52 AM
 #2

Wonderful idea.

Maybe we should also make it impossible to send twice to the same extended address. (But to maintain the ability to send two separate transactions of the same amount to the same real address, maybe the extended address should also contain some random stuff).

1EofoZNBhWQ3kxfKnvWkhtMns4AivZArhr   |   Who am I?   |   bitcoin-otc WoT
Bitcoil - Exchange bitcoins for ILS (thread)   |   Israel Bitcoin community homepage (thread)
Analysis of Bitcoin Pooled Mining Reward Systems (thread, summary)  |   PureMining - Infinite-term, deterministic mining bond
wumpus
Hero Member
*****
qt
Offline Offline

Activity: 798

No Maps for These Territories


View Profile
June 03, 2011, 12:55:48 PM
 #3

Pretty neat idea.

Though if the amount is encoded into it in unreadable form, the client should show the details after pasting and give you the chance to confirm/reject the transaction.

Bitcoin Core developer [PGP] Warning: For most, coin loss is a larger risk than coin theft. A disk can die any time. Regularly back up your wallet through FileBackup Wallet to an external storage or the (encrypted!) cloud. Use a separate offline wallet for storing larger amounts.
realnowhereman
Hero Member
*****
Offline Offline

Activity: 504



View Profile
June 03, 2011, 03:48:36 PM
 #4

Though if the amount is encoded into it in unreadable form, the client should show the details after pasting and give you the chance to confirm/reject the transaction.

Without a doubt.  I wasn't very clear, but that's what I meant with "the amount field would be automatically filled in".


Maybe we should also make it impossible to send twice to the same extended address. (But to maintain the ability to send two separate transactions of the same amount to the same real address, maybe the extended address should also contain some random stuff).

Good idea.  The current time could be encoded in to it too, to some pre-chosen resolution.. I'd pick nearest hour.  Then the client could also warn the user that the address they are sending to is six months old.

1AAZ4xBHbiCr96nsZJ8jtPkSzsg1CqhwDa
Pieter Wuille
Legendary
*
qt
Offline Offline

Activity: 1050


View Profile WWW
June 03, 2011, 04:38:56 PM
 #5

I think a bitcoin: URI is much more suited than the binary format intended for addresses.

aka sipa, core dev team

Tips and donations: 1KwDYMJMS4xq3ZEWYfdBRwYG2fHwhZsipa
Luke-Jr
Legendary
*
expert
Offline Offline

Activity: 2226



View Profile
June 03, 2011, 08:02:44 PM
 #6

How about "<a href='bitcoin:1AAZ4xBHbiCr96nsZJ8jtPkSzsg1CqhwDa?amount=5X5'>Click here to pay (5 mBTC)</a>"

ene
Jr. Member
*
Offline Offline

Activity: 42


View Profile
June 03, 2011, 08:04:07 PM
 #7

This is what URIs were invented for. Hopefully the bitcoin: URI will be implemented soon.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!