Difference between revisions of "Invoice address"

From Bitcoin Wiki
Jump to: navigation, search
(A Bitcoin address is like an e-mail address)
(BIP 179)
 
(89 intermediate revisions by 29 users not shown)
Line 1: Line 1:
A '''Bitcoin address''', or simply '''address''', is an identifier of approximately 33 alphanumeric characters, always beginning with the number 1, that represents a possible destination for a Bitcoin payment. Addresses can be generated at no cost by any user of Bitcoin. For example, using the Bitcoin software, one can click "Get Address" and be assigned an address.  An example of a Bitcoin address is ''175tWpb8K1S7NmH4Zx6rewF9WQrcZv245W''.
+
A '''Bitcoin invoice address''', or simply '''invoice''', is an identifier of 26-35 alphanumeric characters, beginning with the number <code>1</code>, <code>3</code> or <code>bc1</code> that represents a possible destination for a bitcoin payment.
 +
Invoices can be generated at no cost by any user of Bitcoin.
 +
It is also possible to get a Bitcoin invoice address using an account at an exchange or online wallet service.
  
==A Bitcoin address is like an e-mail address==
+
There are currently three [[List_of_address_prefixes|invoice address formats]] in use:
Like e-mail, you can send Bitcoins to a person by sending Bitcoins to their address.  Somewhat unlike e-mail, one person can, and is encouraged, to have an unlimited number of different Bitcoin addresses. It is recommended that you use a unique address for each transaction.  Most Bitcoin software and websites will help with this, by generating a brand new address each time you use the last one, or each time you ask for a new one.
+
# [[Transaction#Pay-to-PubkeyHash|P2PKH]] which begin with the number <code>1</code>, eg: <code>1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2</code>.<!-- tails donation address -->
 +
# [[Pay_to_script_hash|P2SH]] type starting with the number <code>3</code>, eg: <code>3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy</code><!-- anyone-can-spend, null script -->.
 +
# [[Bech32]] type starting with <code>bc1</code>, eg: <code>bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq</code>.<!--some example LN wallet-->
  
When using a web site that accepts Bitcoins or holds Bitcoin balances on your behalf, that website will create and assign temporary Bitcoin addresses to you so you can transfer funds. The temporary addresses might change each time funds come in, but the old addresses usually remain valid. When you send Bitcoins to such a temporary addresses, they typically get credited to your account at that web site within an hour or two (depending on the site's policy).
+
==A Bitcoin invoice address is a single-use token==
 +
Like e-mail addresses, you can send bitcoins to a person by sending bitcoins to one of their invoice addresses.
 +
However, ''unlike'' e-mail addresses, people have many different Bitcoin invoice addresses and [[Address reuse|for privacy and security reasons]] a unique invoice should be used for each transaction.
 +
Most Bitcoin software and websites will help with this by generating a brand new invoice each time you create an invoice or payment request.
  
==Deposits and withdrawals are alike==
+
A naive way to accept bitcoin as a merchant is to tell your customers to send money to a single invoice address. However this does not work because Bitcoin transactions are public on the [[block chain]], so if a customer Alice sends you bitcoins then a malicious agent Bob could see that same transaction and send you an email claiming that he paid. You would have no way of knowing whether it was Alice or Bob who send coins to your invoice. This is why each customer must be given a brand new invoice.
Most transfers of Bitcoins are simply transfers to a Bitcoin address. There is no distinction between a "deposit" or a "withdrawal": every transaction is a "withdrawal" somewhere and a "deposit" somewhere else, all at the same time. Compatibility is never a concern with Bitcoin.  Any kind of Bitcoin software or website can be used to send Bitcoins to any other kind of Bitcoin software or website, and it will always work reliably.
 
  
For example, if you use the Bitcoin client software, you can transfer your Bitcoins to a web site that accepts Bitcoins by clicking "Send Coins" (in your software), then pasting the temporary address (assigned by the website) into your Bitcoin client software.
+
==Invoices can be created offline==
 +
Creating invoices can be done without an Internet connection and does not require any contact or registration with the Bitcoin network.
 +
It is possible to create large batches of invoices offline using freely available software tools.
 +
Generating batches of invoices is useful in several scenarios, such as e-commerce websites where a unique pre-generated invoice address is dispensed to each customer who chooses a "pay with Bitcoin" option.
 +
Newer [[Deterministic wallet | "HD wallets"]] can generate a "master public key" token which can be used to allow untrusted systems (such as webservers) to generate an unlimited number of invoices without the ability to spend the bitcoins received.
  
If the web site allows you to withdraw Bitcoins, you can transfer them back into your Bitcoin client software simply by pasting a new receiving address that you copied from the Bitcoin software, it into the "your address" box on the withdrawal page of the web site.
+
==Invoice addresses are often case sensitive and exact==
 +
Old-style Bitcoin invoice addresses are case-sensitive.  Bitcoin invoices should be copied and pasted using the computer's clipboard wherever possible. If you hand-key a Bitcoin invoice address, and each character is not transcribed exactly - including capitalization - the incorrect invoice address will most likely be rejected by the Bitcoin software.  You will have to check your entry and try again.
  
No client software is ever actually necessary.  If you have Bitcoins in web site A, and you want to transfer some of them to web site B, then you can copy the payment address from web site B, paste it into web site A's withdrawal page, and perform a withdrawal for the exact amount you want to transfer. Web site B will see the funds from web site A as a deposit, exactly the same as though you had initiated it yourself with the Bitcoin software.
+
The probability that a mistyped invoice is accepted as being valid is 1 in 2<sup>32</sup>, that is, approximately 1 in 4.29 billion.
  
==Addresses can be created offline==
+
New-style [[bech32]] invoices are case insensitive.
Creating addresses can be done without any Internet connection contact with the Bitcoin network.  Address creation can be done completely offline, even in large batches.  Large batches of addresses are useful in many scenarios, such as e-commerce websites where a unique pre-generated address is dispensed to each customer if they choose a "pay with Bitcoin" option.
 
  
==Addresses are case sensitive and exact==
+
==Proving you receive with an invoice address==
Bitcoin addresses are case-sensitive.  Typically, Bitcoin addresses should be copied and pasted using the computer's clipboard wherever possible. If a Bitcoin address is hand-keyed, and each character is not transcribed exactly - including capitalization - the incorrect address will typically be rejected.
+
Most Bitcoin wallets have a function to "sign" a message, proving the entity receiving funds with an invoice has agreed to the message.
 +
This can be used to, for example, finalise a contract in a cryptographically provable way prior to making payment for it.
  
==Each address has a "private key"==
+
Some services will also piggy-back on this capability by dedicating a specific invoice address for authentication only, in which case the invoice address should never be used for actual Bitcoin transactions.
For every visible address, there is a corresponding secret number known as a [[private key]].  When using a Bitcoin client, private key numbers are typically stored in the [[wallet file]].  The private key has a special purpose - it is mathematically needed to create transactions acceptable to the Bitcoin network that respend the funds originally sent to the address. If the private key to an address is lost (for example, in a hard drive crash and the user didn't have backups of the wallet file), any associated Bitcoins are lost forever.
+
When you login to or use their service, you will provide a signature proving you are the same person with the pre-negotiated invoice address.
  
==What's in an address==
+
It is important to note that these signatures only prove one receives with an invoice.
Most Bitcoin addresses are 33 characters.  They consist of random digits and uppercase and lowercase letters, with the exception that the uppercase letter "O", uppercase letter "I", lowercase letter "l", and the number "0" are always avoided.  Bitcoin adheres to a rule of always using the number "1" as the first character - this allows visual discrimination from other types of random character strings that might look like Bitcoin addresses - such as [[private key]]s which start with "5", or coins from Bitcoin's [[testnet]] (which typically start with "m"), or coins from other cryptocurrency systems derived from Bitcoin's source code (which are not compatible with Bitcoin).
+
Since Bitcoin transactions do not have a "from" address, you cannot prove you are the ''sender'' of funds.
  
Some Bitcoin addresses can be shorter than 33 characters.  A significant percentage of Bitcoin addresses are only 32 characters - these are completely valid.  Every Bitcoin address stands for a number - somewhat like an account number.  These shorter addresses are valid simply because they stand for numbers that happen to start with zeroes, and when the zeroes are omitted, the encoded address gets shorter.
+
Current standards for message signatures are only compatible with "version zero" bitcoin invoice addresses (that begin with the number 1).
  
Several of the characters inside a Bitcoin address are used as a [[Base58Check encoding|checksum]] so that typos can be automatically detected and rejected.
+
==Invoice address validation==
 +
If you would like to validate a Bitcoin invoice address in an application, it is advisable to use a method from [https://bitcointalk.org/index.php?topic=1026.0 this thread] rather than to just check for string length, allowed characters, or that the invoice starts with a 1 or 3.  Validation may also be done using open source code available in [http://rosettacode.org/wiki/Bitcoin/address_validation various languages] or with an [http://lenschulwitz.com/base58 online validating tool].
 +
 
 +
==[[Multisignature|Multi-signature]] invoice addresses==
 +
Invoices can be created for keys that require a combination of multiple private keys.
 +
Since these take advantage of newer features, they begin with the newer prefix of 3 or bc1 instead of the older 1.
 +
These can be thought of as the equivalent of writing a check to two parties - "pay to the order of somebody AND somebody else" - where both parties must endorse the check in order to receive the funds.
 +
 
 +
The actual requirement (number of private keys needed, their corresponding public keys, etc.) that must be satisfied to spend the funds is decided in advance by the person generating this type of invoice, and once an invoice is created, the requirement cannot be changed without generating a new invoice.
 +
 
 +
==What's in an invoice==
 +
Most Bitcoin invoice addresses are 34 characters.
 +
They consist of random digits and uppercase and lowercase letters, with the exception that the uppercase letter "O", uppercase letter "I", lowercase letter "l", and the number "0" are never used to prevent visual ambiguity.
 +
 
 +
Some Bitcoin invoice addresses can be shorter than 34 characters (as few as 26) and still be valid.
 +
A significant percentage of Bitcoin invoice addresses are only 33 characters, and some invoices may be even shorter.
 +
Technically, every Bitcoin invoice stands for a number.
 +
These shorter invoices are valid simply because they stand for numbers that happen to start with zeroes, and when the zeroes are omitted, the encoded invoice address gets shorter.
 +
 
 +
Several of the characters inside a Bitcoin invoice are used as a checksum so that typographical errors can be automatically found and rejected.
 +
The checksum also allows Bitcoin software to confirm that a 33-character (or shorter) invoice is in fact valid and isn't simply an invoice with a missing character.
 +
 
 +
==Testnet==
 +
Invoice addresses on the Bitcoin Testnet are generated with a different prefix.
 +
See [[List of address prefixes]] and [[Testnet]] for more details.
 +
 
 +
==Misconceptions==
 +
===Address reuse===
 +
 
 +
Invoice addresses are not intended to be used more than once, and doing so has numerous problems associated.
 +
See the dedicated article on [[address reuse]] for more details.
 +
 
 +
===Address balances===
 +
 
 +
Invoice addresses are not wallets nor accounts, and do not carry balances.
 +
They only receive funds, and you do not send "from" an address at any time.
 +
Various confusing services and software display ''bitcoins received with an invoice address, minus bitcoins sent in random unrelated transactions'' as an "address balance", but this number is not meaningful: it does not imply the recipient of the bitcoins sent to the address has spent them, nor that they still have or don't have the bitcoins received.
 +
 
 +
An example of bitcoin loss resulting from this misunderstanding is when people believed their invoice address contained 3 BTC. They spent 0.5 BTC and believed the address now contained 2.5 BTC when actually it contained zero. The remaining 2.5 BTC was transferred to a "change address" which was not backed up and therefore lost. This has happened on a few occasions to users of [[Paper wallets]].
 +
 
 +
==="From" addresses===
 +
Bitcoin transactions do not have any kind of origin-, source- or "from" address. See the dedicated article on "[[From address|from address]]" for more details.
 +
 
 +
 
 +
==Address map==
 +
[[File:Address map.jpg|700px]]
 +
 
 +
 
 +
==See Also==
 +
* [[Technical background of Bitcoin addresses]]
 +
* [[List of address prefixes]]
 +
* [[Exit Address]]
 +
 
 +
== References ==
 +
<references/>
  
:''See also: [[Technical background of Bitcoin addresses]]
 
 
[[Category:Vocabulary]]
 
[[Category:Vocabulary]]
 +
 +
[[es:Dirección]]
 +
[[de:Adresse]]

Latest revision as of 18:54, 23 October 2020

A Bitcoin invoice address, or simply invoice, is an identifier of 26-35 alphanumeric characters, beginning with the number 1, 3 or bc1 that represents a possible destination for a bitcoin payment. Invoices can be generated at no cost by any user of Bitcoin. It is also possible to get a Bitcoin invoice address using an account at an exchange or online wallet service.

There are currently three invoice address formats in use:

  1. P2PKH which begin with the number 1, eg: 1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2.
  2. P2SH type starting with the number 3, eg: 3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy.
  3. Bech32 type starting with bc1, eg: bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq.

A Bitcoin invoice address is a single-use token

Like e-mail addresses, you can send bitcoins to a person by sending bitcoins to one of their invoice addresses. However, unlike e-mail addresses, people have many different Bitcoin invoice addresses and for privacy and security reasons a unique invoice should be used for each transaction. Most Bitcoin software and websites will help with this by generating a brand new invoice each time you create an invoice or payment request.

A naive way to accept bitcoin as a merchant is to tell your customers to send money to a single invoice address. However this does not work because Bitcoin transactions are public on the block chain, so if a customer Alice sends you bitcoins then a malicious agent Bob could see that same transaction and send you an email claiming that he paid. You would have no way of knowing whether it was Alice or Bob who send coins to your invoice. This is why each customer must be given a brand new invoice.

Invoices can be created offline

Creating invoices can be done without an Internet connection and does not require any contact or registration with the Bitcoin network. It is possible to create large batches of invoices offline using freely available software tools. Generating batches of invoices is useful in several scenarios, such as e-commerce websites where a unique pre-generated invoice address is dispensed to each customer who chooses a "pay with Bitcoin" option. Newer "HD wallets" can generate a "master public key" token which can be used to allow untrusted systems (such as webservers) to generate an unlimited number of invoices without the ability to spend the bitcoins received.

Invoice addresses are often case sensitive and exact

Old-style Bitcoin invoice addresses are case-sensitive. Bitcoin invoices should be copied and pasted using the computer's clipboard wherever possible. If you hand-key a Bitcoin invoice address, and each character is not transcribed exactly - including capitalization - the incorrect invoice address will most likely be rejected by the Bitcoin software. You will have to check your entry and try again.

The probability that a mistyped invoice is accepted as being valid is 1 in 232, that is, approximately 1 in 4.29 billion.

New-style bech32 invoices are case insensitive.

Proving you receive with an invoice address

Most Bitcoin wallets have a function to "sign" a message, proving the entity receiving funds with an invoice has agreed to the message. This can be used to, for example, finalise a contract in a cryptographically provable way prior to making payment for it.

Some services will also piggy-back on this capability by dedicating a specific invoice address for authentication only, in which case the invoice address should never be used for actual Bitcoin transactions. When you login to or use their service, you will provide a signature proving you are the same person with the pre-negotiated invoice address.

It is important to note that these signatures only prove one receives with an invoice. Since Bitcoin transactions do not have a "from" address, you cannot prove you are the sender of funds.

Current standards for message signatures are only compatible with "version zero" bitcoin invoice addresses (that begin with the number 1).

Invoice address validation

If you would like to validate a Bitcoin invoice address in an application, it is advisable to use a method from this thread rather than to just check for string length, allowed characters, or that the invoice starts with a 1 or 3. Validation may also be done using open source code available in various languages or with an online validating tool.

Multi-signature invoice addresses

Invoices can be created for keys that require a combination of multiple private keys. Since these take advantage of newer features, they begin with the newer prefix of 3 or bc1 instead of the older 1. These can be thought of as the equivalent of writing a check to two parties - "pay to the order of somebody AND somebody else" - where both parties must endorse the check in order to receive the funds.

The actual requirement (number of private keys needed, their corresponding public keys, etc.) that must be satisfied to spend the funds is decided in advance by the person generating this type of invoice, and once an invoice is created, the requirement cannot be changed without generating a new invoice.

What's in an invoice

Most Bitcoin invoice addresses are 34 characters. They consist of random digits and uppercase and lowercase letters, with the exception that the uppercase letter "O", uppercase letter "I", lowercase letter "l", and the number "0" are never used to prevent visual ambiguity.

Some Bitcoin invoice addresses can be shorter than 34 characters (as few as 26) and still be valid. A significant percentage of Bitcoin invoice addresses are only 33 characters, and some invoices may be even shorter. Technically, every Bitcoin invoice stands for a number. These shorter invoices are valid simply because they stand for numbers that happen to start with zeroes, and when the zeroes are omitted, the encoded invoice address gets shorter.

Several of the characters inside a Bitcoin invoice are used as a checksum so that typographical errors can be automatically found and rejected. The checksum also allows Bitcoin software to confirm that a 33-character (or shorter) invoice is in fact valid and isn't simply an invoice with a missing character.

Testnet

Invoice addresses on the Bitcoin Testnet are generated with a different prefix. See List of address prefixes and Testnet for more details.

Misconceptions

Address reuse

Invoice addresses are not intended to be used more than once, and doing so has numerous problems associated. See the dedicated article on address reuse for more details.

Address balances

Invoice addresses are not wallets nor accounts, and do not carry balances. They only receive funds, and you do not send "from" an address at any time. Various confusing services and software display bitcoins received with an invoice address, minus bitcoins sent in random unrelated transactions as an "address balance", but this number is not meaningful: it does not imply the recipient of the bitcoins sent to the address has spent them, nor that they still have or don't have the bitcoins received.

An example of bitcoin loss resulting from this misunderstanding is when people believed their invoice address contained 3 BTC. They spent 0.5 BTC and believed the address now contained 2.5 BTC when actually it contained zero. The remaining 2.5 BTC was transferred to a "change address" which was not backed up and therefore lost. This has happened on a few occasions to users of Paper wallets.

"From" addresses

Bitcoin transactions do not have any kind of origin-, source- or "from" address. See the dedicated article on "from address" for more details.


Address map

Address map.jpg


See Also

References